GetListProductionOrder schema, example, validation rules, validation stylesheet |
GetListProductionOrder type: GetListProductionOrder | |
The purpose of the GetListProductionOrder is to enable an business software component to request summary Production Order information from another business application module. The response to this request is the ListProductionOrder. The GetListProductionOrder also enables the retrieval of information across several documents by using selection fields. An example of this could be requesting all ProductionOrder Lines for a specific Item. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project. |
GetListProductionOrder extends: BusinessObjectDocument | |||||||
Structure: |
![]() |
||||||
Elements: |
|
GetListProductionOrderDataArea extends: DataArea | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
GetListProductionOrder Scenario Diagram |
GetList schema |
GetList type: GetList | |
The purpose of the GetList verb is to enable a business software component to request summary information for one or more occurrences of a specific noun from another business software component. The GetList may be paired with most of the nouns in the OAGIS specification.The response to this request is a BOD using the List verb. The GetList is designed to retrieve multiple occurrences of data such as all of the sales orders or all of the purchase orders within a requested range. It does not require an exact match of the key fields in order to retrieve information. It may use a range selection criteria with a "from" and "to" selection capability. This behavior is quite different from the Get verb, which is designed to retrieve a specific noun using a specific key field.The GetList verb also enables the retrieval of information across several documents by using selection fields. An example of this could be requesting all sales order lines for a specific item. This type of functionality is limited to the capabilities of the responding application and needs to be determined during the implementation project. More details on this capability will be described below. GetList attributes: o maxitems attribute is a number that indicates the number of maximum items to be returned. o rssave attribute is a Boolean flag that indicates whether the result set should be saved on the sending system if maxitems is exceeded. o rsstart attribute is a number of the starting record for the next section of the result set. If it is omitted, it is to be assumed the first of the maxitems. o rsref attribute is a string that represents the implementation-specific result set identifier for subsequent requests. Selection Criteria: There are two types of selection capabilities enabled by the BODs that use the GetList verb. 1) Field-Based Selection Allows the requesting system to ask for information that matches the data provided. It also allows the requestor to indicate the information that to be returned by specifying the ReturnCriteria indicated on the GetList Verb. 2) Range Selection Allows the requesting system to provide a range of values for known data. This is accomplished by providing two occurances of the Noun. The first occurance indicates the "From" the second occurance indicates the "To" occurance. Again the requestor can indicate the information that to be returned by specifying the ReturnCriteria indicated on the GetList Verb. |
GetList extends: RequestVerb | |||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||
Attributes: |
|
ProductionOrder schema |
ProductionOrder type: ProductionOrder | |
Production Order is a document requesting the manufacture of a specified product and quantity. |
Header type: ProductionOrderHeader | |
Information used to communicate the details of the production order requested to be initiated. |
Line type: ProductionOrderLine | |
Information used to communicate the individual items on the pre-determined Bill of Material structure. |
ProductionOrder extends: Noun | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
ProductionOrderHeader | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The LOTSERIAL in the header specifies the lot and/or serial information about the final assembly defined in this production order |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Elements: |
|
ProductionOrderLine | ||||||||||||||||||||||||||||||||||
The LOTSERIAL in the line specifies the lot and/or serial information about the individual items on the pre-determined Bill of Material structure |
||||||||||||||||||||||||||||||||||
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 |