EBS-DRM Integration: Configuration Checklist and Troubleshooting

EBS-DRM Integration: Configuration Checklist and Troubleshooting [ID 1378989.1]
		Modified 27-DEC-2011     Type WHITE PAPER     Status PUBLISHED

Applies to:

Oracle General Ledger - Version: 12 and later   [Release: 12.0 and later ]
Oracle Fusion General Ledger - Version: 11.1.1.5.1 and later    [Release: 1.0 and later]
Oracle Fusion Accounting Hub - Version: 11.1.1.5.1 and later    [Release: 1.0 and later]
Information in this document applies to any platform.

Abstract

This document provides a Checklist and instructions for Troubleshooting the basic setups for the EBS General Ledger to Hyperion Data Relationship Management (DRM) Integration.  

Document History

 Author:  Varun Netan
 Create Date 17-Nov-2011
 Update Date 27-Dec-2011
 Expire Date 31-DEC-2015 (ignore after this date)

EBS-DRM Integration: Configuration Checklist and Troubleshooting

CHECKLIST FOR THE HYPERION AND EBS DRM SETUP

The following is a checklist for the Basic Setup for the EBS-DRM Integration

HYPERION DRM SETUP	EXAMPLE
Deploy DRM web-service with proper WSS Security policy	wss_saml_or_username_token_service_policy
Apply the latest integration application template. This file can be found in the location: $COMMON_TOP/java/classes/java/classes/oracle/apps/gl/drm	OracleGL_DRM_AppTemplate.xml
Set up an LDAP user for CSS authentication with appropriate roles/privileges. Obtain User ID/password	drmdemo/welcome1
Obtain WSDL URL	http://adc9999999.us.oracle.com:28080/oracle-epm-drm-webservices/DrmService?wsdl
Obtain DRM API Adapter URL	http://adc9999999.us.oracle.com:5242/Oracle/Drm/APIAdapter
Set up external connection - EBSDBConnection - with proper connect string.	Data Source=rws60039rems.us.oracle.com:1597/fg0yd213
Test external connection and export definitions	Connection: EBSDBConnection Exports: EBSValueSetExport, EBSHierarchyExport
EBS GENERAL LEDGER SETUP	EXAMPLE
For EBS 12.1.x, apply the integration patch. (Not required for 12.2+)	11659733:R12.GL.B Pre-req: 10632813:R12.OWF.B
Enter unseeded DRM Profile Option Values	GL: DRM API Adapter URL GL: DRM WSDL URL GL: DRM Username
Verify Seeded DRM Profile Option Values	GL: DRM Property for Value Set Name GL: DRM Template for Version Export GL: DRM Template for Hierarchy Export GL: DRM Property to Allow Version Export GL: DRM Property to Allow Hierarchy Export
Store password for DRM user in FND_VAULT	sqlplus apps/apps@fg0yd213 @$FND_TOP/sql/afvltput.sql SQLGL drmdemo welcome1

 

CHECKLIST FOR THE FUSION-DRM INTEGRATION  SETUP

The following is a checklist for the Basic Setup for the Fusion-DRM Integration

HYPERION DRM SETUP	EXAMPLE
Deploy DRM web-service with proper WSS Security policy	wss_saml_or_username_token_service_policy
Apply the latest integration application template	OracleGL_DRM_AppTemplate.xml
Setup an LDAP user for CSS (external) authentication with appropriate roles/privileges. User ID/password should be the same as Fusion GL user	finuser1/Welcome1
Obtain WSDL URL	http://adc8888888.us.oracle.com:28080/oracle-epm-drm-webservices/DrmService?wsdl
Obtain DRM API Adapter URL	http://adc8888888.us.oracle.com:5242/Oracle/Drm/APIAdapter
Setup external connection - FusionDBConnection - with proper connect string.	Data Source=rws65053fwks.us.oracle.com:1522/rws65053
Test external connection and export definitions	Connection: FusionDBConnection Exports: FusionValueSetExport, FusionHierarchyExport
FUSION GENERAL LEDGER SETUP	EXAMPLE
Verify Fusion user credentials are the same as DRM user	finuser1/Welcome1
Enter unseeded DRM Profile Option Value	GL: DRM API Adapter URL
Verify Seeded DRM Profile Option Values	GL: DRM Property for Value Set Name GL: DRM Template for Version Export GL: DRM Template for Hierarchy Export GL: DRM Property to Allow Version Export GL: DRM Property to Allow Hierarchy Export
Update the DrmService connection to the DRM WSDL URL in Fusion Enterprise Manager. Refer to this document for the steps on how to do so.	http://adc8888888.us.oracle.com:28080/oracle-epm-drm-webservices/DrmService?wsdl

TROUBLESHOOTING THE EBS DRM INTEGRATION SETUPS

The Load Segment Values and Hierarchies program will result in an error, if there is a mismatch in the Setup details between EBS and DRM, or if a component is not correctly set up.  The output of the program called the Execution Report will list the details of the exception. An example of the report is listed below:


The following are some common exceptions that would be listed on the Execution Report.

1. Exception: The security token is not valid

The Exception Details given here are only indicative of what would show on the execution report. The actual text might vary slightly on a case-to-case basis.
Exception Details* Exception when Invoking Web Service -> oracle.apps.fnd.wf.bes.InvokerException: javax.xml.rpc.soap.SOAPFaultException: InvalidSecurityToken : The security token is not valid.

Cause DRM was unable to authenticate using the credentials set up in EBS.

• GL: DRM Username profile option
• DRM Password stored in FND_VAULT.

Fix Enter the correct DRM username and password values, which are set up in EBS.

How to verify that the value is correct

1. Check the value of the system profile option GL: DRM Username in EBS.
2. Ensure that the DRM password is stored in FND_VAULT. To confirm the stored password value, run the following query on the EBS database:

SELECT fnd_vault.get('SQLGL','&DRM_USERNAME') FROM dual;
Here &DRM_USERNAME = value of profile GL: DRM Username.

    3. Using the username and password that is returned, verify that you are able to login to the DRM UI manually.

2. Exception: Error while trying to communicate with DRM API Adapter

Exception DetailsException when Invoking Web Service -> oracle.apps.fnd.wf.bes.InvokerException: javax.xml.rpc.soap.SOAPFaultException: Cannot getVersionNames. Error while trying to communicate with DRM API Adapter at: http://adcdae09.us/
Cause The value for GL: DRM API Adapter URL is not valid.
Fix
Enter the correct adapter URL for the profile value
How to verify that the value is correct Enter the API Adapter URL directly in a browser. A page similar to the example below should display:

3. Exception: Failed to read WSDL

Exception DetailsException when Invoking Web Service -> oracle.apps.fnd.wf.bes.InvokerException: oracle.j2ee.ws.wsdl.LocalizedWSDLException: WSDLException:faultCode=OTHER_ERROR: Failed to read WSDL from http://adcdae09.us.oracle.com:7001/oracle-epm-drm-webservices?WSDL: HTTP connection error code is 403
Cause The value for GL: DRM WSDL URL is not correct
Fix Enter the correct WSDL URL for the profile value
How to verify that the value is correct Enter the WSDL URL directly in a browser.  A page similar to the example below should display:

4. Exception:  DRM-12103: 'PropDef' item 'asd' was not found.

Exception Details Exception when Invoking Web Service -> oracle.apps.fnd.wf.bes.InvokerException: javax.xml.rpc.soap.SOAPFaultException: Cannot getVersionProps. DRM-12103: 'PropDef' item 'asd' was not found.
Cause The value for one of the version property override profiles is not valid. Check the following profiles:

• GL: DRM Property for Value Set Name
• GL: DRM Property to Allow Version Export

Fix Enter the fully-qualified DRM version-level property names for the profiles
How to verify that the value is correct 1. Connect to the DRM UI.
2. Navigate Administer -> Property Definitions -> <Specific Property>
3. Verify that the fully-qualified name matches the profile value, and that the Property Level='Version'.

5. Exception: DRM-12103: 'PropDef' item 'allowHierExport1' was not found.

Exception DetailsException when Invoking Web Service -> oracle.apps.fnd.wf.bes.InvokerException: javax.xml.rpc.soap.SOAPFaultException: Cannot getHierProps. DRM-12103: 'PropDef' item 'allowHierExport1' was not found.
Cause The value for one of the hierarchy property override profiles is not valid. Check the following profile:

• GL: DRM Property to Allow Hierarchy Export

Fix Enter the correct fully-qualified DRM hierarchy level property name for this profile.

How to verify that the value is correct 1. Connect to the DRM UI.
2. Navigate Administer -> Property Definitions -> <Specific Property>
3. Verify Fully-Qualified Name matches profile value and Property Level = 'Hierarchy'

6. Exception: Cannot startExportByName. Export specified not found

Exception DetailsException when Invoking Web Service -> oracle.apps.fnd.wf.bes.InvokerException: javax.xml.rpc.soap.SOAPFaultException: Cannot startExportByName. Export specified not found.

Cause The value for one of the following profiles is not valid:

• GL: DRM Template for Version Export
• GL: DRM Template for Hierarchy Export

Fix Enter the correct DRM version and hierarchy export names in the profiles.
How to verify that the value is correct 1. Connect to DRM UI.
2. Navigate Export -> Exports defined for EBS
3. Verify Export Names matches profile values.

7. Exception: ORA-12560: TNS:protocol adapter error

Exception Details DRM-23073: Export was unable to run due to the following error: ORA-12560: TNS:protocol adapter error

Cause The EBS export definitions in DRM for Version Export and Hierarchy Export are unable to connect to EBS due to some error in the external connection.

Fix Verify that the external connection to the EBS DB (database) is correct.
How to verify that the value is correct 1. Connect to the DRM UI
2. Navigate Export -> Exports defined for EBS
3. Go to the Target Tab. Note the connection name and click on Test Connection. If it fails then, try step 4 below.


4. Navigate Administer -> External Connections. Check that all necessary information is present in the EBS Database Connection:
a. Connection String
b. User ID
c. Selected tables
Save and Test connection to verify

UNDERSTANDING THE PROCESS THAT LOADS VALUES FROM DRM TO EBS

After the DRM interface tables are populated, the data is read, validated and then passed to a GL PL/SQL API which is essentially a wrapper over the FND Flex APIs (see sample)
The dataflow between tables is as follows:

• GL_DRM_SEGVALUES_INTERFACE =====> FND_FLEX_VALUES
• GL_DRM_HIERARCHY_INTERFACE =====> FND_FLEX_VALUE_NORM_HIERARCHY

For FND_FLEX_VALUES, every value from GL_DRM_SEGVALUES_INTERFACE is either inserted (if it doesn't exist in the FND table) or updated (if the value already exists in the FND table).
For FND_FLEX_VALUE_NORM_HIERARCHY, the existing hierarchy is cleared and then re-created on the basis of all the parent-child relationship records, which have been exported into the GL_DRM_HIERARCHY_INTERFACE table.

Summary

Here are some documents that may be helpful with your configuration of the EBS-DRM Integration:

• Deploying and Configuring the Hyperion Data Relationship Management Web Service API
• Oracle Hyperion Data Relationship Management, Fusion Edition 
• EBS: Hyperion Data Management Integration with the Oracle Fusion and E-Business Suite General Ledgers - Document 1315694.1
  
  

References

NOTE:1315694.1 - EBS: Hyperion Data Management Integration with the Oracle Fusion and E-Business Suite General Ledgers

Related Products Oracle E-Business Suite > Financial Management > Financial Control and Reporting > Oracle General Ledger Oracle Fusion Applications > Financials Management > Ledger > Oracle Fusion General Ledger Oracle Fusion Applications > Financials Management > Ledger > Oracle Fusion Accounting Hub Keywords EBS; FUSION APPLICATIONS; INTEGRATION; LEDGER; ORACLE GENERAL LEDGER; SERVICES; WEB SERVICES; WSDL Errors ORA-12560

Back to top