Future_cost.calc_date impacted events

Question

Hi all,
happy new year and happy holidays,
just back from vacation.
can some share the list of the events, which causes calc_date changes?
As I can see, not all of the cost_event are causes calc_date changes, is this a bug? or maybe field is a vestige?
kind regards,
Eldar A.

Answer 1

Hi
The problem with a message like this is that it doesn't really tell you exactly where to look for the source of the trouble. You might, if you are lucky, get something from examining the API code in TOAD or similar, at that specific line number. Failing that, then we need to look for probable causes. Child records of an assignment in this case will most likely be:
Element entries PAY_ELEMENT_ENTRIES_F
Personal Payment methods (if payroll) PAY_PERSONAL_PAYMENT_METHODS_F
Spinal Point placements (if using grade ladders) PER_SPINAL_POINT_PLACEMENTS_F
Note this is by no means an exhaustive list of child entities for an assignment!
My guess would be, if the assignment was entered erroneously, is that element entries were automatically created for the assignment by virtue of 'standard' links. To prove this (or indeed refute it!) do:
SELECT * from PAY_ELEMENT_ENTRIES_F
WHERE assignment_id = 19406;
If that gives any rows, then in order to remove the assignment you will need to remove those element entries first. Given that you want to do via APIs, then pay_element_entry_api.delete_element_entry will do it - however, be aware that if you want to actually remove the element entries (and any date-track changes) completely, then the mode to use is 'ZAP', not 'DELETE'. This is also true of your process for removing the assignment.
Clive