EGL9.2: Allocation Process is Only Posting the First Allocation Step After Assigning Temporary Tables to Application Engine Program FS_ALLC, All Remaining Journals Sit in a 'Valid' Status. (Doc ID 2010381.1)

Last updated on SEPTEMBER 14, 2016

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

On : 9.2 version, Allocations

ACTUAL BEHAVIOR
---------------
The allocation process is only posting the first allocation step after assigning temporary tables to application engine program FS_ALLC, all the remaining journals sit in a 'Valid' status.

EXPECTED BEHAVIOR
-----------------------
The allocation process should post all allocation steps after assigning temporary tables to application engine program FS_ALLC.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

  1. Create two allocation steps and make sure Edit Journal(s) and Post Journal(s) is enabled for both of them.
  2. Create an allocation group and link the allocation steps from step 1 to this group.
  3. Navigate to Allocations > Define and Perform Allocations > Request Allocation and run Application Engine process FS_ALLC.
  4. Two journals are created and posted, one journal for each allocation step.
  5. Sign in to Application Designer and open the Program Properties for Application Engine FS_ALLC.
  6. Add the following Temp Tables to FS_ALLC (this is to fix issue described in Doc ID 618217.1):
    • ADB_ACTLG_TAO
    • JHDR_SEL_TAO
    • JP_BULED_TAO
    • JP_JHDR_TAO
    • JP_JLN_TAO
    • JP_PST_TAO
    • JP_PST1_TAO
    • JP_PST2_TAO
    • JP_PSTB_TAO
    • JP_PSTB1_TAO
    • JP_PSTB2_TAO
    • LEDG_ADB2_TAO
    • LEDG_ADB3_TAO
    • LEDG_ADB4_TAO
    • OI_POST_TAO
    • OPEN_ITEM_TAO
  7. Run the allocation process again.
  8. This time only the first journal is posted! The second journal is NOT posted and remains in status Valid.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, most allocation journals are not posted automatically.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms