Oracle EBS Interface Connector User Guide V1.4

Transcription

1 Oracle EBS Interface Connector User Guide V1.4

2 Contents Oracle EBS Interface Connector User Guide V Introduction Technologies High level Architectural Diagram About Oracle EBS Interface Tables in Oracle EBS Oracle EBS connector pre-requisites Creating Oracle EBS Interface Connection Connector Read notes Connector Write notes DBA Activity Description of.ini files Assumptions & Limitations... 19

3 1. Introduction Informatica Cloud Connector SDKs are off-cycle, off-release add-ins that provide connectivity to SaaS and on-premise applications not supported natively in Informatica Cloud. Connector SDKs can be enabled anytime for your cloud org Id, and are designed to address common use cases including getting data into, and out of, the supported application. Connector SDKs do not require any separate software installation on the machine running the Informatica Cloud Secure Agent. The Connector uses an internal Java application to communicate with the Secure Agent, as shown in the architecture diagram below: Once you have enabled the Connector Package software for your org Id, you need to create a connection in Informatica Cloud to access to the Oracle EBS Interface.

4 2. Technologies Connector is developed using - JDK High level Architectural Diagram Compatibility: This connector supports Oracle EBS Interface 4. About Oracle EBS Oracle E-Business Suite (also known as Applications/Apps or EB-Suite/EBS) consists of a collection of enterprise resource planning (ERP), customer relationship management (CRM), and supply-chain management (SCM) computer applications. The software utilizes Oracle's core Oracle relational database management system technology. The E-Business Suite 3 contains several product lines, including:

5 Oracle CRM Oracle Financials Oracle HRMS Oracle Mobile Supply Chain Applications Oracle Order Management Oracle Procurement Oracle Project Portfolio Management Oracle Quotes Oracle Transportation Management Oracle Warehouse Management Systems Oracle Inventory. Oracle Enterprise Asset Management Each product comprises several modules Significant technologies incorporated into the applications include the Oracle database technologies, (engines for RDBMS, PL/SQL, Java,.NET, HTML and XML), the "technology stack" (Oracle Forms Server, Oracle Reports Server, Apache Web Server, Oracle Discoverer, Initiator and Sun's Java). 5. Interface Tables in Oracle EBS Oracle Applications use open interface tables to insert data in Oracle Applications. For example, by using interface tables, you can insert a purchase order into Oracle Applications to generate the sales order automatically. Data is never loaded directly into Oracle Applications base tables. Instead, data is first loaded into interface tables, and then Oracle-supplied concurrent programs move data from interface tables to base tables. This ensures that all business logic and processing is handled using Oracle components. Interface tables are intermediate tables into which the data is inserted first. Once the data gets inserted into the interface tables, the data is validated, and then transferred to the base tables. Base tables are real application tables that reside in the application database. The data that resides in the interface tables is transferred to the base tables using concurrent programs. A concurrent program is an instance of an execution file. Concurrent programs are scheduled in Oracle Applications to move data from interface tables to base tables. These programs perform the application-level checks and run validation before inserting data into base tables. OracleEBSInterface connector helps in transforming data from source system to target systems. Below are some of the list of some interface tables available in oracleebs Entity Name / Interface table name RA_CUSTOMERS_INTERFACE_ALL RA_CUSTOMER_PROFILES_INT_ALL OE_HEADERS_IFACE_ALL OE_LINES_IFACE_ALL OE_PRICE_ADJS_IFACE_ALL OE_PAYMENTS_INTERFACE OE_CREDITS_IFACE_ALL

6 OE_LOTSERIALS_IFACE_ALL This list is for example, Oracle EBS provides number of standard tables for read operation. 6. Oracle EBS connector pre-requisites Following are the pre-requisites to use oralceebsinterface connector Connector user should have a valid account and credentials with Oracle EBS application. Connector user should have a valid application user name 7. Creating Oracle EBS Interface Connection Before you use the Oracle EBS connector in a data synchronization task, connection must be established with OracleEBS. User should follow these steps to create an oracle EBS connection in Informatica Cloud: 1. Login to Informatica Cloud application 2. Click on the Configuration tab. 3. Click on the Connections page. 4. Click the New button. Connection Property Connection Name Description (optional) Type Secure Agent Oracle Host Name Oracle Port No Oracle Service Name Username Password Application Username Description Provide the Name of the connection Provide the description Select Oracle Interface Table (Informatica Cloud) Secure Agent that Informatica Cloud uses to access the Web Service. Provide the Oracle Host Name Provide the Oracle Port No Provide the Oracle Service Name Provide the Oracle user name Provide the Oracle password Provide the application user name of the Oracle EBS

7 Connection Property Service Config File Name EBSInterfaceTablesConfig.ini Description Name of configuration file with extension: EBSInterfaceTablesConfig.ini Purpose: This configuration is used to 1. Set Connection properties to Oracle EBS 2. To add Interface table names 3. Interface table name is used only in case of write operation Location : This configuration file should be placed in $ \Informatica Cloud Secure Agent\main\bin\rdtm-extra\reserved\userfiles\oraclEBS For more details about configuring refer section Connector Write Notes Parameter Config File Name: EBSConcurrentProgramConfig.ini Name of configuration file with extension: EBSConcurrentProgramConfig.ini Purpose: This configuration is used to 1. To pass parameters to call concurrent program 2. This configuration file is used only in write operation. Location : This configuration file should be placed in $ \Informatica Cloud Secure Agent\main\bin\rdtm-extra\reserved\userfiles\oracleEBS For more details about configuring refer section Connector Write Notes

8 After entering all valid values, press Test. diagram User should get connection successful message as shown in the following 8. Connector Read notes Oracle EBS interface read method will return all the records from oracle EBS system to target system. Note: Oracle EBS interface connector doesn t support filtering the records using data filter. 1. Only oracle EBS standard table or view can be read using this connector 2. Systems objects will be omitted while fetching list of tables/views 3. All table and view names will be prefixed with schema name.

9

10 2. Filed mapping & data should be proper and appropriate to perform CRUD operation

11 9. Connector Write notes Insert operation writes data from the source system to target oracle EBS application using OralceEBSInterface Connector. Inserting data is two step process in oracle EBS interface connector. 1. Load source data into interface table 2. Call concurrent program once data is loaded into interface table Source data should be in prescribed format to be loaded into interface table. The source file structure of insert file should be like below Example: RA_CUSTOMERS_INTERFACE_ALL _TAB_ColumnName1, RA_CUSTOMERS_INTERFACE_ALL _TAB_ColumnName2, RA_CUSTOMER_PROFILES_INT_ALL_TAB_ColumnName1, RA_CUSTOMER_PROFILES_INT_ALL_TAB_ColumnName2 RA_CUSTOMERS_INTERFACE_ALL and RA_CUSTOMER_PROFILES_INT_ALL are interface tables for customer Pre requisites for Insert Filed mapping & data should be proper and appropriate to perform CRUD operation The input parameter value of RA_CUSTOMERS_INTERFACE_ALL _TAB_INSERT_UPDATE_FLAG, RA_CUSTOMER_PROFILES_INT_ALL_TAB_INSERT_UPDATE_FLAG column must be changed to I in

12 RA_CUSTOMERS_INTERFACE_ALL, RA_CUSTOMER_PROFILES_INT_ALL tables respectively for customer interface The value of WIP_JOB_SCHEDULE_INTERFACE_TAB_LOAD_TYPE must be changed to 1 in input parameter for WIP interface All the input dates format must be in this format DD-MON-YY (For Eg: 10-Jan-15)

13

14 The entire interface table column name will be displayed in the Target section

15 2. Update The input parameter value of RA_CUSTOMERS_INTERFACE_ALL _TAB_INSERT_UPDATE_FLAG, RA_CUSTOMER_PROFILES_INT_ALL_TAB_INSERT_UPDATE_FLAG column must be changed to U in RA_CUSTOMERS_INTERFACE_ALL, RA_CUSTOMER_PROFILES_INT_ALL tables respectively for customer interface The input parameter value of RA_CUSTOMERS_INTERFACE_ALL_TAB_ SITE_USE_CODE and RA_CUSTOMERS_INTERFACE_ALL_TAB_ PRIMARY_SITE_USE_FLAG must be blank for customer interface The value of WIP_JOB_SCHEDULE_INTERFACE_TAB_LOAD_TYPE must be changed to 3 in input parameter for WIP interface All the input dates format must be in this format DD-MON-YY (For Eg: 10-Jan-15) 3. Delete OracleEBS Interface connector doesn t support delete operation. To delete data from OracleEBS use OracleEBS Interface Connector 10. DBA Activity Newly created user should have only access to read all the Base Tables or Views and write access to all the Interface tables in the ini file. Steps to create a new user in DB: a. Connect to database as sysdba b. Create user <username> identified by <password>; grant create session to <username>; Granting Different privileges to user a. Connect to database as sysdba b. GRANT SELECT ON [Schema].[Table] TO [User] GRANT INSERT ON [Schema].[Table] TO [User] Steps to Configure the INI File with Parameters A user should first list out the list of interface table and programs associated to it. It will be available in the R12 Release Notes or from Oracle Metalink or from Document Repository that comes along with installation Check for the program name if it has multi org feature User should have the "Application Developer" Responsibility Navigate to Concurrent > Program

16 Parameters

17 Apart from the above list of parameters, few programs in R12 they have Multi org capabilities. Specific to those programs we need to set one more parameter called MORG ID.You can find it in two ways 1. From Frontend, if you select the program and see if Operating Unit Field is enabled, then MORG_ID needs to be a parameter 2. From Backend, check the below query Select MULTI_ORG_CATEGORY from FND_CONCURRENT_PROGRAMS where concurrent_program_name=<<programshortname Ex: RACUST as input>> If the value of MULTI_ORG_CATEGORY is 'S' then MORG_ID needs to be parameter

18 11.Description of.ini files 1. Name of configuration file with extension: EBSInterfaceTablesConfig.ini Purpose: This configuration is used to 1. Set Connection properties to Oracle EBS 2. To add Interface table names 3. Interface table name is used only in case of write operation Location: This configuration file should be placed in $ \Informatica Cloud Secure Agent\main\bin\rdtm-extra\reserved\userfiles\oraclEBS Format: Schema, Concurrent Program Name, FALSE_TABLELIST_Customer Interface table 1, Customer Interface table 2...Customer Interface table n Example: AR,RACUST,CustomerInterface,FALSE_TABLELIST_RA_CUSTOMERS_INTERFACE_ALL,RA_CUSTOMER_PROFILES_INT_ALL

19 2. Name of configuration file with extension: EBSConcurrentProgramConfig.ini Purpose: This configuration is used to 1. To pass parameters to call concurrent program 2. This configuration file is used only in write operation. Location: This configuration file should be placed in $ \Informatica Cloud Secure Agent\main\bin\rdtm-extra\reserved\userfiles\oracleEBS Format: Name of the Module_ PARAMLIST_Parameter List Start, Parameter 1, Parameter2..., Parameter n, Parameter List End Example: CustomerInterface_PARAMLIST_Parameter List Start, CREATE_RECIPROCAL_CUSTOMER :=N,ORG_ID :=204,Parameter List End 12. Assumptions & Limitations 1. Connector supports and compatible with Oracle EBS Connector user should have a valid account and credentials to make the connection and perform CRUD operations. 3. Field mapping & data should be proper and appropriate to perform CRUD operation. 4. Read operation won t support data filter and joining multiple tables (ie extended join is not supported) 5. Interface tables will not be available for all EBS modules; connector will support all standard interface tables. 6. Execution of concurrent program depends on Oracle EBS. Once the concurrent program invoked, execution starts based on the turn in the queue. a. When a new operation likes order, customer to be performed, changes has to be made in EBSInterfaceTablesConfig.ini file 7. Purging will be done in the interface table by the Oracle EBS System 8. Getting the Count of Success and Error Records is based on the interface table that remains after successful insertion into base table. If user prefers to insert data into interface tables using multiple DSS tasks, success and error counts from interface table to base table load will be calculated based on the final DSS task. There will be count mismatch in this case which is a known issue. Few Interfaces are not deleting the success rows automatically after a successful insertion in which the above count logic will not work which is a known bug in Oracle E.g. supplier interface. 9. In the case of midstream field list will be in following format. TableName1 1, ColumnName1, ColumnName2, TableName1 2 TableName1 1 is the Open tag and TableName1 2 is the closing tag. 10. Any issue causing exceptions or data error will be logged in tomcat.log file and any unsuccessful CRUD operations will be logged in session log(eg:concurrent Program failure for Request ID:X)