R12 - Issues When Importing Credit Card Transactions Into AP (Doc ID 1217994.1)

Last updated on SEPTEMBER 09, 2016

Applies to:

Oracle Payables - Version: 12.0.0 to 12.1.3 - Release: 12.0 to 12.1
Information in this document applies to any platform.

Goal

In 11i, when importing Credit Card Transactions to AP, one uses a request set that includes calls to the following programs in turn :

- MasterCard CDF3 Transaction Loader and Validation Program
- Create Credit Card Issuer Invoice
- Payables Open Interface Import

When running the "Payables Open Interface Import" program, the batch name is provided - this makes it easy for users to search for the newly created invoices.

In R12, one attempts to run the same request set.

After running through the request set, the following scenarios and symptoms are observed :

1 - When attempting to query the resultant invoices in AP, the batch name appears in a format like "SelfService:NNNNN".

2 - The Payables Open Interface Import report output is blank - that is, no output is displayed to indicate if invoices were created or rejected.

3 - The invoices are expected to be created as Standard invoice type, but they are actually being created as Payment Request invoice type.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms