Api's for payables open interface

what are the API's that are used in payables open interface????

You can see details at
http://www.oracleappshub.com/account-payable/oracle-api-availability-oracle-payables-ap/

Similar Messages

  • Payables Open Interface Import pass distribution set for header?

    Hi all,
    i'm using OEBS 12.1.3. I want to insert data into payables interface tables to create invoice via back-end. Is it possible to pass data for the DISTRIBUTION SET on header level? I searched in the table AP_INVOICES_INTERFACE but no such column founded. I'm able to pass info for the distribution on the line level...
    Any ideas?
    Thanks in advance,
    Bahchevanov.

    The before report trigger error does occur for n number of reasons...some of the solutions could be
    1. Setting up the debug/summarized params to Y or
    2. Two payables open interface import programs running at the same time and due to non-incompatibility setups, one of them is getting errored out. Try setting up incompatibility and this error will go away - the only problem with this approach is that if this program needs to run on frequent basis, then one will wait on other to complete and consume lot of time.
    3. Try to increase threads of concurrent manager under which this program runs for better resouce management.
    4. Check the normal AP side setups such as tax code definition, supplier site 'pay site flag' etc --Although before report error occurs at the place in rdf where these checks are yet not done but thought to share with you if it helps
    Thanks
    Girish

  • APIS FOR RECEIVING OPEN INTERFACE

    Hi all,
    Can any one help me regarding APIS for receiving open interface for ASN(Advanc shipment notice)
    regards
    SREE

    For 11i, all public APIs are listed at http://irep.oracle.com
    For R12, use the Integration Responsibility responsibility to look up the APIs
    HTH
    Srini

  • 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

  • Facing an Issue with Payables Open Interface Import

    Hi
    I am facing an issue with the Payables Open Interface Import...
    My Requirement is:
    1. Need to upload the PO, Supplier, Invoice #, Invoice Date details to custom table (through web ADi)
    2. From custom table storing in the AP invoice interface tables.
    3. From Interface table, calling API (Payables Open Interface Import) which wil create the invoive (PO matched)
    Now, If user has given wrong data some reasons....Payables Open Interface Import has rejected that entry....user has checked this and corrected later and trying to create the same invoice with the correcte data....As there is a rejected a line exists on the Header interface, line interface...even though if he pass the correct data in the second time it is cosidering that rejected row and not processing the correct row...
    Can any one suggest on this...
    Regards,
    Bala

    When processing a record, you can check if another ap_invoice_interface record exists for the same invoice number and
    1) Delete the old record and then insert a new one
    OR
    2) Update the old record instead of creating a new one
    Hope this helps,
    Sandeep Gandhi

  • AP error while submitting "Payable Open interface"

    Hello,
    I am trying to run the request 'Payables open interface'. I got the output once and the error was because the supplier site was invalid. I created a supplier site saved it and ran the request again. Now, I am getting the following error.
    Payables: Version : 11.5.0 - Development
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    APXIIMPT module: Payables Open Interface Import
    Current system time is 21-JUN-2009 08:15:01
    +-----------------------------
    | Starting concurrent program execution...
    +-----------------------------
    Arguments
    p_source='SQLLDR'
    p_batch_name='N/A'
    p_purge_flag='N'
    p_trace_switch='N'
    p_debug_switch='N'
    p_summary_flag='N'
    p_commit_batch_size='1000'
    p_user_id='1007990'
    p_login_id='2532036'
    APPLLCSP Environment Variable set to :
    XML_REPORTS_XENVIRONMENT is :
    /u02/applmgr/lmtestora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb
    XENVIRONMENT is set to: /u02/applmgr/lmtestora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb
    Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
    American_America.UTF8
    Spawned Process 1752
    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.27.0 - Production on Sun Jun 21 08:15:02 2009
    (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 2776668.
    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
    I am trying this for first time. Any help is highly appreciated.
    Thanks.

    Hi,
    Please go through the following documents and see if it helps.
    Note: 107628.1- Payables Open Interface Invoice Import Troubleshooting Guide (APXIIMPT)
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=107628.1
    Note: 220355.1- APXIIMPT-Payables Open Interface Import Fails Rep-1419:'Beforereport' : Pl/Sql Program Aborted
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=220355.1
    Regards,
    Hussein

  • 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 Purge" Program

    Hi Guys,
    In our production system, it takes 3 minutes to open "Open Interface Invoices" form (AP Manager>Invoices>Entry>Open Interface Invoices). So what should we do so as to avoid this.
    I was thinking to delete data from two tables (AP_INVOICES_INTERFACE & AP_INVOICE_LINES_INTERFACE) based on certain crieterions. Like all the records which have been successfully imported i.e. with status='PROCESSED' can be deleted. So, I can achieve this using two methods:
    1. Manually using SQL Delete statement. i.e.
    DELETE FROM AP_INVOICES_INTERFACE WHERE status='PROCESSED';
    DELETE FROM AP_INVOICE_LINES_INTERFACE
    WHERE invoice_id IN (SELECT invoice_id FROM AP_INVOICES_INTERFACE WHERE status='PROCESSED');
    2. Or I can use "Payables Open Interface Purge" Program.
    I ran this program for my specific source, and checked the count from tables but the result is the same. This means this program has not deleted any of the processed records from these two tables for the particular source.
    What can be the reason for this? Please suggest me on this.
    Thanks a lot!
    Regards,
    Sumir Chawla

    Hi,
    Thanks for your reply friends!
    I ran the program for some source. It completed successfully, log shown below:
    MSG-00001: (Import_purge 1) Check control table for the purge process
    MSG-00001: (Check_control_table 1) Lock the control table
    MSG-00003: (Check_control_table 2) Fetch import_requests
    MSG-00007: (Check_control_table 5) Insert record into control table
    MSG-00008: (Check_control_table 6) Commit
    MSG-00002: (Import_purge ) Deleting records in interface tables...
    MSG-00008: (Import_purge 5) Commit to the database
    MSG-00010: (Import_purge 7) Delete the previous record in ap_interface_controls
    But when I checked both the tables ap_invoices_interface and ap_invoice_lines_interface from backend, the records which should not exist for that particular source and which imported successfully (as purge all is 'No') are still existing in the tables. If I am correct, after successfull run, records should not exist for the source which have status "processed". Please correct me if I am wrong. I think I should log SR.
    Thanks & Regards,
    Sumir Chawla

  • Payables Open Interface Purge completes with error "Invalid Cursor"

    Hello,
    I'm trying to run Payables Open Interface Purge (version 115.8) and get an invalid cursor error in the beforereport trigger. Does anyone know the cause and remedy of this? A portion of the log is below. I've looked at the cursor and everything looks fine to me.
    MSG-00001: (Import_purge 1) Check control table for the purge process
    MSG-00001: (Check_control_table 1) Lock the control table
    MSG-00003: (Check_control_table 2) Fetch import_requests
    MSG-00004: (Check_control_table 3) Check concurrent program status
    MSG-00999: FUNCTION GET_REQUEST_STATUS ERROR, Reason:
    MSG-00999: FND_CONCURRENT.GET_REQUEST_STATUS<-Check_control_table<-Import_purge<- Before report trigger <- APXIIPRG
    MSG-00999: check_control_table<-Import_purge<- Before report trigger <- APXIIPRG
    MSG-00999: (Import_purge 1) Check control table for the purge process
    MSG-00999: Delete record in control table..
    MSG-00999: ORA-01001: invalid cursor
    REP-1419: 'beforereport': PL/SQL program aborted.
    Thank you.

    I'm trying to run Payables Open Interface Purge (version 115.8) and get an invalid cursor error in the beforereport trigger. Does anyone know the cause and remedy of this? A portion of the log is below. I've looked at the cursor and everything looks fine to me.
    MSG-00001: (Import_purge 1) Check control table for the purge process
    MSG-00001: (Check_control_table 1) Lock the control table
    MSG-00003: (Check_control_table 2) Fetch import_requests
    MSG-00004: (Check_control_table 3) Check concurrent program status
    MSG-00999: FUNCTION GET_REQUEST_STATUS ERROR, Reason:
    MSG-00999: FND_CONCURRENT.GET_REQUEST_STATUS<-Check_control_table<-Import_purge<- Before report trigger <- APXIIPRG
    MSG-00999: check_control_table<-Import_purge<- Before report trigger <- APXIIPRG
    MSG-00999: (Import_purge 1) Check control table for the purge process
    MSG-00999: Delete record in control table..
    MSG-00999: ORA-01001: invalid cursor
    REP-1419: 'beforereport': PL/SQL program aborted.11i: Payables Open Interface Invoice Import Troubleshooting Guide (APXIIMPT) [ID 107628.1] -- 3. Open Interface Import Purge Fails with ORA-01001: Invalid Cursor
    Thanks,
    Hussein

  • Payables Open Interface Import

    Currently the AP folks run the 'Payables Open Interface Import' for certain types of source's.
    I am trying to run the 'Payables Open Interface Import' request for a newer source. I am getting the following error:
    REP-1419: 'beforereport': PL/SQL program aborted.
    My parameters are almost the same (only the source name and the batch name are different) as what the AP folks are using. Their requests completed successfully...mine did not. How would I know which part of the before report is causing it to fail?
    Thanks,
    Chiru

    The before report trigger error does occur for n number of reasons...some of the solutions could be
    1. Setting up the debug/summarized params to Y or
    2. Two payables open interface import programs running at the same time and due to non-incompatibility setups, one of them is getting errored out. Try setting up incompatibility and this error will go away - the only problem with this approach is that if this program needs to run on frequent basis, then one will wait on other to complete and consume lot of time.
    3. Try to increase threads of concurrent manager under which this program runs for better resouce management.
    4. Check the normal AP side setups such as tax code definition, supplier site 'pay site flag' etc --Although before report error occurs at the place in rdf where these checks are yet not done but thought to share with you if it helps
    Thanks
    Girish

  • Problem with payables open interface import-unable to pick invoice data

    Hi,
    I have put the Interface data in two staging table and then moved them to AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables.
    Code:
    insert into XXWU_AP_INVOICES_INTERFACE (
    invoice_id,
    invoice_num,
    vendor_id,
    vendor_site_id,
    vendor_site_code,
    invoice_amount,
    INVOICE_CURRENCY_CODE,
    invoice_date,
    DESCRIPTION,
    PAY_GROUP_LOOKUP_CODE,
    source,
    org_id,
    OPERATING_UNIT
    values (
    ap_invoices_interface_s.nextval,
    'INV345DJ',
    '3317',
    '14335',
    'ACH NY1',
    1200.00,
    'USD',
    to_date('01-31-2010','mm-dd-yyyy'),
    'This Invoice is created for test purpose',
    'WUFS SUPPLIER',
    'Manual Invoice Entry',
    81,
    'WU_USD_OU'
    insert into XXWU_AP_INVOICE_LN_INTERFACE (
    invoice_id,
    invoice_line_id,
    line_number,
    line_type_lookup_code,
    amount,
    org_id
    values (
    ap_invoices_interface_s.currval,
    ap_invoice_lines_interface_s.nextval,
    1,
    'ITEM',
    1200.00,
    81
    INSERT INTO AP_INVOICES_INTERFACE (SELECT * FROM XXWU_AP_INVOICES_INTERFACE);
    INSERT INTO AP_INVOICE_LINES_INTERFACE (SELECT * FROM XXWU_AP_INVOICE_LN_INTERFACE);
    I can very much see the data in Open Interface Invoices(Front End). But when I run the payables open interface import program with correct Operating Unit, Source and Batch Name, the program unable to pick the data from the interface tables and unable to create a invoice.
    Note:
    1] The program run successfully everytime, but there is no output in the output file.
    2] In the Log file One Message is there saying 'Zero(0) invoices were created during the process run.'
    3] All the initail setup is right, i think, because I ran the same program few days back and it was working fine and the invoices were created at that time. Now what is going wrong I am unable to figure it out.
    Please help ASAP.Thanks in Advance
    DJ Koch.
    Edited by: DJKOCH on 17 Aug, 2010 9:51 PM

    Can you run the program - Payables Open Interface Import with Debug mode set to Yes.
    Once the program completes sucessfully verify the log file of the program and try to find out if there are any invoices which is causing the exceptions.
    Also confirm that the invoices which are in the AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables are of the correct period in which you are trying to create the invoices.
    Hope this helps.
    Thanks and Regards
    Manish Jain.

  • Problem with Payables Open Interface Import

    We have a third party's software which uploads invoices into the OraFin's (11.5.9) AP_INVOICES_INTERFACE and AP INVOICES_LINES_INTERFACE tables. Then we run PAYABLES OPEN INTERFACE IMPORT PROGRAM, and Invoice_id in AP_INVOICES_ALL has different value then we just had before in interface tables.
    The sequence has replaced the Invoice_id with new one instead of just to transfer it to the base table (AP-Invoices_All) only.
    Is there any way to avoid the change of the given Invoice_id?
    Thanks for your prompt answer, Gurus :).

    The sequence has replaced the Invoice_id with new one instead of just to transfer it to the base table (AP-Invoices_All) only.Is there any way to avoid the change of the given Invoice_id?
    No.
    This is standard functionality. Invoice import program regenerates the invoice_id from sequence everytime the invoice is imported.
    Thanks
    Nagamohan

  • 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

  • Payables Open Interface failed-help plz.

    All,
    Version: 11.5.10.2
    The project is about integrating the legacy system with Oracle 11i. i.e we are importing invoices created in 3rd party appln and importing it to Oracle thru Payables Open interface. I'm stuck with 1 use case. i.e invoice against a PO having split accounting.
    scenario 1:
    1. created a PO in Oracle with 1 line having 2 distributions
    2. Against the same PO, invoice is created with for the same line item and imported to Oracle. I populated PO related info in PONumber,POLineNumber and POShipmentNum in the ap_invoice_lines_interface table.
    3. Payables OPen interface worked fine
    scenario 2:
    1. Against the same PO having split, created an invoice for the line item, this time I added a freight on to it.
    2. Concurrent failed(i.e it didnt throw any error to the ap rejections table),
    3. so i populated po_distribution_num to the ITEM line, and ran the concurrent again. It processed the invoice successfully.
    I've following queries:
    1. In the 1st scenario, without populating po_dist_num to the lines table, conc. processed the invoice successfully
    2. In the 2nd, only after populating the po_dist_num, the conc. processed it successfully
    3. In what scenario/test case, does the payables open interface expects po_dist_num?
    Please advise.
    Rgds,
    Sen

    All,
    Version: 11.5.10.2
    The project is about integrating the legacy system with Oracle 11i. i.e we are importing invoices created in 3rd party appln and importing it to Oracle thru Payables Open interface. I'm stuck with 1 use case. i.e invoice against a PO having split accounting.
    scenario 1:
    1. created a PO in Oracle with 1 line having 2 distributions
    2. Against the same PO, invoice is created with for the same line item and imported to Oracle. I populated PO related info in PONumber,POLineNumber and POShipmentNum in the ap_invoice_lines_interface table.
    3. Payables OPen interface worked fine
    scenario 2:
    1. Against the same PO having split, created an invoice for the line item, this time I added a freight on to it.
    2. Concurrent failed(i.e it didnt throw any error to the ap rejections table),
    3. so i populated po_distribution_num to the ITEM line, and ran the concurrent again. It processed the invoice successfully.
    I've following queries:
    1. In the 1st scenario, without populating po_dist_num to the lines table, conc. processed the invoice successfully
    2. In the 2nd, only after populating the po_dist_num, the conc. processed it successfully
    3. In what scenario/test case, does the payables open interface expects po_dist_num?
    Please advise.
    Rgds,
    Sen

  • 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

Maybe you are looking for