New ME workflow for CLFMAS02

[Former Member]

Hello Experts,

I have been facing an issue with a new workflow I created that I was hoping to get some ideas from you.

The requirement is to push batch characteristics changes from ECC to ME using CLFMAS02 (class type 023) and update available inventory data details for the batch via MII through available web service. I'm currently working with ME 15.1.1.5 and here is what happens.

Current development and configuration:

- iDoc CLFMAS02 is being sent to ME just fine (we have other iDocs being processed with no problems)

- I've created Split workflow with message type CLFMAS02. XSLT file was created resulting on Z_CLFMAS02 with plant information and works fine.

- I've created Standard workflow for message type Z_CLFMAS02. XSLT file was created and works fine.

- MII service transaction was created and working to update the selected inventory ID with the receiving batch characteristics

Issue:

- When CLFMAS02 is received it goes into FAILED status with the following error message: No workflow defined for this message type.

Intial testing:

- If I Retry CLFMAS02 message on Queue Monitor it works fine, generating one Z_CLFMAS for each plant wich are also processed fine, updating correctly inventories we are looking for.

I did some research around it and I found the following scn post: http://scn.sap.com/docs/DOC-69668

Further testing according to that nice post above:

- I've added a MII transaction to SAPMEINT_CustomerMessageDiscriminatorTxn where the output is the string CLFMAS02 when KLART=023 otherwise nothing is passed to the output.

It didn't work. I got the same results.

More testing:

- I've added a service transaction to the split workflow just to generate a log in MII. I was curious to see if the split workflow wasn't being called at all but it turns out it was. Even though on Queue Monitor it says No workflow defined for this message type, the service transaction was called when CLFMAS02 iDoc was received.

Then I did some more extra tests but just dead end.

I really appreciate your time to go over this long message.

Thank you!

Ricardo

[sergiy_katerinich]

Hi,

If I got it right, the bottom line is "the initial receipt of IDoc fails but Retry works". If so, then it looks like a bug, otherwise please describe the issue step by step.

Regards,

Sergiy

[Former Member]

Hi Sergiy,

You got it right. I will create an incident and share once get a resolution.

Thanks,
Ricardo