BADI -MRM_HEADER_CHECK implementation - MIRO - error MESSAGES TAB ??

[Former Member]

Hi All,

I implemented classic BADI- MRM_HEADER_CHECK to raise custom error message(type E) validation for Reference(XBLNR) and append error message using MRM_PROT_FILL and the error message appeared in MESSAGES tab of MIRO transaction.

However, if I have ONLY this custom error in MESSAGES tab and try to post the LIV document system let it post successfully. Usually system should return the "Invoice still has messages" if any error(type E) appear in MESSAGES tab and shouldn't allow posting.

Do i need to add more code in my MRM_HEADER_CHECK implementation ?? to ensure sytem recognizes my custom error message and shouldn't allow posting ??

Regards,

Sri,

[Former Member]

Hi All,

I implemented classic BADI- MRM_HEADER_CHECK to raise custom error message(type E) validation for Reference(XBLNR) and append error message using MRM_PROT_FILL and the error message appeared in MESSAGES tab of MIRO transaction.

However, if I have ONLY this custom error in MESSAGES tab and try to post the LIV document system let it post successfully. Usually system should return the "Invoice still has messages" if any error(type E) appear in MESSAGES tab and shouldn't allow posting.

Do i need to add more code in my MRM_HEADER_CHECK implementation ?? to ensure sytem recognizes my custom error message and shouldn't allow posting ??

Regards,

Sri,

[Former Member]

Check this thread in which Pablo Casamayor uses field symbol call stack technique (to retrieve values from main program memory) and use it to not allow saving in MIRO if there are still error messages.

Another problem also may arise that even if user corrects the invoice document still custom message may still show in the message log, for that issue also the post by Pablo clarifies.

[Pablo Casamayor's solution to MIRO messages problem with BADI: MRM_HEADER_CHECK |;

[nabheetscn]

There is also an exeption in the method HEADERDATA_CHECK also raise that exception ERROR after filling the error data.

Nabheet

[nabheetscn]

After filling the relevant error message raise the exception ERROR which is there in HEADERDATA_CHECK method.

In this way it will display message also and will not save

Nabheet

[nabheetscn]

There is also an exeption in the method HEADERDATA_CHECK also raise that exception ERROR after filling the error data.

Nabheet