Hi all ,
Can we deifne two mutuallydefined items for single user. or is there any solution how to do with two external Ids for same user.

Actually , One of TP uses two different services and he will send data with two differenet sender names and whenever I am trying to keep one mutuallydefined and one userdefined at that am getting following error …

Technical Error : Transform for SenderID of doctype Message failed to produce a value. The transform function was FN_PARTNER_LOOKUP, the first original value was PQRTS.

please let me the way to resolve !!


Thanks & Regards ,
Kaniska

Hi,

you can always used the usual defined values to configure different ID’s.
Are you reciveing the different qualifiers for different SenderID’s?? What kind of data u are recieving from partner?

Plz congiure the different senderID’s as userdefined1 or mutually defined at your end.

-nD

What kind of file your TP will be sending?

xml file

For the required external ID type, TN allows just one of those. The default required external ID is DUNS.

If you have not changed the default to “Mutually Defined” then you can have multiple Mutually Defined IDs for a single profile. In the profile, simply define the second value.

That takes care of your original question. But your overall scenario may need a bit more explanation. Since the two external IDs are for a single profile, the processing rules won’t be able to make a distinction between the two IDs (this is as designed).

You mention that “one TP is using two different services.” Is the document type being sent to these the same?

If you need different processing, then either the profile or the document type will need to differ. Or the document must have an attribute upon which the right processing rule can be selected.

Options

• Two different profiles for the same partner (this is not as terrible as it may sound)
• Two different document types
• One document type with an attribute that can be used to select the right processing rule

HTH

Kaniska,

If you have not changed the default to “Mutually Defined” then you can have multiple Mutually Defined IDs for a single profile. In the profile, simply define the second value.

–>Yes this is what exactly you have to do…and i was trying to say in the other thread of yours. and there shouldn’t be any changes to Document Type / rule.

Thanks Rob for jumping in and pointed out with more info.

HTH,
RMG