Move Order API

Hi All,
Please advice how to modify move order by updating or deleting either by Interface or by API
i have created Move order by API inv_move_order_pub but unable to modify or delete please advice.
Thanks

Hi;
All APIs are listed in Oracle Integration Repository
http://irep.oracle.com/index.html
API User Notes - HTML Format [ID 236937.1]
R12.0.[3-4] : Oracle Install Base Api / Open Interface Setup Test [ID 427566.1]
Oracle Trading Community Architecture API User Notes, June 2003 [ID 241320.1]
Technical Uses of Customer Interface and TCA-API [ID 269121.1]
"12: How To Access API References via the Oracle Integration Repository" [ ID 462586.1]
"Oracle Integration Repository Documentation Resources Release 12" [ ID 396116.1]
Pelase also check below:
Api's in EBS
http://forums.oracle.com/forums/thread.jspa?forumID=39&threadID=984534&messageID=3890192#3890192
http://sairamgoudmalla.blogspot.com/2009/05/script-to-find-oracle-apis-for-any.html
API
http://forums.oracle.com/forums/thread.jspa?threadID=1038379&tstart=0
List of API
http://forums.oracle.com/forums/message.jspa?messageID=4198097#4198097
Oracle Common Application Components API Reference Guide
download.oracle.com/docs/cd/B25284_01/current/acrobat/jta115api.pdf
List of APIs and open interface R12
http://forums.oracle.com/forums/thread.jspa?messageID=2340033
Regard
Helios

Similar Messages

Transact move order API for serial contril item in 10.5.10.2

Hello Friends ,
I need a Help from you , I am badly got struck up. I need to the transact move order part of O2C Cycle Using APIs.
I Could complete the flow upto transact move orders, there i got struck up. Here i need to pass the serial numbers as some of the Items are serialized items.
Can you plz suggest me.
Its in Very Urgent.
i am using version 11.5.10.2
Regards
Ganesh

Hello Ganesh,
Hope you have passes this issue.
I am in the same boat, I need to find out the APIs to update the serial numbers on order at the time of allocation/transact move order step.
Could you please help me with the process/steps/sample code involved in this.
Thanks in advance!
Raj

Mover Order API Serial Number

Hi All,
We have managed to create a sales order and pick release, the status of the line is "Released To Warehouse" with the next stage "Transact Move Order". Some of the items on the sales order are serial number controlled (serial numbers are generated upon receipt from purchase order), hence why the move order has not completed as it requires the serial numbers to be enetered to complete. I can manually do this via the move orders form and can see when I do this that the serial numbers are updated into mrl_serial_numbers_temp, query below for reference.
select wdv.source_header_number, wdv.delivery_id, mtrh.request_number, msnt.fm_serial_number, msnt.to_serial_number
from wsh_deliverables_v wdv, mtl_txn_request_lines mtrl, mtl_txn_request_headers mtrh,
mtl_material_transactions_temp mmtt, mtl_serial_numbers_temp msnt
where wdv.source_line_id = mtrl.txn_source_line_id
and mtrl.header_id = mtrh.header_id
and mtrl.txn_source_line_id = mmtt.trx_source_line_id
and mmtt.transaction_temp_id = msnt.transaction_temp_id
and wdv.source_header_number = '7010000538'
My question is can the move order update or serial numbers be doen via an API, if so which one?
Thanks in advance

Dear Colin,
Can you please tell me whats the value to pass for p_trx_tmp_id in API inv_trx_util_pub.insert_ser_trx ?
I guess, its not the same transaction_temp_id from MTL_MATERIAL_TRANSACTIONS_TEMP
Please let me know how to pass the value for that?
If you can provide a sample code, that would be gr8.
Thanks in advance.
Regards,
Jana

Error Message is not displayed by the API Move Order

Hi All,
Iam using the API "inv_move_order_pub.process_move_order" to create the move orders.
For few records the API is returning the return_status as "E" however the msg_count is returned as "0"
and there is no msg_data returned by the API for the records which are error out.
Kindly help me regarding this.
Regards
Tanisha
Edited by: Tanisha on Feb 2, 2011 2:34 AM

Can you please mention the type of move orders you are trying to create?
For the error records did you verify the validity of item, sub-inventories, locator_id etc?

How to cancel a Move Order line using API

Hi
I have a requirement, where I have to cancel Move order lines.
At times, multiple Move order lines are getting created for the same Sales order line.
Even after the Sales Order line is shipped and closed, the move order line is still open and it also has a corresponding pending transaction in mtl_material_transactions_temp table.
I came across INV_MOVE_ORDER_PUB.process move order line API.
how do I use it to cancel the move order line. Any sample codes would be highly welcome.
Thanks

Finally, found an alternate solution.
used the following code.
===================================
SET serveroutput on size 1000000
DECLARE
l_return_status VARCHAR2(100);
l_msg_count NUMBER;
l_msg_data VARCHAR2(2000);
l_msg_index NUMBER;
l_user_id NUMBER;
l_resp_id NUMBER;
l_appl_id NUMBER;
l_org_id NUMBER := &org_id;
l_move_order_line_id NUMBER := &mo_line_id ;
BEGIN
SELECT user_id
INTO l_user_id
FROM fnd_user
WHERE user_name = 'PRAWILNSON';
SELECT responsibility_id
,application_id
INTO l_resp_id
,l_appl_id
FROM fnd_responsibility_vl
WHERE responsibility_name = 'Order Management Super User';
FND_GLOBAL.apps_initialize (l_user_id, l_resp_id, l_appl_id);
MO_GLOBAL.set_policy_context ('S', l_org_id);
MO_GLOBAL.init;
DBMS_OUTPUT.put_line ('Calling INV_MO_BACKORDER_PVT to Backorder MO');
DBMS_OUTPUT.put_line ('===============================');
inv_mo_backorder_pvt.backorder (p_line_id => l_move_order_line_id
,x_return_status => l_return_status
,x_msg_count => l_msg_count
,x_msg_data => l_msg_data);
DBMS_OUTPUT.put_line ('Return Status is : '|| l_return_status);
-- Check Return Status
IF l_return_status = fnd_api.g_ret_sts_success THEN
DBMS_OUTPUT.put_line ('Successfully BackOrdered the Move Order Line');
COMMIT;
ELSE
DBMS_OUTPUT.put_line ('Could not able to Back Order Line Due to Following Reasons' );
ROLLBACK;
FOR j IN 1 .. l_msg_count LOOP
FND_MSG_PUB.get(p_msg_index => j
,p_encoded => fnd_api.g_false
,p_data => l_msg_data
,p_msg_index_out => l_msg_index);
DBMS_OUTPUT.put_line ('Error Message is : '|| l_msg_data);
END LOOP;
END IF;
END;
/

API to update a allocation and transact move orders.

Hi All,
This is for R12 in INV org (NON WMS enabled). Is there a way to update the move order allocation for a pick wave to update the picked quantity and set the missing quantity action to Cycle Count?
Thanks
Amit

We have exact the same requirement here with serial controlled items.
But you can refer to note 269144.1 firstly.

Issue in Transact Move order while updating serial number

Hi All,
We need to perform sales order issue of items present in particular subinventory.
I am successful in creating sales order having one item .
I did the pick release of the order using the api ,wsh_picking_batches_pub.create_batch and wsh_picking_batches_pkg.submit_release_request to release the batch.
A move order got created , now I need to allocate the serial number for processing the move order,I used the below script to update the line record with incoming start and end serial number.
But the api is throwing error .
DECLARE
-- Common Declarations
   l_api_version      NUMBER                                 := 1.0;
   l_init_msg_list    VARCHAR2 (2)                          := fnd_api.g_true    ;
   l_return_values    VARCHAR2 (2)                         := fnd_api.g_false;
   l_commit           VARCHAR2 (2)                         := fnd_api.g_false;
   x_return_status    VARCHAR2 (2);
   x_msg_count        NUMBER                                 := 0;
   x_msg_data         VARCHAR2 (255);
   -- 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)                          := 'OPERATIONS';
   l_resp_name        VARCHAR2 (30)          := 'MFG_AND_DIST_SUPER_USER_APS';
   -- API specific declarations
   l_header_id        NUMBER                                 := 0;
   l_trohdr_rec       inv_move_order_pub.trohdr_rec_type;
   l_trohdr_val_rec   inv_move_order_pub.trohdr_val_rec_type;
   l_trolin_tbl       inv_move_order_pub.trolin_tbl_type;
   l_trolin_val_tbl   inv_move_order_pub.trolin_val_tbl_type;
   x_trolin_tbl       inv_move_order_pub.trolin_tbl_type;
   x_trolin_val_tbl   inv_move_order_pub.trolin_val_tbl_type;
   x_trohdr_rec       inv_move_order_pub.trohdr_rec_type;
   x_trohdr_val_rec   inv_move_order_pub.trohdr_val_rec_type;
-- Cursor to load Move Order Headers
-- CURSOR c_mo_hdrs IS
-- SELECT * FROM my_custom_move_order_hdrs ;
BEGIN
   fnd_global.apps_initialize (5939, 50625, 20003);
   mo_global.init ('INV');
   -- call API to create move order header
   DBMS_OUTPUT.put_line
                   ('=======================================================');
   DBMS_OUTPUT.put_line ('Calling INV_MOVE_ORDER_PUB.Get_Move_Order API');
   inv_move_order_pub.get_move_order (p_api_version_number      => l_api_version,
                                      p_init_msg_list           => l_init_msg_list,
                                      p_return_values           => l_return_values,
                                      x_return_status           => x_return_status,
                                      x_msg_count               => x_msg_count,
                                      x_msg_data                => x_msg_data,
                                      p_header_id               => 7360068,
                                      p_header                  => NULL,
                                      x_trohdr_rec              => l_trohdr_rec,
                                      x_trohdr_val_rec          => l_trohdr_val_rec,
                                      x_trolin_tbl              => l_trolin_tbl,
                                      x_trolin_val_tbl          => l_trolin_val_tbl
   DBMS_OUTPUT.ENABLE ();
   DBMS_OUTPUT.put_line
                    ('=======================================================');
   DBMS_OUTPUT.put_line ('Return Status: ' || x_return_status);
   IF (x_return_status <> fnd_api.g_ret_sts_success)
   THEN
      DBMS_OUTPUT.put_line ('Error Message :' || x_msg_data);
   END IF;
   -- Print the Move Order Header/Lines to be processed
   IF (x_return_status = fnd_api.g_ret_sts_success)
   THEN
      DBMS_OUTPUT.put_line (   'Header :'
                            || l_trohdr_rec.header_id
                            || ' '
                            || l_trohdr_rec.request_number
                            || ' '
                            || l_trohdr_rec.date_required
                            || ' '
                            || l_trohdr_rec.from_subinventory_code
                            || ' '
                            || l_trohdr_rec.header_status
                            || ' '
                            || l_trohdr_rec.organization_id
                            || ' '
                            || l_trohdr_rec.status_date
                            || ' '
                            || l_trohdr_rec.to_subinventory_code
                            || ' '
                            || l_trohdr_rec.transaction_type_id
                            || ' '
                            || l_trohdr_rec.move_order_type
                            || ' '
                            || l_trohdr_rec.operation
      l_trohdr_rec.from_subinventory_code := 'CustRet';
      --l_trohdr_rec.to_subinventory_code := 'Staging';
      l_trohdr_rec.operation := inv_globals.g_opr_update;
      DBMS_OUTPUT.put_line (   'Header Update :'
                            || l_trohdr_rec.header_id
                            || ' '
                            || l_trohdr_rec.from_subinventory_code
                            || ' '
                            || l_trohdr_rec.to_subinventory_code
                            || ' '
                            || l_trohdr_rec.operation
      FOR i IN 1 .. l_trolin_tbl.COUNT
      LOOP
         DBMS_OUTPUT.put_line (   'Line '
                               || i
                               || ': '
                               || l_trolin_tbl (i).line_id
                               || ' '
                               || l_trolin_tbl (i).line_number
                               || ' '
                               || l_trolin_tbl (i).line_status
                               || ' '
                               || l_trolin_tbl (i).organization_id
                               || ' '
                               || l_trolin_tbl (i).inventory_item_id
                               || ' '
                               || l_trolin_tbl (i).from_subinventory_code
                               || ' '
                               || l_trolin_tbl (i).to_subinventory_code
                               || ' '
                               || l_trolin_tbl (i).quantity
                               || ' '
                               || l_trolin_tbl (i).status_date
                               || ' '
                               || l_trolin_tbl (i).uom_code
                               || ' '
                               || l_trolin_tbl (i).operation
         l_trolin_tbl (i).from_subinventory_code := 'CustRet';
         --l_trolin_tbl (i).to_subinventory_code := 'Staging';
         --l_trolin_tbl (i).inventory_item_id := 19128;
         l_trolin_tbl (i).serial_number_start := '356030032497361';
         l_trolin_tbl (i).serial_number_end := '356030032497361';
         --l_trolin_tbl(i).quantity       := l_trolin_tbl(i).quantity
         l_trolin_tbl (i).operation := inv_globals.g_opr_update;
         DBMS_OUTPUT.put_line (   'Line Updated'
                               || i
                               || ': '
                               || l_trolin_tbl (i).line_id
                               || ' '
                               || l_trolin_tbl (i).from_subinventory_code
                               || ' '
                               || l_trolin_tbl (i).to_subinventory_code
                               || ' '
                               || l_trolin_tbl (i).serial_number_start
                               || ' '
                               || l_trolin_tbl (i).serial_number_end
                               || ' '
                               || l_trolin_tbl (i).operation
      END LOOP;
   END IF;
   DBMS_OUTPUT.put_line
                    ('=======================================================');
   -- call API to create move order header
   DBMS_OUTPUT.put_line
                    ('=======================================================');
   DBMS_OUTPUT.put_line ('Calling INV_MOVE_ORDER_PUB.Process_Move_Order API');
   inv_move_order_pub.process_move_order
                                       (p_api_version_number      => l_api_version,
                                        p_init_msg_list           => l_init_msg_list,
                                        p_return_values           => l_return_values,
                                        p_commit                  => l_commit,
                                        x_return_status           => x_return_status,
                                        x_msg_count               => x_msg_count,
                                        x_msg_data                => x_msg_data,
                                        p_trohdr_rec              => l_trohdr_rec,
                                        p_trohdr_val_rec          => l_trohdr_val_rec,
                                        p_trolin_tbl              => l_trolin_tbl,
                                        p_trolin_val_tbl          => l_trolin_val_tbl,
                                        x_trohdr_rec              => x_trohdr_rec,
                                        x_trohdr_val_rec          => x_trohdr_val_rec,
                                        x_trolin_tbl              => x_trolin_tbl,
                                        x_trolin_val_tbl          => x_trolin_val_tbl
   DBMS_OUTPUT.put_line
                    ('=======================================================');
   DBMS_OUTPUT.put_line ('Return Status: ' || x_return_status);
   IF (x_return_status <> fnd_api.g_ret_sts_success)
   THEN
      DBMS_OUTPUT.put_line ('Error Message :' || x_msg_data);
      ROLLBACK;
     ELSE
     COMMIT;
   END IF;
   DBMS_OUTPUT.put_line
                    ('=======================================================');
-- END LOOP;
EXCEPTION
   WHEN OTHERS
   THEN
      DBMS_OUTPUT.put_line ('Exception Occured :');
      DBMS_OUTPUT.put_line (SQLCODE || ':' || SQLERRM);
      DBMS_OUTPUT.put_line
                   ('=======================================================');
END;
Error Log
=======================================================
Calling INV_MOVE_ORDER_PUB.Get_Move_Order API
=======================================================
Return Status: S
Header :7360068 7360067 15-JUL-13 7 281 15-JUL-13   3
Header Update :7360068 CustRet UPDATE
Line 1: 6730069 1 7 281 19119 Staging 1 15-JUL-13 UN
Line Updated1: 6730069 CustRet Staging 356030032497361 356030032497361 UPDATE
=======================================================
=======================================================
Calling INV_MOVE_ORDER_PUB.Process_Move_Order API
Inv Item Id19119
Old Inv Item Id19119
Inv Item Id-356030032497361
Item Id
Org Id281
Serial Number356030032497361
=======================================================
Return Status: E
Error Message :INV_INV_INVALID_ATTRIBUTE_N_ATTRIBUTE_Start serial number
Please help to solve the issue.
Thanks,
Shruti K. Nayak

Hello Ganesh,
Hope you have passes this issue.
I am in the same boat, I need to find out the APIs to update the serial numbers on order at the time of allocation/transact move order step.
Could you please help me with the process/steps/sample code involved in this.
Thanks in advance!
Raj

Move order number when doing the pick release

hi everyone ,
is there any way to specify the move order number when doing the pick release process
i wante to passe the move order number to the pick release API procedure
or is it possible to change it after doing the pick release
best regards

Uses MTL_TXN_REQUEST_HEADERS_S sequence to generate the move order number in, I believe, when-validate-item tirgger.
Thanks
Nagamohan

Sales Pick Move Order Allocation Update via Program

Hi,
I am trying to update the allocation qty of a Move Order, that is in Allocated status, programmatically. Move Order of type Sales Order Pick.
Can you pls let me know, is there any private API available to perform this activity or steps to achieve this functionality?
Thanks,
Gowri

can i know what xactly u need. will u make it little bit clear pls

Prevent fractional Move Order Allocation

We use "Move Order Issue" type Move orders in our system.
We allocate Lot or serial Items, which are transacted as whole numbers. But the Move order creation/allocation API allows me to request and allocate fractional quantities for lot items. This should ideally fail allocation. SO for LOT Number XXXXX which has 10 quantites, I could potentially request .3, and get an allocation for .3 quantity. I want to prevent this from happening. Is there a setup which prevents fractional allocation.
Thanks
PHK

PHK,
Are you using API or form? If it is form you can easily achieve this using form personalization.
API, you can stop calling allocation logic if available qty is less than the requested quantity.
Thanks
Nagamohan

How to restrict Sales Order LOV in Transact Move Orders

Hello
We would like to restrict LOV in the Transact Move Orders screen to only those orders that were created in that specific Operating Unit. Also, we would like to control the LOV for Release Rules to a specific OU.
I believe the LOVs for both these screens pull from MTL_SALES_ORDERS. Therefore, I guess we would need to create a Value Set of type Table, value will be SEGMENT1 (Sales Orders) but unsure about the where condition.
Any help would be appreciated.
Sanjib

Sanjib
Release Rules: Why don't you use the SRS version if pick releasing rather than the screen. Ofcourse you lose some flexibility to enter order number and customer information. If screen is a must you can take the LOV from the existing form and create a new record group in the new form instance trigger. Add this peice to the lov sql to control the pick release rules result:
(select 1 from org_organization_definitions cust_org
where org.organization_id=cust_org.organization_id
and operating_unit=FND_PROFILE.VALUE('ORG_ID'))
This org is mtl_parmeters table used in LOV.
2. Transact Move Orders: Instead of changing the LOV and playing with the Sales Order Flexfield, you can use the inventory organization security to control who can do a transaction. This will not change the LOV but definitely will control the access to the records after you have queried. As you know this is inventory or warehouse function not the OE function.
You can try one idea though:
Segment2 is order_type which is OU specific. You can create value set that picks the LOV from the order types table for a specific OU, assign that to the segment2 and create a security rule. This rule will have include and exclude rules. You include all the Order types that are in a specific OU and assign that rule to the resp of that OU where move order is transacted. This will limit the LOV of the order types to only those that are availble for that resp. I have not tried this but give it a shot.
Thanks
Nagamohan

Error while running Process Order API to import orders - URGENT HELP NEEDED

Hi all,
I'm stuck with order import using OE_ORDER_PUB.PROCESS_ORDER api. Wanted to import a simple order in Vision database using the process order api. Figured out the right data to use, inserted into Headers and Lines Iface All tables. When calling the OE_ORDER_PUB.PROCESS_ORDER api, it is throwing this error:
"Header ID does not exist on this record or does not match ID specified on header record. You require a valid header ID if the operation is Create."
But when I validate the same record using the CORRECTIONS form in Order Import GUI, the order is successfully validated. Also the order is imported when I click the IMPORT button.
I understand that HEADER_ID column is not required for creating a new order, but not sure why it is erroring. Here is the data I'm using:
Insert into oe_headers_iface_all
(org_id, order_type_id, order_source_id, orig_sys_document_ref, ordered_date, request_date,
sold_from_org_id, sold_to_org_id, ship_from_org_id, ship_to_org_id, invoice_to_org_id,
CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE,LAST_UPDATE_LOGIN,OPERATION_CODE)
values (204, 1430, 1046, '101040', sysdate, sysdate, 204, 1004, 606, 1018, 1017, 0, sysdate, 0, sysdate, 0, 'CREATE');
Insert into oe_lines_iface_all
("ORDER_SOURCE_ID","ORIG_SYS_DOCUMENT_REF","ORIG_SYS_LINE_REF","ORIG_SYS_SHIPMENT_REF","ORG_ID","INVENTORY_ITEM","LINE_TYPE_ID",request_date,"SCHEDULE_DATE","DELIVERY_LEAD_TIME","ORDERED_QUANTITY","ORDER_QUANTITY_UOM",sold_from_org_id, sold_to_org_id, ship_from_org_id, ship_to_org_id, invoice_to_org_id,"UNIT_SELLING_PRICE","CREATED_BY","CREATION_DATE","LAST_UPDATED_BY","LAST_UPDATE_DATE","LAST_UPDATE_LOGIN","OPERATION_CODE")
values
(1046,'101040', '1', '1', 204, 'AS72111', 1427, sysdate, sysdate+1, 0, 10, 'Ea' ,204, 1004, 606, 1018, 1017,100,0,sysdate,0,sysdate,0,'CREATE');
Any help is appreciated.
FYI - this is a 11.5.10.2 version installed on Windows 2003 server.
Thanks in advance.
Jags

I might be late in replying, but hope it might help.
From your query it seems you are inserting records into interface tables and then calling process order API( probably from some PL/SQL block).
This is where I am confused, because I hope you understand, that interface tables are for use with Order Import concurrent Program, and for Process ORder API, you need to provide the data as parameter. The api has, header record type and line table type as parameters. So you need to assign correct data to these variables and pass them as parameter when you are calling Process Order API.
If you are doing the same thing, then post the exact pl/SQL code and error message from the API. That might help diagnose the issue.
Regards,
Nitin Darji

Move Order lines and Delivery Detail lines - Relationship

Hi All,
Is there a one - to - one realtionship between Move Order Line and Delivery Detail Line?
i.e., Each Move Order line will correspond to only one Delivery Details line Record?
Thanks in advance.
Regards,
Gowri

Hello,
There is a one - to - many relationship between Move Order Line and Delivery Detail Line when you split lines in delivery.
select * from mtl_material_transactions t you have source_id.
select * from WSH_DELIVERABLES_v t you have move_order_id.
Regards,
Luko

How to add new line in transact move order line

Hi,
i am able to update locaotr in Transact move order.
But i want to add two locators for the same line.
I tried to insert one more record in data base, but getting error unique index error.
so how can we add new line in transact move order line .
please help to slove this isse.
Thanks In Advance
Venu.

Hi,
the fact that your question is posted in Order Management section, does the move order automatically generated by OM?
nevertheless, i don't think you should (or allowed, in this case) to add a new line in transact move order. Transact move order only queries (not create records) the move order lines eligible to allocate and transact.
So, I don't see why you need to add a new line in transact move order.
You can, however, add a new line in the allocation of the lines, where for instance, you need to have half of the line allocated to one locator, and the other half to another locator
Thanks

Error while updating the sales order through Process Order API

Hi,
Please any one will help plz.
I am updating the promise_date through oe_order_pub.process_order(Process Order API) i am getting the following error.
FND_AS_UNEXPECTED_ERROR N PKG_NAME OE_Order_Cache N PROCEDURE_NAME get_tax_calculation_flag N ERROR_TEXT ORA-01403:no data found
Please any one will help plz
Below is my code.
Declare
l_archive_file_name VARCHAR2(1000);
l_shipment_exists NUMBER:=0;
l_header_id NUMBER;
l_line_id NUMBER;
p_header_rec Oe_Order_Pub.Header_Rec_Type;
l_line_tbl oe_order_pub.line_tbl_type := oe_order_pub.g_miss_line_tbl;
l_header_rec OE_ORDER_PUB.Header_Rec_Type;
l_header_val_out_rec OE_ORDER_PUB.Header_Val_Rec_Type;
l_header_adj_out_tbl OE_Order_PUB.Header_Adj_Tbl_Type;
l_header_adj_val_out_tbl OE_Order_PUB.Header_Adj_Val_Tbl_Type;
l_header_price_att_out_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
l_header_adj_att_out_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
l_header_adj_assoc_out_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
l_header_scredit_out_tbl OE_Order_PUB.Header_Scredit_Tbl_Type;
l_header_scredit_val_out_tbl OE_Order_PUB.Header_Scredit_Val_Tbl_Type;
l_line_rec OE_ORDER_PUB.line_rec_type;
l_line_out_tbl OE_ORDER_PUB.Line_Tbl_Type;
l_line_val_out_tbl OE_ORDER_PUB.Line_Val_Tbl_Type;
l_line_adj_out_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type;
l_line_adj_val_out_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
l_line_price_att_out_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
l_line_adj_att_out_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
l_line_adj_assoc_out_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
l_line_scredit_out_tbl OE_Order_PUB.Line_Scredit_Tbl_Type;
l_line_scredit_val_out_tbl OE_Order_PUB.Line_Scredit_Val_Tbl_Type;
l_lot_serial_out_tbl OE_Order_PUB.Lot_Serial_Tbl_Type;
l_lot_serial_val_out_tbl OE_Order_PUB.Lot_Serial_Val_Tbl_Type;
l_action_request_out_tbl OE_Order_PUB.Request_Tbl_Type;
l_msg_count NUMBER;
l_msg_data VARCHAR2(2000);
l_return_status VARCHAR2(1);
l_index NUMBER;
l_rows_processed NUMBER:=0;
l_line_mawb VARCHAR2(240);
l_line_hawb VARCHAR2(240);
l_line_flight_num VARCHAR2(240);
l_org_id NUMBER :=143;--FND_GLOBAL.ORG_ID;
l_resp_id NUMBER:=FND_GLOBAL.RESP_ID;
l_resp_appl_id NUMBER:=FND_GLOBAL.RESP_APPL_ID;
l_user_id number := FND_GLOBAL.USER_ID;
l_promise_date date;
BEGIN
SELECT ol.org_id, oh.header_id, ol.line_id,ol.promise_date
INTO l_org_id, l_header_id, l_line_id,l_promise_date
FROM apps.oe_order_headers_all oh, apps.oe_order_lines_all ol
WHERE ol.header_id=oh.header_id
AND ol.line_id =1319526; --&line_id
-- apps.fnd_global.apps_initialize(&l_USER_ID,&l_resp_id,&l_resp_appl_id);
apps.fnd_global.apps_initialize(67778,51017,660);
p_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
p_header_rec.header_id :=835035;-- l_header_id;
p_header_rec.operation := OE_GLOBALS.G_OPR_UPDATE;
l_line_tbl := oe_order_pub.g_miss_line_tbl;
-------------------------Line Record -------------------------------
l_line_tbl(1) := oe_order_pub.g_miss_line_rec;
l_line_tbl(1).header_id := 835035;
l_line_tbl(1).line_id := 1319526;
l_line_tbl(1).promise_date := sysdate;
l_line_tbl(1).operation := oe_globals.g_opr_update;
BEGIN
apps.oe_order_pub.process_order
(p_api_version_number => 1.0
,p_init_msg_list => fnd_api.g_true
,p_return_values => fnd_api.g_true
,x_return_status => l_return_status
,x_msg_count => l_msg_count
,x_msg_data => l_msg_data
,p_header_rec => p_header_rec
,p_line_tbl => l_line_tbl
-- out variables
,x_header_rec => l_header_rec
,x_header_val_rec => l_header_val_out_rec
,x_header_adj_tbl => l_header_adj_out_tbl
,x_header_adj_val_tbl => l_header_adj_val_out_tbl
,x_header_price_att_tbl => l_header_price_att_out_tbl
,x_header_adj_att_tbl => l_header_adj_att_out_tbl
,x_header_adj_assoc_tbl => l_header_adj_assoc_out_tbl
,x_header_scredit_tbl => l_header_scredit_out_tbl
,x_header_scredit_val_tbl => l_header_scredit_val_out_tbl
,x_line_tbl => l_line_out_tbl
,x_line_val_tbl => l_line_val_out_tbl
,x_line_adj_tbl => l_line_adj_out_tbl
,x_line_adj_val_tbl => l_line_adj_val_out_tbl
,x_line_price_att_tbl => l_line_price_att_out_tbl
,x_line_adj_att_tbl => l_line_adj_att_out_tbl
,x_line_adj_assoc_tbl => l_line_adj_assoc_out_tbl
,x_line_scredit_tbl => l_line_scredit_out_tbl
,x_line_scredit_val_tbl => l_line_scredit_val_out_tbl
,x_lot_serial_tbl => l_lot_serial_out_tbl
,x_lot_serial_val_tbl => l_lot_serial_val_out_tbl
,x_action_request_tbl => l_action_request_out_tbl
--dbms_output.put_line('l_msg_data-->' ||l_msg_data ||' l_return_status --> ' ||l_return_status);
END;
commit;
END;
Regards,
Sangu

Hi Sangu,
See if the following notes help you:
Error when calling API from SQL*Developer, eg. ORA-01403 in API OE_ORDER_PUB.PROCESS_ORDER (Doc ID 1054295.1)
Cancellation Of Transfer Orders Is Not Possible - ORA-01403: no data found in Package OE_Order_PVT Procedure Process_Order (Doc ID 391307.1)
Thanks &
Best Regards,

Move Order API

Similar Messages

Maybe you are looking for