Cross-Docking and VAS

Hi All,
I'm wondering if anyone has experience working with both Opportunistic/Planned Cross-Docking and VAS directly in ECC.
How do they integrate with each other?
At my client we are going to use VAS to handle repacking at GR at storage type 923. After the VAS task has been completed and the second TO is created for the putaway, I'm hoping this will trigger cross-docking (either OCD or PCD).
Is anyone else doing this - are my expectations correct?
Regards,
Mark.
Edited by: busaboy99 on Feb 6, 2012 5:05 PM

Hi,
Explore following URL
Collective Purchase Order
Bye,
Muralidhara

Similar Messages

Cross docking and flow throughs

Hi Gurus,
Can anyboday send me configuration steps in cross docking and flow through scenarios in is retail.
thanks in advance.
Regards,
PS

Hi,
Explore following URL
Collective Purchase Order
Bye,
Muralidhara

WM cross docking and yard management

Dear Gurus,
Any body here could explain me step by step configaration of WM--Cross docking and Yard Management.
Any help will be rewarded.
Regards,
SAP.

Hi,
hum, this is a bit huge to reply.
Yard is working as cross-docking with a single WM.
Cross-dock needs :
A WM configured
WM movement types to be dedicated
More tricky, it needs to have the Goods receipt sequence to be modified. The goods receipt must be setup to be done before the TO gets created
Yard is more straight forward.
Yard site related to WM
Define the Yard map: The doors, parking spaces... (nota: Maintain the yard doors from the WM customizing. It is a WM location before all.)
some vehicles (Material group, ...)
Some master data. The trucks, the trailers...
To keep in mind:
a truck is an handling unit.
The relation between a delivery and a truck is done with handling units.
The relation between CD and Yard: At CD Decision time, a Yard scheduling activity will be created. Therefore a WM door will booked.
Hope this provides a starting point to you
BR
Alain

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

Re: WM cross docking and yard management

Is there a way to stop automatic scheduling in Yard Management.
Can someone explain how you can schedule a vehicle without first check-in in Yard management.

Hi,
hum, this is a bit huge to reply.
Yard is working as cross-docking with a single WM.
Cross-dock needs :
A WM configured
WM movement types to be dedicated
More tricky, it needs to have the Goods receipt sequence to be modified. The goods receipt must be setup to be done before the TO gets created
Yard is more straight forward.
Yard site related to WM
Define the Yard map: The doors, parking spaces... (nota: Maintain the yard doors from the WM customizing. It is a WM location before all.)
some vehicles (Material group, ...)
Some master data. The trucks, the trailers...
To keep in mind:
a truck is an handling unit.
The relation between a delivery and a truck is done with handling units.
The relation between CD and Yard: At CD Decision time, a Yard scheduling activity will be created. Therefore a WM door will booked.
Hope this provides a starting point to you
BR
Alain

Cross docking functionality in SAP F&R

Hi All,
    I want to know how the cross docking functionality is handled in SAP F&R.
   Whether I should give RP type 11 in store level and RP type 01/02 in DC level for these cross docking products?
   Whether anyone has done the dynamic allocation functionality for cross docking products in which there should be an option to send the latest Order proposal values to ECC from SAP F&R so that STO s can be done with those new OP values?
Regards,
Resmi Raj.

Hi Eduardo,
Thanks for your reply. I have the similar scenario
Herein, we have kept relationship as mentioned below
Article: 100050
Store: FRS4
DC: FRD4
Vendor - TESTVEND1
For Vendor -> DC, we have maintained the distribution profile as FTM (Cross docking) and the RP type for article as 01
For DC -> Store, we have maintained RP type as 11
Now when we have updated the consumption data for both DC & store for the article at DC / store. We ran FRP for both DC (FRD4) and store (FRS4). The order proposal was getting created correctly for store, while no order proposal was created for DC as per the RP type.
Now, how is it being classified as a Cross docking scenario as we expect that the OP (STO's), once their inbound delivery is created, then they should be cumulated in ECC and generated a collective PO for Cross docking. Is that correct. Also, can you please let know the exact process to be followed for the same.
thanks
Best Regards
Prashant

Cross Docking for stock category Q (inspection stock)

Hello everyone,
My client uses cross docking in 4.7 release and recently a requirement came up where they wanna be able to cross dock stock received from production while the User Decision from QM is still pending.
I have tried to walkthrough the code behind planned/opp cross docking and realised that only available stock is taken into consideration.
I d be really grateful if anyone could suggest how to best approach and tackle this issue? Please consider that the quant should not lose the inspection lot number so that once UD is given, the stock category changes automatically.
Thank you
Kind Regards

Yes it is possible. In the IM/WM interface tables, in the second table, you can vary the process according to stock status. See the third column.
LogisticsExecution \ Warehouse Management \ Interfaces \ Inventory Management \ Define Movement Type
Following is the config. help text for the field
Special Stock Indicators for Whse Mgmt
Use
In the Materials Management system you can post different transactions using one movement type. For example, posting goods receipt to unallocated stock or goods receipt to
stock in quality inspection.
These transactions are treated differently by the system on the basis of this indicator. Together with other indicators of a movement type in the Materials Management system, this indicator is used to correctly allocate a movement type in the Warehouse Management system so that the transaction can be posted accordingly.
Regards,
Nick

Cross-Docking Config.

I am working on Cross-docking scenario in ECC system and I am stuck at "Generating a Cross-Docking" Decision. This is the 6th step as per Best Practice GZ6.
What are config settings that should be maintained to generate a decision?
I have maintained General Settings of Cross-docking at WAMS and got stucked at Monitoring settings.
Kindly help.
Thanks!
Abdul Saleem

W71 is a BPP for executing Opprotunistic Cross Docking and, quite frankly, I found it makes no sense at all. It has a step to create an Outbound Delivery using MB1A - VL10B is usually used to ccreate and Outbound Delivery. MB1A just creates a Goods Issiue. The same applies the the step for creating an Inbound Delivery - MB1C??? That creates a Goods Receipt - not a Delivery.
The best I've found for actually setting up Cross Docking is:
http://help.sap.com/erp2005_ehp_02/helpdata/en/3e/49503e30a9d549e10000000a114084/content.htm
http://help.sap.com/saphelp_rc10/helpdata/en/6f/dadd4424b711409384ce2382728f57/content.htm
Even still, I have run into a problem allowing the Goods Receipt of an Inbounde Delivery prior to confirming the WM Transfer Order. The steps in the config doc show where it should be set, but it is in the Handling Units section of the IMG. The documentation implies this should work for non-HU receipts as well. I keep getting the error that the GR cannot be completed because the WM TO is not complete.
I'm still looking for an answer to this.
Jim

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

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

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

Cross-Docking, Deliveries and availability check

Friends & Gurus,
From what I read, Cross Docking (ECC 6.0) works with deliveries. I can link an inbound to an outbound delivery so as soon as the goods are received they head straight to the outbound delivery.
If I plan to use X-Docking for stockouts, how can I link the deliveries if the outbound cannot be created because of availabity check (no stock on hand).
Question: Should I change the availability check of the outbound deliveries so I can create them without stock on hand in order to use X-Docking functionality?
Thanks stranger!

Hi
If you are talking about blocked stock you can remove the check for blocked stock in OPJJ transaction. this will make availability check will not consider blocked delivery
If useful reward points
Regards
Ranga

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.

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

Cross-Docking and VAS

Similar Messages

Maybe you are looking for