I checked the config I my system and for Honeywell devices I have 16x20ITS. I'm not using the reference, I'm using this in a live system with people in the warehouse 
. I only looked for the reference, because I didn't remember how to generate the templates.
↧
Re: RF Screens are not appearing properly on RF handheld scanner device
↧
Re: RF Screens are not appearing properly on RF handheld scanner device
Hi Sousa
Are you using any specific ITS service parameters in GUI Link in SICF transaction to fit the required content to RF screen? I am using Honeywell 99GX and Intermec devices. Above picture is from honeywell device. Let me try with 16X20 then.
Thanks
Sasidhar Gupta
↧
↧
Re: TU creation in EWM using ECC Shipment
Yes I have created the packaging material. The shipment creation is not even triggering the idol creation, is there any config that I am missing. It is a high priority issues, Any help is appreciated..
Cheers
thiru
↧
Re: TU creation in EWM using ECC Shipment
Have you ativated SHPMT message type?
Please check below link and try. We have successfully did this in our project.
↧
Re: TU creation in EWM using ECC Shipment
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
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
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
↧
↧
Re: TU creation in EWM using ECC Shipment
Thanks Sasidhar for the note. I have already set up the system in the way described above. When i create a shipment in ECC, and attach delivery and do th packing, i expect to see a idoc( shipment create). But i don't see it . Any thoughts on why this is not happening, anything that i might be missing from config or master data side.
↧
Re: TU creation in EWM using ECC Shipment
Hi Thiru
For eg: you have packmaterial Packmat for packing products (creates HUs) and container for loading HUs, you create HUs in delivery if needed and just add container as packing material in & while creating shipment. Finally make sure that HUs are not linked to container (if you want only TU to be created). You must have already configured NACE for generating IDoc message. So when you save your shipment, in the output tab you should see output generated. Hope this helps you.
Regards
Sasidhar Gupta
↧
Re: Empty HU creation
Hello Phani,
We need to consider TU and collect the deliveries
Regards,
Priya
↧
Re: TU creation in EWM using ECC Shipment
Just check if any outbound Idoc is failed using WE05 for SHPMT message type. If all setting are correct for IDoc creation then system should trigger the IDoc from ECC system, and should create TU number in EWM. You can get shipment reference also in TU display transaction.
↧
↧
Re: RF Screens are not appearing properly on RF handheld scanner device
Hi Sasidhar,
Which OS is installed on the RF devices? I have observed in last implementation it did not work on normal IE browser is OS is windows mobile. Better to use devices with XP or advanced one.
Also, there are some powerful industrial browser avaialble in market (Sometimes come by default with devices) are useful.
Thanks,
Sandip
↧
EWM-2 Step Picking issue
Hi,
I have been doing setup of 2 step picking, currently allocation WT shows destination bin as source bin which is not correct, i have following questions:
1) Is the POSC mandatory for 2 step picking, if do so @ what stage(withdrawal/allocation) system determines the storage process? what are the steps are necessary i.e. OB01/OB02/OB03/0B04?
2) Is the work center needed during allocation step?
3) How the system determines destination bin during allocation?
4) Can we execute 2 step process without HU/Work Center/POSC?
5) Pls share if there is any doc. which explain complete 2 step picking (apart from SAP Help).
Please let me know.
Thanks,
Ganesan
↧
Re: EWM 9.0 How to deleted HU after cancel WO
Dear Sandip
Please provide more infomation for check.
Thank
Suchart P.
↧
EWM PPF Assign Warehouse Request to Wave
We found that PRDO is assigned to wave number 100000585 from
PPF Action. But when check from mon ,there is no wave 100000585.
We try to create new wave and include this odo into the wave. It is not possible.
↧
↧
Re: Create multiple WT performance issue in EWM
Hi guys,
There are two notes to solve this issue.
1510229 and 1621270.
Julia
↧
Re: Empty HU creation
We need to consider TU and collect the deliveries
Regards,
Priya
↧
Re: EWM PPF Assign Warehouse Request to Wave
Hi,
Did you check your Q in SMQ2? It could be that it is still processing and hanged up for some reason. That would be the first place to look.
Thanks,
Faical
↧
Re: EWM-2 Step Picking issue
Hi,
Can you please check and see if your ODO has a staging bin assigned in the item? If you are missing the staging bin EWM will put the destination bin as source bin.
Thanks,
Faical
↧
↧
Qty miss in outbound delivery
Dear Experts,
in some when we create outbound delivery with reference purchase order by T-Code VL10D, few article qty miss in outbound delivery why this happening has coming pls give the solution ....
and that will allow manually qty fill after extend the the date in outbound delivery
Best Regards
jagdish
↧
Re: Qty miss in outbound delivery
Dear Jagdish ,
I believe system is not able to confirm quantity at order on said date , hence you will have to extend date for stock to be available ( availability check confirms quantity to sales order )
Kindly check stock requirement list MD04 and analyze whether materials is available for despatch on said date.
Try same and let me know results.
Thanks
Jinoy
↧
Re: EWM PPF Assign Warehouse Request to Wave
Dear Faical,
Check in T-Code /SCWM/MON Wave
Thank,
Suchart
↧