CN_GET_TX_DATA_PUB.UPDATE_API Record Does Not Work Correctly
(Doc ID 959699.1)
Last updated on MARCH 08, 2019
Applies to:Oracle Incentive Compensation - Version 12.0.4 and later
Information in this document applies to any platform.
User has custom code to validate that the transaction attributes are correct.
If the attributes are incorrect, user creates the reversal records via call to public api CN_GET_TX_DATA_PUB.update_api_record. When user pass in the wrong comm_lines_api_id record to be adjusted, the system generated unbalanced reversing records resulting in overpaid or underpaid
The issue can be reproduced at will with the following steps:
1. Create new transaction via api or manually
2. Run sales credit allocation
3. Run transaction interface loader
4. Run calculation
5. Call CN_GET_TX_DATA_PUB.update_api_record to adjust the record by passing in the incorrect comm_lines_api_id
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document