When the system converts to an alternative unit of measure in the operation, the numerators and denominators are switched.
The error does not occur until after an upgrade from 2.2A-2.2C or 2.1A-2.1I to a higher release level, or in an upgrade from 2.2S-2.2C or 2.1A-2.1I after 3.0, if you maintained your routings up to 2.2C/2.1I such that the result was correct, even though the documentation on the conversion factors states that the conversion factors should have been maintained exactly the other way around.
Program error corrected in 2.2D/2.1J.
SolutionChange the master data (routing) and order data. To do this, write a report that you execute once and that swaps the conversion factors in the operations. The report does NOT block the data to be changed and must not be performed while routings and/or orders are being changed in the system.
The report changes only the current client data. When there are
several clients active, begin the report either in each client
respectively or extend the DB instructions with CLIENT SPECIFIED,
so that all clients are included in a run.
TABLES: PLPO, AFVV.
DATA: L_UMREZ LIKE PLPO-UMREZ.
SELECT * FROM PLPO
WHERE ( UMREZ <> 1 OR UMREN <> 1 )
AND ( UMREZ <> 0 OR UMREN <> 0 ).
CHECK PLPO-UMREZ <> PLPO-UMREN .
WRITE: / PLPO-PLNTY, PLPO-PLNNR, PLPO-PLNKN,
PLPO-UMREZ, PLPO-UMREN.
IF PLPO-UMREZ = 0.
PLPO-UMREZ = PLPO-UMREN.
PLPO-UMREN = 1.
ELSE.
L_UMREZ = PLPO-UMREZ.
PLPO-UMREZ = PLPO-UMREN.
PLPO-UMREN = L_UMREZ.
ENDIF.
UPDATE PLPO.
ENDSELECT.
SELECT * FROM AFVV
WHERE ( UMREZ <> 1 OR UMREN <> 1 )
AND ( UMREZ <> 0 OR UMREN <> 0 ).
CHECK AFVV-UMREZ <> AFVV-UMREN .
WRITE: / AFVV-AUFPL, AFVV-APLZL,
AFVV-UMREZ, AFVV-UMREN.
IF AFVV-UMREZ = 0.
AFVV-UMREZ = AFVV-UMREN.
AFVV-UMREN = 1.
ELSE.
L_UMREZ = AFVV-UMREZ.
AFVV-UMREZ = AFVV-UMREN.
AFVV-UMREN = L_UMREZ.
ENDIF.
UPDATE AFVV.
ENDSELECT.
Key word: Scheduling
No comments:
Post a Comment