GetRouting schema, example, validation rules, validation stylesheet |
GetRouting type: GetRouting | |
The purpose of the GetRouting is to communicate to a business application module or system a request for an existing Routing structure to be returned in a ShowRouting. |
GetRouting extends: BusinessObjectDocument | |||||||
Structure: |
![]() |
||||||
Elements: |
|
GetRoutingDataArea extends: DataArea | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
GetRouting Scenario Diagram |
Get schema |
Get type: Get | |
The GET verb is to communicate to a business software component a request for an existing piece of information to be returned. The GET may be paired with most of the nouns defined in the OAGIS specification.The response to this request is the SHOW verb. The behavior of a BOD with a GET verb is quite predictable across most of the nouns it may be paired with.The GET is designed to retrieve a single piece of information by using that information's primary retrieval field, or key field. The GET verb is not used to request several documents at once. The GETLIST verb is designed to achieve that purpose and will be covered in more detail later.Selection Criteria:There are two types of selection capabilities for most BOD's that use the GET verb.1) The first selection capability is called Field-Based Selection. Within a GET-based Business Object Document, the first Data Type that occurs in a specific BOD structure is commonly used to provide the Field-Based Selection criteria. This is always defined within the specific BOD and is commonly the required fields for that specific Data type.The Field-Based Selection enables the requester to provide a value or values (in the case of multiple required Field Identifiers), in the required fields. Then the responding component uses those values to find and return the requested information to the originating business software component.2) The second type of selection capability for GET-based BODs is called Data Type Selection. Data Type selection enables the requester to identify which Data Types within the noun are requested to be returned in the response. The use of this capability is described for each corresponding Data Type for all BODs that use the GET verb. The Data Types are identified for retrieval within the GET instance of a BOD by including the name of the Data Type in the meta data but without any Field Identifiers or Segments identified within the Data Type. This will signify to the responding application that all of the data that corresponds to that Data Type is to be included in the response.If the Data Type is not requested, the Data Type identifier is not included in the GET request and this will signify to the responding component that the Data Type is not to be returned. |
Get extends: RequestVerb | |||||||||
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 |