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. In addition to “business-to-business sales,” the “business-to-business transportation” process is a possible mapping scenario in SAP S/4HANA. A purchasing organization assigned to the purchase order calendar creates a purchase order that orders goods from a factory assigned to another company code. The factory in the delivery code delivers the goods to the factory for which the purchasing body ordered the goods. Since both companies balance their accounts independently of each other, the supplier company must invoice the goods to the ordering company. This internal billing transaction is carried out via an intercompany invoicing document. The supplier company will charge the ordering company a price that will allow it to cover its costs. The following intercompany business transactions are possible – Processing of intercompany sales Transfer of intercompany shares All parameters have been defined, we now create an intercompany transaction In this document, I explain the details of the intercompany sale process as well as the configuration steps.

Changes to the order are more easily synchronized, but also have an immediate impact on production. Should this always happen? In the usual standard distribution process, better insulation and separation takes place due to separate orders. The intercompany invoicing document type IV is assigned to all types of order documents for which intra-group sales processing can be carried out. 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 SAP tutorial focuses on understanding the SAP Intercompany sales process. Business-to-business sales processing allows a company to sell goods from a factory assigned to another company code. Both scenarios in SAP allow for much lighter mapping of business-to-business processes, also known as business-to-business processes, than the conventional “sales to end customers” and “intra-group sourcing” approaches. When processing the shipping order, the recipient of the goods is entered into the order and copied into the shipping document. This is not possible with this transaction, but there is no sales order. Instead, the recipient is determined by the corresponding setting in Materials Management.

There, a corresponding customer master is assigned to each target plant. In addition, the destination factory is entered by the user in the order in which stocks are transferred. Unlike “normal” order processing, two invoices are created for delivery in the inter-company sales scenario. First of all, the external invoice is generated in the code of the sales company. The distributor uses it to invoice the delivery to the end customer. The turnover is recorded in the financial accounting and adopted in the income statement. Here, however, the costs in the income statement are usually not determined from the moving average price, as it is known that this reflects the valuation price in the manufacturing enterprise and therefore the expected production costs from the point of view of another enterprise code. The costs of the business case are therefore often determined using the “internal moving average price”. This is the price that the sales company pays to the production company.

From the point of view of the sales company, the average internal mobile price therefore represents the cost of sales. In the last step, we arrive at the registration of the incoming invoice in the code of the sales company. In the “normal” purchase process (purchase requisition, purchase order, receipt of goods, invoice), the incoming invoice is validated via the verification of the invoice with regard to the purchase order and receipt of the goods. In the conventional process (sale to end customers), this would be done in a congruent way. However, since the accounting of the purchase order and receipt of goods in distribution operations does not apply in the business-to-business sales scenario, this function cannot be used here, which is why the invoice must be entered directly into the financial accounting as a supplier document. . . .