posted 12 years ago
I have a BPEL service that calls a PL SQL procedure. I have added a new element to the BPEL called quote_cart_line.
All I had to the BPEL to accomplish this was edit 3 files -
Async_Invoke_Import_Model.xsd (Source)
APPS_NI_MODEL_IMPORT_UTIL_IMPORT_SELECTIONS.xsd (Target)
Transform_NIE_Inputs.xsl (Transforming from Source to Target)
I have done this to two other BPELs and they work fine. (1st BPEL calls the second BPEL passing this new element, which then passes it to this BPEL I am having trouble with, which then should be binding it to a PL SQL type)
So this BPEL calls a PL SQL procedure, binding the elements from the BPEL to a PL SQL type (ni_model_import_line). So I edited the PL SQL type to accept this new parameter:
I invoke all of this, and the new element gets populated in 3 different BPELs, including this one I explained here. But when it comes time to call the PL SQL I am now getting an error:
This doesnt happen if I remove the references to this new element and try again, so it obviously is a problem with the element, but I have no idea what it is. It works fine when going from BPEL to BPEL, but as soon as the process tries to call the PL SQL procedure this happens. It is even more frustrating because I have done this exactly before adding another element, and it worked fine...
Any ideas or tips please?
True wisdom is in knowing you know nothing - Socrates