Experience I've been working with PeopleSoft since 2001, gaining technical and functional experience in several modules in HRMS and Financials/SCM, from analysis to development to testing. I'm currently an independent contractor available for local and international roles.
We have a requirement where we need to schedule the PayCycle processing. The requirement is that the PayCycle Selection should be scheduled. Then the user would manually validate all the payments and take required action (hold/exclude). Finally the user would manually run the Payment Creation Process.
The delivered pay cycle job APPCJOB directly creates the payments and there is no scope for the validation of the payments in between the selecetion and creation processes.
How do I go about it?
Thanks in advance,
Kiran.
ANSWER: Hi Kiran,
You can create a separate job which runs the selection process only, and you can attach this new job to the same run control as the APPCJOB. Open the APPCJOB definition and create your new job based on this, excluding the creation process.
So the users would run this custom job, do their validation, and then run the creation process manually.
---------- FOLLOW-UP ----------
QUESTION: Hi Ashram,
But the problem here is that both, the PayCycle selection as well as the PayCycle creation engines are the same AP_2015 AE. The processing is maintained using pay cycle statuses which the same app engine checks and then processes the payments.
PeopleSoft states that in case you have to add any new status, you may have to modify the delivered pay cycle AE.
I am looking at any solutions that have been implemented without customizing the AE (if this can be done that is).
Thanks for the help.
Thanks,
Kiran.
Answer In that case, you may need to customize the AE. I'm not too familiar with the Payroll apps, but one approach would be split the AP_2015 process into 2 - the first part would do the selection, and the second part would do the creation. Some analysis would need to be done on the AE to ensure that both functions can be done independently of each other, i.e no temp tables needs to be shared, etc. If the app engine relies solely on the pay cycle status, then it should definitely be possible.
