Unable to cancel sales order line using API

Hi,
After running the below API script I am getting the error message as
Error Message: FND FND_AS_UNEXPECTED_ERROR N PKG_NAME OE_Order_PVT N
PROCEDURE_NAME Process_Order N ERROR_TEXT ORA-01403: no data found
Help me out to fix the issue.
Please find the code below :
create or replace procedure xxso_line_cancel
is
l_user_id NUMBER;
l_resp_id NUMBER;
l_appl_id NUMBER;
l_header_rec_in oe_order_pub.header_rec_type;
l_line_tbl_in oe_order_pub.line_tbl_type;
l_action_request_tbl_in oe_order_pub.request_tbl_type;
l_header_rec_out oe_order_pub.header_rec_type;
l_line_tbl_out oe_order_pub.line_tbl_type;
l_header_val_rec_out oe_order_pub.header_val_rec_type;
l_header_adj_tbl_out oe_order_pub.header_adj_tbl_type;
l_header_adj_val_tbl_out oe_order_pub.header_adj_val_tbl_type;
l_header_price_att_tbl_out oe_order_pub.header_price_att_tbl_type;
l_header_adj_att_tbl_out oe_order_pub.header_adj_att_tbl_type;
l_header_adj_assoc_tbl_out oe_order_pub.header_adj_assoc_tbl_type;
l_header_scredit_tbl_out oe_order_pub.header_scredit_tbl_type;
l_header_scredit_val_tbl_out oe_order_pub.header_scredit_val_tbl_type;
l_line_val_tbl_out oe_order_pub.line_val_tbl_type;
l_line_adj_tbl_out oe_order_pub.line_adj_tbl_type;
l_line_adj_val_tbl_out oe_order_pub.line_adj_val_tbl_type;
l_line_price_att_tbl_out oe_order_pub.line_price_att_tbl_type;
l_line_adj_att_tbl_out oe_order_pub.line_adj_att_tbl_type;
l_line_adj_assoc_tbl_out oe_order_pub.line_adj_assoc_tbl_type;
l_line_scredit_tbl_out oe_order_pub.line_scredit_tbl_type;
l_line_scredit_val_tbl_out oe_order_pub.line_scredit_val_tbl_type;
l_lot_serial_tbl_out oe_order_pub.lot_serial_tbl_type;
l_lot_serial_val_tbl_out oe_order_pub.lot_serial_val_tbl_type;
l_action_request_tbl_out oe_order_pub.request_tbl_type;
l_chr_program_unit_name VARCHAR2 (100);
l_ret_status VARCHAR2 (1000) := NULL;
l_msg_count NUMBER := 0;
l_msg_data VARCHAR2 (2000);
l_api_version NUMBER := 1.0;
CURSOR c_so_details
IS
SELECT ol.line_number, ol.shipment_number, ol.header_id, ol.line_id, ol.flow_status_code
FROM
oe_order_headers_all oh,
oe_order_lines_all ol
WHERE
ol.header_id = oh.header_id
AND ol.flow_status_code IN ('AWAITING_SHIPPING','ENTERED')
AND oh.flow_status_code IN ('BOOKED', 'ENTERED')
and oh.header_id = 34756
and line_number=1;
begin
fnd_global.apps_initialize ( user_id => 1257 ,resp_id => 21623 , resp_appl_id => 660);
mo_global.set_policy_context('S',122);
mo_global.init('ONT');
FOR i IN c_so_details
LOOP
l_line_tbl_in (1) := oe_order_pub.g_miss_line_rec;
l_line_tbl_in (1).line_id := i.line_id;
l_line_tbl_in (1).ordered_quantity := 0;
l_line_tbl_in (1).cancelled_quantity := 4;
l_line_tbl_in (1).cancelled_flag := 'Y';
l_line_tbl_in (1).change_reason := '1'; --Administrative Reason
l_line_tbl_in (1).change_comments := 'Cancel Order Line with reference to ticket#000000';
l_line_tbl_in (1).operation := oe_globals.g_opr_update;
oe_msg_pub.delete_msg;
oe_order_pub.process_order
(p_api_version_number => l_api_version,
p_init_msg_list => fnd_api.g_true,
p_return_values => fnd_api.g_true,
p_action_commit => fnd_api.g_true,
p_line_tbl => l_line_tbl_in,
x_header_rec => l_header_rec_out,
x_header_val_rec => l_header_val_rec_out,
x_header_adj_tbl => l_header_adj_tbl_out,
x_header_adj_val_tbl => l_header_adj_val_tbl_out,
x_header_price_att_tbl => l_header_price_att_tbl_out,
x_header_adj_att_tbl => l_header_adj_att_tbl_out,
x_header_adj_assoc_tbl => l_header_adj_assoc_tbl_out,
x_header_scredit_tbl => l_header_scredit_tbl_out,
x_header_scredit_val_tbl => l_header_scredit_val_tbl_out,
x_line_tbl => l_line_tbl_out,
x_line_val_tbl => l_line_val_tbl_out,
x_line_adj_tbl => l_line_adj_tbl_out,
x_line_adj_val_tbl => l_line_adj_val_tbl_out,
x_line_price_att_tbl => l_line_price_att_tbl_out,
x_line_adj_att_tbl => l_line_adj_att_tbl_out,
x_line_adj_assoc_tbl => l_line_adj_assoc_tbl_out,
x_line_scredit_tbl => l_line_scredit_tbl_out,
x_line_scredit_val_tbl => l_line_scredit_val_tbl_out,
x_lot_serial_tbl => l_lot_serial_tbl_out,
x_lot_serial_val_tbl => l_lot_serial_val_tbl_out,
x_action_request_tbl => l_action_request_tbl_out,
x_return_status => l_ret_status,
x_msg_count => l_msg_count,
x_msg_data => l_msg_data
commit;
l_msg_data := NULL;
IF l_ret_status <> 'S'
THEN
FOR iindx IN 1 .. l_msg_count
LOOP
l_msg_data := l_msg_data || ' ' || oe_msg_pub.get (iindx);
END LOOP;
DBMS_OUTPUT.put_line ('Return Status: ' || l_ret_status);
DBMS_OUTPUT.put_line ('Error Message: ' || l_msg_data);
ELSE
DBMS_OUTPUT.put_line ('Return Status: ' || l_ret_status);
DBMS_OUTPUT.put_line ('Error Message: ' || l_msg_data);
END IF;
END LOOP;
END;

Hi,
After running the below API script I am getting the error message as
Error Message: FND FND_AS_UNEXPECTED_ERROR N PKG_NAME OE_Order_PVT N
PROCEDURE_NAME Process_Order N ERROR_TEXT ORA-01403: no data found
Help me out to fix the issue.
Please find the code below :
create or replace procedure xxso_line_cancel
is
l_user_id NUMBER;
l_resp_id NUMBER;
l_appl_id NUMBER;
l_header_rec_in oe_order_pub.header_rec_type;
l_line_tbl_in oe_order_pub.line_tbl_type;
l_action_request_tbl_in oe_order_pub.request_tbl_type;
l_header_rec_out oe_order_pub.header_rec_type;
l_line_tbl_out oe_order_pub.line_tbl_type;
l_header_val_rec_out oe_order_pub.header_val_rec_type;
l_header_adj_tbl_out oe_order_pub.header_adj_tbl_type;
l_header_adj_val_tbl_out oe_order_pub.header_adj_val_tbl_type;
l_header_price_att_tbl_out oe_order_pub.header_price_att_tbl_type;
l_header_adj_att_tbl_out oe_order_pub.header_adj_att_tbl_type;
l_header_adj_assoc_tbl_out oe_order_pub.header_adj_assoc_tbl_type;
l_header_scredit_tbl_out oe_order_pub.header_scredit_tbl_type;
l_header_scredit_val_tbl_out oe_order_pub.header_scredit_val_tbl_type;
l_line_val_tbl_out oe_order_pub.line_val_tbl_type;
l_line_adj_tbl_out oe_order_pub.line_adj_tbl_type;
l_line_adj_val_tbl_out oe_order_pub.line_adj_val_tbl_type;
l_line_price_att_tbl_out oe_order_pub.line_price_att_tbl_type;
l_line_adj_att_tbl_out oe_order_pub.line_adj_att_tbl_type;
l_line_adj_assoc_tbl_out oe_order_pub.line_adj_assoc_tbl_type;
l_line_scredit_tbl_out oe_order_pub.line_scredit_tbl_type;
l_line_scredit_val_tbl_out oe_order_pub.line_scredit_val_tbl_type;
l_lot_serial_tbl_out oe_order_pub.lot_serial_tbl_type;
l_lot_serial_val_tbl_out oe_order_pub.lot_serial_val_tbl_type;
l_action_request_tbl_out oe_order_pub.request_tbl_type;
l_chr_program_unit_name VARCHAR2 (100);
l_ret_status VARCHAR2 (1000) := NULL;
l_msg_count NUMBER := 0;
l_msg_data VARCHAR2 (2000);
l_api_version NUMBER := 1.0;
CURSOR c_so_details
IS
SELECT ol.line_number, ol.shipment_number, ol.header_id, ol.line_id, ol.flow_status_code
FROM
oe_order_headers_all oh,
oe_order_lines_all ol
WHERE
ol.header_id = oh.header_id
AND ol.flow_status_code IN ('AWAITING_SHIPPING','ENTERED')
AND oh.flow_status_code IN ('BOOKED', 'ENTERED')
and oh.header_id = 34756
and line_number=1;
begin
fnd_global.apps_initialize ( user_id => 1257 ,resp_id => 21623 , resp_appl_id => 660);
mo_global.set_policy_context('S',122);
mo_global.init('ONT');
FOR i IN c_so_details
LOOP
l_line_tbl_in (1) := oe_order_pub.g_miss_line_rec;
l_line_tbl_in (1).line_id := i.line_id;
l_line_tbl_in (1).ordered_quantity := 0;
l_line_tbl_in (1).cancelled_quantity := 4;
l_line_tbl_in (1).cancelled_flag := 'Y';
l_line_tbl_in (1).change_reason := '1'; --Administrative Reason
l_line_tbl_in (1).change_comments := 'Cancel Order Line with reference to ticket#000000';
l_line_tbl_in (1).operation := oe_globals.g_opr_update;
oe_msg_pub.delete_msg;
oe_order_pub.process_order
(p_api_version_number => l_api_version,
p_init_msg_list => fnd_api.g_true,
p_return_values => fnd_api.g_true,
p_action_commit => fnd_api.g_true,
p_line_tbl => l_line_tbl_in,
x_header_rec => l_header_rec_out,
x_header_val_rec => l_header_val_rec_out,
x_header_adj_tbl => l_header_adj_tbl_out,
x_header_adj_val_tbl => l_header_adj_val_tbl_out,
x_header_price_att_tbl => l_header_price_att_tbl_out,
x_header_adj_att_tbl => l_header_adj_att_tbl_out,
x_header_adj_assoc_tbl => l_header_adj_assoc_tbl_out,
x_header_scredit_tbl => l_header_scredit_tbl_out,
x_header_scredit_val_tbl => l_header_scredit_val_tbl_out,
x_line_tbl => l_line_tbl_out,
x_line_val_tbl => l_line_val_tbl_out,
x_line_adj_tbl => l_line_adj_tbl_out,
x_line_adj_val_tbl => l_line_adj_val_tbl_out,
x_line_price_att_tbl => l_line_price_att_tbl_out,
x_line_adj_att_tbl => l_line_adj_att_tbl_out,
x_line_adj_assoc_tbl => l_line_adj_assoc_tbl_out,
x_line_scredit_tbl => l_line_scredit_tbl_out,
x_line_scredit_val_tbl => l_line_scredit_val_tbl_out,
x_lot_serial_tbl => l_lot_serial_tbl_out,
x_lot_serial_val_tbl => l_lot_serial_val_tbl_out,
x_action_request_tbl => l_action_request_tbl_out,
x_return_status => l_ret_status,
x_msg_count => l_msg_count,
x_msg_data => l_msg_data
commit;
l_msg_data := NULL;
IF l_ret_status <> 'S'
THEN
FOR iindx IN 1 .. l_msg_count
LOOP
l_msg_data := l_msg_data || ' ' || oe_msg_pub.get (iindx);
END LOOP;
DBMS_OUTPUT.put_line ('Return Status: ' || l_ret_status);
DBMS_OUTPUT.put_line ('Error Message: ' || l_msg_data);
ELSE
DBMS_OUTPUT.put_line ('Return Status: ' || l_ret_status);
DBMS_OUTPUT.put_line ('Error Message: ' || l_msg_data);
END IF;
END LOOP;
END;

Similar Messages

  • Can anyone tell me how to insert the new sales order lines using API.

    Hi,
    I am trying to Insert new sales order lines using oe_order_pub.Process_Order API, but i am unable to insert.
    Help me on this.
    Thanks in Adavance
    Shravan Kumar.

    Hi,
    Have you checked this link?
    http://download-west.oracle.com/docs/cd/B25516_08/current/acrobat/115omapi.zip
    it has extensive information on OM APIs
    Regards
    Prashant Pathak

  • Error in cancelling sales order line using process order API

    Hi,
    I have created a sales order which is in booked status. I want to cancel the order line . when I am running the concurrent request I am getting the following error message.I am using the process order API to perform this operation.
    API Error Message You are not allowed to update Inventory Item because:
    line has been booked
    API Error Message You are not allowed to update Line Type because:
    Line is Booked
    Can anyone help.
    thanks
    Ashwini

    Hi,
    What is the application release?
    What concurrent program you are running? Is it a custom or seeded one? And, what is the API name?
    Please see if these docs are applicable.
    Unable To Manual Mass Update Items For Multiple Booked Sales Order Lines [ID 887905.1]
    Cannot Update Ordered Item To Related Item On Booked Sales Order Line [ID 298796.1]
    Thanks,
    Hussein

  • Unable to insert the new sales order line using API.

    Hi,
    when i am tring to insert the deleted line with ENTERED Status, i am getting the follwing error msg.
    Yesterday morning i insert the lines, but from yesterday evening onwords i am unable to insert line and i am getting below error msg.
    Item with inventory_item_id=394131 is not defined in Item validation Org
    i written the code like this
    l_step                     varchar2(250);
    l_err_msg               varchar2(1000);
    l_line_tbl                oe_order_pub.Line_Tbl_Type;
    lx_return_status           VARCHAR2(2000);
    lx_msg_count                NUMBER;
    lx_msg_data                VARCHAR2(2000);
    lx_header_rec                oe_order_pub.Header_Rec_Type;
    lx_header_val_rec           oe_order_pub.Header_Val_Rec_Type;
    lx_header_adj_tbl           oe_order_pub.Header_Adj_Tbl_Type;
    lx_header_adj_val_tbl           oe_order_pub.Header_Adj_Val_Tbl_Type;
    lx_header_price_att_tbl      oe_order_pub.Header_Price_Att_Tbl_Type;
    lx_header_adj_att_tbl           oe_order_pub.Header_Adj_Att_Tbl_Type;
    lx_header_adj_assoc_tbl      oe_order_pub.Header_Adj_Assoc_Tbl_Type;
    lx_header_scredit_tbl           oe_order_pub.Header_Scredit_Tbl_Type;
    lx_header_scredit_val_tbl      oe_order_pub.Header_Scredit_Val_Tbl_Type;
    lx_Header_Payment_tbl           oe_order_pub.Header_Payment_Tbl_Type;
    lx_Header_Payment_val_tbl      oe_order_pub.Header_Payment_Val_Tbl_Type;
    lx_line_tbl                oe_order_pub.Line_Tbl_Type;
    lx_line_val_tbl           oe_order_pub.Line_Val_Tbl_Type;
    lx_Line_Adj_tbl           oe_order_pub.Line_Adj_Tbl_Type;
    lx_Line_Adj_val_tbl           oe_order_pub.Line_Adj_Val_Tbl_Type;
    lx_Line_price_Att_tbl           oe_order_pub.Line_Price_Att_Tbl_Type;
    lx_Line_Adj_Att_tbl           oe_order_pub.Line_Adj_Att_Tbl_Type;
    lx_Line_Adj_Assoc_tbl           oe_order_pub.Line_Adj_Assoc_Tbl_Type;
    lx_Line_Scredit_tbl           oe_order_pub.Line_Scredit_Tbl_Type;
    lx_Line_Scredit_val_tbl      oe_order_pub.Line_Scredit_Val_Tbl_Type;
    lx_Line_Payment_tbl           oe_order_pub.Line_Payment_Tbl_Type;
    lx_Line_Payment_val_tbl      oe_order_pub.Line_Payment_Val_Tbl_Type;
    lx_Lot_Serial_tbl           oe_order_pub.Lot_Serial_Tbl_Type;
    lx_Lot_Serial_val_tbl           oe_order_pub.Lot_Serial_Val_Tbl_Type;
    lx_action_request_tbl           oe_order_pub.Request_Tbl_Type;
    v_hold_release_rec OE_HOLDS_PVT.order_tbl_type;
    v_hold_source_rec OE_HOLDS_PVT.Hold_Source_Rec_Type;
    v_err_msg               VARCHAR2(2000);
    v_return_flag VARCHAR2(1);
    v_err_flag               VARCHAR2(1);
    BEGIN     
    FOR c_ins_rec in (SELECT *          
              FROM terom_sales_order_lines_stg          
    LOOP
         IF c_ins_rec.flow_status_code = 'ENTERED' THEN
         -- ASSIGNMENT OF LINE RECORD FOR ENTERED STATUS
         l_line_tbl(1)           := OE_ORDER_PUB.G_MISS_LINE_REC;
         l_line_tbl(1).header_id      := c_ins_rec.header_id;
         l_line_tbl(1).inventory_item_id := c_ins_rec.inventory_item_id;     
         l_line_tbl(1).ordered_quantity := c_ins_rec.ordered_quantity;
         l_line_tbl(1).operation      := OE_GLOBALS.G_OPR_CREATE;      
    ELSE
         -- ASSIGNMENT OF LINE RECORD
         l_line_tbl(1)           := OE_ORDER_PUB.G_MISS_LINE_REC;
         l_line_tbl(1).header_id      := c_ins_rec.header_id;
         l_line_tbl(1).inventory_item_id := c_ins_rec.inventory_item_id;
         l_line_tbl(1).ordered_quantity := c_ins_rec.cancelled_quantity;     
         l_line_tbl(1).operation      := OE_GLOBALS.G_OPR_CREATE;
         END IF;
         -- API CALL
         APPS.OE_ORDER_PUB.PROCESS_ORDER(
                             p_api_version_number      => 1.0,
                             p_init_msg_list           => apps.fnd_api.g_true,
                             p_return_values           => apps.fnd_api.g_false,
                             x_return_status           => lx_return_status,
                             x_msg_count                => lx_msg_count,
                             x_msg_data                => lx_msg_data,
                             p_line_tbl                => l_line_tbl,
                             x_header_rec           => lx_header_rec,
                             x_header_val_rec           => lx_header_val_rec,
                             x_header_adj_tbl           => lx_header_adj_tbl,
                             x_header_adj_val_tbl      => lx_header_adj_val_tbl,
                             x_header_price_att_tbl      => lx_header_price_att_tbl,
                             x_header_adj_att_tbl      => lx_header_adj_att_tbl,
                             x_header_adj_assoc_tbl      => lx_header_adj_assoc_tbl,
                             x_header_scredit_tbl      => lx_header_scredit_tbl,
                             x_header_scredit_val_tbl     => lx_header_scredit_val_tbl,
                             x_line_tbl                => lx_line_tbl,
                             x_line_val_tbl           => lx_line_val_tbl,
                             x_line_adj_tbl           => lx_line_adj_tbl,
                             x_line_adj_val_tbl           => lx_line_adj_val_tbl,
                             x_line_price_att_tbl      => lx_line_price_att_tbl,
                             x_line_adj_att_tbl           => lx_line_adj_att_tbl,
                             x_line_adj_assoc_tbl      => lx_line_adj_assoc_tbl,
                             x_line_scredit_tbl           => lx_line_scredit_tbl,
                             x_line_scredit_val_tbl      => lx_line_scredit_val_tbl,
                             x_lot_serial_tbl           => lx_lot_serial_tbl,
                             x_lot_serial_val_tbl      => lx_lot_serial_val_tbl,
                             x_action_request_tbl      => lx_action_request_tbl
    COMMIT;
    can any one help me why this error mesg is coming, it's very URGENT.
    Thank,
    Shravan Kumar Kota.

    Hi,
    Have you checked this link?
    http://download-west.oracle.com/docs/cd/B25516_08/current/acrobat/115omapi.zip
    it has extensive information on OM APIs
    Regards
    Prashant Pathak

  • Cancel Sales Order lines that are picked

    Hi
    1. I'm trying to cancel sales order lines through process order api that are picked and delivery status is Staged/Pick Confirmed. The error is
    You are not allowed to cancel Order Line because:
    Line has been pick confirmed/staged.
    I'm unable to perform by below means
    1.There is a processing constraint on the field SCHEDULE_ARRIVAL_DATE.
    Delete the processing constraint and retry the cancel line process - Processing constraint form the fields are protected against update
    2.Navigate to the shipping transaction form and query the order. Select the line and enter 0 at shipped quantity.Save the record.Ship confirm the line, this will cause the line to be backordered.Query the order line in the order entry form and cancel this. - Shipping transactions form the fields are protected against update
    2. Is there a way to cancel Internal Sales Order(ISO) lines of one OU and the corresponding internal requisition is another OU
    Thanks
    kumar

    If you are in R12, there are some enhancements from Oracle that allows updating/cancelling certain Internal requistion fields and Internal orders automatically. You may need to disable few processing constraints too.
    As of Now Oracle support change to following attribute at OM side
    1 Order Quantity
    2 Request Date
    3 Schedule date
    4 Arrival date
    Similarly if we make changes in following fields in Approved IR
    1 Quantity
    2 Need by Date
    These changes will got reflected in ISO
    Plus cancel the IR line or ISO line, the other one gets cancelled automaically.
    To cancel the picked line, first undo the pick confirmation process by back ordering. or unassign the delivery details from the delivery (if created already) and cancel the delivery.In either case, you need to manually trasnfer the qty from staging area to original locations. Oracle doesn't automatically move the qty back, (undo move order transaction).
    Ganesan.

  • 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;
    /

  • Need to pass in line charges when cancel order line using API?

    Hi,
    Do we need to pass in line charges (charges, freight cost) when cancel order line using Oe_Order_Pub.Process_Order API?

    I found the answer to my own question:
    Yes it is a supported feature. It is documented on the following page:
    http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/desktop/NativeApp lication.html#event:invoke
    When you subscribe to the invoke event of the NativeApplication it will subsequently dispatch the event and you read the e.arguments Array object to get the startup arguments passed into the native application.

  • Sales Order line Reservation API

    Hi All,
    how to do reserve the sales order line by using plsql program. Can you provide the API name which i can use for sales order line reservation.
    thanks
    reddy

    Hi,
    Please mention the application release and the OS. Also, post the code of the API you are using.
    Please See if these documents are applicable.
    Note: 887776.1 - NO LOT VALIDATION AFTER PATCH 4649626
    Note: 396645.1 - "APP-GMI-83119 Invalid lot no" While Transferring from Newly Created Lot with Null Inventory
    Note: 428393.1 - Cannot Move Lot with No Onhand Inventory
    Regards,
    Hussein

  • Need to report on sales order lines using specific pricing modifier

    Is there a report I can run for a specific modifier number that will give me all the sales order lines that were adjusted using that pricing modifier?

    Use oe_price_adjustments table and link that to the qp_list_headers and lines to get the details of the modifiers.
    Thanks
    Nagamohan

  • Unable to copy the Price Modifiers associated with a Sales Order Line

    Dear All,
    I am copying Sales Order Line using the process_order API. I was not able to copy the Price Modifiers associated with the Lines. How can I accomplish this..?
    Is there any API available for copying the Price Modifier info associated with the Sales Order Line..?
    Environment is 11i and OS is SUN Solaris
    Please update...
    Many thanks in advance..

    Hello All,
    Please let me know is this possible to have the list of Invoices for an associated Sales Order.
    Thanks,
    Abdul

  • How to prevent Copy from Cancelled Sales Orders.

    Hi,
    I have a requirement as below.
    I want to stop users from Copying a Cancelled Sales Order Lines.
    Can anybody please let me know how I can achieve this.
    I tried using the processing constraints but couldn't succeed.
    Thanks in advance.
    Thanks
    Shekhar

    Hi,
    Also you can refer the following security rule feature which oracle provides to set your rule from users performing actions like copying, deleting and cancelling.
    http://download.oracle.com/docs/cd/A60725_05/html/comnls/us/oe/esecruls.htm#r_secrul
    Thanks
    Nancy

  • Sales order line with status calcelled picked by auto invoice program

    I cancelled  one line in Sales Order and Shipped remaining lines
    after Ship Confirm process ,I ran workflow background process.
    I am getting cancelled line information to AR interface tables
    when I run Auto invoice amount is sitting in Unearned account
    The status of cancelled line -  Cancelled
    Flow status code is cancelled
    INVOICE_INTERFACE_STATUS_CODE I AM SEEING is YES for that line.
    Why the cancelled Sales order line is picked by auto invoice program?
    Thanks,
    John

    Hi Ivruksh,
    Thanks for the reply, the reference you gave was not actually related to the issue I had, let me put it this way,
    Our Auto Invoice Job is scheduled at midnight, it runs and process only few CM's, rest of them are left behind with out any error message in error tables. Al I can see in the ra_interface_lines_all table is interface_line_id is populated, which shows that the Auto Invoice program has picked all the records but it is processing only few, the rest are left out with out any error message.
    Interestingly, when I tried to run those stuck CM's Individual one by one its gets successfully processed.
    Is anyone faced with similar kind of issue, kindly let me know of any solutions you guys had.
    Thanks in advance.
    Regards
    Srinivas

  • How to use of API for Cancel Sales Orders

    Hi....
    I want to use API for Cancel Sales Orders. Plz give me advice how we can cancel orders. I know that there is procedure provide in ORACLE APPs (i.e. OE_ORDER_PUB.process_order). But in this procedure i know the how to create and update sales order, but how to Cancel order with the use of this API.
    Plz send me soultion as soon as possible. ITS VERY VERY URGENT BASE.
    Thanks in Advance.

    Hi all,
    We are importing Sales Orders on 11.5.9 using OE_Order_PUB.Process_Order API .We have supplied most of the mandatory fields and the same data works from the front end. When we use the API it throws a Ora 20001.
    A snapshot of the error message.
    SQL> exec pk_process_object.process_order('1o');
    Message Count is :2
    Message is RA-20001: User in Package OE_Header_Util Procedure Get_Order_Number
    Message is :User-Defined Exception in Package OE_Header_Util Procedure
    Pre_Write_Process
    Return Status is ErrorU
    PL/SQL procedure successfully completed.
    --------------------------------------------------------------------------------------------

  • Sales order line items delivery cancelled but still appears in MD04.

    Hi PP Gurus,
    In the sales there are 6 line items are there out of which for 1 line item delivery and PGI happened. And for remaining line items delivery got cancelled, but these line items for which delivery cancelled appearing in the MD04, I have rejected the sales order line items but these line items still shows in MD04. Please advise how to remove these line items from MD04.
    Thanks and Regards,
    SHARAN.

    Hi
    Pl refer SAP Note : 1166713 for the Problem which says " You have posted goods issue and therefore the delivery requirements should no longer be existing. These inconsistencies can be seen using report SDRQCR21"
    Regards
    Brahmaji

  • SALES ORDER LINE IS CANCELLED BUT DELIVERY DETAIL IS SHOING AS BACKORDERED

    SALES ORDER LINE IS CANCELLED BUT still the DELIVERY DETAIL IS showing as BACKORDERED it should be in cancelled
    status.The Sales order (only one ex:3904854) is cancelled , however order in shipping transactions screen indicates order is on backorder.
    at that time of order cancellation the line level workflow error out due to the Workflow package is inactive .
    I tried to resubmit the error out workflow using retry option from the responsibility “Workflow Administrator” the workflow is completed with forcible option but still the delivery detail is in back order status not changing it to cancel status.
    Error Name :-4068 [Error Process Error: WF Error Message: ORA-04068: existing state of packages has been discarded  
              ORA-04061: existing state of package body "APPS.XRX_SUPPLIES_NEW_WF_PKG" has been invalidated    
              ORA-04065: not executed, altered or dropped package body "APPS.XRX_SUPPLIES_NEW_WF_PKG"                         
              ORA-06508: PL/SQL: could not find program unit being called: "APPS.XRX_SUPPLIES_NEW_WF_PKG" [Error Process           Error: 3114: Activity 'WFERROR/R_ERROR_RETRY' is not a process.]
    Error Stack: Wf_Engine_Util.Function_Call(XRX_SUPPLIES_NEW_WF_PKG.XRX_CLOSE_LINE_DETAILS, OEOL, 55098479, 195982, RUN)
    [Error Process Error:   Wf_Engine.CreateProcess(WFERROR, WF5147218, R_ERROR_RETRY) ]

    Mohan
    You need a simple script to get the status corrected. Log an SR or search metalink for the script. I am sure there is one out there (if you search with the orphan reservations). This script supported, but not exactly targeted at your problem But it will solve it. You can log an SR and confirm.
    Thanks
    Nagamohan

Maybe you are looking for