The ProcessMaintenanceOrder provides the ability to request an application/ system to create a MaintenanceOrder More information at: http://www.openapplications.org/oagis/9.
Is the schema based inheritance for all BODs. The logical model would also include the DataArea. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
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 More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
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 More information at: http://www.openapplications.org/oagis/9.
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). More information at: http://www.openapplications.org/oagis/9.
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.
More information at: http://www.openapplications.org/oagis/9.
<ccts:UniqueID> QDT000000</ccts:UniqueID>
<ccts:CategoryCode> QDT</ccts:CategoryCode>
<ccts:DictionaryEntryName> Month_ Date. Type</ccts:DictionaryEntryName>
<ccts:VersionID> 1.0</ccts:VersionID>
<ccts:DefinitionText> 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.</ccts:DefinitionText>
<ccts:RepresentationTermName> Date</ccts:RepresentationTermName>
<ccts:QualifierTerm> Month</ccts:QualifierTerm>
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. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
XML Instance Representation
<UserArea>
Allow any elements from any namespace (strict validation). [0..*]
The Process verb is used to request processing of the associated noun by the receiving application or business to party. In a typical external exchange scenario a Process BOD is considered to be a legally binding message. For example, if a customer sends a ProcessPurchaseOrder BOD to a supplier and the supplier acknowlegdes with a positive AcknowledgePurchaseOrder, then the customer is obligated to fullfil the agreement, unless of course other BODs are allowed to cancel or change the original order. More information at: http://www.openapplications.org/oagis/9.0.
Identifies with the ActionExpression the level by carrying a value of the expressionLanguage (this is typically XPath) within the BOD that the actionCode is to be performed. The ChangeStatus communicates just that the Change Status. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
A Maintenance Order is an order for a machine, building, tooling or fixed asset to be repaired or for preventitive maintenance to be performed. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
Is the Identifiers of the given instance of an entity within the scope of the integration. The schemaAgencyID attribute identifies the party that provided or knows this party by the given identifier.
More information at: http://www.openapplications.org/oagis/9.
Is the revision of the semantically named document. The combination of the ID and its revision uniquely identifies the associated entity. More information at: http://www.openapplications.org/oagis/9.
Is the Code to indicate the status for the Noun or Component in which the Status Component occurs. More information at: http://www.openapplications.org/oagis/9.
Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective. More information at: http://www.openapplications.org/oagis/9.
StatusABIEType is logically derived from UN/CEFACT TBG17 ABIE StatusType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. More information at: http://www.openapplications.org/oagis/9.
Provides the structure to indicate a Date/Time period where the Time is provided with in the Start and Duration or EndDateTime. More information at: http://www.openapplications.org/oagis/9.
TimePeriodABIEType is logically derived from UN/CEFACT TBG17 ABIE PeriodType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system. More information at: http://www.openapplications.org/oagis/9.
The Item identifiers that uniquily identify a given item. These identifiers may be specific to the party in which they make reference. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
Allows an instance of an item to communicate the ElectronicProductCodeID that it was assigned. The ElectronicProductCodeID is one of the major RadioFrequency Identifiers used. More information at: http://www.openapplications.org/oagis/9.
A Facility identifies a location within an entity. The facility may have sub-locators identified using a sequenced identification notation e.g. Warehouse A100 Sub-Location 11, Row R10 would be represented as an array of three Facility elements with values as A100, 11, R10, name attribute as Warehouse, Sub-Location and Row and sequence attribute as 1,2 and 3 respectively. More information at: http://www.openapplications.org/oagis/9.
Address BaseType provides the information about the address or semantic address of an associated entity. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
The Number of the building or house on the street that identifies where to deliver mail. For example, Building 300 on Standards Parkway More information at: http://www.openapplications.org/oagis/9.
<ccts:UniqueID> QDT000000</ccts:UniqueID>
<ccts:CategoryCode> QDT</ccts:CategoryCode>
<ccts:DictionaryEntryName> Delivery Point_ Code. Type</ccts:DictionaryEntryName>
<ccts:VersionID> 1.0</ccts:VersionID>
<ccts:DefinitionText> 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.</ccts:DefinitionText>
<ccts:RepresentationTermName> Code</ccts:RepresentationTermName>
<ccts:QualifierTerm> Delivery Point</ccts:QualifierTerm>
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 More information at: http://www.openapplications.org/oagis/9.
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 name attribute identifies the name 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 More information at: http://www.openapplications.org/oagis/9.
<ccts:UniqueID> QDT000000</ccts:UniqueID>
<ccts:CategoryCode> QDT</ccts:CategoryCode>
<ccts:DictionaryEntryName> Country Subdivision_ Code. Type</ccts:DictionaryEntryName>
<ccts:VersionID> 1.0</ccts:VersionID>
<ccts:DefinitionText> 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.</ccts:DefinitionText>
<ccts:RepresentationTermName> Code</ccts:RepresentationTermName>
<ccts:QualifierTerm> Country Subdivision</ccts:QualifierTerm>
PreferenceABIEType is logically derived from UN/CEFACT TBG17 ABIE PreferenceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. More information at: http://www.openapplications.org/oagis/9.
The OAGIS CoordinateType allows the use of another coordinate system for the use within a warehousing and inventory environment and the geographic coordinat system. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
Is the Lot and Setial numbers for the items contained in the associated component by identifing the number of items and the uniques serial number of those items that belong to a given Lot. More information at: http://www.openapplications.org/oagis/9.
Is used to describe the quantity of item's, products or resources being budgeted, produced, purchased, received, sold, or used. More information at: http://www.openapplications.org/oagis/9.
Identifies the Lot Identifiers of all of the lots that are contained in the associated set of items. More information at: http://www.openapplications.org/oagis/9.
Identifies the quantity of the associated service or item that is addresses by the component in which the quantity is associated. More information at: http://www.openapplications.org/oagis/9.
Allows an instance of an item to carry any radio frequency identifier (RFID) that maybe used by a supply chain. More information at: http://www.openapplications.org/oagis/9.
Indicates whether an item is active, inactive, or in other various states. Examples of values for this field include: Active, Inactive, Hold, Deleted, Obsolete More information at: http://www.openapplications.org/oagis/9.
Is the parent's serial number of the given item. This allows the traking of serialized components of an assembly. More information at: http://www.openapplications.org/oagis/9.
Is the ScheduleLineNumber of a particular item of interest for the given DocumentReference. The Line Number is of the primary DocumentId of the sender indicated by the DocumentId under DocumentIds. More information at: http://www.openapplications.org/oagis/9.
Is the SublineNumber of a particular item of interest for the given DocumentReference. The Line Number is of the primary DocumentId of the sender indicated by the DocumentId under DocumentIds. More information at: http://www.openapplications.org/oagis/9.
Identifies a grouping of entities together. An example usage may be a grouping of Operatations for a Routing. More information at: http://www.openapplications.org/oagis/9.
Identifies the sequence in which the associated entity is to occur with in a given operation, step or business process.. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
The Bank Identifier Code is a unique address which, in telecommunication messages, identifies precisely the financial institutions involved in financial transactions. More information at: http://www.openapplications.org/oagis/9.
The location of a thing, as captured by an address (or addresses), GPS Coordinates, and/or in relation to other locations. More information at: http://www.openapplications.org/oagis/9.
LocationABIEType is logically derived from UN/CEFACT TBG17 ABIE LocationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
ContactABIEType is logically derived from UN/CEFACT TBG17 ABIE ContactType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. More information at: http://www.openapplications.org/oagis/9.
Is the position or designation of the pesron with whom associated within the given organization. Examples are Director, Software Engineer, Purchasing Manager etc More information at: http://www.openapplications.org/oagis/9.
CommunicationABIEType is logically derived from UN/CEFACT TBG17 ABIE CommunicationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. More information at: http://www.openapplications.org/oagis/9.
The text that permits access to the electronic network of the associated communication number such as telephone network, for example 9, *70. More information at: http://www.openapplications.org/oagis/9.
Identifies the tamper-proof seal placed on a shipping container to prevent pilfering of the contents. More information at: http://www.openapplications.org/oagis/9.
Identifies the item number assigned to the type of goods for the purposes of freight classification and cost calculation. More information at: http://www.openapplications.org/oagis/9.
Identifies the Item associated with the Line or Detail of a transaction. The item provides the details of the generic Item component information. More information at: http://www.openapplications.org/oagis/9.
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 More information at: http://www.openapplications.org/oagis/9.
HazardousMaterialABIEType is logically derived from UN/CEFACT TBG17 ABIE
HazardousMaterialType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
TemperatureMeasureType is logically derived from UN/CEFACT TBG17 ABIE TemperatureType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file.
More information at: http://www.openapplications.org/oagis/9.
FlashpointTemperature is related to hazadous substances or goods, indicates the temperature at which the associated substance of goods become flammable, explossive or toxic.. More information at: http://www.openapplications.org/oagis/9.
Identifies the Packaging information for a given item.
Note: The UPC here is the UPC of the packaging for a given item. More information at: http://www.openapplications.org/oagis/9.
DimensionABIEType is logically derived from UN/CEFACT TBG17 ABIE DimensionType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. More information at: http://www.openapplications.org/oagis/9.
Is the maximum number of instances of an item in the unit of measure that maybe contained within the package. More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
Indicates the maintenance order that proceeded this order or from which this maintenance order originated after further investigation or work was performed. More information at: http://www.openapplications.org/oagis/9.
Indicates the timestamp when the machine failed or broke down such that it was no longer useable. More information at: http://www.openapplications.org/oagis/9.
Indicates whether an operation in a maintenance order have to be performed all at once or can be split into non-contiguous work segments. More information at: http://www.openapplications.org/oagis/9.
ProjectABIEType is logically derived from UN/CEFACT TBG17 ABIE ProjectType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file.
More information at: http://www.openapplications.org/oagis/9.
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. More information at: http://www.openapplications.org/oagis/9.
The accounting distribution information associated with a Business Object Document. The position of the Distribution within a Business Object Document provides the context and additional meaning. More information at: http://www.openapplications.org/oagis/9.
Identifies the percentage of the Line Price applicable to the distribution line. This is used to derive the Amount on the distribution line. More information at: http://www.openapplications.org/oagis/9.
Is the primary account classification within a chart of accounts. For example reveune, Fixed Asset, Land, Buildings, etc. More information at: http://www.openapplications.org/oagis/9.
This group identifies an entity within an enterprise from both the financial and operational perspective More information at: http://www.openapplications.org/oagis/9.
Identifies the agiven portion of an organization.
Some commonly defined Units are identified here.
These units are typically used to track financial data in reporting systems within an organization. Similar to Business Units, Organizational Units are only relevant within an enterprise More information at: http://www.openapplications.org/oagis/9.
The Cost Center is an accumulator of cost information that may be an organizational unit or area of responsibility. It is an organization code that allows a grouping of expenses and costs. More information at: http://www.openapplications.org/oagis/9.
The Profit Center is an accumulator of revenue information that may be an organizational unit or area of responsibility. A profit center can be used for internal management control. Profit centers can calculate operating profit using the cost-of-sales accounting and/or period accounting methods More information at: http://www.openapplications.org/oagis/9.
A G/L entity is the smallest organizational unit for which individual financial statements must be drawn up according to relevant commercial law.
It is normally the primary balancing segment of the GL Account structure. Typically, this is the owning entity for the transaction.
Synonyms are Business Unit, Fund, G/L Company, Joint Venture, Non-Profit Association Name More information at: http://www.openapplications.org/oagis/9.
This identifies resources that are required to perform the maintenance operation. Resource Requirements can be specified for the entire maintenance order or for each operation within the order More information at: http://www.openapplications.org/oagis/9.
PriceABIEType is logically derived from UN/CEFACT TBG17 ABIE PriceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. More information at: http://www.openapplications.org/oagis/9.
Indicates the cost or price of something represented as a value per a number of units. The price of eggs for example would be 1.29 per 1 dozen. More information at: http://www.openapplications.org/oagis/9.
Indicates the PerQuantity side of this Amount. Typically, this value is 1 with a uom of each, meaning that, e.g., a UnitPrice with the Amount 1.29 would be the price per each or simply $1.29 each. For pricing wire, the UnitPrice Amount might be $7.00 with a PerQuantity of 100 and a uom of LinearFeet, meaning the unit price would be $7 per 100 linear feet. More information at: http://www.openapplications.org/oagis/9.
The total cost of this project, as either an entered amount (no activity costing) or calculated as the sum of the activity costs.
This field is updated by the LoadProjectAccounting BOD.
More information at: http://www.openapplications.org/oagis/9.
Provides a list of category codes that identify the capabilities and features of the associated object. More information at: http://www.openapplications.org/oagis/9.
Represents the response to selection criteria that will be used to evaluate the Party. It may also represent capabilities the party offers which are not requested. Examples include quality certifications (ISO-9000), CAD data compatibility (Pro/E), manufacturing operations (JIT), company size, and performance ratings. More information at: http://www.openapplications.org/oagis/9.
Total amount of break time used by all Labour involved with the associated entity.
In cases where BreakTimeDuratation occurs along with BreakTimePeriod. BreakTimeDuration is being depricated in favor of BreakTimePeriod. More information at: http://www.openapplications.org/oagis/9.
Total time that the associated entity or entities was down during the associated task or operation.
In cases where DownTimeDuratation occurs along with DownTimePeriod. DownTimeDuration is being depricated in favor of DownTimePeriod. More information at: http://www.openapplications.org/oagis/9.
Identifies the safety related information associated with a machine, location or any other entity, or with performing an activity on any of the above entities More information at: http://www.openapplications.org/oagis/9.
Identifies a Hazard associated with a machine, location or any other entity and/or with performing an activity on any of the above entities More information at: http://www.openapplications.org/oagis/9.
Information on the problem, possible symptoms that may lead to the problem, and the cause and remedy for the problem.
Causes and/or remedies could be reported against a failure in a multi-level hierarchical reporting. For example, failure analysis could be recorded as follows; for failure A, causes P and Q are the factors and remedies X, Y and Z are to be taken. More information at: http://www.openapplications.org/oagis/9.
Is the identifier of a specific operation. Possible examples of use are in the Manufacturing Routing or the Maintenance Order. or WorkINProcessOperation. More information at: http://www.openapplications.org/oagis/9.