Custom Alert is throwing an error in APPS.GMS_INSTALL

Question

1. We have created a custom alert and using Alert Manager we defined this new alert in applications.
2. In order to test this alert we navigated to Request -> Check and gave the Application Name, Alert Name and Start Date and submitted a new request.
3. To view this new alert, we have navigated to Request -> View.
4. The status shows Completed Normal, but when we click on view output, it is throwing the following error:
FRM-40735: WHEN-NEW-FORM-INSTANCE trigger raised unhandled exception ORA-06502.
ORA-06502: PL/SQL: numeric or value error: character to number conversion error
ORA-06512: at "APPS.GMS_INSTALL", line 31
Did anyone came across this error message? Any input is highly appreciated.
Thanks.

Answer 1

So, you are saying that the method runs successfully in SWO1 but fails when run inside the workflow? If that is the case, then, something is missing in the binding. Make sure your binding is correctly done. There are several levels of bindings:
Method <-> Standard Task, and Standard Task <-> Workflow Template. Make sure the binding in both places is correct. Clicking the check button often times provides hints at what could be wrong. Keep special attention to passing header lines to internal tables and vice versa.
If you are sure the binding is correct, then, set a break point in the method. There are many ways you can do that. First, you can change the standard task to "foreground" instead of "background" and assign yourself as the agent. The task will then show up in your inbox. Executing it will take you to the break point. The second trick is to write an infinite loop in the method as follows:
DATA:
  l_char1  VALUE '1',
  l_char2.
WHILE l_char1 = '1'.
  l_char2 = 'a'.
ENDWHILE.
What will happen is that when the task is executed in background, it will get stuck in this loop. Go to transaction SM50 to find the stuck process. Select that line then select menu option: Program/Session --> Program --> Debugging. This will open the debugger for you. In the debugger change the value of l_char1 to anything other than 1 and you'll exit the loop and be able to debug the rest of the code. If you forget to change the value and click F8, just go to SM50 again.