Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from JG-SAPHR on Jan 31 at 5:44 PM 1. Expand fully your payroll schema using RPDASC00.
2. Go through the functions that do not apply for off cycle payroll.
3. In case of significant schema changes, it would be better to use copies of the payroll schema/subschema, so that you would not hinder other users or tasks.
4. Insert lines in the payroll schema to skip those lines in the schema/subschema. Usually you should not need to skip in PCR's. If using test schema, use a transport name to indicate that it is not for transport.
5. Import the employees data affected in prod client into dev test client and Test system/client.
6.a. Test payroll (both normal and off-cycle) for these / other employees with the normal schema and the test schema created above. You may involve user/s in this testing.
6.b. If the changes above are not enough, correct the schema/PCRs as required.
7. Make changes in the normal schema and move the transports to Test system client. Test again with the data as before. Then get users to test.
8. Move the changes to prod. Test some more in prod with payroll simulation.
9. Monitor prod client for a couple of cycles, particularly annual, etc.
| | | ---------------Original Message---------------
From: Anonymous
Sent: Friday, January 31, 2014 9:31 AM
Subject: ARRRS and DDNTK Deduction Not to Be Done for Offcycle Run
Hi,
The requirement is to deduct pending amounts of regular run in next regular run only.
If there is an offcycle run in between the wagetypes in DDNTK and ARRRS table should not be processed and same DDNTK and ARRRS table need to be available at end offcycle run. So that in regular the same can be deducted.
As of now, the pending deductions from regular run are being adjusted in offcycle run immediately after.
Please suggest if it is possible to implement the same.
Thanks in advance :) |
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
