Dear Experts,
Is there a way we can use Opportunistic Cross Dock in such a way that we can enable EWM to only search for a specific Outbound Delivery when the Putaway Cross-Dock WT is getting created?
Regards,
Shashidhar
↧
OCD in EWM
↧
Re: Queue: MCEX11 destination is missing
I suppose you made this screenshot, when you tried to re-create the model, the system gives you a warning that "the following entries exist and should be cleaned up"? Because then you do not have the ok in the last column (what Suraj refers to).
According the screenshot your logical system name is "ECR"?
Now I wonder what this means for the logical system name / RFC connection name / business system in the target system? Your business system is assigned to a RFC connection. But this one for sure is not named "ECR". And if the name of the logical system and the RFC connection are not the same? Probably this all just goes into nirwana...
Brgds
Juergen
↧
↧
Re: SAP PCo 2.3 and SAP EWM Integration
Below should help you a bit.
Customizing Settings:
1. Define PLC interface types. PLC interface types facilitate the settings for controls of a similar nature (for example, several stacker cranes with an identical interface).
For more information, see the Implementation Guide (IMG) for EWM under Master Data®Material Flow System (MFS)®Master Data®Define PLC Interface Type.
2. Define a PLC in EWM for each real PLC with which EWM is to communicate.
For more information, see the IMG for EWM under Material Flow System (MFS)®Master Data ®Define Programmable Logic Controller (PLC).
3. Define one or more communication channels for each PLC.
For more information, see the IMG for EWM under Material Flow System (MFS)®Master Data ®Communication Channel ®Define Communication Channel.
4. Define communication point types. Consider whether you need a special processing for different communication points when telegrams of a certain type arrive.
For more information, see the IMG for EWM under Material Flow System (MFS)®Master Data®Define Communication Point Types.
5. Define communication points. Each point in the system that is not a final storage bin and which EWM is to take into account as an interim step must be a communication point.
For more information, see the IMG for EWM under Material Flow System (MFS)®Master Data®Define Communication Point.
6. Define communication point dependencies if you want to limit the capacity of communication points in EWM or record the status at communication points in EWM. In doing so, you define which other communication points are checked by EWM with regard to HUs waiting there if a communication point is relieved or its status changes to Ready.
For more information, see the IMG for EWM under Material Flow System (MFS)®Storage Control®Define Communication Point Dependencies.
7. Define conveyor segments if you want to check their status or capacity in EWM.
For more information, see the IMG for EWM under Material Flow System (MFS)®Master Data®Define Conveyor Segment.
8. Define conveyor segment group types if you use conveyor segments and want to treat them jointly with regard to their status, for example.
For more information, see the IMG for EWM under Material Flow System (MFS)®Master Data®Define Conveyor Segment Group Type.
9. Define conveyor segment groups if you want to treat conveyor segments jointly.
For more information, see the IMG for EWM under Material Flow System (MFS)®Master Data®Define Conveyor Segment Groups.
10. Then assign the conveyor segments to the conveyor segment groups.
For more information, see the IMG for EWM under Material Flow System (MFS)®Master Data®Assign Conveyor Segments for Conveyor Segment Groups.
11. Flag the storage types that represent the warehouse regulated by the controls as MFS-relevant. Two storage type roles are available:
12. Prestorage area: H Material Flow Control for Automatic Storage Retrieval
13. High-rack storage area: J Automatic Warehouse (Driven by MFS).
For more information, see the IMG for EWM under Master Data®Define Storage Type.
14. Define storage groups for layout-oriented storage control. Storage control allows you to form groups of storage bins – known as storage groups – for route determination.
For more information, see the IMG for EWM under Material Flow System (MFS)®Storage Control®Define Storage Groups for Layout-Oriented Storage Control.
15. Define interim destinations for the transportation of HUs within your warehouse. You do this according to the principle: from A to Z via B, from B to Z via C. This point represents the core of your Customizing activities. You can specify source and destination either roughly (storage type only) or finely (with storage group). It is also possible to entirely do without one of the two. For example, "everything from aisle 1 - irrespective of final destination - via the intermediate location CP13" (stock removal station of aisle 1). You can also specify different paths for full, partly full, or empty HUs.
For more information, see the IMG for EWM under Material Flow System (MFS)®Storage Control®Define Layout-Oriented Storage Control.
16. Define suitable activity areas. You use activity areas to control the assignment of warehouse tasks to queues. The controls defined in each case process the queues.
For more information, see the IMG for EWM under Master Data®Activity Areas ®Activities.
17. Define an MFS queue for each PLC.
For more information, see the IMG for EWM under Material Flow System (MFS)®Master Data®Define MFS Queue.
18. Define a resource category for each resource type used. For more information, see the IMG for EWM underMaterial Flow System (MFS)®Master Data®Define MFS Resource Category.
19. Define abbreviations for MFS actions. Define function modules that the system is to call in the case of these actions.
For more information, see the IMG for EWM under Material Flow System (MFS)®Telegram Processing®Define MFS Actions.
20. Clarify the telegram structures (record structure, telegram types) with the person responsible for the PLC and create the corresponding record structures in the ABAP dictionary. You can use the Object Navigator of the ABAP Workbench for this purpose, for example.
21. Define which telegram IDs the PLC expects or uses for the intended message types and which record structures it uses in each case.
For more information, see the IMG for EWM under Interfaces®Material Flow System (MFS)® Telegram Processing®Define Telegram Structure.
22. Define which action modules are to be called for which PLC telegrams.
For more information, see the IMG for EWM under Material Flow System (MFS)®Telegram Structure ®Find MFS Actions.
23. Define the required exceptions.
For more information, see the IMG for EWM under Material Flow System (MFS)®Exception Handling ®EWM Exceptions.
24. Assign PLC errors to the relevant telegram errors.
For more information, see the IMG for EWM under Material Flow System (MFS)®Exception Handling®Assign Telegram Errors to PLC Errors.
System Settings
1. Create storage bins for the communication points and assign these to the communication points. In doing so, ensure that the storage bins each have the correct storage group. The system determines the storage group via the interim storage bins. On the SAP Easy Access screen, choose Extended Warehouse Management®Master Data ®Product ®Material Flow System (MFS)®Maintain Communication Points.
2. Define sorting rules for the new storage bins. The system assigns warehouse tasks to warehouse orders. In MFS, this is always a 1:1 assignment. Nevertheless, an activity-related sort sequence is necessary for data-technical reasons. On the SAP Easy Access screen, choose Extended Warehouse Management®Master Data ®Storage Bin ®Sort Storage Bins.
3. Create a resource for each stacker crane and assign a queue to the resource. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management ®Master Data ®Material Flow System (MFS) ®Maintain MFS Resource.
4. Create a new RFC destination (TCP/IP connection). Define a program ID. You must set this in the external communication layer. The communication layer registers itself in the SAP system under this name. You can then call the communication layer from EWM.
On the SAP Easy Access screen, choose Tools®ALE®ALE Administration® Runtime Settings®Maintain RFC Destination.
5. Specify for each PLC whether you want to use the SAP communication layer SAP XMII MDS for EWM or a different communication layer. Specify the name of the RFC destination and, where appropriate, the functions to be called in the external communication layer. To do so, on the SAP Easy Access screen, chooseExtended Warehouse Management ®Master Data ®Material Flow System (MFS)®Maintain Programmable Logic Controller.
6. Set the IP address and port of the communication channels. The EWM system passes on these parameters to the external communication layer when the channel is opened. The communication layer is then in this respect maintenance-free. On the SAP Easy Access screen, choose Extended Warehouse Management ®Master Data ®Material Flow System (MFS)®Maintain Communication Channel.
7. Create a new TCP/IP connection. Enter a program ID. The external communication layer must use this to register itself in the SAP system. On the SAP Easy Access screen, choose Tools®ALE®ALE Administration® Runtime Settings® Maintain RFC Destination.
8. Start the communication channels. On the SAP Easy Access screen, choose Extended Warehouse Management ®Monitoring ®Warehouse Management Monitor® Material Flow System®Communication Channel.
Result
The material flow system is configured. SAP EWM can communicate warehouse tasks affecting the area of responsibility of the defined PLC to the latter and in this way control the relevant area in the warehouse without operator intervention.
↧
Re: SAP PCo 2.3 and SAP EWM Integration
Thanks a lot Sathish.
I will try the above steps and let you know if face any issue.
Thanks,
Ritim
↧
Re: OCD in EWM
Hello Shashidhar,
The standard Opportunistic Cross-docking logic during Putaway WT creation is embedded in the standard implementation of the Badi "/SCWM/EI_CD_OPP_INBOUND".
Your requirement is not achievable in standard via customizing/SPRO.
To enable the OCD just on specific delivery, material, etc... you need to create your own implementation of the BADI "/SCWM/EI_CD_OPP_INBOUND" where you would copy most of the standard implementation code but integrate your own logic (to retrieve the proper ODO item..).
This has already been achieved with success for some of my customers.
Regards and good luck
JM
↧
↧
Re: How to assign external warehouse number to supply chain unit in ewm ?
Do you still have the issue after changing this? can you try with fresh delivery?
Regards,
Sathish
↧
Re: How to assign external warehouse number to supply chain unit in ewm ?
Jep! i already try with those new configuration..... still the same error message...
Regards
Denis
↧
Re: Unpack the HU
Thanks a lot satish,
Let me try and get back to you.
Many Thanks
Ganeshan
↧
Re: How to assign external warehouse number to supply chain unit in ewm ?
I think... you should read the solution manager documenation and implementation guides. Because all this is described there. It is very difficult to come up with all that by yourself and probably you end up with something wrong anyway.
Brgds
Juergen
↧
↧
Re: How to assign external warehouse number to supply chain unit in ewm ?
To be honest...I've already read few books about EWM inplementation (also SAP-Help) and due to this everything is fine...could you may be tell me where I can find this solution manager documentation? And what implementation guide you are talking about?
Thank you
BR
Denis
↧
Re: How to assign external warehouse number to supply chain unit in ewm ?
Denis,
Difficult to pinpoint the error.
1.Please use the report /n/SCWM/REECCHECK to confirm the integration is complete.
2. check the mapping of the ERP storage location to EWM
↧
Re: Transportation Unit
Saravana,
Can you explain the situation little more? What is the functionality you would like to achieve?
Where are you expecting the TU information to come from? ERP system? in That case you can use IDOC's to transmit TU to EWM using ECC shipping functionality
Warm Regards,
Norbert Mendonca
↧
Implementation of Hugo Boss
Hi experts,
Can anyone know who implemented SAP EWM for Hugo Boss.
↧
↧
Re: How to assign external warehouse number to supply chain unit in ewm ?
Hi Denis.
We will start from ERP.
1. check ERP wh to EWM wh assignment.
In EWM check SPRO >> interface and below 2 setting its should show same as ERP.
Then Check SCU it should be your plant. And assign WH as attribute.
Check LNUM_EWM - BP has assigned with SCU in identification tab and same BP in SCU.
and as per above setting below setting will populate besitzer automatically if all above setting is good.
You check step by step and recreate new del.
Regards
Suraj
↧
Re: Transportation Unit
Hi Saravana,
Its possible.
TU data from ERP comes via Idoc to EWM and its creates TU in EWM.
Now here when you wanna to create TU from excel file from any system. try to use this Function module and create.
Regards
Suraj
↧
Re: Transportation Unit
Hi Sravana K,
FM /SCWM/IDOC_INPUT_SHPMNT is used to create TUs and same can be used for your requirement as well.
Thanks and regards
Anoop
↧
Re: How to assign external warehouse number to supply chain unit in ewm ?
Hi Denis,
Make sure you have SCU assigned to your EWM warehouse with business attribute INV (Warehouse) also check other configurations table enteries you might have missed some enteries for warehouse linkage.
Regards
Anoop S P
↧
↧
Re: Queue: MCEX11 destination is missing
Hi Denis,
good that your issue is solved, just wanted to answer your question "from where the sender system comes from when distri model is created"? as by new you should already have idea because you have done the client assignment.
Anyway it finds the logical sender system from the client which you have logged in----there is one logical system assigned to that client in other table...
Regards
Anoop S
↧
Re: How to assign external warehouse number to supply chain unit in ewm ?
Hello Denis,
Can you assign RO - Receiving Office and SO - Shipping Office as well. these are important attributes as well for Outbound/Inbound deliveries.
Regards,
Sathish
↧
Re: Not able to process inbound delivery in ewm
Hi Suresh,
First of all you need to maintain a SCU with attaribute INV (Warehouse) in /SCWM/scumain
then you can maintain the SCU hierarchy with your Shipping Office and Receiving Office as required in /scwm/scuhiermain
then you need to assigned this SCU ot your warehouse in Master Data in SPRO --> Assign Warehouse Number
Regards
Anoop
↧