Question Re: Determination on save - Infinite loop issue (RAP) in Technology Q&A

Determination on save - Infinite loop issue (RAP)

muthuhana37 — Mon, 07 Aug 2023 16:45:36 GMT

Hello Team,

I have two determination like below where I want to update admin fields,

determination AdminCreate on save { create; }

determination AdminUpdate on save { create, update; }

While creating instance, I want create admin fields should be populated and while updating instance, update admin fields should be populated but somehow it causes infinite loop and getting below dump

Error analysis

The application has indicated exception "LCX_ABAP_BEHV_DETVAL_ERROR" as the reason for the
termination:
Infinite loop caused by cyclical triggering of on-save determinations

I need to understand,

How to resolve this because without using update EML inside the determination, how to populate values ?
Why create & update should need to define together in the trigger conditions ?
Any other approach is there for this use case ?

Thanks a lot.

Best Regards,

Muthu

Re: Determination on save - Infinite loop issue (RAP)

Andre_Fischer — Mon, 07 Aug 2023 19:28:43 GMT

Try to limit your determinations such that they are only triggered on field level.

Shortdump LCX_ABAP_BEHV_DETVAL_ERROR | SAP Community

Re: Determination on save - Infinite loop issue (RAP)

muthuhana37 — Tue, 08 Aug 2023 03:54:13 GMT

Thanks andre.fischer for your quick response.

Yes keeping trigger conditions on field level disappears the error but in my use case I want to populate these admin fields at the time of create & update.

I kept these fields as read only so from UI it will not get triggered while create/update instance.

Any suggestion here ?

Re: Determination on save - Infinite loop issue (RAP)

JessieCheah — Tue, 08 Aug 2023 08:15:35 GMT

Hi Muthu,

why not just have determination AdminUpdate on save { create, update; } and in your determination, evaluate if AdminCreate fields are initial, to skip AdminUpdate fields and vice versa (When AdminCreate fields are not initial, to populate AdminUpdate fields)?

Regards,

Jessie

Re: Determination on save - Infinite loop issue (RAP)

muthuhana37 — Tue, 08 Aug 2023 15:25:37 GMT

Hello jessie.cheah,

This again going for infinite loop because I have update request EML inside determination which triggers itself again and again.

When I change the trigger conditions to create alone which doesn't trigger for while updating the instance.

Re: Determination on save - Infinite loop issue (RAP)

JessieCheah — Wed, 09 Aug 2023 01:58:34 GMT

Oh yes you're right, because of the { update; }

But before we go further in, what are the admin fields that you are trying to populate? Are those self defined fields, or just fields like CreatedBy, LastChangedBy etc. ?

Re: Determination on save - Infinite loop issue (RAP)

muthuhana37 — Wed, 09 Aug 2023 03:35:05 GMT

just fields like CreatedBy, LastChangedBy etc.

Re: Determination on save - Infinite loop issue (RAP)

JessieCheah — Wed, 09 Aug 2023 06:32:39 GMT

You can use the following annotations in your base view, the framework will then fill up the admin fields automatically.

@Semantics.user.createdBy: true

@Semantics.user.lastChangedBy : true

@Semantics.user.localInstanceLastChangedBy: true

@Semantics.systemDateTime.createdAt: true

@Semantics.systemDateTime.lastChangedAt: true

@Semantics.systemDateTime.LocalInstanceLastChangedAt: true

See example https://github.com/SAP-samples/abap-platform-fiori-feature-showcase/blob/ABAP-platform-cloud/src/%23dmo%23fsa_i_root.ddls.asddls

Re: Determination on save - Infinite loop issue (RAP)

DiegoValdivia — Fri, 10 Oct 2025 20:54:40 GMT

For anyone else facing this same issue, I was able to avoid the infinite loop by using a Global Class with a Static Attribute to control if the Determination was already executed at least once.

Helper Class:

CLASS zcl_test_saver_helper DEFINITION PUBLIC FINAL CREATE PUBLIC . PUBLIC SECTION. CLASS-DATA: already_saved TYPE abap_boolean. PROTECTED SECTION. PRIVATE SECTION. ENDCLASS. CLASS zcl_test_saver_helper IMPLEMENTATION. ENDCLASS.

Behavior Pool Method

METHOD update_timestamps. IF zcl_test_saver_helper2=>already_saved EQ abap_false. zcl_test_saver_helper2=>already_saved = abap_true. READ ENTITIES OF ZI_Test1_S IN LOCAL MODE ENTITY Test1 ALL FIELDS WITH CORRESPONDING #( keys ) RESULT DATA(lt_res). MODIFY ENTITIES OF ZI_Test1_S IN LOCAL MODE ENTITY Test1 UPDATE FIELDS ( UpdateDate ) WITH VALUE #( FOR key IN keys ( %tky = key-%tky UpdateDate = cl_abap_context_info=>get_system_date( ) ) ) FAILED DATA(ls_failed) REPORTED DATA(ls_reported). ENDIF. ENDMETHOD.

Re: Determination on save - Infinite loop issue (RAP)

d_schuitemaker62 — Fri, 31 Oct 2025 12:50:41 GMT

I had to resort to the same solution. A pity that the system does not automatically do this max one time running of determinations.