Hierarchy
EA-FIN (Software Component) EA-FIN⤷
CA-JVA (Application Component) Joint Venture und Production Sharing Accounting⤷
GJV2 (Package) Joint Venture Development
IMG Activity
| ID | SIMG_NOP_0003 | Mapping Inbound EDI Qualifiers to JVA Processes |
| Transaction Code | S_KK4_66000042 | IMG-Aktivität: SIMG_NOP_0003 |
| Created on | 19991013 | |
| Customizing Attributes | SIMG_NOP_0003 | Mapping Inbound EDI Qualifiers to JVA Processes |
| Customizing Activity | SIMG_NOP_0003 | Mapping Inbound EDI Qualifiers to JVA Processes |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_NOP_0003 |
You can use the mapping qualifiers set up in master data to configure JVA non-operated billing for incoming EDI. In this step of configuring incoming EDI, you can identify the accounting treatment to be accorded the expenses associated with a particular qualifier used for the invoice 810 transaction set.
In this step of configuration, you can associate certain qualifiers, which represent specific types of expenses, with certain JVA processes (identified by the function and function item combination specified on this screen).
The JVA process carries a set of posting rules which will determine how the accounting entries resulting from execution of the process will be posted. For inbound EDI transmissions, the posting rules for a function-function item combination will be applied to the expenses associated with the mapping qualifier connected with the function and function item on this configuration table. In addition, an account to which the expense will be booked must also be specified on the same line on which the mapping qualifier is connected to the function-function item combination.
Example
Requirements
As part of configuring JVA processes, you should specify posting rule details for all non-operated JVA function and function item combinations. These posting rule details should be configured for the JVA company before you assign mapping qualifiers to the function and function item.
As part of defining JVA configuration master data for your company, you should have set up mapping qualifiers for inbound EDI processing. A mapping qualifier should be set up for each type of expense that is to receive a specific type of accounting treatment. Mapping qualifiers can be specified for both 810 and 819 transaction set expenses.
Standard settings
During JVA processing in mapping inbound EDI as part of master data set-up, you will associate these mapping qualifiers with JV/properties and JVA cost objects.
Recommendation
Activities
To associate the type of expenses identified by a specific mapping qualifier on the 810 transaction set with a JVA process and with a specific G/L account, enter the following information on the JV EDI Inbound: Account Transaction Mapping Table:
In the Qual field, enter the code for the mapping qualifier for a particular type of expense that is to be handled by a specific JVA process and assigned to the G/L account entered on this line.
In the Func field, enter the code for a JVA function for non-operated JV expense processing.
In the Item field, enter the code for a JVA function item for a particular line item posting controlled by the function specified on this line.
In the Account field, enter the code for the G/L account to which the expense associated with the mapping qualifier and posted by the JVA process identified by the function-function item combination will be booked.
Further notes
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
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 |
| V_T8JDQ | V - View | GJEO | NOP_0003 | EDI inbound: 819 account mapping |
History
| Last changed by/on | SAP | 20010306 |
| SAP Release Created in |
