Announcements for Payroll and OTL can now be found in the Announcements - Payroll and OTL - EBS (MOSC) subcategory. Follow to be sure you don't miss a thing!
PAY: RetroCosting and PAY_COSTS Tigger
Hi All
I have a question for all Payroll consultants out there with experience with using RetroCosting.
The current I am at has done some costing customisation by way of Tiggers on the PAY_COSTS table. The client has some business rules that are not met by the standard Costing hierarchy. As such, the triggers are used to update the cost string once the Costing process has done its job.
The problem arises when RetroCosting is run. Assume:
1) Element E100 is process in a payrolls run for Period 1 (Assume amount is $50)
2) The costing process is then run for Period 1. The seeded Costing process allocates costing string A-B-C to Element E100. This record is inserted into the PAY_COSTS table
I have a question for all Payroll consultants out there with experience with using RetroCosting.
The current I am at has done some costing customisation by way of Tiggers on the PAY_COSTS table. The client has some business rules that are not met by the standard Costing hierarchy. As such, the triggers are used to update the cost string once the Costing process has done its job.
The problem arises when RetroCosting is run. Assume:
1) Element E100 is process in a payrolls run for Period 1 (Assume amount is $50)
2) The costing process is then run for Period 1. The seeded Costing process allocates costing string A-B-C to Element E100. This record is inserted into the PAY_COSTS table
0