GetConsumption schema, example, validation rules, validation stylesheet |
GetConsumption type: GetConsumption | |
The most common use of the GetConsumption is to request a buyer's usage information about an item or product for the supplier of such item or product. This BOD will not create or update either buyer's or supplier's inventory records. The receiver of the request is responsible to make effective use of this information. The BOD can be used in the following ways: (1) for a supplier of goods to request from the buyer, the consumptn status of goods (2) for a vendor to request from the retailer if retail sales of goods have been made; and (3) for inventory systems to request consumptn status from plant data collection and warehouse management systems. This is an outline of the business flow that this BOD supports: (1) Overall purchase, replenishment or vendor managed inventory agreement is in place and/or a Get Consumptn message is sent by the supplier. (2) Show Consumptn Message is returned the to supplier, distributor or third party logistics provider, that material has been consumed. This is done in response to events such as these (and/or the Get message), depending on implementation context: · Material is replenished to line side at manufacturing facitliy. · Material is assembled into final product. · Material is purchased and removed from facility by customer. (3) Supplier, distributor, third party logistics provider replenishes material, using information provided in the Show Consumptn message, the demand and shipment forecasts, and the terms of the overall purchase or vendor managed inventory agreement. |
GetConsumption extends: BusinessObjectDocument | |||||||
Structure: |
![]() |
||||||
Elements: |
|
GetConsumptionDataArea extends: DataArea | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
GetConsumption 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: |
|
Consumption schema |
Consumption type: Consumption | |
The process whereby a certain amount or quantity of inventory, resources or product is utilized which likely lead to the need for some form of replenishment. |
Header type: ConsumptionHeader | |
Line type: ConsumptionLine | |
ConsumptionLocation type: Location | |
Describes the line side shelf or retail shelf address and the route taken to move the items there. This is the location at which the items are consumed 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 ... |
Consumption extends: Noun | ||||||||||
This is used to share a consumer's usage information about an item or product with the supplier of the item or product |
||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
ConsumptionHeader | |||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||
Elements: |
|
ConsumptionLine | |||||||||||||||||||||||||||||||||||||||||||
This represents the detail lines of the consumption advice |
|||||||||||||||||||||||||||||||||||||||||||
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 |