Patch 9211869 3RD PARTY CHECKWRITER ATTACHMENT NUMBERS NOT CORRECT WHEN MUL

Question

Hi:
I have created an XML Third Party Check report that is based on the queries found in the seeded Oracle PAYUSGAR.rdf 115.24 check report. The patch 9211869 fixed an issue in the standard report where multiple checks for the same employee to the same payee for the same amount were NOT printing the correct garnishment reference number. I have reviewed the report code but have not been able to fix this same issue through XML.
My queries will produce all of the correct data except the 2nd duplicate (same employee to the same payee for the same amount) prints the reference number from the 1st element rather than the 2nd. Does anyone know how the check data is tied to the elements through the tables?
My example is:
Person: Max Doe Check: 1234 Paid to: California Agency Check Amount: 121.00 Pre_payment_id: 766297 Ref # 4567
Person: Max Doe Check: 1234 Paid to: California Agency Check Amount: 121.00 Pre_payment_id: 766302 Ref # 657AA
(Ref # 657AA prints on the second check as Ref # 4567)
The query from the report is:
SELECT peev.screen_entry_value garn_ref_no
,:check_amount
,TO_CHAR(pay_us_payment_pkg.get_trx_date(
:business_group_id,
:ppa_payroll_action_id,
NULL,
:ppa_payroll_id,
:ppa_consolidation_set_id,
:ppa_org_payment_method_id,
:ppa_effective_date,
:ppa_date_earned,
:ppa_override_date,
ppp.pre_payment_id,
ppa.effective_date
),'DD-MON-YYYY') payment_date
,TO_CHAR(ppa.date_earned, 'DD-MON-YYYY')
,prr_att.run_result_id
,peef.entry_information2 -- FIPS code
,peef.entry_information3 -- Medical Indicator
,paa.assignment_action_id
,pet.element_type_id
FROM pay_element_entry_values_f peev,
pay_input_values_f piv_att,
pay_element_entries_f peef,
pay_run_results prr_att,
pay_run_results prr_pay,
pay_payroll_actions ppa,
pay_assignment_actions paa,
pay_action_interlocks pai,
pay_pre_payments ppp,
pay_input_values_f piv_pay,
pay_run_result_values prrv_att,
pay_run_result_values prrv_pay,
pay_element_types_f pet,
pay_element_types_f pet_calc,
pay_element_classifications pec
WHERE ROUND(ppp.VALUE ,2) = :check_amount
AND ppp.pre_payment_id = :pre_payment_id
AND ppp.assignment_action_id = pai.locking_action_id
AND pai.locked_action_id = paa.assignment_action_id
AND ppa.payroll_action_id = paa.payroll_action_id
AND ppa.action_type IN ('R', 'Q')
AND ((paa.source_action_id IS NOT NULL AND ppa.run_type_id IS NOT NULL) OR
(paa.source_action_id IS NULL AND ppa.run_type_id IS NULL))
AND ppp.personal_payment_method_id = peef.personal_payment_method_id
AND peef.assignment_id = paa.assignment_id
AND ppa.date_earned BETWEEN peev.effective_start_date
AND peev.effective_end_date
AND ppa.date_earned BETWEEN peef.effective_start_date
AND peef.effective_end_date
AND piv_att.input_value_id = peev.input_value_id
AND UPPER(piv_att.NAME) = 'ATTACHMENT NUMBER'
AND ppa.effective_Date BETWEEN piv_att.effective_start_date
AND piv_att.effective_end_date
AND piv_att.input_value_id = prrv_att.input_value_id
AND prrv_att.result_value = peev.screen_entry_value
AND prrv_att.run_result_id = prr_att.run_result_id
AND paa.assignment_Action_id = prr_att.assignment_Action_id
AND prr_att.element_type_id = peef.element_type_id
AND peef.element_type_id = pet.element_type_id
AND pet.classification_id = pec.classification_id
AND pec.classification_name = 'Involuntary Deductions'
AND pec.legislation_code = 'US'
AND pec.business_group_id IS NULL
AND fnd_number.canonical_to_number(pet.element_information5) = pet_calc.element_type_id
AND pet_calc.element_name LIKE pet.element_name || '%Calculator'
AND pet_calc.element_type_id = piv_pay.element_type_id
AND NVL(ppa.date_earned, ppa.effective_date) BETWEEN piv_pay.effective_start_date AND piv_pay.effective_end_date
AND piv_pay.input_value_id = prrv_pay.input_value_id
AND UPPER(piv_pay.NAME) = 'PAY VALUE'
AND fnd_number.number_to_canonical(ppp.VALUE) = prrv_pay.result_value
AND prr_pay.run_result_id = prrv_pay.run_result_id
AND prr_pay.assignment_action_id = paa.assignment_action_id
AND prr_pay.element_type_id = pet_calc.element_type_id
ORDER BY prr_att.run_result_id;
Somehow, Oracle has fixed this in the rdf but I have not been able to figure out how exactly. This is a function call in the report but they are passing the check amount and the prepayment_id. Regardless of which pre_payment_id is sent in, 2 rows are returned.
If anyone has any thoughts, please let me know. This is the final tweak that is stopping our go-live with this.
Thanks, RL

Answer 1

Hi,
Has this been resolved. I'm investigating ways to develop this report as the current CheckWriter(XML) does not work for 3rd party. Please let me know, if it worked for you.
Thank you,
Radha
[email protected]