CREDITED_INVOICE_ID - Relevant field in AP Open Interface

Hi All,
I just want to know, If I'm importing Credit Invoices through Open Interface, in which field of open interface (header or lines) should I insert "Credited Invoice ID" as I want this field:
ap_invoices_all.credited_invoice_id,
.. to be populated.
Please advise....
Thanks,
OraLearner

If I understand your requirement correctly, you want to purge the PROCESSED invoices from the interface tables. May be you can create a Request Set for the:
1.Invoice Open Interface Import and
2. Purge Program for the interface tables.
Thanks

Similar Messages

  • PAYABLES OPEN INTERFACE INVOICE IMPORT 시 REQUIRED FIELD 정보

    제품 : FIN_AP
    작성날짜 : 2005-05-10
    PAYABLES OPEN INTERFACE INVOICE IMPORT 시 REQUIRED FIELD 정보
    ==========================================================
    PURPOSE
    AP Open Interface Invoice Import 를 통해 Invoice 를 생성 코자 할 경우 반드시 필요한 Field 에 대한 정보이다.
    Explanation
    1. PO 나 Project 과 Match 하지 않는 Invoice Case
    Table : AP_INVOICE_INTERFACE
    ==============================
    Required Columns
    ================
    -INVOICE_ID : AP_INVOICES_INTERFACE_S.NEXTVAL를 이용하여 생성됨
    -INVOICE_NUM : 특정 Supplier 내에서는 unique 해야함
    -VENDOR_ID/VENDOR_NUM/VENDOR_NAME : Active 하여야 하며 PO_VENDORS과 Mapping
    -VENDOR_SITE_ID/VENDOR_SITE_CODE : Active 한 Site 여야 하며 PO_VENDOR_SITES table과 mapping
    -INVOICE_AMOUNT : 'STANDARD' type인 경우에는 양수, 'CREDIT' type인 경우는 음수를 입력
    -ORG_ID : AP_SYSTEM_PARAMETERS.ORG_ID
    -SOURCE : select lookup_code from ap_lookup_codes where lookup_type='SOURCE' 중 하나
    Table : AP_INVOICE_LINES_INTERFACE
    ==================================
    Required Columns for LINE_TYPE_LOOKUP_CODE = 'ITEM'
    ===================================================
    -INVOICE_ID : AP_INVOICES_INTERFACE.INVOICE_ID
    -INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S.NEXTVAL
    -LINE_NUMBER : 해당 invoice 내에서 unique 해야함.
    -LINE_TYPE_LOOKUP_CODE :'ITEM'
    -AMOUNT
    -ACCOUNTING_DATE: Optional. Defaulted from INVOICE_DATE or SYSDATE
    - DIST_CODE_CONCATENATED / DIST_CODE_COMBINATION_ID
    : select code_combination_id from gl_code_combinations
    where account_type = 'E' and enabled_flag = 'Y'
    and summary_flag = 'N'
    and sysdate between nvl(start_date_active, sysdate-1)
    and nvl(end_date_active, sysdate+1))
    Required Columns for LINE_TYPE_LOOKUP_CODE = 'TAX'
    ===================================================
    -INVOICE_ID : AP_INVOICES_INTERFACE.INVOICE_ID
    -INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S.NEXTVAL
    -LINE_NUMBER : 해당 invoice 내에서 unique 해야함.
    -LINE_TYPE_LOOKUP_CODE : 'TAX'
    -TAX_CODE / TAX_CODE_ID : AP_TAX_CODES_ALL table에서 mapping
    -AMOUNT
    -ACCOUNTING_DATE : Optional. Defaulted from INVOICE_DATE or SYSDATE
    -DIST_CODE_CONCATENATED or DIST_CODE_COMBINATION_ID
    : select code_combination_id from gl_code_combinations
    where account_type = 'E' and enabled_flag = 'Y'
    and summary_flag = 'N'
    and sysdate between nvl(start_date_active, sysdate-1)
    and nvl(end_date_active, sysdate+1))
    2. PO Matched Invoice 의 경우                    Table: AP_INVOICE_INTERFACE
    ============================
    Required Columns
    ================
    -INVOICE_ID : AP_INVOICES_INTERFACE_S.NEXTVAL를 이용하여 생성됨
    -INVOICE_NUM : 특정 Supplier 내에서는 unique 해야함
    -PO_NUMBER : approved 된 PO 여야 하며 cancelled, closed 혹은 final closed 된 PO NUMBER 는 안됨. PO_HEADERS Table 과 mapping
    -INVOICE_AMOUNT : 'STANDARD' type인 경우에는 양수, 'CREDIT' type인 경우는 음수를 입력
    -SOURCE : select lookup_code from ap_lookup_codes where lookup_type='SOURCE'
    -ORG_ID : AP_SYSTEM_PARAMETERS_ALL.ORG_ID
    Table: AP_INVOICE_LINES_INTERFACE
    =================================
    Required Columns for PO Matched Lines
    =====================================
    -INVOICE_ID : AP_INVOICES_INTERFACE.INVOICE_ID
    -INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S.NEXTVAL
    -LINE_NUMBER : 해당 invoice 내에서 unique 해야함.
    -LINE_TYPE_LOOKUP_CODE : 'ITEM'
    -AMOUNT : QUANTITY_INVOICED * UNIT_PRICE
    If MATCH_OPTION is 'P', then populate:
    -RELEASE_NUM or PO_RELEASE_ID : Blanket Release only, validated against PO_RELEASES_ALL
    -PO_NUMBER or PO_HEADER_ID : Validated against PO_HEADER_ALL
    -PO_LINE_NUMBER or PO_LINE_ID : Validated against PO_LINES_ALL
    -PO_SHIPMENT_NUM or PO_LINE_LOCATION_ID : Validated against PO_LINE_LOCATIONS_ALL
    If MATCH_OPTION is 'R', then populate:
    -RECEIPT_NUMBER : RCV_SHIPMENT_HEADERS.RECEIPT_NUM
    -RCV_TRANSACTION_ID or PO_LINE_LOCATION_ID : RCV_TRANSACTIONS과 Mapping
    Example
    Reference Documents
    Note 205331.1

    Chandrasekar,
    as i know, the main thing you should consider is, that starting from R12 you will
    be able to import invoices only through the Payables Open Interface.
    basically, Invoice Import is used by OA to create invoice (from expense reports or from Oracle Projects). for standard invoice import, i've ever used Payables Open Interface.
    Milan
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Chandrasekara Kayamboo ([email protected]):
    I would like to know which is the best way to import invoice and what are the advantages and disadvange in each.
    Regards
    Chandrasekar<HR></BLOCKQUOTE>
    null

  • Flex field values open interface tables

    Hi ,
    Could anyone please tell me which of the Oracle Apps. Open interface tables used to upload Gl. Segment values.
    Thanks
    Jonny

    If just DFF Attribute column try direct update of attribute column.
    Otherwise perhaps the APIs have them?
    Regards,
    Gareth

  • Invoices Payables Open Interface Import Error REP-1419: 'beforereport': PL/

    I am having the following error when I try to import the invoces from the interface tables. I've search for the problem but and tried various solutions but they did not solve the problem or did not apply.
    Can someone help??
    APXIIMPT module: Payables Open Interface Import
    Current system time is 22-SEP-2006 22:31:13
    +-----------------------------
    | Starting concurrent program execution...
    +-----------------------------
    Arguments
    p_source='CI'
    p_batch_name='INITIAL'
    p_purge_flag='N'
    p_trace_switch='N'
    p_debug_switch='N'
    p_summary_flag='N'
    p_commit_batch_size='1000'
    p_user_id='1115'
    p_login_id='337907'
    Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
    American_America.WE8ISO8859P1
    MSG-01104: (Before Report) Modified file
    MSG-00000: p_purge_flag :N
    MSG-00000: c_nls_yes :Yes
    MSG-00000: c_nls_no :No
    MSG-00000: p_summary_flag :N
    MSG-00000: p_nls_summary :No
    MSG-00000: p_nls_purge :No
    REP-1419: 'beforereport': PL/SQL program aborted.
    Report Builder: Release 6.0.8.25.0 - Production on Fri Sep 22 22:31:14 2006
    (c) Copyright 1999 Oracle Corporation. All rights reserved.
    Enter Username:
    Start of log messages from FND_FILE
    End of log messages from FND_FILE
    Program exited with status 1
    Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 577860.
    Review your concurrent request log and/or report output file for more detailed information.

    I get the following error message: "Invalid Liability Liability account is invalid". I've tried both populating the ACCTS_PAY_CODE_COMBINATION_ID field and leaving it null. Some googling also said mentioned that particular error message may be misleading.
    And yes, I'm passing the correct code from the lookup_type. The only difference is that for the one that works, I'm using an Oracle seeded source lookup. However, in the lookups screen I can't see where there are any special configuration.
    I should also mention that the invoices will be imported from an external system, and there will be no PO attached to the invoice. I'm not sure if this info is relevent though.
    I've done some researching and thinking and maybe there is some kind of profile option I need to set but I haven't been able to find it yet.
    Also, I can't find the AP_ERRORS_GT table or any other closely named ones.
    Edited by: Sean Ong on 15/08/2012 01:27

  • Payables Open Interface Import error

    Hi all
    I have the following issue in EBS R12.
    RDBMS : 11.2.0.3.0
    Oracle Applications : 12.1.3
    I'm inserting records into the AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables and then running the "Payables Open Interface Import" concurrent program.
    When I set the SOURCE column in the AP_INVOICES_INTERFACE table as a user-defined source (from AP_LOOKUP_CODES wher lookup_type = 'SOURCE') I get an error. If instead, I use a seeded source (ERS), it works. Every other field is exactly the same.
    There is no difference between the lookups in the AP_LOOKUP_CODES. There is one difference in the lookups in that ERS is created as a "INVOICE TRX SOURCE" in the Purchasing Lookups. I'm unable to add my user-defined source there because it is a protected System lookup.
    Looking a bit more, I noticed that ERS seems to have some additional lookups associated to it. Is there some configuration I need to do for my user-defined lookup? If so, where should I do it?
    Has anyone encountered this problem before? If so, what was your solution?
    Cheers,
    Sean

    I get the following error message: "Invalid Liability Liability account is invalid". I've tried both populating the ACCTS_PAY_CODE_COMBINATION_ID field and leaving it null. Some googling also said mentioned that particular error message may be misleading.
    And yes, I'm passing the correct code from the lookup_type. The only difference is that for the one that works, I'm using an Oracle seeded source lookup. However, in the lookups screen I can't see where there are any special configuration.
    I should also mention that the invoices will be imported from an external system, and there will be no PO attached to the invoice. I'm not sure if this info is relevent though.
    I've done some researching and thinking and maybe there is some kind of profile option I need to set but I haven't been able to find it yet.
    Also, I can't find the AP_ERRORS_GT table or any other closely named ones.
    Edited by: Sean Ong on 15/08/2012 01:27

  • Open Interface Rejects - SQL Report

    Hi guys, I'm trying to help out some folks in AP with an easier access to view Open Interface rejects. I already knew the relation between AP_INVOICES_INTERFACE and AP_INTERFACE_REJECTIONS was INVOICE_ID AND PARENT_ID (respectively). Now I've seen that some invoices also have a relation between AP_INVOICE_LINES_INTERFACE and AP_INTERFACE_REJECTIONS, same columns related (INVOICE_ID AND PARENT_ID respectively).
    What I'm having a problem with, maybe I've just been sitting here too long, but I cannot get it all into one report.
    I tried this, but it's giving me way more records than it should:
    SELECT AIR.CREATION_DATE
    , AIR.REJECT_LOOKUP_CODE
    , AII.PO_NUMBER
    , AII.GROUP_ID
    , AII.VENDOR_NUM
    , AII.INVOICE_NUM
    , AII.INVOICE_DATE
    , AII.INVOICE_AMOUNT
    , AII.SOURCE
    FROM AP.AP_INTERFACE_REJECTIONS AIR
    , AP.AP_INVOICES_INTERFACE AII
    , AP.AP_INVOICE_LINES_INTERFACE AILI
    WHERE (AII.INVOICE_ID = AIR.PARENT_ID AND AII.ORG_ID = 162)
    OR (AILI.INVOICE_ID = AIR.PARENT_ID AND AILI.ORG_ID = 162)
    Any thoughts on where I mucked it up or how I could actually go about this? What shows in the actual Open Interface app is a good start, it's just missing some fields like vendor name and reject lookup code.
    Thanks for any help!

    945273 wrote:
    Hi guys, I'm trying to help out some folks in AP with an easier access to view Open Interface rejects. I already knew the relation between AP_INVOICES_INTERFACE and AP_INTERFACE_REJECTIONS was INVOICE_ID AND PARENT_ID (respectively). Now I've seen that some invoices also have a relation between AP_INVOICE_LINES_INTERFACE and AP_INTERFACE_REJECTIONS, same columns related (INVOICE_ID AND PARENT_ID respectively).
    What I'm having a problem with, maybe I've just been sitting here too long, but I cannot get it all into one report.
    I tried this, but it's giving me way more records than it should:
    SELECT AIR.CREATION_DATE
    , AIR.REJECT_LOOKUP_CODE
    , AII.PO_NUMBER
    , AII.GROUP_ID
    , AII.VENDOR_NUM
    , AII.INVOICE_NUM
    , AII.INVOICE_DATE
    , AII.INVOICE_AMOUNT
    , AII.SOURCE
    FROM AP.AP_INTERFACE_REJECTIONS AIR
    , AP.AP_INVOICES_INTERFACE AII
    , AP.AP_INVOICE_LINES_INTERFACE AILI
    WHERE (AII.INVOICE_ID = AIR.PARENT_ID AND AII.ORG_ID = 162)
    OR (AILI.INVOICE_ID = AIR.PARENT_ID AND AILI.ORG_ID = 162)
    Any thoughts on where I mucked it up or how I could actually go about this? What shows in the actual Open Interface app is a good start, it's just missing some fields like vendor name and reject lookup code.
    Thanks for any help!I don't know the table strructures or relationships, but based on what you said, I think you want something more like:
    SELECT air.creation_date, air.reject_lookup_code, aii.po_number, aii.group_id,
           aii.vendor_num, aii.invoice_num, aii.invoice_date, aii.invoice_amount,
           aii.source
    FROM ap.ap_interface_rejections air, ap.ap_invoices_interface aii,
         ap.ap_invoice_lines_interface aili
    WHERE ali.invoice_id = alii.invoice_id and
          ali.invoice_id = air.parent_id and
          aii.org_id = 162You may need/want to add the org_cd predicate to the interfact lines as well, depending if there could be invoices with the same id in multiple orgs.
    Assuming you have the relations correct, this should give you a row for every line on every invoice that has a row in the ap_interface_rejections table. It might be worthwhile to look at the ap_interface_rejections table to see if it has an analog for the invoice line number, which could also be used in the join, to get a more specific result set.
    John

  • APXSUIMP module: Supplier Open Interface Import  ERROR

    Hi All,
    I am loading our historical data po_vendors from old EBS 11.0.3 to the new EBS 11i.
    I inserted the data first in AP_SUPPLIERS_INT table.
    Then I run the program APXSUIMP.
    But I got the ff. error
    >
    Payables: Version : 11.5.0 - Development
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    APXSUIMP module: Supplier Open Interface Import
    Current system time is 17-DEC-2008 15:55:17
    +-----------------------------
    | Starting concurrent program execution...
    +-----------------------------
    Arguments
    P_WHAT_TO_IMPORT='ALL'
    P_COMMIT_SIZE='1000'
    P_PRINT_EXCEPTIONS='Y'
    P_DEBUG_SWITCH='Y'
    P_TRACE_SWITCH='Y'
    Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
    American_America.US7ASCII
    Spawned Process 2113682
    MSG-00001: After SRWINIT
    MSG-00002: After Get_Company_Name
    MSG-00003: After Get_NLS_Strings
    REP-1419: 'beforereport': PL/SQL program aborted.
    Report Builder: Release 6.0.8.25.0 - Production on Wed Dec 17 15:55:18 2008
    (c) Copyright 1999 Oracle Corporation. All rights reserved.
    Enter Username:
    Start of log messages from FND_FILE
    End of log messages from FND_FILE
    Program exited with status 1
    Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 285681.
    Review your concurrent request log and/or report output file for more detailed information.
    Executing request completion options...
    Finished executing request completion options.
    Concurrent request completed
    Current system time is 17-DEC-2008 15:55:18
    >
    Can you help please....Thanks

    Hi,
    This is just a one-table test run only for ap_supplier_int > vo_vendors
    By the way the set-up is non multi-org, does if affect the error?
    Searched WebIV with "APXSUIMP REP-1419 beforereport" and found: .
    Note.313569.1 Ext/Mod APXSUIMP Supplier Open Interface Receives the Following Error REP-1419 .
    Symptoms
    The APXSUIMP module: Supplier Open Interface Import is erroring with the following error: .
    MSG-00003:
    After Get_NLS_Strings REP-1419: 'beforereport': PL/SQL program aborted. .
    Patch#4172504 - has been applied,
    however, the process still errors. .
    Cause
    As this was a new test instance, the user had not set the
    MO:Operating Unit profile option in the System Administrator responsibility,
    nor run the Execute Convert to Multi-org utility from adadmin. .
    The system was not setup properly. .
    Solution
    #1 - Apply patch#4172504 ->->-> this CT is already above this code
    #2 - Responsibility:
    System Administrator Navigation:
    Profile-System Ensure a value has been set for profile MO:Operating Unit.
    #3 - Execute Convert to Multi-org from adadmin. . .
    WORKAROUNDS: ------------ Patch 5167581 was applied and did not resolve the issue .
    Set for profile MO:Operating Unit.     Responsibility: System Administrator    
    Navigation: Profile-System . No change, error still exists We also don not have value for MO: Operating Unit > What value should I put on this field?
    Thanks a lot

  • SAMPLE RECEIVING OPEN INTERFACE SCRIPT(ROI 이용자를 위한 SCRIPT)

    제품: MFG_PO
    작성날짜 : 2006-05-11
    SAMPLE RECEIVING OPEN INTERFACE SCRIPT(ROI 이용자를 위한 SCRIPT)
    ================================================================
    PURPOSE
    Receiving Open Interface(ROI)를 좀더 쉽게 사용할 수 있도록 만들어진
    tool이라고 할 수 있다. 이 script를 이용을 통해 user는 PO no, user id,
    Org id를 입력하면 script는 PO에서 최소한의 data를 가져와 receiving
    transaction을 생성하기 위해 ROI에 data를 입력한다.
    Receiving Transaction Processor는 insert 된 data를 실행한다.
    Explanation
    Instructions:
    1.Script exroi.sql을 local computer에 copy 하거나 sqlplus 환경의 text
    edior에 script 내용을 cut&paste 한다.
    2.사용가능한 PO no, User id, Org id를 결정한다.
    3.sqlplus prompt에서 아래와 같이 입력한다.
    SQL> @ezroi.sql
    4.PO no, User id, Org id를 입력하라는 prompt를 볼 수 있을 것이다.
    5.exroi.sql script를 관련된 PO data를 가져와 rcv_headers_interface 및
    rcv_transactions_interface tables에 insert 한다.
    만일 PO shipment lind이 closed, cancelled, fully received 되었다면
    ROI table에 data를 insert 하지 않는다.
    Note: 이 script가 data를 validate 하진 않으며,ROI API 자체 validation
    이 실행될 뿐이다.
    6.Script가 끝나면 Receiving Transaction Processor를 실행하여 insert 된
    lines을 처리할 수 있다. Transaction Status Summary 화면을 통해 실행된
    line이 pending 인지 error 상태인지 확인할 수 있다.
    Notes:
    1.Org_id parameter 값을 찾는법:
    a) Application에 접속, Help> Diagnostics> Examine으로 이동.
    Block:$Profile$, Field: ORG_ID 를 선택한다.
    b) ORG_ID 값을 note 해 놓고 ORG_ID prompt시 이 값을 입력한다.
    2.User_Name parameter 값을 찾는법:
    a) Application에 접속, Help> Diagnostics> Examine으로 이동.
    Block:$Profile$, Field: USER_NAME 를 선택한다.
    b) USER_NAME 값을 note 해 놓고 USER_NAME prompt시 이 값을 입력한다.
    Example
    "eZROI.sql' script...
    --*** eZROI ***
    --*** by ***
    --*** Preston D. Davenport ***
    --*** Oracle Premium Applications Support ***
    --*** Oracle Worldwide Global Support Services ***
    --*** Date: 23-JUL-2003 - Beta release ***
    --*** Date: 09-SEP-2003 - Rev A Added multi- ***
    --*** shipment line capability ***
    --*** Parameters: ***
    --*** ORG_ID Organization ID ***
    --*** USER_NAME FND User Name ***
    --*** PO_NUMBER Purchase Order Number ***
    --*** This script intended for a standard Purchase ***
    --*** Order document to be inserted into the Oracle ***
    --*** Receiving Open Interface (ROI) via the standard ***
    --*** Oracle open interface api for a simple Receive ***
    --*** transaction. ***
    --*** Note: This script only considers open Purchase ***
    --*** Orders. This script will not allow over- ***
    --*** receipt, cancelled or closed PO's to be ***
    --*** inserted into the ROI and received ***
    CLEAR BUFFER
    SET VERIFY OFF
    SET LINESIZE 140
    SET PAGESIZE 60
    SET ARRAYSIZE 1
    SET SERVEROUTPUT ON SIZE 100000
    SET FEEDBACK OFF
    SET ECHO OFF
    DECLARE
    X_USER_ID NUMBER;
    X_PO_HEADER_ID NUMBER;
    X_VENDOR_ID NUMBER;
    X_SEGMENT1 NUMBER;
    X_ORG_ID NUMBER;
    X_LINE_NUM NUMBER;
    BEGIN
    DBMS_OUTPUT.PUT_LINE('***ezROI RCV API Insert Script***');
    SELECT PO_HEADER_ID , VENDOR_ID , SEGMENT1 , ORG_ID
    INTO X_PO_HEADER_ID , X_VENDOR_ID , X_SEGMENT1 , X_ORG_ID
    FROM PO_HEADERS_ALL
    WHERE SEGMENT1 = '&PO_NUMBER'
    AND ORG_ID = &ORG_ID;
    SELECT USER_ID INTO X_USER_ID
    FROM FND_USER
    WHERE USER_NAME = UPPER('&USER_NAME');
    INSERT INTO RCV_HEADERS_INTERFACE
    HEADER_INTERFACE_ID ,
    GROUP_ID ,
    PROCESSING_STATUS_CODE ,
    RECEIPT_SOURCE_CODE ,
    TRANSACTION_TYPE ,
    LAST_UPDATE_DATE ,
    LAST_UPDATED_BY ,
    LAST_UPDATE_LOGIN ,
    VENDOR_ID ,
    EXPECTED_RECEIPT_DATE ,
    VALIDATION_FLAG
    SELECT
    RCV_HEADERS_INTERFACE_S.NEXTVAL ,
    RCV_INTERFACE_GROUPS_S.NEXTVAL ,
    'PENDING' ,
    'VENDOR' ,
    'NEW' ,
    SYSDATE ,
    X_USER_ID ,
    0 ,
    X_VENDOR_ID ,
    SYSDATE ,
    'Y'
    FROM DUAL;
    DECLARE
    CURSOR PO_LINE IS
    SELECT PL.ITEM_ID , PL.PO_LINE_ID , PL.LINE_NUM ,
    PLL.QUANTITY , PL.UNIT_MEAS_LOOKUP_CODE ,
    MP.ORGANIZATION_CODE , PLL.LINE_LOCATION_ID ,
    PLL.CLOSED_CODE , PLL.QUANTITY_RECEIVED ,
    PLL.CANCEL_FLAG, PLL.SHIPMENT_NUM
    FROM PO_LINES_ALL PL ,
    PO_LINE_LOCATIONS_ALL PLL ,
    MTL_PARAMETERS MP
    WHERE PL.PO_HEADER_ID = X_PO_HEADER_ID
    AND PL.PO_LINE_ID = PLL.PO_LINE_ID
    AND PLL.SHIP_TO_ORGANIZATION_ID = MP.ORGANIZATION_ID;
    BEGIN
    FOR CURSOR1 IN PO_LINE LOOP
    IF CURSOR1.CLOSED_CODE IN ('APPROVED','OPEN')
    AND CURSOR1.QUANTITY_RECEIVED < CURSOR1.QUANTITY
    AND NVL(CURSOR1.CANCEL_FLAG,'N') = 'N'
    THEN
    INSERT INTO RCV_TRANSACTIONS_INTERFACE
    INTERFACE_TRANSACTION_ID ,
    GROUP_ID ,
    LAST_UPDATE_DATE ,
    LAST_UPDATED_BY ,
    CREATION_DATE ,
    CREATED_BY ,
    LAST_UPDATE_LOGIN ,
    TRANSACTION_TYPE ,
    TRANSACTION_DATE ,
    PROCESSING_STATUS_CODE ,
    PROCESSING_MODE_CODE ,
    TRANSACTION_STATUS_CODE ,
    PO_LINE_ID ,
    ITEM_ID ,
    QUANTITY ,
    UNIT_OF_MEASURE ,
    PO_LINE_LOCATION_ID ,
    AUTO_TRANSACT_CODE ,
    RECEIPT_SOURCE_CODE ,
    TO_ORGANIZATION_CODE ,
    SOURCE_DOCUMENT_CODE ,
    DOCUMENT_NUM ,
    HEADER_INTERFACE_ID ,
    VALIDATION_FLAG
    SELECT
    RCV_TRANSACTIONS_INTERFACE_S.NEXTVAL ,
    RCV_INTERFACE_GROUPS_S.CURRVAL ,
    SYSDATE ,
    X_USER_ID ,
    SYSDATE ,
    X_USER_ID ,
    0 ,
    'RECEIVE' ,
    SYSDATE ,
    'PENDING' ,
    'BATCH' ,
    'PENDING' ,
    CURSOR1.PO_LINE_ID ,
    CURSOR1.ITEM_ID ,
    CURSOR1.QUANTITY ,
    CURSOR1.UNIT_MEAS_LOOKUP_CODE ,
    CURSOR1.LINE_LOCATION_ID ,
    'RECEIVE' ,
    'VENDOR' ,
    CURSOR1.ORGANIZATION_CODE ,
    'PO' ,
    X_SEGMENT1 ,
    RCV_HEADERS_INTERFACE_S.CURRVAL ,
    'Y'
    FROM DUAL;
    DBMS_OUTPUT.PUT_LINE('PO line: '||CURSOR1.LINE_NUM||' Shipment: '||CURSOR1.SHIPMENT_NUM||' has been inserted into ROI.');
    ELSE
    DBMS_OUTPUT.PUT_LINE('PO line '||CURSOR1.LINE_NUM||' is either closed, cancelled, received.');
    END IF;
    END LOOP;
    DBMS_OUTPUT.PUT_LINE('*** ezROI COMPLETE - End ***');
    END;
    COMMIT;
    END;
    SET VERIFY ON
    Reference Documents
    Note 245334.1

    I have the same problem on ESXI 5.5 for over a month now, tried the patches, tried the LTS kernel which others say results in an immediate result without patches, nothing seems to work and nobody seems to be able to offer a solution.
    Did you make any progress ??
    Error! Build of vmblock.ko failed for: 3.10.25-1-lts (x86_64)
    Consult the make.log in the build directory
    /var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
    make[2]: *** No rule to make target '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/linux/inode', needed by '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/vmblock.o'. Stop.
    Makefile:1224: recipe for target '_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock' failed
    make[1]: *** [_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock] Error 2
    make[1]: Leaving directory '/usr/src/linux-3.10.25-1-lts'
    Makefile:120: recipe for target 'vmblock.ko' failed
    Last edited by crankshaft (2014-01-10 11:32:32)

  • Supplier Open Interface Import

    Hi All,
    I loaded data into AP_SUPPLIERS_INT but when I run the program Supplier Open Interface Import, it does not update the STATUS field in AP_SUPPLIERS_INT and report shows:
    Atrium Corporation Report Date: 25-SEP-2010 12:39
    Suppliers Open Interface Import Execution Report Page: 1
    Import Options: New
    Batch Size: 1000
    Print Exceptions Only: No
    Suppliers Open Interface Audit Report
    Supplier Supplier
    Number Name
    Total Suppliers Imported: 0
    *** No Data Exists for this Report ***
    Suppliers Open Interface Rejections Report
    Supplier Supplier
    Number Name Reason
    Total Suppliers Rejected: 0
    *** No Data Exists for this Report ***
    Any help, please.
    Thanks
    John

    Hi,
    Unhide the Debug (Debug Switch) parameter of the Report, Supplier Open Interface Import and run the program with Debug flag as Yes.
    Please post the log to help us understand the issue.
    Regards,
    Sridhar

  • EAM Asset Number Open Interface  - Technical Reference docs required

    Hello,
    I'm developing a migration of EAM assets.
    I have no issue by filling the interface tables MTL_EAM_ASSET_NUM_INTERFACE and MTL_EAM_ATTR_VAL_INTERFACE and then running the "Import Asset Number" standard functionallity.
    But, I need to work with genealogy information. The table MTL_OBJECT_GENEALOGY_INTERFACE is used to relate parent and child assets .. but when I run "Import Asset Number" nothing happens .. I mean, if I query the asset in the application, I can see it without the parent asset association.
    Now, I'm trying to use the API's for EAM, but until now without success ...
    I saw that there exist a "Technical Reference" document for EAM .. but I can't find it ...
    Do you know from where I can download it ? ...
    or, if the mentioned document does not exist anymore
    Do you know where I can find documents about eAM Open Interface, more detailed than the information of the "Implementation Guide" ?
    Thanks in advance,
    Sergio Maestri

    Did the original poster ever find a resolution to this issue? I'm seeing the same behavior. I examined all of the documentation listed in the post already (though I can't find doc 256410.1).
    In my example, my child asset is a rebuildable asset, but that won't always be the case. Even though I see that the Import Asset Genealogy request has run successfully, my record doesn't change. I should get an error  as I'm deliberately trying to create a new parent-child relationship with a child that currently has a parent. This gives me an error message in the Maintenance Super User -> Asset -> Configuration History page.
    Here's what I did to create the import record:
    insert into MTL_OBJECT_GENEALOGY_INTERFACE
    (INTERFACE_HEADER_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, BATCH_ID, GROUP_ID, OBJECT_TYPE, PARENT_OBJECT_TYPE, GENEALOGY_ORIGIN, GENEALOGY_TYPE, PROCESS_STATUS, IMPORT_MODE,
    ORGANIZATION_CODE, INVENTORY_ITEM_ID, SERIAL_NUMBER, PARENT_ORGANIZATION_CODE, PARENT_INVENTORY_ITEM_ID, PARENT_SERIAL_NUMBER, START_DATE_ACTIVE) VALUES
    (MTL_OBJECT_GEN_INTERFACE_S.NEXTVAL, sysdate, 1068, sysdate, 1068, 100, 100, 2, 2, 3, 5, 'P', 0,
    'EM1', 8319, 'Battery1000', 'EM1', 7885, 'FL1020', sysdate);
    The only way I could get this to work was to set the MTL_OBJECT_GENEALOGY_INTERFACE.PROCESS_STATUS = 'R' and then call EAM_GENEALOGY_IMPORT_PUB.import_genealogy via PL/SQL. If I did that, I didn't get an error back from the PL/SQL call, but I did get a decent message in the ERROR_MESSAGE field of the interface table: "Child Battery1000 already has a parent FL1030 from 15-DEC-2006 10:43:50; the open period from 16-AUG-2013 15:55:52 overlaps with it."
    The Parameters dialog for the Import Asset Genealogy request only works if PROCESS_STATUS = 'P' and the EAM API only works if PROCESS_STATUS = 'R'.
    Is it me or does this seem poorly thought out or at the very least poorly documented?

  • How to get unique Batch Name for AP Open Interface Import Program

    Hi,
    We have enabled the invoice batch controls i.e. the profile option 'AP: Use Invoice Batch Controls' set to Yes.
    We have an interface with some system from where we receive a data file that has AP invoices. The invoices are loaded into staging table, and finally into AP invoice interface tables. After this the AP Open interface import is run.
    The relevant programs are in a concurrent request set and are executed every day.
    The issue is with the 'Batch Number' parameter of the Payables Open Interface Import Program. If I enter some text as the batch number, the Batch gets created with that name only. As such we need the Batch number to be unique for each job run.
    Oracle help says "If the AP: Use Invoice Batch Controls profile option is enabled and if you provide no value for this parameter then the system provides a value for you. The value the system provides is the concatenation of the Source and a unique sequential number. For example, ERS: 1234".
    However the problem is the Batch Name Parameter is mandatory, and cannot be left NULL.
    Has any one faced this issue earlier? Am I missing any setup or step?
    Any inputs in this regard would be highly appreciated!
    Best regards,
    Anand

    The proper Oracle suggested method would be to put a wrapper program around your request set that determines the batch name.
    The easier (abet less supported) method:
    CREATE OR REPLACE TRIGGER custom.coop_ap_batches_all_insert
    BEFORE
    INSERT
    ON ap.ap_batches_all
    REFERENCING NEW AS NEW OLD AS OLD
    FOR EACH ROW
    BEGIN
    -- to update batch name...
    -- created so that the nightly batches can have unique names by date
    -- nightly batches will be created with their simple name
    -- IE VIR, DI, MI, etc... this trigger will rename them
    -- to YYYY-MM-DD-VIR, YYYY-MM-DD-DI, YYYY-MM-DD-MI, etc...
    IF LENGTH(TRIM(:new.batch_name)) < 4 THEN
    :new.batch_name := TO_CHAR(SYSDATE,'YYYY-MM-DD') || '-' || :new.batch_name;
    END IF;
    :new.batch_name := UPPER(:new.batch_name);
    END;
    /

  • Payable Open Interface Import---Asset Book name is being generated

    Hi,
    I am working on Payables Open Interface Import in R12.
    I am not generating the 'Track as Asset Flag' and 'Asset Book Type Code' fields in Ap_invoice_lines_nterface table.
    And the distribution account is also an Expense account.
    But after the payables open interface import is completed, the asset book name is being populated in ap_invoice_lines_all table.
    and as a result, recoverable and non recoverable tax lines are being created in the ap_invoice_distributions_all table making the invoice total and line total unequal.
    Did any body faced a similar issue?
    Please help....
    this is really very urgent.
    Any queries, please ask me [email protected]
    Thanks in advance,
    Sharmila

    Hi,
    I have raised a SR with Oracle and got following suggestion:
    === ODM Solution /Action Plan ===
    To implement the solution, please execute the following steps:
    1. Download and review the readme and pre-requisites for Patch.9577089:R12.AP.B.
    2. Ensure that you have taken a backup of your system before applying
    the recommended patch.
    3. Apply the patch in a test environment.
    4. Confirm the following file versions:
    120.67.12010000.27 of apiimutb.pls
    You can use the commands like the following:
    strings -a $XX_TOP/filename |grep '$Header'
    5. Retest the issue.
    6. Migrate the solution as appropriate to other environments.
    Will keep you all posted.
    Regards,
    Sharmila

  • Prevent AP Invoices being picked by POII (Payables Open Interface Import)

    Hi,
    We have a requirement to prevent the AP Invoices in Payable Open Interface table from being picked by POII (Payables Open Interface Import) program.
    Kindly provide your inputs on this.
    Thanks & Regard,
    Satvik Patel

    That is correct, the documentation does specify not to populate a value into this field, however there is no harm in doing so.
    Alternatively, if you are not using the Payables Open Interface Workflow, then you could either populate a value of "Y" or "S" into the WORKFLOW_FLAG column, to prevent the invoices from getting imported.
    Or you could just supply a dummy value for the org_id column in the interface table
    Edited by: pillair on Aug 1, 2012 1:10 AM

  • Prevent RCV Txn Processor from calling Payables Open Interface Import

    When we create ASBN and run Receiving Transaction Processor, it automatically inserts invoice data into AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE then triggers Payables Open Interface Import.
    We have tried to set PO: Create ASBN invoices using AP interface tables to No but this creates the invoice via API instead of via the interface. We would still like to use the interface but we need to call Payables Open Interface Import manually.
    How can we do this?
    Thanks in advance.
    Anna Fajardo

    That is correct, the documentation does specify not to populate a value into this field, however there is no harm in doing so.
    Alternatively, if you are not using the Payables Open Interface Workflow, then you could either populate a value of "Y" or "S" into the WORKFLOW_FLAG column, to prevent the invoices from getting imported.
    Or you could just supply a dummy value for the org_id column in the interface table
    Edited by: pillair on Aug 1, 2012 1:10 AM

  • Self-Assessed Tax Through Payables Open Interface Import

    Does anyone know what fields are required to process an invoice with use tax through the payable open interface import? We have a custom interface in 11i that loads these invoices and validates nightly. However, in R12 we are using E-Bus Tax engine to "manually" check the "Self Assess" while creating invoices. How can this same process be done through the import????????
    Edited by: user5893077 on Mar 2, 2011 3:50 PM

    Have you customized/setup the Project Accounting Workflow builder. You need to do some setup for this workflow builder so that the project accounts can be derived properly.

Maybe you are looking for