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!

Similar Messages

Warehouse task in status "b" (waiting) will not be activated

Dear experts,
in the following situation i want to execute a stock removal and the following problem appears:
When the warehouse task for stock removal will be created, the layout-oriented storage process control creates two warehouse tasks:
The first warehouse task is MFS relevant and will be automatically confirmed by the resource (Telegramtraffic).
The second warehouse task (not MFS relevant) stays in status "b" and can´t be activated. But it has to be confirmed manuelly by the user and because of status "b" it´s not possible for the user to confirm the warehouse task.
Why will the second warehouse task not be activated? Do someone know any hints to clear this situation?
Thanks in advance.
Best regards,
Rodrigo

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!

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.

Opportunistic Cross-Docking and Transfer Requirements

Hi all,
I'm trying to set up opportunistic cross-docking sent sent GR stock directly to the production supply areas when there is a shortage of inventory in the warehouse.
The PSAs are replenished with a manual KANBAN call which generates a TR with 350 mvt type.
I'm struggling to ge this to work, and when I read the SAP Help on opportunistic cross docking the process flow keeps discussing that the system searches for relevant TOs, not TRs...... but then I know you can do planned cross-docking for GR to TR - I've set this up before.
Has anyone done the same and might have tips for me?
Regards,
Mark.

Hi Mark,
I am also looking for a solution / guidline of this scenario.
Could you please tell me if you have implemented this in the meanwhile?
Thank you! Regards
Uwe

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 Quantity

I am sorry if I cannot test this, but we need this information in order to make the recommandation to acquire EWM. We do not have it yet.
Here is the question : in the SAP documentation:
http://help.sap.com/erp2005_ehp_02/helpdata/en/3e/49503e30a9d549e10000000a114084/content.htm
Point 4.a.ii in the process flow says that " TO item contains the same material, quantity, plant and storage location as the putaway TO item to be created."
"SAME QUANTITY" is what I do not understand.....
If I have 3 open Picking TOs (quantity of 1 for each) for a material and I receive 5 on a PO, will the system create one putaway TO (quantity of 1 ) for each of those 3 open picking TOs ( to Goods Issue Area) and one Putaway TO ( to storage area ) for the 2 remaining ?
We are a manufacturing facility and we need to replace a system that cross dock everything missing or due in the short term when we receive.
Thanks,
Alain

Hi,
As per what I have observed, cross-docking happens in case of Full pallets. Usually TOs are created to pick full pallets or partial pallets. Also receiving happens in terms of Full pallets or partial pallets. If my receiving quantity is a full pallet quantity, then in case of opportunistic cross docking(Inbound to Outbound), it looks for possible open Pick TO items with same quantity(full pallet), cancels it and creates a cross dock TO from GR area to GI area for that outbound delivery.
Hope that helps.
Thanks
Vinod.

More than 50 MB sized applications are grayed out with status of "Waiting/Installing", when we update those apps from WiFi Connection?

Hi,
Few application updates are available in iOS App store. However, Those applications are grayed out with status of "Waiting/Installing", when we update those apps from WiFi Connection. It's happening only for more than 50 MB sized applications. Unable to install those application through WiFi, However, it's successfully installed through MacBook Pro iTunes application. Please suggest me, why this happening suddenly.
Thanks in Advance,
Suresh Balakrishnan.

- If I make the deployment required, it will install right away regarless of maintenance windows. However, i don't want to use this option because if the user logs in to other machine (e.g. boardroom computer), it will auto install this software.
Re-check your deployment, specially the user experience:
If you've checked the box next to "Software installation", it will install after the deadline has passed and ignores maintenance windows. Change the deployment to required and uncheck that box and the software should be installed according to your
maintenance windows.

EWM Opportunistic Cross Dock

Hi All,
I am doing the following scenario and I have all the config and master data setting that is needed to do cross dock.
This scenario is cross dock from the Inbound side
1. Create Sales order for qty 10 in ECC and that is replicated in EWM.
2. Wave the ODO in EWM and that creates an WT to pick 10 qty from the GNL location. The WT is still open and I did not confirm it yet. The WT has source and destination HU determined. The WO has Queue assigned based on Queue determination
3. I now create an Inbound delivery in ECC for same prod and Qty 10 and it is replicated in EWM.
4. In EWM, I pack the qty 10 in a HU and then I do a 'Goods Receipt' to the GR-ZONE. I don't have a POSC
5. Now I am manually creating a putaway WT for the ID.
Now this is where my problem is. I was hoping that system will cross dock this inbound delivery with the outbound delivery and in doing so, it will cancel the open Pick WT that was created for the ODO and will create a new cross dock WT but system did not do so. It is creating a direct putaway WT to the GNL location.
ALSO, this process works when for the ODO, I do not create any open WT. In that case, during putaway WT creation it is cross docked.
So the question is, does EWM consider open WT's during XDock? In some texts, SAP writes that the open WT's will get cancelled and cross docked but that is not happening.
Thanks for your inputs and help
James

Hi,
EWM can cancel an open pick WT. What it says in the docu is " If open pick warehouse tasks of this kind exist, EWM cancels these without violating the FIFO principle."
Well, in reality it is not that simple. First of all the open WTs must be RF relevant (you wrote you have a queue, but it must be an RF-queue (which I suppose you have)). The other thing is the question with FIFO. Now it does make sense that EWM does not cancel a WT if the already assigned quantity is older then the one you have in the GR zone. But what acutally happens is that the system checks the goods removal rule being used for the open WT. If this one uses the GR date or the SLE date, then the system does NOT cancel the WT. This is part of the standard BADI implementation you have to have to CD. And this is where you have to put in your own logic.
Brgds
Juergen
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/curriculum/scm_ewm
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub

EWM Opportunistic Cross Docking issue - Its put away instead of 2121 - Pick

Hi
We have checked all settings, configuration for Opportunistics cross docking - EWM (SCM) set up.
Storage type search sequence, activity type, WPT etc
But while performing following steps we are facing the issue :
1: We create PO in ERP
2: Inb delivery in ERP
3: Read Inb del in EWM - PRDI
4: Perform Follow on task - WT creation and SAVE
5: Create Sales order and outb del in ERP
6: Read the docu in SCM - EWM
5: See MOnitor - for Inbound delivery status is Put away
Outbound SHOULD HAVE BEEN 2121 (WPT) with PICK, but still Put away GR is already performed.
Its 1021 instead of 2121 WPT..
Any pointers please ?

Jacob,
Yes, I after I posted that message I retested and it worked as I expected. The only downside is that any GR reversals for the production orders will go to COGI due to the fact that 901 no longer allows negative stocks, but this is not that big of a deal.
Thanks for confirming my thinking.
Jeff

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

2-way SyncBO's with Status I-Waiting?!

Hi,
I am struggling with a sync issue. We are using MAM 2.0 running on a 6.2 WAS with ME 2.1.
I am unable to get the 2-way SyncBo's (MAM_001, MAM_010 and MAM_070) through. In MEREP_MON I can see they have status I-Waiting.
Any ideas on what could be wrong?
Best regards
Chris

Dear Gisk,
I am also facing the same problem as above.
I have deployed MAM 2.5 SR2 on desktop.
<b>The sync BOs(S01) MAM25_070, MAM25_010 and MAM25_01 are going into waiting stage.</b>
I have tried doing Ctrl+F10 but I am gettingfolowing message.
<b>None of the selected worklists can be reprocessed
Message no. MEREP_00309</b>.
Can you please help me solving this issue? Actually there is no runtime dump getting created (Transaction ST22)and also there is no log no data for these sync Bos.
I am not sure how to debug it further as there is no log.
Thanks&Regards
Satya

Kanban with status sequence WAIT EMPTY FULL shows '-' neg. sign after GR

Hi PP
I am using one control cycle in kanban with replenishment strategy
stock transfer where in stock transfer using "stock transfer with
reservation".
I made one bin empty at the demand source using t code PK13N
But when i am doing transfer posting using migo against the
replenishment element created by emptying the kanban , i am getting
messge "NO KANBAN EXIST".
why system is behaving abnormal i mean trnasfer posting not happening.
system is not behaving normal.If i forcibly do the posting ignoring
warining message above mentioned it shows no change in bin status ,
then if i manually change status to green by PK13n it makes it green
but wth negative sign.This behavior is quite abnormal as i have
sufficient stock to get transfered too.
status sequence is with three statuses WAIT EMPTY FULL
Please help in this regard
Even if i use this status sequence for inhouse production also same problem is their

Hi,
Check the settings for replenishment strategy u have selected for the material.
OM11 - Production Relenishment strategy
OM12 - Procurement Replenishment strategy
as in ur case u are now procuring that element so, check order type in ur replenishment strategy
Regards
Samunder Singh

Cross Docking with LE-WM - or - Reactivating Back Orders upon Goods Receipt

I have been reviewing the documentation for Opportunistic and Planned Cross Docking in LE-WM. The requirement is to release Back Orders upon receipt of a shipment to avoid putting them away and picking them right away from the bin. We want to release the Back Orders for picking in the GR area at the time of receipt.
So far it appears that Opportunistic Cross Docking depends on a Transfer Order already existing. The system then cancels the existing TO and replaces it with a TO to pick from the receipt Storage Type.
Planned Cross Docking appears to require an existing Outbound Delivery to the expected Inbound Delivery.
In the case of a Back Order, no Outbound Delivery or Transfer Order exist since there is no stock to release until the goods are received.
Is there a way to release Back Orders to be picked directly from Goods Receipt?
Thanks;
Jim

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 with GATP

I am considering ECC WM and / or EWM. One of my requirements is an opportunistic cross dock that will assign goods at GR to an open sales order line item. EWM opportunistic CD is synonomous with PFGR. Does ECC WM provide any benefits over EWM in terms of cross docking with GATP?
Many thanks.
Michael

Have you received any feedback from SAP or from third party consultants that the WM to EWM connection is feasilble? The benefits of EWM to GATP vs. ECC WM to GATP are very big, however , I am not even sure that WM to GATP is a real option. That is why I ask.

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

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

Similar Messages

Maybe you are looking for