sapnote_0000385830

8/10/2019 sapnote_0000385830

http://slidepdf.com/reader/full/sapnote0000385830 1/3

27.08.2013 of 3

SAP Note 385830 - Inconsistencies with goods movements inthe background

Note Language: English Version: 4 Validity: Valid Since 28.02.2001

Summary

Symptom

Goods movements are not completely updated.

Example: Material documents without accounting documents.

Additional key words

MMINKON, inconsistency, LMBWLU14, BAPI_GOODSMVT_CREATE, WMMBXY.

Cause and prerequisites

The SAP-internal function modules MB_CREATE_GOODS_MOVEMENT and

MB_POST_GOODS_MOVEMENT are used for the execution of a goods movement in

the background.

The data to be updated (Material document, stocks, valuation, ...) is

marked (through call of update modules IN UPDATE TASK or registration via

PERFORM ... ON COMMIT).If errors occur as of the start of these marks, you must make sure that

everything will be reset. Up to now, you could achieve this through sending

a termination message (MESSAGE A ...) which normally deletes the marked

program parts, releases all locks and finishes the transaction.

However,if the call of the above modules occurs with addition EXCEPTIONS

ERROR_MESSAGE, the system will also catch the termination message. It is

expected that the initiator evaluates the termination information that is

then situated in the global SY fields and that they react accordingly.

If this does not happen at all or incorrectly and if a COMMIT WORK is

triggered later, the system will execute the program parts that have been

marked until the occurrence of the error in the update.

Firstly, such an error behaviour is caused by customer-specific programsthat use modules while disregarding the fact that these modules are not

released. Secondly, the error behaviour is caused by SAP programs that have

EXCEPTIONS ERROR_MESSAGE in the call path in the case of call hierarchies

that are nested several times and they have these at a spot which cannot

correctly deal with the termination caused by the goods movement.

Important additional information

The above function modules may only be used by original SAP programs. The

modules have not been released for the use by customers (see release

statuses in Transaction SE37). If this will be done nevertheless, the

maintenance responsibility of SAP expires for possible damages. This will

also be valid if SAP program parts are copied and are used instead of the

originals in the production operation.

Solution

Carry out the program change.

New behavior

Errors which occur as of the start of the update mark will now immediately

cause a program termination (MESSAGE_TYPE_X). Only this approach ensures

the unconditional program ending. The previous MESSAGE A... requires the

initiator's programming discipline that does not exist.

As a result, the following behavior changes can occur:

o Applications which reported the termination message of the goodsmovement correctly as a log up to now cannot do this anymore.

8/10/2019 sapnote_0000385830


27.08.2013 of 3

SAP Note 385830 - Inconsistencies with goods movements inthe background

o Terminations during the book-in-phase of IDocs leave the

IDocs'status unchanged.

Errors that would now lead to a program termination on account of this

correction are not application errors (these are already displayed in the

dialog section) but they are serious errors that require a manual

intervention of the system administration. These errors cannot be

influenced by the end user.

Header Data

Release Status: Released for Customer

Released on: 12.06.2002 07:40:35

Master Language: GermanPriority: Correction with high priority

Category: Program error

Primary Component: MM-IM-GF-MB MB_CREATE_GOODS_MOVEMENT

Valid Releases

Software Component Release From

Release

To

Release

and

Subsequent

SAP_APPL 30 31I 31I

SAP_APPL 40 40B 40B

SAP_APPL 45 45B 45B

SAP_APPL 46 46B 46B

SAP_APPL 46C 46C 46C

Support Packages

Support Packages Release Package Name

SAP_APPL 31I SAPKH31I73

SAP_APPL 40B SAPKH40B60



SAP_APPL 46C SAPKH46C16

SAP_HR 31I SAPKE31I73

Related Notes

8/10/2019 sapnote_0000385830


sapnote_0000385830

Documents

Transcript of sapnote_0000385830