How To Fix FDT_CORE256 - &1 avec comp. applic. &2 ne peut pas utiliser &3 avec comp. applic. &4.

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 256

• Message text: &1 avec comp. applic. &2 ne peut pas utiliser &3 avec comp. applic. &4.

Quelle est la cause de ce problème?

The system has determined one of the following situations:
Object &v1& is using object &v3&.
You are trying to establish a usage relationship with object &v1& using
object &v3&.
Object &v3& has access level "application component", requiring that
only objects assigned to the same application component can use it.
However, the using object &v1& is assigned to application component &v2&
, while the used object &v3& is assigned to application component &v4&.
Since these two application components are different, object &v3& cannot
be used by object &v1&.

Comment cela peut-il arriver?

Object,,Application Component
O1,,FI-AA
O2,,FI-GL
Here, O1 cannot use O2 because the objects have been assigned to
different application components (FI-AA versus FI-GL).
Object,,Application Component
O1,,FI-GL
O2,,FI-GL
Here, O1 can use O2 because both objects are assigned to the same
application component, FI-GL.

Réponse du système

If the usage relationship has already been saved, object &v1& cannot be
activated. If you are about to establish the usage relationship, the
system prevents you from doing so.

Comment corriger cette erreur?

To solve the issue, proceed according to either of the following
alternatives:
Create a copy of object &v3& in the same BRFplus application as object
&v1&. Then, create a reference from object &v1& to the copied object.
Check whether raising the access level of object &v3& could solve the
issue. However, keep in mind that raising the access level may lead to
unwanted side effects.

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.