ByDesign - Incoming Sales Order - Remote Master PC Code was not provided.

[former_member262605]

when I try to process an incoming Sales Order in ByDesign, the message is not processed because of the following error:

"Remote Master PC Code was not provided."

Does anyone know what this message means (I cannot find it in any documentation, SCN, Google).

Is this caused by a setting in ByDesign, a missing element in the message, or by the sending system? Message was send from SOAP UI as well as from Dell Boomi. Error message was the same in both cases.

My test message was created manually, based on the WSDL file, and it's far from complete I guess.

If anyone could send me an example xml file of a working Sales Order, that would be great!

Thanks,

Marcel Dekker

[former_member262605]

Hi Knut,

we managed to create a Sales Order.

Thanks for your support!

regards,

Marcel

[knutheusermann]

Hi Marcel,

please use the communication user displayed in the communication arrangement. This user has all required authorizations.

Regards,
Knut

[former_member262605]

Thanks Knut,

I have changed the header.

Also, a colleague found a small error in one of the party ID's (probably caused by a copy / paste action).

We now have a Sales Order that's being recognised as a Sales Order by ByDesign !

The next hurdle is the technical user not having enough authorisation to create the Sales Order, but we are working on that.

thanks for your answer!

Regards,

Marcel

[knutheusermann]

Hi Marcel,

I assume you are using the asynchronous B2B interface SalesOrderProcessingOrderingIn of communication scenario Sales Order Integration?

In such 3rd-party inbound integration scenarios using asynchronous B2B interfaces the message header (element //PurchaseOrderRequest/MessageHeader) should contain the following information:

1. ID
2. CreationDateTime
3. SenderParty referring to the business partner representing the sender (e.g. the buyer)
4. RecipientParty referring to the business partner representing the receiver (e.g. the company in ByD representing the seller)
5. BusinessScope referring to the sending process (e.g. Purchase Order Processing at Customer)
6. BusinessScope referring to the receiving process (e.g. Sales Order Processing)

The error message "Remote Master PC Code was not provided." is very likely caused by a missing business scope in the message header.

Please find below an example of a message header filled for interface SalesOrderProcessingOrderingIn:

<MessageHeader>
  <ID>1234</ID>
  <CreationDateTime>2017-01-16T18:52:00Z</CreationDateTime>
  <SenderParty>                                
    <!-- Business partner in ByD representing the buyer -->
    <!-- Standard ID scheme agency IDs: 009 GLN, 016 DUNS -->
    <StandardID schemeAgencyID="009">123456789</StandardID>
  </SenderParty>
  <RecipientParty> 
    <!-- Company in ByD representing the seller -->
    <StandardID schemeAgencyID="009">9876543210</StandardID>
  </RecipientParty>
  <BusinessScope>
    <!-- Type Code: 2 sending process, 3 receiving process -->
    <!-- ID: 97 Purchase Order Processing at Customer, 7 Sales Order Processing -->
    <TypeCode listAgencyID="310" listID="25201">2</TypeCode>
    <ID schemeAgencyID="310" schemeID="10555">97</ID>
  </BusinessScope>
  <BusinessScope>
    <TypeCode listAgencyID="310" listID="25201">3</TypeCode>
    <ID schemeAgencyID="310" schemeID="10555">7</ID>
  </BusinessScope>
</MessageHeader>

You find more information on ByD message headers in section "Message Header in Asynchronous Services" of the Webservice documentation on SAP Help forByD.

Best regards,
Knut