UpdateInspection schema, example, validation rules, validation stylesheet |
UpdateInspection type: UpdateInspection | |
The purpose of the UpdateInspection is to supply Inspection information for goods or services to another business application module. This BOD may is initiated by the sending system upon some event occurring. There are many possible business applications in several environments that may use this capability. For example; 1. A PurchaseOrder application could use this to send information to a Plant Data Collection application, or vice versa. 2. An MRP, Inventory, Purchasing or Manufacturing business application could use this to communicate inspection information. 3. A Laboratory Information System could send quality information to an Inventory application, 4. A Quality Control application could send information to an MRP, Inventory, or Purchasing application. |
UpdateInspection extends: BusinessObjectDocument | |||||||
Structure: |
![]() |
||||||
Elements: |
|
UpdateInspectionDataArea extends: DataArea | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
UpdateInspection 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: |
|
Inspection schema |
Inspection type: Inspection | |
Reports the inspection of items identifies the source document |
Result type: InspectionResult | |
Indicates the results of the inspection. |
Inspection extends: Noun | ||||||||||||||||||||||||||||||||||||||||
In some cases, the goods inspected may already be in inventory in a queue awaiting inspection. In this case the visibility to the PO may no longer be available. In which case the DeliveryReceipt reference must be used. This may also require an Inventory event to occur to ensure the status of the goods is updated in Inventory to reflect whether the goods are available for Inventory use after inspection. |
||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||||||||
Elements: |
|
InspectionResult | ||||||||||||||||||||||
This describes the reasons for rejecting or accepting the corresponding quantity |
||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||
Elements: |
|
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 |