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

Similar Messages

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

  • 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

  • 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

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

  • 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

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

  • Payable Open Interface Import

    Hi All,
    I am trying to run payable open interface import program to upload 'STANDARD' invoice.Problem is that when i run 'PAYABLE OPEN INTERFACE IMPORT'
    program it fetch record from interface table, but does not create invoice in oracle and its also not showing the rejection reason in 'AP_INTERFACE_REJECTION'.
    I also found a doc regarding this issue on metalink with id 1139837.1 , but the solution in this doc is already working.
    Please let me know if you have a workaround.
    Oracle Version--R12.1.3
    Database Version--11g

    Hello
    Please elaborate on the solution
    I am facing the same issue with R12.1.3 and 11g database.
    I have checked the metalink note and that is not applicable to me as well.
    I have turned on the debug switch and yet the failed invoices don't appear on the rejection report
    Regards
    Ariv

  • JAEHYLEE  (R11i AP)   Payables Open Interface Import  REJECT CODE:NO TERMS

    Purpose
    Payables Open Interface Import REJECT CODE:NO TERMS
    Symptoms
    'EDI' Source로 invoice를 import할때 Payables Open Interface Import program 이 error로 종료된다
    정상적인 에러 No Terms로 출력이 되나 , 데이타 상에는 아무 이상이 없으며
    debug log file 의 reject code는 NO TERMS INFO라고 출력된다
    REJECT CODE:NO TERMS INFO
    CauseThe import program in procedure v_check_invalid_terms does not have exception handling. So, when ever it has exceptions like no_data_found or too_many_rows control was returning to the final exception block and the procedure was returning false to the calling procedure. Hence the error instead of Reject reason.
    Bug 4704918 - APXIIMPT DOESN'T REJECT INVOICES WITH INCONSISTENT TERMS.
    Solution
    AP.N이상에서 patch 4755024를 적용
    Please apply Patch 4755024 - 1OFF:4704918:AP.N:FP.G:11.5.10:APXIIMPT DOESN'T REJECT INVOICES
    Reference
    Note 359089.1

    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.

  • Error in Payables Open Interface Import

    Hi Experts,
    I am loading some Invoices through Payable Interface.
    I have populated data in both the interface table i.e. ap_invoices_interface and ap_invoice_lines_interface.
    when i run Payables Open Interface Import its giving me the below message and the status column in ap_invoice_interface showing 'REJECTED'
    Enter Password:
    REP-0004: Warning: Unable to open user preference file.
    MSG-00000: 0 invoice(s) were created during the process run
    MSG-00000: 6 invoice(s) were fetched during the process run
    MSG-00000: summarize flagN
    MSG-00883: After Repport Trigger: Setting the Org Context to Multiple
    The org_id in both the table are same.
    I dont understand what could be the error. Please help me in find out the solutions.
    Thanks,
    Atul

    What is your application release?
    I am loading some Invoices through Payable Interface.
    I have populated data in both the interface table i.e. ap_invoices_interface and ap_invoice_lines_interface.
    when i run Payables Open Interface Import its giving me the below message and the status column in ap_invoice_interface showing 'REJECTED'
    Enter Password:
    REP-0004: Warning: Unable to open user preference file.
    MSG-00000: 0 invoice(s) were created during the process run
    MSG-00000: 6 invoice(s) were fetched during the process run
    MSG-00000: summarize flagN
    MSG-00883: After Repport Trigger: Setting the Org Context to MultiplePlease see if (R12AP: Interface Does Not Copy The DFF Values From Lines To Distribution. [ID 1457398.1]) helps.
    Thanks,
    Hussein

  • Payables Open Interface Import rejection

    Hi All
    Encountered an issue with Payables Open Interface Import.
    An invoice is getting rejected with reason 'INVALID SUPPLIER'.
    I have imported invoices for the same supplier as part of data conversion.
    The only change in data as compared to the transactions that were successfully imported is the Payment method.
    It was CHECK/WIRE for imported invoices and it is Cash for the invoice I'm trying to import.
    Appreciate any info on this.
    We are on applications release R12.1.3
    I've reviewed the below notes and it doesn't cover my scenario
    R12: Master Note: APXIIMPT - Payables Open Interface Import - Functional Overview [ID 1311923.1]
    R12: Master Note: APXIIMPT - Payables Open Interface Import - Troubleshooting [ID 1311932.1]
    Regards
    Ariv

    you better make it active that supplier& Site level also check from front end(through supplier form, where ever inactive date is there pls remove and try to run open payable interface again)
    Thanks
    hari

  • 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

  • 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

Maybe you are looking for

  • Excise duty capture and posting..?

    Hi all Can anybody explain me about , excise invoice capture and posting .. What is capture and posting excise invoice in CIN..? 1.When we capture excise duty..? were it wil go 2.When we wil post the same..? were it wil go Thanks sap-mm

  • Runtime exeception after deploying PAR file in portal

    Hi , I am facing an issue during the deployment of PAR file in our  Quality portal. I have download the PAR file from the system-->import to the NWDS--> did the modification (only to the properties files as part of my requirement) -->Export as PAR fi

  • E mail facility for MIRO doc from R3 to mail server.

    Dear All, Is ther any E mail facility available for MIRO doc from R3 to mail server? I want to fire e mail for each MIRO document which is posted in SAP R3 with the detail of MIRO doc number & respective PO number to concern person. Thanks. Upesh.

  • The touch screen keyboard of my blackberry

    Recently the touch screen keyboard if my blackberry torch has stopped working when I close the my phone (slide close) and also the rotation that Blackberry torch does when you change the position of it isn't also work, I thought it was software probl

  • Does anyone have SNMP toolkit for labview software by viodia?

    I want the software called SNMP toolkit for Labview. I tried contacting the people of www.viodia.com, but none of them have replied so far.  If anyone has then please send me at [email protected] or [email protected] . Thanx Santosh Chavan IIT MADRAS