Integration mapping C4C-ERP error.

[Former Member]

Hi everyone!

Yesterday I added on fine tune - opportunities some custom status.

I configured that GAN e IMPL code are the two status that can generate a quote on ERP.

Today I make a test and this error appears

CM_MBF_OPA_TRANSF_DEF:External code for ExternalUserStatusCode GAN could not be determined.

I understand it could be a mapping error but I'm not sure with what should I mapp in ERP.

On the other hand, this opportunity does not flow to ERP, so the problem must be in my C4C configuration..

Can you please advise?

Thanks in advance!!!

Regards

[chandansb · Accepted solution]

Hello Maria,

Using integration, Opportunities from C4C can only fetch pricing for products and request for follow up documents in ERP. So I guess there is no reason why you need to set the custom status. (As they are not at all going to be replicated to ERP with Opportunity)

I will suggest you not to use the Custom Status as there is no reason to map/match with ERP status.

Hope this helps.

Regards,

Chandan

[Former Member · Accepted solution]

Hi Chandan thanks for your reply.

Custom status is used as a category that the client wants.

But I'll try not using it and see if the integration works. It worked without this before.

Thanks!

[Former Member · Accepted solution]

Chandan on the xml it says

</ItemProduct>

</Item>

<ExternalUserStatusCode listID="OPPT">GAN</ExternalUserStatusCode>

</Opportunity>

So looks like it is traveling to ERP?

Regards

[Former Member · Accepted solution]

Hey Maria,

Check if you have maintained the Code List Mapping for ExternalUserStatusCode with these custom codes you have created?

I suspect the problem is with C4C unable to determine the code you are sending in XML

Manideep Satya

[Former Member · Accepted solution]

Hi Manideep the problem is that i don't know with which ERP code I have to mapp.

Regards

[h_duengelhoef · Accepted solution]

Hi Maria,

map it to any id that is not yet used as external value in a different row. The standard PI mapping doesn't map the opportunity status code to ERP. Therefore it doesn't matter to which value to map it to

Hermann