Opportunistic Cross-docking in EWM

[Former Member]

Hey guys,

I am using the Inbound driven opportunistic cross-docking functionality in EWM. I've made all the relevant customizing settings and maintained the product master data.

My scenario: I have an Outbound Delivery Order for 5 PCE for product X.

I perform a goods receipt for 8 PCE for product X.

Now, when I manually create the Warehouse Tasks for my warehouse request (/SCWM/TODLV_I), EWM creates two WT's:

- WT1 will move 5 PCE from my GR-area to the GI-area (so, cross docking)

- WT2 will move 3 PCE from my GR-area to the fixed bin area.

So, this works as designed.

However, when I let EWM create the WT's via PPF, it only creates one WT; 8 PCE from GR-area to fixed bin area.

So, in other words, the cross docking functionality is not working in this case.

Does anyone know how to make the necessary settings to solve this?

Thanks & regards,

Oliver

[tamaszsolnai · Accepted solution]

Hi Oliver,

Are you using process oriented or layout oriented storage process control or both?

Do you have an unique warehouse process type for Cross Docking?

It seems for me that the system is not recognising that you would like to do Cross Docking, it is following the configured put aeay process.

Tamas

[Former Member · Accepted solution]

Hello Tamas,

For my cross-docking process, I'm not using LOSC or POSC; I'm just using the standard putaway process, whse process type 1010.

Indeed, it looks like the job which creates WT's doesn't recognize the CD-process. This is strange, because when I create the WT's manually (/SCWM/TODLV_I - Putaway for Inbound Delivery ), it does "see" that the cross-docking process is in scope.

From my opinion, there should be no difference between the two options.

Any help is appreciated!

Regards,

Oliver

[Former Member · Accepted solution]

Hi Oliver,

Please check the below.

1. The cross docking items shouldnt be qualified for Quality Inspection, which means there should be no quality inspection rule.

2 Cross check your product group definition and the same product group is used for Cross docking determination.

Because your scenario is working manually the above may not be a major issue, 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.

Along with this put a closs monitor on SLG1 to understand the determination used when warehouse tasks are created.

Let us know your findings.

Regards,

Kishore

[Former Member · Accepted solution]

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.

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.

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

[Former Member]

This message was moderated.

[tamaszsolnai]

Hi Oliver,

The following things should also configured:

- Stock removal strategy: you have to assign the inbound storage type to the stock removal strategy.

IMG EWM>Goods Issue process > Strategies > Specify Storage Type Search Sequence

- Stock determination rule and group: you have to extend the search criteria for the GR area

The stock determination group have to be assigned to Product Master in EWM

IMG EWM> Cross Process Settings > Stock Determination > Maintain Stock Determination Groups

IMG EWM> Cross Process Settings > Stock Determination > Configure Stock Determination

- RF queue determination: the cross docking can only handle by RF device only.

IMG EWM> Cross Process Settings > Resource Management > Define Queues

I really hope it will help for your problem.

Tamas

[Former Member]

Hi Tamas,

Thanks for the info, though these settings have already been made.

As said, it works fine when I create the WT's manually; in that case, EWM automatically "finds" the outbound delivery order.

I think there's something different between the creation of WT's manually vs. creation of WT's automatically, though I can't figure out what it is.

Regards,

Oliver

[Former Member]

Hi Oliver,

Look at this OSS note 1651868, this might help your situation.

Regards,

Kishore Yerra

[Former Member]

Hi Kishore Yerra,

Thanks for the note; looking at the description this would definitely help.

Unfortunately, the problem still occurs after implementation of the note. I've logged an OSS call now, as it seems to be a program error.

I'll keep you updated.

Regards,

Oliver

[Former Member]

Hello all,

Just a quick update: SAP is currently investigating this issue. They have confirmed it is a program error, I'll update this thread once a solution has been provided.

Regards,

Oliver

[Former Member]

Hello all,

SAP has created a new SAP note to solve this issue. After implementation, the issue was solved in my system.

Note number: 1677517

Regards,

Oliver