SAP系統BUG - info recorde的價格與Condition的不統一

原文：http://ssgang.itpub.net/post/10314/397943

Info Record中價格欄位: EINE-NETPR與Condition的欄位:KONP-KBETR有時會出現不統一的現象, 特別是在批量上傳Info Record時, 系統沒有同時更新兩個欄位, 造成不匹配. 系統有提供一個修正此BUG的程式: RM06INP0

處理建議:

1.Old Price和New Price均顯示"Not found"的 =>不要處理.

2.Old Price有,New Pirce "not found"的 =>無最新Infor.Record,給相關采購處理

3.Old Price和new price均有,且不一至的 =>去掉"Test Run",讓程式來更新價格.

最好給足條件,一個一個跑,且及時到內表中查看結果.不要一大批地跑,一旦發現錯誤,可以及時回復

祥見SAP Notes:

Symptom

After the change of the info record currency, the conversion factors between the order unit and the purchase order price unit are no longer correct on the purchasing view.The conversion factors between the base unit of measure and the order unit on the general view are, however, possibly correct.

However it is also possible that there are incorrect values in database table EINE.

A similar behavior can also occur for contracts.

Other terms

MEKPE, MEKP, EURO, WEWU, BME, BPRME, EINE, EINA, EINA-MEINS, EINA-LMEIN, KONP, KUMZA, KUMNE, LMEIN, MEKL, MEKLE, scheduling agreement, outline agreement, MEKRE, MEKR, EINE-NETPR

Solution

Implement the program correction.

Note:

Bear in mind that this note only has a preventive effect and cannot correct already existing data inconsistencies.

Proposed solution:

To eliminate possible data inconsistencies, we recommend that you carry out the currency conversion again.

Alternative:

Provided that, in the conditions of the affected purchasing documents, the conversion factors between the order unit and the purchase order price unit and also the prices in the conditions are correct, it is possible to carry out a correction using the following reports:

For info records: RM06INP0; also refer to Note 392988

For contracts: RM06ENP0

The 'No date check' indicator should be set for both reports.

After using the reports, it is not necessary to carry out a further currency conversion