It is not a good idea to update back-end tables. Oracle will stop supporting your instance.
You need to go to each physical layer and make it non-costable first. Then you can update all the physical records to the same costable type.
By physical record, I mean each record in the database - 1-Jan to 12-Feb is one physical record..
I know it's not the smartest thing to do. But what else can I do from the application end? Please advise and explain the steps in detail, if possible
Also which physical records do you mean should be updated? I am not sure which table exactly are you talking about?
The system throws the error, when you have different costable rules for different dates.
So, you could either delete future or old records to have a single record and then have the costing details.
Navigate to the first date of the element link record, make the element as not-costed.
Navigate to the send date for the same link, make it not-costed.
Do the same for all the records for the element link.
Now go to whichever record you want and make the link as costed or fixed-costed, based on your business needs.
Hope that helps.
The costable type is the same for both element links. One more thing this element is recurring and linked to formula and a balance. What are the impacts of end dating the link , recreate a new one and reassign it to staff??
Please help me I don't want to mess up with the production..
Yes, you can end-date the link and create a new one.
Just make sure you dont have any element entries for the element.
we do have element entries that's why I am wondering how it would affect the exiting balances
help me please
Balances should not be a problem. Balances are driven by run results(not element entries).
So you can safely do this -
#1. end-date the element entries.
#2. create a new link
#3. recreate the element entries.
But I still do not understand why your existing links are not updatable ?
thanks a lot.
that worked finally.
Actually I feel i must confess and I wish it help others from repeating my mistakes.
I have created a backup table for the two records of the element link and set
,BALANCING_KEYFLEX_ID = NULL
,COSTABLE_TYPE ='N' --'C'
,TRANSFER_TO_GL_FLAG = 'N'
But that did not solve my problem from the front end and error above still popped up.
So, I tried to restore the records to the first state using my backup table. It didn't work. The update trigger failed.
However I realized later that the values of COST_ALLOCATION_KEYFLEX_ID are different in both records in the backup table. I guess I should have tried in the first place to undo the last change or set its effective date to the start date of the element link.
Thanks a lot Vigneswar. You have been a great help.
Good to hear it worked
Most of the times, the error says it all, but we dont realise it.