EPY: PYAP_XTAX Is Not Populating The BUSINESS_UNIT_PC In The Voucher Message. (Doc ID 1919272.1)

Last updated on AUGUST 04, 2015

Applies to:

PeopleSoft Enterprise HCM Payroll for North America - Version 9.1 and later
Information in this document applies to any platform.

Goal

 The problem is that the AP tax extract is not passing along the value it finds in PAY_TAX_LIAB_AP.BUSINESS_UNIT_PC. In all cases in which BUSINESS_UNIT_PC was populated in the source table, PYAP_XTAX converted this to a blank to insert into the AP invoice detail record AP_EXTRACT_LINE. But for sponsored programs, if the chartfield combination contains PROJECT_ID and ACTIVITY_ID chartfields, it is required to also have a valid value in the chartfield BUSINESS_UNIT_PC to pass edits in finance. And although this chartfield is populated correctly in VALID_COMBO_TBL, ACCT_CD_TBL and PAY_TAX_LIAB_AP, it was not being passed to AP_EXTRACT_LINE  when the AP interface tax extract process ran. The core process of PYAP_XTAX is to select the taxes to be processed from payroll records, including PAY_DED_LIAB_AP, which carries the liability funding and is populated by PAYGL02. PYAP_XTAX selects tax transactions and their associated liability funding and inserts them into a temp record PYAP_XTAX1_TAO. PYAP_XTAX then pushes the contents of PYAP_XTAX1_TAO into AP_EXTRACT_LINE. It is in populating PYAP_XTAX1_TAO that PYAP_XTAX selects the wrong value for BUSINESS_UNIT_PC.

Solution

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