How To Fix FDT_CORE378 - Utilis. multiple d'objets identiques (&1 et &2) non autorisée dans &3/&4

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_CORE - Formula & Derivation Tool: Core

• Message number: 378

• Message text: Utilis. multiple d'objets identiques (&1 et &2) non autorisée dans &3/&4

Quelle est la cause de ce problème?

In the current ruleset, the system has detected multiple occurrences of
the same data object used in the same scope. This situation may lead to
ambiguous references that the system cannot resolve.
From a ruleset perspective, data objects may occur within the following
scope areas:
Function context
Function result
Temporary ruleset variables
Each data object you use must be unique within each of these scope areas
as well as across all scope areas. However, experience shows that it can
happen quite easily that you have two tables referring to the same
structure, or two structures referring to the same element data object.
This results in a violation of the requirement mentioned above.
Note: You may probably see this conflict message several times, due to
the sequential processing of the check. We therefore recommend you start
correcting this issue at the first occurrence and check again. Chances
are that one correction may already solve several subsequent issues at
once.

Réponse du système

The object cannot be activated.

Comment corriger cette erreur?

To solve the issue, choose one of the following alternatives:
Bind the affected data objects to suitable ABAP Dictionary (DDIC)
objects. You should do this in particular for all involved structures
and tables. This ensures that the used data objects are automatically
unique. This is the recommended approach.
If, for whatever reason, data binding is not an option, reorganize the
affected data objects as follows:
With the help of the 'Display Related Object' link provided by the
message, navigate to the data object.
Analyze the usages of the data object with the help of the 'Where Used'
function.
Sort out all usages that do not belong to the function context /
function result / ruleset temporary variables. These cannot create a
conflict and need not be considered here.
For each usage within one of the ruleset scope areas, create a copy of
the object in question and insert it at the position where the duplicate
object reference used to be.
Note that in some use cases you have to keep the old name for the newly
created objects. For example, this can be necessary for object usages in
mapping relationships in the context of other expressions. We recommend
you make a note of each object's purpose either in the object
description or documentation.
Regardless which of the above alternative approaches you choose, you
have to take one final measure:
Reassign all data object references in the ruleset. This is necessary to
ensure that the newly created objects (either bound to the dictionary or
copies of the original objects) are used instead of the original.

Procédure pour les administrateurs système

Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.

Extrait du message d'erreur du système SAP. Copyright SAP SE.