Last updated on JUNE 10, 2017
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 8.9 and later
Information in this document applies to any platform.
Enterprise, North American Payroll, Release 8.9
Basically, VALID_COMBO_TBL is the table that keeps all valid chartfield combinations used by all online pages (that call for Combination Code ... same as Account Code in prior release). Those 'used' combination code are stored in ACCT_CD_TBL which is being used by all batch programs.
The link between both tables are by a field (FDM_HASH) or (FDM_COMBO_CD).
FDM_COMBO_CD is the same as ACCT_CD. FDM_HASH is a unique identfier created by the system.
This document was previously published as Customer Connection Solution 201018159
Went live with Release 8.9, need clarification on how the acct_cd_tbl get populated. Currently entering into the valid_combo_tbl on-line. Is there a process to run to move the data to the acct_cd_tbl? What are differences between ACCT_CD_TBL and VALID_COMBO_TBL and how do these two tables link together?
After adding new account(s) to VALID_COMBO_TBL, do I run 'Load Combination Code Table' to have these new account(s) in ACCT_CD_TBL?
Will the ACCT_CD_TBL then be updated automatically by the system including our custom fields whenever a new combo account was set up?
Is there a delivered processes to load batch records into PS_DEPT_BUDGET_ERN? Will it effect the FDM_HASH of the PS_ACCT_CD_TBL?
Since the ACCT_CD field is encrypted in some tables, what are considerations for loading additional tables to avoid issues loading ACCT_CD field?
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