UNDT000007-SC2 SC Code List. Identifier The identification of a list of codes. Code List Identification Identifier string UNDT000007-SC3 SC Code List. Agency. Identifier An agency that maintains one or more lists of codes. Code List Agency Identifier string Defaults to the UN/EDIFACT data element 3055 code list. UNDT000007-SC4 SC Code List. Agency Name. Text The name of the agency that maintains the list of codes. Code List Agency Name Text string UNDT000007-SC5 SC Code List. Name. Text The name of a list of codes. Code List Name Text string UNDT000007-SC6 SC Code List. Version. Identifier The version of the list of codes. Code List Version Identifier string UNDT000007-SC7 SC Code. Name. Text The textual equivalent of the code content component. Code Name Text string UNDT000007-SC8 SC Language. Identifier The identifier of the language used in the code name. Language Identification Identifier string UNDT000007-SC9 SC Code List. Uniform Resource. Identifier The Uniform Resource Identifier that identifies where the code list is located. Code List Uniform Resource Identifier Identifier string UNDT000007-SC10 SC Code List Scheme. Uniform Resource. Identifier The Uniform Resource Identifier that identifies where the code list scheme is located. Code List Scheme Uniform Resource Identifier Identifier string Allows the adding of new requirements and the modification of previously established requirements through various Sync Indicator values. Customers can use PlanningSchedule to communicate demand requirement in three different ways. It can be as specific as the Item level or at the Commodity code level, which is higher than item. Furthermore, it can be required simply by functional specification via feature identifiers and values using the optional Data Type FeatureValueData. Is where the information that the BOD message carries is provided, in this case SyncPlanningSchedule. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (PlanningSchedule). Is the schema based inheritance for all BODs. The logical model would also include the DataArea. OAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on. Indicates the version of the given BOD defintion. Indicates whether this BOD is being sent in a "Test" or a "Production" mode. If the BOD is being sent in a test mode, it's information should not affect the business operation. However, if the BOD is sent in "Production" mode it is assumed that all test has been complete and the contents of the BOD are to affect the operation of the receiving business application(s). Indicates the language that the contents of the BOD is in unless otherwise stated. This Data Type is used to communicate a flexible bucket definition. The value of Identifier can be taken from predefined values such as Day, Week, etc. or it can hold a user defined identifier with a specific time period. In any case the actual time period and Identifier must be used. Represents the secondary packing code used to further identify the package of the product. Hmmm, where is the primary packing code? Identifies the sender of the given BOD instance Allows any digital Signatures to be added to the Instance of the BOD Instance in order to sign for any portion of the BOD content. Provides the structure to indicate a Date/Time period where the Time is provided with in the Start and Duration or EndDateTime. ReturnCriteria identifies the content that is to be returned, given query success. In essence, the expression here has the effect of filtering the part(s) of the found element(s) that are to be returned. ReturnCriteria plays no role in the query itself. That is handled as a match against the request BOD's noun exemplar. ReturnCriteria allows the sender of the BOD to indicate which information (down to the field level) is requested to be returned, given that the query has been successful in matching the exemplar to existing nouns. That is, in a GetListPurchaseOrder, if one or more PurchaseOrders with a TotalPrice = $1M were found, ReturnCriteria tells the BOD recipient which parts of the PurchaseOrder should be populated with content when the response (ShowPurchaseOrder) is formulated. The expressionLanguage indicates the expression language being used. In order for the ReturnCriteria expression to be evaluable by the BOD recipient, the recipient must be capable of processing and interpreting the specified expression language. XPath is the default, due to its ubiquity among XML processing technologies. The abstract Header type that is the basis for all non-statusable OAGIS Document Headers The abstract Line type that is the basis for all non-statusable OAGIS Document Lines TimePeriodABIEType is logically derived from UN/CEFACT TBG17 ABIE PeriodType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Idicates if the Item is reported theoretically (back-flushed) or if the ITEM is reported directly (actual) The ClassificationCodes that identify a single or hierarchical association of classifications. For example, Pump, Centrifugal would be represented by two Codes, the first one as Pump, the second as Centrifugal. The Sequence attribute of the Code identifies the hierarchical position of the identifier in the case of multi-level codes. The name attribute identifies the name of the corresponding classification level. Possible examples are ROOT, BRANCH, LEAF LocationABIEType is logically derived from UN/CEFACT TBG17 ABIE LocationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. HazardousMaterialABIEType is logically derived from UN/CEFACT TBG17 ABIE HazardousMaterialType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Is the tag and information of the new information to be passed. Is the name of the tag for the information being passed. Is the type of the information being passed in the NameValue. QDT000000 QDT Response_ Code. Type 1.0 Code Response StatusABIEType is logically derived from UN/CEFACT TBG17 ABIE StatusType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Extends the ItemBaseType to identify a set of Items along with their SerialNumbers and/or Lot information. ProjectABIEType is logically derived from UN/CEFACT TBG17 ABIE ProjectType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Indicate the type of project. QDT000000 QDT Description_ Text. Type 1.0 Text Description A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified. This is the ID assigned to the document by the creator of the document. Is the basis for Items. QDT000000 QDT Temperature_ Measure. Type 1.0 Measure Temperature QDT000000 QDT State_ Code. Type 1.0 Code State Identifies a unique serial number and/or lot number for an item The OAGIS CoordinateType allows the use of another coordinate system for the use within a warehousing and inventory environment and the geographic coordinat system. Address BaseType provides the information about the address or semantic address of an associated entity. DimensionABIEType is logically derived from UN/CEFACT TBG17 ABIE DimensionType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. ContactABIEType is logically derived from UN/CEFACT TBG17 ABIE ContactType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Contains the sequenced identifier for the associated component or noun. QDT000000 QDT Delivery Point_ Code. Type 1.0 A character string (letters, figures, or symbols) that for brevity and/or languange independence may be used to represent or replace a definitive value or text of an attribute together with relevant supplementary information. Code Delivery Point QDT000000 QDT Country Subdivision_ Code. Type 1.0 A character string (letters, figures, or symbols) that for brevity and/or languange independence may be used to represent or replace a definitive value or text of an attribute together with relevant supplementary information. Code Country Subdivision QDT000000 QDT Country_ Code. Type 1.0 Code Country PreferenceABIEType is logically derived from UN/CEFACT TBG17 ABIE PreferenceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. CommunicationABIEType is logically derived from UN/CEFACT TBG17 ABIE CommunicationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Since collaboration between a customer and a supplier can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate their current demand or supply schedule in response to what they received from the other party. Either party can indicate detailed exception descriptions along with reason code and action code to the other party why the original demand/supply requirements need to be adjusted using the optional component PlanningScheduleException . The purpose of the SyncPlanningSchedule is to communicate requirement information (part number, quantity, etc.) between a customer and their supplier on a regular basis, for example daily, weekly etc, or for a user-defined time bucket type definition (Component FexibileBucket) that is sent as part of this PlanningSchedule. SyncPlanningSchedule allows the adding of new requirements and the modification of previously established requirements. Customers can use this PlanningSchedule to communicate demand requirement in three different ways. It can be as specific as the Item level or at the Commodity code level, which is higher than item. Furthermore, it can be required simply by functional specification via feature identifiers and values using the optional component FeatureValue. The Sync verb is used when the owner of the data is passing or publishing that information or change in information to other software components. This is to be used when the receiver of the SyncBOD does not own the data. This verb is commonly used when mass changes are necessary or when a publish and subscribe mechanism is used in the integration architecture.The purposes of this verb include application integrity and ease of data entry for the business user by enabling a single point of input. Indicates a demand forecast sent from a customer to a supplier, or a supply schedule sent from a supplier to a customer. Provides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of. Provides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of. Header level information for the schedule. Line level information for the schedule. All time bucket definitions used within the schedule. Identifies characteristics and control identifiers that relate to the application that created the Business Object Document. The sender area can indicate the logical location of the application and/or database server, the application, and the task that was processing to create the BOD. is the date time stamp that the given instance of the Business Object Document was created. This date must not be modified during the life of the Business Object Document. If the BOD is to be signed the signature element is included, otherwise it is not. Signature supports any digital signature that maybe used by an implementation of OAGIS. The qualifyingAgency identifies the agency that provided the format for the signature. This element supports any digital signature specification that is available today and in the future. This is accomplished by not actually defining the content but by allowing the implementation to specify the digital signature to be used via an external XML Schema namespace declaration. The Signature element is defined to have any content from any other namespace. This allows the user to carry a digital signature in the xml instance of a BOD. The choice of which digital signature to use is left up to the user and their integration needs. The BODId provides a place to carry a Globally Unique Identifier (GUID) that will make each Business Object Document instance uniquely identifiable. This is a critical success factor to enable software developers to use the Globally Unique Identifier (GUID) to build the following services or capabilities: 1. Legally binding transactions, 2. Transaction logging, 3. Exception handling, 4. Re-sending, 5. Reporting, 6. Confirmations, 7. Security. Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS. This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document throught the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document. The Open Applications Group will make best efforts to quickly consider all proposed submissions.The USERAREA is always the last element in all components, except where the component has been extended inline. The customer's actual requested amount of the item to be shipped. The customer's actual requested amount of the item to be shipped. Represents the Properties or Features of the associated entity Additional detail for each line item. Exception detail for Detail or Lline information. Is the Identifiers of the given instance of an entity within the scope of the integration. The providedBy attribute identifies the party that provided or knows this party by the given identifier. Identifies a bucket defined above for the type of buckets the plan has requested. Examples of values for this field include Days, Weeks (Starting Monday for 5 Days), Calendar Months, Lunar Months (Starting Jan 1st 28 Days per period, Balance on Last Period), Quarters (Starting Jan 1st. 3 Calendar Months Each.) or some other user defined and named value. Identifies the Name of the object in which associated. An explicit period of time for the bucket. Identifies the previously received plan schedule that this new schedule is responding to as a reference. The typical scenario is a supplier uses a Sync PlanningSchedule or Sync ShipmentSchedule to respond to a customer demand schedule, and this will identify the customer demand schedule that this supplier previously received. The date and time is also used in identifying the previously received plan schedule that the new plan schedule is responding to. Note that the combination of document id, document date, and revision number can uniquely identify a plan schedule. DateType indicates whether the dates specified on the schedule are delivery based or shipment based. Dates specified on the schedule include FromDateTime and ToDateTime at Header and Line levels. ScheduleType indicates whether the PlanningSchedule is a demand schedule from a customer or a supply schedule from a supplier. For the supplier schedule to respond to the original demand schedule, the RespondingScheduleReference is used to identify the customer's original demand schedule that it is responding to. Indicates the time period in which the associated component is effective. Indicates whether the dates specified on the schedule are delivery based or shipment based. Valid values for this field include: - Ship - Deliver ScheduleType is a code or identifier that describes the specific schedule and can be used in a variety of contexts. When used in the context of employee, ScheduleType refers to the specific schedule for the employee or worker. When used in the context of a Schedule, ScheduleType indicates whether the Schedule is a demand schedule from a customer or a supply schedule from a supplier. Valid values for this context are: “Demand”, “Supplier” A generic Party for non-validated or application-validated parties. A work-around for situations where Schema-validation of Parties is not feasible or not desired. Identifies the ShipToParty for the document or the line. In a lot of cases, this is the same as the CustomerParty. In multi-organization purchasing, the CustomerParty may be different from the BuyerParty Indicates the type of demand requested. Examples of values for this field include: - Forecast - Firm - Authorization - Past Due - Shipment/Receipt - Other Is the manufacturing view of an Item where the complete detail of an Item is represented by the MasterItem. identifies the date on which engineering changes to the item or product is effective. Is the actual delivery date and time of the line item. The date and time that the associated object was received. Is the timestamp that indicates when the associated entity(ies) are shipped. Indicates the date and time an item was shipped. It is used to specify the last shipment date for the particular sequenced part. Indicates the actual amount shipped. It is used to specify the last quanity recieved for a particular sequenced part. Is the date time stamp of the last time any thing was received from this supplier. Indicates the quantity delivered. Is used to describe the quantity of item's, products or resources being budgeted, produced, purchased, received, sold, or used. Is the number of items that have been received for the associated entity. Is the quantity that is shipped. Identifyies the authorization level of the user or application that is sending the Business Object Document Message. This authorization level being recognized be the receiving system indicates what can be done on the receiving system(s). Identifies the location that shipped goods are to be loaded. Provides the Hazardous Material Code and description. Is the reference number associated with in-plant routing information. Identifies the Packaging information for a given item. Note: The UPC here is the UPC of the packaging for a given item. Indicates the priority or urgency of the associated entity. Identifies a project that is associated with the given component. Is a reference to the last Delivery received by the customer from the supplier. Is a reference to the last Shipment or ASN received by the customer from the supplier. Provides the logical location of the server and applications from which the Business Object Document originated. It can be used to establish a logical to physical mapping, however its use is optional. Each system or combination of systems should maintain an external central reference table containing the logical names or logical addresses of the application systems in the integration configuration. This enables the logical names to be mapped to the physical network addresses of the resources needed on the network. Note: The technical implementation of this Domain Naming Service is not dictated by this specification. This logical to physical mapping may be done at execution time by the application itself or by a middleware transport mechanism, depending on the integration architecture used. This provides for a simple but effective directory access capability while maintaining application independence from the physical location of those resources on the network Provides a finer level of control than Logical Identifier and represents the business application that issued the Business Object Document. Its use is optional. The Open Applications Group has not constructed the list of valid Component names. A suggestion for naming is to use the application component names used in the scenario diagrams in section two of OAGIS. Example Components may be Inventory, or Payroll. Describes the business event that initiated the need for the Business Object Document to be created. Its use is optional. Although the Task may differ depending on the specific implementation, it is important to enable drill back capability. Example Tasks may be Receipt or Adjustment. Enables the sending application to indicate the instance identifier of the event or task that caused the BOD to be created. This allows drill back from the BOD message into the sending application. The may be required in environments where an audit trail must be maintained for all transactions. Is an option controlled by the Sender business application. It is a request to the receiving application to send back a confirmation BOD to the sender. The confirmation Business Object Document may indicate the successful processing of the original Business Object Document or return error conditions if the original Business Object Document was unsuccessful. The confirmation request has the following valid values: Never - No confirmation Business Object Document requested OnError - OnError send back a confirmation Business Object Document only if an error has occurred Always - Always send a confirmation Business Object Document regardless Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective. Is the tag and information of the new information to be passed. Number of hours. Represents a list of codes that specify action to fix the exceptions. Examples of values for this field include: Reduce demand quantity Increase production. Represents a list of codes of the possible most common exceptions. Examples of values for this field include: - Late Sales Order or Forecast Demand - Shortage - Exceeds Capacity Identifies the reason for an activity The datetime on which the object was last modified The date that document was created within the system of record. Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system. Identifies the Activity that is associated to the Project in which the distribution is to be assigned.. An ActivityId cannot occur with out a ProjectId. Start timestamp indicating the starting point of the event. Indicates the duration of time as represented by ISO 8601. Where the value space is a six dimensional space where the coordinates designate the Gregorian year, month, day, hour, minute, and second. The number of seconds can include decimal digits to arbitary pecision. Is the ending timestamp of the event. Element for the communication of all codes. This is the DateTime the associated object is made effective Is the primary document id for the document associated. Is the alternate document id for the associated document. The Attachment represents binary data files that may be included within a BOD. These files replace the paper specifications and drawings attached to a BOD definition to clearly communicate design requirements. This Data Type is optional. Attachment usage is further defined by its position. Is the Code to indicate the status for the Noun or Component in which the Status Component occurs. Contains the set of possible identifiers for an associated Party. The location of a thing, as captured by an address (or addresses), GPS Coordinates, and/or in relation to other locations. Contacts are the point of communication with the given party. In the case of an organization it may be the requestioner, the buyer, customer service, etc. Identifies the Lot that a given Item Instance belongs to. Indicates the type of the object in which assoicated. Is the time in which the associated entity is actually in process. Indicates whether the ItemQuantity is a fixed size and does not scale along with the quantity of the BOM or Routing being produced Is the duration of time that is required to add to a manufacturing process to forecast availability of this Item. This is the percentage of the total quantity on the Bill of Material that is required to be available before the manufacturing process can begin Indicates whether the associated quatities are backflushed or not. Indicates if the associated quatities are reported as they happen. Indicates whether the related object is to be tracked Identifies the status of an item as a scrapped item Used to identify a Medical First Aid Guide (MFAG) for hazardous substance. Is the Technical name of the associated entity. The placard endorsement that is to be shown on shipping papers for hazardous materials. Can also be used for the number of the orange placard (lower part) require on transport. The placard notation that is to be shown on shipping papers for hazardous materials. Can also be used for the number of the orange placard (upper part) require on transport. Specifies the level of marine pollution for this hazardous substance. A code identifying the Inhalation Toxicity Hazard Zone for the hazardous substance, this is generally identfied by a government agency in the United States this is provided by the US Department of Transportation. Temperature of the associated entity. FlashpointTemperature is related to hazadous substances or goods, indicates the temperature at which the associated substance of goods become flammable, explossive or toxic.. The primary entry route by which the Hazardous Material gains access to the human body. Provides the dimensions of the associated component. Is the number of instances of the item in the unit of measure contained with in the package. Is the maximum number of instances of an item in the unit of measure that maybe contained within the package. Indicates when the status change occured. Allows an instance of an item to carry any radio frequency identifier (RFID) that maybe used by a supply chain. Unique serial number assigned to the given item instance by the manufacturer. This can be used in three ways: specify multiple serial numbers for a given lot, or specify multiple lots without serial numbers, or specify multiple serial numbers without a LotID. Typically, the parent element that uses LotSerial also provides the ability to provide a single lot number and serial number pair, which can be used for the cases where there are no multiple lots or serial numbers involved Is the maximum number of items that can be put into a lot for this Item. Is the minimum number of items that can be put into a lot for this Item, Is used with the MinimumLotSize and MaximumLotSize. It contains the multiplier between the minimum and maximum manufactured lot quantities. For example, if the maximum lot quantity is 10,000 and the minimum lot quantity is 1000, the lot size multiplier could be 1000. This means the Item may be manufactured in lot sizes starting at 1000 and going up to 10,000 by 1000 increments.For example, 1000, 2000, 3000, etc. A lot of 4500, would not be allowed under these constraints. The monetary value of the object in which the amount is associated Identifies the tamper-proof seal placed on a shipping container to prevent pilfering of the contents. Identifies the item number assigned to the type of goods for the purposes of freight classification and cost calculation. Is a unique identifier for the purpose of tracking an individual package or shipment. Is the revision of the semantically named document. The combination of the ID and its revision uniquely identifies the associated entity. Identifies if the Item is a Service This identifies the classification of an entity. An entity may be classified into mulitple groups for different reasons. Examples of Classification include Commodity Codes, Freight Classifications, Product Line classifications and so on. Suggested Values are COMMODITY, FREIGHT, PRODUCTLINE Identifies the specification of an entity. Identifies the Lot Identifiers of all of the lots that are contained in the associated set of items. Identifies the quantity of the associated service or item that is addresses by the component in which the quantity is associated. Identifier for a business or individual provided by the government. This maybe a FIIN, Social Security Number, or Drivers License Number to name a few. Identifier for business provided by Dun and Bradstreet. The Bank Identifier Code is a unique address which, in telecommunication messages, identifies precisely the financial institutions involved in financial transactions. Is the primary item Identifier associated with the given item within the scope of the given integration as provided by the Party or entity that has created this document instance. Is the identifier provided by the customer for the item. Is the identifier provided by Manufacturer for the Item. One example may be the model number. Is the identifier provided by the supplier for the item. Allows an instance of an item to have a UPC identifier associated. Allows an instance of an item to communicate the ElectronicProductCodeID that it was assigned. The ElectronicProductCodeID is one of the major RadioFrequency Identifiers used. Is the value and unit of measure in the z-axis in a thrre dimensional system. Examples of this maybe the Altitude in the case of a map of the world, or the height or shelf in a rack system in the case of a manufacturing or warehouse facility. Is the system in which the userid applies. Format Code indicates the format of the address. Examples are US Military, US Formatted Address, European Formatted Address etc. There is no intent to decode the address formats - these are informational only. No list of valid values exists or is proposed here. The name of the person or organization that the associated entity is intended. The name that the associated entity is sent by. The Number of the building or house on the street that identifies where to deliver mail. For example, Building 300 on Standards Parkway The building or house name on the street that identifies where to deliver mail The Street Name where the building/ house is located Identifies the apartment number or office suite. The floor where the housename is located Identifies a Post Office Box number Identifies the Dock or the Mail Stop or Lane or any other specific Delivery Point. Qualifies the further division of the City, example a city may have many districts or Boroughs. The type attribute identifies the type of this entity e.g. City, Borough etc, and there is a pre-defined list of types supported, with the ability to add new ones as necessary Identifies the town or the city Qualifies the further division of the Country. These may be Districts, Regions, States, Provinces etc. A possible list of values is as specified in ISO 3166-2. The type attribute identifies the type of this e.g. District, Region etc, and there is a pre-defined list of types supported, with the ability to add new ones as necessary Country in which the Address is in. A possible list of values is as specified in ISO 3166-2. Postal Code of the Address. Indicates the width of an object Indicates the length of an object Indicates the Height of an object Allows the data to be embedded directly into the BOD instance. Indicates the name of the File being referenced. Allows a reference to an ISBN. Identifies the type of the file type of the attachment. Specifies how big the file is. Is the title of the person. For example Dr.. Is the position or designation of the pesron with whom associated within the given organization. Examples are Director, Software Engineer, Purchasing Manager etc A text description of the responsibility of the associated entity. A value expressing the value of a Sequence. Identifies the channel in which the associated entity comes. Code identifying the usage of the contact point e.g. business, private, etc. The country dialing code for a communication number. The area dialing code for a communication number. The commication number, not including country dialing or area dialing codes. The extension of the assoicated communication number. The text that permits access to the electronic network of the associated communication number such as telephone network, for example 9, *70. Indicates that the associated entity preferrs HTML format. Is a message to the reader about the object associated. Common Free Form Text elements that occur together. Provides the Identifier(s) of the document being communicated. Uniquily identifies a Document within an organization. Typically there is only an ID for a document within one system. However, with the use of different business applications there maybe different ids assigned to the same document within an organization from the different systems and in the case of B2B transactions different businesses may have different Identifiers for the same document. This construct is designed to allow for these different identifications. Common References to DocumentReferences and Attachements A group that contains the identifier for the associated component or noun. Contain the ids for a given party. These ids may be assigned by multiple organizations. Contains the Item IDs for an associated item. Indicates the ID of the associated component or noun. QDT000000 QDT Month_ Date. Type 1.0 A particular point in the progression of time together with the relevant supplementary information. Provides the XML Schema simpleType that allows either just the Date or the Date and Time to be provided in the elements that are based on this type and/or types that use this as their base. Date Month