Intercompany business processing describes business transactions which take place between two plants in different company codes belonging to one organization. The ordering plant orders goods from a plant which is assigned to another company code.
The following intercompany business transactions are possible:
- Intercompany sales processing
A sales organization which is assigned to the ordering company code creates a sales order ordering goods from a plant assigned to another company code.
The plant in the delivering company code delivers the goods to the customer for whom the sales organization placed the order.
- Intercompany stock transfer
A purchasing organization which is assigned to the ordering company code creates a purchase order ordering goods from a plant assigned to another company code.
The plant in the delivering company code delivers the goods to the plant for which the purchasing organization ordered the goods.
Because the two companies balance their accounts independently, the delivering company must bill the ordering company for the goods. This internal billing transaction is carried out by means of an intercompany billing document. The delivering company bills the ordering company at a price that allows the delivering company to cover its costs.
In this document I will detail Intercompany Stock Transfer with examples and how it is done in SAP.
Take an example of a company structure
Company Structure
| Company code | Plant | Name |
| 1000 | A | Steel Power |
| 1100 | B | Steel Racer |
Business Transaction
Plant A orders 100 tons of "Steel-1" from plant B at a price of USD 10.00 per ton.
1. Plant A, company code 1000:
The person responsible creates a normal purchase order (type NB) for the vendor Steel Racer who is assigned to Plant B.
In SAP: - Create IG process order using ME21N
2. Plant B, company code 1100
On receipt of the purchase order, the vendor Steel Racer enters a delivery for 100 tons of "Steel-1".
In SAP: - Create OBD using VL10H or VL10B
You can find this OBD number in Purchase Order History tab in PO
3. When the material leaves the premises, the vendor Steel Racer posts goods issue.
The values and the quantity are not yet posted in the receiving plant (Plant A).
In SAP: - Go to VL02N and do following steps:-
1. Batch determination of delivery.
2. Complete picking.
3. Remove transport block.
4. Do PGI of the delivery.
At this point an Outbound Idoc is triggered. Setting for this Idoc in partner profile is done in customer partner section.
As per business requirement, the data in this Idoc can be modified as well. Process code
SD05 is used in message type DESADV. This Process code is attached to FM
IDOC_OUTPUT_DESADV01, in this FM there are some user exits where Idoc data can be modified.
4. Plant A, company code 1000:
When the material arrives at Plant A, the person responsible posts goods receipt against the purchase order. The system now posts values and quantities in the receiving plant.
In SAP: - An IBD is created in the system. This IBD is created via an inbound idoc to same SAP system from where the Outbound Idoc of OBD was sent.
This IBD can be seen in the confirmation tab of the PO.
5. Plant B, company code 1100:
On the basis of the delivery, the system creates a billing document (intercompany billing) amounting to USD 1000.
6. Plant A, company code 1000:
In company code 0001, the incoming invoice can be posted by posting an Invoice entry with an internal billing document via Idoc.
In SAP: - Idoc setting
Document flow of an OBD created via this IG process.
So by taking the help of SAP EDI IG process flow can be completed in real time.
Reference :- help.sap.com