Hw to deactivate a valid cross-docking item i.e., 2-step picking

Hi Experts,
Hw to deactivate a valid cross-docking item i.e., the two step relevance should be de-activated for the delivery items. i want to convert 2-step picking to one-step picking based on elapsed time.
Be helpful. Its urgent.
Thanks & Regards,
Madhu

System will generate XD deliveries once you do the goods receipt against Vendor Purchase Order.In your case two outbound deliveries generated as you have to UB Purchase Orders.After Creation of deliveries then you tried to create the delivery through wf30 .As the deliveries created alredy you got error No entries found relevant to delivery generation;'
If you delete the deliveries then it is difficult to create new outbound deliveries.

Similar Messages

Cross Docking EWM

Hi Experts,
the chapter "Merchandise distribution cross-docking " of the EWM-Manual (EWM 7.0) says: "SAP ERP ... sends inbound and outbound delivery documents to EWM, which contain the process methods and the purchase order item as a reference. ... The merchandise distribution process in EWM corresponds to the process method in SAP ERP"
SAP ERP sends the inbound and outbound delivery via "SHP_IBDLV_SAVE_REPLICA / SHP_OBDLV_SAVE_REPLICA". Which of the data fields contains the process method (e. g. Merchandise distribution cross-docking )
Thanks!
Kind regards
Ralf

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

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

IS-R: Picking in Flow Through and Cross Docking

In Merchandise Distribution (conceptually),
- for recipient-driven flow through, picking is done before GI.
- for cross-docking, no picking.
Which configuration controls the picking has to be done in flow-through and not to be done in cross-docking?

>
Vitthavat A. wrote:
> In Merchandise Distribution (conceptually),
> - for recipient-driven flow through, picking is done before GI.
> - for cross-docking, no picking.
>
> Which configuration controls the picking has to be done in flow-through and not to be done in cross-docking?
Hi,
Path - IMG - Logistics General - Merchandise Distribution -- Plant Profiles for Merchandise Distribution
If you indicate not relevant for picking
or
Delivery Item category - OVLP
Same indicator is available at delivery item category
Regards
Vijai Jain

RLM - Error at MIGO (Cross Dock) for supply process Stock / Non Stock

Hello Friends!
I am experiencing a strange error at time of MIGO for a RLM Stock / Non Stock supply process. I believe it could be due to RLM's effort in creating a (Cross Dock) Delivery in the background.
Error details: 'Enter a material or an item category' -- Message no. VL383
Please help!. Thanks!

Hello Friends!
I am experiencing a strange error at time of MIGO for a RLM Stock / Non Stock supply process. I believe it could be due to RLM's effort in creating a (Cross Dock) Delivery in the background.
Error details: 'Enter a material or an item category' -- Message no. VL383
Please help!. Thanks!

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.

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.

System ignoring cross-docking decision during LT0F

Hi all,
I'm trying to do some planned cross-docking between and inbound delivery and a TR for production supply.
I've created a CD decision which is sitting there waiting, however when I create the putaway TO via LT0F for inbound delivery, the TO is created ignoring completely the CD decision which is linking that delivery item to the TR.
Any suggestions - and please don't just post a link to the SAP help prerequisites - I've already been through this!
Regards,
Mark.

HI
The second point says that the quantity in inbound delivery and outbound delivery should same as Pallitization data maintained in the material master WM 2 view(LE quantity)or multiples of it.
If you have a quantity less than the Palletization Quantityin the deliveries then the deliveries will not appear in the Cross dock moniter.
LE quantity: 20 in the material master
your deliveries qty should be 20 or multiples of 20.
please try with this.
Regards
Srinivas

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.

Duplicate dock items since upgrading to Mountain Lion

My upgrade to Mountain Lion has worked well, except for one minor irritating thing: a couple of applications are now duplicated in the dock at every log-in.
• I have only one copy of each application (specifically they are TextExpander and Vitamin-R).
• Log-in Items in my Account pane in System Preferences shows nothing unusual.
• Nothing in the prefs panels for each program shows any problem or likely conflict
• All four dock items are fully functional.
• I can slide the duplicates from the dock to kill them, leaving only one copy of each app active. When I restart the machine the duplicates are back.
I realise this is going to be something simple, but I can't think of anywhere else to look. Does anyone else have any ideas?

Go to your Finder "Go" menu choose "Go to Folder" and enter ~/Library/Preferences. Then delete these files and restart or log out and back in.
com.apple.dock.plist
com.apple.dock.db
This should return the Dock to default, so you'll need to reset it the way you like it.

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 in SAP R/3 ECC 6.0

Folks,
I'm struggling to make 2-step w/ planned cross docking work. Basically, unable to connect the planned with the candidate document.
Here is the scenario:
1. (Candidate) Outbound delivery created with a delivery date / time of 09/04/08 - 10:00 (No TO initiated)
2. (Planned) Inbound delivery created with a delivery date / time of 09/04/08 - 12:00 (No TO initiated)
The system invokes different messages based on the following config. settings: (These messages occur when I right click on the inbound delivery and select "plan cross docking")
Setting 1:
Planning time: 1 D
Default Release: 1D
Def Latest Release: -
Message: No inbound documents have been selected for planning
Setting 2:
Planning time: 1 D
Default Release: 1D
Def Latest Release: 1D
Message: Time ref. 09/04/2008 10:00:00 of plan.doc. xxxxxxxxx does not match cand.documents time refs
BTW, it's a simple setup WITHOUT transportation, yard management, HUM or SUT.
Thanks in advance for your valuable comments!!

Dear Christiane,
First & foremost appreciate your quick response.
As per what you say (& If I have understood it correctly) having the Delivery Date & Time of the Inbound as 09.04.2010 10:00 would solve the issue ? I did change the Inbound Delivery time but to no avail.......as per my example.....what do you think should be the Inbound/Outbound Date & Time
If I understood right, as per my example, the Outbound Delivery time is set to 12:00, the latest release time is set to 1 hr thus the latest time for the outbound to be released is 11:00 (Outbound Del time - latest rel time)
Planning time is again 1hr, so planning window is from 10:00 to 11:00 - [(Outbound Del time - latest rel time) - Planning time]. Hence if I set the Inbound time to 10:00 it should work right ?
The release time, what effect does this have ?
Looking forward to your help.
Imran

Validation on text item

Hi all,
i have a text item P6_MAXLIABILITY
I put a validation on that item with regular expression.
I want that validation to happen, when the focus moves to the next item.
could any one give me a suggestion?
bye
Srikavi

Hi,
if the focus changes the javascript is event "onblur();" automatically fired. Then you can call own javascript function and validate the input.
Example:
<form name="test" action="">
Name: <input type="text" name="input1" onblur="checkContent(this.value)">
</form>
<script type="text/javascript">
document.test.input1.focus();
function checkContent (field) {
if (field == "") {
alert("Please input something!");
document.test.input1.focus();
return false;
</script>

Validation on an Item

Hello,
I am trying to put a validation on an item.
I have two columns:
Ethics Status and Ethics Tracking Number
Ethics Status is required but Ethics Tracking Number is only Required if Ethics Status is Yes.
I am unsure how to go about doing this. Can anyone point me in the right direction?
Thanks,
Jessica

I would create a Validation for the item Ethics Tracking Number that says it cannot be NULL, and then set the condition to "Value of Item In Expression 1 Is NOT NULL", and then in the Expression 1 box fill in the name of the page item for the Ethics Status field.
This way the validation is only applied when the condition evaluates to TRUE, which will only happen when Ethics Status is not null.
So if you had the item P1_ETHICS_STATUS, then put that in the Expression 1 box.

Hw to deactivate a valid cross-docking item i.e., 2-step picking

Similar Messages

Maybe you are looking for