While Booking RMA Line status Closed

Hi,
I created a RMA(Return) order in iStore but the RMA line status goes to Closed, Header status in Booked. How to change the line status to Awaiting Return or Booked in R12.
Thanks
Vivek

Hi again,
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]
Pelase also check below:
Api's in EBS
Re: Api's in EBS
http://sairamgoudmalla.blogspot.com/2009/05/script-to-find-oracle-apis-for-any.html
API
Fixed Asset API
List of API
Re: List of APIs
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
Re: List of APIs and open interface R12
Regard
Helios

Similar Messages

  • Need to Cancel RMA has the line Status Awaiting invoice interface

    Hi All,
    I have high priority issue.
    I need to cancel a RMA with Credit Only which has header status Booked and it has two lines which has Awaiting Invoice Interface Status.
    Now my user wants to cancel this RMA.
    Could anyone can help me how to cancel this RMA or else we have any API to cancel this RMA.
    Thanks in advance
    Best Regards,
    CSK

    Hi,
    Following metalink id can be helpful
    Internal Order Line Status: Awaiting Invoice Interface - Incomplete Data [ID 1456386.1]
    Batch_Source_Name is required for Invoice Interface Error Prevents Invoicing [ID 343430.1]
    Edited by: 923198 on Sep 7, 2012 9:41 AM

  • Sales Order RMA Line Closed

    Hi All,
    I have a sales order RMA created once a line is received WF changeing its status in Closed.
    I need to still have the possibility to update DFF for closed line, does anybody knows how to setup process constraints to allow DFF updated when an OM lines is closed ?
    Thanks

    Thanks for the suggestion.
    Unfortunately these DFF are defined at the line level and the values there is different for each line so it's not possible to setup the same at the header level.
    There is some way to link DFF lines value to the SO Header WF status ?
    Thanks

  • Internal Sales Order imported with Line status "Booked".

    Hi Guys,
    Expecting a status of "Awaiting Shipment" in the line status but getting the status of "Booked".
    checked the following metalink notes but did not help
    Scheduling Internal Sales Orders Results in Error - One of the Group Elements or Mandatory Components Failed [ID 368187.1]
    Internal Sales Order Gets Created In "Booked" Status [ID 1357172.1]
    Any Thoughts???

    Guys,
    Issue is resolved.
    Earlier in 11i in ASCP, instance Org defintion is setup for only the required Inv org.
    But in R12 we need to define for all the available Inv organisations.
    Later after running the complete collections and running the ASCP plan resolved the issue.
    Thanks
    Radha.

  • Order Line status is Awaiting Shipping but the header status is Closed.

    All,
    I have few order lines which are in Awaiting Shipping Status but the order header is closed.
    When I checked the Shipping Transactions, the lines are backordered.
    I did release and ship confirmed the lines and now the line status is closed.
    My understanding is that the header flow should not get closed until all the lines in are completed and closed.
    But in this scenario, its not the case. Is it a bug (or) its the standard functionality (or) is there any way we can control this?
    Please advise.
    Thanks
    -Karthik Raj

    You are correct - this is not supposed to happen. But every now and then Oracle workflow hiccups and causes these kinds of issues.
    You can raise an SR and ask Oracle to give you a data fix script.
    Or you can write your own script to reopen the header.
    Sandeep Gandhi

  • WSH DELIVERY LINE STATUS에 대한 해석

    제품 : MFG_SE
    작성날짜 : 2003-11-20
    WSH DELIVERY LINE STATUS에 대한 해석
    ====================================
    PURPOSE
    Delivery line status는 현재 진행중인 shipping process가 어떤 상태인지를
    보여준다.이 status를 잘 인식하고 있으면 shipping process에 문제가 발생할
    경우 여러 도움을 줄 수 있다.
    Explanation
    Delivery line의 released status는 진행중인 shipping process의 progress
    를 나타낸다.이 released status는
    Oracle Shipping Execution Shipping Transactions window나,
    Oracle Order Management Order window/Actions button, Additional
    information, Delivery tab에서 조회할 수 있다.
    Delivery line status를 조회하기
    1. Navigate to the Query Manager window, delivery lines를 찾으면 이
    delivery lines이 Shipping Transactions 화면에 조회된다.
    2. Line을 선택하고 Detail button을 click하면 Pick Status field에
    조회된 delivery line의 현재 status를 보여준다.
    3. Main tab으로 이동하기 위해 Done button을 click 한다.
    4. Main tab에서 Pick status column이 보이도록 right scroll을 사용한다.
    Delivery line statuses의 차이점
    ===============================
    -.Not Applicable (Code: X)
    : delivery line이 invoice 생성은 가능하나 non-shippable.
    ex) service line, warranty line
    -.Not Ready for Release (Code: N)
    : delivery line이 pick release를 할 수 있는 상태가 아님.
    이런 상태는 보통 order line이 Import Delivery Line Concurrent process
    를 이용하여 manual하게 Shipping Execution에 import된 경우이다.
    이는 Awaiting Shipping workflow acrivity에 도달하지 못함을 의미한다.
    -.Ready for Release (Code: R)
    : pick release가 가능한 delivery line.
    Order line이 Awaiting Shipping workflow activity에 닿아 있는 상태.
    (Booked, Scheduled)
    -.Submitted to Warehouse (Code: S)
    : Pick release가 delivery line을 진행시켰으며, move order header, line
    을 생성, available qty를 찾아 inventory allications을 생성.
    Pick confirm은 아직 하지 않은 상태이나, 만약 pick release시 auto-pick
    confirm을 사용했다면 status를 release에서 Staged로 바꾼다.
    Auto-pick confirm을 사용하지 않았고 delivery line을 계속 진핼시키려면
    Inventory Move Order Transaction 화면에서 pick confirm을 manual하게
    실행한다.
    -.Staged (Code: Y)
    : delivery line은 pick confirm 되었고,inventory는 storage subinv에서
    staging subinv으로 transfer 되어진 상태.
    ship confirm 실행 전까지는 staged 상태로 남아 있다.
    -.Backordered (Code: B)
    : Pick release가 delivery line을 진행시켰으나 entire 수량을 찾지
    못했을때 -Inventory에 충분한 material이 없거나 inventory balance가
    안 맞을때- backordered 상태가 된다.
    -.Shipped (Code: C)
    : delivery line의 delivery가 ship confirm 되고, OM/INV interface
    processes가 완료되었으며 trip 또한 closed 된 상태이다.
    -.Cancelled (Code: D)
    : delivery line에 연결되어 있는 order line이 cancelled 된 상태이다.
    Example
    Reference Documents
    Note 205708.1

  • Unable to ship confirm, showing stops cannot be set to status closed

    hi all,
    while i am performing shipconfirm,
    it showing "Error:some deliveries selected for ship confirm have errors or warnings"
    and details showing "stops cannot be set to status closed"
    appreciate u r best suggestions.
    thanks
    govardhan

    Dear ,
    Maybe you need to check all delivery line status ..
    All line status should be "Staged.." .
    If there is any status not staged, System will show the error.
    Hope it's useful to you.

  • Header and Line Statuses in OM

    hi
    Can any one give a brief on the below statuses in OM header and Line Level.
    The below is the list
    Order Header Statuses
    Following is a list of all possible statuses assigned to an order header.
    • Active
    • Awaiting Invoice Interface - Incomplete Data
    • Awaiting Invoice Interface - On Hold
    • Awaiting Start Date
    • Booked
    • Cancelled
    • Closed
    • Customer Accepted
    • Draft
    • Draft - Customer Rejected
    • Draft - Internal Rejected
    • Draft Submitted
    • Entered
    • Expired
    • Internal Approved
    • Internal Rejected
    • Invoice Interface - Complete
    • Lost
    • Offer Expired
    • Pending Customer Acceptance
    • Pending Internal Approval
    • Submitted
    • Terminated
    • User Working
    Order Line Statuses
    Following is a list of all possible statuses assigned to an order line.
    • Awaiting Export Screening
    • Awaiting Fulfillment
    • Awaiting Invoice Interface - Incomplete Data
    • Awaiting Invoice Interface - On Hold
    • Awaiting Invoice Interface - Partially Interfaced, RFR Item
    • Awaiting Invoice Interface - Pending Complete Delivery
    • Awaiting Invoice Interface - RFR Item
    • Awaiting Invoice Interface - Unexpected error
    • Awaiting Payment Assurance - On Hold
    • Awaiting Payment Assurance - Receipts Not Assured
    • Awaiting Receipt
    • Awaiting Reprice - Invalid setup
    • Awaiting Reprice - On reprice line hold
    • Awaiting Reprice - Pricing error
    • Awaiting Reprice - Unexpected error
    • Awaiting Return
    • Awaiting Return Disposition
    • Awaiting Shipping
    • Awaiting Supply
    • BOM and Routing Created
    • Booked
    • Cancelled
    • Closed
    • Completed Export Screening
    • Config Item Created
    • Customer Accepted
    • Data Error Export Screening
    • Draft
    • Draft - Customer Rejected
    • Draft - Internal Rejected
    • Draft Submitted
    • Entered
    • Fulfilled
    • Interfaced to Receivables
    • Internal Approved
    • Internal Rejected
    • Inventory Interfaced
    • Invoice Interface - Not Applicable
    • Lost
    • Offer Expired
    • PO-Created
    • PO-Partial
    • PO-Received
    • PO-ReqCreated
    • PO-ReqRequested
    • Partially Interfaced to Receivables
    • Payment Assurance - Complete
    • Payment Assurance - Incorrect Data
    • Pending Customer Acceptance
    • Pending Internal Approval
    • Picked
    • Picked Partial
    • Preprovision
    • Preprovision Failed
    • Preprovision Requested
    • Preprovision Succeeded
    • Production Complete
    • Production Eligible
    • Production Open
    • Production Partial
    • Provisioning Failed to update Transaction Details
    • Provisioning Rejected
    • Provisioning Requested
    • Provisioning Successful
    • Provisioning in Error
    • Released to Warehouse
    • Reprice - Complete
    • Reprice - Not Applicable
    • Returned
    • Scheduled
    • Shipped
    • Supply Eligible
    • Supply Open
    • Supply Partial
    • Third Party Billing Failed
    • Third Party Billing Requested
    • Third Party Billing Succeeded

    This information can be found in the Approvals Management implementation guide in metalink. The part number for this document is B31622-02
    Regards

  • How to cancel the sales order - header and line status are in Entered Stage

    Dears,
    I have some sales order to be cancelled in which the header and line status are in *"Entered"*. I am not able to cancel these sales order.
    Also note that these orders are for maintenance service.Once i book these orders the lines will change to closed status.
    So it is not possible to book and cancel the lines.
    Kindly me to resolve this.

    926530 wrote:
    Boss,
    If i do Action-->cancel on header, it just makes the qty to zero.But the header and line status still showing as entered.It will not cancel the order.
    The problem for me is that these lines are coming in my monthly reports. This is what your question says...be more specific as what is your issue..which in turn is your problem
    How to cancel the sales order - header and line status are in Entered Stage
    Coming to your Action-->cancel...as far as i know ...the header status will change to canceled..
    unless until you have some processing constraints in place...which is stopping you...
    HTH
    Mahendra

  • Why SO Header not get closed automatically after all SO lines get closed?

    Hi all :
    Do you know the reason, why some SO Header still as Booked Status, even All the SO lines are already closed ?
    If I see the Workflow status the SO Header is in Status = Deferred and Activity = Wait
    And I can close it manually if I rewind the Activity in the Workflow, but I want to know why the SOs not get closed automatically.
    Thank you in advance
    Edited by: Daniel on Jan 18, 2011 8:41 AM

    Have you scheduled the concurrent request to use Workflow Background Processor to Process OEOH ? What is the frequency? Has it run after the lines got closed?
    Also, check the value of the WAIT attribute in the OEOH workflow? By default, it is set to close headers at the end of month.
    For more detail please see Note:141919.1 on Metalink.
    Also refer to metalink document # 397364.1 which details how to change the WAIT attributes.
    Hope this helps,
    Sandeep Gandhi

  • Error while Cancel RMA Using API

    Hi All,
    I was trying to cancel a RMA lines which has the status INVOICE HOLD by using the below script
    DECLARE
    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_chr_ret_status VARCHAR2 (1000) := NULL;
    l_msg_count NUMBER := 0;
    l_msg_data VARCHAR2 (2000);
    l_num_api_version NUMBER := 1.0;
    CURSOR c_so_details IS
    SELECT oh.order_number, ol.
    FROM oe_order_lines_all ol, oe_order_headers_all oh
    WHERE oh.header_id = ol.header_id
    AND oh.org_id = ol.org_id
    AND NVL (ol.cancelled_flag,'N') = 'N'
    AND oh.order_number = '90015792'
    AND ol.line_number in (1,2)
    AND ol.shipment_number = 1
    AND ol.flow_status_code = 'INVOICE_HOLD';
    BEGIN
    SELECT user_id
    INTO l_user_id
    FROM fnd_user
    WHERE user_name = 'CSK_C1';
    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);
    FOR iso_rec IN c_so_details LOOP
    l_line_tbl_in (1) := oe_order_pub.g_miss_line_rec;
    l_line_tbl_in (1).line_id := iso_rec.line_id;
    l_line_tbl_in (1).ordered_quantity := 0;
    l_line_tbl_in (1).change_reason := 'Admin Error';
    l_line_tbl_in (1).change_comments := 'CANCEL ORDER';
    l_line_tbl_in (1).operation := oe_globals.g_opr_update;
    oe_msg_pub.delete_msg;
    mo_global.init;
    mo_global.set_policy_context ('S', iso_rec.org_id);
    oe_order_pub.process_order
    *(p_api_version_number => l_num_api_version,*
    p_init_msg_list => fnd_api.g_false,
    p_return_values => fnd_api.g_false,
    p_action_commit => fnd_api.g_false,
    p_header_rec => l_header_rec_in,
    p_action_request_tbl => l_action_request_tbl_in,
    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_chr_ret_status,
    x_msg_count => l_msg_count,
    x_msg_data => l_msg_data);
    l_msg_data := NULL;
    IF l_chr_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;
    END IF;
    DBMS_OUTPUT.ENABLE (10000);
    DBMS_OUTPUT.put_line ('Sales Order => '||iso_rec.order_number||' - Line Number => '||iso_rec.line_number||' - Shipment Number => '||iso_rec.shipment_number||' Having Line ID=> '||iso_rec.line_id||' Cancelled Successfully' );
    DBMS_OUTPUT.put_line ('Return Status: '|| l_chr_ret_status);
    DBMS_OUTPUT.put_line ('Error Message: '|| l_msg_data);
    END LOOP;
    END;
    but the ouput is*
    Sales Order => 90015792 - Line Number => 1 - Shipment Number => 1 Having Line ID=> 3269602 Cancelled Successfully
    Return Status: U
    Error Message: .FND
    Sales Order => 90015792 - Line Number => 2 - Shipment Number => 1 Having Line ID=> 3269603 Cancelled Successfully
    Return Status: U
    Error Message: .FND
    also the lines still remain INVOICE HOLD
    Could anyone help me on this .
    I want cancel this order by today please suggest.
    Thanks in advance
    CSK.

    Hi Kesava,
    I notice that in the package you used the application user_name=CHUNDUK calls the API pa_project_pub.create_project.
    I wonder if you used chunduk as database user to execute the package Or you used APPS to execute the package?
    The APi document states that it is a requirement to create a db username as the same name with the application username.
    I have been running the problem to execute API 's delete project and try to figure what could be my problem.
    TIA

  • Approved RMA but status is Pending

    Hi,
    I enabled the iStore Return process with Approval. I created one RMA order and Approved by an approver, but the RMA order status still Internal Pending Approval. How to change the order status to Booked at Header level now Internal Pending Approval.
    Thanks
    Vivek

    Hi,
    Probably something wrong in the posting run? Have you checked it (the log of the posting report batch job)? It is probably that the leave cannot be posted to the info type. Check with time management functional consultant.
    Regards,
    Karri

  • While doing RMA, Reference field shows Return Orders as well....

    Hi,
    While testing RMA Functionality, I came across few issues (questions). I need help from all OM Gurus.
    1) When entering RMA Order, once enter the order and go to line, on the reference field, I am trying to link it to Original sales order. Once I select the Sales Order as Reference, I am able to see all the orders placed by that customer. SURPRISINGLY, it also shows the RMA Type of orders as well. Does it an intended functionality?
    2) If the Original sales order line is having 10 qty, when I enter First RMA by giving reference to the original one, it by default populates item number and qty. Now, I override the qty column with lesser qty lets say 5 and process the line. Now when I create another RMA by referencing the RMA order to the same line, it again populates the qty field to 10 only. Ideally, it should populate 5 only as 5 we have already received. Though, we are getting an error saying that it should not be greater than original sales order. But how associate will come to know how many qtys are pending to return?
    3) While entering an original sales order, I have overridden the price from 100 to 80. Now, when I am creating an RMA, it is showing the price as 100 only. I guess there is some functionality called Calculate Price Flag with three options but I am not able to understand what it is actually doing.
    Any help will be highly appreciated.

    1) The Intended Functionality is when you select "Reference Column" for any RMA Line, it will ask you for Reference Type (Lets say you are selecting Sales Order) then it will ask you for Order Number and Line Number. So, this is how Linking the RMA Line with any Sales Order goes.
    2) You have to goto the Original Sales Order -> Select Line -> From Actions Button, select Additional Line Information -> Return Tab. Here, you will get all the RMA or Returns information which are link to this Sales Order Line.
    3) Regarding Calculate Price Flag, the Pricing tab enables you to specify whether the new order or order line is copied at the original pricing or is repriced. To reprice, you can specify the pricing date. If you choose to reprice the order or order line, manual discounts and charges are removed and automatic discounts and charges are recalculated. If you choose to retain original pricing, all discounts and charges are retained and the Calculate Price Flag is set to Freeze Price for order lines and Partial Price for return lines. Additionally, you can choose to set the Calculate Price Flag to Partial Price by selecting the corresponding radial button on the Pricing Options Tab.
    When the destination order type while copying an order is RMA, Order Management will set the Calculate Price Flag to P for the copied
    order lines even if you specify At Original Price within the Pricing Options tab copy window.
    Hope it may help you.
    Regards,
    Khan.

  • Create new order status and line status in oracle EBS

    Hi,
    I want to create new order status,line status (Like Booked, Entered etc.) and also want these in istore .
    Please help me out.please provide the navigation path to create this.
    Thanks
    Mark
    Edited by: Mark on Jun 30, 2011 5:03 PM

    Have you check in the online documentation for Ebiz, and metalink.?

  • Getting error RVTBM-008 and RVTBM-120 during receiving RMA line

    Hello,
    Initially we tried to receive the RMA line but here we forgot to setup the lot number hence i am getting error when i was run the receiving transaction processor.
    Then i put the correct LOT number and again delete all the lines from 'Receiving Transaction Summary' and tried to receive the RMA line in Inventory but i am getting below error when the Receiving Transaction Processor run.
    Concurrent program RVCTP returned error
    Cause: RVCTP encountered an internal error. Parameters: RVCTP,IMMEDIATE,584656,
    Action: Note both this error number and the actions you are trying to perform. Contact your system ad
    RVTBM-008: Subroutine rvtbm_immediate_mngr() returned error
    Cause: Subroutine rvtbm_immediate_mngr() returned an internal error.
    Action: Note this error number and the actions you are trying to perform. Contact your syste
    RVTBM-120: Subroutine rvtptcontrol() returned error
    Cause: Subroutine rvtptcontrol() returned an internal error.
    Action: Note this error number and the actions you are trying to perform. Contact your system administrator
    Concurrent Manager encountered an error while attempting to start your immediate concurrent program RVCTP. Routine &ROUTINE received a return code of failure.
    Contact your support representative.
    I am using Apps version-12.0.6
    Please help me to rectify this issue.
    Thanks,
    Rajesh

    Action: Note both this error number and the actions you are trying to perform. Contact your system ad
    RVTBM-008: Subroutine rvtbm_immediate_mngr() returned error
    Cause: Subroutine rvtbm_immediate_mngr() returned an internal error.
    Action: Note this error number and the actions you are trying to perform. Contact your syste
    RVTBM-120: Subroutine rvtptcontrol() returned errorSearch MOS for the above two errors and go through the docs.
    RMA Deliver Transactions Stuck in RVCTP With RVTPT-020: Rvtoe_rmapushapi() [ID 278993.1]
    UNABLE TO MAKE RECEIPTS AGAINST RMA User-Defined Exception in Package [ID 1082586.1]
    RCVRCERC: Some RMAs fail with RVTBM-008: Subroutine rvtbm_immediate_mngr() returned error [ID 738890.1]
    RVTII-030 rvtiicreate() When Receiving some RMA [ID 371464.1]
    RVTBM-008: Subroutine rvtbm_immediate_mngr() returned error in Depot Repair Bulk Receiving [ID 1301960.1]
    Thanks,
    Hussein

Maybe you are looking for