Bookshelf Home | Contents | Index | Search | PDF |
Siebel Connector for Oracle Applications > Detailed Data Mappings > Entity Attribute Mappings for Oracle Applications R10.7 >
Account Integration EAM Mappings
Oracle Customers and Siebel Account business objects are integrated. The associated EAM mappings are shown in Table 17 and Table 18.
Entity Mapping
Attribute Mapping
Table 18. Account Attribute Mapping Siebel Field Oracle Base Column Siebel to Oracle Integration Oracle to Siebel Integration Siebel Field (Account) Oracle Base Column (RA_CUSTOMERS) Siebel to Oracle Integration (RA_CUSTOMERS_ INTERFACE_ALL) Oracle to Siebel Integration (RA_CUSTOMERS) Id ORIG_SYSTEM_ REFERENCE ORIG_SYSTEM_
CUSTOMER_REF ORIG_SYSTEM_REFERENCE Integration Id CUSTOMER_ID CUSTOMER_ID Account Organization Integration Id -- ORG_ID Name CUSTOMER_NAME CUSTOMER_NAME CUSTOMER_NAME CUSTOMER_TYPE CUSTOMER_TYPE (defaulted to R) Type CUSTOMER_CATEGORY_ CODE CUSTOMER_CATEGORY_
CODE (through value map Oracle Account Category) CUSTOMER_CATEGORY_
CODE (through value map Oracle Account Category) Account Status STATUS CUSTOMER_STATUS (through value map Oracle Account Status) STATUS (through value map Oracle Account Status) Created By CREATED_BY CREATED_BY (through value map Oracle User ID) Updated By LAST_UPDATED_BY LAST_UPDATED_BY (through value map Oracle User ID) Created CREATION_DATE CREATION_DATE Updated LAST_UPDATE_DATE LAST_UPDATE_DATE CSN CUSTOMER_NUMBER CUSTOMER_NUMBER GSA Flag GSA_INDICATOR GSA_INDICATOR Home Page URL URL URL Price List Integration Id PRICE_LIST_ID (No Oracle interface available) PRICE_LIST_ID Freight Terms FREIGHT_TERM FREIGHT_TERM (through value map Oracle Freight) Main Phone Number See Telephone Number Mapping for R10.7.
Value map: Oracle Address Phone Main Fax Number Siebel Field (Account Credit Profile) Oracle Base Column AR_CUSTOMER_PROFILE_
AMOUNTS Siebel to Oracle Integration Oracle to Siebel Integration (SIE_CUSTOMER_PROFILE_
AMOUNTS) Credit Control Area Code CUSTOMER_PROFILE_
AMOUNT_ID CUSTOMER_PROFILE_
AMOUNT_ID Credit Limit Amount OVERALL_CREDIT_LIMIT OVERALL_CREDIT_LIMIT Credit Currency Code CURRENCY_CODE CURRENCY_CODE Siebel Field (Account Synonym) Oracle Base Column (RA_CUSTOMERS) Siebel to Oracle Integration Oracle to Siebel Integration (RA_CUSTOMERS) Synonym CUSTOMER_NAME_
PHONETIC (No Oracle interface available) CUSTOMER_NAME_
PHONETIC Siebel Field (Business Address) Oracle Base Column (RA_ADDRESSES_ALL) Siebel to Oracle Integration (RA_CUSTOMERS_
INTERFACE_ALL) Oracle to Siebel Integration (RA_ADDRESSES_ALL) Id ORIG_SYSTEM_ REFERENCE ORIG_SYSTEM_ADDRESS_
REF ORIG_SYSTEM_REFERENCE Integration Id ADDRESS_ID ADDRESS_ID Bill Address Flag RA_SITE_USES_ALL.SITE_USE_CODE = BILL_TO
(See Site Use Mapping) SITE_USE_CODE = BILL_TO Ship Address Flag RA_SITE_USES_ALL.SITE_USE_CODE = SHIP_TO
(See Site Use Mapping for R10.7) SITE_USE_CODE = SHIP_TO Main Address Flag SITE_USE_CODE = GENERAL Primary Bill To Address Id RA_SITE_USES_ALL.PRIMARY_FLAG = Y
(See Site Use Mapping for R10.7) PRIMARY_SITE_USE_FLAG = Y Primary Ship To Address Id RA_SITE_USES_ALL.PRIMARY_FLAG = Y
(See Site Use Mapping for R10.7) PRIMARY_SITE_USE_FLAG = Y Primary Address Id RA_SITE_USES_ALL.PRIMARY_FLAG = Y
(See Site Use Mapping for R10.7) PRIMARY_SITE_USE_FLAG = Y Street Address ADDRESS1 ADDRESS1 ADDRESS1 Street Address 2 ADDRESS2 ADDRESS2 Integration Id ADDRESS_ID ADDRESS_ID City CITY CITY CITY State STATE STATE STATE Province PROVINCE PROVINCE PROVINCE County COUNTY COUNTY COUNTY Postal Code POSTAL_CODE POSTAL_CODE POSTAL_CODE Country COUNTRY COUNTRY (through value map Oracle Country) COUNTRY (through value map Oracle Country) Main Phone Number See Telephone Number Mapping for R10.7.
Value map: Oracle Address Phone Main Fax Number Address Active Status STATUS (No Oracle interface available) STATUS Siebel Field (Contact) Oracle Base Column (RA_CONTACTS) Siebel to Oracle Integration (RA_CONTACT_PHONES_
INT_ALL) Oracle to Siebel Integration (RA_CONTACTS) Id ORIG_SYSTEM_ REFERENCE ORIG_SYSTEM_
CONTACT_
REF ORIG_SYSTEM_REFERENCE Integration Id CONTACT_ID CONTACT_ID M/M TITLE CONTACT_TITLE (through value map Oracle Contact Title) TITLE Job Title JOB_TITLE CONTACT_JOB_TITLE JOB_TITLE Last Name LAST_NAME CONTACT_LAST_NAME LAST_NAME First Name FIRST_NAME CONTACT_FIRST_NAME FIRST_NAME M/F SEX_CODE SEX_CODE SEX_CODE Email Address EMAIL_ADDRESS EMAIL_ADDRESS EMAIL_ADDRESS Mail Stop MAIL_STOP MAIL_STOP MAIL_STOP Contact Organization Integration Id ORG_ID ORG_ID ORG_ID Active Status STATUS (No Oracle interface available) STATUS Comment CONTACT_PERSONAL_ INFORMATION (No Oracle interface available) CONTACT_PERSONAL_
INFORMATION Created By CREATED_BY CREATED_BY (through value map Oracle User ID) Updated By LAST_UPDATED_BY LAST_UPDATED_BY (through value map Oracle User ID) Created CREATION_DATE CREATION_DATE Updated LAST_UPDATE_DATE LAST_UPDATE_DATE Cellular Phone # See Telephone Number Mapping for R10.7.
Value map: Oracle Address Phone Fax Phone # Home Phone # Work Phone # Alternate Phone # Assistant Phone #Oracle Customer Profiles for R10.7
A customer profile with class Default is created in Oracle Applications for each new customer and each new address with BILL_TO site use using the RA_CUSTOMER_PROFILES_INT_ALL interface table.
Telephone Number Mapping for R10.7
The Siebel Applications and Oracle Applications data models differ with respect to their storage of telephone numbers. In Siebel, telephone numbers are stored as fields within the Account, Business Address, and Contact business components. In Oracle, telephone numbers are stored in a separate RA_PHONES table that is joined to the customer, address, and contact tables. The PHONE_TYPE column is used to identify the type of the phone number: FAX, GEN, and so on.
To facilitate integration between these entities, EAI value maps have been created between Siebel Applications field names and Oracle Applications phone types for each phone number field in the Account, Business Address and Contact business component. For each non-null phone field in Siebel, a new RA_PHONES record is created in Oracle Applications and the PHONE_TYPE is set accordingly.
For example, suppose the field Main Phone Number is set to 123 456 7890 in the Siebel Applications Account user interface. When the account is updated in Oracle a new RA_PHONES record will be created and linked with the customer table. Main Phone Number maps to GEN in the Oracle Applications Account Phone EAI value map and so the PHONE_TYPE will be GEN. The PHONE_NUMBER column will be set to 1234567890.
Site Use Mapping for R10.7
Oracle Applications support the concept of multiple site uses for an address through the RA_SITE_USES_ALL table. In Siebel Applications, this is expressed through the Bill Address Flag, Ship Address Flag, and Main Address Flag fields on the Business Address business component and corresponds to the BILL_TO, SHIP_TO, and GENERAL site uses respectively. The Primary Bill To Address Id, Primary Ship To Address Id, and Primary Address Id fields on the Account business component identify the address of each type that will perform the primary role. This corresponds with the PRIMARY_SITE_USE_FLAG = Y in the RA_SITE_USES_ALL table.
Site uses for an address must be set before the address is submitted to Oracle Applications. Once the address has been submitted to Oracle Applications no changes are supported. At least one site use must be specified for each address.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Connector for Oracle Applications Published: 18 April 2003 |