My Oracle Support Banner

How to Avoid The APP-FND-00676 For DFF's using Reference Fields From Different Forms (Doc ID 1364676.1)

Last updated on SEPTEMBER 14, 2023

Applies to:

Oracle Field Service - Version 12.1.3 and later
Oracle Service Contracts - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Goal

When a descriptive flexfield uses a reference field, referring to a :BLOCK.:FIELD value from a specific form, that flexfield will cause an error if it is displayed on a different form as well, where that :BLOCK.FIELD combination does not exist.

The error will be:
==========
APP-FND-00676: The flexfield routine FDFGDC cannot read the default reference field specified for this descriptive flexfield. The developer specified a context field (via the Register Descriptive Flexfields form) that does not exist in this block of this form.

Action: Contact your system administrator, and choose another default reference field for this descriptive flexfield.
==========

This note will propose a solution to this problem that allows the user to see the DFF on both forms without error. For clarity, a real case is presented, using the Additional Information for Agents (Service) Descriptive Flexfield. This DFF is used on several forms, such as the Service Request (CSXSRISR), Dispatch Center (CSFDCMAI) and Contact Center (CSCCCCRC). This method would be applicable to any area in E-Business Suite where a descriptive flexfield is used on multiple forms.

Solution

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
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.