Invoice Import VS Payables Open Interface

I would like to know which is the best way to import invoice and what are the advantages and disadvange in each.
Regards
Chandrasekar

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

Similar Messages

  • Payable open interface import Issue!

    Hello:
    I want to insert the Debit Memo invoice type through Payable open interface import API, But Payable open interface import program throw the error named is Invalid Inv type lookup code.
    I read out the Oracle Paybales documentation, Oracle does not support the DEBIT invoice type it only supports Standard and Credit type.
    Is there any possibility can we insert the DEBIT type from Payable open interface import program?.
    Please reply me ASAP.
    Thank you.
    Zeeshan

    Thank you Sanjit!
    Sanjeet Can you tell me the steps of How to register my stored procedure in APPS and how can I set my concurrent request.
    Please I need a steps.
    Regards
    Zeeshan

  • 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

  • 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.

  • 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

  • How to create cross charge AP invoice through Payables Open Interface Import

    Hi,
    I am working on developing an AP invoice interface program for creating cross charge invoices in Oracle 11i.
    Cross charge invoice means the supplier & site is from operating unit A, but the costing should hit the project number in Operating unit B.
    The pa_projects_all.allow_cross_charge_flag for the project number is set to Y. I am using below scripts to enter data into the interface tables:
    <code>
    INSERT INTO ap_invoice_lines_interface
                               (invoice_id,
                                invoice_line_id, line_type_lookup_code,
                                amount, org_id,
                                last_update_date, last_updated_by,
                                creation_date, created_by,
                                project_id, task_id,
                                expenditure_type, expenditure_item_date,
                                expenditure_organization_id
                        VALUES (v_invoice_id,
                                ap_invoice_lines_interface_s.NEXTVAL, 'ITEM',
                                c_line.invoice_amount, v_org_id,
                                TRUNC (SYSDATE), fnd_global.user_id,
                                TRUNC (SYSDATE), fnd_global.user_id,
                                v_project_id, v_task_id,
                                v_expenditure_type, v_expenditure_item_date,
                                v_organization_id
    INSERT INTO ap_invoices_interface
                         (invoice_id, invoice_num, invoice_date,
                          gl_date, vendor_id, vendor_site_id,
                          invoice_amount, invoice_currency_code,
                          exchange_rate, exchange_rate_type, exchange_date,
                          terms_id, terms_date, payment_method_lookup_code,
                          pay_group_lookup_code, payment_currency_code,
                          last_update_date, last_updated_by, creation_date,
                          created_by, SOURCE, org_id
                  VALUES (v_invoice_id, c_head.invoice_num, c_head.invoice_date,
                          c_head.gl_date, v_vendor_id, v_vendor_site_id,
                          c_head.invoice_amount, c_head.invoice_currency,
                          v_rate, 'Corporate', c_head.invoice_date,
                          v_terms_id, TRUNC (SYSDATE), v_payment_method,
                          v_paygroup, c_head.payment_currency,
                          TRUNC (SYSDATE), fnd_global.user_id, TRUNC (SYSDATE),
                          fnd_global.user_id, 'CONCUR', v_org_id
    <code>
    After inserting data into the interface tables, I submitted the Payable Open Interface Import with correct source and the record fails with below errors:
    REASON                         DESCRIPTION
    Account Required             An account is required
    PA Flexbuild Failed          Project Flexbuilder failed with error
    The above inserts are working fine for same entity invoices.
    I am not sure what could be the error.
    Any help is greatly appreciated.
    Thanks
    Imran

    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.

  • 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

  • Loading bank accounts with invoices using Payables Open Interface Import

    Dear Gurus,
    We are on 11.5.10.2.
    We create invoices in the 3rd party system, then load them into oracle using payables open interface import process.
    When users create invoices, they choose Vendor and Site first. If the Vendor Site has multiple bank accounts assigned, users may select the one that is non-primary.
    When we load the invoices into Oracle, it finds the PRIMARY account for the particular vendor site, and assigns it to the invoice.
    Is it possible to load bank accounts assigned to invoices into Oracle AP?
    Many Thanks,
    Iana

    Hi,
    No issues for me on Payables Open Invoice Interface with 12.0.6 - and yes make sure you match up the invoice_id on invoice, lines interface tables.
    Regards,
    Gareth

  • Payables Open Interface Import program is not Importing the Invoices

    Hi All,
    We are trying to create new invoices (SUM_DIF) based on the Foreign currency gain/Loss amounts. But payables open interface import program is rejecting all invoices with the rejectionr code as "No Invoice Lines, Atleast one invoice line is required".
    But when we check in the interface tables we have invoices as well as the corresponding lines for those invoices. This issue is happening in 12.0.6
    Any one faced this similar issue earlier? Any help is highly appreciated.
    Thanks,
    Rama Krishna.

    Hi,
    No issues for me on Payables Open Invoice Interface with 12.0.6 - and yes make sure you match up the invoice_id on invoice, lines interface tables.
    Regards,
    Gareth

  • Facing issues in Payables Open Interface Import Program

    Hi,
    We have a requirement of calling Payables Open Interface Import Program from Pl/sql package.
    Invoices are getting created.
    But the issue is when we query our invoice from invoice workbench and we try to view  the record history (help->record history)
    We are getting the error as ‘fdxwho failed due to ORA-01403’.
    The code is
    l_num_req_id :=
                fnd_request.submit_request
                                          (application      => 'SQLAP',
                                           program          => 'APXIIMPT',
                                           argument1        => fnd_global.org_id,
                                           -- org_id
                                           argument2        =>l_chr_source, 
                                           -- Invoice source
                                           argument3        => NULL,
                                           argument4        => l_chr_batch_name,
                                           -- Batch Name
                                           argument5        => NULL,
                                           argument6        => NULL,
                                           --  Hold Raeson
                                           argument7        => NULL,    -- GL Date
                                           argument8        => 'N',
                                           argument9        => 'N',
                                           argument10       => 'N',
                                           argument11       => 'N',
                                           argument12       => '1000',
                                           argument13       => fnd_global.user_id,
                                           argument14       => fnd_global.login_id
    Regards
    Suresh

    Hi,
    Please review notes:
    APP-01564 ORA-01403 in FDXWHO In Any Payables Form (Doc ID 1077762.6)
    "APP-FND-01564 ORACLE error 1403 in fdxwho" in Record History (Doc ID 879528.1)
    Thanks &
    Best Regards,

  • Error when running Payables Open Interface Import

    Hi Experts,
    I need help. I'm facing a problem when run Payables open interface import. Before that, I was running same concurrent many times and the concurrent program is completed normal. But, when I try again I'm getting error. what exacly problem is? What should I do?
    arguments
    p_org_id='84'
    p_sources='manual invoice entry'
    p_batch_name='N/A,
    p_purge_flag='Y'
    p_trace_switch='N'
    p_debug_switch='Y'
    p_summary_flag='Y'
    p_commit_batch_size='1000'
    p_user_id='1110'
    p_login_id='75025'
    Current NLS_NUMERIC_CHARACTERS Envirotment Variables are :
    American_America.US7ASCII
    Enter Password:
    REP-0004 : Warning : Unable to open user preference file.
    MSG-00001 : (Before Report) After SRWINIT
    MSG-00002 : (Before Report) After Get_Company_Name
    MSG-00003 : (Before Report) After Get_NLS_Strings
    MSG-00001 : (Get Base Curr data 1) Get Base Currency Information
    MSG-00004 : (Before Report) After Get_Base_Curr_Data
    MSG-00005 : After Get Operating Unit
    MSG-00006 : After Get Purge Flag
    MSG-00002 : (Before Report Trigger 1) Import Invoices.
    MSG-00003 : (Before Report Trigger 3) Exception : When Others.
    REP-1419 : 'beforereport' : PL/SQL program aborted.
    REP-0069 : Internal Error
    REP-57054 : In-process job terminated: Terminated with error:
    REP-1419 : MSG-00001 : (Before Report) After SRWINIT
    MSG-00002 : (Before Report) After Get_Company_Name
    MSG-00003 : (Before Report) After Get_NLS_Strings
    MSG-00001 : (Get Base Curr data 1) Get Base Currency Information
    MSG-00004 : (Before Report) After Get_Base_Curr_Data
    MSG-00005 : After Get Operating Unit
    MSG-00006 : After Get Purge Flag
    MSG-00002 : (Before Report Trigger 1) Import Invoices.
    MSG-00003 : (Before Report Trigger
    Best Regards,
    Ade Hilman

    Hi Ade;
    Please check below note which is mention similar error
    Validate AAD fails with ORA-20001: -: XLA-95103: An internal error occurred. [ID 943024.1]
    Hope it helps
    Regard
    Helios

  • Payables Open Interface Import getting errors out

    Hello All,
    I am trying to run "Payables Open Interface Import" program to upload the invoice but the program is getting error out, in the log file at the end i am getting the below error:
    (Insert ap inv dists 1a) Inside the insert function
    (Insert ap inv dists 1) Insert into ap_invoice_distributions
    (Insert ap inv dists 1) Insert into ap_invoice_distributions
    ORA-00001: unique constraint (AP.AP_INVOICE_DISTRIBUTIONS_U1) violated
    Insert_ap_inv_dists<-Create_lines<-Import_invoices<- Before report trigger
    (Create Lines 22) Insert into ap_invoice_distributions
    create_non_item_lines<-Import_invoices<- Before report trigger
    Any one faced this kind of issue?
    any suggestions to resolve this.
    Thanks & Regards
    Aboothahir

    Pl post details of OS, database and EBS versions.
    Pl see these MOS Docs
    Payables Open Interface Error ORA-00001: unique constraint (AP.AP_INVOICE_DISTRIBUTIONS_U1) violated          (Doc ID 357784.1)
    APXIIMPT Payables Open Interface Import Fails ORA-00001          (Doc ID 353052.1)
    Unique Constraint Violated Importing Invoices With Multi Line Distribution Set          (Doc ID 386323.1)
    HTH
    Srini

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

Maybe you are looking for

  • 5800 freezes on start-up and doesn't recognise ser...

    hi, i have a 5800 XM which i got from vodafone last year.   I have a problem when starting up the phone.  First the vodafone start-up screen/symbol doesn't come up. then the phone manages to load the main screen but it has no vodafone symbol, no sign

  • SAP GUI 7.10 and ICH

    Hi all, Has anyone worked on SCM 5.0 - ICH using SAP GUI 7.10? With old version of SAP GUI, I am able to access the transactions of ICH, where as when I upgrade it t0 7.10, those transactions does not work. It says <b>".exe not found, use windows sea

  • Time Capsule, Time Machine, Lion, repeater.

    Need to upgrade home network for more space, longer range, upgrade to Lion. Have an existing router, Netgear, that does not reach all areas and devices. Would also like to set up a wireless backup for all computers on network. Of course we need to up

  • Use a JCA 1.5 Adapter with BPEL

    We have a JCA 1.5 adapter working with OC4J 10.1.3. Has someone an example how to use a JCA 1.5 adapter with the WSIF JCA binding in BPEL ?

  • Tables-Primary Key-Sequential read

    Hi Folks, Out of the following which imporves performace? 1.Using all the primary keys of a table in the where clause of a select statement? 2.Using any one or two (not all) primary keys of a table in the where clause of a select statement? Let me th