FI/ MM Document Missing for MIRO and MR1M

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. 

Please do as following:

a) Check if a user is exit in SD area. Branch the program of SAPMV45A with the use of Transaction SE80. For any routines that starts from "USEREXIT_", and check for command "ROLLBACK" or "MESSAGE A-" and remove them. If it has not been done then perform it quickly. 

b) If the documents of FI are not been updated then execute a report of ZREPMIR7 to perform the follow up posting of FI documents for those post which are incomplete. 

c) If the documents on FI are only updated then use the transaction SAMT for checking of here the usage of internal COMMIT WORK commands are working.

d) With the Updation of FI documents and the purchase order history in MM. Then check if the COMMIT WORK or ROLLBACK commands are being used in customer implementation of INVOICE_UPDATE BadI. These commands are to be removed.