UpdateProductRequirement schema, example, validation rules, validation stylesheet |
UpdateProductRequirement type: UpdateProductRequirement | |
The purpose of the UpdateProductRequirement is to enable a business application such as Order Management to reserve a quantity of goods or services for a specific date and time. The business process scenario is the Order Management application interacting with the Available to Promise or Production application in order to determine availability of a product for the customer. This scenario is commonly referred to as Make to Order or Build to Order. The UpdateProductRequirement accomplishes this task in a two step process within this one request: 1. First the receiving business application checks to see if an item is available in sufficient quantity by a specific date and time. 2. The receiving business application then reserves that quantity of inventory for that specific date and time combination if the product is available. If the product requested is not available, The responding application may send one of two responses: 1. A ConfirmBOD to confirm the denial of the request. 2. A ShowProductAvailability to communicate an alternative product availability. This may be OrderItem, Date, or Quantity, or a combination of these. This may also be accompanied with a message in the Note field Identifier stating that this is an alternative. If the product requested is available: The responding application may send a ConfirmBOD to confirm the execution of the request. This BOD will likely cause updates to occur. This BOD may be used individually, or as part of a larger interface scenario. The GetProductAvailability and ShowProductAvailability may be used before an UpdateProductRequirement, but they are not required. |
UpdateProductRequirement extends: BusinessObjectDocument | |||||||
Structure: |
![]() |
||||||
Elements: |
|
UpdateProductRequirementDataArea extends: DataArea | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
UpdateProductRequirement Scenario Diagram |
Update schema |
Update type: Update | |
The Update verb is used to describe specific processing in a more fine-grained manner beyond add, change or delete processing. An example is the update of inspection information from one business application to another. The event is not adding a document, or changing fields per se, it is communicating the occurrence of an event as well as the corresponding data that accompanies the event. |
Update extends: Verb | |||||||
Structure: |
![]() |
||||||
Elements: |
|
UpdateExpressionCriteria | |||||||||||||||||
Structure: |
![]() |
||||||||||||||||
Elements: |
|
||||||||||||||||
Attributes: |
|
||||||||||||||||
Enumerations: |
|
ProductRequirement schema |
ProductRequirement type: ProductRequirementBase | |
Product Requirement is a request to reserve or allocate a specified quantity of a specified item. Typically, this requirement would be received by an inventory or production system. |
Verb Common Files |
Verb.xsd schema |
AcknowledgableVerb extends: ConfirmableVerb | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
AcknowledgementType restricts: xs:NMTOKEN | |||||||
Enumerations: |
|
ConfirmableVerb extends: Verb | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
ConfirmType restricts: xs:NMTOKEN | |||||||
Enumerations: |
|
Expression restricts: xs:string | |
ExpressionCriteria | |||||||||
Structure: |
![]() |
||||||||
Elements: |
|
||||||||
Attributes: |
|
RequestVerb extends: ConfirmableVerb | |||||||
Structure: |
![]() |
||||||
Elements: |
|
VerbBase.xsd schema |
Verb type: Verb | |
Verb | |
Structure: |
![]() |
Noun Common Files |
ProductRequirementBase.xsd schema |
ProductRequirementBase extends: Noun | |||||||||||||||||||||||||||||||||||||||||||
This is a base type that is used for any Product Requirement or Availability scenarios |
|||||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||||||||||||||
Elements: |
|