Do you have any question about this error?
Message type: E = Error
Message class: O0 - IS-OIL area independent messages
Message number: 021
Message text: Eviter de modifier applications <> MM/SD (découplage) -> Cl. dév. &1
IS-Oil is based to a large extent on enhancements to the application
components <ZK>Materials Management</> (development class M*) and
<ZK>Sales and Distribution</> (development class V*).
In order to keep our dependence on other components to a minimum, IS-Oil
developers should not develop modifications in "foreign" applications
and minimize the dependencies to other components.
However, in specific cases, it may be necessary to make an enhancement,
but here there are also a couple of logical alternatives:
Check whether or not the enhancement can be solved some other way.
If not, check, if the enhancement can be communicated to the standard
developer, who can then change the coding (if, for example, only
constants can be called in the program, and not oil objects, for example
table definitions). This is to ensure that there are no oil
modifications in the oil coding which are later built into Core coding.
If you are in doubt, call Oil techn.team; the person responsible for the
object can be displayed using Report RDDRESTA or OITRESTA.
First, the correction will have to be built in by us. Sometimes the Core
developers put it into the Hot Package coding, though, before that can
occur. The advantages of this process are obvious:
The object does not have to be maintained and delivered by IS-Oil.
Minimization of transport volume and installation times at customer
site.
Fewer conflicts during the Hot Package merge
Easier to combine IS-Oil with other application components without
having to deal with conflicts or merges.
Standard created the DECO transaction for that, which determines if
sub-objects are being used in objects in a "foreign" environment (in
this case, the OI* dev. classes). In the past the entire SAP system was
delivered, although the customer only ordered/uses a few of the
application components. This solution was developed due to the
dependencies that exist among the modules. Decoupling is used due to the
immense problems brought about by long installation times/upgrade times
as well as delivery postponements, because, for example, one component
was not fully ready in development. That was decided on, because SAP
decided that that situation was unacceptable with respect to the
customers.
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.
For that reason, the system produces the warning:
Within oil development system, please start transaction DECO and verify
the "foreign use" of mentioned above object. Don't hesitate to contact
the oil technical team to discuss a solution to remove the dependency to
an "foreign component".
Extrait du message d'erreur du système SAP. Copyright SAP SE.
O0021
- Eviter de modifier applications <> MM/SD (découplage) -> Cl. dév. &1 ?Get instant SAP help. Start your 7-day free trial now.
O0020
Pbs lors d'utilisation du contr. copie des ventes pour &1->&2 (&3 &4)
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
O0019
Suppression &1 lignes table &2 réussie
Quelle est la cause de ce problème? Information message that &V1& lines of table &V2& were updated in the database, caused by progr...
O0022
Saisie &1 &2 &3 &4 n'a aucun sens ici (contexte ?!)
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
O0023
Erreur interne dans &2 &1 avec code retour &3 (&4)
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
Cliquez sur ce lien pour rechercher tous les messages SAP.