Hello Experts,
While posting an invoice documents in Logistic Invoice Verification of MIRO and MR1M, the system is not updated in FI document or MM document.
Updated May 18, 2018
Hello Experts,
While posting an invoice documents in Logistic Invoice Verification of MIRO and MR1M, the system is not updated in FI document or MM document.
Comments
These errors does not occur in a standard system. The use of exits from areas of SD like USEREXIT_MOVE_FIELD_TO_VBAK. The hierarchy for the call are:
a) SAPLMR1M MODULE (PAI) FCODE_6000.
b) SAPLMR1M FORM FCOBU.
c) SAPLMR1M FORM BELEG_BUCHEN.
d) SAPLMRMP FUNCTION MRM_INVOICE_POST.
e) SAPLMRMP FORM FAKTURAINDEX.
f) SAPLV45M FUNCTION SD_PURCHASE_CHG_ORDER_STATUS.
The user use the option of ROLLBACK command, while a program already has some entries to an updated programs. Thus the result is that the entries are been reset, still the current is not terminated. The module functions that are executed with the ROLLBACK command with “IN UPDATE TASK” written in an updated program. All the entries are updates in database with COMMIT WORK command and it causes inconsistencies because of the update in MM documents.
If in case the MM documents are not to be founded then the FI follow on documents are set to be updated.
In other case if the FI follow on document are updated but MM documents are missing and the purchase history order is updated. In this term the implementation of customer define BAdI of INVOICE_UPDATE BAdI has to be examined.