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:
Name Type Description
DataArea UpdateProductRequirementDataArea

Is where the information that the BOD message carries is provided, in this case UpdateProductRequirement. The information consists of a Verb and one or more Nouns. The verb (Update) indicates the action to be performed on the Noun (ProductRequirement).

UpdateProductRequirementDataArea extends: DataArea
Structure:
Elements:
Name Type Description
ProductRequirement reference
Update reference

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:
Name Type Description
UpdateCriteria UpdateExpressionCriteria

UpdateExpressionCriteria
Structure:
Elements:
Name Type Description
Expression
Attributes:
Name Type Usage Description
action required
expressionLanguage
lock xs:boolean
Enumerations:
Add
Change
Delete
Replace

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:
Name Type Usage Description
acknowledge AcknowledgementType

AcknowledgementType restricts: xs:NMTOKEN
Enumerations:
Always
Never
OnChange

ConfirmableVerb extends: Verb
Structure:
Attributes:
Name Type Usage Description
confirm ConfirmType

ConfirmType restricts: xs:NMTOKEN
Enumerations:
Always
Never
OnChange

Expression restricts: xs:string

ExpressionCriteria
Structure:
Elements:
Name Type Description
SelectExpression Expression

Allows the 1-n number of selection expressions for the information to be returned.

Attributes:
Name Type Usage Description
expressionLanguage xs:string optional

RequestVerb extends: ConfirmableVerb
Structure:
Elements:
Name Type Description
ReturnCriteria

Allows the initator of the BOD to indicate the information (down to the field level) that is requested to be returned. The expressionLanguage indicates the expression language being used.

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:
Name Type Description
AvailableDateTime DateTime
Business reference
DocumentReferences reference
EffectiveDateTime DateTime
GLEntity GLEntity

Is the GLEntity that owns the items now.

The primary balancing segment of the G/L Account structure. P and L statements are required at this level. A G/L entity is the smallest organizational unit for which individual financial statements must be drawn up according to relevant commercial law.

Synonyms: Business Unit, Fund, General Ledger Company, Joint Venture, Non-Profit Association Name

Item reference
ItemQuantity Quantity

A decimal value.

Note reference

A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified.

ProductLine ProductLine

This is a grouping used to represent something that is sold either internally or externally. It typically is a grouping of ITEMs. SYNONYMS: Commodity Product Family Kit

Categorization used to represent something that is sold either internally or externally. It typically is a grouping of ITEMs.PRODCTLINE replaces PRODUCT.SYNONYMS§ Commodity§ Product Family§ Kit

RequiredDateTime DateTime
Site reference

Identifies the location in which the Items are currently located.

SubstitutionAllowedInd Indicator

Indicates whether or not the Order Item can be substituted with a similar item.

Indicates if the semantic name is needed or not.

UserArea reference