Delivery Automatic Creation for Inter-company STO

简介: Delivery Automatic Creation for Inter-company STO

Delivery Automatic Creation for Inter-company STO


In the SAP standard system, subsequent outbound delivery documents of inter-company STO can be automatically created through background configuration, that is, ME21N will automatically trigger delivery documents when creating inter-company STO documents.


This blog briefly introduces how to realize this function.


Part I:Business scenario and master data


Goods issue company code:NMI1


Issue plant:NMI1, vendor code: 100061


Sales area:NMI1/01/01


Receiving company code:0001


Receiving plant:NM01, customer code: 40


Purchase organization:0002


Article code:555


STO document type:ZNB


SAP system:S4HANA 1909


Part II:core configuration point


STO related basic configuration (IMG->MM->Purchasing->PO->Setup STO).

1.1, Assign Document Type, One-Step Procedure, Underdelivery Tolerance



image.png



1.2, Configure Delivery Type & Availability Check Procedure by Plant


image.png




1.3, Activate Automatic Delivery Creation and CRM Billing



image.png



1.4, Activate Automatic Delivery Creation for PO Type and Shipping Point


image.png




2, The configuration of shipping point assignment and goods receiving point determination.

image.png



Make sure we have assign shipping point to the issue plant NMI1.


Make sure we have assign goods receiving point for the receiving plant NM01.


Part III: Create inter-company STO document to monitor the effect.


Execute the transaction code ME21N,


image.png


We fill the data,and then save it.


image.png


We created a STO document 4700000003.


Execute the transaction code ME23Nto display the data of STO 4700000003.


image.png


You can that the tab 'Purchase Order History' appeared in the item details, and the outbound delivery document 80000829 was created automatically.


We got the expected result.


相关文章
Delivery Automatic Creation for UB type STO
Delivery Automatic Creation for UB type STO
Delivery Automatic Creation for UB type STO
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
005. how is RFC to backend determined - maintenance view IWFNDV_MGDEAM
005. how is RFC to backend determined - maintenance view /IWFND/V_MGDEAM Created by Wang, Jerry, last modified on Dec 26, 2014
005. how is RFC to backend determined - maintenance view IWFNDV_MGDEAM
Field creation not permitted in partner development mode
Field creation not permitted in partner development mode
Field creation not permitted in partner development mode
how is RFC to backend determined - maintenance view IWFNDV_MGDEAM
005. how is RFC to backend determined - maintenance view /IWFND/V_MGDEAM Created by Wang, Jerry, last modified on Dec 26, 2014
110 0
how is RFC to backend determined - maintenance view IWFNDV_MGDEAM
automatic asynchronous creation if no note exists
Created by Wang, Jerry, last modified on May 12, 2015
119 0
automatic asynchronous creation if no note exists
strange behavior:why u31000 is accessed for Extension project
Created by Wang, Jerry, last modified on May 20, 2015
106 0
strange behavior:why u31000 is accessed for Extension project
SAP MM Inter-company STO No Inbound DN triggered after Outbound DN PGI done
SAP MM Inter-company STO No Inbound DN triggered after Outbound DN PGI done