Trigger error but only in Apex

Question

I have a trigger with the following insert statement:
insert into oe_headers_iface_all(order_source_id,orig_sys_document_ref,order_type_id, created_by,creation_date,last_updated_by,last_update_date, sold_from_org_id,sold_to_org_id,operation_code,booked_flag)
values(1023, 'TESTING', 1116, 0, sysdate, 0, sysdate, 225,65372,'INSERT','N');
This trigger runs fine outside of Apex; it doesn't error and inserts those values into that table. But when I insert a record into my table through Apex, I get the following error:
ORA-01722: invalid number ORA-06512: at "APPS.RMA_TRACKER_T1", line 144 ORA-04088: error during execution of trigger 'APPS.RMA_TRACKER_T1'
If I comment out that insert statement it runs in Apex and does not error.
Any idea at all what could be making Apex so mad at this insert statement? It says "invalid number" but I've checked the fields over and over, and like I said if I just run that statement myself or insert a record in my table manually it runs and doesn't error, so Apex appears to be lying to me. Also, the Apex version is 4.0.1.00.03.
Edited by: Cydonia on May 25, 2011 3:54 PM

Answer 1

<sigh> I HATE problems like the one you described. VERY painful to deal with.
Let's review what you said.
1. the insert is fine outside apex
2. The insert crashes from within Apex with ORA-01722. Of course Oracle is not telling you which value
3. You already checked the "fields" over and over (no doubt!). Do you mean the datatypes or the data values?
insert into oe_headers_iface_all(order_source_id,orig_sys_document_ref,order_type_id, created_by,creation_date,last_updated_by,last_update_date, sold_from_org_id,sold_to_org_id,operation_code,booked_flag)
values(1023, 'TESTING', 1116, 0, sysdate, 0, sysdate, 225,65372,'INSERT','N'); I don't see anything unusual about the INSERT. Are the insert values really hard-coded like this? Pretty simple!
Any idea at all what could be making Apex so mad at this insert statement? It says "invalid number" but I've checked the fields over and over, and like I said if I just run that statement myself or insert a record in my table manually it runs and doesn't error, so Apex appears to be lying to me. Also, the Apex version is 4.0.1.00.03.Is the INSERT occurring through a PL/SQL routine you are executing via Apex or automatically through page submission?
Add debugging statements in the trigger to record every number and date field (convert to strings) in the trigger to find out what values you are dealing with. Either use htp.p to display character representations of the values OR write a quick debugging function using autonomous transaction to save and commit the values internally. If you use a debugging table concatenate all of thee fields together as strings to minimize the chances of getting the same error; make sure you enclose values in double quotes "'" to flag nulls in case something is being unexpectedly changed.
Something is happening that you don't suspect. Your VALUES list is straightforward and hard-coded so I wonder if trigger logic is trying to modify one of the values you listed. Perhaps multiple triggers and/or procedures and functions are involved.
Good luck!