SAP Knowledge Base Article - Public

3581986 - Ship-to Party cannot be updated as the Subcontractor when creating outbound delivery by using APP "Post Transfer Posting" with movement 541

Symptom

After creating outbound delivery by using APP "Post Transfer Posting" with movement 541, the field "Ship-to Party" cannot be updated as the subcontractor in this outbound delivery.

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

  1. Send stock to a subcontractor by using APP "Post Transfer Posting" with movement 541
  2. Click on button "Post" and an outbound delivery is created
  3. The Subcontractor cannot be updated in Ship-to Party

Cause

Outbound delivery with movement type 541 cannot cause the goods movement and materials in this outbound delivery are still in the plant. So the "Ship-to Party" in this outbound delivery cannot be updated as the subcontractor.

Resolution

Movement Type 541 is a SAP standard behavior called "Transfer of unrestricted-use stock to subcontracting stock". With this movement type, materials can only establish contact with the subcontractor without goods movement.

For more information regarding Subcontracting process, refer to the scope item BMY.

See Also

BMY

Keywords

Movement Type, 541, Post Transfer Posting, Ship-to Party, Subcontractor, outbound delivery, MIGO, goods movement, Transfer of unrestricted-use stock to subcontracting stock, scope item, BMY , KBA , LE-SHP-DL-2CL , Delivery Processing (Public Cloud) , MM-IM-GF-2CL , Basic Functions (Public Cloud) , MM-PUR-GF-SC-2CL , Subcontracting (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions