1
Contents
Introduction ... 2
Master Data ... 2
1. Creating Supplying Plant as Vendor ... 2
2. Creating Receiving Plant as Customer ... 4
Configuration Guide ... 5
1. Define Document Type ... 5
2. Set up Stock Transport Order ... 6
2.1 Define Shipping Data for Plants ... 6
2.2 Create Checking Rule ... 8
2.3 Define Checking Rule ... 9
2.4 Assign Delivery Type and Checking Rule ... 11
2.5 Assign Document Type, One Step Procedure, Underdelivery Tolerance... 12
2.6 Define Allocation Type for STO... 13
Transactional Data... 14
3.1 Create Intercompany Purchase Order ... 14
3.2 Create Outbound Delivery ... 15
3.3 PGI Outbound Delivery ... 17
2
Introduction
Companies with plants in multiple locations typically have the requirement to transfer stock between plants. The STO (stock transport order) process is used to handle this transfer systematically in SAP. However if these plants belong to different Company Codes then we need to use the Intercompany STO process. 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.
Master Data
In order to carry out the STO process the two plants that the stock transfer is taking place, i.e. the plant that that is supplying the stock and the plant that is receiving the stock need to be set up as a Vendor and a Customer respectively.
1. Creating Supplying Plant as Vendor
Transaction: XK01
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.
4
2. Creating Receiving Plant as Customer
Transaction: XD01
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.
5
Configuration Guide
The following configuration needs to be in place for the Intercompany process.
1. Define Document Type
IMG Path:
Purchase Order type used for STO for plants within the same company codes is UB and for the Intercompany process you could use the standard NB type. You could also define a separate Z document type to differentiate these purchase orders.
6
2. Set up Stock Transport Order
IMG Path:
All setting relevant for Intercompany STO setup will be under this node.
2.1 Define Shipping Data for Plants
The plants need to be defined and shipping data added. i.e. the Customer no that was created as a prerequisite needs to be added here.
7 IMG Path:
8
2.2 Create Checking Rule
9
Here you can define a checking rule which will be used for the ATP check. Typically the standard checking rules are used and for Intercompany STO since there is an outbound delivery involved the checking rule “B” is used.
2.3 Define Checking Rule
10
Here you can assign the Checking rule to the Availability check (on the material master) and maintain relevant settings (types of stock/inward movements ATP would consider to fulfill the requirement) for the combination.
11
2.4 Assign Delivery Type and Checking Rule
IMG Path:
Here you assign the PO Document type and Delivery type to the Checking Rule to be used for each Supplying plant.
12
2.5 Assign Document Type, One Step Procedure, Underdelivery Tolerance
IMG Path:
The assignment here will restrict the use of other document types with the given Supplying plant/Plant combinations when creating purchase orders.
13
2.6 Define Allocation Type for STO
IMG Path:
Here you can assign the ARUN type to be used for the Document type/Supplying plant combination which will be used for assigning stock for the delivery.
14
Transactional Data
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.
3.1 Create Intercompany Purchase Order
You would need to create an Intercompany PO with the relevant document type to the intercompany vendor.
Transaction: ME21N
Note – The Shipping tab needs to be active for Intercompany POs with the relevant fields populated. If you don’t see the shipping tab there could be an issue with the customer being not assigned to the Vendor or Shipping data not maintained and you would not be able to drop the outbound delivery.
15
3.2 Create Outbound Delivery
You would need to create an outbound delivery referencing the purchase order to indicate the stock movement out of the supplying plant. (defined as the Intercompany vendor here)
Transaction: VL10B
Clear out the defaulted selection highlighted above and execute with the purchase order in the
selection.
Select the line and hit the Background button to create the delivery.
16
If you select the line and hit Show/Hide delivery button it should display the delivery number.
Note – You need to have sufficient unrestricted stock in the supplying plant to create the outbound delivery. You can check this in Transaction: MMBE display the stock overview or check the ATP horizon in the purchase order as below.
17
Note – This the traffic light is red you would need to check the stock availability or master data settings.
3.3 PGI Outbound Delivery
Next step would be to carry out the Post goods issue for the outbound delivery to indicate the stock leaving the supplying plant.
18
3.4 Goods receive the purchase order
Once the delivery is received at the receiving plant you could perform a goods receipt to compete the logistics process.
Transaction: MIGO
This completes the logistic part of the intercompany STO process and the intercompany sales and payment invoices can be created to complete the financial postings.
19 Author: Malith Tharaka Perera
E-Mail: [email protected] / [email protected]
Website: www.learnsaptips.com View my profile in LinkedIn
Disclaimer
This article is done based on my research and readings, unless otherwise stated. The views expressed are my own and not of anyone else.
Author accepts no liability for the content of the articles in this website or for the consequences of any actions taken on the basis of the information provided. Using this information is at the users own discretion and responsibility.
