UNDT000007-SC2 SC Code List. Identifier The identification of a list of codes. Code List Identification Identifier string UNDT000007-SC3 SC Code List. Agency. Identifier An agency that maintains one or more lists of codes. Code List Agency Identifier string Defaults to the UN/EDIFACT data element 3055 code list. UNDT000007-SC4 SC Code List. Agency Name. Text The name of the agency that maintains the list of codes. Code List Agency Name Text string UNDT000007-SC5 SC Code List. Name. Text The name of a list of codes. Code List Name Text string UNDT000007-SC6 SC Code List. Version. Identifier The version of the list of codes. Code List Version Identifier string UNDT000007-SC7 SC Code. Name. Text The textual equivalent of the code content component. Code Name Text string UNDT000007-SC8 SC Language. Identifier The identifier of the language used in the code name. Language Identification Identifier string UNDT000007-SC9 SC Code List. Uniform Resource. Identifier The Uniform Resource Identifier that identifies where the code list is located. Code List Uniform Resource Identifier Identifier string UNDT000007-SC10 SC Code List Scheme. Uniform Resource. Identifier The Uniform Resource Identifier that identifies where the code list scheme is located. Code List Scheme Uniform Resource Identifier Identifier string Is where the information that the BOD message carries is provided, in this case ShowPaymentStatus. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (PaymentStatus). Is the schema based inheritance for all BODs. The logical model would also include the DataArea. OAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on. Indicates the version of the given BOD defintion. Indicates whether this BOD is being sent in a "Test" or a "Production" mode. If the BOD is being sent in a test mode, it's information should not affect the business operation. However, if the BOD is sent in "Production" mode it is assumed that all test has been complete and the contents of the BOD are to affect the operation of the receiving business application(s). Indicates the language that the contents of the BOD is in unless otherwise stated. Identifies the sender of the given BOD instance Allows any digital Signatures to be added to the Instance of the BOD Instance in order to sign for any portion of the BOD content. The abstract Header type that is the basis for all non-statusable OAGIS Document Headers 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. StatusABIEType is logically derived from UN/CEFACT TBG17 ABIE StatusType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Information to communicate the payment transaction. QDT000000 QDT Country_ Code. Type 1.0 Code Country QDT000000 QDT Description_ Text. Type 1.0 Text Description A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified. QDT000000 QDT Response_ Code. Type 1.0 Code Response This is the ID assigned to the document by the creator of the document. Provides the structure to indicate a Date/Time period where the Time is provided with in the Start and Duration or EndDateTime. PmtInf/PmtTx/ChqInstr Specifies the type of checque to be issued. Information needed due to regulatory and statutory requirements. Code - Specifies the regulatory reporting code. Amount - Amount of money and currency that may need to be reported for regulatory and statutory requirements. Note - Or Information - Additional details that cater for domestic regulatory requirements. PmtInf/PmtTx/InstrForFrstAgt PmtInf/PmtTx/RmtInf LocationABIEType is logically derived from UN/CEFACT TBG17 ABIE LocationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. QDT000000 QDT Currency_ Code. Type 1.0 Code Currency TimePeriodABIEType is logically derived from UN/CEFACT TBG17 ABIE PeriodType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. QDT000000 QDT State_ Code. Type 1.0 Code State ContactABIEType is logically derived from UN/CEFACT TBG17 ABIE ContactType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. PmtInf/PmtTx/InstrForFrstAgt/Tax Address BaseType provides the information about the address or semantic address of an associated entity. The OAGIS CoordinateType allows the use of another coordinate system for the use within a warehousing and inventory environment and the geographic coordinat system. CommunicationABIEType is logically derived from UN/CEFACT TBG17 ABIE CommunicationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. PreferenceABIEType is logically derived from UN/CEFACT TBG17 ABIE PreferenceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. QDT000000 QDT Delivery Point_ Code. Type 1.0 A character string (letters, figures, or symbols) that for brevity and/or languange independence may be used to represent or replace a definitive value or text of an attribute together with relevant supplementary information. Code Delivery Point QDT000000 QDT Country Subdivision_ Code. Type 1.0 A character string (letters, figures, or symbols) that for brevity and/or languange independence may be used to represent or replace a definitive value or text of an attribute together with relevant supplementary information. Code Country Subdivision TaxABIEType is logically derived from UN/CEFACT TBG17 ABIE TaxType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Indicates that tax code of the tax being represented by the given instance of tax. Possible values are: Sales Tax, Use Tax, VAT Contains the sequenced identifier for the associated component or noun. Uniquely identifies the exemption along with the agency that defines the excemption. CalculationABIEType is logically derived fom the UN/CEFACT TBG 17 ABIE CalculationType, which is defined in the Reusabale Aggregate Business Information Enitity (RUABIE) XML Schema file. The purpose of the ShowPaymentStatus is to enable an application to respond with specific PaymentStatus information from another business application module. This typically a transaction that occurs between a company and a Bank in order to remit PaymentStatus to company that has provide goods or services. This tpically provided in response to the GetPaymentStatus. The Show verb is used when sending the information about a specific instance of a business document or entity. The Show verb may be used to respond to a Get request or it can be used in a publish scenario, where it pushes information to other applications based on a business event.Although BODs based on this verb do not commonly cause updates to occur, there may be times when the component receiving the Show decides to use the information it receives to update. This is entirely the decision of the receiving software component and is not forbidden.The behavior of the Show verb is quite straight forward with one exception. The Show response to any Get request needs to read the request carefully to ensure the response is returning the requested Data Types. 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. A copy of the ApplicationArea for the original BOD that was processed. Present either as additional reference information, or for use in identifying the BOD in situations where a BODReference is not known. Identifies characteristics and control identifiers that relate to the application that created the Business Object Document. The sender area can indicate the logical location of the application and/or database server, the application, and the task that was processing to create the BOD. is the date time stamp that the given instance of the Business Object Document was created. This date must not be modified during the life of the Business Object Document. If the BOD is to be signed the signature element is included, otherwise it is not. Signature supports any digital signature that maybe used by an implementation of OAGIS. The qualifyingAgency identifies the agency that provided the format for the signature. This element supports any digital signature specification that is available today and in the future. This is accomplished by not actually defining the content but by allowing the implementation to specify the digital signature to be used via an external XML Schema namespace declaration. The Signature element is defined to have any content from any other namespace. This allows the user to carry a digital signature in the xml instance of a BOD. The choice of which digital signature to use is left up to the user and their integration needs. The BODId provides a place to carry a Globally Unique Identifier (GUID) that will make each Business Object Document instance uniquely identifiable. This is a critical success factor to enable software developers to use the Globally Unique Identifier (GUID) to build the following services or capabilities: 1. Legally binding transactions, 2. Transaction logging, 3. Exception handling, 4. Re-sending, 5. Reporting, 6. Confirmations, 7. Security. Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS. This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document throught the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document. The Open Applications Group will make best efforts to quickly consider all proposed submissions.The USERAREA is always the last element in all components, except where the component has been extended inline. Party initiating the payment to the forwarding or first agent. This can be the debtor (in a credit transfer), the creditor (in a direct debit) or a party that initiates the payment on behalf of the debtor or creditor. Financial institution that receives the payment transaction from the account owner or authorised party and processes the instruction. Financial institution that receives the payment transaction from the account owner or authorised party and processes the instruction. Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective. Date at which the initiating party requests that the payment instruction be executed. If payment by cheque, the date when the cheque is required to be generated by the bank. Specifies the transfer method that will be used by the first agent to transfer the funds to the creditor. IST limits these values to CreditTransfer (TRF) and Checque (CHK). Party that owes an amount of money to the creditor. In the context of the payment model, the debtor is also the debit account owner. Information to communicate the payment transaction. Provides the logical location of the server and applications from which the Business Object Document originated. It can be used to establish a logical to physical mapping, however its use is optional. Each system or combination of systems should maintain an external central reference table containing the logical names or logical addresses of the application systems in the integration configuration. This enables the logical names to be mapped to the physical network addresses of the resources needed on the network. Note: The technical implementation of this Domain Naming Service is not dictated by this specification. This logical to physical mapping may be done at execution time by the application itself or by a middleware transport mechanism, depending on the integration architecture used. This provides for a simple but effective directory access capability while maintaining application independence from the physical location of those resources on the network Provides a finer level of control than Logical Identifier and represents the business application that issued the Business Object Document. Its use is optional. The Open Applications Group has not constructed the list of valid Component names. A suggestion for naming is to use the application component names used in the scenario diagrams in section two of OAGIS. Example Components may be Inventory, or Payroll. Describes the business event that initiated the need for the Business Object Document to be created. Its use is optional. Although the Task may differ depending on the specific implementation, it is important to enable drill back capability. Example Tasks may be Receipt or Adjustment. Enables the sending application to indicate the instance identifier of the event or task that caused the BOD to be created. This allows drill back from the BOD message into the sending application. The may be required in environments where an audit trail must be maintained for all transactions. Is an option controlled by the Sender business application. It is a request to the receiving application to send back a confirmation BOD to the sender. The confirmation Business Object Document may indicate the successful processing of the original Business Object Document or return error conditions if the original Business Object Document was unsuccessful. The confirmation request has the following valid values: Never - No confirmation Business Object Document requested OnError - OnError send back a confirmation Business Object Document only if an error has occurred Always - Always send a confirmation Business Object Document regardless 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). The datetime on which the object was last modified The date that document was created within the system of record. Provides bank account details. Country in which the Address is in. A possible list of values is as specified in ISO 3166-2. Is the Identifiers of the given instance of an entity within the scope of the integration. The providedBy attribute identifies the party that provided or knows this party by the given identifier. Is the primary document id for the document associated. Is the alternate document id for the associated document. The Attachment represents binary data files that may be included within a BOD. These files replace the paper specifications and drawings attached to a BOD definition to clearly communicate design requirements. This Data Type is optional. Attachment usage is further defined by its position. Contains the set of possible identifiers for an associated Party. Identifies the Name of the object in which associated. The location of a thing, as captured by an address (or addresses), GPS Coordinates, and/or in relation to other locations. Contacts are the point of communication with the given party. In the case of an organization it may be the requestioner, the buyer, customer service, etc. An explicit period of time for the bucket. The underlying reason for the payment transaction, e.g. a charity payment, or a commerical agreement between the creditor and the debitor. Provided by the code contained. Provides a roprietary text description. Amount of money to be transferred between debtor and creditor, before deduction of charges, expressed in the currency of the debtor's account or in another currency. Amount of money to be transferred between the debtor and creditor, before deduction of charges, expressed in the currency of the debtor's account and to be transferred into a different currency. Information related to a cheque instruction. Identifies the party that originated the purchase of the goods, service or payment. An agent between the first and final agent. Usage guideline: This information is provided by the initiating party, based on information provided by the creditor or final party. How this information is handled by the first agent will depend on the service level/business practice between initiating party and first agent. Party that receives an amount of money from the debtor. In the context of the payment model, the creditor is also the credit account owner. Financial institution that receives the payment transaction on behalf of an account owner, and posts the transaction to the account. Party that is the ultimate beneficiary of the cash transfer. Specifies if the creditor and/or debtor will bear the charges associated with the processing of the payment transaction. Unique and unambiguous reference to the foreign exchange contract agreed between the initiating party and the first agent. Information needed due to regulatory and statutory requirements,. Further information related to the processing of the payment instruction, provided by the initiating party, and intended for the final agent. Further information related to the processing of the payment instruction, which may need to be acted upon by the first agent, depending on agreement between customer and the first agent. The instruction can relate to a level of service between the customer and the first agent, or can be information required by the first agent. Information supplied to enable the matching of an entry with the items that the payment is intended to settle, eg, commercial invoices in an Accounts Receivable system. Element for the communication of all codes. This is the DateTime the associated object is made effective Identifies the reason for an activity Specifies the currency code of the object in which it is associated. Indicates the type of the object in which assoicated. This is the Account Identification assigned to the customer (Payer) by the Supplier (Payee) Unique and unambiguous identifier for a payment instruction assigned by the initiating party. Unique and unambiguous identification of a payment transaction, as assigned by any of the parties on the initiating side, which will be passed on throughout the entire end-to-end chain. Unique and unambiguous identification of remittance information which is sent separately from the payment initiation information. Indicates when the status change occured. Is the revision of the semantically named document. The combination of the ID and its revision uniquely identifies the associated entity. Associated account of the associated entity. Identifies the cheque number. Specifies the delivery method of the cheque. Identifies the party that ordered the issuance of the cheque. This is the Party (the person or organization) to receive delivery of a the associated entitys. This can be goods, services, cheques, etc. Several examples of the value of this field include an office number, a complete address, or a person Indicates the priority or urgency of the associated entity. Date when the draft becomes payable and when debtor’s account is debited. Code agreed between the initiating party and the first agent, which specifies the cheque layout, company logo and digitised signature to be used to print the cheque. Information that needs to be printed on the cheque, used by the payer to add miscellaneous information. Regional area in which the cheque can be cleared, when a country has no nation-wide cheque clearing organisation. The monetary value of the object in which the amount is associated Reason or nature of the debit, on the debtor’s account, that must be returned in debit advices/statements to the debtor. Specifies the method to be used by the first agent to deliver the remittance advice information. Electronic address to which the first agent is to send the remittance information. Postal address to which the first agent is to send the remittance information. Amount of money due to government or tax authority, according to various pre-defined parameters such as thresholds or income. Information, in free text form, which is supplied to enable the matching (reconciliation) of a payment with the items that the payment is intended to settle, such as commercial invoices in an Accounts Receivable system. Information, in structured form, which is supplied to enable the matching (reconciliation) of a payment with the items that the payment is intended to settle, such as commercial invoices in an Accounts Receivable system. Is the Code to indicate the status for the Noun or Component in which the Status Component occurs. Identifier for a business or individual provided by the government. This maybe a FIIN, Social Security Number, or Drivers License Number to name a few. Identifier for business provided by Dun and Bradstreet. The Bank Identifier Code is a unique address which, in telecommunication messages, identifies precisely the financial institutions involved in financial transactions. Start timestamp indicating the starting point of the event. Indicates the duration of time as represented by ISO 8601. Where the value space is a six dimensional space where the coordinates designate the Gregorian year, month, day, hour, minute, and second. The number of seconds can include decimal digits to arbitary pecision. Is the ending timestamp of the event. Allows the data to be embedded directly into the BOD instance. Indicates the name of the File being referenced. Allows a reference to an ISBN. Identifies the type of the file type of the attachment. Specifies how big the file is. Is the title of the person. For example Dr.. Is the position or designation of the pesron with whom associated within the given organization. Examples are Director, Software Engineer, Purchasing Manager etc A text description of the responsibility of the associated entity. Tax Identification Number of the creditor. Type of tax payer (creditor) Tax Identification Number of the debtor Tax reference information that is specific to a taxing agency. Total amount of money on which the tax is based. Amount of money resulting from the calculation of the tax. Indicates the tax for the object associated. Amount of money and currency of a document referred to in the remittance section. The amount is typically either the original amount due and payable, or the amount actually remitted for the referenced document. PmtInf/PmtTx/RmtInf/Invcr PmtInf/PmtTx/RmtInf/Invcee Format Code indicates the format of the address. Examples are US Military, US Formatted Address, European Formatted Address etc. There is no intent to decode the address formats - these are informational only. No list of valid values exists or is proposed here. The name of the person or organization that the associated entity is intended. The name that the associated entity is sent by. The Number of the building or house on the street that identifies where to deliver mail. For example, Building 300 on Standards Parkway The building or house name on the street that identifies where to deliver mail The Street Name where the building/ house is located Identifies the apartment number or office suite. The floor where the housename is located Identifies a Post Office Box number Identifies the Dock or the Mail Stop or Lane or any other specific Delivery Point. Qualifies the further division of the City, example a city may have many districts or Boroughs. The type attribute identifies the type of this entity e.g. City, Borough etc, and there is a pre-defined list of types supported, with the ability to add new ones as necessary Identifies the town or the city Qualifies the further division of the Country. These may be Districts, Regions, States, Provinces etc. A possible list of values is as specified in ISO 3166-2. The type attribute identifies the type of this e.g. District, Region etc, and there is a pre-defined list of types supported, with the ability to add new ones as necessary Postal Code of the Address. Is the value and unit of measure in the z-axis in a thrre dimensional system. Examples of this maybe the Altitude in the case of a map of the world, or the height or shelf in a rack system in the case of a manufacturing or warehouse facility. Is the system in which the userid applies. PmtInf/PmtTx/RmtInf/Strd/RfrdDocAmt/DuepyblAmt PmtInf/PmtTx/RmtInf/Strd/RfrdDocAmt/DscntApldAmt PmtInf/PmtTx/RmtInf/Strd/RfrdDocAmt/RmtdAmt PmtInf/PmtTx/RmtInf/Strd/RfrdDocAmt/CdtNoteAmt PmtInf/PmtTx/RmtInf/Strd/RfrdDocAmt/TaxAmt Identifies the channel in which the associated entity comes. Code identifying the usage of the contact point e.g. business, private, etc. The country dialing code for a communication number. The area dialing code for a communication number. The commication number, not including country dialing or area dialing codes. The extension of the assoicated communication number. The text that permits access to the electronic network of the associated communication number such as telephone network, for example 9, *70. Indicates that the associated entity preferrs HTML format. Is a message to the reader about the object associated. A value expressing the value of a Sequence. Indicates the time period in which the associated component is effective. Is the base amount from which the charge/allowance is derived. Is the base quantityfrom which the charge/allowance is derived. Allows the sender to indicate how the Charge/Allowance was calculated. This is used to represent the tax amount in the currency of the taxing authority in addition to the transactional tax amount which may be in a different currency. Is the multiplier to convert the source units to the target units. (e.g.) The conversion of one currency to another currency monitary amount in the from currency is multiplied by the CalculationRateNumeric to calcultate the monitary amount in the to currency. Another example maybe the conversion between units of measure. A group that contains the identifier for the associated component or noun. Common Free Form Text elements that occur together. Provides the Identifier(s) of the document being communicated. Uniquily identifies a Document within an organization. Typically there is only an ID for a document within one system. However, with the use of different business applications there maybe different ids assigned to the same document within an organization from the different systems and in the case of B2B transactions different businesses may have different Identifiers for the same document. This construct is designed to allow for these different identifications. Common References to DocumentReferences and Attachements Group of elements used to provide further means of identifying the payment transaction. Contain the ids for a given party. These ids may be assigned by multiple organizations. Indicates the ID of the associated component or noun. QDT000000 QDT Month_ Date. Type 1.0 A particular point in the progression of time together with the relevant supplementary information. Provides the XML Schema simpleType that allows either just the Date or the Date and Time to be provided in the elements that are based on this type and/or types that use this as their base. Date Month