R12: XLAREPSEQ Create Reporting Sequence Fails With Concurrent Request for "Create Reporting Sequence Number" Has Completed With Error
(Doc ID 555778.1)
Last updated on NOVEMBER 22, 2022
Applies to:
Oracle General Ledger - Version 12.0.3 to 12.1.3 [Release 12.0 to 12.1]Information in this document applies to any platform.
XLAREPSEQ - Create Reporting Sequence
Symptoms
On 12.0.3 in Production:
When attempting to close a period, the following error occurs in the XLAREPSEQ - Create Reporting Sequence program.
ERROR
-------
Exceptions posted by this request:
Routine &ROUTINE received a return code of failure. Contact your support representative.
In the log file :-
Exceptions posted by this request:
Concurrent Request for "Create Reporting Sequence Number" has completed with error.
In FND Messages trace:
Get_assign_context_info completes successfully., x_seq_context_id: , x_control_date_type: , x_req_assign_flag: , x_sort_option_code:
x_sequence_type: , x_assignment_id: , x_control_date_value: , x_req_assign_flag:
After calling fun_seq.get_assigned_sequence_info... , l_seq_ver_id_tbl(i): , l_assign_id_tbl(i): , l_out_ctrl_dt_tbl(i): , l_req_assign_flag_tbl(i): , l_error_code_tbl(i): NO_ASSIGN_CONTEXT
Before calling Sort_Acct_Entires: Sort Option -
p_request_id: 17676435, ae_header_id: 9877683, sort_option_code: , SQLERRM: User-Defined Exception
p_request_id: 17676435, SQLERRM: ORA-20001:
p_retcode = 2
p_errbuf =
END of procedure assign_sequence
end of procedure reporting_sequence
Exceptions posted by this request:
Concurrent Request for "Create Reporting Sequence Number" has completed with error.
STEPS
The issue can be reproduced at will with the following steps:
1. Setup > Open/Close
2. Close a period.
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 |
Still Have Questions? |
References |