You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

REST Web Service delivery method does not send documented default request headers or a message ID

in Supply Chain Planning and Collaboration

We are setting up outbound UBL 2.1 invoices (Peppol BIS Billing 3.0) from Receivables through Collaboration Messaging to a Peppol service provider. In a test environment we sent the same kind of invoice once with a SOAP delivery method and once with a REST Web Service delivery method, and captured what arrived at our own test receiver. The REST delivery arrived without any message metadata. Without a message ID and the B2B headers, the REST delivery method is not something we can run an enterprise B2B integration on, so we use SOAP V2 for now.

What the documentation says

"Define Delivery Methods" in Configuring and Managing B2B Messaging (26C and 26D) lists the default request headers for the REST Web Service delivery method: Content-Type, SenderId, SenderIdType, DocumentType, PartnerId and PartnerIdType. PartnerId "is required if you are using a service provider", and we use one.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!