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_ENV_0004 | Company Configuration for Inbound EDI |
| Transaction Code | S_KK4_66000100 | IMG-Aktivität: SIMG_ENV_0004 |
| Created on | 19991013 | |
| Customizing Attributes | SIMG_ENV_0004 | Company Configuration for Inbound EDI |
| Customizing Activity | SIMG_ENV_0004 | Company Configuration for Inbound EDI |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ENV_0004 |
You can configure EDI to process incoming billing information for ventures in which the company using JVA holds a non-operating interest. To configure your company for inbound EDI, you must at a minimum specify the following settings for the FB01 posting that will be created with the inbound EDI information:
- Method for determining the posting date of the FB01
- Level of detail or aggregation at which data will be posted in the FB01
You can also specify settings for the following types of data to filter incoming EDI data:
- Disposition of memo AFEs
- Treatment of working interests that exceed those stated in the transmitted operating statement
- Handling of monetary amounts that represent discrepancies in transmitted totals
Example
Requirements
Before performing any customization, you should run the RGJVEDII program to install basic EDI inbound configuration.
Standard settings
Usually the date on which the FB01 is posted is selected as the date type for determining the posting date of the FB01.
Also, you can aggregate data on the FB01 at the cost object and account level, but usually detailed posting at the service code level is selected.
Recommendation
Activities
For AFEs, working interest shares, and monetary amounts that deviate from the controls specified in the EDI transmission, there are two alternative treatments. If you so choose, the FB01 containing the data will be parked. On default, an IDOC (intermediate document) is created with the data and a status of error.
If you choose to park the FB01 containing anomalous data, you must also specify thresholds for memo AFEs, working interest shares, or monetary amounts that will trigger parking of the FB01.
You may also specify a particular posting period and year for the FB01 posting.
Further notes
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| 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_T8JDA | V - View | GJEA | ENV_0004 | EDI inbound: company configuration |
History
| Last changed by/on | SAP | 20010305 |
| SAP Release Created in |
