Bookshelf Home | Contents | Index | PDF |
Siebel Connector for Oracle Applications > Detailed Data Mappings > Entity Attribute Mappings for Oracle Applications R10.7 > Account Integration EAM MappingsOracle Customers and Siebel Account business objects are integrated. The associated EAM mappings are shown in Table 17 and Table 18. Entity Mapping
Attribute Mapping
Oracle Customer Profiles for R10.7A 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.7The 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.7Oracle 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. |
Siebel Connector for Oracle Applications |