The system automatically performs costing according to the costing methodology assigned to the business organization. The intercompany batch (PI01 / PI02) appears as a statistical value on the conditions of the sales order screen – the batch has no influence on the final value of the customer`s order. Intercompany fees are not printed on the client`s documents. This pricing procedure (RVAA01) is determined both at the sales order level and in the billing processing for the end customer. We maintain the PR00 condition type to display the price of the order company code to the end customer. Status records for PR00 are maintained through organizational elements of the order group, end customer, and hardware. Z.B.: Commercial organization of the order of the company code + end customer + material. We must also keep the PI01 condition type to represent the costs of the order company code (in other words, the sales of the supplier company code). This is a type of statistical report and is intended for informational purposes only. Status records for PI01 are created with the following key combination: Purchase Order Sales Organization + Delivery Plant + Material Price ICAA01 is determined at the intercompany billing level. This blog contains information about the intercompany process. Your comment touches on a very important and interesting part of the business-to-business sales process! The standard F2 billing document is created with the sales territory of the comp code 1002. The delivery company and the ordering company are part of the same company.
The delivery company`s business-to-business invoicing document is therefore recorded as receipt of the ordering company`s invoice. Since the intercompany invoice comes from the code of the supplier/ delivery company; Thus, the sales area of the supplier company code should also be, i.e. 3000 (not 1002). The delivery plant processes the delivery in order to create an intercompany invoicing document (Type IV billing document) for the selling company. This company code records the invoice accounting for this billing document. The system verifies the company codes of the sales organization and sales plant and automatically processes intra-group invoicing via the intercompany invoicing document. This internal customer number must be assigned to the ordering sales organization. Therefore, the system automatically registers this internal customer number during business-to-business invoicing. Pricing: We need to maintain two pricing procedures RVAA01 and ICAA01. The RVAA01 price scheme represents the PR00 condition type and any other discounts or surcharges intended for the end customer.
IMG >> Sales >> Billing >> Intercompany Billing Thank you for the publication. Could you please let me know what the PATH is for this screen: what will be the pricing procedure that will be followed when billing the customer? As there are types of conditions such as IC01, check all your settings to create intercompany billing again: In this screenshot we assign a factory to a sales area. In the business-to-business billing document, the system supports this sales area. The PR00 condition type is also displayed in the intercompany billing document. They are provided for informational purposes only and do not affect the value of the document. The first billing document created in the company code 1002 and the payer is a customer. The type of condition IV01 in the business-to-business invoicing document represents the turnover vis-à-vis the supplier company. However, the corresponding condition type PI01 in the invoice document to the end customer is displayed as a statistical element for information purposes. The VPRS condition type in the intercompany billing document displays the costs of the delivery company code. or IMG – >Sales and Distribution – > Invoicing – Invoicing > Intercompanies – define > order types for intra-group invoicing ICAA01 pricing procedure – The pricing procedure for intra-group invoicing is the combination of: Sales area (from the supplier company code) + pricing method of the invoicing document type IV + customer pricing procedure of the company`s internal invoicing Assigned to customers. The ICAA01 pricing method has condition type IV01, which represents the revenue from the delivery company code in intercompany billing.
Typically, when dealing with different company codes, you may determine that you need to transfer shares between two different company codes. However, if the share is transferred to the same corporate code, there is no need for an intercompany transaction. However, if the share is transferred between different company codes, there is a transfer of value and an intra-group sale. The sales organization, sales channel and division are assigned to factories for which it is possible to manage sales within the Group. Delivery Plant uses these specifications to process business-to-business billing. As part of a normal business, we may decide to source from Group companies in order to meet excess demand or to make optimal use of overcapacity in the Group`s factories. If we obtain our sales product from a factory of another group company, we can use internal invoicing and generate the necessary documents for both the selling company and the supplier company. Once the issuance of goods has taken place, you can change the delivery for invoicing. You can create the billing documents just like any other billing document on the billing screen: All the parameters have been completed, Let`s now create an intercompany transaction Let`s take an example to better understand intercompany sales.
Suppose there are two company codes, namely 1000 and 2000. A customer can place an order for goods in a sales organization belonging to the company code 3000. However, the goods may be manufactured by a supply plant belonging to the company code 1000. A sales order is created that specifies factory delivery of enterprise code 1000. The sales organization then invoices the customer for the purchased materials. SAP R/3 automatically creates a company-to-company billing document when the customer`s billing document is created. This intercompany invoice is sent from the delivery plant to the selling sales organization. This assignment determines the sales area (in the intercompany invoicing document). This is really a good article, to clarify the basics, you can help me with one of the requirements where intercompany billing needs to be increased to settle insurance claims, but there is no investment involved.
What measures should be taken and whether the „PLANT“ is mandatory in this IC invoicing process? This invoicing document is the invoice that is created by the supplier (who delivers the goods to the customer based on the instructions of the client) and sent to the order center. IV01 and IV02 are used with subtotal 9 (gross value) and routine 22 (intercompany billing) as shown below. In standard SAP, business-to-business sales have two pricing methods RVAA01 and ICAA01. The customer places an order with the reservation number 1002. 1002 decides to deliver from the 2010 factory belonging to the company code (3000). I created and saved a normal sales order. Inventory entries for delivery are located in factory 2010 and company code 3000. In addition, two billing documents are generated with reference to the same shipping document. The document flow is as follows: Delivery may need to be processed twice for invoicing. In the SAP Sales & Distribution module, intercompany sales take place if the sales organization belongs to a different company code than the supplier factory. The transaction path to access the invoicing of intercompany sales is: How can we use a single pricing procedure for the entire process (invoicing to the customer, invoicing to the company code) The intercompany invoicing document is created with the sales area of the supplier entity (i.e.
the sales area of the company code 3000). I created a customer ID (XD01) in 1002 and assigned it to the sales organization of 1002. This customer ID is a payer and represents 1002 for intra-group settlement of the seizure….