Error In Funding WB When Using Agreement DFF Attributes 11-15 (Doc ID 1504098.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Project Contracts - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

Error in Funding WB when using Agreement DFF attributes: 11-15
Added definition to use agreement DFF attributes 11-15. When we look at upgraded funding in Project Contracts and try to view the agreement DFF we get an error APP_FND-01024: You passed an incorrect value to a flexfield user exit.

In R12, Oracle provided new attribute fields on PA_AGREEMENTS_ALL which are configurable as segments in the DFF. For some of the other billing modernization efforts, we have reason to utilize these new segments. We’ve enabled 5 more – attributes 11 – 15.

Migrated my DFF changes through to OFM so that we could see they’re visible in the Project Contracts 2nd [ ] on the funding workbench. This is the one that should pop-up the Agreement DFF for display or edit.

Unfortunately, we now get an ERROR when we query up existing contracts/agreements and navigate into that second DFF. It appears that it may be related to the fact that the OKE form only recognizes 10 attribute fields … and that the tables OKE_K_FUNDING_SOURCES and OKE_K_FUNDING_SOURCES_H only have fields PA_ATTRIBUTE1 – PA_ATTRIBUTE10 defined.

Error Message:

APP-FND-01024: You passed an incorrect value to a flexfield user exit.

Cause: You passed USEDBFLDS="Y" to one of the flexfield user exits #FND POPID | LOADID | VALID |
POPDESC | LOADDESC | VALDESC and the form does not have all the database SEGMENT1 - SEGMENTn or
ATTRIBUTE1 - ATTRIBUTEn fields.

Action: Set USEDBFLDS="N" if the form does not use the SEGMENTn or ATTRIBUTEn fields.

Action: Check that all the SEGMENTn or ATTRIBUTEn fields are in the form. View previous messages to see which field is missing.

Also tried to enter a NEW contract in OFM named MNB-TEST and set the DFFs. For a new record, get an error. Details shows that it can’t set the value for fields attribute11 – attribute14. After we save, we see the same error:

APP-FND-01238: Cannot set value for field DUMMY_ATTRIBUTE11

Cause

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