Ap_selected_invoices_all Payment_Priority

Hi All,
I am selecting payment_priority and one more column for check printing from table ap_selected_invoices_all. However this table does not return any record when I am paying single invoice thorugh Quick Pay. Please tell me which tables are populated for Quick Pay Payment process in R12.
Thanks

Hi Claire,
if my understanding for the question is correct: the following is the steps you need to perform to get the sequence_num(voucher numbering generated) in payables in sequential order:
1 Define Document sequence
Responsibility – System Administrator
Navigation - Application – Document - Define
2 Define Document Categories
Document Category - Payables
Responsibility – System Administrator
Navigation – Application – Document – Category
3) Assign document sequencing
3)Document Assignment -Payab;es
Responsibility – System Administrator
Navigation – Application – Document –Assign
4 Profile Option : Sequential Numbering - Always Used / Partial Used
Sequential Numbering – Payables
Responsibility – System Administrator
Navigation – Profile – System
The profile option name is Sequential Numbering
Please ignore the steps suggested if my understanding is wrong.
Thanks
Manish Jain.

Similar Messages

Hows is SEQUENCE_NUM derived in the AP_SELECTED_INVOICES_ALL

Hello,
Please can you advise how the SEQUENCE_NUM is derived in the AP_SELECTED_INVOICES_ALL table in Payables?
The Sequence Number is said to be the order in which Payables pays Supplier Invoices. How does payables decide on the order of payment?
I very much look forward to your response,
Kind Regards, Claire

Hi Claire,
if my understanding for the question is correct: the following is the steps you need to perform to get the sequence_num(voucher numbering generated) in payables in sequential order:
1 Define Document sequence
Responsibility – System Administrator
Navigation - Application – Document - Define
2 Define Document Categories
Document Category - Payables
Responsibility – System Administrator
Navigation – Application – Document – Category
3) Assign document sequencing
3)Document Assignment -Payab;es
Responsibility – System Administrator
Navigation – Application – Document –Assign
4 Profile Option : Sequential Numbering - Always Used / Partial Used
Sequential Numbering – Payables
Responsibility – System Administrator
Navigation – Profile – System
The profile option name is Sequential Numbering
Please ignore the steps suggested if my understanding is wrong.
Thanks
Manish Jain.

REJECT_CODE Vendor information and/or Operating Unit information is missing

hi
i am using Oracle Applications : 11.5.10.2.
i am trying to load suppliers and suppliers data into oracle AP.
i tried doing this with some sample data.
i executed the following code below :
insert into AP_SUPPLIERS_INT (VENDOR_INTERFACE_ID, VENDOR_NAME, SEGMENT1, STATUS)
values (*10006*,'XXX Financials2','199999','NEW');
i then ran the following process:
Supplier Open Interface Import
the supplier was added without errors
i then inserted a record into the
AP_SUPPLIER_SITES_INT table :
vendor_interface_id =*10006*,
LAST_UPDATE_DATE= SYSDATE,
LAST_UPDATED_BY          ='123',
VENDOR_SITE_CODE = 'true test' ,
CREATION_DATE     =SYSDATE ,
CREATED_BY     ='123' ,
PURCHASING_SITE_FLAG= 'N' ,
PAY_SITE_FLAG     = 'Y' ,
ATTENTION_AR_FLAG     = 'N' ,
ADDRESS_LINE1     ='gmmm df' ,
ADDRESS_LINE2     ='gmmm dfdv' ,
ADDRESS_LINE3     ='gmmm dfvdd' ,
ADDRESS_LINE4     ='gmmm dfvdd' ,
PAYMENT_METHOD_LOOKUP_CODE='Check' ,
TERMS_DATE_BASIS     ='Current' ,
ACCTS_PAY_CODE_COMBINATION_ID     = '1365' ,
PREPAY_CODE_COMBINATION_ID     = '1470' ,
PAYMENT_PRIORITY     = '99' ,
TERMS_ID= '10001' ,
INVOICE_AMOUNT_LIMIT =20,
PAY_DATE_BASIS_LOOKUP_CODE     = 'DISCOUNT' ,
ALWAYS_TAKE_DISC_FLAG= 'A' ,
INVOICE_CURRENCY_CODE     ='JMD' ,
PAYMENT_CURRENCY_CODE     ='JMD' ,
HOLD_ALL_PAYMENTS_FLAG='N' ,
HOLD_FUTURE_PAYMENTS_FLAG     ='N' ,
HOLD_UNMATCHED_INVOICES_FLAG= 'N' ,
EXCLUSIVE_PAYMENT_FLAG= 'N' ,
EXCLUDE_FREIGHT_FROM_DISCOUNT     = 'N' ,
ORG_ID= '142' ,
CREATE_DEBIT_MEMO_FLAG= 'N' ,
OFFSET_TAX_FLAG= 'N'
i then ran the following process:
Supplier Sites Open Interface Import
the process completes with a status of 'Normal'.
below is an extract of the output :
Supplier Sites Open Interface Import Execution Repor Page: 1
Import Options: All
Batch Size: 1000
Print Exceptions Only: No
Sites Open Interface Audit Report
Org Id Supplier Number Supplier Name Site Name
Total Sites Imported: 0
*** No Data Exists for this Report ***
Sites Open Interface Rejections Report
Org Id Supplier Number Supplier Name Site Name Reason
Total Sites Rejected: 0
when i checked the AP_SUPPLIER_SITES_INT table ,
the REJECT_CODE field has the value *'Vendor information and/or Operating Unit information is missing.'*
I THINK ALL THE REQUIRED FIELDS ARE POPULATED
why am i recieving this error ? is this caused by a bug? is there a required field that i didn't populated ?
please help me to solve this ....
thanks much!!

Hi,
Could you please check : Doc ID: 316368.1 of Metalink...
Symptoms_+
The Supplier Site Contacts Open Interface Import program is not importing certain contact
information.
The Supplier Site Contacts Open Interface Import Execution Report shows the following Rejection
Reason:
Vendor information and/or Operating Unit information is missing
Cause_+
The Last_name field is a required field.
As per the Oracle Payables User's Guide.
Appendix G-111
AP_SUP_SITE_CONTACT_INT chart shows the LAST_NAME is a Required field
Solution_+
As per the Oracle Payables User's Guide.
Appendix G-111
AP_SUP_SITE_CONTACT_INT chart shows the LAST_NAME is a Required field
If you test this out directly in the Suppliers window in Oracle Payables:
Navigation: Suppliers-Entry
Queried up a Supplier, then clicked into the Site field under the Contact tab.
Entered the contact information and omitted the Last Name, when trying to save the record,
the system gives the following message:
*'FRM-40202: Field must be entered' and the cursor is on the Last Name field. This is a required*
field and is the intended functionality.
Hope this will help
Regards,
S.P DASH

AP Payment Reprot

Dear All,
i need to include the check printing report at payment time, when user click the
option print now this report will be printed , how to connect this report to this
option in R12.
Thanks

Thank you very much for your help.
I did find the reports which run from the payment batch form.
And i also gathered a custom program which transfers the file from the standard out directory to the customized one.
But there has been some change in the requirements and instead of inserting the file into the database i am picking the data from ap_selected_invoice_checks_all and ap_selected_invoices_all and inserting into a staging table from where web-methods is going to pick data and send it across to other vendor for more processing.
I know that web-methods can spool the data from the staging table every few minutes but i was searching for some way to start the web-methods procedure from oracle. I know the communicating from web-methods to oracle is possible but i am not sure how to do it other way round that is from oracle to web-methods.
TIA,
Neelam

AP Payment Batch form

As per my understanding AP Payment Batch form generates a file with formated check layouts.This file is sent to the server.
I am supposed to store this file in the database.
Was going through the seeded APXPAWKB form couldn't find the code which generates this file.
Will it be possible for someone to throw some light here.
Do let me know incase more information is required.
Eagerly waiting to hear.
TIA,
Neelam

Thank you very much for your help.
I did find the reports which run from the payment batch form.
And i also gathered a custom program which transfers the file from the standard out directory to the customized one.
But there has been some change in the requirements and instead of inserting the file into the database i am picking the data from ap_selected_invoice_checks_all and ap_selected_invoices_all and inserting into a staging table from where web-methods is going to pick data and send it across to other vendor for more processing.
I know that web-methods can spool the data from the staging table every few minutes but i was searching for some way to start the web-methods procedure from oracle. I know the communicating from web-methods to oracle is possible but i am not sure how to do it other way round that is from oracle to web-methods.
TIA,
Neelam

Iby_ext_party_pmt_mthds is not being created from supplier open interface

In 11i payment method the PAYMENT_METHOD_LOOKUP_CODE was stored on the po_vendors record.this value could be retrieved by :
SELECT payment_method_lookup_code
INTO v_temp_look_up
FROM po.po_vendors
WHERE Trim(UPPER (vendor_name)) = Trim(UPPER (var_vendor_nm));
Sites record also had PAYMENT_METHOD_LOOKUP_CODE that could be retrieved by:
select pos.payment_method_lookup_code
INTO v_temp_look_up
from po_vendors po,PO_VENDOR_SITES_ALL pos
where po.vendor_id=pos.vendor_id
AND Vendor_site_Id=var_Vendor_site_Id ;
Some of our old custom applications however ONLY USE the PAYMENT_METHOD_LOOKUP_CODE from the po.po_vendors RECORD.
Hence upon completion of the SUPPLIER OPEN INTERFACE the PAYMENT_METHOD_LOOKUP_CODE would be accessible from the po.po_vendors record.
Now we are upgrading to R12.
I did some reading and realized that r12 PAYMENT_METHOD_LOOKUP_CODE
Is stored in IBY_EXTERNAL_PAYEES_ALL and iby_ext_party_pmt_mthds.
I loaded a vendor via the interface using:
INSERT INTO AP.AP_SUPPLIERS_INT
(VENDOR_INTERFACE_ID,
VENDOR_NAME,
SEGMENT1,
VENDOR_TYPE_LOOKUP_CODE,
TERMS_ID,
SET_OF_BOOKS_ID,
PAY_DATE_BASIS_LOOKUP_CODE,
PAY_GROUP_LOOKUP_CODE,
PAYMENT_PRIORITY,
INVOICE_CURRENCY_CODE,
PAYMENT_CURRENCY_CODE,
DISTRIBUTION_SET_ID ,
ACCTS_PAY_CODE_COMBINATION_ID ,
PREPAY_CODE_COMBINATION_ID,
PAYMENT_METHOD_LOOKUP_CODE ,
TERMS_DATE_BASIS ,
ATTRIBUTE_CATEGORY,
ATTRIBUTE1,
payment_method_code)
VALUES
VAR_VENDOR_INTERFACE_ID ,
SUP_VENDOR_NAME_var,
SUP_SEGMENT1_var,
Upper(Trim(VENDOR_TYPE_LOOKUP_CODE_var)),
10000 ,
2024 ,
SUP_PAY_DATE_BASIS_LOOKUP_CODE_var,
Upper(Trim(Nvl(PAY_GROUP_LOOKUP_CODE_var))) ,
SUP_PAYMENT_PRIORITY_var,
SUP_INVOICE_CURRENCY_CODE_var,
SUP_PAYMENT_CURRENCY_CODE_var,
SUP_DISTRIBUTION_SET_ID_var,
'3007',
'3007',
'EFT',
SUP_TERMS_DATE_BASIS_var,
SUP_ATTRIBUTE_CATEGORY_var,
SUP_ATTRIBUTE1_var ,
'EFT') ;
I ran the supplier interface and it completed successfully.
I ran the query for the supplier:
SELECT * FROM ap_suppliers WHERE VENDOR_NAME ='MARVEN, MARVEN'
AND VENDOR_ID='35425'
AND PARTY_ID ='47546' ;
This query returned the correct record.
I then ran another query to get the iby_ext_party_pmt_mthds for the SUPPLIER.
SELECT * FROM iby_ext_party_pmt_mthds
WHERE ext_pmt_party_id IN (
SELECT EXT_PAYEE_ID FROM IBY_EXTERNAL_PAYEES_ALL
WHERE PAYEE_PARTY_ID='47546'
BUT IT DID NOT RETURN ANY VALUE!!!
I logged into the oracle payables and then went to the suppliers screen.
I then clicked the Payment Details link. Under the Payment Method section none of the payment methods were selected !
I checked the ‘Wire’ Payment method and saved.
I then ran the query :
I then ran another query to get the iby_ext_party_pmt_mthds for the SUPPLIER.
SELECT * FROM iby_ext_party_pmt_mthds
WHERE ext_pmt_party_id IN (
SELECT EXT_PAYEE_ID FROM IBY_EXTERNAL_PAYEES_ALL
WHERE PAYEE_PARTY_ID='47546'
And it returned the correct row.
Now I would like to know
Why is the iby_ext_party_pmt_mthds record was not created from the supplier open interface seeing that I specified a value (‘EFT’) for the payment method for the supplier?
kindly help...thanks in advance

It looks like the final answer is, I had it configured correctly. The problem I encountered was my testing of the signature. I assumed I could control the interval that was used to track the failed attempts.
I never found a way to do that and I can't find any documentation that tells me what the interval is. It is fairly small because I couldn't key in 3 failed attempts fast enough to trigger the deny action. A little patience and a scripted attack hit my server and it banned it every hour. All 3 attempts are hitting in < one second.
Signature statistics [process switch:fast switch]
signature 2157:2: packets checked [0:1] alarmed [0:0] dropped [0:0]
signature 2157:1: packets checked [0:19] alarmed [0:0] dropped [0:0]
signature 3106:0: packets checked [0:83] alarmed [0:0] dropped [0:0]
signature 3109:0: packets checked [0:10] alarmed [0:10] dropped [0:0]
signature 6250:0: packets checked [31:0] alarmed [10:0] dropped [0:0]
deny acl's created 10
signature 6056:0: packets checked [1:0] alarmed [1:0] dropped [0:0]
Interfaces configured for ips 1

Not being remove Blank space in Supplier Name

Dear,
Actully we have round more than 200 supplier having supplier name with space due to this client face problem especially in parameter while running reprots or sometime occur in oracle application, therefor i have developed this routine to remove space from the left & right side of suppliername, but not being update although some update get performed when package execute showig status sucessfull & error is blank as mentioned below.
If any know about to update supplier name in Fron-End, right now we update supplier name but it's not wokrin could y please guide how can we upadate supplier name individulay so we can do it fron-end as per needed.
DBMS_OUTPUT.PUT_LINE(' STATUS '||v_return_status||' ERROR '||v_error_msg);
STATUS S ERROR
declare
v_return_status varchar2(100); --OUT NOCOPY VARCHAR2,
v_error_msg varchar2(100); --OUT NOCOPY VARCHAR2);
begin
for i in (
select s.*,par.jgzz_fiscal_code,par.sic_code,par.tax_reference,par.tax_name From ap_suppliers s,hz_parties par
where ltrim(rtrim(s.vendor_name)) <> s.vendor_name
and s.vendor_name = par.party_name
and created_by_module = 'AP_SUPPLIERS_API'
and vendor_name = 'ABC ' ) loop
v_return_status := null;
v_error_msg := null;
POS_VENDOR_PUB_PKG.Update_Vendor
p_vendor_id => i.vendor_id ,
p_segment1 => i.segment1 ,
p_vendor_name => ltrim(rtrim(i.vendor_name)),
p_vendor_name_alt => i.vendor_name_alt ,
p_summary_flag => i.summary_flag ,
p_enabled_flag => i.enabled_flag ,
p_segment2 => i.segment2 ,
p_segment3 => i.segment3 ,
p_segment4 => i.segment4 ,
p_segment5 => i.segment5 ,
p_employee_id => i.employee_id ,
p_vendor_type_lookup_code => i.vendor_type_lookup_code ,
p_customer_num => i.customer_num ,
p_one_time_flag => i.one_time_flag ,
p_parent_vendor_id => i.parent_vendor_id ,
p_min_order_amount => i.min_order_amount ,
p_terms_id => i.terms_id ,
p_set_of_books_id => i.set_of_books_id ,
p_always_take_disc_flag => i.always_take_disc_flag ,
p_pay_date_basis_lookup_code => i.pay_date_basis_lookup_code ,
p_pay_group_lookup_code => i.pay_group_lookup_code ,
p_payment_priority => i.payment_priority ,
p_invoice_currency_code => i.invoice_currency_code ,
p_payment_currency_code => i.payment_currency_code ,
p_invoice_amount_limit => i.invoice_amount_limit ,
p_hold_all_payments_flag => i.hold_all_payments_flag ,
p_hold_future_payments_flag => i.hold_future_payments_flag ,
p_hold_reason => i.hold_reason ,
p_type_1099 => i.type_1099 ,
p_withhold_status_lookup_code => i.withholding_status_lookup_code ,
p_withholding_start_date => i.withholding_start_date ,
p_org_type_lookup_code => i.organization_type_lookup_code ,
p_start_date_active => i.start_date_active ,
p_end_date_active => i.end_date_active ,
p_minority_group_lookup_code => i.minority_group_lookup_code ,
p_women_owned_flag => i.women_owned_flag ,
p_small_business_flag => i.small_business_flag ,
p_hold_flag => i.hold_flag ,
p_purchasing_hold_reason => i.purchasing_hold_reason ,
p_hold_by => i.hold_by ,
p_hold_date => i.hold_date ,
p_terms_date_basis => i.terms_date_basis ,
p_inspection_required_flag => i.inspection_required_flag ,
p_receipt_required_flag => i.receipt_required_flag ,
p_qty_rcv_tolerance => i.qty_rcv_tolerance ,
p_qty_rcv_exception_code => i.qty_rcv_exception_code ,
p_enforce_ship_to_loc_code => i.enforce_ship_to_location_code ,
p_days_early_receipt_allowed => i.days_early_receipt_allowed ,
p_days_late_receipt_allowed => i.days_late_receipt_allowed ,
p_receipt_days_exception_code => i.receipt_days_exception_code ,
p_receiving_routing_id => i.receiving_routing_id ,
p_allow_substi_receipts_flag => i.allow_substitute_receipts_flag ,
p_allow_unorder_receipts_flag => i.allow_unordered_receipts_flag ,
p_hold_unmatched_invoices_flag => i.hold_unmatched_invoices_flag ,
p_tax_verification_date => i.tax_verification_date ,
p_name_control => i.name_control ,
p_state_reportable_flag => i.state_reportable_flag ,
p_federal_reportable_flag => i.federal_reportable_flag ,
p_attribute_category => i.attribute_category ,
p_attribute1 => i.attribute1 ,
p_attribute2 => i.attribute2 ,
p_attribute3 => i.attribute3 ,
p_attribute4 => i.attribute4 ,
p_attribute5 => i.attribute5 ,
p_attribute6 => i.attribute6 ,
p_attribute7 => i.attribute7 ,
p_attribute8 => i.attribute8 ,
p_attribute9 => i.attribute9 ,
p_attribute10 => i.attribute10 ,
p_attribute11 => i.attribute11 ,
p_attribute12 => i.attribute12 ,
p_attribute13 => i.attribute13 ,
p_attribute14 => i.attribute14 ,
p_attribute15 => i.attribute15 ,
p_auto_calculate_interest_flag => i.auto_calculate_interest_flag ,
p_validation_number => i.validation_number ,
p_tax_reporting_name => i.tax_reporting_name ,
p_check_digits => i.check_digits ,
p_allow_awt_flag => i.allow_awt_flag ,
p_awt_group_id => i.awt_group_id ,
p_pay_awt_group_id => i.pay_awt_group_id ,
p_awt_group_name => null ,
p_pay_awt_group_name => NULL ,
p_global_attribute1 => i.global_attribute1 ,
p_global_attribute2 => i.global_attribute2 ,
p_global_attribute3 => i.global_attribute3 ,
p_global_attribute4 => i.global_attribute4 ,
p_global_attribute5 => i.global_attribute5 ,
p_global_attribute6 => i.global_attribute6 ,
p_global_attribute7 => i.global_attribute7 ,
p_global_attribute8 => i.global_attribute8 ,
p_global_attribute9 => i.global_attribute9,
p_global_attribute10 => i.global_attribute10 ,
p_global_attribute11 => i.global_attribute11 ,
p_global_attribute12 => i.global_attribute12 ,
p_global_attribute13 => i.global_attribute13 ,
p_global_attribute14 => i.global_attribute14 ,
p_global_attribute15 => i.global_attribute15 ,
p_global_attribute16 => i.global_attribute16 ,
p_global_attribute17 => i.global_attribute17 ,
p_global_attribute18 => i.global_attribute18 ,
p_global_attribute19 => i.global_attribute19 ,
p_global_attribute20 => i.global_attribute20 ,
p_global_attribute_category => i.global_attribute_category ,
p_bank_charge_bearer => i.bank_charge_bearer ,
p_bank_branch_type => i.bank_branch_type,
p_match_option => i.match_option ,
p_create_debit_memo_flag => i.create_debit_memo_flag ,
p_party_id => 2085 ,
p_parent_party_id => i.parent_party_id ,
p_jgzz_fiscal_code => i.jgzz_fiscal_code,
p_sic_code => i.sic_code ,
p_tax_reference => i.tax_reference,
p_inventory_organization_id => NULL ,
p_terms_name => NULL ,
p_default_terms_id => NULL ,
p_ni_number => NULL ,
p_last_update_date => NULL ,
x_return_status => v_return_status,
x_error_msg => v_error_msg
DBMS_OUTPUT.PUT_LINE(' STATU S '||v_return_status||' ERROR '||v_error_msg);
end loop;
end;
Edited by: oracle0282 on Dec 24, 2011 3:36 AM
Edited by: oracle0282 on Dec 25, 2011 9:51 PM

Just a thought..
How about creating a new supplier and then opt for Supplier Merge?
Using supplier merge you may transfer all the open PO's and invoices of the old supplier to the new
supplier. By using the supplier merge, the old supplier would be end date automatically by the
system.
P.S. I am NOT sure whether there exist a datafix to edit the supplier name.
Regards,
Srini

UPGRADE 1103 to 1159 - PAYMENTS CONVERSION QUESTION!

Hello,
UPGRADE 1103 to 1159 - PAYMENTS CONVERSION QUESTION!
This is the scenario, we are planning to do. Currently we have 11.0.3 in one box. We are planning for re-implementation for 11.5.9 in the new box. So we
have to convert approx 14 months of open and closed data for the historic purposes. (Like PO's, Invoices, Payments and ledger data etc.)
Again, these conversions cannot be handled through the front end using some Data Loader kind of tool etc...
Data Loader tool, I used a lot for loading Flexfield Value Set Values, Category Codes etc...
But my question is converting these AP_PAYMENTS related data in the back end. (Like Check num, Payment Batch ID, Invoice Number, Invoice ID, Supplier Number,
Supplier ID, etc.) from old 11.0.3 box to new 11i box.
Since there was some confusion is going on with Payments related areas, because there was now API's etc... some of them are telling it is very difficult to migrate "AS IS" into 11i. I also heard that oracle won't support this.
Just want to clarify clearly on this issues.
Because we are moving from the small box of 11.0.3 into Big box for 11.5.9. So we don't want to loose all the histories for about 20 months. especially open
Closed / Open - Invoices, Payments, PO's, REQ's, Active Items which are in the Open Blanket PO's, Employees, etc...
Of all these everything sounds like doable because they do have API's etc... Of course, I belive there is no API for the Vendors only. We want to know is this true for the Payments also.
Any urgent clarifications is very much appreciated with clear explanation.
Thanks in advance
Mani Varadan

The payment conversion is little bit tricky in term on its understanding and functionality.
There are lot of dependices of payments conversion on the others objects like invoice.
You need to be very clear in requirements.
Here is the extracted documents for giving you clear understanding about payments.
Overview of Process
Prior to creating a payment batch, four setup are required.
A.Define a bank for bank branches with which you do business.
B.Define bank accounts.
C.Choose a predefined or custom payment format.
D.Finally, define payment documents for disbursements for each bank account.
To give an overview of the steps required to create payment batch payments:
1) Initiate the payment batch by entering the criteria for invoices you want to pay. The payment batch process selects invoices, and then builds the payments. It determines which invoices will be paid on each payment document, and lists this information for you on the Preliminary Payment Register.
2) Make any necessary modifications to your payment batch, such as selecting additional invoices, deselecting invoices, deselecting suppliers, etc. Once modifications are complete, the modify payment batch process automatically builds the payments if any invoices were added.
3) Format payments to produce an output file.
4) Print checks from the output file if you are not creating electronic payments or sending the output file to a third party for printing.
5) Confirm the payment batch by recording the document numbers associated with each payment. During this step, the invoice status is updated to Paid and a document number is associated with the invoice and invoice payment.
As conversion(from 11.0.3 to 11.5.9) is concern step 3,4 is excluded from the standard processes.
These are the tables involved during the payment conversion.
AP_SELECTED_INVOICES_ALL
AP_INV_SELECTION_CRITERIA_ALL
AP_INVOICES_ALL
AP_PAYMENT_SCHEDULES_ALL
These are background (concurrent) processes involved in batch process consists of the following
a. Autoselect
b. Build Payments
c. Preliminary Payment Register
d. Format
e. Confirm
f. Final Payment Register.
10.7:
If you are using the application in character mode, navigate to the Reset Payment Batch form. The navigation path is
\Navigate --> Controls --> Payment --> ResetPaymentBatch.
Select the payment batch name and the system displays the status of the batch. Your options for proceeding vary according to the batch status.
11.5.8/9
You can perform actions on your batch in Payment Batches form by clicking on the Actions button. The appropriate actions are highlighted depending on the status of the batch.
THIS SECTION TALK ABOUT THE DETAIL TECHNICAL OVERVIEW
Payment Conversion Technical Overview
For the conversion is concern we are following four-step process
I.Defined and prerequisite steps as discussed above
II.Selecting the Invoice
III.Building the Payment
IV.Confirm
THESE ARE THE PREREQUISITE SETUP
We are assuming the bank set is already done from 10.7 to 11i.Bank set up means bank account id, and its corresponding payment format.
For this purpose we are using mapping function for bank account id and on that basis we are getting corresponding checks stock id.This means defining a payment documents for disbursements
SELECT INVOICES
When a payment batch is started one row for each record is created in the
AP_INV_SELECTION_CRITERIA_ALL table.
This table stores the criteria that a payment batch uses to select invoices for payments. The module name for the Auto Select process is APXPBSEL. The Select Invoices, or AutoSelect, is the first step in the payment batch process.
When we run a concurrent program the AutoSelect process starts by loading records that meet the invoice selection criteria into the table AP_SELECTED_INVOICES_ALL from the tables AP_INVOICES_ALL and AP_PAYMENT_SCHEDULES_ALL.
The criteria that AutoSelect uses to determine which record to select from AP_INVOICES_ALL and AP_PAYMENT_SCHEDULES_ALL is stored in AP_INV_SELECTION_CRITERIA_ALL.
To be sure that no duplicate invoices get selected, invoices that are already selected in another payment batch are not selected. Invoice payments that have no remaining payment amounts are not selected either.
BUILD PAYMENTS
The module name for the Build Program is APXPBBLD. From the list created by AutoSelect, the Build program determines which invoices will be paid on each
Payment document, and lists this information on the Preliminary Payment Register if Selected. The Build program is spawned when AutoSelect has completed. When the Build Program starts, the application uses information from the table AP_SELECTED_INVOICES_ALL to create rows in the table AP_SELECTED_INVOICE_CHECKS_ALL.
In addition to creating rows in the AP_SELECTED_INVOICE_CHECKS_ALL, the build payments program also performs the following tasks:
Assigns document numbers for payments
Assigns Check Ids
Renumbers the remaining documents starting from the first_available_document
Updates the payment batch status to BUILT
Since we are doing conversion from 10.7 to 11i where all payments need to converted hence we are keeping payment batch status as FORMATTED
CONFIRM
This is the final step for the payment batch process, where we will pick a payment batch from front end, and then making confirm. The menu for this
AP Payable =>Payment Batches form =>by clicking on the Actions button
Internally the confirm program first updates the AP_SELECTED_INVOICE_CHECKS_ALL records,
then transfers those records to
AP_CHECKS_ALL.
In addition, the AP_SELECTED_INVOICES_ALL
records are transferred into the corresponding
AP_INVOICE_PAYMENTS_ALL,
AP_INVOICES_ALL and
AP_PAYMENT_SCHEDULES_ALL.
Table Involved in Payment Batch Process
These are the various table involved in the payment process of 10.7 and 11i.It is recommended that if corresponding earlier conversion is done then use the mapping function to get the new value.
oAP_SELECTED_INVOICES_ALL
oAP_INV_SELECTION_CRITERIA_ALL
oAP_INVOICES_ALL
oAP_PAYMENT_SCHEDULES_ALL
oAP_SELECTED_INVOICE_CHECKS_ALL
oAP_CHECKS_ALL
oAP_INVOICE_PAYMENTS_ALL
oAP_PAYMENT_SCHEDULES_ALL
oAP_INVOICES_ALL
oAP_BANK_ACCOUNTS_ALL `
Common Issue:
1.Determine the status of the Payment Batch?
A: Query up the Payment Batch in the Payment Batches Summary window to view the status. If you can not get into the application, you can select the status from SQL*Plus:
SELECT status FROM ap_inv_selection_criteria_all
WHERE checkrun_name = ?<payment batch name>?;
2. Dont change the last update date
We are doing the conversion for payments, hence we cant change he last_updated_date to sysdate as this will create a problem by concurrent program, in that case we need to populate the field for FUTURE_DATED_PAYMENT=N
3. dont populate the value for INVOICE_PAYMENT_TYPE
If there are some prepayments in the conversion process donor populate this field and pass NULL, otherwise this will create a duplicate invoice, which will cause a problem for concurrent batch for payment.
Hope now you will be very clear about the process.
let me me offline, if you need further.
regards
sanjit
[email protected]

Invoice Document sequence generated repeatedly

1. At the time of booking invoice and saving invoice document no generated for example :-2045546
and then while clicking the distribution line it show the following error.
APP-SQLAP-1000: ORA-01403: no data found oocured in
AP_CREATE_PAY_SCHEDS_PKG.AP_Create_form_Terms<- AP_INVOICES_POST_PROCESS_PKG.
insert_children<-APXINWKB with parameters(invoice_id=56293,Terms_id=
Last_Updated_By=, Created_By=,Payment_Priority=99,Batch_id=,Terms_date=
Invoice_Amount=,Amount_for_discount=,Payment_Method=,Currency=)
While Performing the following operation:
2. After clicking ok on that error it gives us the another new document no for the same invoice for example :-2045552
3.This process continues and giving us the new document no for the same invoice until we close the oracle system itself.
Please provide the way to resolved error.
Regards
Nitin

Is this an E-Business Suite question? You may want to try out that area on the forums: E-Business Suite

IBY_PAYMENTA_ALL.PAYMENT_REFERENCE_NUMBER

Hello,
Not sure if anyone has the answer for this.
In 11i when the batch is submitted and failed for validation the ap_selected_invoice_checks_all.check_number has a value, in R12 what I understood is this table is obsolete.
Instead I am using iby_payments_all.payment_reference_number but this column is empty when Payment Process Request fails validation and also I don't see any data in ap_selected_invoices_all.pay_selected_check_id or print_selected_check_id for the given checkrun_name which is same as my PaymentProcessRequest Name.
Any idea if this is driven by a setup in R12? like payment method at the invoice level has to be Check instead of Wire? etc..

Hey Gordon,
I think this is the system behaviour.
I found out that the new document setting will based on the last document before you close the windows.
Let's say when I close the window, the documet is showing the BP Reference Number, then the new or next document will show the BP Reference Number also.
On the other hand, if I open a document without the BP Ref. Number, and close it, the new or next document will not show the BP Ref. Number.
So should I say that, the system will record the last view we have?
Hope my explaination is clear.
Thank you.
Regards,
Wai Leng

After Update Trigger not triggering for first update

Hi All,
I have written a Trigger on AP_SUPPLIERS table to update AP_SUPPLIER_SITES_ALL when payment priority gets updated on AP_SUPPLIERS table. Trigger calls a pragma autonomous procedure after update happens, and updates sites table. We are on R12 (12.1.3) with DB 11.2.0.3.0
Somehow this is not working for the first update, after that for every update it is working. Any idea why this might be happening?
Trigger Code:
CREATE OR REPLACE TRIGGER XX_AP_SUPPLIER_SIT_UPD_SYNC
AFTER UPDATE
ON AP.AP_SUPPLIERS
REFERENCING NEW AS NEW OLD AS OLD
FOR EACH ROW
DECLARE
l_vendor_id     NUMBER;
l_paym_priority NUMBER;
BEGIN
   XX_AP_SUPSITE_UPDATE(:NEW.PAYMENT_PRIORITY, :NEW.VENDOR_ID);
   EXCEPTION
     WHEN OTHERS THEN
       RAISE;
END XX_AP_SUPPLIER_SIT_UPD_SYNC;
Procedure Code:
CREATE OR REPLACE PROCEDURE APPS.XX_AP_SUPSITE_UPDATE (p_payment_priority IN NUMBER,p_vendor_id IN NUMBER) AS
PRAGMA AUTONOMOUS_TRANSACTION;
ex_custom EXCEPTION;
PRAGMA EXCEPTION_INIT( ex_custom, -20001 );
BEGIN
UPDATE AP_SUPPLIER_SITES_ALL
SET PAYMENT_PRIORITY =p_payment_priority
WHERE VENDOR_ID = p_vendor_id;
COMMIT;
EXCEPTION
WHEN OTHERS THEN
    raise_application_error( -20001, 'Error while updating payment priority on Site '||SQLERRM );
END XX_AP_SUPSITE_UPDATE;

Thanks for your replies Saubhik/VT,
now my trigger is compiled. but is not triggering. pl help me to resolve .....
create or replace
TRIGGER AUDIT_DEV.trg2
AFTER DELETE OR UPDATE OF EMP_STATUS ON AUDIT_DEV.AUDIT_PERSONS
FOR EACH ROW
declare
OSUSER varchar2(30);
     MACHINE varchar2(30);
     logon_time date;
db_user varchar2(30);
USERNAME VARCHAR2(30);
EMP_USER_MODIFIED AUDIT_PERSONS.EMP_USER_MODIFIED%TYPE;
     EMP_DATE_MODIFIED AUDIT_PERSONS.EMP_DATE_MODIFIED%TYPE;
     EMP_SK AUDIT_PERSONS.EMP_SK%TYPE;
     EMP_ID AUDIT_PERSONS.EMP_ID%TYPE;
     EMP_NAME AUDIT_PERSONS.EMP_NAME%TYPE;
EMP_RESIGNATION_DATE AUDIT_PERSONS.EMP_RESIGNATION_DATE%TYPE;
BEGIN
select     username,osuser,machine,logon_time into db_user,osuser,machine,logon_time from v$session where sid=(select sid from v$mystat where rownum=1);
INSERT INTO AUDIT_DEV.AUDIT_PERSONS_LOG (EMP_USER_MODIFIED,EMP_DATE_MODIFIED,EMP_SK,EMP_ID,EMP_NAME,EMP_RESIGNATION_DATE,EMP_STATUS_OLD,EMP_STATUS_NEW,osuser,db_user,machine)
VALUES(EMP_USER_MODIFIED,EMP_DATE_MODIFIED,EMP_SK,EMP_ID,EMP_NAME,EMP_RESIGNATION_DATE,:old.EMP_status,:new.EMP_status,osuser,db_user,machine );
COMMIT;
END;
09:59:06 AUDIT_DEV@dev>UPDATE AUDIT_DEV.AUDIT_PERSONS SET EMP_STATUS='TEST' WHERE EMP_ID='4234';
EMP_STATUS
TEST
1 row selected.
Elapsed: 00:00:00.01
10:00:03 AUDIT_DEV@dev>commit;
Commit complete.
Elapsed: 00:00:00.01
10:00:17 AUDIT_DEV@dev>select * from AUDIT_persons_log;
no rows selected
Elapsed: 00:00:00.00
10:00:17 AUDIT_DEV@dev>
Edited by: Abk on Nov 4, 2010 10:42 AM

PAYMENT BATCH를 MANUAL하게 CANCEL 하는 SQL

제품 : FIN_AP
작성날짜 : 2004-05-17
PAYMENT BATCH를 MANUAL하게 CANCEL 하는 SQL
=====================================
PURPOSE
고객사에서 간혹 Payment Batch의 Status 가 Formatting, Confirming 으로
멈추어 있어서 고객이 다시 Cancel을 할 경우 Cancelling 상태로 머물면서 Payment Batch Request 가 진행이 되지 않을 경우가 있다. 이때 해당 Concurrent Request 는 취소하고 해당 Payment Batch에 대해서 Datafix Script 을 통하여 Status 를 Cancelled 로 변경할 수 있도록 한다.
Problem Description
Payment Batch Stauts 가 Cancelling 상태에서 변하지 않는다. Concurrent Request 는 끝나지 않고 계속 Hang 상태에 머물러 있다.
Workaround
Solution Description
다음 sql 문을 이용하여 직접 cancelled 상태로 변경한다.
1) DELETE from ap_checkrun_conc_processes_all
where checkrun_name = '<payment batch name>';
2) DELETE from ap_selected_invoices_all
where checkrun_name = '<payment batch name>';
3)     DELETE from ap_selected_invoice_checks_all
     where checkrun_name = '<payment batch name>';
4) DELETE from ap_checkrun_confirmations_all
where checkrun_name = '<payment batch name>';
5)     UPDATE ap_inv_selection_criteria_all
     SET status = 'CANCELED'
     where checkrun_name = '<payment batch name>';
status update 시 canceled 라고 반드시 입력해야 함에 주의한다.
CANCELLED 라고 L을 2번 입력하면 취소되었다고 인식 하지 않는다.
Reference Documents
143668.1

AP Supplier Contacts Interface

Hi to all.
Hi have some doubts for supplier conversion on R12. I need to convert Supplier, Supplier Sites and Supplier Contacts. For what I saw I can join the Supplier and Supplier Sites using the same SUPPLIER_INTERFACE_ID so the interface understand the supplier --> supplier site connection. I do not understand how to do the same association between supplier site and contacts. In AP_SUP_SITE_CONTACT_INT there is not a supplier site interface id, and if I populate it with vendor site code and organization id, the conversion of contact does not work because it ask for vendor_id. But I do not know the Vendor ID when I populate the interface!
Am I missing something?
Or should I do the conversion in Two step? First supplier and supplier site, and only after the contacts?
Please Kindly advise.

Hi, I managed to have it working. Probably I was missing the link with supplier site code. Btw the script is the following, if it can help
INSERT INTO AP_SUPPLIERS_INT
( VENDOR_INTERFACE_ID ,
SEGMENT1,
TERMS_NAME,
PAYMENT_PRIORITY ,
PAY_GROUP_LOOKUP_CODE,
VENDOR_NAME,
VENDOR_TYPE_LOOKUP_CODE,
STATUS )
values(AP_SUPPLIERS_INT_S.NEXTVAL, --VENDOR_INTERFACE_ID
'545456', --SEGMENT1,
-- 566, --EMPLOYEE_ID,
'IMMEDIATE', --TERMS_NAME,
1 , --PAYMENT_PRIORITY ,
'AAAA', --PAY_GROUP_LOOKUP_CODE,
'DUMMYCOMPANY', --VENDOR_NAME,
'COMPANY', --VENDOR_TYPE_LOOKUP_CODE,
'NEW' -- STATUS
COMMIT;
INSERT INTO AP_SUPPLIER_SITES_INT(
STATUS,
VENDOR_INTERFACE_ID, -- VENDOR_INTERFACE_ID,
VENDOR_SITE_INTERFACE_ID,
VENDOR_SITE_CODE,
ADDRESS_STYLE,
ADDRESS_LINE1,
ADDRESS_LINE2,
ADDRESS_LINE3,
CITY,
ZIP,
COUNTRY,
EMAIL_ADDRESS,
PAY_SITE_FLAG,
PURCHASING_SITE_FLAG,
--OPERATING_UNIT_NAME
ORG_ID)
values
'NEW',--STATUS
AP_SUPPLIERS_INT_S.CURRVAL ,--VENDOR_INTERFACE_ID
AP_SUPPLIER_SITES_INT_S.NEXTVAL,--VENDOR_SITE_INTERFACE_ID
'DUMMY SITE',--VENDOR_SITE_CODE
'NE',--ADDRESS_STYLE
'ADDRESS1',--ADDRESS_LINE1
'ADDRESS2',--ADDRESS_LINE2
'ADDRESS3',--ADDRESS_LINE3
'Anywhere',--CITY
'00100',--ZIP
'IT', ---COUNTRY
'[email protected]',--EMAIL_ADDRESS
'Y',--PAY_SITE
'Y', -- PURCHASING_SITE_FLAG
121 )--OPERATING_UNIT_ID
COMMIT;
INSERT INTO AP_SUP_SITE_CONTACT_INT (
VENDOR_INTERFACE_ID,
VENDOR_CONTACT_INTERFACE_ID,
VENDOR_SITE_CODE,
ORG_ID,
-- OPERATING_UNIT_NAME,
FIRST_NAME,
LAST_NAME,
PHONE,
EMAIL_ADDRESS)
VALUES (
AP_SUPPLIERS_INT_S.CURRVAL ,--VENDOR_INTERFACE_ID
AP_SUP_SITE_CONTACT_INT_S.NEXTVAL,
'DUMMY SITE',
121,
-- 'DUMMY OPERATING UNIT', --OPERATING_UNIT_NAME,
'JOE',
'DOE',
'555d-54',
'[email protected]')
COMMIT;

Remove an End_Date on a Vendor

Hi- I have a custome interface to do Supplier adds and updates in R12.
My issue is that once a update comes in for an already end_dated supplier, the customer wants the updates done, and the supplier reactivated.
I have no problem making the updates, but passing null into the API does nothing to remove the end_date on the supplier.
How can I do this? Is there an API to re-activate a supplier? Should I just pass in '31-DEC-4912' instead of null?

Hi Jason,
You can try this as well...
In Ap_VENDORS_PKG.updte_row look for end_date_active
     UPDATE po_vendors
          SET
          vendor_id               =     x_Vendor_Id,
          last_update_date          =     x_Last_Update_Date,
          last_updated_by               =     x_Last_Updated_By,
          vendor_name               =     x_Vendor_Name,
          segment1               =     x_Segment1,
          summary_flag               =     x_Summary_Flag,
          enabled_flag               =     x_Enabled_Flag,
          last_update_login          =     x_Last_Update_Login,
          employee_id               =     x_Employee_Id,
          validation_number          =     x_Validation_Number,
          vendor_type_lookup_code          =     x_Vendor_Type_Lookup_Code,
          customer_num               =     x_Customer_Num,
          one_time_flag               =     x_One_Time_Flag,
          parent_vendor_id          =      x_Parent_Vendor_Id,
          min_order_amount          =     x_Min_Order_Amount,
          ship_to_location_id          =     x_Ship_To_Location_Id,
          bill_to_location_id          =     x_Bill_To_Location_Id,
          ship_via_lookup_code          =     x_Ship_Via_Lookup_Code,
          freight_terms_lookup_code     =     x_Freight_Terms_Lookup_Code,
          fob_lookup_code               =     x_Fob_Lookup_Code,
          terms_id               =     x_Terms_Id,
          set_of_books_id               =     x_Set_Of_Books_Id,
          always_take_disc_flag          =     x_Always_Take_Disc_Flag,
          pay_date_basis_lookup_code     =     x_Pay_Date_Basis_Lookup_Code,
          pay_group_lookup_code          =     x_Pay_Group_Lookup_Code,
          payment_priority          =     x_Payment_Priority,
          invoice_currency_code          =     x_Invoice_Currency_Code,
          payment_currency_code          =     x_Payment_Currency_Code,
          invoice_amount_limit          =     x_Invoice_Amount_Limit,
          hold_all_payments_flag          =     x_Hold_All_Payments_Flag,
          hold_future_payments_flag     =     x_Hold_Future_Payments_Flag,
          hold_reason               =     x_Hold_Reason,
          distribution_set_id          =     x_Distribution_Set_Id,
          accts_pay_code_combination_id     =     x_Accts_Pay_CCID,
          future_dated_payment_ccid     =     x_Future_Dated_Payment_CCID,
          prepay_code_combination_id     =     x_Prepay_CCID,
--TIN          num_1099               =     x_Num_1099, bug5930700
--TIN Proj enter value for num_1099 field bug5930700
num_1099 =
          decode( UPPER(x_Vendor_Type_Lookup_Code),'EMPLOYEE',NULL,'CONTRACTOR',
               decode(x_Org_Type_Lookup_Code,'INDIVIDUAL',NULL
                                   ,'FOREIGN INDIVIDUAL',NULL
                                   ,'PARTNERSHIP',NULL
                                   ,'FOREIGN PARTNERSHIP',NULL
                                   ,x_Num_1099),
               x_Num_1099),
--TIN Proj enter value for individual_1099 field bug5930700
individual_1099 =
          decode( UPPER(x_Vendor_Type_Lookup_Code),'EMPLOYEE',NULL,'CONTRACTOR',
               decode(x_Org_Type_Lookup_Code,'INDIVIDUAL',x_Num_1099
                                   ,'FOREIGN INDIVIDUAL',x_Num_1099
                                   ,'PARTNERSHIP',x_Num_1099
               ,'FOREIGN PARTNERSHIP',x_Num_1099
,NULL),
               NULL),
          type_1099               =     x_Type_1099,
          withholding_status_lookup_code     =     x_withholding_stat_Lookup_Code,
          withholding_start_date          =     x_Withholding_Start_Date,
          organization_type_lookup_code     =     x_Org_Type_Lookup_Code,
          vat_code               =     x_Vat_Code,
          start_date_active          =     x_Start_Date_Active,
          end_date_active          =     x_End_Date_Active,
          qty_rcv_tolerance          =     x_Qty_Rcv_Tolerance,
          minority_group_lookup_code     =     x_Minority_Group_Lookup_Code,
          payment_method_lookup_code     =     x_Payment_Method_Lookup_Code,
          bank_account_name          =     x_Bank_Account_Name,
          bank_account_num          =     x_Bank_Account_Num,
          bank_num               =     x_Bank_Num,
          bank_account_type          =     x_Bank_Account_Type,
          women_owned_flag          =     x_Women_Owned_Flag,
          small_business_flag          =     x_Small_Business_Flag,
          standard_industry_class          =     x_Standard_Industry_Class,
          attribute_category          =     x_Attribute_Category,
          attribute1               =     x_Attribute1,
          attribute2               =     x_Attribute2,
          attribute3               =     x_Attribute3,
          attribute4               =     x_Attribute4,
          attribute5               =     x_Attribute5,
          hold_flag               =     x_Hold_Flag,
          purchasing_hold_reason          =     x_Purchasing_Hold_Reason,
          hold_by                    =     x_Hold_By,
          hold_date               =     x_Hold_Date,
          terms_date_basis          =     x_Terms_Date_Basis,
          price_tolerance               =     x_Price_Tolerance,
          attribute10               =     x_Attribute10,
          attribute11               =     x_Attribute11,
          attribute12               =     x_Attribute12,
          attribute13               =     x_Attribute13,
          attribute14               =     x_Attribute14,
          attribute15               =     x_Attribute15,
          attribute6               =     x_Attribute6,
          attribute7               =     x_Attribute7,
          attribute8               =     x_Attribute8,
          attribute9               =     x_Attribute9,
          days_early_receipt_allowed     =     x_Days_Early_Receipt_Allowed,
          days_late_receipt_allowed     =     x_Days_Late_Receipt_Allowed,
          enforce_ship_to_location_code     =     x_Enforce_Ship_To_Loc_Code,
          exclusive_payment_flag          =     x_Exclusive_Payment_Flag,
          federal_reportable_flag          =     x_Federal_Reportable_Flag,
          hold_unmatched_invoices_flag     =     x_Hold_Unmatched_Invoices_Flag,
          match_option               =     x_match_option,
          create_debit_memo_flag          =     x_create_debit_memo_flag,
          inspection_required_flag     =     x_Inspection_Required_Flag,
          receipt_required_flag          =     x_Receipt_Required_Flag,
          receiving_routing_id          =     x_Receiving_Routing_Id,
          state_reportable_flag          =     x_State_Reportable_Flag,
          tax_verification_date          =     x_Tax_Verification_Date,
          auto_calculate_interest_flag     =     x_Auto_Calculate_Interest_Flag,
          name_control               =     x_Name_Control,
          allow_substitute_receipts_flag     =     x_Allow_Subst_Receipts_Flag,
          allow_unordered_receipts_flag     =     x_Allow_Unord_Receipts_Flag,
          receipt_days_exception_code     =     x_Receipt_Days_Exception_Code,
          qty_rcv_exception_code          =     x_Qty_Rcv_Exception_Code,
          offset_tax_flag               =     x_Offset_Tax_Flag,
          exclude_freight_from_discount     =     x_Exclude_Freight_From_Disc,
          vat_registration_num          =     x_Vat_Registration_Num,
          tax_reporting_name          =     x_Tax_Reporting_Name,
          awt_group_id               =     x_Awt_Group_Id,
          check_digits               =     x_Check_Digits,
          bank_number               =     x_Bank_Number,
          allow_awt_flag               =     x_Allow_Awt_Flag,
          bank_branch_type          =     x_bank_branch_type,
          EDI_Payment_Method          =     x_EDI_Payment_Method,
          EDI_Payment_Format          =     x_EDI_Payment_Format,
          EDI_Remittance_Method          =     x_EDI_Remittance_Method,
          EDI_Remittance_Instruction     =     x_EDI_Remittance_Instruction,
          EDI_transaction_handling     =     x_EDI_transaction_handling,
          Auto_Tax_Calc_Flag          =     x_Auto_Tax_Calc_Flag,
          Auto_Tax_Calc_Override          =     x_Auto_Tax_Calc_Override,
          Amount_Includes_Tax_Flag     =     x_Amount_Includes_Tax_Flag,
          AP_Tax_Rounding_Rule          =     x_AP_Tax_Rounding_Rule,
          vendor_name_alt               =     x_Vendor_Name_Alt,
global_attribute_category = X_global_attribute_category,
global_attribute1 = X_global_attribute1,
global_attribute2 = X_global_attribute2,
global_attribute3 = X_global_attribute3,
global_attribute4 = X_global_attribute4,
global_attribute5 = X_global_attribute5,
global_attribute6 = X_global_attribute6,
global_attribute7 = X_global_attribute7,
global_attribute8 = X_global_attribute8,
global_attribute9 = X_global_attribute9,
global_attribute10 = X_global_attribute10,
global_attribute11 = X_global_attribute11,
global_attribute12 = X_global_attribute12,
global_attribute13 = X_global_attribute13,
global_attribute14 = X_global_attribute14,
global_attribute15 = X_global_attribute15,
global_attribute16 = X_global_attribute16,
global_attribute17 = X_global_attribute17,
global_attribute18 = X_global_attribute18,
global_attribute19 = X_global_attribute19,
global_attribute20 = X_global_attribute20,
bank_charge_bearer = X_Bank_Charge_Bearer
     WHERE     rowid = x_Rowid;
Hope this will help...
Regards,
S.P DASH

Payment Process Request(PPR) not selecting invoice which should be eligible

I am R12 (12.1.2), DB-11.2.0.1, Solaris 64 Bit.
The PPR process is not auto selecting some of the invoices for payment which should be eligible for selection. It was working fine before and stopped working now for some invoices.
We have seen this happening in the past also, and sometime the invoices start showing again with no particular changes.
I followed the first 12 step of the document "952763.1", but no luck.
If I go to PPR, the invoices are automatically going in tables AP_UNSELECTED_INVOICES_ALL. I mean, without unselecting them, they are automatically inserted into that table on each try.
Edited by: 985596 on Feb 1, 2013 8:31 AM

Hi,
Below are the reasons for PPR are not selecting the invoices.
1. The invoice should not be selected by any other PPR
Action: Using the aplist, confirm the checkrun_id is null in ap_payment_schedules_all.
2. The payment schedule's relevant date should be between the PPR's Pay From and Pay Through dates. The relevant date for selection can be either a discount date or the due date
(a) If the due date is between the pay from and pay through dates, the payment schedule will be eligible for selection regardless of the discount date.
Action: Find the due_date in ap_payment_schedules_all.
Find the pay_from_date and pay_thru_date in ap_inv_selection_criteria_all.
If the pay_from_date is null, just confirm the due_date is less than or equal to the pay_thru_date.
If the pay_from_date is not null, confirm the due_date is greater than or equal to the pay_from_date and the due_date is less than or equal to the pay_thru_date.
If this test passes, skip to Step 3.
(b) If the due_date doesn't fall within the parameters, we must rely on the discount date(s). However, this is only available when pay_only_when_due_flag is not Y
Action: Check the pay_only_when_due_flag in ap_inv_selection_criteria_all.
If this is Y, the payment schedule did not fall within the required date parameters and was not selected for that reason.
If it is null or N, continue to the next step.
(c) Determine the relevant discount date.
Action: Confirm the pay_date_basis_lookup_code in ap_supplier_sites_all is discount.
If not, the invoice won't be selected.
See if the always_take_disc_flag in ap_supplier_sites_all is Y.
If yes, then the relevant date is the discount_date from ap_payment_schedules_all.
If no, then find the check_date from ap_inv_selection_criteria_all.
Make the following comparisons and take the date from the first one that is true.
If the check_date is on or before discount date, take the discount date.
If the check_date is on or before the second discount date, take the second discount date.
If the check_date is on or before the third discount date, take the third discount date.
If none of the above is true, the invoice will not be selected.
(d) Confirm the relevant discount date is within the date parameters.
If the always_take_disc_flag is Y, the discount date from Step (c) must be between the pay_from_date and the pay_thru_date, inclusive.
If the always_take_disc_flag is Y and the pay_from_date is null, the discount date from Step (c) just has to be on or before the pay_thru_date.
If the always_take_disc_flag is N, the discount date from Step (c) must be between the check date and the pay_thru_date, inclusive.
3. The payment schedule cannot be fully paid
Action: Confirm the payment_status_flag in ap_payment_schedules_all is N or P
Also confirm the payment_status_flag in ap_invoices_all is N or P
4. The invoice cannot be subject to forced revalidation
Action: Confirm the force_revalidation_flag in ap_invoices_all is N or Null.
5. The payment schedule's payment priority must be between the Payment Priority High and Payment Priority Low parameters designated for the PPR
Action: Find the payment_priority from ap_payment_schedules_all.
Null counts as 99.
Confirm this is between the hi_payment_priority and low_payment_priority, inclusive, from ap_inv_selection_criteria_all.
6. Cancelled invoices will not be selected
Action: Confirm the cancelled_date is null in ap_invoices_all.
7. There cannot be a hold on the payment schedule
Action: Confirm the hold_flag in ap_payment_schedules_all is null or N.
8. A supplier site level hold will prevent payment schedule selection
Action: Confirm the hold_all_payments_flag in ap_supplier_sites_all is null or N.
9. For Payment Request invoices there must be a corresponding record in hz_party_sites
Action: If the invoice_type_lookup_code in ap_invoices_all is PAYMENT REQUEST, and the party_site_id from ap_invoices_all is not null, it must match to a party_site_id from hz_party_sites.
10. Fv_econ_benf_disc.ebd_check must return Y for this invoice
This is a federal function that determines whether it is economically beneficial to pay the invoice now. If Federal is not installed, this will always return Y.
Action: Run the following to check for federal installs
set serveroutput on
begin
mo_global.set_policy_context('S',&org_id_from_invoice);
if (FV_INSTALL.ENABLED) then
dbms_output.put_line('Enabled');
else
dbms_output.put_line('Not Enabled');
end if;
end;
If this returns Not Enabled, continue to the next step. If it returns Enabled, you may need to check the federal rates setup for determining economically beneficial payments.
11. If the user specified an Invoice Batch Name, the invoice must be in that batch
Action: If invoice_batch_id is populated in ap_inv_selection_criteria_all, confirm the same invoice_batch_id is populated in ap_invoices_all.
12. If the user specified the Payee the invoice must be from that payee
Action: If the vendor_id is populated in ap_inv_selection_criteria_all, confirm the same vendor_id is populated in ap_invoices_all.
If the party_id is populated in ap_inv_selection_criteria_all, confirm the same party_id is populated in ap_invoices_all.
13. If the user specified an exchange rate type, it must not conflict with the exchange rate type on the invoice
Action: If an IS_USER inv_exchange_rate_type is populated in ap_inv_selection_criteria_all, confirm the exchange_rate_type on the invoice is also User.
If an IS_NOT_USER inv_exchange_rate_type is populated in ap_inv_selection_criteria_all, confirm the exchange_rate_type on the invoice is either null or a non user type.
14. If the user specified a payment method, it must match the payment method on the payment schedule
Action: If the payment_method_code is populated in ap_inv_selection_criteria_all, confirm the same payment_method_code is populated in ap_payment_schedules_all.
15. If the user specified a vendor type, it must match the vendor type of the invoice's supplier
Action: If the vendor_type_lookup_code is populated in ap_inv_selection_criteria_all, confirm the same vendor_type_lookup_code is populated in ap_suppliers.
16. If any legal entities were specified, the invoice must be in one of those legal entities
Action: If there are any rows in ap_le_group for this checkrun_id, the legal_entity_id in ap_invoices_all must match the legal_entity_id from one of those rows.
17. If any operating units were specified, the invoice must be in one of those operating units
Action: If there are any rows in ap_ou_group for this checkrun_id, the org_id in ap_invoices_all must match the org_id from one of those rows.
18. If any currencies were specified, the invoice's payment currency must match one of them
Action: If there are any rows in ap_currency_group for this checkrun_id, the payment_currency_code in ap_invoices_all must match the currency_code from one of those rows.
19. If any pay groups were specified, the invoice's pay group must match one of them
Action: If there are any rows in ap_pay_group for this checkrun_id, the pay_group_lookup_code in ap_invoices_all must match the vendor_pay_group from one of those rows.
20. For zero-amount invoices, the user must have checked the Include Zero Amount checkbox
Action: If the amount_remaining in ap_payment_schedules_all is 0, confirm the zero_invoices_allowed value in ap_inv_selection_criteria_all is Y.
21. Unapproved invoices will not be selected
Action: Confirm the wfapproval_status in ap_invoices_all and the wfapproval_status on each row in ap_invoice_lines_all is either APPROVED, MANUALLY APPROVED or NOT REQUIRED.
24. An invoice with holds will not be selected for payment
Action: Confirm there are no rows in ap_holds_all where release_lookup_code is null.
25. The invoice must be fully validated. A different query is executed based on whether purchase encumbrances are used for any of the included orgs
Action: Determine the value of the purch_encumbrance_flag in financials_system_parameters.
A. If the purch_encumbrance_flag is null or N, confirm none of the rows in ap_invoice_distributions_all have a match_status_flag of N or S.
B. If the purch_encumbrance_flag is Y, confirm none of the rows in ap_invoice_distributions_all have a match_status_flag of N, S or T.
26. Invoices without distributions will not get selected
Action: Confirm there are rows in ap_invoice_distributions_all.
27. For customers using CCR (a Federal functionality) the Invoice Supplier should not be CCR Expired
Action: See the statement on step 10 to determine if Federal is installed. If it is installed confirm there is not a row in FV_TPP_ASSIGNMENTS_V where the beneficiary_party_id and beneficiary_party_site_id match the party_id and party_site_id from ap_invoices_all and the fv_tpp_pay_flag equals N.
Regards,
Raju.

Ap_selected_invoices_all Payment_Priority

Similar Messages

Maybe you are looking for