Report quantity as blank or zero in the TO and keep it open for future pick

Question

Hi Gurus,
We have a scenario here an dneed your help:
We haev a transfer order created fro a delivery for 4 items. The system is showing that we have stock. While went for picking the one material is not there physically. While trying to confirm the TO in vl06o we can report blank for the material not picked and system converts it zero automatically. It ask for the confirmation of differences. If we say yes the system saves the TO and close it as confirmed. Now what will happen to the item which is not picked yet? How we can pick the remaining items? Is there any way?
Thanks for any help...
Shamsul

Answer 1

I might be understanding correctly, but I use cursor variables within a package all of the time. I have never tried calling the procedures from C++ but it is fairly simple in Java and wouldn't think C++ would be much different, just more involved.
In the package spec you have to define the ref cursor variable. If your cursor always returns the same rowtype then it is better to define the cursor, then define the ref cursor as c%rowtype. If the results of the cursor are going to change then you just define the variable as a ref cursor. These examples may help.
CURSOR eu_status_cur IS
SELECT eu_status
FROM item_eu_status;
TYPE eu_status_ref IS REF CURSOR RETURN eu_status_cur%ROWTYPE;
TYPE component_ref IS REF CURSOR;
The eu_status_ref will always return a single value row from the item_eu_status table while the second can return anything.
The package procedure then defines the parameters as one of these types.
PROCEDURE get_intermediate (
i_containing_id IN item.item_id%TYPE,
i_item_id IN item.item_id%TYPE,
o_formula OUT formula_ref,
o_eu_status OUT eu_status_ref,
o_special_library OUT special_library_ref,
o_sensory_attribute OUT sensory_attribute_ref,
o_application OUT application_ref,
o_raw_materials OUT raw_material_ref,
o_intermediates OUT intermediate_ref,
o_components OUT component_ref
Within the procedure you just open the ref cursor.
OPEN o_eu_status FOR
SELECT eu_status
FROM item_eu_status
WHERE item_id = i_item_id;
The client side will be different for Java vs C++ obviously. The OracleCallableStatement object takes care of most of the details when using Java, but since the (OCI) driver uses the OCI library I'm guessing that is where the real functionality is.