Last updated on MARCH 09, 2017
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.
Users run AP_MATCH on single Vouchers one after another. If the user modifies and saves the run control for the next AP_MATCH with the same run control before the current process completes, the VOUCHER.IN_PROCESS_FLG remains "Y" and is not updated to "N".
The problem is in AP_MATCH.UpdFlags.Step01.
UPDATE PS_VOUCHER SET IN_PROCESS_FLG = 'N' WHERE PROCESS_INSTANCE = 4519441
AND IN_PROCESS_FLG = 'Y' AND CLOSE_STATUS <> 'C' AND MATCH_DUE_DT TO_DATE(TO_CHAR(SYSDATE,'YYYY-MM-DD'),'YYYY-MM-DD') AND
PS_VOUCHER.VOUCHER_ID IN (SELECT VOUCHER_ID FROM PS_MTCH_RUN_VCHR MTCH WHERE
OPRID = 'MCCASTR' AND RUN_CNTL_ID = 'MATCHINGR' AND REQUEST_ID = '1' AND
PS_VOUCHER.BUSINESS_UNIT = MTCH.BUSINESS_UNIT AND PS_VOUCHER.VOUCHER_ID =
MTCH.VOUCHER_ID) AND PROCESS_MAN_CLOSE = 'N'
-- Row(s) affected: 0
Here is the SQL from the app engine:
SET IN_PROCESS_FLG = 'N'
WHERE PROCESS_INSTANCE = %ProcessInstance
AND IN_PROCESS_FLG = 'Y' %Bind(WHERE_CLAUSE, NOQUOTES) %Bind(WHERE_CLAUSE2, NOQUOTES)
1. Add PO with Matching
2. Dispatch PO
3. Create Voucher from PO
4. Add Matching Run Control
5. Run Matching for Voucher
6. Before process completes, modify the Matching Run Control to process a different Voucher ID
7. Save Matching Run Control
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