ListRouting schema, example, validation rules, validation stylesheet |
ListRouting type: ListRouting | |
The purpose of the ListRouting is to communicate one or more summary listings of Routing information to another business application component. This may be the result of a GetList request or it may be initiated by some other business event. |
ListRouting extends: BusinessObjectDocument | |||||||
Structure: |
![]() |
||||||
Elements: |
|
ListRoutingDataArea extends: DataArea | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
ListRouting Scenario Diagram |
List schema |
List type: List | |
The purpose of the LIST verb is to enable a business software component to respond to a GETLIST request or to proactively send a listing of summary information containing many instances of occurrences of data for a noun to one or more other business software components.The results of a LIST may then be used as is, or they may be used to select a specific instance of a document or entity in order to issue a detail GET request.Although BODs based on this verb do not commonly cause updates to occur, there may be times when the component receiving the LIST decides to use the information it receives to update. This is entirely the decision of the receiving software component and is not forbidden.The behavior of the LIST verb is quite straight forward with a few exceptions. The LIST response to any GETLIST request needs to read the request carefully to ensure the response is returning the requested Data Types. The LIST needs to ensure the response to the GETLIST does not exceed the maxItems value.The LIST needs to find the specific Field Identifiers that are used for the Field-Based Selection or Range-Based Selection and process them accordingly. The attributes associated with the LIST BODs are as follows: o rsstart attribute is a number that idicates the starting record for the section of the resulting set returned in the list message. This value should always match the rsstart value in the originating GetList BOD. o rscount attribute is a number that indicates the number of records returned in the message. The subsequent request for additional records should have a rsstart value of rscount + 1. o rstotal attribute is a number that indicates the total number of records in the result set. o rscomplete attribute is a Boolean that indicates that the list provided exhaust the possible values. o rsref attribute is a string that represents the implementation-specific result set identifier for subsequent requests. |
List extends: ConfirmableVerb | |||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||
Attributes: |
|
Routing schema |
Routing type: Routing | |
Routing is the description of all of the resources, steps, and activities associated with a path or routing associated with a manufacturing or production process. Typically, a routing contains people, machines, tooling, operations, and steps. |
Header type: RoutingHeader | |
AssignedOperationGroups type: OperationGroup | |
Information specifying a grouping of operations and their relationships. |
RouteOperation type: RouteOperation | |
Information specifying the operations and there order for the specified routing. |
PreviousOperation type: PreviousOperation | |
Information specifying the previous operation. This provides the immediate preceding operation of the current operation defined in RouteOperation. The RouteOperation of the operations of the potential first operations will not have an associated PreviousOperation, however all others must contain one. |
GroupMember type: GroupMember | |
Information specifying the occurrence of the operations within an OperationGroup. At least one occurrence of the GroupMember component is required for each occurrence of the OperationGroup component. Except for the request BODs which use the verbs Get and GetList. |
GroupMember | ||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
OperationGroup | ||||||||||||||||
In a manufacturing environment where a CNC Lathe or a Manual Lathe may be alternative operations used in the production of a finished good. In the example above the Manual Lathe OperationGroup Name would be Alternate OperationGroupType. |
||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
PreviousOperation extends: WIPOperationBase | ||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
RouteOperation extends: WIPOperationBase | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
Routing extends: Noun | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
RoutingHeader | ||||||||||||||||||||||||||||||||||
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 |