How To Fix IW012 - Disporelevanz wird geändert

IW012 - Overview

• Message type: E = Error

• Message class: IW - Order Processing

• Message number: 012

• Message text: Disporelevanz wird geändert

<LB>&CAUSE&</>
In Customizing under <LS>Define Field Selection for Order Operations
(PM and CS)</> you have configured the field <LS>Reservation/P.Req</>
such that it is only displayed when control key &V1& is used. Thus, it
cannot be used to change the MRP-relevance.

Systemantwort

The MRP relevance is reset depending on the Customizing settings under
<LS>Define Change Documents, Collective Purchase Requisitions, MRP
Relevance</> and depending on the order status. The system proceeds as
follows:
<ZH>When creating an order:</>
The system sets the MRP relevance, that is currently configured with
the Customizing setting <LS>Define Change Documents, Collective
Purchase Requisition, MRP-Relevance</>.

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

<ZH>In status created (CRTD):</>
If the MRP-relevance is set to <LB>never</> in Customizing, the system
sets it to <LB>never</>.
If the MRP-relevance is set to <LB>immediate</> in Customizing, the
system sets it to <LB>immediate</>.
If the MRP-relevance is set to <LB>from release</> in Customizing, the
system sets it depending on the activation of the reservation /
purchase requisition:
If the generation of reservations and purchase requisitions was
activated manually using the pushbutton <LB>Activate Res/PReq (Ctrl+F3)
</>, the MRP-relevance is set to <LB>immediate</>.
If the generation of reservations and purchase requisitions was not
activated manually, the MRP-relevance is set to <LB>from release</>.
<ZH>In status released (REL):</>
If the MRP-relevance is set to <LB>never</> in Customizing, the system
sets it to <LB>never</>.
If the MRP-relevance is set to <LB>from release</> or <LB>immediate</>
in Customizing, then the system sets it to <LB>immediate</>.
<LB>When changing an existing order:</>
The system sets the MRP-relevance that was valid when creating the
order under the Customizing setting <LS>Define Change Documents,
Collective Purchase Requisitions, MRP-Relevance</>. This ensures the
consistency of the individual operations within an order, if, for
example, new operations are added and the MRP-relevance in Customizing
has changed in the meantime.
<ZH>In status created (CRTD):</>
If the MRP-relevance in Customizing was set to <LB>never</> for
creation, then the system sets it to <LB>never</>.
If the MRP-relevance in Customizing was set to <LB>immediate</> for
creation, then the system sets it to <LB>immediate</>.
If the MRP-relevance in Customizing was set to <LB>from release</> for
creation, then it is set depending on the activation of the reservation
or purchase requisition:
If the generation of reservations and purchase requisitions was
activated manually using the pushbutton <LB>Activate Res./P.Req (Ctrl+
F3)</>, or if the activation of the reservation/purchase requisition
was triggered by the change, then the MRP-relevance is set to
<LB>immediate</>.
If the generation of reservations and purchase requisitions was not
activating manually and was not triggered by the change, then the
MRP-relevance is set to <LB>from release</>.
<ZH>In status released (REL):</>
If the MRP-relevance in Customizing was set to <LB>never</> during
creation, the system sets it to <LB>never</>.
If the MRP-relevance in Customizing was set to <LB>from release</> or
<LB>immediate</>, the system sets it to <LB>immediate</>.

Wie behebe ich diesen Fehler?

Vorgehensweise für Systemadministratoren

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE