Update Recv.Point of an Item in Delivery

Hi Experts,
I need to update the Ext.Delivery(LIKP-LIFEX), Recv.Point(LIPS-EMPST) for a Delivery. Is there any FM through which we can update these two fields.
I found the BAPI BAPI_INB_DELIVERY_CHANGE thorough which we can update the Ext.Delivery. But I couldn't find any BAPI which will update Recv.Point which is at Item level. Can any body help me in this regard.
I can't BDC in this regard.
Regards,
Krishna K.

You can use Update List Item action in the workflow to update the check box field in List A. This workflow will called from List B when Item added to the List B.
Check the below link for example
http://rishijagati.blogspot.com/
Other option is you can use event handlers to achieve the functionality.
http://msdn.microsoft.com/en-us/library/gg252010%28v=office.14%29.aspx
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

Similar Messages

SHPCON serial number updates item on delivery but not item in HU

I am using SHPCON to update the item on delivery with serial numbers. After that I use SHPCON to pack that same item in a handling unit. From the pack screen I should be able to select the item and hit the serial number button and see the serial number. Instead it says there is no serial number on the item. I populated E1EDL11 under E1EDL24 to get the serial number on the item. I also tried during packing populating E1EDL46 under the HU item E1EDL44 but that doesn't work either.
Anybody run into this issue?

Hi,
If your Sloc is HU managed then need to maintain serial numbers in HU only.
i think you are doing packing at shipment level, HU should packed and serial numbers assigned then finally assigned to shipment document.
Rgds,
Kris.

Since i updated lion the pointer will not show contents when i hover the pointer over the item....

Since i updated lion on mac pro the pointer will not show contents whil hovering the pointer over the item.... ???

If you use extensions like Adblock Plus or NoScript or Flashblock that can block content then make sure that such extensions aren't blocking content. 
You can see the installed Firefox extensions in "Tools > Add-ons > Extensions".
Start Firefox in [[Safe Mode]] to check if one of your add-ons is causing your problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
See [[Troubleshooting extensions and themes]] and [[Troubleshooting plugins]]

Need to determine plant and storaeg location for item in delivery

Hello All,
I have an inbound IDOC which changes the quantity of items in a delivery and also adds new items if necessary. I need to do a auto PGI also if required.
Am using BDC to update the delivery. Now the problem is when I add a new item to the delivery. I add the material, quantity and Unit recieved from the IDOC. I need to determine the plant and storage location and fill that too in the delivery.
Kindly let me know how I can determine these two values. Which table holds this data?
Please note that I am changing only the delivery. The document preceding the delivery wont be changed.
Thanks for your help.
Regards,
Johnson

normally the plant is determined on this basis:
customer inforecord (table KNMT)
customer master (KNVV)
material (MVKE)
The storage location is determined in table TVKOL based on:
shipping point (you have it in delivery header LIKP-VSTEL)
plant (see above)
storage conditions (material master MARA-RAUBE)
regards
Roberto

Shipping point is missing from automatic delivery for external operation

Hi All,
I have tried to do one operation vy external processing. All the configuration and master data done. But during the goods receipt for the material from vendor after processing (t code MIGO) system is providing message as "Shipping point is missing from automatic delivery".
1. In the control key, automatic GR is not there, so from where automatic delivery is coming?
2. I have maintained the shipping point for the plant as plant in SPRO>LOG Exe> Shipping> Shipping point and goods receiving point determination> Assign good receiving point for In bound deliveries.
Please provide the solution.
Thanks
Krishna

Dear friend,
As far as i know:
1. check out the shipping point assignment to plant : t-code OVXC ; just in case make sure your shippong point is correct - goto spro->enterprise strucutre->definition->logistics execution->def.,copy,del,check shipping point
2. make sure your SC (shipping condition) and loading group are correct in the "Shipping point determination";
also make sure you did GR points assignment correctly (the next item in IMG)
good luck!

Delete non-picked items in delivery using iDoc

Hello gurus,
I'm integrating SAP ECC and external WM solutions using iDocs. The outbound delivery is created in SAP ECC and sent to WMS using DESADV iDoc. The picking is performed in WMS and the list of shipped items with batch numbers are returned to SAP and Goods Issue is posted. iDoc WHSCON is supposed to be used for that purpose.
The problem is that in case if not all the line items were shipped it's necessary to delete them from the delivery because otherwise GI will not be posted. But the non-picked items no longer exist in the response iDoc WHSCON so it's even impossible to set QUALF=DEL for these items. WMS sends back only actually shipped items in iDoc, and not the deleted ones.
Do you have any solutions for overcoming this problem?
Maybe there is any BAPI or iDoc qualifier that will allow to delete all items from the delivery so that they will be recreated by the same iDoc? Or there is any checkbox in SAP that will automatically delete unpicked items during posting of GI?
Thanks!

hi
in this both error comes ,
1)E VL 609 20 Delivery has not yet been put away / picked (completely)
a) picking quantity not entered , in delivery , first you enter the picking quantity ,
you create the 2 lines for sale order , so create for one line item for delery , go to vlo1n enter shipping point , sale order number line item number 1 to 1 enter press enter system will take only one item in delivery then you enter the picking quantity , and pgi ,
in delivery two line item only line item enter picking quantity and another line item not enter the picking quantity , it not possible to pgi , both line item you enter the picking quantity ,
you create the same delivery number for 2line item , so first complete the 1st line item pgi and , go to vl02n and enter , click on menu bar out bound deliverrs-delivery sale order -enter sale order number and line item , and do the pgi ,
2)VL 608 20 Delivery has not yet been completely processed by WM
you process activate the wm , so you can do the lt03 , then it will come vlo2n and check the picking quantity it will come auto matically

Getting Error when deleting line item of delivery

Hi,
I have cancelled the billing document and set the delivery pick quantity as zero for line item of a delivery and when i am trying to delete that particular line item of delivery, i am getting error message as 'Billing is already exist'. Please suggest how to delete the delete the delivery line item.

Hi Krish,
1) U can delete the SC at header level , only if it has not yet approved.
2)Once the SC is approved you can delete the SC at Item level under following conditions:
You cannot delete items that have already been approved and for which follow-on
documents already exist in the backend system, if:
A purchase requisition was created and the completed indicator is set for it,
or the quantity received for the purchase order is equal to or greater than the
quantity requested.
A reservation was created and the final issue indicator is set for it or the
quantity withdrawn equal to or greater than the quantity requested.
A purchase order was created and the delivery completed indicator is set for
it, or a goods receipt has already been entered.
You cannot delete service items that already exist in the backend system.
Hope this will help u.
Award points for suitable anwser !

I need a FM to update batch no. & picking qty. of delivery also to do PGI.

I need a FM to update batch no.& picking qty of delivery items as well as to do PGI (Post goods issue) for the same delivery.I am using 'WS_DELIVERY_UPDATE' but it doesn't update the batch no. and gives error saying no bactches are deifned for delivery no XXXXX and item XXXX.Can any one suggest the suitable function module to do this? It will be better if you can give details about input parameters with example.
Thanks & Regards,
Nimish Dongare.

Hi,
I used the following code for both picking & PGI...I think it shud also work for updating the batch details.
Picking:
*get header data
WA_VBKOK-VBELN_VL = <DEL_NBR>
WA_VBKOK-VBELN = VBFA-VBELV
get line data
LOOP AT TAB_VBPOK.
TAB_VBPOK-VBELN_VL = WA_VBKOK-VBELN_VL.
tab_vbpok-posnr_vl = <line number> '900001'
tab_vbpok-matnr= <material nbr>
tab_vbpok-charg= <batch nbr>
tab_vbpok-pikmg =<pick qty>
tab_vbpok-meins= <uom>
 TAB_VBPOK-VBELN = SY-DATUM.
 TAB_VBPOK-POSNN = SY-UZEIT.
 TAB_VBPOK-VBTYP_N = VBFA-VBTYP_N.
 SELECT * INTO TABLE TVBFA FROM VBFA
 WHERE VBELV = WA_VBKOK-VBELN_VL.
 SORT TVBFA DESCENDING.
 CLEAR TVBFA.
 READ TABLE TVBFA WITH KEY VBELV = TAB_VBPOK-VBELN_VL
 POSNV = TAB_VBPOK-POSNR_VL
 VBTYP_N = 'Q'
 TAQUI = ' '.
 IF SY-SUBRC EQ 0.
 V_PIKMG = TAB_VBPOK-PIKMG + TVBFA-RFMNG. " Picking quantity
 CLEAR TVBFA.
 READ TABLE TVBFA WITH KEY VBELV = TAB_VBPOK-VBELN_VL
 POSNV = TAB_VBPOK-POSNR_VL
 VBTYP_N = 'Q'
 TAQUI = 'X'.
 IF SY-SUBRC EQ 0.
 V_PIKMG = V_PIKMG + TVBFA-RFMNG. " Total Picking quantity
*****Error Message: Picked quantity is larger than the quantity to be delivered.
 IF LIPS-LFIMG LT V_PIKMG.
 PERFORM GET_RETURN USING 'E' 'VL' '019' SPACE SPACE SPACE SPACE
 RETURN.
 V_EXIT = 'Y'.
 EXIT. " EXIT THE RFC.
 ENDIF.
 ENDIF.
 ENDIF.
 MODIFY TAB_VBPOK.
CALL FUNCTION 'WS_DELIVERY_UPDATE_2'
 EXPORTING
 VBKOK_WA = WA_VBKOK
 SYNCHRON = 'X'
 DELIVERY = WA_VBKOK-VBELN_VL
 UPDATE_PICKING = 'X'
 COMMIT = 'X'
 IF_DATABASE_UPDATE_1 = '1'
 TABLES
 VBPOK_TAB = TAB_VBPOK
 PROT = I_PROTT.
 IF NOT I_PROTT IS INITIAL.
 RETURN-TYPE = 'E'.
 RETURN-MESSAGE = 'Picking Failed!'.
 EXIT. "EXIT THE RFC
 ELSE.
 COMMIT WORK AND WAIT.
 ENDIF.
PGI
*get header data
WA_VBKOK-VBELN_VL = <DEL_NBR>
WA_VBKOK-VBELN = VBFA-VBELV
CALL FUNCTION 'WS_DELIVERY_UPDATE_2'
 EXPORTING
 VBKOK_WA = WA_VBKOK
 SYNCHRON = 'X'
 DELIVERY = WA_VBKOK-VBELN_VL
 NICHT_SPERREN_1 = 'X'
 IF_ERROR_MESSAGES_SEND = 'X'
 TABLES
 PROT = I_PROTT.
IF NOT I_PROTT IS INITIAL.
 RETURN-TYPE = 'E'.
 RETURN-MESSAGE = 'Goods Issue Failed!'.
 EXIT. "EXIT THE RFC
ELSE.
 COMMIT WORK AND WAIT.
endif.
thanks

Update Column value after current item is Approved and then publish major version using Sharepoint 2013 designer workflow

Hi,
We have a requirement to update a column value once the item has been approved.
Following settings have been made in the publishing articles list:
Require content approval for submitted items : yes
Create major and minor (draft) versions
Who should see draft items in this document library? :Only users who can edit items
Require documents to be checked out before they can be edited? : yes
I have createdatu a Sharepoint 2013 workflow to check if Approval sts of current item = 0 i.e. Approved , then check out and update the item and finally checkin the item. Everything works fine till this point except that the minor version of the item is
checked in. Due to this the updated columns are not published to others.
Also, I created a Sharepoint 2010 workflow to SET CONTENT APPROVAL = APPROVED and started this workflow from my list workflow above, but the item does not get checked-in and always shows "In Progress" status with comment "The item is currently
locked for editing. Waiting for item to be checked in or for the lock to be released.".
Please let me know where I am missing out so that once the item is approved, column value gets updated and current item is still in Approved status.
Thanks

Hi,
According to your post, my understanding is that you want to update Column value after current item is Approved and then publish major version using Sharepoint 2013 designer workflow.
You will get into this kind of Catch-22 situation trying to set the Content Approval Status in SharePoint Designer workflow:
- You must check out the document before you can change the Content Approval Status
- You can't change the Content Approval Status once the document in checked out
Since you set the Require documents to be checked out before they can be edited=Yes, you will need to check out the document when run the workflow on the item. But you cannot approve a document when it is checked
out. So the logic in workflow conflicts.
As a workaround, you can use the Start Another Workflow action to start the normal Approval workflow on the document. The built-in Approval workflow can work with a document that’s not checked out.
The designer approval workflow also can work with a document that’s not checked out.
You can create two workflow using SharePoint Designer 2013.
First, create a SharePoint 2010 platform workflow.
Then, create a SharePoint 2013 platform workflow.
Then when the SharePoint 2013 platform workflow start, it will start the SharePoint 2010 platform workflow to set content approval status, then the SharePoint 2013 platform workflow will update current item value.
More information:
SharePoint Designer Workflow Content Approval Issue
SharePoint 2010 Approval Workflow with Content Approval
Best Regards,
Linda Li
Linda Li
TechNet Community Support

System should not allow to add line items in delivery

Hi,
1) system should not allow to add line items in delivery( in reference to sales order or STO)
2) sales order/STO should not be changed if delivery exists
how to control the above
Alec

Hi Lakxmi,
I found answer for 1st point from you are old answers.
can you throw somelight on 2nd point.
Thanks
Anil

Order related item and delivery related item in one billing document

Hi Experts,
how can we include order related item and delivery related item in one billing document .
Please give me the configuration logic .

Hello,
1)Reference Document Number VBRK-XBLNR.
In transaction VTFA and VTFL at header level setup the field 'Reference number' so that it is the same (example 'E')
2) Payment Reference VBRK-KIDNO
It should be a consequence of the split, and not a cause. So you can ignore it
3) Billing date for billing index VBRK-FKDAT
In sales order and delivery you should set the same billing date. Alternatively, the the first screen of VF01 please set a Defailt billing date
4) Customer purchase order number VBRK-BSTNK_VF
It is necessary that sales order to be billed and sales order referenced to delivery to be billed have the same purchase order number. There is not other way.
5) Assignment number VBRK-ZUONR
In transaction VTFA and VTFL at header level setup the field 'Assignment number' so that it is the same (example 'E')
6) Translation Date
Same solution of point 3.
Best regards,
Ivano.

PGI per item in delivery using VL06G

Hello All,
I have created an order with 2 items and delivery for 2 items, but picked only 1 item fully and want to do PGI for that item with out deleting the second item from delivery.
I tried doing PGI (VL02N) for this item system give below message :
MT     Area     Msg. Item    Message Text
E         VL        609   20        Delivery has not yet been put away / picked (completely)
E         VL        608   20       Delivery has not yet been completely processed by WM
I tried from VL06G to do PGI using "Display delivery items" as PGI can be done by selecting the item as well. But this dint work.
Can any body explain how to do PGI for few items in delivery with out deleting the unpicked items.
Regards,
Praveen

hi
in this both error comes ,
1)E VL 609 20 Delivery has not yet been put away / picked (completely)
a) picking quantity not entered , in delivery , first you enter the picking quantity ,
you create the 2 lines for sale order , so create for one line item for delery , go to vlo1n enter shipping point , sale order number line item number 1 to 1 enter press enter system will take only one item in delivery then you enter the picking quantity , and pgi ,
in delivery two line item only line item enter picking quantity and another line item not enter the picking quantity , it not possible to pgi , both line item you enter the picking quantity ,
you create the same delivery number for 2line item , so first complete the 1st line item pgi and , go to vl02n and enter , click on menu bar out bound deliverrs-delivery sale order -enter sale order number and line item , and do the pgi ,
2)VL 608 20 Delivery has not yet been completely processed by WM
you process activate the wm , so you can do the lt03 , then it will come vlo2n and check the picking quantity it will come auto matically

How to update loading point using a BAPI

Does anyone know how to update loading point in a delivery using a BAPI / function module like BAPI_OUTB_DELIVERY_CHANGE. We could populate loading point in the structure for function module ws_delivery_update2. But it does not update the loading point.
Thanks
Edited by: Satyanarayana Tiruveedhi on Mar 13, 2009 6:11 AM

Paul, I don't know if the person I'm trying to advise (who uses a Mac) will be able to do as you suggest. However, I thought this would be an interesting exercise for me to try myself just to see if I can get it to work.
I tried your suggestion on all three of my devices, with no success (PAP2T, SPA2102, and SPA504G)...?
Once I have uploaded the .bin file(s) to my web site, are you saying that the only setting change I need to make is to just enter the exact path to the uploaded file in the field "Upgrade Rule" ? This doesn't seem to enable the upgrade procedure on any of my devices that I tried it on (even after a manual power off/on reset). Upgrade Enable is set to "yes" (the default).
P.S.
My original path was using https://. So, I just changed it to http:// on the spa504g, and this time the LCD display has the message: "Upgrading Firmware, Please do not turn off power...". Problem is, all my registration lights stay green, and no lights are blinking to indicate an upgrade is in progress. Then after a few minutes, or so, the LCD display returns back to normal display (Upgrade message dissappears). All is normal, but spa504g did not do a firmware upgrade....?
Actually, my spa504g already has latest firmware at 7.5.3. So, I'm trying to downgrade back to 7.5.2b, just to test out this procedure.
Message was edited by: Jeff Bourgeois

Eng_eco_pub.process_Eco for UPDATE of effectivity_date on revised items

Hi All,
We are on Oracle Applications Rel 11.5.8.
We are trying to update an existing ECO with an ‘UPDATE’ transaction_type using eng_Eco_pub API. Here is the code. We first execute this script with CREATE and ECO is created. However, when we run the same script to UPDATE with transaction_type = ‘UPDATE’, the bill_sequence_id in eng_revised_items is updated to g_miss_num (9.99E125). The API is returning ‘SUCCESS’ and updates the bill_sequence_id to 9.999E125. Not sure what we are missing here. Appreciate any inputs or sample code for UPDATING an already created ECO.
REVISED_ITEM_ID BILL_SEQUENCE_ID CHANGE_NOTICE
11668210 192981011 IK-API0316
REVISED_ITEM_ID BILL_SEQUENCE_ID CHANGE_NOTICE
11668210 9.99E125 IK-API0316
Thank You!
DECLARE
l_eco_name VARCHAR2(10) := 'IK-API0000' ;
l_org_code VARCHAR2(3) := 'GLO';
l_transaction_type VARCHAR2(10) := 'CREATE'; -- or UPDATE for updating the same ECO
l_rev_item_number1 VARCHAR2(20):= '16-2214-01';
l_eff_date DATE := NULL;
v_old_effective_date DATE;
l_new_revised_item_revision VARCHAR2(3) := '-A0';
l_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
l_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
l_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type ;-- := Eng_Eco_Pub.g_miss_revised_item_tbl;
l_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
l_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
l_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
l_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
l_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
l_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
-- API output variables
x_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
x_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
x_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type ;-- := Eng_Eco_Pub.g_miss_revised_item_tbl;
x_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
x_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
x_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
x_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
x_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
x_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
-- Other API variables for return status / error handling / debugging
l_error_table Error_Handler.Error_Tbl_Type;
l_return_status VARCHAR2(1) := NULL;
l_msg_count NUMBER := 0;
l_output_dir VARCHAR2(500) := '/apps/orarpt/SJDEV/utl';
l_debug_filename VARCHAR2(60) := 'test.dbg';
-- WHO columns
l_user_id NUMBER := -1;
l_resp_id NUMBER := -1;
l_application_id NUMBER := -1;
l_row_cnt NUMBER := 1;
l_user_name VARCHAR2(30) := 'CA_ADMIN';
l_resp_name VARCHAR2(30) := 'Engineering';
l_comp_eff_date date := null;
l_disable_date date := null;
BEGIN
-- Get the user_id
SELECT user_id,sysdate + 10,sysdate
INTO l_user_id,l_comp_eff_date,l_eff_date
FROM fnd_user
WHERE user_name = l_user_name;
-- Get the application_id and responsibility_id
SELECT application_id, responsibility_id
INTO l_application_id, l_resp_id
FROM fnd_responsibility_tl
WHERE responsibility_name = l_resp_name;
FND_GLOBAL.APPS_INITIALIZE(l_user_id, l_resp_id, l_application_id); -- Mfg / Mfg & Dist Mgr / INV
dbms_output.put_line('Initialized applications context: '|| l_user_id || ' '|| l_resp_id ||' '|| l_application_id );
dbms_output.put_line('before initialixe');
Error_Handler.Initialize;
l_return_status := NULL;
dbms_output.put_line('after initialixe');
-- FOR UPDATE API to update effectivity date on Revised item.
l_eco_rec.eco_name := l_eco_name;
l_eco_rec.organization_code := l_org_code;
l_eco_rec.change_type_code := 'DESIGN';
l_eco_rec.eco_department_name := NULL;
l_eco_rec.priority_code := NULL; --'Medium';
l_eco_rec.approval_list_name := NULL; --'SU_ONLY';
l_eco_rec.reason_code := NULL;
l_eco_rec.Approval_Status_TYPE := 5 ;-- 'Approved'; -- will default to Not submitted for Approval
l_eco_rec.Status_TYPE := 1; -- 1 to bring in SCHEDULE status
l_eco_rec.description := l_eff_date || ' - ECO - '||l_eco_rec.eco_name ;
l_eco_rec.transaction_type := l_transaction_type;
l_eco_rec.return_status := NULL;
IF l_transaction_type ='CREATE' THEN
l_revised_item_tbl(l_row_cnt).transaction_type := l_transaction_type; -- transaction type : CREATE / UPDATE
l_revised_item_tbl(l_row_cnt).eco_name := l_eco_name;
l_revised_item_tbl(l_row_cnt).organization_code := l_org_code;
l_revised_item_tbl(l_row_cnt).revised_item_name := l_rev_item_number1;
l_revised_item_tbl(l_row_cnt).new_revised_item_revision := '-A0'; -- pass only if the previous unimplemented updating ECO has a new revision
l_revised_item_tbl(l_row_cnt).Updated_Revised_Item_Revision := ''; -- l_new_revised_item_revision;
l_revised_item_tbl(l_row_cnt).start_effective_date := l_eff_date;
l_revised_item_tbl(l_row_cnt).new_effective_date := l_eff_date ; -- l_comp_eff_date;
l_revised_item_tbl(l_row_cnt).alternate_bom_code := null;
l_revised_item_tbl(l_row_cnt).status_type := 1; -- 'Open'
l_revised_item_tbl(l_row_cnt).change_description := l_rev_item_number1 || ' --B0 ECO - '||l_eco_rec.eco_name ;
l_revised_item_tbl(l_row_cnt).disposition_type :=1 ;
l_revised_item_tbl(l_row_cnt).update_wip := 1;--2
l_revised_item_tbl(l_row_cnt).mrp_active := 1;
--l_revised_item_tbl(l_row_cnt).new_item_revision:= '';
l_revised_item_tbl(l_row_cnt).new_routing_revision:= '';
l_revised_item_tbl(l_row_cnt).from_end_item_unit_number:= ''; -- this field is mandatory
l_revised_item_tbl(l_row_cnt).eco_for_production:=2;
l_revised_item_tbl(l_row_cnt).earliest_effective_date := l_eff_date;
l_revised_item_tbl(l_row_cnt).use_up_item_name := l_rev_item_number1; null;
--l_revised_item_tbl(l_row_cnt).use_up_plan_name :=null;
END IF;
IF l_transaction_type = 'UPDATE' THEN
FOR v_component in (SELECT * from eng_revised_items where change_notice = 'IK-API0000') LOOP
l_revised_item_tbl(l_row_cnt).eco_name := l_eco_name;
l_revised_item_tbl(l_row_cnt).organization_code := l_org_code;
l_revised_item_tbl(l_row_cnt).revised_item_name := l_rev_item_number1;
l_revised_item_tbl(l_row_cnt).new_revised_item_revision := '-A0';
l_revised_item_tbl(l_row_cnt).New_Revised_Item_Rev_Desc := '-F0 ik added';
l_revised_item_tbl(l_row_cnt).Updated_Revised_Item_Revision := '-F0';
l_revised_item_tbl(l_row_cnt).Start_Effective_Date := l_eff_date;
l_revised_item_tbl(l_row_cnt).New_Effective_Date := l_eff_date;
l_revised_item_tbl(l_row_cnt).Alternate_Bom_Code := v_component.alternate_bom_designator;
l_revised_item_tbl(l_row_cnt).Status_Type := v_component.status_type;
l_revised_item_tbl(l_row_cnt).Mrp_Active := v_component.Mrp_Active;
l_revised_item_tbl(l_row_cnt).Earliest_Effective_Date := sysdate;
l_revised_item_tbl(l_row_cnt).Requestor := '';
l_revised_item_tbl(l_row_cnt).Use_Up_Plan_Name := v_component.Use_Up_Plan_Name;
l_revised_item_tbl(l_row_cnt).Disposition_Type := v_component.Disposition_Type;
l_revised_item_tbl(l_row_cnt).Update_Wip := v_component.Update_Wip;
l_revised_item_tbl(l_row_cnt).Cancel_Comments := v_component.Cancel_Comments;
l_revised_item_tbl(l_row_cnt).Change_Description := 'TESTING ';
l_revised_item_tbl(l_row_cnt).Attribute_category := v_component.Attribute_category;
l_revised_item_tbl(l_row_cnt).Attribute1 := v_component.Attribute1;
l_revised_item_tbl(l_row_cnt).Attribute2 := v_component.Attribute2;
l_revised_item_tbl(l_row_cnt).Attribute3 := v_component.Attribute3;
l_revised_item_tbl(l_row_cnt).Attribute4 := v_component.Attribute4;
l_revised_item_tbl(l_row_cnt).Attribute5 := v_component.Attribute5;
l_revised_item_tbl(l_row_cnt).Attribute6 := v_component.Attribute6;
l_revised_item_tbl(l_row_cnt).Attribute7 := v_component.Attribute7;
l_revised_item_tbl(l_row_cnt).Attribute8 := v_component.Attribute8;
l_revised_item_tbl(l_row_cnt).Attribute9 := v_component.Attribute9;
l_revised_item_tbl(l_row_cnt).Attribute10 := v_component.Attribute10;
l_revised_item_tbl(l_row_cnt).Attribute11 := v_component.Attribute11;
l_revised_item_tbl(l_row_cnt).Attribute12 := v_component.Attribute12;
l_revised_item_tbl(l_row_cnt).Attribute13 := v_component.Attribute13;
l_revised_item_tbl(l_row_cnt).Attribute14 := v_component.Attribute14;
l_revised_item_tbl(l_row_cnt).Attribute15 := v_component.Attribute15;
l_revised_item_tbl(l_row_cnt).From_End_Item_Unit_Number := v_component.From_End_Item_Unit_Number;
l_revised_item_tbl(l_row_cnt).New_From_End_Item_Unit_Number := '';
l_revised_item_tbl(l_row_cnt).Original_System_Reference :=v_component.Original_System_Reference;
l_revised_item_tbl(l_row_cnt).Return_Status := '';
l_revised_item_tbl(l_row_cnt).Transaction_Type := l_transaction_type;
-- L1, the following is added for ECO enhancement
l_revised_item_tbl(l_row_cnt).From_Work_Order := '';
l_revised_item_tbl(l_row_cnt).To_Work_Order := '';
l_revised_item_tbl(l_row_cnt).From_Cumulative_Quantity := v_component.from_cum_qty;
l_revised_item_tbl(l_row_cnt).Lot_Number := v_component.Lot_Number;
l_revised_item_tbl(l_row_cnt).Completion_Subinventory := v_component.Completion_Subinventory;
l_revised_item_tbl(l_row_cnt).Completion_Location_Name :='';
l_revised_item_tbl(l_row_cnt).Priority := v_component.Priority;
l_revised_item_tbl(l_row_cnt).Ctp_Flag := v_component.Ctp_Flag;
l_revised_item_tbl(l_row_cnt).New_Routing_Revision := v_component.New_Routing_Revision;
l_revised_item_tbl(l_row_cnt).Updated_Routing_Revision := '';
l_revised_item_tbl(l_row_cnt).Routing_Comment := v_component.Routing_Comment;
-- L1, the above is added for ECO enhancement
l_revised_item_tbl(l_row_cnt).Eco_For_Production := v_component.Eco_For_Production;
END LOOP;
END IF;
Eng_Eco_PUB.Process_Eco( p_api_version_number => 1.0
, p_init_msg_list => FALSE
, x_return_status => l_return_status
, x_msg_count => l_msg_count
, p_bo_identifier => 'ECO'
, p_eco_rec => l_eco_rec
, p_eco_revision_tbl => l_eco_revision_tbl
, p_revised_item_tbl => l_revised_item_tbl
, p_rev_component_tbl => l_rev_component_tbl
, p_ref_designator_tbl => l_ref_designator_tbl
, p_sub_component_tbl => l_sub_component_tbl
, p_rev_operation_tbl => l_rev_operation_tbl
, p_rev_op_resource_tbl => l_rev_op_resource_tbl
, p_rev_sub_resource_tbl => l_rev_sub_resource_tbl
, x_eco_rec => x_eco_rec
, x_eco_revision_tbl => x_eco_revision_tbl
, x_revised_item_tbl => x_revised_item_tbl
, x_rev_component_tbl => x_rev_component_tbl
, x_ref_designator_tbl => x_ref_designator_tbl
, x_sub_component_tbl => x_sub_component_tbl
, x_rev_operation_tbl => x_rev_operation_tbl
, x_rev_op_resource_tbl => x_rev_op_resource_tbl
, x_rev_sub_resource_tbl => x_rev_sub_resource_tbl
, p_debug => 'N'
, p_output_dir => l_output_dir
, p_debug_filename => l_debug_filename
dbms_output.put_line('after API call');
DBMS_OUTPUT.PUT_LINE('=======================================================');
DBMS_OUTPUT.PUT_LINE('=======================================================');
DBMS_OUTPUT.PUT_LINE('Return Status: '||l_return_status);
dbms_output.put_line('x_eco_rec.eco_name:'|| x_eco_rec.eco_name );
dbms_output.put_line('x_eco_rec.org_code:'|| x_eco_rec.organization_code);
IF (l_return_status = 'E') THEN
dbms_output.put_line('x_msg_count:' || l_msg_count);
Error_Handler.GET_MESSAGE_LIST(x_message_list => l_error_table);
DBMS_OUTPUT.PUT_LINE('Error Message Count :'||l_error_table.COUNT);
FOR i IN 1..l_error_table.COUNT LOOP
--DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).entity_index||':'||l_error_table(i).table_name);
DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).entity_index||':');
DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||substr(l_error_table(i).message_text,1,250));
END LOOP;
--ROLLBACK;
ELSE
DBMS_OUTPUT.PUT_LINE('==COMMITING==');
--COMMIT;
END IF;
DBMS_OUTPUT.PUT_LINE('=======================================================');
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('Exception Occured :');
DBMS_OUTPUT.PUT_LINE(SQLCODE ||':'||SQLERRM);
DBMS_OUTPUT.PUT_LINE('=======================================================');
RAISE;
END;

Hi All,
We are on Oracle Applications Rel 11.5.8.
We are trying to update an existing ECO with an ‘UPDATE’ transaction_type using eng_Eco_pub API. Here is the code. We first execute this script with CREATE and ECO is created. However, when we run the same script to UPDATE with transaction_type = ‘UPDATE’, the bill_sequence_id in eng_revised_items is updated to g_miss_num (9.99E125). The API is returning ‘SUCCESS’ and updates the bill_sequence_id to 9.999E125. Not sure what we are missing here. Appreciate any inputs or sample code for UPDATING an already created ECO.
REVISED_ITEM_ID BILL_SEQUENCE_ID CHANGE_NOTICE
11668210 192981011 IK-API0316
REVISED_ITEM_ID BILL_SEQUENCE_ID CHANGE_NOTICE
11668210 9.99E125 IK-API0316
Thank You!
DECLARE
l_eco_name VARCHAR2(10) := 'IK-API0000' ;
l_org_code VARCHAR2(3) := 'GLO';
l_transaction_type VARCHAR2(10) := 'CREATE'; -- or UPDATE for updating the same ECO
l_rev_item_number1 VARCHAR2(20):= '16-2214-01';
l_eff_date DATE := NULL;
v_old_effective_date DATE;
l_new_revised_item_revision VARCHAR2(3) := '-A0';
l_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
l_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
l_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type ;-- := Eng_Eco_Pub.g_miss_revised_item_tbl;
l_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
l_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
l_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
l_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
l_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
l_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
-- API output variables
x_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
x_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
x_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type ;-- := Eng_Eco_Pub.g_miss_revised_item_tbl;
x_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
x_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
x_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
x_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
x_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
x_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
-- Other API variables for return status / error handling / debugging
l_error_table Error_Handler.Error_Tbl_Type;
l_return_status VARCHAR2(1) := NULL;
l_msg_count NUMBER := 0;
l_output_dir VARCHAR2(500) := '/apps/orarpt/SJDEV/utl';
l_debug_filename VARCHAR2(60) := 'test.dbg';
-- WHO columns
l_user_id NUMBER := -1;
l_resp_id NUMBER := -1;
l_application_id NUMBER := -1;
l_row_cnt NUMBER := 1;
l_user_name VARCHAR2(30) := 'CA_ADMIN';
l_resp_name VARCHAR2(30) := 'Engineering';
l_comp_eff_date date := null;
l_disable_date date := null;
BEGIN
-- Get the user_id
SELECT user_id,sysdate + 10,sysdate
INTO l_user_id,l_comp_eff_date,l_eff_date
FROM fnd_user
WHERE user_name = l_user_name;
-- Get the application_id and responsibility_id
SELECT application_id, responsibility_id
INTO l_application_id, l_resp_id
FROM fnd_responsibility_tl
WHERE responsibility_name = l_resp_name;
FND_GLOBAL.APPS_INITIALIZE(l_user_id, l_resp_id, l_application_id); -- Mfg / Mfg & Dist Mgr / INV
dbms_output.put_line('Initialized applications context: '|| l_user_id || ' '|| l_resp_id ||' '|| l_application_id );
dbms_output.put_line('before initialixe');
Error_Handler.Initialize;
l_return_status := NULL;
dbms_output.put_line('after initialixe');
-- FOR UPDATE API to update effectivity date on Revised item.
l_eco_rec.eco_name := l_eco_name;
l_eco_rec.organization_code := l_org_code;
l_eco_rec.change_type_code := 'DESIGN';
l_eco_rec.eco_department_name := NULL;
l_eco_rec.priority_code := NULL; --'Medium';
l_eco_rec.approval_list_name := NULL; --'SU_ONLY';
l_eco_rec.reason_code := NULL;
l_eco_rec.Approval_Status_TYPE := 5 ;-- 'Approved'; -- will default to Not submitted for Approval
l_eco_rec.Status_TYPE := 1; -- 1 to bring in SCHEDULE status
l_eco_rec.description := l_eff_date || ' - ECO - '||l_eco_rec.eco_name ;
l_eco_rec.transaction_type := l_transaction_type;
l_eco_rec.return_status := NULL;
IF l_transaction_type ='CREATE' THEN
l_revised_item_tbl(l_row_cnt).transaction_type := l_transaction_type; -- transaction type : CREATE / UPDATE
l_revised_item_tbl(l_row_cnt).eco_name := l_eco_name;
l_revised_item_tbl(l_row_cnt).organization_code := l_org_code;
l_revised_item_tbl(l_row_cnt).revised_item_name := l_rev_item_number1;
l_revised_item_tbl(l_row_cnt).new_revised_item_revision := '-A0'; -- pass only if the previous unimplemented updating ECO has a new revision
l_revised_item_tbl(l_row_cnt).Updated_Revised_Item_Revision := ''; -- l_new_revised_item_revision;
l_revised_item_tbl(l_row_cnt).start_effective_date := l_eff_date;
l_revised_item_tbl(l_row_cnt).new_effective_date := l_eff_date ; -- l_comp_eff_date;
l_revised_item_tbl(l_row_cnt).alternate_bom_code := null;
l_revised_item_tbl(l_row_cnt).status_type := 1; -- 'Open'
l_revised_item_tbl(l_row_cnt).change_description := l_rev_item_number1 || ' --B0 ECO - '||l_eco_rec.eco_name ;
l_revised_item_tbl(l_row_cnt).disposition_type :=1 ;
l_revised_item_tbl(l_row_cnt).update_wip := 1;--2
l_revised_item_tbl(l_row_cnt).mrp_active := 1;
--l_revised_item_tbl(l_row_cnt).new_item_revision:= '';
l_revised_item_tbl(l_row_cnt).new_routing_revision:= '';
l_revised_item_tbl(l_row_cnt).from_end_item_unit_number:= ''; -- this field is mandatory
l_revised_item_tbl(l_row_cnt).eco_for_production:=2;
l_revised_item_tbl(l_row_cnt).earliest_effective_date := l_eff_date;
l_revised_item_tbl(l_row_cnt).use_up_item_name := l_rev_item_number1; null;
--l_revised_item_tbl(l_row_cnt).use_up_plan_name :=null;
END IF;
IF l_transaction_type = 'UPDATE' THEN
FOR v_component in (SELECT * from eng_revised_items where change_notice = 'IK-API0000') LOOP
l_revised_item_tbl(l_row_cnt).eco_name := l_eco_name;
l_revised_item_tbl(l_row_cnt).organization_code := l_org_code;
l_revised_item_tbl(l_row_cnt).revised_item_name := l_rev_item_number1;
l_revised_item_tbl(l_row_cnt).new_revised_item_revision := '-A0';
l_revised_item_tbl(l_row_cnt).New_Revised_Item_Rev_Desc := '-F0 ik added';
l_revised_item_tbl(l_row_cnt).Updated_Revised_Item_Revision := '-F0';
l_revised_item_tbl(l_row_cnt).Start_Effective_Date := l_eff_date;
l_revised_item_tbl(l_row_cnt).New_Effective_Date := l_eff_date;
l_revised_item_tbl(l_row_cnt).Alternate_Bom_Code := v_component.alternate_bom_designator;
l_revised_item_tbl(l_row_cnt).Status_Type := v_component.status_type;
l_revised_item_tbl(l_row_cnt).Mrp_Active := v_component.Mrp_Active;
l_revised_item_tbl(l_row_cnt).Earliest_Effective_Date := sysdate;
l_revised_item_tbl(l_row_cnt).Requestor := '';
l_revised_item_tbl(l_row_cnt).Use_Up_Plan_Name := v_component.Use_Up_Plan_Name;
l_revised_item_tbl(l_row_cnt).Disposition_Type := v_component.Disposition_Type;
l_revised_item_tbl(l_row_cnt).Update_Wip := v_component.Update_Wip;
l_revised_item_tbl(l_row_cnt).Cancel_Comments := v_component.Cancel_Comments;
l_revised_item_tbl(l_row_cnt).Change_Description := 'TESTING ';
l_revised_item_tbl(l_row_cnt).Attribute_category := v_component.Attribute_category;
l_revised_item_tbl(l_row_cnt).Attribute1 := v_component.Attribute1;
l_revised_item_tbl(l_row_cnt).Attribute2 := v_component.Attribute2;
l_revised_item_tbl(l_row_cnt).Attribute3 := v_component.Attribute3;
l_revised_item_tbl(l_row_cnt).Attribute4 := v_component.Attribute4;
l_revised_item_tbl(l_row_cnt).Attribute5 := v_component.Attribute5;
l_revised_item_tbl(l_row_cnt).Attribute6 := v_component.Attribute6;
l_revised_item_tbl(l_row_cnt).Attribute7 := v_component.Attribute7;
l_revised_item_tbl(l_row_cnt).Attribute8 := v_component.Attribute8;
l_revised_item_tbl(l_row_cnt).Attribute9 := v_component.Attribute9;
l_revised_item_tbl(l_row_cnt).Attribute10 := v_component.Attribute10;
l_revised_item_tbl(l_row_cnt).Attribute11 := v_component.Attribute11;
l_revised_item_tbl(l_row_cnt).Attribute12 := v_component.Attribute12;
l_revised_item_tbl(l_row_cnt).Attribute13 := v_component.Attribute13;
l_revised_item_tbl(l_row_cnt).Attribute14 := v_component.Attribute14;
l_revised_item_tbl(l_row_cnt).Attribute15 := v_component.Attribute15;
l_revised_item_tbl(l_row_cnt).From_End_Item_Unit_Number := v_component.From_End_Item_Unit_Number;
l_revised_item_tbl(l_row_cnt).New_From_End_Item_Unit_Number := '';
l_revised_item_tbl(l_row_cnt).Original_System_Reference :=v_component.Original_System_Reference;
l_revised_item_tbl(l_row_cnt).Return_Status := '';
l_revised_item_tbl(l_row_cnt).Transaction_Type := l_transaction_type;
-- L1, the following is added for ECO enhancement
l_revised_item_tbl(l_row_cnt).From_Work_Order := '';
l_revised_item_tbl(l_row_cnt).To_Work_Order := '';
l_revised_item_tbl(l_row_cnt).From_Cumulative_Quantity := v_component.from_cum_qty;
l_revised_item_tbl(l_row_cnt).Lot_Number := v_component.Lot_Number;
l_revised_item_tbl(l_row_cnt).Completion_Subinventory := v_component.Completion_Subinventory;
l_revised_item_tbl(l_row_cnt).Completion_Location_Name :='';
l_revised_item_tbl(l_row_cnt).Priority := v_component.Priority;
l_revised_item_tbl(l_row_cnt).Ctp_Flag := v_component.Ctp_Flag;
l_revised_item_tbl(l_row_cnt).New_Routing_Revision := v_component.New_Routing_Revision;
l_revised_item_tbl(l_row_cnt).Updated_Routing_Revision := '';
l_revised_item_tbl(l_row_cnt).Routing_Comment := v_component.Routing_Comment;
-- L1, the above is added for ECO enhancement
l_revised_item_tbl(l_row_cnt).Eco_For_Production := v_component.Eco_For_Production;
END LOOP;
END IF;
Eng_Eco_PUB.Process_Eco( p_api_version_number => 1.0
, p_init_msg_list => FALSE
, x_return_status => l_return_status
, x_msg_count => l_msg_count
, p_bo_identifier => 'ECO'
, p_eco_rec => l_eco_rec
, p_eco_revision_tbl => l_eco_revision_tbl
, p_revised_item_tbl => l_revised_item_tbl
, p_rev_component_tbl => l_rev_component_tbl
, p_ref_designator_tbl => l_ref_designator_tbl
, p_sub_component_tbl => l_sub_component_tbl
, p_rev_operation_tbl => l_rev_operation_tbl
, p_rev_op_resource_tbl => l_rev_op_resource_tbl
, p_rev_sub_resource_tbl => l_rev_sub_resource_tbl
, x_eco_rec => x_eco_rec
, x_eco_revision_tbl => x_eco_revision_tbl
, x_revised_item_tbl => x_revised_item_tbl
, x_rev_component_tbl => x_rev_component_tbl
, x_ref_designator_tbl => x_ref_designator_tbl
, x_sub_component_tbl => x_sub_component_tbl
, x_rev_operation_tbl => x_rev_operation_tbl
, x_rev_op_resource_tbl => x_rev_op_resource_tbl
, x_rev_sub_resource_tbl => x_rev_sub_resource_tbl
, p_debug => 'N'
, p_output_dir => l_output_dir
, p_debug_filename => l_debug_filename
dbms_output.put_line('after API call');
DBMS_OUTPUT.PUT_LINE('=======================================================');
DBMS_OUTPUT.PUT_LINE('=======================================================');
DBMS_OUTPUT.PUT_LINE('Return Status: '||l_return_status);
dbms_output.put_line('x_eco_rec.eco_name:'|| x_eco_rec.eco_name );
dbms_output.put_line('x_eco_rec.org_code:'|| x_eco_rec.organization_code);
IF (l_return_status = 'E') THEN
dbms_output.put_line('x_msg_count:' || l_msg_count);
Error_Handler.GET_MESSAGE_LIST(x_message_list => l_error_table);
DBMS_OUTPUT.PUT_LINE('Error Message Count :'||l_error_table.COUNT);
FOR i IN 1..l_error_table.COUNT LOOP
--DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).entity_index||':'||l_error_table(i).table_name);
DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).entity_index||':');
DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||substr(l_error_table(i).message_text,1,250));
END LOOP;
--ROLLBACK;
ELSE
DBMS_OUTPUT.PUT_LINE('==COMMITING==');
--COMMIT;
END IF;
DBMS_OUTPUT.PUT_LINE('=======================================================');
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('Exception Occured :');
DBMS_OUTPUT.PUT_LINE(SQLCODE ||':'||SQLERRM);
DBMS_OUTPUT.PUT_LINE('=======================================================');
RAISE;
END;

PO - Item Data - Delivery Schedule Tab - Delivered qty, issued qty, GR qty

Hi Frens,
In a Purchase Order, under Item data < delivery schedule tab, we have delivered quantity, issued quantity and GR quantity fields.
Is there any TABLE to find out these quantities against PO.
Thanks and Regards,
CK Vikas

>
CK Vikas wrote:
> Hi Raj, You mean EKBE?
Yes EKBE is the right table for your requirement.

Update Recv.Point of an Item in Delivery

Similar Messages

Maybe you are looking for