SAP ABAP IMG Activity PSM_VC_FM_ADVANCE_CA (Define Additional Lines for Advance Payment (Spain))
Hierarchy
☛ EA-PS (Software Component) SAP Enterprise Extension Public Services
   ⤷ PSM-FM-MD (Application Component) Master Data
     ⤷ FMCC (Package) FIFM: Cash budget management customizing
IMG Activity
ID PSM_VC_FM_ADVANCE_CA Define Additional Lines for Advance Payment (Spain)  
Transaction Code S_AEN_10000598   (empty) 
Created on 20050314    
Customizing Attributes PSM_VC_FM_ADVANCE_CA   Define Additional Lines for Advance Payment (Spain) 
Customizing Activity PSM_VC_FM_ADVANCE_CA   Define Additional Lines for Advance Payment (Spain) 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PSM_VC_FM_ADVANCE_CA    

Use

This IMG activity is for the use of Spanish customers. Here you can define:

  • A G/L account to be derived from the document type when a payment request is created
  • New documents to be automatically posted when a payment request is posted

See the example below for further details.

Requirements

The following prerequisites apply:

Standard settings

Activities

Example

For the two functions involved, there are two examples:

  • G/L account to be derived from the document type

    Under the node Payment Request you enter the following data:

    CoCode    Doc. Type    First Year    G/L Account

    001    AA    2005    999999

Note
This line is entered only once. Then, every time you create a payment request for company code 001, document type AA, in fiscal year 2005 or the following, G/L account 999999 is automatically derived for the payment request.

  • New documents to be automatically posted

        Under the node Payment Request, you enter the same data as in the above example.

        Under the node Lines for New Postings, you enter the following:

    Counter    Doc.Type    Vendor    PK    SpGLAc    Acct        Off.PK    Off. Acct

    1    A1    X    29    Z    -        50    111111

    2    A1    X    29    H    -        50    111111

    3    A1    X    21        -        50    111111

    4    A1        40        111111        50    444111

    5    A2        40        111555        50    555000

In this case, when you post a payment request as specified in the first example, two new documents are generated and posted. Both of them contain the same amount as the payment request:

  • The first document has document type A1 and contains four line items:
    • One line item is to be posted for the vendor. In this example, there are three lines for vendor posting (for different special GL indicators). When the payment request is posted, only the line with the same GL indicator as the one used in the payment request is used for the new document.
      If the payment request has special GL indicator Z, Customizing lines 2 and 3 will be ignored. If the request has special GL indicator H, Customizing lines 1 and 3 will be ignored. And if the request has no special GL indicator at all, Customizing lines 1 and 2 will be ignored.
    • The second line uses posting key 50 to post to account 111111.
    • The third line uses posting key 40 to post to account 111111.
    • The fourth line uses posting key 50 to post to account 444111.
  • A second document is posted with document type A2 using posting key 40 to post to account 111555. As the counterpart, posting key 50 is used to post to account 555000.

Business Attributes
ASAP Roadmap ID 105   Define functions and processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG PSM_VC_FM_ADVANCE_CA 0 KI48000005 Request 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VC_FM_ADVANCE_CASH C - View cluster SM34  
History
Last changed by/on SAP  20050503 
SAP Release Created in 600