Shulou(Shulou.com)06/02 Report--

SAP MM MIGO posting error reporting-balance calculated in local currency-countermeasure

Use the MIGO transaction code for purchase order 4500000191, perform receiving, system error:

The detailed error messages are as follows:

Balance in local currency

Message number F5703

Diagnosis

There is a balance in the local currency "VND" with the following details.

Exchange rate type "10", amount "1" and currency code "VND".

Data in the local currency has been transferred from the calling application.

The business background is that the business creates a return purchase order and returns it to a foreign supplier. Before returning the goods, the business staff made a batch segmentation, according to the actual business, the return quantity is composed of 8 batches. Due to the unit conversion, the number of each return batch is up to three decimal places, and the exchange rate conversion is also involved in this return business.

1) I encountered this kind of error in MIGO transaction for the first time, so I first thought of using this error message to look up information on the Internet. Some suggestions are as follows:

The error is in GL code

GO to FS00 GL Master, for your GL

Go to Control Tab and remove the check box which reads "Only Balance Local currecy"

Consult you FI teams once

According to the results of this inquiry, the author went to the financial consultant to help contact the financial business and modify the general ledger account. The financial adviser disagreed, saying that the "Only Balance Local currecy" mark could not be changed casually. He persuaded the financial adviser softly and hard, and the other side promised to help modify the editor, saying that he would hurry up and change it back after the post was successful. Unfortunately, this change was not successful. The SAP system reported an error that the balance of the general ledger account was not 0!

2) there's nothing we can do about it, so we have to make a big move and ask an ABAP consultant to help us find out what went wrong. After the Debug program, we found the following inner table data

The sum of column J (WRBTR) is not 0, but 0. 01.

The problem is that in the three rows of the yellow mark, the sum of the J columns of the three rows is 0.01 because the decimal point is rounded.

In DEBUG mode, modify the last decimal place in the data in the J column of the three rows to ensure that the sum of the J columns of the three rows is 0, and finally the MIGO posting is successful!

This problem can be regarded as solved by such a barbaric method. However, the author still hopes to find a more suitable way to solve similar problems, so it is arranged into this text, which can be regarded as throwing a brick to attract jade.

2019-05-05 was written in Suzhou.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.