GetSequenceSchedule schema, example, validation rules, validation stylesheet |
GetSequenceSchedule type: GetSequenceSchedule | |
Commonly, the sequence schedule is generated by a work in process application and transmitted to an order or material planning application. The purpose of the GetSequenceSchedule is to enable a business applications module to request this SequenceSchedule information from another business application. The response to this BOD is ShowSequenceSchedule. |
GetSequenceSchedule extends: BusinessObjectDocument | |||||||
Structure: |
![]() |
||||||
Elements: |
|
GetSequenceScheduleDataArea extends: DataArea | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
GetSequenceSchedule 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: |
|
SequenceSchedule schema |
SequenceSchedule type: SequenceSchedule | |
A ShipTo Partner is required to represent the business partner that the goods or services are shipped to. Optionally, partner types SoldTo, BillTo and ShipFrom, and Supplier can be used. |
Header type: SequenceScheduleHeader | |
Header level informatoin for the schedule. |
Event type: SequenceScheduleEvent | |
Sequence Schedule Date and Time information associated with the Schedule Line. |
Line type: SequenceScheduleLine | |
Line level informatoin for the schedule within a particular event. |
SequenceSchedule extends: Noun | ||||||||||
A Sequence Schedule is used to indicate sequencial scheduling of ordered items in the manufacturing process. Commonly, the sequence schedule is generated by a work in process application and transmitted to an order or material planning application. |
||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
SequenceScheduleEvent | |||||||||||||||||||
The Event represents date and time information for the associated Schedule Line(s). The date and time the detail lines of the sequence schedule are required to be delivered. This allows Sequence Lines to be grouped together by an Event and minimizes the amount of potential redundant data. |
|||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||
Elements: |
|
SequenceScheduleHeader extends: DocumentHeader | |||||||||||||
Information that applies to the entire sequence schedule. |
|||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
SequenceScheduleLine extends: DocumentLine | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Represents the detail lines of the sequence schedule such as the item ordered along with quantity, delivery date and other schedule information. This Data Type is used only as a part of the SequenceScheduleEvent and cannot exit without it. Often the PurchaseOrder is referenced on a sequence schedule line. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 |
Document.xsd schema |
Document extends: Noun | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
DocumentHeader | ||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||
Elements: |
|
DocumentLine | |||||||
Structure: |
![]() |
||||||
Elements: |
|
DocumentOrderHeader restricts: DocumentHeader | |||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||
Elements: |
|