Payment process request end with "Waiting for payment file Processing" status

Payment process profile end with "Waiting for payment file processing"


Steps to reproduce 

1. Submit Payment Process Request.
2. Select invoices.
3. Click Submit.
4. See that the request ends in status of "waiting for payment file processing".

When running PPR, user can choose whether to automatically create the payment file or submit create electronic/printed payment file ESS request later on manually. This is controlled by 'Create Payment Files Immediately" check box under Payments & Processing options tab of the PPR.

In this case, user ran the PPR with out checking 'Create Payment Files Immediately" check box. Hence the process stopped after creating the payments. Next step is to create a formatted payment file for these payments. To continue with processing of this PPR, customer can manually run 'Create Printed Payment Files' request by clicking on Create Printed Payment Files link in Payments dashboard.

Solution:- 

To continue with processing of the PPR, manually submit the Create Electronic/Printed Payment file using the navigation path below:

Navigation: Payments > Tasks > Create Electronic Payment File OR Create Printed Payment File


To automatically create the payment file with out this manual intervention, submit PPR with 'Create Payment Files Immediately" check box selected.

Query to get the Supplier/Vendor details from oracle E-Business Suite R12.X.X

This query will give you the vendor list by site wise in EBS R12

Pass the parameter as Vendor name or from number to number.

SELECT 
PO.SEGMENT1 VENDOR_NUMBER,
PO.VENDOR_NAME,
PO.VENDOR_NAME_ALT,
PO.VENDOR_TYPE_LOOKUP_CODE,
POS.VENDOR_SITE_CODE
,VENDOR_SITE_CODE_ALT
,POS.ADDRESS_LINE1
,POS.ADDRESS_LINE2
,POS.ADDRESS_LINE3
,POS.ADDRESS_LINE4
,POS.CITY
,POS.COUNTRY
,POS.ZIP
,POS.COUNTY
,POS.STATE
,POS.INVOICE_CURRENCY_CODE
,POS.PAYMENT_CURRENCY_CODE
,POS.PAYMENT_METHOD_LOOKUP_CODE
,POS.PAY_GROUP_LOOKUP_CODE
,HR.NAME
,INACTIVE_DATE
,GLCC.CONCATENATED_SEGMENTS LIABILITY_ACCOUNT
,GLCCP.CONCATENATED_SEGMENTS PREPAY_ACCOUNT
,POS.EMAIL_ADDRESS
FROM AP_SUPPLIERS PO,AP_SUPPLIER_SITES_ALL POS
,GL_CODE_COMBINATIONS_KFV GLCC,GL_CODE_COMBINATIONS_KFV GLCCP
, HR_OPERATING_UNITS HR
WHERE PO.VENDOR_ID=POS.VENDOR_ID
AND GLCC.CODE_COMBINATION_ID=POS.ACCTS_PAY_CODE_COMBINATION_ID
AND GLCCP.CODE_COMBINATION_ID=POS.PREPAY_CODE_COMBINATION_ID
AND HR.ORGANIZATION_ID=POS.ORG_ID
AND PO.SEGMENT1 BETWEEN NVL(:P_SUPPLIER_NUMBER_FROM,PO.SEGMENT1) AND NVL(:P_SUPPLIER_NUMBER_TO,PO.SEGMENT1)
AND PO.VENDOR_NAME=NVL(:P_VENDOR_NAME,PO.VENDOR_NAME)
ORDER BY 1;

PRC: Interface Invoices to Receivables Ends with Rejection 'Accounting flexfield could not be validated

Issue:

PRC: Interface Invoices to Receivables Ends with Rejection 'Accounting flexfield could not be validated

Resolution:-

1.  First you will need to figure out what account the system is trying to build. 
2.  Using the Project Billing Super User responsibility, Setup | Auto Accounting | Assign Rules => Query on function 'Revenue and Invoice Accounts'
3.  Put your cursor in the function 'Unbilled Retention Account' and go through each rule which will help you build the account, i.e., segment 0 is 'Company Rule' with a constant of 01, segment 1 is 'Cost Center Rule' with a constant of 000 and segment 2 is the 'Account Number Rule' with a constant of 1233.  Thus the account we are building is 01.000.1233.
4.  Using the General Ledger Super User responsibility navigate
5.  Setup | Accounts | Code Combinations => enter the account code combination generated in PA, i.e., 01-000-1233.
6.  Verify the 'Enable' box is checked.  If not, please enable. 
7.  Re-run the PRC:  Interface Invoices to Receivables process.


NOTE:  PRC: Interface Invoices to Receivables will end with rejection 'Accounting flexfield could not be validated' if current date is not in between code combination start date and code combination end date.
Validation for code combination while interfacing invoice does not depend on invoice date but Sys date.

If any cross validation or Security rules applied any one of the segment also this issue will occur.