EGL9.2: Combo Build FS_CEBD Process Not Inserting Same Number of Rows in COMBO_DATA_TBL in SQL Server as in DB2
(Doc ID 2993095.1)
Last updated on DECEMBER 14, 2023
Applies to:
PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
After converting to SQL Server from DB2 database, Combo Build is running to success but the COMBO_DATA_TBL populated by the Combo Build process has significantly less rows inserted in the SQL Server environment as in the DB2 environment for the same configured Combo Groups and Combo Rules in the below tables -
PS_BU_LED_COMB_TBL A,
PS_COMBO_GROUP_TBL B,
PS_COMBO_GRRUL_TBL C,
PS_COMBO_RULE_TBL D,
PS_COMBO_FLDS_TBL E
One example is Combo Group 'XX_DEPT' which contains Combo Edit Rule 'XXXXXXDEPT which has multiple rows setup with various accounts and departments.
For the above Combo Rule the Combo Edit trace file from DB2 shows the below number of rows inserted to the COMBO_DATA_TBL
-- Row(s) affected: 34227
whereas for the above Combo Rule the Combo Edit trace file from SQL Server shows the below number of rows inserted to the COMBO_DATA_TBL
-- Row(s) affected: 2
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 |