R12: AP: Period Close Exception Report, Period Name Field is Greyed Out, Log Shows Errors: AP_LEDGER_OR_OU_REQ
(Doc ID 1547693.1)
Last updated on NOVEMBER 30, 2024
Applies to:
Oracle Payables - Version 12.0.0 to 12.1.3 [Release 12.0 to 12.1]Information in this document applies to any platform.
Symptoms
Log file for Period Close Exception Report shows the following Error:
oracle.apps.xdo.XDOException: !!Error : trigger 'beforeReportTrigger' returns status as 'false'
at oracle.apps.xdo.dataengine.XMLPGEN.executeTriggers(XMLPGEN.java:654)
at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:263)
at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:215)
at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:254)
at oracle.apps.xdo.dataengine.DataProcessor.processDataStructre(DataProcessor.java:390)
at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:355)
at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:334)
at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:294)
at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
at oracle.apps.xdo.dataengine.XMLPGEN.executeTriggers(XMLPGEN.java:654)
at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:263)
at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:215)
at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:254)
at oracle.apps.xdo.dataengine.DataProcessor.processDataStructre(DataProcessor.java:390)
at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:355)
at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:334)
at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:294)
at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Period Name parameter is greyed out
FND Debug Log of the execution shows the following:
Begin process_period: current timestamp:29-JUL-24 08.44.07.283532000 AM US/EASTERN
begin process_period. Current time stamp is= 29-JUL-24 08.44.07.304474000 AM US/EASTERN
Parameters: p_ledger_id=; p_org_id=; p_period_name=; p_period_start_date=01-JUL-24; p_period_end_date=29-JUL-24; p_sweep_to_period=; p_action=PERIOD_CLOSE_EXCP_REPORT
Global variables initialized
validate_parameters: flag=EE; message=AP_LEDGER_OR_OU_REQ
End process_period: current timestamp:29-JUL-24 08.44.07.304577000 AM US/EASTERN
before_report_apxpcer: flag=EE; message=AP_LEDGER_OR_OU_REQ
begin process_period. Current time stamp is= 29-JUL-24 08.44.07.304474000 AM US/EASTERN
Parameters: p_ledger_id=; p_org_id=; p_period_name=; p_period_start_date=01-JUL-24; p_period_end_date=29-JUL-24; p_sweep_to_period=; p_action=PERIOD_CLOSE_EXCP_REPORT
Global variables initialized
validate_parameters: flag=EE; message=AP_LEDGER_OR_OU_REQ
End process_period: current timestamp:29-JUL-24 08.44.07.304577000 AM US/EASTERN
before_report_apxpcer: flag=EE; message=AP_LEDGER_OR_OU_REQ
Steps to reproduce:
- Log into Oracle Applications using a Payables responsibility.
- Open the Standard Request Submission (SRS) screen
(N) Other > Request > Run - Find/Run the "Period Close Exceptions Report (XML)" program.
- You shall get the above mentioned error in the concurrent program log.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |