Applies to:
Oracle General Ledger - Version 12.0 to 12.0 [Release 12.0]Information in this document applies to any platform.
Standard Reports
***Checked for relevance on 7-Feb-2012***
Symptoms
When submitting the Account Analysis Report, the following errors occur:Error
------
APP-FND-00798 : Invalid reference gl_srs_coa_id_bysob in valueset attached to segment flexfield
form.
APP-FND-00730 This flexfield has an invalid valueset
Changes
NoneCause
This is the Value for GL_SRS_LEDGER_FLEXFIELD Value set:FND POPIDR APPL_SHORT_NAME="SQLGL" CODE="GL#"
NUM=:$FLEX$.GL_SRS_COA_ID_BYSOB REQUIRED="Y"
VALIDATE="NONE" SEG=":!VALUE" DESC=":!MEANING"
NAVIGATE="!DIR" VDATE=""
FND VALIDR APPL_SHORT_NAME="SQLGL" CODE="GL#"
NUM=:$FLEX$.GL_SRS_COA_ID_BYSOB VALIDATE="NONE"
REQUIRED="Y" DESC=":!MEANING" SEG=":!VALUE" VDATE=""
The value "GL_SRS_COA_ID_BYSOB" caused the issue.
Solution
To implement the solution, please execute the following steps:
Go to Setup > Financials > Flexfields > Validation > Sets
Query the value set name "GL_SRS_LEDGER_FLEXFIELD" and click on 'Edit Information' button on the Value validation section.
Change the validation of GL_SRS_LEDGER_FLEXFIELD to the following value:
FND POPIDR APPL_SHORT_NAME="SQLGL" CODE="GL#"
NUM=:$FLEX$.GL_SRS_COA_UNVALIDATED REQUIRED="Y"
VALIDATE="NONE" SEG=":!VALUE" DESC=":!MEANING"
NAVIGATE="!DIR" VDATE=""
FND VALIDR APPL_SHORT_NAME="SQLGL" CODE="GL#"
NUM=:$FLEX$.GL_SRS_COA_UNVALIDATED VALIDATE="NONE"
REQUIRED="Y" DESC=":!MEANING" SEG=":!VALUE" VDATE=""
Retest the issue
Query the value set name "GL_SRS_LEDGER_FLEXFIELD" and click on 'Edit Information' button on the Value validation section.
Change the validation of GL_SRS_LEDGER_FLEXFIELD to the following value:
FND POPIDR APPL_SHORT_NAME="SQLGL" CODE="GL#"
NUM=:$FLEX$.GL_SRS_COA_UNVALIDATED REQUIRED="Y"
VALIDATE="NONE" SEG=":!VALUE" DESC=":!MEANING"
NAVIGATE="!DIR" VDATE=""
FND VALIDR APPL_SHORT_NAME="SQLGL" CODE="GL#"
NUM=:$FLEX$.GL_SRS_COA_UNVALIDATED VALIDATE="NONE"
REQUIRED="Y" DESC=":!MEANING" SEG=":!VALUE" VDATE=""
Retest the issue
No comments:
Post a Comment