Delivery Type Determination for STO's

September 16, 2017 | Author: Anupa Wijesinghe | Category: Logistics, Technology, Computing, Business, Computing And Information Technology
Share Embed Donate


Short Description

As part of the Stock Transport Order logistic execution process, we need to create an outbound delivery with reference t...

Description

Contents Introduction .................................................................................................................................................. 2 Customizing................................................................................................................................................... 2 Copy control settings used for inbound delivery creation ........................................................................... 5

1

Introduction In our previous posts, we learnt about below 4 different Stock transport order types and respective configuration steps.    

Intra – Company STO – Click here Inter – Company STO – Click here Rush STO – Click here STO between Storage Locations – Click here

As part of the Stock Transport Order logistic execution process, we need to create an outbound delivery with reference to STO number using transaction VL10B. In order to create a delivery document with reference to any other SAP object, we need to have copy control settings between those 2 document types. For example, in order to create a delivery with reference to a sales order, we need to have sales order type to delivery type copy controls maintained. But in case of a STO, we do not have copy control customizing between purchase order type (STO Type) to outbound delivery type (Eg: NB to NLCC or UB to NL). Therefore, it is interesting to understand how SAP handles such scenario’s in customizing.

Customizing In standard SAP, when you create an outbound delivery for an Intra-company STO purchase order, the delivery type will be automatically determined as “NL”. In case of an inter-company STO purchase order, the delivery type will be determined as “NLCC”. Delivery type “NL” does not require billing, where as delivery type “NLCC” requires billing. Most of the cases billing is done based on the transfer price between those 2 companies. Therefore, let’s start our investigation from that point. When you open this IMG node for delivery type “NL”, you will see a field called “Default Order type”. This field value is set to “DL”. IMG Path:

2

Delivery type “NLCC” also holds the same “Default Order type” as “DL” 3

If you compare the sales order related delivery type “LF” with above, you will see there is no “Default Order Type” assigned to it.

4

Copy control settings used for inbound delivery creation During outbound delivery creation for the STO, system internally takes the copy control settings between document type “DL” to delivery type “NL” or “DL” to delivery type “NLCC”. This is determined by the sales document type assigned in the delivery type customizing (Under “Order reference” section). See below; IMG Path:

5

Header:

Item:

6

When you create a delivery with reference to a standard order, the delivery type is determined based on the “Default delivery type” field in the sales document type customizing. This setting is done in below sales document types IMG note.

Like we have assigned the default delivery type in the sales document type customizing, we have similar setting to assign the delivery type for the purchase order type as well. Under below IMG node, the SD delivery type (NL) is assigned to an intra-company purchase order type (UB) and supply plant combination.

7

IMG Path:

For inter-company STO process, the SD delivery type (NLCC) is assigned to inter-company purchase order type (NB) and supply plant combination.

8

Author: Anupa Wijesinghe E-Mail: [email protected] / [email protected] Website: www.learnsaptips.com View my profile in LinkedIn Follow me on Twitter

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.

9

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF