topic Re: How to delete standard error message in Application Development and Automation Discussions

How to delete standard error message

Former Member — Tue, 15 Jul 2014 09:19:35 GMT

Hello,

We have a requirement to create new charge credit instance ( BO FOPXD_TAXRPENT ). When an instance of New charge credit is created , an instance of the DO FOPXF_EXER is created which in turn creates an instance of DO Coding block item.

When this instance of coding block is created the BO creates an error message "G/L account missing ". (Message class: /ISCB/CB_CHECK Mesage number:004)

The call to the DO Coding block is made by the determination class CL_FOP_D_TAXRPENT_CRE_EXRCEXPL of BO FOPXD_TAXRPENT after this error message is added to the message handler the control returns to the above mentioned class.

As per our requirement, we need to delete this error message from the message handler in the BO FOPXD_TAXRPENT in class CL_FOP_D_TAXRPENT_CRE_EXRCEXPL.

Please suggest possible ways to access the error message and delete the same from the message handler in this class.

Thanks,

Subhankari

Re: How to delete standard error message

Former Member — Tue, 15 Jul 2014 11:25:06 GMT

Hi Subhankari,

From the above my understanding is that you dont want to show the above error message.

Check for the variable named ET_MESSAGES. Try to clear that internal table. Ideally it contains the messages to be shown on the screen.

Hope this helps.

Regards,
Sanket.

Re: How to delete standard error message

Former Member — Fri, 18 Jul 2014 06:09:11 GMT

Hi Sanket,

Thank you the prompt reply I tried the same but the ET_MESSAGE comes as initial as in this case the BO coding block is on ESF2 framework and the later BO FOPXD_TAXRPENT is on BOPF framework. So the message in being raised to the ESF framework handler in the coding block and we need to delete the message in the BOPF framework.

Is it feasible?

Regards,

Subhankari

Re: How to delete standard error message

bharath_k6 — Tue, 22 Jul 2014 11:40:58 GMT

Dear Subhankari,

I would suggest the following options.

1. Either you create a overwrite exit for the method in which error message is processed. Write only the code which is required for you in overwrite exit. or

2. Create Implicit enhancement to clear the ET_MESSAGES internal table or

Check any of the above options whichever is convenient to you.

Thanks,

Bharath.K