Determination of movement type in SAP STO outbound delivery

简介: Determination of movement type in SAP STO outbound delivery

Determination of movement type in SAP STO outbound delivery


As we known that in the inter-company STO scenario, we often need to create outbound delivery so that the issue company can do picking and PGI for the outbound delivery.


In different STO scenario, the movement types of those outbound delivery are different. For example, the vendor consignment stock inter-company STO, the normal owned stock inter-company STO, one-step transfer inter-company STO, two step transfer inter-company STO, the movement types are different.


Then how SAP system can know which movement type should be used for those different scenarios? This blog will explain this.


1, First we can specify the delivery type for STO document.

image.png





For example, if the inter-company STO from NMI1 to NM03, for normal owned stock, the delivery type is NLCC, for vendor consignment stock, the delivery type is NK.

image.png



For the intra-company STO from NM1 to NM03, the delivery type will be NL.


2, Second, we can determine the item category used in outbound delivery, by the combination of delivery type/item category group/usage/Item category of higher-level item.




image.png




Item category group: it is maintained in article master data.


Item category usage: V, stands for purchase order.


ItemC: item category of higher-level item, normally it is empty.

image.png





3, Then we can determine the corresponding schedule line category through the combination of item category and MRP type.


Through the following configuration,

image.png





Delivery item category NKN can be used in the delivery note of the inter-company STO for vendor consignment stock. Related schedule line category is K0.


Delivery item category NLC can be used in the delivery note of the inter-company STO for normal owned stock. Related schedule line category is NC.


Note that the schedule line category cannot be seen in the outbound delivery document of the inter company STO scenario. It will only appear in the sales order document.


4, At last, we can get the corresponding movement type according to schedule lines category K0 or NC.


Through the following configuration,


image.png






It can be seen that for the inter company STO scenario of normal owned stock, under normal circumstances, the movement type of the delivery document when we post goods issue is 643. If it is a one-step stock transfer, the movement type is 645.

image.png



It can be seen that in the inter company STO scenario of vendor consignment stock, the movement type of the delivery document goods issue posting is 635 under normal circumstances. If it is a one-step stock transfer, its movement type is empty, that is, standard SAP does not support one-step stock transfer in this scenario.


Hope this blog can help you.


相关文章
|
12月前
SAP 电商云 Spartacus UI set delivery mode HTTP put 请求的触发时机
SAP 电商云 Spartacus UI set delivery mode HTTP put 请求的触发时机
|
12月前
SAP 电商云 Spartacus UI delivery mode 页面设计的结构分析
SAP 电商云 Spartacus UI delivery mode 页面设计的结构分析
|
11月前
|
负载均衡 前端开发 网络协议
使用 Azure SNAT 为 SAP Commerce Cloud 的 outbound connection 进行端口映射
使用 Azure SNAT 为 SAP Commerce Cloud 的 outbound connection 进行端口映射
|
12月前
|
存储 API
SAP 电商云 Spartacus UI 的交货模式 Delivery Mode 设计
SAP 电商云 Spartacus UI 的交货模式 Delivery Mode 设计
|
12月前
SAP 电商云 Spartacus UI 设置 delivery mode 在 3G 慢速网络下的排队效果
SAP 电商云 Spartacus UI 设置 delivery mode 在 3G 慢速网络下的排队效果
|
12月前
|
存储
SAP 电商云 Spartacus UI 设置 Delivery Mode 的时序分析和一个竞争条件问题分享
SAP 电商云 Spartacus UI 设置 Delivery Mode 的时序分析和一个竞争条件问题分享
|
12月前
|
前端开发
SAP 电商云 Spartacus UI Delivery Mode ID 的 validator
SAP 电商云 Spartacus UI Delivery Mode ID 的 validator
|
12月前
|
存储 机器学习/深度学习 架构师
SAP 软件的精髓之一:各种各样的决定机制 - Determination Logic
SAP 软件的精髓之一:各种各样的决定机制 - Determination Logic
|
12月前
SAP 电商云 Spartacus UI 修改 Delivery Mode 触发的三个 HTTP 请求 2
SAP 电商云 Spartacus UI 修改 Delivery Mode 触发的三个 HTTP 请求
|
12月前
SAP 电商云 Spartacus UI 修改 Delivery Mode 触发的三个 HTTP 请求 1
SAP 电商云 Spartacus UI 修改 Delivery Mode 触发的三个 HTTP 请求