topic Re: MFBF Dump in Application Development and Automation Discussions

MFBF Dump

Former Member — Sat, 23 Mar 2013 13:13:14 GMT

Dear Guru,

We are getting the dump as:

Error analysis

Short text of error message:

No status object is available for INL 0

Long text of error message:

Diagnosis

When trying to read the status of an object (INL 0), a system error

occurred: For object number TM0000000002QL there is no status

object.

Procedure

Please contact your system administrator.

Technical information about the message:

Message class....... "BS"

Number.............. 001

Variable 1.......... "INL 0"

Variable 2.......... "TM0000000002QL"

Variable 3.......... " "

Variable 4.......... " "

Did anybody faced this problem and solved?

Kindly, guide us.

Re: MFBF Dump

RaymondGiuseppi — Sat, 23 Mar 2013 19:27:28 GMT

First check for OSS note at your system level like Note 94699 - Prod. order/network/proc. order: Objects w/o status object. Error can come from an error in standard, so you could find corrections, else that can be caused by wrong customer coding, e.g. COMMIT WORK in a BAdI, Enhancement spot or Customer Exit or wrong usage of non released FM.

Some OSS notes contain correction reports, but if the error comes from a customer development, you have to identify and correct your code.

Regards,

Raymond

Re: MFBF Dump

Former Member — Mon, 25 Mar 2013 05:21:30 GMT

Hi Raymond,

Thanks a lot....Our problem got solved, User exits + Commit work was the culprit.

Again a thing to ask...COMMIT WORK when used in normal Z program works fine but when used in User exit it throws dump how come this can happen...presently we are using ECC 6.0....

Waiting for your reply.

Re: MFBF Dump

RaymondGiuseppi — Mon, 25 Mar 2013 08:13:47 GMT

In your Zprogram you are alone, no problem with Commit-work, in a customer-exit or BAdi, you are in the middle of a SAP transaction which manage its own checks and commit/rollback so your commit may (and will) break the logic of the current transaction.

A "commit  work" statement must not be executed within a user exit or a modification in an SAP transaction!

There are tools to execute such actions as BAPI call in an exit like using RFC enabled wrapper called IN BACKGROUND TASK or updating database z-tables via update task FM, those will be executed after/during the update task which update the database. In case of IN BACKGROUND TASK those are executed in a new LUW (like a new transaction) after completion of update task, so you can code BAPI call here.

Regards,

Raymond