My Oracle Support Banner

Custom BiPublisher Reports Are Not Working With ROD Database. (Doc ID 1274355.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Fusion Transportation Intelligence - Version 6.1.1 and later
Information in this document applies to any platform.

Symptoms

On : 6.1.1 version,

Custom BI publisher reports are not working with ROD database, the following error occurs in the bipublisher.log file.

ERROR
-----------------------
BI Publisher Error during Content Generation

102810_141227999][STATEMENT Logger.init(): *** DEBUG MODE IS OFF. ***
102810_141227999][STATEMENT Template parsing started...
102810_141228000][STATEMENT Data Template ......
102810_141228000][STATEMENT oracle.xml.parser.v2.XMLDocument@5fab116a
102810_141228000][STATEMENT Inside properties Parser...

102810_141228000][STATEMENT xml_tag_case=upper
102810_141228000][STATEMENT debug=on
102810_141228000][STATEMENT Inside parameterParser...
102810_141228000][STATEMENT Parameter:P_GL_USER Default value: DBA.ADMIN
102810_141228000][STATEMENT Parameter:P_ROLE_ID Default value: ADMIN
102810_141228000][STATEMENT Parameter:P_L_SOURCE_LOCATION Default value: 1=1
102810_141228000][STATEMENT Parameter:P_L_BUSINESS_UNIT Default value: 1=1
102810_141228000][STATEMENT Parameter:P_L_START_TIME Default value: 1=1
102810_141228000][STATEMENT Parameter:P_L_PROFIT_CENTER Default value: 1=1
102810_141228000][STATEMENT Parameter:P_L_TRANSPORT_MODE Default value: 1=1
102810_141228000][STATEMENT Parameter:P_L_CARRIER Default value: 1=1
102810_141228000][STATEMENT Parameter:P_L_DEST_LOCATION_GID Default value: 1=1
102810_141228000][STATEMENT Parameter:P_L_DEST_LOCATION_NAME Default value: 1=1
102810_141228000][STATEMENT Parameter:P_L_DEST_COUNTRY_CODE Default value: 1=1
102810_141228000][STATEMENT Parameter:P_L_SOURCE_COUNTRY_CODE Default value: 1=1
102810_141228000][STATEMENT Inside dataQueryParser...
102810_141228000][STATEMENT Inside dataStructureParser...
102810_141228000][STATEMENT Group ...report
102810_141228001][STATEMENT Group ...G_shipment_gid
102810_141228001][STATEMENT Template parsing completed...
102810_141228001][STATEMENT Setting Data Template
102810_141228001][STATEMENT Setting JDBC Connection
102810_141228002][STATEMENT Start process Data
102810_141228002][STATEMENT Process Data ...
102810_141228002][STATEMENT Executing data triggers...
102810_141228002][STATEMENT BEGIN
SSCC_SETTLEMENT_REPORT_V2.P_GL_USER := :P_GL_USER ;
SSCC_SETTLEMENT_REPORT_V2.P_ROLE_ID := :P_ROLE_ID ;
SSCC_SETTLEMENT_REPORT_V2.P_L_SOURCE_LOCATION := :P_L_SOURCE_LOCATION ;
SSCC_SETTLEMENT_REPORT_V2.P_L_BUSINESS_UNIT := :P_L_BUSINESS_UNIT ;
SSCC_SETTLEMENT_REPORT_V2.P_L_START_TIME := :P_L_START_TIME ;
SSCC_SETTLEMENT_REPORT_V2.P_L_PROFIT_CENTER := :P_L_PROFIT_CENTER ;
SSCC_SETTLEMENT_REPORT_V2.P_L_TRANSPORT_MODE := :P_L_TRANSPORT_MODE ;
SSCC_SETTLEMENT_REPORT_V2.P_L_CARRIER := :P_L_CARRIER ;
SSCC_SETTLEMENT_REPORT_V2.P_L_DEST_LOCATION_GID := :P_L_DEST_LOCATION_GID ;
SSCC_SETTLEMENT_REPORT_V2.P_L_DEST_LOCATION_NAME := :P_L_DEST_LOCATION_NAME ;
SSCC_SETTLEMENT_REPORT_V2.P_L_DEST_COUNTRY_CODE := :P_L_DEST_COUNTRY_CODE ;
SSCC_SETTLEMENT_REPORT_V2.P_L_SOURCE_COUNTRY_CODE := :P_L_SOURCE_COUNTRY_CODE ;

:XDO_OUT_PARAMETER := 1;
END;

102810_141228002][STATEMENT 1:SSCC.SBEAVER :
102810_141228002][STATEMENT 2:SSCC.SUPER_USER :
102810_141228002][STATEMENT 3:1=1 :
102810_141228002][STATEMENT 4:begins with~'0517' :
102810_141228002][STATEMENT 5:SAME AS~'2010-05-01' :
102810_141228002][STATEMENT 6:1=1 :
102810_141228002][STATEMENT 7:1=1 :
102810_141228002][STATEMENT 8:1=1 :
[102810


After applying the debugging patch 10270199 to get the SQL exception that occurs and not showing in the log, the below error seen.

cause.BIPublisherContentGenerationError

oracle.apps.xdo.XDOException: ORA-06550: line 2, column 1: PLS-00201: identifier 'SSCC_SETTLEMENT_REPORT_V2.P_GL_USER' must be declared ORA-06550: line 2, column 1: PL/SQL: Statement ignored ORA-06550: line 3, column 1: PLS-00201: identifier 'SSCC_SETTLEMENT_REPORT_V2.P_ROLE_ID' must be declared ORA-06550: line 3, column 1: PL/SQL: Statement ignored ORA-06550: line 4, column 1: PLS-00201: identifier 'SSCC_SETTLEMENT_REPORT_V2.P_L_SOURCE_LOCATION' must be declared ORA-06550: line 4, column 1: PL/SQL: Statement ignored ORA-06550: line 5, column 1: PLS-00201: identifier 'SSCC_SETTLEMENT_REPORT_V2.P_L_BUSINESS_UNIT' must be declared ORA-06550: line 5, column 1: PL/SQL: Statement ignored ORA-06550: line 6, column 1: PLS-00201: identifier 'SSCC_SETTLEMENT_REPORT_V2.P_L_START_TIME' must be declared ORA-06550: line 6, column 1: PL/SQL: Statement ignored ORA-06550: line 7, column 1: PLS-00201: identifier 'SSCC_SETTLEMENT_REPORT_V2.P_L_PROFIT_CENTER' must be declared ORA-06550: line 7, column 1: PL/SQL: Statement ignored ORA-06550: line 8, column 1: PLS-00201: identifier 'SSCC_SETTLEMENT_REPORT_V2.P_L_TRANSPORT_MODE' must be declared ORA-06550: line 8, column 1: PL/SQL: Statement ignored ORA-06550: line 9, column 1: PLS-00201: identifier 'SSCC_SETTLEMENT_REPORT_V2.P_L_CARRIER' must be declared ORA-06550: line 9, column 1: PL/SQL: Statement ignored ORA-06550: line 10, column 1: PLS-00201: identifier 'SSCC_SETTLEMENT_REPORT_V2.P_L_DEST_LOCATION_GID' must be declared ORA-06550: line 10, column 1: PL/SQL: Statement ignored ORA-06550: line 11, column 1: PLS-00201: identifier 'SSCC_SETTLEMENT_REPORT_V2.P_L_DEST_LOCATION_NAME' must be declared ORA-06550: line 11, column 1: PL/SQL: Statement ignored

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.