Skip to main content
Solved

ORA-06502 during CreateCopyProject – Event Action “Workflow” on C_ACTIVITY fails before BPMN starts

  • November 25, 2025
  • 1 reply
  • 12 views

Forum|alt.badge.img+5
  • Do Gooder (Customer)

Hello,

 

I am facing a blocking issue when using the projection:

CreateCopyProjectHandling.svc / CreateCopyProjectVirtual_DoCreate

The POST request executes correctly, but the backend returns this error:

 

DATABASE_ERROR ORA-20105: FndEventAction.EVENT_ACTION_ERROR: The Event Action "Workflow" on "C_ACTIVITY" has failed. ORA-06502: PL/SQL: numeric or value error: character string buffer too small ORA-06512: at "IFSAPP.FND_EVENT_ACTION_API" ... ORA-06512: at "IFSAPP.EVENT_SYS" ... ORA-06512: at "IFSAPP.C_ACTIVITY_EVI", line 11

What I observed

  • I have an Event Action attached to Activity / C_ACTIVITY which triggers a BPMN workflow.

  • The workflow never starts: no instance appears, the watcher shows no activity.

  • I removed all conditions and all OLD/NEW attributes from the Event Action → error still occurs.

  • I even tested with only Workflow ID enabled, same result.

  • Therefore it is not related to the BPMN process itself.

Analysis

I inspected the trigger C_ACTIVITY_EVI:

 

msg_ := Message_SYS.Construct('C_ACTIVITY'); Message_SYS.Add_Attribute(msg_, 'LU', 'Activity'); Message_SYS.Add_Attribute(msg_, 'ROWKEY', :NEW.ROWKEY); Message_SYS.Add_Attribute(msg_, 'NEXT_ID', DOC_NUMBER_COUNTER_API.FETCH_NEXT_NUMBER('EVENTBUS','-')); Event_SYS.Event_Execute('Activity','C_ACTIVITY', msg_);

Nothing here seems able to overflow VARCHAR2(32767).

According to the stack trace, the error occurs inside FND_EVENT_ACTION_API, during the internal execution of the Event Action "Workflow", not inside the trigger itself.

It looks like the Event Engine tries to serialize some attribute(s) from the newly created Activity (generated during project copy) and one of these values exceeds a VARCHAR2 buffer size.

As a consequence:

  • The Event Action fails before the BPMN Workflow engine is called.

  • The BPMN never starts.

  • The CreateCopyProject operation fails.


 

My question

Has anyone encountered issues where Event_SYS / FND_EVENT_ACTION_API fails with ORA-06502 during project copy, due to the internal payload generated for C_ACTIVITY events?

I need guidance on:

  1. Which Activity fields are included by default in the event payload for C_ACTIVITY.

  2. How to identify which field may exceed the buffer used by the Event Engine.

  3. Whether there is a configuration or workaround to bypass/extend this payload.

  4. Whether this is a known defect in CreateCopyProject or Event Framework.

Any help is appreciated 

Thanks!

 

Best answer by NINO

Solution to ORA-06502 on Event Action "Workflow" / C_ACTIVITY during CreateCopyProject

 

In the Custom Event configuration for C_ACTIVITY, two mandatory system attributes were disabled:

  • ROWKEY

  • ROWVERSION

These attributes are required by the internal Event Engine to construct a valid event payload for C_ACTIVITY.

 

Solution Manager → Configuration → Events → Custom Event → C_ACTIVITY

Enable both:

  • ROWKEY → New Value = Yes / Old Value = Yes

  • ROWVERSION → New Value = Yes / Old Value = Yes

(see screenshot)

Once these attributes are enabled:

The event payload is correctly generated
The Event Action no longer fails
The BPMN workflow is triggered normally
CreateCopyProjectVirtual_DoCreate executes successfully

 

 

1 reply

Forum|alt.badge.img+5
  • Author
  • Do Gooder (Customer)
  • Answer
  • November 25, 2025

Solution to ORA-06502 on Event Action "Workflow" / C_ACTIVITY during CreateCopyProject

 

In the Custom Event configuration for C_ACTIVITY, two mandatory system attributes were disabled:

  • ROWKEY

  • ROWVERSION

These attributes are required by the internal Event Engine to construct a valid event payload for C_ACTIVITY.

 

Solution Manager → Configuration → Events → Custom Event → C_ACTIVITY

Enable both:

  • ROWKEY → New Value = Yes / Old Value = Yes

  • ROWVERSION → New Value = Yes / Old Value = Yes

(see screenshot)

Once these attributes are enabled:

The event payload is correctly generated
The Event Action no longer fails
The BPMN workflow is triggered normally
CreateCopyProjectVirtual_DoCreate executes successfully