EGL9.1: Allocation Encountered Unique Constraint Error at Step FS_ALLC_OUTJ.iJLine.iLine When Run for Multiple Business Units Together With Similar Data
Last updated on JANUARY 18, 2017
Applies to:PeopleSoft Enterprise FIN General Ledger - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.
When run for multiple business units together with similar data, encountered with unique constraint error at step FS_ALLC_OUTJ.iJLine.iLine for the second Business unit in request.
Especially it happens when the zero basis option chosen as ‘Select next Basis’. When run with zero basis option as ‘Stop processing’ issue could not be replicated.
Steps to replicate:
1. Create new Allocation Steps as per the details provided in customer replication
2. Create an Allocation group containing the steps created above. Select the Continue checkbox against each of the steps.
3. Create similar Pool & Basis data for 2 different Business units.
4. Request allocation.
Please see Replication screenshots for more details.
ORA-00001: unique constraint (EMDBO.PS_JRNL_LN) violated Failed SQL stmt: INSERT INTO PS_JRNL_LN (BUSINESS_UNIT, JOURNAL_ID, JOURNAL_DATE, UNPOST_SEQ, JOURNA L_LINE, LEDGER, ACCOUNT, ALTACCT, DEPTID, OPERATING_UNIT, PRODUCT, FUND_CODE, CLASS_FLD, PROGRAM_COD E, BUDGET_REF, AFFILIATE, AFFILIATE_INTRA1, AFFILIATE_INTRA2, CHARTFIELD1, CHARTFIELD2, CHARTFIELD3, BOOK_CODE, GL_ADJUST_TYPE, BUDGET_PERIOD, SCENARIO, CURRENCY_CD, BUSINESS_UNIT_PC, PROJECT_ID, ACTI VITY_ID, RESOURCE_TYPE, RESOURCE_CATEGORY, RESOURCE_SUB_CAT, ANALYSIS_TYPE, STATISTICS_CODE, MONETAR Y_AMOUNT, MOVEMENT_FLAG, STATISTIC_AMOUNT, JRNL_LN_REF, SUSPENDED_LINE, LINE_DESCR, JRNL_LINE_STATUS , JOURNAL_LINE_DATE, FOREIGN_CURRENCY, RT_TYPE, FOREIGN_AMOUNT, RATE_DIV, RATE_MULT, PROCESS_INSTANC
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms