SAP FICO IDoc Interface: Inventory Management to Accounting

Goods movements result from transactions in the Production (PP) and Sales and Distribution (SD) application components, or from inventory postings. In Logistics, they lead to adjustments in warehouse stock in the Inventory Management (MM-IM) application component. This also results in a posting to Accounting. Therefore, Accounting receives the corresponding data from Logistics.

Consumption of raw materials results in an inventory change posted to Inventory Management. The posting transfers to Accounting.

400000 Raw Material Consumption to 300000 Raw Materials $ 40000

The posting updates to Controlling (CO).

Data Transfer from Inventory Management in an External System

The SAP R/3 Accounting components can accept data from goods movements posted in external logistic systems. The inbound IDoc ACPJOU01 from the RW interface is used for this purpose (refer to IDoc Interfaces for Data Transfer to the RW Interface).

Communication with ALE

If you use distributed systems (Application Link Enabling = ALE), the inbound IDoc for goods movements in Accounting communicates with the outbound IDoc for Inventory Management in the SAP R/3 System.

Data Transfer to Accounting in an External System

To transfer goods movement data from the SAP R/3 System to the Accounting components in an external system, you use outbound IDoc ACPJOU01 for Inventory Management (MM-IM).

Data Transfer to Accounting

Each goods movement in the Logistics components of the SAP R/3 System transfers data to outbound IDoc ACPJOU01, depending on the Customizing settings.

First, function module IDOC-OUTPUT_CHECK conducts general data consistency checks. Then, function module IDOC_OUTPUT_ACPJOU_PROJECT projects the RW document onto an IDoc-specific internal structure and converts quantities and currencies to the ISO standard. Finally, processing branches to function module IDOC_OUTPUT_ACPJOU_POST, where the initial field values of NUMC reset to SPACE and those fields change for which defined conversions exist in the user interface.

A customer function is provided for the IDoc header and items. An IDoc extension fills several segments with additional lines. However, you cannot change the existing data in the IDoc, that is, you cannot modify existing lines.

If errors appear in Accounting during processing, corresponding messages appear and are registered in Logistics. Confirmation of IDoc processing from Accounting is supported by IDoc ACCONF01.

BODs

IDoc ACPJOU01 fulfills the Open Application Group (OAG) communication structure for the Business Object Documents (BODs) Post Journal (goods movement) and Confirm for the communication between the logistics and accounting systems.

• The outbound IDoc for inventory management can be transferred to the BOD structure. SAP does not convert IDocs into BODs; this service is provided by certified EDI and ALE partners.

• The inbound IDoc for Accounting can be provided with data through the BODs.

Preconditions and Requirements

Synchronisation of the outbound and inbound systems is mandatory; the same account assignment objects must exist in both systems during the data transfer.

The outbound system does not check whether the account assignment objects exist in the inbound system. Before data transfer, you should ensure that the required account assignment objects exist.

Structure of Idoc ACPJOU01

For more information about the structure of ACPJOU01 and its documentation, proceed as described Displaying IDoc Type and Segment Documentation.