Conversion exit in ABAP RESTful Programming Model

[Former Member]

I would like to develop a Fiori app based on the ABAP RESTful Programming Model, but when activating the service it gives an error.

"You cannot use the FIPEX conversion exit here" or "You cannot use the FMCIL conversion exit here"

I use many fields with conversion exits.

Isn't it generally intended in ABAP RESTful Programming Model?

Thanks for help

[venkateswaran_k]

Dear Tim

What was the conversion exit function you are using?

Regards,

Venkat

[Former Member]

Hey Venkateswaran,

In my first attempt the errors came with the exits FIPEX and FMCIL.

Now the exit ABPSN...

regards

[Andre_Fischer]

Hi Tim,

I assume you are trying to use conversion exits in SAP Cloud Platform ABAP environment, right?

Unfortunately I have to tell you that only conversion exit ALPHA can be used in SAP Cloud Platform, ABAP environment (released with 1905). All other SAP delivered conversion exits are not released and cannot be used in customer-defined domains.

Customer-defined conversion exists are supported taking following rules into account:

Use "Y" or "Z" as the first letter of the conversion exit

Create a function group using an ABAP namespace /.../ or as a local object

Create respective function modules CONVERSION_EXIT_cnvex_INPUT/OUTPUT which are technically part of the SAP namespace

In on premise systems 1909 onwards you can use any conversion exit.

Best Regards,

Andre

[Former Member]

Hey Andre,

thanks for your answer. I use on premise in version 1909. And FIPEX or FMCIL are standard SAP conversion exits.

Best regards

Tim

[Andre_Fischer]

Hi Tim,

in an 1909 on premise system the conversion exits defined in the domains are automatically called by the SAP Gateway Framework.

How are you calling your conversion exits?

Regards,

Andre

[chphaniv]

Hello Andre,

I am getting the the Conversion exit error while activating the Service Binding, and we are on 1909. Is there a workaround to fix this? Thanks in advance..

Regards,

Phani.

[Former Member]

Hey Andre and Phani,

i have the same error. I get the error while activating the service Binding in Eclipse.

I think it calls by itself. I do nothing but use a CDS View. It is called automatically by a data element?

[Sschlegel]

Hi Tim,

I have the same error - did you find a solution for it?

Thx in advance!

Regards

Sören

[Former Member]

Hi andre.fischer

I am experiencing the same error when trying to publish a service. We too are on 1909. Is there perhaps a solution that you could share with us please?

Kind regards,

[Former Member]

Hi carine.tchoutouodjomo and horst.keller

I am experiencing the same error when trying to publish a service. We too are on 1909. Is there perhaps a solution that you could share with us please?

Kind regards,

[Former Member]

looping martin.huvar

[Andre_Fischer]

Hi sharif.gool,

can you please tell me where this error occurs? That means which conversion exit / data element you are using ?

Best regards,

Andre

[rajeshkatkoori]

Hi Andre,

We are in 2020 and when I am doing my first Restful App i am getting the same error but for different standard domain 'Do not use conversion exit QTYRN here.' Please advice how to handle this error to display this field and activate the Service Binding for V2.

Regards,

Rajesh

[afordham]

I am also getting this error in on-premise 1909, trying to publish a Service Binding containing a CDS view that uses a field with data element KOTABNR:
'Do not use conversion exit KOTAB here.

[ivan_georgiev]

I am having a similar issue currently on a S/4 HANA (2020) system with the field TPLNR (Metadata not loaded - Do not use conversion exit TPLNR here...). Has anyone managed to find a solution for this?

[kretschj]

And if you on premise system 1909 and still get that error ? is there a workaround ?

[former_member759424]

I am also getting this error in on-premise 1909. And i have error

Backend Error: Do not use conversion exit NUMCV here.

For Odata service using Z* table with stadart data element

  vornr         : vornr;
  uvorn         : uvorn;

[kretschj]

The only way i could solve this problem was to build a view below and use the command "Cast" on the "SAP" Dataelement, to cast the entity on a identical entity, which does not have an Conv Exit. for example

Dateelemt with Conv Exit : PSPID -> used in I_project as Project:

cast(Project as Z_PSPID_FOR_RAP) as Project

andre.fischer : Would be nice if you could verfiy this solutions and also publish that solution, so that you get don't furstrated, if you want to use RAP at Project. The Notes provided by SAP for this problem are not really helpfull

[ThorstenWoehrle]

Hello all,

I also wanted to publish the service binding for my first RAP project and I also get the message with a conversion exit.

System is on-premise 2020 - last comment is almost one year old.
Are there any updates on this issues or ways to handle such problems?
Would be great especially for people starting to built their first app

Best regards
Thorsten

[Jelena_Perfiljeva]

Please use Comment button to reply to an existing answer.

[iyankannu_iyankannu]

In Tcode "/n/iwbep/errorlog " you should able find the Entity Property which has the Conversion exit mentioned in Error.

[Andre_Fischer]

Not in the cloud. But there you have the Error Log view in ADT

https://blogs.sap.com/2020/07/22/how-to-use-the-sap-gateway-error-log-in-adt/

which you however have to activate.

But soon it will become automatically part of the standard view in ADT :-).

[Renzo]

Hi Tim, please check this blog post: https://blogs.sap.com/2022/06/27/conversion-exits-and-the-abap-restful-application-programming-model....

[hongjonghwa11]

Thank you!