Cross docking using SLS ( Supplementery logistics services )

Hi All,
I am trying to perform cross docking by using SLS. The scenario is that Store place order to D.C where D.C is performing a collective P.O run ( Wf10). Generally before you generate D.C order the SLS indicator should be checked based on the setting and when a P.O against vendor is created the Article should be divided on P.O based on the reciepient. Well this is not working for me.
The setting i am maintaining are -
1. Create an Adiitional and assigned to article and also assigned the procedure 0005 SLS Pre-pack.
2. I am using Single article
3. Maintained Distribution profile as Cross dock on article master.
Guys i am really not able to understand what exactly i missed.
Please advice me.
Thank you so much for taking out ur time to read it.
Regards,
Pratap

Hi Pratap,
Have you maintained the config for merchandise distribution for Supplementary Logistics Services.
IMG --> Logistics General --> Merchandise Distribution --> Supplementary Logistics Services: Maintain Service Profile
Enter the procedure - 0005.
Select procedure 0005 --> Control Table for Purchasing
Maintain event (create) and Doc cat "F", Order type and Follow up action for procedure additionals "85".
Once you have done this config try creating the collective PO.
The document type you are using should be maintained in this config.
Hope this resolves your issue.
Regards
Yogesh Joshi

Similar Messages

Cross-Docking using ECC 6.0 SP12 - How to configure?

People,
we are using ECC 6.0 SP 12 and we would like to configure Cross-Docking.
I cannot find the option in SPRO:
Logistics Execution -> Warehouse Management -> Cross-Docking
I believe this configuration path is related to SP 14.
How can I configure it in SP 12?
Thanks a lot!

We are using the versions:
EA-APPL     600     0010     SAPKGPAD10
SAP_ABA     700     0012     SAPKA70012
SAP_BASIS 700     0012     SAPKB70012
I have to install a service pack in this components to get this funcionality?
Thanks a lot,
Cristiana

Goods marking on cross-docking orders

Dear colleagues,
Will you please help me with another conceptual issue in IS-Retail? I thought that the difference between the cross-docking and flow-through was that the goods are not repacked in the former case, i.e. the vendor marks the final destination of the goods (the store), so that the DC can merely move the parcel from the receiving ramp to the dispatch ramp and send them further.
However, I see that the system generates vendor orders for the total quantities per article (no split of the total quantity per store). I wonder then how the vendor will know how to pack the goods and mark them with the address of the end destination?!
Or otherwise, what is the idea of cross-docking?
TIA
Raf

H Rafael,
I understand your question. I was not clear earlier. If I work through your example, Let us say you have 3 stores - A, B and C
and you have ordered 12 units - 4 for each Store. The Vendor has only 9 units.
Now we have the following options -
A) You agree with this vendor on predetermined rules to distribute in case of under delivery. You could decide to distribute proportionally (standard adjustment profile) or a custom version (your own function module) which kicks in at Goods Receipt automatically.
B) You do not have a predetermined rule and hence the Vendor contacts you to ask for instructions, this would mean you would give a manual instruction on the rule to be used. In this case I would rather do a manual distribution than an automatic one at GR. However this option is not optimal for any business as the whole point of cross-docking and SLS automation is to avoid manual communications with the Vendor.
Ideally I would do the following. Sit with the Vendor who would pre-pack and agree the set of predetermined rules that will be applicable. For example - You could have one rule for all Mens Clothing, and another for Womens Shoes. etc.
You can then use your Custom Function module to pick the right rule based on the article and apply the rule at the GR. Since the rules are agreed in advance with the Vendor, the Vendor would have packed the right quantities.
Hope that helps.
Cheers,
Naveen

WM: opportunistic cross-docking

Hi all,
According to my understanding of the help.sap.com online documentation, we are NOT supposed to use the Cross-docking Monitor while trying to achieve an opportunistic cross-docking stock transfer between an inbound delivery and an outbound delivery. Once we appropriately complete the Customizing, the system is supposed to generates BY ITSELF a cross-docking decision during the process of TO creation (after the arrival of the incoming stock or release of the outgoing document).
Am I right ? Up to now, I can't achieve it...
I've checked my Customizing several times against this documentation these last days. According to it, there are two points of view regarding the creation of the opportunistic cross-docking decision:
- either the system does it by itself (= killing the Outbound delivery TO, modifying the destination of the Inbound delivery TO and updating related documents);
- or involved Inbound and Outbound deliveries must be manually designated for cross-docking throught the use of the monitor (like it is necessary to create Planned cross-docking decisions).
So, my questions are:
1. Do we need to manually designate Inbound and Outbound deliveries candidates for cross-docking using the monitor in order to create an opportunistic cross-docking decision?
2. If so, how can we automate the creation of the candidate designation?
Thx in advance for valuable inputs!
Edited by: al7sap on Oct 22, 2008 5:23 PM

Hello,
For Oppertunistic Cross dock..
You need to create either Putaway TO/Pick TO and then system checks the cross doc and cancel the TO and create a new TO from 902 to 916. and also updates in the document flow. This you can do with out Cross dock monitor. With out planning the cross dock you can do the cross docking by following the config in help.sap.com.
for more information about the complete config you need to see the sap link below. sure it will help you.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/c6/f85c504afa11d182b90000e829fbfe/frameset.htm
thanks.
tkreddy

Opportunistic Cross Docking Warehouse Task with status "B" - Waiting -

Hi All,
Does anyone have any experience with Opportunistic Cross Docking using SAP EWM 7.1? We have successfully executed OCD and EWM creates a warehouse task to move goods directly from GR to GI Zones but somehow the task is marked as waiting (B) and can't be confirmed through RFUI or using the GUI. Also this task is not assigned to a Warehouse order.
Looking forward to your inputs.
Thanks.
Y

Hi,
the configuration of the first storage type is:
The second type is configurated:
The third is:
The first warehouse task is from AKL1 to EAR1 and it works.
The second warehouse task is from EAR1 to EARE and here is the problem.
Best regards,
Rodrigo!

Cross-docking in WM with use of MIGO

Dear SAP experts,
I'm looking for my company to install cross-docking in SAP ECC6.0 were they use MIGO to do the goods receipt. Which are the possibilities I have to active/setup cross-docking in SAP based on MIGO receipts?
Many thanks for your help on this one,
Michael

Dear experts,
Is it possible? Can I make use of cross-docking in standard SAP without the use of inbound deliveries?
Many thanks for your help!
Michael

Cross Docking Functionality - ECC6.0

Hi,
Can some explain in detail what are the Cross Docking Functionalities has been provided in ECC 6.0 compared to the previous versions.
Thanks,
Chak.

Hi chakku,
Cross docking changes in ECC 6.0.
Effects on Customizing
To use Cross-Docking, you must define the following in Customizing for
Logistics Execution -> Warehouse Management - Cross-Docking:
o   General warehouse level settings, including the cross-docking
      storage type, outbound document release and latest release times,
      and FIFO tolerance duration.
o   The relevancy of cross-docking for warehouse movement types
You also have the option of personalizing the monitor and alert monitor,
as well as implementing project-specific logic via Business Add-Ins.
See also
o   IMG for Logistics Execution -> Warehouse Management -> Cross-Docking
o   SAP Library for Logistics Execution -> Warehouse Management ->
      Cross-Docking
Regards,
hareesha

Transporttaion Cross Docking between EWM and ECC across company codes

Seceanrio is as follows:
We have an EWM managed site in GB, and an IM managed site in IE.
We would like to use the transportation cross docking solution from within Service Parts Management to transfer goods from GB to IE, (ECC > EWM > ECC) across company codes.
Is this possible within the standard SAP solution?
Thanks in advance,
Craig Bramhald

Hi Hari
Inter Company Purchase scenario works when the same material exists in both the company codes... I dont know how SAP would manage this in the case of Assets, when the Same Asset No is not existent in the other Co Code...
However, Refer 1523976 PurchaseOrderERPRequest_In_V1:Asset account assignment fails
This applies to EhP4 / EhP5 - But I dont know if you are using the enterprise service PurchaseOrderERPRequest_In_V1 ....
If not, better create an OSS message to SAP and check with them mentioning the notes that you have mentioned in your message
BR,Ajay M

Opportunistic cross-docking not working

Hi All,
We are trying to implement opportunistic cross-docking process. My understanding is that during the creation of the goods receipt TO the system looks for any open picking TO and accordingly directly moves material from 902 to 916 storage type. The following configuration is done
1. For the warehouse opportunistic cross-docking has been activating by selecting option 4.
2. Cross-docking relevancy has been defined for movement type 101
3. For movement type 101, the 'Consider pre-allocated' check box is not ticked
4. In the respective movement types 1 & 2 for 'TO creation' are entered as screen control in movement types 101 and 601
5. No automatic confirmation for TO is set up
The following transactions are now done
1. Create a sales order with outbound delivery and TO created (not confirmed)
2. PO with MIGO (we are not using HU and hence no inbound delivery)
3. Now during the creation of the TO for the goods receipt, the expectation is that the system will look for the open picking TO and will cancel the same and then create the putaway TO directly from 902 to 916. But this does not happen.
Not sure if I am missing some setting or some transaction needs to be done differently. I went through SAP help but it does not give more details on what setting might be missing.
Regards,
Ketan

Hi Jurgen,
Thanks for the link. But I had already gone through it and configured the system accordngly. The surprising part is that corss-docking is working for outboud documents i.e. if i create a TO for inbound first and then for outbound then while creating the TO for outbound it automatically takes the source as 902 and cancels the put away TO. However for other way round where the outbound TO is first created and then the inbound, the expectation is that reverse should happen i.e. the destination in the TO should be taken as 916 and original picking TO should be cancelled. However it is not happening.
In the link it talks about points 5 & 6 which are only for HU environment and since we do not have the same I have not configured those. But my question now would be is it that opportunistic inbound cross-docking can only be possible with HU but not required for outbound. Else I do not see any other reason why this might be happening.

Not able to link inbound to outbound in cross dock

Hi,
we have a warehouse managment setup in our project we are using cross dock process linking of my inboun delivery to outbound delivery. In my inbound delivery consits of 2 materials amd my outbound also consists of the same materials while i am going to connect this inbound delivery to outbound delivery. The inbound is giving all the materials and while the outbound is showing only one item cross dock monitor but the second item is present in outbound delivery but it is not displaying in the monitor tool.
Can any one let me know.
sunil

Can you give me some more inputs on this? I need to know exactly what is the role of ware house there? What exactly you are doing in cross docking? Are you shipping the material received through inbound process by just putting in another truck? What mvt types are used here both for inbound and out bound?

Cross Docking from a Factory

Hi all,
I´m doing a first approach to cross docking, So far what I read about it is that the goods are taken from goods receipt to goods issue without being placed in storage in the meantime.
My customer is a factory. They heard about the Cross Docking advantages improving the process in the Warehouse and avoiding storage and inventory tasks (they are using WM).
Iu2019m not sure if Cross Docking can be the way for improving the process of producing and sending to costumers without storing in the warehouse or there is a easy way to follow with not Cross Docking involved.
Thank You
Al

The problem is that all the information I found so far about it is over the process of external goods coming and sending they out without the need of storing in the warehouse. They go directly to the picking area (one step) or in two step process going first from 902 (Good receive from external) to Cross docking Sorage type.and another movement from Cross Docking Storage type to 916 Good issue Storage type.
I need to know if it is possible to implement a solution of Cross Docking for certain number of products having a factory and a warehouse. If so, would you give me a brief process flow?.
Thank You very much.
Al
Edited by: agmogena on Aug 22, 2011 12:01 PM

Cross Docking Pick TO cancellation

Hi Experts
I am trying to Configure the Cross docking scenario
I have configured the following
1. Cross-dock Warehouse level customization in SPRO-LE-WM-Cross Docking-Maintain Warehouse level Settings
2. Cross dock relevancy for movement types in SPRO-LE-WM-Cross Docking-Define Cross docking relevancy for movement types
3. There is no Pre-allocated stock check for both movement types 101 and 601
4. Stock placement and stock removal confirmation required for storage types 902 and 916.
Transaction Steps:
1.Outbound delivery, TO created
2.Inbound delivery created, GR done, while creating Putaway TO system is moving the stock from 902 storage type to 916 storage type
But the pick TO created against the Outbound delivery is not cancelled and the Outbound delivery is not updated with the Putaway TO.
Which step or config i am missing?
Regards
Venkat

Hi, you have two options to configure cross-docking. Take a look at these documents for detailed explanation.
1) Planned Cross-Docking
Planned Cross-Docking - Cross-Docking (LE-WM-DCK) - SAP Library
2) Opportunistic Cross-Docking
Opportunistic Cross-Docking - Cross-Docking (LE-WM-DCK) - SAP Library
I figure you are using opportunistic xDck based on your question.
Could you just go through all the steps on the document I linked?
Just go through all of the requirements, carefully inspecting if any
of those doesn't match the process.
First you have the settings required. Make sure they are OK.
Then check the process flow and your documents you are testing
with.

Cross docking in EWM

Hi all,
We are trying to create a cross docking scenario in EWM. We are trying for the EWM triggered opportunistic cross docking. With all the suggested config settings and master data, the process is not happening. Can anybody share a config document regarding steps to be followed for Cross docking (in EWM).

kishore yerra wrote:
Because your scenario is working manually the above may not be a major issue.
That's right. I've checked my settings, but this doen't seem to be the problem. As said, it works fine when creating WT's manually.
kishore yerra wrote:
the way we can try and diagnose this would be to deactivate your entries for storage type search sequence and try to retain only one entry that you used for cross docking.
I've changed the storage type search sequence for putaway, so that the only available storage type is the Goods Issue zone. The system now creates a WT for putaway in 9020. However, it doesn't link the stock to the outbound delivery order, so it actually acts like a putaway. So, this is not the solution unfortunately.
kishore yerra wrote:
Along with this put a closs monitor on SLG1 to understand the determination used when warehouse tasks are created.
SLG1 shows the following error message when creating the WT:
Immediate Actions Only: Condition Is Not Evaluated (Message no. SPPF_DET_CRM002)
it also displays one interesting warning message:
Action Merging: One Unprocessed Action with Equality Check (Message no. SPPF062)
I'm not sure what to do next; any suggestions?
Regards,
Oliver

Cross docking in WM

HI,
can anyone explain about the usage of cross docking functionality and how to use it.
how to link an inbound docume

Hi Susil,
Cross-docking implies moving materials directly from the incoming to the outgoing physical areas of the warehouse. To process these materials without first putting them into storage, the warehouse must be aware of what deliveries are coming in and which deliveries are going out.
Inbound delivery helps in planning of incoming Materials in the Warehouse hence can make use of effective implementation of Cross Docking.
Cross docking can be monitored using Cross Docking Monitor. Details of the Cross docking monitor are well explained in the link below
http://help.sap.com/SCENARIOS_BUS2004/helpdata/EN/fc/efc43f82ab6d3fe10000000a114084/content.htm
Regards,
Ramakrishna

Cross-docking with external WM system

Hello Gurus,
We are trying to implement cross docking but we donu2019t have wm on the SAP ERP. We would like to know if this is possible. And this is possible, how can we manage this scenario for example: A delivery from PLANT A to a client that uses PLANT B as cross-docking plant. When the shipment leaves PLANT A what movement we need to do. When the materials of the delivery are received on PLANT B what movement should we do. When the shipment leaves PLANT B we make the goods issue?
Is this correct? If this is correct you have to change the plant of the sales order and delivery from PLANT A to PLANT B.
Best regards,
Tiago Magalhães

Managed by process not by any configuration.

Cross docking using SLS ( Supplementery logistics services )

Similar Messages

Maybe you are looking for