- #ABACUS CORPORATION PTE LTD MANUAL#
- #ABACUS CORPORATION PTE LTD CODE#
As an alternative to creating AP I-doc, it is possible to flag the purchase process for ERS (Evaluated Receipt Settlement). #ABACUS CORPORATION PTE LTD CODE#
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. #ABACUS CORPORATION PTE LTD 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. 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. The offsetting line items from inter-company clearing create a payable in 2000 and a receivable in 1000.Ĭross-company Stock Transfer with shipping and billing The goods receipt posted against the purchase order creates expense in 2000 but liability to pay vendor in 1000. In example shown, purchase order is in company code 1000 and the assigned cost center 2010 belongs to company code 2000 (other cost objects such as orders can also be used). In this process, a purchase order on a vendor is opened assigning cost center of another entity in the account assignment segment. 
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. Cross-company code transaction in FIĬross-company code transaction (viewed from transaction code FBU3) is an accounting entry involving more than one company code. The company codes used share the same controlling area in these examples.
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. 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.
0 kommentar(er)
