Establishing TN profiles to work with ambiguous Ariba credentials

1

Hi All. We are very new with wM. Looking for some insights from anyone that deals with Ariba. Specific problem is how to set up profiles to handle ambiguous TO credential information. Some Ariba customers send us cXML OrderRequest with TO credentials with domain=DUNS and and a value of our DUNS #. Others send us domain=DUNS, but the value is our networkid. Anyone else run into this?

Case 1
<to>
<credential>
<identity>025036265</identity>
</credential>

Case 2
<to>

<credential>
<identity>AN01000079261</identity>
</credential>

Thanks for any insights.

2

Hi - the Credential element must have the correct domain specified - either ‘NetworkID’ or ‘DUNS’.

For eg: (Note: the cXML snippet below was mangled to all-lowercase by the forum software)

&#60;from&#62; 
  &#60;credential&#62; 
    &#60;identity&#62;AN010011111&#60;/identity&#62; 
  &#60;/credential&#62; 
  &#60;credential&#62; 
    &#60;identity&#62;123456789&#60;/identity&#62; 
  &#60;/credential&#62; 
&#60;/from&#62; 
&#60;to&#62; 
  &#60;credential&#62; 
    &#60;identity&#62;AN01000022222&#60;/identity&#62; 
  &#60;/credential&#62; 
  &#60;credential&#62; 
    &#60;identity&#62;123123123&#60;/identity&#62; 
  &#60;/credential&#62; 
&#60;/to&#62;

> Others send us domain=DUNS, but the value is our networkid.

Hmm. that’s shonky. I thought Ariba would throw a validation error in such cases?

3

Thanks Sonam, but Ariba does allow it. I believe it actually occurs because of a set-up GUI they provided. We receive the scenarios I described into our PRODUCTION account. Ariba told us that we could get our customers to fix it, but they didnt want to mess with it. We now have 5 customers that send domain=DUNS with the identity=our netID, and 2 that send domain=DUNS using our actual DUNS #. I am both surprised & disappointed that no one else seems to be using wM with Ariba. At least I have not gotten any other feedback. Can anyone confirm that it’s just OUR customers? Anyone else doing Ariba with more than 1 customer & for longer than the past 6 months?

Thanks in advance.

4

Chris,

You can make changes to your gateway service to run another service to go through all the IDs and try to match any. This service would have to be called after wm.tn.doc:recognize and before the document is persisted and submitted to TN.

Contact me offline for more details and code samples.

Rupinder