Transaction Web Service Does Not Consider DFF Default Values
Last updated on MARCH 08, 2017
Applies to:Oracle Fusion Incentive Compensation - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 1.0]
Information in this document applies to any platform.
On : 126.96.36.199.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
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms