Purpose of AP_INTERFACE_CONTROLS in the payables open import program.

Hi,
Can anyone explain the purpose of the table AP_INTERFACE_CONTROLS in the payable open import program.
Regards
Deepak

Hello Deepak.
AP_INTERFACE_CONTROLS is a temporary table that holds control information about segregated data in the AP_INVOICES_INTERFACE table during the Payables Open Interface Import. The table ensures that each import must be unique with respect to the combination of SOURCE and GROUP_ID. This allows the submission of multiple imports at the same time.
Your Oracle Payables application deletes the information from this table when you complete an import.
Octavio

Similar Messages

Payables Open Interface Program Source Problem

Hello All,
I am trying to import invoice using "Payable Open Interface Program".
I have two Sources from which I am uploading invoices.
Lets say the Sources be A and B. (in the lookup code i have added A and B under Source lookup type).
Now the problem is Payables program is importing successfully for Source A and the program is erroring out for source B.
Can u suggest me what could be the problem here?
Is there any other setup required with respect to sources need to be done?
Thanks & Regards
Aboothahir

hello all,
I am able to upload the invoices now using both the sources.The problem was with source B i was not passing the group name. so i passed the group name and the records are getting uploaded.
thanks & regards
aboothahir

R12 Invoice Distributions not in table after Payable Open Interface Program

Hello,
I have inserted data in AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE and launched Payable Open Interface Program.
All my invoices has been successfully processed.
Just after completion of import program, i query an invoice on apps and all the Distribution lines are displayed when i click on "All Distribution" button BUT when i query the table AP_INVOICE_DISTRIBUTIONS_ALL by the invoice_id, no records are displayed.
Its only when i press the button save on Apps or when i validate the invoice that i can see records in the table AP_INVOICE_DISTRIBUTIONS.
Please help.. need to know where these lines are stored initially because i need to perform a post-import update on the attributes at INVOICE_DISTRIBUTION level.
thanks

I believe that is standard functionality. You can create a request set to run the Invoice Validation Program after your import is successfully done.
Carl Hammond had posted a similar one before. You can search the forum for that message, otherwise, he probably has the right answer.
Thanks
Nagamohan

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

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

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

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

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

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

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.

Mark Invoices as Paid through Payables Open Interface

Hi.
I have looked at the table definitions for importing invoices into Oracle Payables through the Payables Open Interface. It is clear to me how simply writing to these two tables: AP_INVOICES_INTERFACE and AP_INVOICES_LINES_INTERFACE.
However, the invoices that i want to import into Oracle have already been processed and paid. It seems that there is no way through these two tables to mark an invoice as Paid and pass in the associated the payment data (for example - a check number). I am retrieving data from an external invoice and payment processing web site and importing this into Oracle E-Business Suite through these two tables. So is there:
- A way to mark these invoices as Paid through the import and include the check number it was paid with?
- If not what is the best way to accomplish that in Oracle? Is there any other interface that Oracle provides that will allow this. Do I need to create some kind of routine or workflow in Oracle need to be created to do this? I am new to Oracle, so it is not clear at the moment.
Thanks!
Scott

Scott,
You cannot bring in paid invoices through payables open interface table.
This is one workaround you can use.
1. import the invoices through open interface, the interface record will be marked as Processed.
2. As soon as your invoice is created, your liability account will be hit and will be increased and cash account will be decreased (I m not using the credit/debit terms purposefully).
3. You then create a payment batch , and pay the invoice, this will balance the liability and cash accounts
This way you can simulate the payment you did outside the system and still your books will be in sync.
Things you would need to take care of:
1. Payment Dates
2. Stop the payment instrument (check/creditmemo/debitmemo) from going out
Lastly, this is a OAF forum, you might get better replies in AP or EBiz forums, so please post your query there.
Thanks
Tapash

Purpose of AP_INTERFACE_CONTROLS in the payables open import program.

Similar Messages

Maybe you are looking for