![sap movement type for intercompany transactions sap movement type for intercompany transactions](https://blogs.sap.com/wp-content/uploads/2013/09/16_274786.jpg)
- #SAP MOVEMENT TYPE FOR INTERCOMPANY TRANSACTIONS MANUAL#
- #SAP MOVEMENT TYPE FOR INTERCOMPANY TRANSACTIONS CODE#
The pricing on sales order now shows another pricing condition type for inter-company pricing. In cases where affiliate fulfils the order, it triggers cross-company scenario. Subsequently, supply chain can allocate the products ordered from own plant or from plant of an affiliate. In order based billing scenario, customer billing takes place on receipt of order. A customer places order the fulfilment of which takes place from an affiliate company.
![sap movement type for intercompany transactions sap movement type for intercompany transactions](https://www.saptutorials.in/wp-content/uploads/2021/07/image-10.png)
The screen views below show an example of STO process with accounting entries.Ĭross-company sales order involves three parties – end customer, selling entity and order fulfilling entity.
#SAP MOVEMENT TYPE FOR INTERCOMPANY TRANSACTIONS CODE#
Assign default tax code for vendors per country.Assign G/L account to post offset for inter-company vendor invoice.Assign vendor company code on invoice to company code.Make settings for invoices received via electronic data interchange (EDI).In message control, assign message type to create invoice. Maintain customer profile (KU) to create Invoice/Billing document.However, if order combination is allowed for deliveries, it is easier to reconcile accounting with AP I-doc since the accounting is a mirror image of the AR side. ERS can read all goods receipts in receiving entity and post invoices using rate from STO. As an alternative to creating AP I-doc, it is possible to flag the purchase process for ERS (Evaluated Receipt Settlement).Process code INVF posts FI invoice, INVL/INVM can post MM logistics invoice. Maintain vendor profile (LI) for the inter-company vendor.Make sure logical system (LS) is active for the client.
#SAP MOVEMENT TYPE FOR INTERCOMPANY TRANSACTIONS MANUAL#
Some manual configurations are required to make the invoicing process work.Some further settings to get vendor invoice to post in receiving entity are defining and assigning output type to billing document & setting up relationship between customer master of sending entity with vendor master of receiving entity.Inter-company billing document can trigger an accounts payable I-doc to post vendor invoice in receiving company code. Activate account assignment of offsetting entry of inter-company transaction.Maintain pricing conditions if required as per definition of pricing procedure. The settings of inter-company pricing procedure are important to pass product price from STO in billing documents. Maintain and assign an inter-company pricing procedure to the sales area of supplying plant.Define supplying and receiving plants for STO process and link those to respective customer master, sales area (sales organization, distribution channel, division), purchase document type, delivery type, checking rules.Some important definitions in configuration are: The process requires configuration of stock transport orders, inter-company pricing and billing.
![sap movement type for intercompany transactions sap movement type for intercompany transactions](http://saphelp.ucc.ovgu.de/NW750/EN/07/09be4ea2d3452eaa1f6765a86d491a/ppt_img.gif)
Stock Transport Order (STO) is a type of purchase order document that posts goods movements in sending and receiving plants while also accounting for receivables and payables in their respective company codes. In the accounting entry, there is a debit to expense account in 2000, a credit to vendor in 1000 and offsetting items inter-company vendor and customer accounts respectively. In the example shown below, company code 1000 is posting a vendor invoice for an expense incurred in company code 2000. The company codes used share the same controlling area in these examples.Ĭross-company code transaction (viewed from transaction code FBU3) is an accounting entry involving more than one company code. Sensitive information had to be masked on screenshots. The document may not be comprehensive, uses simple & basic examples. The document is not describing detailed configuration behind these transactions or any valuations such as transfer pricing.
![sap movement type for intercompany transactions sap movement type for intercompany transactions](https://blogs.sap.com/wp-content/uploads/2013/09/27_274847.jpg)
This is a high-level document that shows some cross company and inter-company postings. Many inter-company transactions may occur between difference entities (company codes) and SAP implementation should support such transactions and valuations. These company codes could be establishments in different geographies, countries or could be related parties or affiliates operating at different levels of integration of supply chain (to give some examples). Each legal entity could be a separate company code in SAP organization structure. To manage a complex business, often corporates incorporate multiple legal entities. Inter-company resource sharing in Production Process Cross-company Stock Transfer with shipping and billing