Simple Types |
AccountingPeriodName restricts: xs:string | |
AcknowledgementCode restricts: xs:string | |||||||
Enumerations: |
|
AcknowledgementType restricts: xs:NMTOKEN | |||||||
Enumerations: |
|
AuthorizationCode restricts: xs:string | |
AuthorizationId restricts: xs:string | |
BucketName restricts: xs:string | |
BusinessArea restricts: xs:string | |
BusinessUnit restricts: xs:string | |
BusinessUnitId restricts: xs:string | |
ChargeClass restricts: xs:string | |
Type for former CHARGETYPE |
ChargeId restricts: Code | |
Classification restricts: xs:string | |
Code restricts: xs:string | |
Base type for a Code of any kind |
Commodity restricts: xs:string | |
Are codes that identify user-defined groupings of items. |
Confirmation restricts: xs:string | |||||||||||||
Enumerations: |
|
ConfirmType restricts: xs:NMTOKEN | |||||||
Enumerations: |
|
ControlType restricts: Type | |
Describes the type type of control used for the associated component. |
CostCenter restricts: xs:string | |
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. |
CostType restricts: xs:string | |||||||||||||
Is the methodology by which the value of an item is determined. Values are: Standard Moving Average LIFO - For last in first out. FIFO - For first in first out. |
|||||||||||||
Enumerations: |
|
Country restricts: xs:string | |
Standard values from ISO 3166-3:1999 Part 1 Codes for the representation of names of countries and their subdivisions - Part 1: Country codes |
Currency restricts: xs:string | |
CurrencyEnum restricts: xs:string | |||||||||||||||||||||||||||||||||||
Original Author: Roger Costello www.xfront.com Standard values from ISO 4217:2001 Codes for the representation of currencies and funds |
|||||||||||||||||||||||||||||||||||
Enumerations: |
|
Date restricts: xs:date | |
DateTime restricts: xs:dateTime | |
DateTimeAny | |
DebitCredit restricts: xs:string | |||||
Enumerations: |
|
Department restricts: xs:string | |
Represents a component of the enterprise, usually an organizational unit lower than division.For a commercial organization, the department is a lower level to which individuals may be assigned. This may not apply in some organizations such as Public Sectors.It is an organizational unit of the G/L Entity. It can be an element of the G/L account structure that represents a level of an organization. |
DistributionCenter restricts: xs:string | |
Division restricts: xs:string | |
Represents a component of the enterprise. Typically, division is the organizational unit between the GL Entity and the department. This may be used to capture revenue and/or cost. |
Duration restricts: xs:duration | |
EMailAddress restricts: xs:string | |
Format based on ? |
Encoding | |
EncodingBase restricts: xs:string | |||||||||
The standard set of encoding types from ??? |
|||||||||
Enumerations: |
|
Expression restricts: xs:string | |
Factor restricts: xs:float | |
FreightClass restricts: xs:string | |
Qualifies goods for purposes of freight cost calculation. An example would the qualifications used by National Motor Freight Carriers. EXAMPLES National Motor Freight Carriers (NMFC) Class Code Based on an evaluation of density, stowability, ease of handling and liability, the commodities are grouped into one of 18 classes. |
FreightTerms restricts: xs:string | |
Describes how the freight cost for a shipment of goods should be billed. EXAMPLES: Prepaid, Collect, Third Party, Prepaid and Add, Consignee Billed |
Fund restricts: xs:string | |
Processing Note: In some applications, the complete identification of this value may require multiple attributes. |
Geography restricts: xs:string | |
Is the physical or logical regions that are often used in sales reporting may be used to track cost of goods sold. |
GPSSystemType restricts: xs:string | |
Indicator restricts: xs:boolean | |
Indicates if the semantic name is needed or not. |
InvoiceType restricts: xs:string | |||||||
The type of invoice |
|||||||
Enumerations: |
|
ISBN restricts: xs:string | |
Format based on ISO 2108:1992 Information and documentation International standard book numbering (ISBN) |
IssueType restricts: xs:string | |
ItemType restricts: Type | |
JobCode restricts: Code | |
JounrnalEntryId restricts: xs:string | |
Kanban restricts: Code | |
Is the reference number associated with in-plant routing information. |
KindOfResource restricts: xs:string | |
Latitude restricts: xs:string | |
LedgerId restricts: xs:string | |
LicenseType restricts: xs:string | |||||
Enumerations: |
|
LineNumber restricts: xs:string | |
Identifies the instance of a Line within a given document. |
LoadingDockCode restricts: Code | |
LocationId restricts: xs:string | |
LogicalId restricts: xs:string | |
Longitude restricts: xs:string | |
LotName restricts: xs:string | |
LotNumberSpecification restricts: xs:string | |
MachineClassification restricts: Classification | |
MachineId restricts: xs:string | |
ManufacturingReportingFlag restricts: xs:string | |||||
Identifies whether an ITEM is reported theoretically (back-flushed) or if the ITEM is reported directly (actual). |
|||||
Enumerations: |
|
MessageType restricts: xs:string | |
OperationSequenceCode restricts: SequenceCode | |
Is the sequence code associated with a operation. |
OperationType restricts: xs:string | |||||||
Is used to indicate how the rates are specified. Valid values are: - Standard = An operation that has a rate specified as "quantity per unit of time". - Fixed = A duration operation that takes a specific amount of time regardless of thevquantity being processed. - Batch = An operation type that has a fixed amount of time for a given batch or partial batch. |
|||||||
Enumerations: |
|
OrganizationalUnitId restricts: xs:string | |
OrganizationalUnitName restricts: xs:string | |
OwnershipCode restricts: Code | |
Idenifies who owns the associated entity. |
PackingCode restricts: xs:string | |
PackingMaterial restricts: xs:string | |
PaymentMethod restricts: xs:string | |||||||||||
Standard values from ISO 10962:2001? Securities and related financial instruments - Classification of Financial Instruments (CFI code) |
|||||||||||
Enumerations: |
|
PO restricts: xs:string | |
Position restricts: xs:string | |
PostalCode restricts: xs:string | |
A local postal code such as US Zipcode. |
Preference restricts: xs:string | |
Identifies the preference. |
Priority restricts: xs:string | |
ProductLine restricts: Code | |
Categorization used to represent something that is sold either internally or externally. It typically is a grouping of ITEMs.PRODCTLINE replaces PRODUCT.SYNONYMS§ Commodity§ Product Family§ Kit |
ProfitCenter restricts: xs:string | |
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. |
ProjectActivityId restricts: Code | |
The id for an accounting project's activity. |
ProjectActivityStatus restricts: xs:string | |
The status descriptor for an accounting project's activity. |
ProjectActivityType restricts: xs:string | |
ProjectActivityWorkEffort restricts: xs:string | |
ProjectId restricts: xs:string | |
The unique identifier for an accounting project. |
ProjectResource restricts: Code | |
ProjectStatus restricts: xs:string | |
The status descriptor for an accounting project. |
ProjectTransactionType restricts: xs:string | |
The project accounting classification of the transactions. EXAMPLES: Billed, Cash, Cost, Revenue |
PurchasingEntityCode restricts: Code | |
Rating restricts: xs:string | |||||||
Business Party ratings. |
|||||||
Enumerations: |
|
ReasonCode restricts: Code | |
Used as a reason indicator for any type of business event or activity. |
ReferenceId restricts: xs:string | |
Relationship restricts: xs:string | |
Remittance restricts: Code | |
A reference identifier to print on remittance advice, for example, supplier invoice number. |
Restriction restricts: xs:string | |
SequenceCode restricts: Code | |
SerialNumber restricts: xs:string | |
SimpleId restricts: xs:string | |
SpatialRelationshipDescriptor restricts: xs:string | |
The word used as a binder or connector to describe the relationship of the two locations. Typical values include: on, in, on top of, under, above, adjacent to, cattycorner, down the street from, etc. |
StepType restricts: Type | |
Identifies the type of step with in an Operation. (typically am Manufacturing Operation). |
Tag restricts: xs:string | |
Task restricts: xs:string | |
TaxWithholdingExempt restricts: xs:boolean | |
TelephoneNumber restricts: xs:string | |
Format based on canonical form +### (###) ####### |
TemperatureScale restricts: xs:string | |||||||
The possible temperature scales. |
|||||||
Enumerations: |
|
Time restricts: xs:time | |
ToolClassification restricts: Classification | |
ToolId restricts: xs:string | |
TransferType restricts: xs:string | |||||
Is used to describe the item transfer. |
|||||
Enumerations: |
|
TransportationTerms restricts: xs:string | |
Is a contractual code used to describe the point where delivery occurs (goods ownership is transferred) in a contract of sale. It identifies the rights and obligations of each partner (supplier, carrier and customer) in the transaction and may specify the requirements to assume ownership (i.e. paying for the cost of the goods and/or transportation). The United Nations Trade Facilitation Information Exchange (UN/TraFIX) has established the following codes (INCOTERMS 1990) for use in international trade to Europe, Asia and the Pacific. (See http://www.unece.org/trade/rec/rec05en.htm). These terms may also be found in the United States Uniform Commercial Code (UCC). EXAMPLES§ EXW – Ex Works … (named place) FCA – Free Carrier … (named place) FAS – Free Along Ship … (named port of shipment) FOB – Free On Board … (named port of shipment) CFR – Cost and Freight … (named port of destination) CIF – Cost, Insurance and Freight … (named port of destination) CPT – Carriage Paid To … (named place of destination) CIP – Carriage and Insurance Paid to … (named place of destination) DAF – Delivered At Frontier … (named place) DES – Delivered Ex Ship … (named port of destination) DEQ – Delivered Ex Quay (Duty Paid) … (named port of destination) DDU – Delivered Duty Unpaid … (named place of destination) DDP – Delivered Duty Paid … (named place of destination) |
TransportationType restricts: xs:string | |
Type restricts: xs:string | |
UOM restricts: xs:NMTOKEN | |
Standard values from ISO / SI ???? |
UOMType restricts: Type | |
URI restricts: xs:anyURI | |
UserId restricts: xs:string | |
The user’s enterprise-wide identifier. It is also known as the user code. SYNONYMS: Operator ID |
ValueClass restricts: xs:string | |
Is a grouping used to determine the General Ledger accounting effect. These are user defined values, with the exception of the values TOTAL, MATERIAL, LABOR, BURDEN, OVERHEAD, SUBCONTRACT. |
WorkCenter restricts: xs:string | |
Year restricts: xs:gYear | |
Complex Types |
AccountingPeriod extends: TimePeriodAny | |||||||
The accounting period the document is to post within. The period is within a fiscal year to which a business transaction is assigned. |
|||||||
Structure: |
![]() |
||||||
Elements: |
|
AcknowledgableVerb extends: ConfirmableVerb | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
AcknowledgementDetail extends: Status | |
Structure: |
![]() |
Address extends: PostalAddressBase | ||||||||||||||||||||||
Address, |
||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||
Elements: |
|
Addresses | |||||||
Structure: |
![]() |
||||||
Elements: |
|
AddressId | |||||||||
An Address specific identifier type. |
|||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
Allowance | |||||||||||||||||||||||||
Identifies a type of allowance on order related BODs |
|||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||
Elements: |
|
AlternatePartyIds | |||||||
Structure: |
![]() |
||||||
Elements: |
|
Amount | |||||||||
Simple content with the currency as an attrbute |
|||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
AmountPerQuantity | |||||||||||||
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. |
|||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
Amounts | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
ApplicationArea | |||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||
Elements: |
|
Attachment | |||||||||||||||||||||||||||||||||||||
Attachment allows supporting documents to be attached to the BOD. This is for reference and management of binary/non-XML documents such as spreadsheets, CAD files, graphics, etc. Defines information about the attachement which may be inline, a MIME part or an external URI |
|||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||||||||
Elements: |
|
||||||||||||||||||||||||||||||||||||
Attributes: |
|
Attachments | |||||||
Structure: |
![]() |
||||||
Elements: |
|
AuthorizationType | |||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||
Elements: |
|
BOMDocumentReference extends: DocumentReference | ||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
BusinessObjectDocument | |||||||||||||||||
Structure: |
![]() |
||||||||||||||||
Elements: |
|
||||||||||||||||
Attributes: |
|
||||||||||||||||
Enumerations: |
|
Charge | ||||||||||||||||||||||
A charge identifies and monetary amount that must be paid. |
||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||
Elements: |
|
Charges | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
ConfirmableVerb extends: Verb | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
Contact | ||||||||||||||||||||||||||||
A business Party contact is a person and has a specific role. |
||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||
Elements: |
|
Contacts | |||||||
Structure: |
![]() |
||||||
Elements: |
|
CrossReferenceItemIds | |||||||
Structure: |
![]() |
||||||
Elements: |
|
DataArea | |
Is where the information that the message carries is provided. This is done by using the Verb which indicates the action to be performed on the Noun and 1 or more Nouns, which is the object that the action is to be performed. |
|
Structure: |
![]() |
DatePeriod | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
||||||||||||
Attributes: |
|
Dependences | |
Structure: |
![]() |
Description | |||||||||
Free-form text description of the Noun or Componenet in which the description occurs. The lang attribute indicates the language the description is in. Owner inidcates the user or entity that provided teh description.. |
|||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
Disposition extends: Status | |
Determines the receipt routing of an item or part. Examples of values include: Customer consignment Inspection Vendor consignment Blocked Bonded User defined SYNONYMS Receipt Routing Material Status Material Condition Code |
|
Structure: |
![]() |
Distribution | |||||||||||||||||||
A distribution identifies how monetary amounts are distributed accross an organization. |
|||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||
Elements: |
|
DocumentIds | |||||||
Structure: |
![]() |
||||||
Elements: |
|
DocumentIdType | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
DocumentReference | |
Identifies another document within the scope of the OAGIS specification, such as a PurchaseOrder or Invoice that maybe associated with a particular Business Object Document. |
|
Structure: |
![]() |
DocumentReferences | |||||||
Structure: |
![]() |
||||||
Elements: |
|
EmbeddedData | |||||||||
Holds the contents of an inline attachment. |
|||||||||
Structure: |
![]() |
||||||||
Elements: |
|
||||||||
Attributes: |
|
Employee | |||||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||||||||||||||
Elements: |
|
EmployeeAssignment | ||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||
Elements: |
|
EmployeeCategory | |
Structure: |
![]() |
EmployeeId | |
An Employee specific Identifier |
|
Structure: |
![]() |
EmployeeQualification | ||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||
Elements: |
|
ExpressionCriteria | |||||||||
Structure: |
![]() |
||||||||
Elements: |
|
||||||||
Attributes: |
|
FeatureValue extends: NameValueBase | ||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||
Elements: |
|
FunctionalAmount | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
GenericDocumentReference extends: DocumentReference | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
GenericIdType extends: DocumentIdType | |||||||
Structure: |
![]() |
||||||
Elements: |
|
GLAccount | |
GL Account is an entry in the GL chart of accounts. It is the "what", not the "who" or "where". Examples Include: Assets, Office Supplies, Revenues, Salaries, Travel SYNONYMS: Account Number, GL Natural Account, Object Account |
|
Structure: |
![]() |
GLEntity | |
The primary balancing segment of the G/L Account structure. P and L statements are required at this level. A G/L entity is the smallest organizational unit for which individual financial statements must be drawn up according to relevant commercial law. Synonyms: Business Unit, Fund, General Ledger Company, Joint Venture, Non-Profit Association Name |
|
Structure: |
![]() |
GPSCoordinates | ||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
Hazard extends: SafetyBase | ||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
HazardousItem | |||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||
Elements: |
|
HazardousMaterial | |||||||||||||
Provides the Hazardous Material Code and description. |
|||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
||||||||||||
Attributes: |
|
Id | |
Generic identifier type with open qualifyingAgency. |
|
Structure: |
![]() |
InventoryLocation | |
This identifies the item being transferred and the location. |
|
Structure: |
![]() |
Item | ||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||
Elements: |
|
ItemCategoryId | |
Structure: |
![]() |
ItemData | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Elements: |
|
ItemId | |||||||||
Identifies Item code. This can be a UPC or an EAN or a company assigned Id. Along with a revision number of the Item. |
|||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
ItemIdBase | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
ItemIds | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
ItemIdType extends: ItemIdBase | |||||||
Structure: |
![]() |
||||||
Elements: |
|
ItemReference extends: ResourceReference | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
ItemResource extends: Resource | |||||||
Structure: |
![]() |
||||||
Elements: |
|
LaborResource extends: Resource | |||||||
Structure: |
![]() |
||||||
Elements: |
|
LedgerEvent | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
License | |||||||||
Indicates whether a license is need for a given transaction. |
|||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
LingualString | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
Location extends: Noun | ||||||||||||||||||||||||||||
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 ... |
||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||
Elements: |
|
LocationCode | |
Similiar to Warehouse, DockId... LoadPoint would be Geographic area |
|
Structure: |
![]() |
Lot | ||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
LotSerial | |||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||
Elements: |
|
Machine extends: ResourceReference | |||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||
Elements: |
|
MachineResource extends: Resource | |||||||
Structure: |
![]() |
||||||
Elements: |
|
Message | |||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||
Elements: |
|
MfgDocumentReferences extends: DocumentReference | |||||||
Structure: |
![]() |
||||||
Elements: |
|
Name | |
Structure: |
![]() |
NameValue extends: NameValueBase | |||||||
Structure: |
![]() |
||||||
Elements: |
|
NameValueBase | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
NameValuePair | |||||||||||||
Is the tag and information of the new information to be passed. |
|||||||||||||
Structure: |
![]() |
||||||||||||
Attributes: |
|
Note | |||||||||||||
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. |
|||||||||||||
Structure: |
![]() |
||||||||||||
Attributes: |
|
Noun | |
Structure: |
![]() |
Operation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Elements: |
|
OperationGroupType | |
Is the operational grouping type. Examples: Alternate – any of these may be used, Parallel – non-sequential – all must be done but order does not matter, Sequential – these items must be done one after the other and time is critical |
|
Structure: |
![]() |
OperationId | |
Uniquly identifies an operation. |
|
Structure: |
![]() |
OperationName | |
Is the formal name of a Manufacturing Shop Floor Operation. |
|
Structure: |
![]() |
OrderDocumentReference extends: DocumentReference | ||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||
Elements: |
|
OrderItem | |||||||||||||||||||||||||||||||||||||||||||||||||
Provides information on the Orderable Item. When associated with an order like a Purchase Order, it identifies the item being ordered at the associated Line. |
|||||||||||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||
Elements: |
|
OrderStatus | ||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
|||||||||||||||
Attributes: |
|
|||||||||||||||
Enumerations: |
|
OrganizationalUnit | |||||||||||||||||||
A fully generic means of identifying an organizational unit. Can be an actual business unit (at any level) or an area of responsibility. Each is described with respect to others, via the ProximalUnit construct. |
|||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||
Elements: |
|
Packaging | ||||||||||||||||||||||||||||||||||
Identifies the Packaging information for a given item. Note: The UPC here is the UPC of the packaging for a given item. |
||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||
Elements: |
|
Parties | |||||||
Structure: |
![]() |
||||||
Elements: |
|
PartyAssignedItemId extends: ItemIdType | |||||||
Identifies an Items identifier that has been assigned by another Party. |
|||||||
Structure: |
![]() |
||||||
Elements: |
|
PartyAssignedPartyId extends: PartyIdType | |||||||
PartyQualifiedPartyId - the type of any [Party]PartyId, such as BillToPartyId. |
|||||||
Structure: |
![]() |
||||||
Elements: |
|
PartyBase extends: Noun | |||||||||||||
A mininmal Party type, as root to Party subst group type hierarchy |
|||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
||||||||||||
Attributes: |
|
PartyDocumentId extends: DocumentIdType | |||||||
Document specific identifier type. |
|||||||
Structure: |
![]() |
||||||
Elements: |
|
PartyGenericIdType extends: GenericIdType | |||||||
Structure: |
![]() |
||||||
Elements: |
|
PartyId | |
Structure: |
![]() |
PartyIdAny | |
The abstracty type for the head element of a PartyId substitution group. Must be compatible with all derivations. |
|
Structure: |
![]() |
PartyIdType | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
PartyInstitutional extends: PartyBase | ||||||||||||||||||||||||||||||||||||||||||||||||||||
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
||||||||||||||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||
Elements: |
|
PartyProductionOrderIdType extends: ProductionOrderIdType | |||||||
Structure: |
![]() |
||||||
Elements: |
|
PartyReference | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
PartyReferences | |||||||
Structure: |
![]() |
||||||
Elements: |
|
PartyRouteIdType extends: RouteIdType | |||||||
Structure: |
![]() |
||||||
Elements: |
|
PaymentTerms | |||||||||||||||||||||||||||||||||||||
Identifies the payment terms for an Order or Invoice. Supports the abiility to specify an absolute due date, a number of days from a start daye, a percent discount or an absolute discount. A common term like "Net30Days" is explicitly code as either a calculated DueDateTime or a PaymentTermsDateTime and NumberOfDays. |
|||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||||||||
Elements: |
|
Percent | |
Indicates the percentage. |
|
Structure: |
![]() |
Period | |
Structure: |
![]() |
Person | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
PersonCode | |
Structure: |
![]() |
PersonName | ||||||||||||||||||||||||||||
Full specification for a persons name. |
||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||
Elements: |
|
PostalAddress extends: PostalAddressBase | |||||||
Structure: |
![]() |
||||||
Elements: |
|
PostalAddressBase | |||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||
Elements: |
|
Precaution extends: Safety | |
Structure: |
![]() |
PrimaryDocumentId | |||||||
Structure: |
![]() |
||||||
Elements: |
|
ProductionOrderDocumentReference extends: DocumentReference | ||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||
Elements: |
|
ProductionOrderIdType extends: DocumentIdType | |||||||
Structure: |
![]() |
||||||
Elements: |
|
Project extends: Noun | ||||||||||||||||||||||||||||||||||||||||
A set of tasks with the following attributes: a singular purpose, a start and end date, those that accumulate costs, and those that may have materials and overhead. SYNONYMS: Job, Process Model, Program, Work Breakdown Structure (WBS) element |
||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||||||||
Elements: |
|
ProjectActivity | ||||||||||||||||||||||
The specific business process or task within a project. For example, billing, receiving or preparing purchase orders. |
||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||
Elements: |
|
ProjectResourceCategory | |
The categorization of project resources into classes, subclasses, etc., such as Labor, Material, Equipment |
|
Structure: |
![]() |
ProximalLocation | |||||||||||||
Reflects the relationship of a thing to a location, using a "binder" and a location. If a Part is located "in Bin 23", the binder is "in" and the location is "Bin 23". |
|||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
QualifiedResource | ||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||
Elements: |
|
Quantity | |||||||||
A decimal value. |
|||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
Reason | |||||||||
A reason indicator for any type of business event or activity with optional code attribute. |
|||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
RelatedUnitType | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
remAuthorization | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
RequestVerb extends: ConfirmableVerb | |||||||
Structure: |
![]() |
||||||
Elements: |
|
Resource | |
An abstract type describing the allocation of persons, equipment or materials, likely in a manufacturing environment. Pattern should be: Id, Class/Category, Required Quantities AW: Empty for now, if the xs:all is robust in the future may want to place common Resource fields here- mdf: Really shouldn't use group here - harder to extend. But if the resource has to come first... |
|
Structure: |
![]() |
ResourceReference extends: Resource | |
Structure: |
![]() |
Resources | |||||||
AW: In the future xs:All would be very helpful; still unbounded works here AW: not using Subs group with Resource so names can be local |
|||||||
Structure: |
![]() |
||||||
Elements: |
|
Revision | |
Is the revision code that can be associated with an Item, an order, a Bill of Material. The revision code indicates that the say item has been modified or updated in some way. |
|
Structure: |
![]() |
RouteCode | |
Structure: |
![]() |
RouteDocumentReference extends: DocumentReference | ||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
RouteIdType extends: DocumentIdType | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
Safety extends: SafetyBase | |||||||
Safety Information related to the work. This may be Hazards or Precautions |
|||||||
Structure: |
![]() |
||||||
Elements: |
|
SafetyBase | ||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
SalesOrganization | |
Idenitifies the SalesOrganizations. |
|
Structure: |
![]() |
SalesPersonCode | |
Structure: |
![]() |
Sender | ||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||
Elements: |
|
ServiceLevel | |
Structure: |
![]() |
ShippingMaterial | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
Signature | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
Someone | ||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
StateChange | |||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||
Elements: |
|
Status | ||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
Step | |||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||
Elements: |
|
StepId | |
Uniquily identifies the Step of an Operation. (typically am Manufacturing Operation). |
|
Structure: |
![]() |
Suffix | |
Structure: |
![]() |
Tax | ||||||||||||||||||||||||||||||||||
Identifies a type of tax on order related BODs |
||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||
Elements: |
|
TaxCode | |
The tax identifier for an ITEM. Possible values are: VAT1, VAT2, VAT3, VAT4, VAT5, US Federal Tax. |
|
Structure: |
![]() |
TaxJurisdiction | |
The tax jurisdiction of the business partner. |
|
Structure: |
![]() |
Temperature | |||||||||||||
A temperature value in decimal. |
|||||||||||||
Structure: |
![]() |
||||||||||||
Attributes: |
|
TimePeriod | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
||||||||||||
Attributes: |
|
TimePeriodAny | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
||||||||||||
Attributes: |
|
Tool extends: ResourceReference | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
ToolingResource extends: Resource | |||||||
Structure: |
![]() |
||||||
Elements: |
|
TransportationMethod | |
Structure: |
![]() |
TransportationTerm | ||||||||||||||||
When a seller ships something via common to a buyer in accordance with the Uniform Commerical Code and international legal agreements, you must specify a particular "phrase" that states who assumes the risk of shipment, who is responsible for loading and unloading the goods, where ownership or title to the goods passes, who paid or pays the carrirer, etc. Examples of these "phrases" include: - "FOB Origin Prepaid and Add" (Free On Board - no cost for loading, title passes at seller's dock, seller prepaid freight cost and delivery insurance, seller will freight costs to cost of goods) - "FOB Destination" or "FOB Destination Prepaid" (Free On Board - no cost for loading, title passes at buyer's dock, seller prepaid freight cost and delivery insurance) In software applications, this phrase is commonly split into two coded pieces, a "legal terms" risk and responsibility component for use with common carriers (FOB Destination) and some kind of qualifying component (Prepaid and Add). |
||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
|||||||||||||||
Attributes: |
|
Usage | |
Structure: |
![]() |
User | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
UserAccount | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
UserArea | |
Structure: |
![]() |
Variation | |
Structure: |
![]() |
Verb | |
Structure: |
![]() |
WageGroup | |
Is used to classify an employee’s wage. |
|
Structure: |
![]() |
WageType | |
Is a code or identifier that describes the specific type a wage an employee or worker is paid. Examples include: Exempt from Overtime, Non-Exempt from Overtime. |
|
Structure: |
![]() |
Warehouse | |
Structure: |
![]() |
WIPOperationBase | ||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||
Elements: |
|
WIPOperationReference extends: DocumentReference | |||||||||||||||||||||||||
Is a reference to a work-in-process operation. |
|||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||
Elements: |
|
Global Elements |
AccountingContact type: Contact | |
The person with accounting responsiblities. This is added to replace USERID in LoadPurchaseLedgerInvoice A business Party contact is a person and has a specific role. |
AcknowledgementDetail type: AcknowledgementDetail | |
AdditionalCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
Address type: Address | |
Address, |
Addresses type: Addresses | |
Associated address(es) for this party. |
AllCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
AllCostsToLocationCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
Allowance type: Allowance | |
Identifies a type of allowance on order related BODs |
AlternateBOMReference type: BOMDocumentReference | |
Identifies an alternate BOM that maybe used in place of the one being referenced in this particular instance. |
Amount type: Amount | |
Simple content with the currency as an attrbute |
ApplicationArea type: ApplicationArea | |
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. |
AssigningPartyId type: PartyIdType | |
This is an atomic (non-recursive) identifier, to disambiguate in cases where there might be more than one semantic element name (e.g., SupplierPartyId). |
Attachment type: Attachment | |
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. Attachment allows supporting documents to be attached to the BOD. This is for reference and management of binary/non-XML documents such as spreadsheets, CAD files, graphics, etc. Defines information about the attachement which may be inline, a MIME part or an external URI |
Attachments type: Attachments | |
Attachments allows any number of Attachment components to be associated with a Component or Noun. These Attachments use semantic names in order to provide meaning for the Attachment. The combination of the semantic name and position provide context for the Attachment. |
BasicFreightCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
BillToParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
BillToPartyId type: PartyAssignedPartyId | |
PartyQualifiedPartyId - the type of any [Party]PartyId, such as BillToPartyId. |
BOMDocumentReference type: BOMDocumentReference | |
Is a reference to a Bill-O-Material Document. |
BrokerDocumentId type: PartyDocumentId | |
Document specific identifier type. |
BrokerParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
BrokerReference type: PartyReference | |
Business type: OrganizationalUnit | |
This is used to identify the buisness entity that is involved in a transaction. The structure of the business entity is represented within here. Each application may have a different aproach to defining this entity A fully generic means of identifying an organizational unit. Can be an actual business unit (at any level) or an area of responsibility. Each is described with respect to others, via the ProximalUnit construct. |
BusinessObjectDocument type: BusinessObjectDocument | |
BuyerItemId type: PartyAssignedItemId | |
Identifies the Buyer's Item identification for the given Item. Identifies an Items identifier that has been assigned by another Party. |
CarrierDocumentId type: PartyDocumentId | |
Document specific identifier type. |
CarrierItemId type: PartyAssignedItemId | |
Is the item identifier that the carrier associates with the shipitem or container. Identifies an Items identifier that has been assigned by another Party. |
CarrierParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
CarrierReference type: PartyReference | |
Identifies a reference to a Carrier. |
CatalogDocumentReference type: GenericDocumentReference | |
Reference to a Catalog. |
Charge type: Charge | |
A charge identifies and monetary amount that must be paid. |
Charges type: Charges | |
Collects the semantically named Charges for the Components that reference Charges. The combination of the semantically rich name and the position with in the Business Object Document provide the context for the Charge. |
Contact type: Contact | |
A business Party contact is a person and has a specific role. |
ContactAbs type: Contact | |
A business Party contact is a person and has a specific role. |
Contacts type: Contacts | |
Associated contacts for this party. |
ContractDocumentReference type: OrderDocumentReference | |
CorrespondenceLanguage type: xs:language | |
The language(s) that can be used in some written or spoken correspondence. |
CustomerDocumentId type: PartyDocumentId | |
Document specific identifier type. |
CustomerItemId type: PartyAssignedItemId | |
Identifies the Customer's Item identification for the given Item. Identifies an Items identifier that has been assigned by another Party. |
CustomerParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
CustomerPartyId type: PartyAssignedPartyId | |
PartyQualifiedPartyId - the type of any [Party]PartyId, such as BillToPartyId. |
CustomerReference type: PartyReference | |
DataSheetAttachment type: Attachment | |
Attachment allows supporting documents to be attached to the BOD. This is for reference and management of binary/non-XML documents such as spreadsheets, CAD files, graphics, etc. Defines information about the attachement which may be inline, a MIME part or an external URI |
DeliverToContact type: Contact | |
Is the person(s) or department in which to deliver the ordered items to. A business Party contact is a person and has a specific role. |
DestinationHaulageCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
DestinationPortCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
Disposition type: Disposition | |
Indicates whether an item is active, inactive, or in other various states. Examples of values for this field include: Active, Inactive, Hold, Deleted, Obsolete Determines the receipt routing of an item or part. Examples of values include: Customer consignment Inspection Vendor consignment Blocked Bonded User defined SYNONYMS Receipt Routing Material Status Material Condition Code |
DistribursmentCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
Distribution type: Distribution | |
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. A distribution identifies how monetary amounts are distributed accross an organization. |
DocumentId type: DocumentIdType | |
Is the primary DocumentId of the document for the given context. For example, if a buyer is sending a Purchase Order to a Suplier the PurchaseOrder Id will be contained with in the DocumentId. Similarily, in the instance of a semantic name of a SalesOrderDocumentReference the DocumentId will carry the senders identifier for the SalesOrder in the DocumentId and the cross-references would be provided by using the other semantic Docmentids. |
DocumentIds type: DocumentIds | |
Is the identifier for the document. It is possible to carry the document identifier for the other Parties. These DocumentIds are referenced by party-specific names. |
DocumentIdType type: DocumentIdType | |
DocumentReference type: DocumentReference | |
Identifies another document within the scope of the OAGIS specification, such as a PurchaseOrder or Invoice that maybe associated with a particular Business Object Document. |
DocumentReferences type: DocumentReferences | |
Allows references to other business transactions to be referenced by the document/component that includes DocumentReferences. These references make use of semantic names in order to capture the purpose of the references. This in combination with the relative position with in a business document provide context for their use. |
DrawingAttachment type: Attachment | |
Drawing Attachment allows drawings to be attached to a Noun or Component. Attachment allows supporting documents to be attached to the BOD. This is for reference and management of binary/non-XML documents such as spreadsheets, CAD files, graphics, etc. Defines information about the attachement which may be inline, a MIME part or an external URI |
DropShipAddress type: Address | |
The address for drop shipments Address, |
DUNS type: PartyId | |
PartyIdType for DUNS numbers. Simple Id for now, but could be altered to impose pattern. |
EANUCC13 type: ItemId | |
Is the EANUCC assigned idenifier for the item. Identifies Item code. This can be a UPC or an EAN or a company assigned Id. Along with a revision number of the Item. |
Employee type: Employee | |
Employee information |
EmployeeAssignment type: EmployeeAssignment | |
This identifies an employee's work location and the HR organization to which the employee is associated |
EmployeeParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
EmployeeReference type: PartyReference | |
ExporterParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
FeatureValue type: FeatureValue | |
Identifies pair wise features that the Orderable Item may have. |
FieldValue type: NameValue | |
Is a general purpose NameValue synchronization of fields. This is typically need to synchronize codes and identifiers between systems so that the same values may be used or so that a cross reference of values can be used to translate from one parties values to another. |
FileAttachment type: Attachment | |
Attachment allows supporting documents to be attached to the BOD. This is for reference and management of binary/non-XML documents such as spreadsheets, CAD files, graphics, etc. Defines information about the attachement which may be inline, a MIME part or an external URI |
FreightBillToParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
FreightBillToReference type: PartyReference | |
GLElement type: NameValue | |
Allows accounting code elements, which cannot be linked to specified OAGI Field Identifiers that have to be transmitted. |
GPSCoordinates type: GPSCoordinates | |
Hazard type: Hazard | |
Identifies a Hazard. Hazards can be associated with Items or with activities such as maintenance operations |
HazardousItem type: HazardousItem | |
Identifies a Item, location and Hazardousmaterial identifier. |
HazardousMaterial type: HazardousMaterial | |
Provides the Hazardous Material Code and description. Provides the Hazardous Material Code and description. |
HoldAtParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
ImporterParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
InstructionsAttachment type: Attachment | |
Attachment allows supporting documents to be attached to the BOD. This is for reference and management of binary/non-XML documents such as spreadsheets, CAD files, graphics, etc. Defines information about the attachement which may be inline, a MIME part or an external URI |
InvoiceDocumentReference type: OrderDocumentReference | |
Item type: Item | |
Identifies the Item being used. |
ItemData type: ItemData | |
Information that describes the attributes of a specific item. At least one occurrence of thisComponent is required for each occurrence of the RouteOperation Component. |
ItemId type: ItemIdType | |
Identifies Item code. This can be a UPC or an EAN or a company assigned Id. Along with a revision number of the Item. |
ItemIds type: ItemIds | |
Identifies the ItemIds associated with the Order Items. |
ItemReference type: ItemReference | |
References the Item needed for a given task. |
ItemResource type: ItemResource | |
ItemStatus type: Status | |
Indicates whether an item is active, inactive, or in other various states. Examples of values for this field include: Active, Inactive, Hold, Deleted, Obsolete |
JointVentureParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
JointVentureReference type: PartyReference | |
Labor type: Employee | |
Identifies the Labor needed for a given task. |
LaborResource type: LaborResource | |
LedgerDocumentReference type: GenericDocumentReference | |
LedgerEvent type: LedgerEvent | |
Location type: Location | |
The location of a thing, as captured by an address (or addresses), GPS Coordinates, and/or in relation to other locations. 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 ... |
LogisticsProviderDocumentId type: PartyDocumentId | |
Document specific identifier type. |
Lot type: Lot | |
Identifies the Lot that a given Item belongs to. |
LotSerial type: LotSerial | |
Is the Lot and Setial numbers for the items contained in the associated component. |
Machine type: Machine | |
Idenitifies a machine. |
MachineResource type: MachineResource | |
MaintenanceOrderReference type: GenericDocumentReference | |
ManufacturerItemId type: PartyAssignedItemId | |
Identifies the Manufacturer's Item identification for the given Item. Identifies an Items identifier that has been assigned by another Party. |
ManufacturerParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
ManufacturerReference type: PartyReference | |
MarketingContact type: Contact | |
A business Party contact is a person and has a specific role. |
Message type: Message | |
MfgDocumentReference type: DocumentReference | |
Identifies another document within the scope of the OAGIS specification, such as a PurchaseOrder or Invoice that maybe associated with a particular Business Object Document. |
MfgDocumentReferences type: MfgDocumentReferences | |
Provides references to other manufacturing related documents. |
MiscellaneousCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
NameValueBase type: NameValueBase | |
Note type: Note | |
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. |
Noun type: Noun | |
Operation type: Operation | |
Information that describes the operation to be performed. |
OperationReference type: WIPOperationReference | |
Is a reference to an associated work-in-process operation. Is a reference to a work-in-process operation. |
OrderItem type: OrderItem | |
Provides information on the Orderable Item. When associated with an order like a Purchase Order, it identifies the item being ordered at the associated Line. Provides information on the Orderable Item. When associated with an order like a Purchase Order, it identifies the item being ordered at the associated Line. |
OrderStatus type: OrderStatus | |
Order specific status information. |
OriginPortCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
Packaging type: Packaging | |
Identifies the Packaging information for a given item. Note: The UPC here is the UPC of the packaging for a given item. Identifies the Packaging information for a given item. Note: The UPC here is the UPC of the packaging for a given item. |
Parties type: Parties | |
Grouping of semantically named Parties. |
PartyAssignedItemId type: PartyAssignedItemId | |
Identifies an Items identifier that has been assigned by another Party. |
PartyAssignedPartyId type: PartyAssignedPartyId | |
The head of the PartyAssignedPartyId substitution group. Any [Party]PartyId, e.g., BillToPartyId, must be placed in this group to be usable as a substitution, and must be of a type that is a legal derivation of PartyIdAny PartyQualifiedPartyId - the type of any [Party]PartyId, such as BillToPartyId. |
PartyReference type: PartyReference | |
PartyReferences type: PartyReferences | |
References to any parties. |
PartyType type: PartyBase | |
A mininmal Party type, as root to Party subst group type hierarchy |
PayFromParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
PayFromReference type: PartyReference | |
PaymentTerms type: PaymentTerms | |
Identifies the payment terms for an Order or Invoice. Supports the abiility to specify an absolute due date, a number of days from a start daye, a percent discount or an absolute discount. A common term like "Net30Days" is explicitly code as either a calculated DueDateTime or a PaymentTermsDateTime and NumberOfDays. Identifies the payment terms for an Order or Invoice. Supports the abiility to specify an absolute due date, a number of days from a start daye, a percent discount or an absolute discount. A common term like "Net30Days" is explicitly code as either a calculated DueDateTime or a PaymentTermsDateTime and NumberOfDays. |
Person type: Person | |
Indentifies the person. |
PersonName type: PersonName | |
Full specification for a persons name. |
PictureAttachment type: Attachment | |
Attachment allows supporting documents to be attached to the BOD. This is for reference and management of binary/non-XML documents such as spreadsheets, CAD files, graphics, etc. Defines information about the attachement which may be inline, a MIME part or an external URI |
PostalAddress type: PostalAddress | |
Provides the postal address of the location. |
Precaution type: Precaution | |
Identifies the Precautions associated with a Hazard |
PrimaryAddress type: Address | |
The primary address Address, |
PrimaryContact type: Contact | |
A business Party contact is a person and has a specific role. |
ProductionOrderReference type: ProductionOrderDocumentReference | |
Is reference to a ProductionOrder |
Project type: Project | |
A set of tasks with the following attributes: a singular purpose, a start and end date, those that accumulate costs, and those that may have materials and overhead. SYNONYMS: Job, Process Model, Program, Work Breakdown Structure (WBS) element This is used to enable all relevant sub-systems that submit transactions to the project accounting application to maintain valid values for the key project fields. The target applications for this update would include, but not necessarily be limited to: Accounts Payable Accounts Receivable Budget Order Management Purchasing Time and Labor Travel and Expense A set of tasks with the following attributes: a singular purpose, a start and end date, those that accumulate costs, and those that may have materials and overhead. SYNONYMS: Job, Process Model, Program, Work Breakdown Structure (WBS) element |
ProjectReference type: GenericDocumentReference | |
Is a reference to a Project document. |
Property type: NameValue | |
Represents the Properties of the Items being communicated. |
PublisherParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
PublisherReference type: PartyReference | |
PurchaseOrderDocumentReference type: OrderDocumentReference | |
Qualification type: NameValue | |
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. |
QualifiedResource type: QualifiedResource | |
Information that describes the resources to perform the specified resource usage for the operation and/or the step that is defined by the preceding Operation or Step. |
QuoteDocumentReference type: OrderDocumentReference | |
ReceiptDocumentReference type: OrderDocumentReference | |
Is a reference to the receipt document. |
RemitToParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
RemitToReference type: PartyReference | |
RequisitionDocumentReference type: OrderDocumentReference | |
Resource type: Resource | |
An abstract type describing the allocation of persons, equipment or materials, likely in a manufacturing environment. Pattern should be: Id, Class/Category, Required Quantities AW: Empty for now, if the xs:all is robust in the future may want to place common Resource fields here- mdf: Really shouldn't use group here - harder to extend. But if the resource has to come first... |
Resources type: Resources | |
Indicates the resources being allocated. AW: In the future xs:All would be very helpful; still unbounded works here AW: not using Subs group with Resource so names can be local |
ReturnToParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
RFQDocumentReference type: OrderDocumentReference | |
RouteDocumentReference type: RouteDocumentReference | |
Reference to a Routing. |
RoutingDisposition type: Disposition | |
Indicates the receipt routing disposition for an Item. Determines the receipt routing of an item or part. Examples of values include: Customer consignment Inspection Vendor consignment Blocked Bonded User defined SYNONYMS Receipt Routing Material Status Material Condition Code |
SalesContact type: Contact | |
A business Party contact is a person and has a specific role. |
SalesOrderDocumentReference type: OrderDocumentReference | |
SCAC type: PartyId | |
StandardCarrierAlphaCode |
SecondaryAddress type: Address | |
Address, |
SecondaryContact type: Contact | |
A business Party contact is a person and has a specific role. |
ShipFromItemId type: PartyAssignedItemId | |
Identifies the ShipFrom's Item identifier. Identifies an Items identifier that has been assigned by another Party. |
ShipFromParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
ShipFromReference type: PartyReference | |
ShipperReference type: PartyReference | |
ShippersDocumentId type: PartyDocumentId | |
Document specific identifier type. |
ShippingAddress type: Address | |
The address to ship the material to Address, |
ShippingMaterial type: ShippingMaterial | |
Identifies the materials used to ship. |
ShippingNote type: Note | |
Is the shipping instructions or notes. 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. |
ShipToParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
ShipToPartyId type: PartyAssignedPartyId | |
PartyQualifiedPartyId - the type of any [Party]PartyId, such as BillToPartyId. |
ShipToReference type: PartyReference | |
Site type: Location | |
Identifies the heirachical site level for a position. 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 ... |
SoldToParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
SpecialHandlingNote type: Note | |
Describes any special, physical handling needs that the freight might have. For example, the need for a lift gate. 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. |
SpecificAmountCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
Status type: Status | |
Indicates the state of the Noun or Component in which it occurs. |
Step type: Step | |
Information specific to the steps specified to perform the operation. |
SupplementaryCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
SupplierDocumentId type: PartyDocumentId | |
Document specific identifier type. |
SupplierItemId type: PartyAssignedItemId | |
Identifies the Supplier's Item identification for the given Item. Identifies an Items identifier that has been assigned by another Party. |
SupplierParty type: PartyInstitutional | |
A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf |
SupplierPartyId type: PartyAssignedPartyId | |
PartyQualifiedPartyId - the type of any [Party]PartyId, such as BillToPartyId. |
SupplierReference type: PartyReference | |
Tax type: Tax | |
Allows for taxes on tax. Identifies a type of tax on order related BODs |
Tool type: Tool | |
Identifies the tool needed for a given task. |
ToolResource type: ToolingResource | |
TransportationCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
TransportationTerm type: TransportationTerm | |
When a seller ships something via common to a buyer in accordance with the Uniform Commerical Code and international legal agreements, you must specify a particular "phrase" that states who assumes the risk of shipment, who is responsible for loading and unloading the goods, where ownership or title to the goods passes, who paid or pays the carrirer, etc. Examples of these "phrases" include: - "FOB Origin Prepaid and Add" (Free On Board - no cost for loading, title passes at seller's dock, seller prepaid freight cost and delivery insurance, seller will freight costs to cost of goods) - "FOB Destination" or "FOB Destination Prepaid" (Free On Board - no cost for loading, title passes at buyer's dock, seller prepaid freight cost and delivery insurance) In software applications, this phrase is commonly split into two coded pieces, a "legal terms" risk and responsibility component for use with common carriers (FOB Destination) and some kind of qualifying component (Prepaid and Add). When a seller ships something via common to a buyer in accordance with the Uniform Commerical Code and international legal agreements, you must specify a particular "phrase" that states who assumes the risk of shipment, who is responsible for loading and unloading the goods, where ownership or title to the goods passes, who paid or pays the carrirer, etc. Examples of these "phrases" include: - "FOB Origin Prepaid and Add" (Free On Board - no cost for loading, title passes at seller's dock, seller prepaid freight cost and delivery insurance, seller will freight costs to cost of goods) - "FOB Destination" or "FOB Destination Prepaid" (Free On Board - no cost for loading, title passes at buyer's dock, seller prepaid freight cost and delivery insurance) In software applications, this phrase is commonly split into two coded pieces, a "legal terms" risk and responsibility component for use with common carriers (FOB Destination) and some kind of qualifying component (Prepaid and Add). |
TransportPlusAdditionalCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
TransportToLocationCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
Type type: Status | |
Further qualifies the type of semantic component or document. |
UOMGroupReference type: GenericDocumentReference | |
Reference to the UOM cross references for units of measures. |
UPC type: ItemId | |
Is the UPC Identifier of the item. Identifies Item code. This can be a UPC or an EAN or a company assigned Id. Along with a revision number of the Item. |
UserAccount type: UserAccount | |
UserArea type: UserArea | |
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. |
Verb type: Verb | |
VoucherDocumentReference type: OrderDocumentReference | |
WeightValuationCharge type: Charge | |
A charge identifies and monetary amount that must be paid. |
WorkScheduleReference type: GenericDocumentReference | |
All Attributes |
@acknowledge type: AcknowledgementType |
Used in:
AcknowledgableVerb
|
@active type: xs:boolean |
Used in:
PartyBase
|
@author type: xs:string |
Used in:
Note
|
@code type: xs:string |
Used in:
Reason
|
@confirm type: ConfirmType |
Used in:
ConfirmableVerb
|
@conversionFactor type: xs:decimal |
Used in:
FunctionalAmount
|
@currency type: Currency |
Identifies the currency of the amount.
Used in:
Amount
|
@encoding type: Encoding |
Used in:
EmbeddedData
|
@entryDateTime type: DateTime |
Used in:
OrderStatus
Note
Temperature
|
@entryDateTime type: DateTime |
Used in:
OrderStatus
Note
Temperature
|
@entryDateTime type: DateTime |
Used in:
OrderStatus
Note
Temperature
|
@environment restricts: xs:string |
Used in:
BusinessObjectDocument
|
@expressionLanguage type: xs:string |
Used in:
ExpressionCriteria
|
@inclusive type: xs:boolean |
Used in:
TimePeriodAny
TimePeriod
DatePeriod
|
@inclusive type: xs:boolean |
Used in:
TimePeriodAny
TimePeriod
DatePeriod
|
@inclusive type: xs:boolean |
Used in:
TimePeriodAny
TimePeriod
DatePeriod
|
@inline type: xs:boolean |
Used in:
Attachment
|
@issuingAgency type: TransportationType |
The United Nations Trade Facilitation Information Exchange (UN/TraFIX) has established the following codes (INCOTERMS 1990) for use in international trade to Europe, Asia and the Pacific. (See http://www.unece.org/trade/rec/rec05en.htm).
Used in:
TransportationTerm
TermCode
HazardousMaterial
Code
|
@issuingAgency type: xs:string |
Used in:
TransportationTerm
TermCode
HazardousMaterial
Code
|
@lang type: xs:language |
Used in:
LingualString
BusinessObjectDocument
|
@lang type: xs:language |
Used in:
LingualString
BusinessObjectDocument
|
@name type: Tag |
Is the name of the tag for the information being passed.
Used in:
NameValuePair
|
@oneTime type: xs:boolean |
Used in:
PartyBase
|
@owner type: xs:string |
Used in:
Description
|
@qualifyingAgency type: xs:string |
Used in:
AddressId
Signature
|
@qualifyingAgency type: xs:string |
Used in:
AddressId
Signature
|
@revision restricts: xs:string |
Used in:
BusinessObjectDocument
|
@scale type: TemperatureScale |
Used in:
Temperature
|
@type type: Type |
Is the type of the information being passed in the NameValue.
Used in:
NameValuePair
License
|
@type type: LicenseType |
Used in:
NameValuePair
License
|
@uom type: UOM |
Used in:
Quantity
|
@url type: xs:string |
Used in:
ItemId
|