Understanding Identification structure in an EBO

Many newcomers to AIA and canonical models get overwhelmed with what information needs to be populated on the header. In Integration Developers Guide (which can be downloaded from metalink number 824495.1 or use this URL https://webiv.oraclecorp.com/cgi-bin/webiv/do.pl/Get?WwwID=note:824495.1), under the heading, Populating the EBO Object Identification has details on populating identification structure.

Below section describes Identification structure usage.

1. BusinessComponentID - This is a unique key for the application agnostic representation of the object instance. This is generated by the API provided by the Oracle AIA infrastrucutire. Within XSLT you would call populate XREF API to generate this key value. Hence these values will be stored in XREF table.
2. ID/ContextID - This is the business friendly (i.e. the one that has business context identification) identifier present in the participating application for this particular object instance. For example, PO number and Sales Order number.
3. ApplicationObjectkey - This is the Primary key of the participating application which is internally generated unique key for this particular object instance. For example, PK-Order-ID or Worker_ID.
4. AlternateObjectKey - Different ways of Identifying the same object instance. Use this element to capture additional information about the key. For example, GrouID in General Ledger entry or CONSECUTIVE_BILLING_NUMBER in Invoice. Not all Identifications may have this field populated.

Further, to define the environment in which an identifier is valid, a set of attributes that describes the validity of the key is supported in addition to the actual key value.
1. schemeID - Attribute schemeID provides information about the object type identified by the ID, for example ItemGUID for the GUID of an item and PartyGUID for the GUID of a party. For the BusinessComponentID, the schemeID is set to the name of the object followed by ' GUID'. For the ID, the schemeID is set to the name of the element as known in the participating application.
2. schemeVersionID - This describes the version of the identification scheme.
3. schemeAgencyID- This is the ID of the agency that manages the identification scheme of the identifier. The GUIDs generated by Oracle AIA will have AIA 01 populated in this attribute. For identifiers generated by participating applications, the short code for that of the participating application will be stores in this attribute.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

News, views and implementation best practices from the Oracle Application Integration Architecture team.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today