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

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

UpdateInspectionDataArea extends: DataArea
Structure:
Elements:
Name Type Description
Inspection reference
Update reference

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:
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

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:
Name Type Description
AcceptedQuantity Quantity

This identifies the total quantity acceptedagainst this inspection line

A decimal value.

Attachments reference
DocumentId reference
DocumentReferences reference
InspectionDateTime DateTime

This is the datetime at which the inspection is carried out

ItemIds reference
LotSerial reference
ReasonCode ReasonCode

Identifies the reason code for tje inspectionl.

Used as a reason indicator for any type of business event or activity.

RejectedQuantity Quantity

This identifies the total quantity rejected against this inspection line. A further break-up of this quantity can be speciifed in the Rejection component

A decimal value.

Result reference
Site Location

Identifies location that the inspection was performed.

The replacement for SiteLevel, the original, flattened concept of numbered, sibling site levels. Location is intended to capture all of the location information for a given, named location. This could include more than one location descriptor, such as a PostalAddress and the GPS Coordinates. Location can also be described relative to other locations, by including a "Proximal Location" (a location nearby or surrounding/containing this location). In this fashion, locations can be identified and cascaded, e.g., the top floor of The Forrester Building which is at 400 Tech Square, right next to the Acamai Building: top floor The Forrester Building 400 Tech Square Next to the Acamai Building or in Bin 21 on Shelf 4 at Row 3B in Building 19: Bin 31 Shelf 4 Row 3B Building 19 ...

UserArea reference

InspectionResult

This describes the reasons for rejecting or accepting the corresponding quantity

Structure:
Elements:
Name Type Description
Description Description

Description of the inspection results.

Free-form text description of the Noun or Componenet in which the description occurs. The lang attribute indicates the language the description is in. Owner inidcates the user or entity that provided teh description..

ItemQuantity Quantity

This indicates the quantity rejected or accepted against the corresponding ReasonCode

A decimal value.

Note Note

Free-form note about the InspectionResult

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.

ReasonCode ReasonCode

This indicates the reason for rejecting or accepting the specific quantity

Used as a reason indicator for any type of business event or activity.

Status reference
UserArea reference

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