![]() Ģ) Created App Engine program FSCF_FIX_CFI for POC Resolution to mass-fix SQL's if customer does not want to run CF Configuration again. It is also available as a posted standalone fix. This fix is delivered as FMS Financials 9.0 Bundle #22. This problem is addressed by GL development in "CF Configuration is updating BK_CFI_* and FS_CFI_* SQL's with Chartfields in the wrong order." The issue is resolved in two parts:ġ) Modify functions Bld_CF_Inh_SQL (in FUNCLIB_CF_FS.SQL_FUNCTION.FieldFormula) and Bld_Bank_CFI_SQL (in FUNCLIB_BANK.SQL_FUNCTION.FieldFormula) to order Chartfields correctly when re-creating the SQL's in batch mode. For example, modifying and resaving External Bank Account setups will reorder the SQL definition for BK_CFI_FLST% objects, and modifying and resaving chartfield inheritance setups corrects the SQL definition for FS_CFI_FLST% objects. This allowed a workaround to be used to correct the problem. Note that only the batch process FS_CONFIG creates these out of order SQL defintions. Depending on which fields are involved, the problem may appear as data being incorrectly stored, or in the case of ARUPDATE processes, result in ABENDS when datatypes conflict. ![]() This may result in chartfields mapping to incorrect fields, e.g. When delivered chartfields and inheritance setups are modified, and the batch process (FS_CONFIG) is used to propagate these changes, a defect may cause the order of chartfields to be stored incorrectly in these SQL definitions. In Receivables, the ARUPDATE/AR_PGG_SERV process dynamically builds the SELECT and INSERT SQL statements from these SQL definitions. The SQL definitions may be modified via online setups, such as when defining External Bank Accounts, or mass updated by batch process, through FS_CONFIG, or Standard Configuration for chartfields. The SQL definitions for chartfield objects are stored in PSSQLTEXTDEFN and varies for each installation depending on the chartfield configuration (active or inactive) and chartfield inheritance setup. Purpose PeopleSoft Receivables Home PeopleSoft Receivables Troubleshooting Primary Case Studies Ĭhartfields are fields that store chart of accounts information and provide the basic structure to segregate and categorize transactional and budget data used throughout Oracle Peoplesoft Enterprise applications. Information in this document applies to any platform. PeopleSoft Enterprise FIN Receivables - Version 8.8 to 9.2 Troubleshooting Chartfield Configuration Creating SQL Definitions With Incorrect Chartfield Order
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |