TU creation in EWM using ECC Shipment

Question

Hi All
Can someone help me with correct steps to create shipment in ECC which can create TU in EWM using standard IDoc interface?
I followed steps as per help.sap, integration between ECC & EWM is fine. I could see the shipment IDoc in EWM but it is getting failed. After debugging I have realized that I should not pack HUs into Container while creating shipment in ECC.
But is that correct process?
Thanks
Sasidhar Gupta

Answer 1

Hi Thiru
If have already followed SAP Help, please post the error what you are getting.
Create/update Shipment in ECC when TU was created/updated in EWM
Create TU via qRFC in EWM
Number range '' '/SCWM/SR_A' could not be read
Check these discussions also. Also you can check the below SAP documentation.
Define Default Values for IDoc Outbound
Use
You can use this Customizing activity to define default values for IDoc outbound that are required for the integration with the Transportation (LE-TRA) component of SAP Enterprise Resource Planning (SAP ERP).
These master data values in SAP ERP are needed in the IDocs sent from EWM to SAP ERP. Without these values, SAP ERP does not accept the IDocs.
Note:
These default values are only used during creation or deletion of shipments in ERP. They are not used when existing shipments are changed or updated.
Requirements
You have made the following settings:
You have defined logical systems in Customizing for SAP NetWeaver under Application Server -> IDoc Interface / Application Link Enabling (ALE) -> Basic Settings -> Logical Systems -> Define Logical System.If you use EWM as an add-on application for ERP, you have set up two logical systems: SYSTEM_1 and SYSTEM_2.
If you use EWM as a component of SAP Supply Chain Management (SAP SCM), you have set up one logical system in ERP for EWM and one logical system in EWM for ERP.
You have defined RFC destinations on the SAP Easy Access screen under Tools -> Administration -> Administration -> Network -> RFC Destinations.If you use EWM as an add-on application for ERP, you have set up an RFC destination as an internal connection called NONE.
If you use EWM as a component of SAP SCM, you have set up an RFC destination in ERP for EWM and one in EWM for ERP.
You have maintained distribution models in Customizing for SAP NetWeaver under Maintain Distribution Model.
If you use EWM as an add-on application for ERP, you have set up an ALE distribution model to trigger the sending of the IDoc from EWM to ERP. The model view needs to be created for distribution of message type SHPMNT and SHIPPL from the logical system SYSTEM_1 to the logical system SYSTEM_2.
If you use EWM as a component of SAP SCM, you have set up an ALE distribution model in EWM to trigger the sending of the IDoc from EWM to ERP. The model view needs to be created for distribution of message type SHPMNT and SHIPPL from the logical system for EWM to the logical system for ERP.
You have maintained ALE port definitions on the SAP Easy Access screen under Tools -> ALE -> ALE Administration -> Runtime Settings -> Port Maintenance.
If you use EWM as an add-on application for ERP, you have set up one port. This port is called V-NONE and it carries the RFC destination NONE.
If you use EWM as a component of SAP SCM, you have set up a port in ERP for EWM that carries the RFC destination for EWM, and one in EWM for ERP that carries the RFC destination for ERP.
You have maintained ALE partner profiles on the SAP Easy Access screen under Tools -> ALE -> ALE Administration -> Runtime Settings -> Partner Profiles.If you use EWM as an add-on application for ERP, you have set up two partner profiles of partner type LS (logical system).
  Sending IDoc SHPMNT from ERP to EWM (triggered though message control) 
For partner logical system SYSTEM_2, you have entered the following outbound parameters:
Partner Role: LS
Message Type: SHPMNT
Message Variant: for example, ERP
On the Outbound Options tab page, you have entered the following data:
Receiver Port: for example, V_NONE
Basic Type: SHPMNT05
You have selected the Transfer IDoc Immediately radio button.
On the Message Control tab page, you have entered the following data:
Application: V7
Message Type: for example, SEWM
Process Code: SD11
Receiving IDoc SHPMNT in EWM from ERP
For the partner logical system SYSTEM_1, you have entered the following inbound parameters:
Partner Role: initial
Message Type: SHPMNT
Message Variant: for example, ERP
On the Inbound Options tab page, you have entered the following data:
Process Code: /SCWM/SHPM
Sending IDoc SHPMNT from EWM to ERP
For partner logical system SYSTEM_2, you have entered the following outbound parameters:
Partner Role: initial
Message Type: SHPMNT
Message Variant: initial
On the Outbound Options tab page, you have entered the following data:
Receiver Port: for example, V_NONE
Basic Type: SHPMNT05
You have selected the Transfer IDoc Immediately radio button.
Sending IDoc TPSSHT from EWM to ERP
For partner logical system SYSTEM_2, you have entered the following outbound parameters:
Partner Role: initial
Message Type: SHIPPL
Message Variant: initial
On the Outbound Options tab page, you have entered the following data:
Receiver Port: for example, V_NONE
Basic Type: TPSSHT01
You have selected the Transfer IDoc Immediately checkbox.
Receiving IDoc SHPMNT in ERP from EWM
For the partner logical system SYSTEM_1, you have entered the following inbound parameters:
Partner Role: initial
Message Type: SHPMNT
Message Variant: initial
On the Inbound Options tab page, you have entered the following data:
Process Code: SHPM
Receiving IDoc TPSSHT in ERP from EWM
For the partner logical system SYSTEM_1, you have entered the following inbound parameters:
Partner Role: initial
Message Type: SHIPPL
Message Variant: initial
On the Inbound Options tab page, you have entered the following data:
Process Code: SHIP
If you use EWM as a component of SAP SCM, you have set up two partner profiles of partner type LS (logical system) in ERP and EWM.
Sending IDoc SHPMNT from ERP to EWM (trigger via message control)
For partner logical system for EWM, you have entered the following outbound parameters:
Partner Role: LS
Message Type: SHPMNT
Message Variant: initial
On the Outbound Options tab page, you have entered the following data:
Receiver Port: Port created in ERP for EWM
Basic Type: SHPMNT05
You have selected the Transfer IDoc Immediately radio button.
On the Message Control tab page, you have entered the following data:
Application: V7
Message Type: for example, SEWM
Process Code: SD11
Receiving IDoc SHPMNT in EWM from ERP
For partner logical system for ERP, you have entered the following inbound parameters:
Partner Role: initial
Message Type: SHPMNT
Message Variant: initial
On the Inbound Options tab page, you have entered the following data:
Process Code: /SCWM/SHPM
Sending IDoc SHPMNT from EWM to ERP (triggered through ALE distribution model)
For partner logical system for ERP, you have entered the following outbound parameters:
Partner Role: initial
Message Type: SHPMNT
Message Variant: initial
On the Outbound Options tab page, you have entered the following data:
Receiver Port: Port created in EWM for ERP
Basic Type: SHPMNT05
You have selected the Transfer IDoc Immediately radio button.
Sending IDoc TPSSHT from EWM to ERP (triggered via ALE distribution model)
For partner logical system for ERP you need to have an entry in the outbound parameters for
Partner Role: initial
Message Type: SHIPPL
Message Variant: initial
On the Outbound Options tab page, you have entered the following data:
Receiver Port: Port created in EWM for ERP
Basic Type: TPSSHT01
You have selected the Transfer IDoc Immediately radio button.
Receiving IDoc SHPMNT in ERP from EWM
For the partner logical system for EWM, you have entered the following inbound parameters:
Partner Role: initial
Message Type: SHPMNT
Message Variant: initial
On the Inbound Options tab page, you have entered the following data:
Process Code: SHPM
Receiving IDoc TPSSHT in ERP from EWM
For the partner logical system for EWM, you have entered the following inbound parameters:
Partner Role: initial
Message Type: SHIPPL
Message Variant: initial
On the Inbound Options tab page, you have entered the following data:
Process Code: SHIP
Activities
You can define default values for IDoc outbound in the following way:
1. Enter the following data:
Business system
Message type
Shipment type
  Note:  
You need to define a separate shipment type in ERP. Use this shipment type for message type SHPMNT. The IDoc is only filled with this shipment type if transportation planning type is "B - Obligatory Internal Planning in EWM". This shipment type for transportation planning type B must be different from the shipment types that you use for transportation planning type "A - Obligatory External Planning in ERP". Otherwise, ERP sends an IDoc back to EWM, which is not intended within warehouse outbound processing with transportation planning in EWM.
Transportation planning point
Note:
You need to define a separate transportation planning point in ERP, for example "0002 - Dummy for Deletion". Use this transportation planning point for message type SHIPPL. The IDoc is only processed in ERP if you define this transportation planning point in ERP as a transportation planning point for external systems. For more information, see Customizing for ERP under Logistics Execution -> Transportation -> Interfaces -> External Transportation Planning Systems -> Maintain Transportation Planning Point for External Systems.
In this Customizing activity, you need to enter the logical system of EWM as the partner number of external transportation planning system, the partner type of the logical system (for example, LS), an external number range (for example, 01), and the controlling parameter for changes (for example, "00 - no restrictions for changes").
2. Save your entries.
Thanks
Sasidhar Gupta