1. The document describes an issue where FI follow-on documents or MM documents are missing when invoices are posted using Logistics Invoice Verification. This can occur if commits or rollbacks are used in custom code or user exits. 2. It provides several recommendations to check for commits, rollbacks, or other issues in custom code like user exits or BAdIs that could cause inconsistencies. 3. The solution involves removing any commits or rollbacks from custom code, checking for issues in specific areas like user exits or workflows, and implementing notes that address related problems.

1. 743744
2019-11-07
743744 - MIRO, MR1M: FI follow-on documents or MM
documents are missing
Version 21 Type SAP Note
Language English Master Language German
Priority Correction with high priority Category External error
Release Status Released for Customer Released On 16.08.2017
Component MM-IV-LIV ( Logistics Invoice Verification )
Please find the original document at https://launchpad.support.sap.com/#/notes/ 743744
Symptom
You are posting invoices using Logistics Invoice Verification (MIRO, MR1M). When
you post some of the logistic invoice documents, the system does not update the
FI documents or the MM documents.
Other Terms
MMINKON, ZREPMIR7, MIRO, MR1M,update, USEREXIT_MOVE_FIELD_TO_VBAK, FAKTURAINDEX,
VBAK, VBUP, SD, commit, rollback, C_TEXTEDIT_CONTROL============CP,
GET_TEXT_AS_R3TABLE
Reason and Prerequisites
This error is not known to occur in the standard system.
You are using user exits from the SD area, such as USEREXIT_MOVE_FIELD_TO_VBAK.
The call hierarchy is as follows:
6 SAPLV45M FUNCTION SD_PURCHASE_CHG_ORDER_STATUS
5 SAPLMRMP FORM FAKTURAINDEX
4 SAPLMRMP FUNCTION MRM_INVOICE_POST
3 SAPLMR1M FORM BELEG_BUCHEN
2 SAPLMR1M FORM FCOBU
1 SAPLMR1M MODULE (PAI) FCODE_6000
(The user exit is called in the module SD_PURCHASE_CHG_ORDER_STATUS, and all
posting entries that were written to the update program before calling the
routine SAPLMRMP FAKTURAINDEX are deleted by the rollback). You are using other
customer-specific programs.
You use the ROLLBACK command in the customer-specific include, or the system
issues a message of the type "A", for example, which internally triggers a
ROLLBACK command. Since the program has already written some entries to the
update program at this time, these entries are reset. However, the program is
not terminated.
This means that all function modules executed after execution of the ROLLBACK
command with the addition "IN UPDATE TASK" write the entries to the update
program, and these entries are then updated in the database with the COMMIT WORK
command. This causes an inconsistency, since only the MM documents are updated.
You use the COMMIT WORK command in the user exits or in your customer-specific
programs. As a result, all records in the update program are updated. Following
this, an error occurs and a ROLLBACK command is triggered in the standard
system, and therefore no postings take place. At this point, only the remaining
entries are deleted from the update program. In this case, all MM documents are
missing, and FI follow-on documents are updated. Avoid commands, which lead to
1 of
© 2019 SAP SE or an SAP affiliate company. All rights reserved 5

2. 743744
2019-11-07
explicit database commits (such as 'COMMIT WORK' or 'ROLLBACK'), as well as
implicit database commits.
Implicit commits in the database are always triggered if the work process would
have to wait:
Sending an SAP screen
•
Sending a dialog message (E, I, W message).
•
Remote Function Calls (CALL FUNCTION...DESTINATION)
•
Call of a function module or termination of a function module in another
work process
•
CALL of the function module COMMIT CALL
•
CALL screens (POPUP)
•
may be possible by changing the screen after a call using CALL TRANSACTION
<t_code> or SUBMIT <program>.
•
Statements: EXEC SQL ..... commit work ... ENDEXEC
•
Statements: WAIT
•
Debugging, break points
•
If all the FI follow-on documents were updated but the MM document is missing
(tables RBKP, RSEG, and RBCO are empty) and only the purchase order history
(table EKBE) was updated, the customer-defined BAdI implementation of the
INVOICE_UPDATE BAdI should be examined.
Solution
1. Check the user exits in the SD area. Branch to the program SAPMV45A using
transaction SE80. For all form routines with a name that starts with
"USEREXIT_", check for the commands "ROLLBACK" or "MESSAGE A-" and remove
them. See Note 551929. If this note has not yet been implemented, you must
implement it immediately. Note that message V4 300 must be specified with
the type "E" in Customizing, so that the system exits the transaction and no
partial postings can take place if an error occurs in one of the SD user
exits.
2. If you are working with workflows, check your workflow process.
3. If the FI documents are not updated, see Note 382797, and execute the
report ZREPMIR7 to carry out a follow-up posting for (FI) documents that
were not posted completely.
4. If only the FI documents were updated, use transaction SAMT to check if
and where you are using internal COMMIT WORK commands. You must remove these
commands immediately.
5. If the FI documents are updated but only the purchase order history
(EKBE) is updated in MM, check whether the COMMIT WORK or ROLLBACK commands
are used in the customer-defined implementation of the INVOICE_UPDATE BAdI.
You must remove these commands immediately. Also look for implicit database
commits (see above) and remove them.
2 of
© 2019 SAP SE or an SAP affiliate company. All rights reserved 5

3. 743744
2019-11-07
6. After you have checked and implemented the recommendations from points 1-
5, if FI follow-on documents or MM documents are still missing, you must
implement the modification source code (alert function), to determine at
which points in the source code internal COMMIT WORK or ROLLBACK commands
are executed. Each time this is the case, the system issues the error
message "internal rollback occured" or "internal commit work occured". You
must also implement Note 619606 if has not yet been implemented in your
system.
7. Check whether the "FREE MEMORY" command is used in one of the SD user
exits or in other customer source code. It deletes the contents of the
memory area, and the modification will not work correctly.
Software Components
Software Component Release
SAP_APPL 45B - 45B
SAP_APPL 46B - 46B
SAP_APPL 46C - 46C
SAP_APPL 470 - 470
SAP_APPL 500 - 500
SAP_APPL 600 - 600
Correction Instructions
Software Component From To Version Changed on ID
SAP_APPL 500 500 3 31.05.2013 14:30:30 0001187838
SAP_APPL 470 470 5 31.05.2013 15:04:12 0001187837
SAP_APPL 46C 46C 10 31.05.2013 14:59:46 0000312512
SAP_APPL 600 600 8 31.05.2013 14:34:15 0000550609
Other Components
Component Description
3 of
© 2019 SAP SE or an SAP affiliate company. All rights reserved 5

4. 743744
2019-11-07
MM-IV-GF-UPD Database Updates
Prerequisites
Software Component From To SAP Note/KBA Title Component
SAP_APPL 46B 46C 363007 RMBABG00: Invoice posted twice MM-IV-LIV
SAP_APPL 600 600 924038 Subsequent correction for Note 862207 MM-IV-LIV-PP
SAP_APPL 600 600 1013722 Object link for IDOC not transferred MM-IV-GF-EDI
This document refers to
SAP Note/KBA Title
92550 Stock inconsistency due to customer enhancement (exit, BAdI)
803803 Catching error messages w/ local update in b/ground process.
781498 MIR4: Missing follow-on documents
765668 Problems during the post of documents
762943 MIRO: FI documents are missing with posted MM documents
657538 Incorrect totals record update by commitment carried forward
551929 SD document blocked: No billing-relevance (third-party) II
382797 MIRO: Analysis and repair for missing follow-on documents
203503 F5152 when posting IDocs
1776835 Preventing inconsistencies by posting termination in MM
175047 Causes for FI document number gaps (RF_BELEG)
1156325 BAdIs in the Logistics Invoice Verification environment
This document is referenced by
SAP Note/KBA Title
4 of
© 2019 SAP SE or an SAP affiliate company. All rights reserved 5

5. 743744
2019-11-07
1876234 Missing MM Invoice Documents
1776835 Preventing inconsistencies by posting termination in MM
175047 Causes for FI document number gaps (RF_BELEG)
382797 MIRO: Analysis and repair for missing follow-on documents
781498 MIR4: Missing follow-on documents
92550 Stock inconsistency due to customer enhancement (exit, BAdI)
1156325 BAdIs in the Logistics Invoice Verification environment
803803 Catching error messages w/ local update in b/ground process.
765668 Problems during the post of documents
762943 MIRO: FI documents are missing with posted MM documents
657538 Incorrect totals record update by commitment carried forward
551929 SD document blocked: No billing-relevance (third-party) II
203503 F5152 when posting IDocs
5 of
© 2019 SAP SE or an SAP affiliate company. All rights reserved 5