"Type "ABAP_BOOL" is unknown" in sap fiori

[former_member282367]

Hi All,

After implementing the below sap note there are many error reflected.

2028544 - Request termination if currency or unit code is empty

  Error in the ABAP Application Program

  The current ABAP program "/IWBEP/CL_MGW_MED_PROVIDER====CP" had to be

   terminated because it has

  come across a statement that unfortunately cannot be executed.

  The following syntax error occurred in program

   "/IWBEP/BD_MGW_META_DATA_LOAD==CP " in include

   "/IWBEP/IF_MGW_MED_ODATA_TYPES=IU " in

  line 39:

  "Type "ABAP_BOOL" is unknown"

  " "

  " "

  " "

  The include has been created and last changed by:

  Created by: "SAP "

  Last changed by: "SPRLIT "

  Error in the ABAP Application Program

  The current ABAP program "/IWBEP/CL_MGW_MED_PROVIDER====CP" had to be

   terminated because it has

  come across a statement that unfortunately cannot be executed.

Kindly help out in solving the issue .

Thanks & Regards

Rakesh R

[Former Member]

We're encountering the same issue and have raised and OSS message on this.

Here is SAP's response:

Dear Customer,

Our developer has created note 2121266 for this problem. The error "Type "ABAP_BOOL" is unknown" is still occuring in your system. As a workaround, you can add the coding "type-pools ABAP." manually into the interface section of /IWBEP/IF_MGW_MED_ODATA_TYPES using SE24.

interface /IWBEP/IF_MGW_MED_ODATA_TYPES

     public .

     type-pools ABAP

                                             <<<=== please add manually!

     interface /IWBEP/IF_MGW_APPL_TYPES load .

Or, you can add ABAP as "type group/object type" using SE24->/IWBEP/IF_MGW_MED_ODATA_TYPES -> change ->Properties -> "forward declaration section".

To prevent the problem from occuring in the future, please implement note 2121268.

SAP Active Global Support

Let us know if this solved your issue.

Regards,

Kevin

[Former Member]

Hi

Thank you for the feedback. Note 2121268 has resolved our issue.

Regards,

Thashin

[Former Member]

Hi Guys,

Did you find any solution?

We are facing the same issue, any help will be appreciated,

[Former Member]

Hi Rodrigo,

Unfortunately not, I really wish SAP would respond on this.

I've seen this same issue now with two different customers. We submitted an OSS note to SAP and their response was to do a Core mod to the class to add TYPE-POOLS: ABAP.

The problem with this is now we are seeing this error in multiple classes, and we don't want to have to add modifications to each class.

[Former Member]

Tthank you for the quick response, I will open an OSS note and let you know if we find other solution.

[Former Member]

Hello

Has there been any reply from SAP on your OSS message? We face the same issue.

Regards,

Thashin

[Former Member]

Hello Thashin:

We got the same response, the solution is to go to change mode of /iwbep/if_mgw_med_odata_types and enter "TYPE-POOLS:  abap." in the line number 5,  it should look as below:

   PUBLIC  .

   TYPE-POOLS:  abap.

   TYPES  ty_e_med_entity_name  TYPE  /iwbep/med_external_name  .

Regards,

[Former Member]

Hello Rodrigo

Thank you for the suggestion. I will request our developers to implement this.

Regards,

[Former Member]

Hello Rodrigo

Any chance you can provide me with the OSS number that you have created for this issue? I am trying to work with our SAP support contact to get this included into a SAP Note.

Regards,

[Former Member]

Sorry, it was for a client, I no longer have access to it.

Regards,

[Former Member]

We are running into this same issue - any resolution?

[apoorva_singh]

Did you guys find any solution to this? We are facing the same issue...

Thanks & best regards...