Our developer here, has had to look at re-writing his wrapper script to call the RTI FPS process for the new XML version of 'RTI - Full Payment Submission Process (FPS) 2018/2019'. This used to spawn seperate runs against each payroll. But with new parameters for the concurrent program not able to get this to work as has done before. So getting java errors as below
Anyone else come across this - assume other clients will have previously looked to use wrapper scripts potentially for this need...
Raised with Oracle with the wrapper script call and error stack but no response currently
Payroll: Version : 12.1
Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
Entering generateIRMark inside while nvtARCHIVE_REQUEST_ID value 51 requestId 51 inside while nvtARCHIVE_REQUEST_ID_HIDDEN value PAY_GB_XML_SUBMISSION_DTLS tableName PAY_GB_XML_SUBMISSION_DTLS aftre while getIRMark java.lang.NullPointerException at oracle.apps.pay.xmlrep.webui.PayGBIRGeneratorCP.clobToString(PayGBIRGeneratorCP.java:281) at oracle.apps.pay.xmlrep.webui.PayGBIRGeneratorCP.getIRMark(PayGBIRGeneratorCP.java:224)
Regards Peter L.
#12158 - 04/07/1810:13 AMRe: Wrapper script -issues when calling 'RTI - Full Pa
Hi Peter, We don't have a wrapper script for this particular concurrent program, but we do for about 20 others and it's worked without fail (we use an AUL to group payrolls into blocks of 30 or so), so not sure what is different with this particular one but I'd be interested in the outcome. Anytime we've previously had an issue it's been due to a parameter mismatch for what is actually sent to the concurrent program. Regards, Jay
#12171 - 24/07/1810:19 AMRe: Wrapper script -issues when calling 'RTI - Full Pa
[Re: Jay Kavia]
Hi Jay, For reference this did end up going to Oracle Support/Development and issue was found to be a 'hidden' parameter that hadn't been defined in the wrapper program and caused the error when not being set...
"The issue occurs because MAGFILE_GENERATE_IN_FS parameter is null.
Problem - MAGFILE_GENERATE_IN_FS should be 'Y'. Currently, this parameter is not defined while submiting the concurrent program request, thus, it is coming as null in the backend. Solution - Add another argument with 'MAGFILE_GENERATE_IN_FS=Y' "