Monthly Archives: September 2015

Oracle EBS: Concurrent Program – GL Code Combination Parameter

Home Page comment faire une rencontre avec une femme site rencontre guinee http://theeasybreezyway.com/?parkyw=com-conocer-gente-nueva&eb4=dc rencontre koweit http://comfycozycouture.com/CCC/kipiwer/6980 http://gtheal.com/?marakanr=crossing-paths-dating-app&89d=f9 madame bovary rencontre entre charles et emma analyse rencontre femme sur cam official site Scenario

The requirement is to pass code combination as an input parameter to the concurrent program report.

 

Case 1 – To pass the code combination segment values as-is based on the code combination passed as a parameter. The requirement is not to validate the input combination and no dynamic insert

Create a ValueSet – Special Validation Type

Create Event Edit

FND POPID
APPL_SHORT_NAME=SQLGL
CODE=”GL#”
NUM=:$FLEX$.GL_SRS_CHART_OF_ACCOUNTS_ID
REQUIRED=N
VALIDATE=NONE
SEG=:!VALUE
DESC=:!MEANING
DATA_FIELD=:!ID
DINSERT=N

Create Event Load

FND LOADID
APPL_SHORT_NAME=SQLGL
CODE=”GL#”
NUM=:$FLEX$.GL_SRS_CHART_OF_ACCOUNTS_ID
REQUIRED=N
VALIDATE=NONE
SEG=:!VALUE
DESC=:!MEANING
DATA_FIELD=:!ID
DINSERT=N

Special_Validation_Routine

Case 2 – To pass the code combination ID based on the code combination passed as a parameter

Refer to Standard Concurrent Program Report – GL Cash Clearing Account Analysis Report

Value Set – GL_SRS_FLEXFIELD

Oracle EBS: OAF VO Extension of Java File – oracle.jbo.SQLStmtException: JBO-27122: SQL error


Scenario

In a situation where the iProcurement page has been extended to display the requisitions to preparer, the following error has occurred:

Error Page

Exception Details.
oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: SELECT * FROM (select
requisition_header_id,
segment1,
description,
creation_date,
POR_VIEW_REQS_PKG.GET_REQ_TOTAL(REQUISITION_HEADER_ID) req_total,
POR_RCV_POST_QUERY_PKG.getOrderNumber(REQUISITION_HEADER_ID) order_num_release_num,
POR_RCV_POST_QUERY_PKG.getSupplier(REQUISITION_HEADER_ID) supplier,
ORG_ID OPERATING_UNIT
from
po_requisition_headers) QRSLT WHERE (requisition_header_id in (select requisition_header_id from por_rcv_reqs_all_v where ( to_person_id = :1 or preparer_id = :1 ) ))

## Detail 0 ##
java.sql.SQLException: Missing IN or OUT parameter at index:: 2

Receiving_Tab

Cause

Ensure the bind variables have a different name when Oracle Positional is chosen as a binding style while extending the standard View Object

( to_person_id = :1 or preparer_id = :1 )

Fix

The binding name needs to unique when used in a query. Although the value to be provided is same to the SQL, use a different binding name to resolve the above error.