Transaction Web Service Does Not Consider DFF Default Values
(Doc ID 2054122.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Fusion Incentive Compensation - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 1.0]
Information in this document applies to any platform.
On : 220.127.116.11.0
The Incentive Compensation base Transaction Descriptive Felexfield ( CN_TP_BASETRANS_DFF) has been setup to default a value for one of the segments.
If the Transaction Web Service is used to load transactions, the default value for the flexfield segment does not get populated.
The expectation is that the DFF attribute will be populated with the default value when importing transactions using the webservice..
The issue can be reproduced at will with the following steps:
1.Create a DFF attribute in the base transaction DFF that is defined with a default value
2. Import transaction using the web service.
3. The default value is not populated in the DFF
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|