Automatic posting to vendor account is done by EDI. This process requires several steps: 1. Creating a Customer to represent the receiving Company.
Creating a Vendor to represent the supplying company. Creating a Port 4. Maintain an Output Type 5. Creating a Logical Address 6.
The relevant MM customizing is maintained. The relevant FI customizing is maintained. Note: The customer has been created in the supplying company code. The Vendor is created with the standard transaction XK Note: The Vendor is created in the receiving Company Code. The organizational data in this case is the same as above. A dialog box will open asking whether you want the system to generate an automatic name or whether you wish to use your own name.
Intercompany STO Process
Port name: Automatically generated Version: 4. Assign Output Determination Procedures. Code VV Logical address P is made of the supplying Company Code and the receiving Customer P Note: If the receiving Customer is a numeric number you must add zeros between the Company code and Customer number so the Logical Address will be 14 digits.
In our case the customer is an alpha numeric number so the second line was not necessary.Purchasing: Company Code, Plant:Sto. Loc:Purchase Organization:.
Loc:Sales Area, 66, 66, Shipping Point Org Here Maintain the supplying plant so that it is linked to the vendor master. Note: A Plant can only be assigned to one vendor number. So we have to extend the same vendor number to different Pur.
Org if required. Ch Norm Standard Item. Note: If You are not able to see tax condition types or not maintaining any tax indicators then it is not possible to Create a delivery against STO. Same applies to Customer Master in Step2. Loc with below selected views.
B — SD Delivery Standard. Otherwise Goods Receipt have to be carried out in another step. It depends on Partial deliveries allowed or not.
Then the remaining quantity will not be shown as open in requirements. Make sure You have sufficient stock in issuing storage location of supplying plant. Note: If you are using one step procedure the enter the receiving storage location Here Observe the shipping tab with the above details as shown. Here first of all SAP checks for any plant assigned in vendor Master. Create condition record for output tax condition type in Trasaction VK MWST output tax.
Note: To adopt price from purchasing in to billing create a condition type with same name as PB Now the PO price is adopted in to billing. Here make sure that delivery date is in between the dates entered. Then Execute. Note: If you are able to see an extra line item with status green proceed to next step or else click on log button as shown above.
Go to Transaction VL02N. In Goods Movement tab observe the movement type two step. In item Conditions Tab Observe conditions as shown below. If You are not able to process PGI, then check WM is activated in storage location or if one step procedure check PO whether receiving storage location entered or not. In Transaction VF01 Create billing document with reference to outbound delivery. Make Sure Account determination has been done and Save the billing document.
Observe the accounting document. Check the accounting document. Not possible to determine shipping point for item Message no.During a business transaction in which the organization belongs to another company code than the delivering plant, an intercompany sale from stock is carried out.
In this case, intercompany billing is carried out between both company codes with the help of an intercompany billing document. Intercompany sales and distribution processing allows a company to sell goods from a plant which is allocated to another company code.
The system checks the company codes of the sales organization and of the delivering plant and automatically carries out intercompany billing processing for different outcomes. Two billing documents are created in this case:. A customer billing document which is sent from the sales organization to the customer who receives the goods. An intercompany billing document which is sent from the delivering plant to the sales organization.
The difference between the customer billing document and the intercompany billing document remains in the selling company as a contribution margin. To be able to use intercompany billing for the intercompany sale from stock, you must set the configurations to the following points:. Allocate corresponding organizational data for intercompany billing to the plants with which intercompany sales and distribution processing is to be carried out.
For controlling intercompany sales from stock, the following configurations have been set in Customizing:. For the definition of the billing document, the billing type II intercompany billing was included. Condition types PI02 for condition rates to be determined in percent and PI01 for condition rates with fixed amounts have been included for calculating intercompany billing prices.
The system checks the allowed combinations of sales organization, distribution channel and plant by means of the table TVKWZ. Specify the billing type for intercompany billing "IV" for each sales document type for which you want to use intercompany billing. Allocate appropriate organizational data for inter-company billing to the plants, with which intercompany sales and distribution processing should be carried out in the fields "Sales organisationDistribution channel and Division IV".
Sales org will accept and punch the order in the system with sold to party as end customer code in the system. This can happen only after raises invoice to his end customer to whom the material has been delivered by Assign plant of delivering company code Eg.
Plant to be selected is delivering plant belonging to different company code. With this selection system will treat this order as intercomany sales. With reference to this order delivery will be created from the delivering plant and post the goods issue for this delivery. Ordering sales org will create billing document F2 with reference to delivery for end customer. Not what you're looking for? Search community questions. This question has been deleted.
This question has been undeleted. Former Member. Posted on Apr 11, at AM Views. Add comment. Related questions. Sort by: Votes Newest Oldest. This answer has been deleted. This answer has been undeleted. Posted on Apr 11, at AM.
Hi Annie, The basic idea of Intercompany Billing is shown below. Intercompany Billing During a business transaction in which the organization belongs to another company code than the delivering plant, an intercompany sale from stock is carried out.To manage a complex business, often corporates incorporate multiple legal entities.
Each legal entity could be a separate company code in SAP organization structure. 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.
Many inter-company transactions may occur between difference entities company codes and SAP implementation should support such transactions and valuations. This is a high-level document that shows some cross company and inter-company postings. The document is not describing detailed configuration behind these transactions or any valuations such as transfer pricing.
Cross-company code transaction viewed from transaction code FBU3 is an accounting entry involving more than one company code. In the example shown below, company code is posting a vendor invoice for an expense incurred in company code In the accounting entry, there is a debit to expense account ina credit to vendor in and offsetting items inter-company vendor and customer accounts respectively. In this process, a purchase order on a vendor is opened assigning cost center of another entity in the account assignment segment.
In example shown, purchase order is in company code and the assigned cost center belongs to company code other cost objects such as orders can also be used. The goods receipt posted against the purchase order creates expense in but liability to pay vendor in The offsetting line items from inter-company clearing create a payable in and a receivable in In this transaction, a company code makes payment for an invoice open item posted in a different company code. In example shown below, company code selects a vendor open item from company code to post payment.
A cross company code accounting document is posted to clear vendor open item inbank outgoing in and inter-company payable and receivable in and respectively. F transaction is used for simplicity. 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 process requires configuration of stock transport orders, inter-company pricing and billing.
Some important definitions in configuration are:. First is inter-company AR posted in sending entity. Second is inter-company AP invoice posted in receiving entity with I-doc output type. A production or process order in this process uses a work center assigned to a cost center of another company code of the same group. It indicates some resource sharing between affiliate companies.
On posting confirmation and consumption of inputs, the resulting accounting document shows inter-company receivable and payable in respective entities. An example is shown below. Cross-company sales order involves three parties — end customer, selling entity and order fulfilling entity.
A customer places order the fulfilment of which takes place from an affiliate company. In order based billing scenario, customer billing takes place on receipt of order.
Subsequently, supply chain can allocate the products ordered from own plant or from plant of an affiliate. In cases where affiliate fulfils the order, it triggers cross-company scenario. The pricing on sales order now shows another pricing condition type for inter-company pricing.Two organization structures: one for purchasing and another for sales. Purchasing: Company Code, Plant:Sto. Loc:Purchase Organization:.
Loc:Sales Area, 66, 66, Shipping Point Org Here Maintain the supplying plant so that it is linked to the vendor master. Note : A Plant can only be assigned to one vendor number. So we have to extend the same vendor number to different Pur. Org if required. Ch Norm Standard Item. Note : If You are not able to see tax condition types or not maintaining any tax indicators then it is not possible to Create a delivery against STO.
Same applies to Customer Master in Step2. Loc with below selected views. B — SD Delivery Standard. Otherwise Goods Receipt have to be carried out in another step. It depends on Partial deliveries allowed or not. Then the remaining quantity will not be shown as open in requirements. Note : If you are using one step procedure the enter the receiving storage location Here Observe the shipping tab with the above details as shown.
Here first of all SAP checks for any plant assigned in vendor Master. Create condition record for output tax condition type in Trasaction VK MWST output tax. Note : To adopt price from purchasing in to billing create a condition type with same name as PB Now the PO price is adopted in to billing.
Here make sure that delivery date is in between the dates entered. Then Execute.Demo 7.3 Stock Transport Order with Delivery
Note: If you are able to see an extra line item with status green proceed to next step or else click on log button as shown above.
Go to Transaction VL02N. In Goods Movement tab observe the movement type two step.
SAP S/4 Hana – Cross Company and Inter-Company Transactions
In item Conditions Tab Observe conditions as shown below. If You are not able to process PGI, then check WM is activated in storage location or if one step procedure check PO whether receiving storage location entered or not.
In Transaction VF01 Create billing document with reference to outbound delivery. Make Sure Account determination has been done and Save the billing document.
Observe the accounting document. Check the accounting document. Your email address will not be published. Nice post!As per the Model GST draft law, stock transfers across states or different registrations within the same state are GST relevant transactions. These processes must have a GST Invoice. This document provides information about creation of Info record, capturing GSTIN in vendor master and customer master, creation of new billing document type, setting up pricing procedure for STO, copy control, classification of conditions types, maintenance of business place wise GL determination.
You may create document with any other name. Maintain the entries of same dummy GL in OB40 for all the tax codes which has been used above. For the tax codes that are created for GST, maintain condition record for atleast one condition from tax procedure with 0 rate and key combination "Tax Classification" A table.
This is required to make the tax code active for the tax procedure. We have millions of materials SKUs and hundreds of stores Plants. This relationship info record is mantained at purchase org level in Retail solution. This configuration is stopping us to use the process for multi-plant sender having common vendor receiver. Browse pages. A t tachments 10 Page History. Jira links.
For information about stock transport orders with delivery, see Note You must create a vendor master record for the purchasing organization of the receiving plant. You must assign the supplying plant to the vendor master record. You must assign a customer master record to the receiving plant. You require a customer master record for the receiving plant.
This customer master record must be created for the organizational units of the supplying plant. Execute transaction code VOFA. Pricing Procedure for STO Billing It is recommended that you configure separate pricing procedure for the new billing type created in step 4. The following screenshot is for illustration only. You can configure the pricing procedure as per your business needs. The condition type for base price PR00 in above screenshot is to be configured accordingly.
This may serve as a base for GST tax calculations. Ensure that you are assigning an appropriate Accounting key ZST in the above screenshot against the base condition type. Save the settings. Maintain the single dummy GL in OB40 for the above used transaction key.
Create Outbound delivery document and issue the goods. Create GST Outbound invoice. Post Goods Receipt. Former Member. Hi Minu Thanks for sharing an excellent document. Permalink Apr 24, Hi, The creation of an info record at plant level is not a good solution for a Retail Company. Exist another option to inform this tax code?Master Data. Creating Supplying.
Plant as Vendor. Creating Receiving Plant as Customer. Configuration Guide. Define Document Type. Set up Stock Transport Order. Transactional Data. Companies with plants in multiple locations typically have the requirement to transfer stock between plants.
This requires several configuration steps and prerequisites to be in place for this solution to work and entities can benefit from the ability to monitor stock in transit, traceability through document flow and ability to account for delivery costs on the stock transport order.
In this document we will discuss the prerequisites and configuration that needs to be in place to achieve the Intercompany STO process in SAP. In order to carry out the STO process the two plants that the stock transfer is taking place, i.
Creating Supplying Plant as Vendor. Transaction: XK Here you will be creating a regular Intercompany Vendor and including the following setting. On the Purchasing Data screen on the vendor master, add the relevant plant as shown below. Transaction: XD Here you will be creating the receiving plant as the customer for shipping data determination.
Ensure the following setting is made on the Shipping tab. The following configuration needs to be in place for the Intercompany process. IMG Path :. You could also define a separate Z document type to differentiate these purchase orders. All setting relevant for Intercompany STO setup will be under this node. The plants need to be defined and shipping data added. Here you can define a checking rule which will be used for the ATP check.
To better understand the process we will now run through a step by step cycle to see what transactional data is needed to complete the Intercompany STO process.