Ansicht
Dokumentation
JV EDI Outbound: Invoice and Operating Statement ( RELNJVA_30C_EDI_OUTBOUND )
RFUMSV00 - Advance Return for Tax on Sales/Purchases General Material DataThis documentation is copyright by SAP AG.
Short text
JV EDI Outbound: Invoice and Operating Statement
Description
By making use of the JV EDI Outbound process, standardized data can be extracted and transmitted electronically to other JV trading partners for processing on their systems, provided that an EDI interface exists with these partners.
This interface currently only supports US trading partners, has been developed in compliance with the JIBE standards specified by the PIDX (Petroleum Industry Data Exchange) committee and adheres to the ANSI X12 protocol.
Joint Venture supports the creation of Invoice (810) and Operating Expenditure Statement (819) transaction set IDocs.
IDoc contents
The Invoice transaction set is comprised of summary level information. It uses the JV_INV01 IDoc type which has a fixed structure for most part, however it is very flexible with regard to supplemental detail.
The Operating Statement transaction set, unlike the Invoice, contains detail level information. It makes use of IDoc type JV_EXP01 which also has a fixed structure and flexibility in supplemental detail.
Supplemental detail is incorporated into the transaction sets mentioned above and is contained in the PID, DTM and JID segments. All supplemental detail segments are fully configurable and will be described in more detail under User Interface.
Processing
Billing extract data is used as input into the 810 and 819 transaction set creation, which is based on industry defined service codes for each of these transaction sets. There are deliberate overlaps in the information transmitted in these transaction sets. Based on service codes, it is determined by the receiving partner's system which transaction set to utilize. The industry has indicated that it will probably attempt to eliminate the 810 transaction set in the near future and move to 819-only based processing.
Installation
The first step is to install the basic JV EDI Outbound configuration by executing program RGJVEDIX. This will only apply configuration to empty tables, if re-installation is required then the applicable tables must first be cleared. This program installs almost all the non-partner specific default configuration and is a pre-requisite for the partner profile configuration. All relevant configuration for JV EDI Outbound is listed below.
Customizing
After the basic configuration described above, the following must also be configured:-
- EDI port definition
- EDI partner profiles (with message control and outbound parameters)
- JV operator address and contact details
- JV operator profile and JIBE details
- JV partner profiles and JIBE details
- Billing structure EDI settings
- Invoice service codes
- Operating statement service codes
- BI mapping to invoice service codes
- Account, class/subclass mapping
- Supplemental driver mapping to BI/account/RI/cost object
- EDI billing levels
- Supplemental detail sets
- EDI supplemental segment field components
- EDI supplemental segment drivers
- JIBE condition codes
User Interface
The level of supplemental detail generated and transmitted by the JV EDI Outbound process may be strongly influenced by configuration. The supplemental segments are dynamically built based on billing levels defined in SDS configuration. These billing levels dictate which segments and segment fields are selected from the supplemental segment driver table and how the fields will be populated for segment creation. In order to populate a segment field, an associated component from the supplemental segment field component table, determines whether the value will be derived from a literal, another field or by calling a program form routine to extract the information. By making use of the above tables and a combination of standard and custom form routines defined in user exit LGJEOFZZ, the level of supplemental detail required can be changed without modifying standard code. Individual fields or entire segments can be added or deleted by using this functionality. The introduction of additional field components provides flexibity regarding segment field population.
Error Recovery
When the JV EDI Outbound process is being executed in background mode and a fatal error is encountered for any one of the IDocs created, the processing will terminate with an error. This will result in a mix of correct and incorrect IDocs. Manual intervention is required in order to rectify the problem and recreate only the IDocs having errors, by executing the process for specific partners and properties selectively.
Dependencies
JV EDI Outbound is dependent on the successful execution of the Billing Extracts to be used as input for Invoices and Operating Statements. This processing will normally take place after the end of a fiscal period. The Billing Extracts in turn are dependent on Cutback. For additional information on the level of supplemental detail available, refer to JV Billing functionality notes.
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 6280 Date: 20240520 Time: 203652 sap01-206 ( 132 ms )
