Master data for supplierParty and customerParty, version 2.0.0

[larsolofsson]

How can master data be looked up for supplierParty and customerParty? No uuid are supplied for these parties in purchase order 2.0.0.

To get the time offset for local time supplied in latestAllowedDateTimeForChange, the customer needs to look up master data for supplierParty.

[patricekrakow]

We already have the supplierParty (non-required) property to the JSON payload so we can decouple the supplier and the domain name. But, this property is not used in the examples of our purchase order use case. I can change these examples to include the supplierParty (non-required) property to convey the message that we recommend the usage of it.

On the other hand, the customer is (only) represented by the OAuth 2.0 bearer token, we do have 1:1 mapping between the customer and the bearer token. If we also want to decouple the customer and the bearer token, we would indeed need to add a customerParty property to the JSON payload.

[patricekrakow]

I will add the customerParty as non-required properties to the following schemas:

• CreatePurchaseOrder
• GetPurchaseOrderById
• ListOfPurchaseOrders
• ModifyPurchaseOrder

I will also update the scenario C (Parties) of the master data use case to contain a customer party and a supplier party, so we can use their UUIDs into the scenarios of the purchase order use case. I will also update one scenario of the purchase order use case with the customerParty property.

We can consider this change as backward compatible and communicate it as an increment of the minor version (e.g. 2.0.0 -> 2.1.0).