Skip to main content

Oracle Apps Credit Card: Process in iExpense and Payables

Oracle Apps Credit Card: Process in iExpense and Payables

Tables
ap_credit_card_trxns_all
ap_card_programs_all
ap_cards_all
AP_EXPENSE_FEED_LINES
AP_EXPENSE_FEED_DISTS


Credit Card setups:
1. Credit Card Code Sets window: create credit card code sets.

2. Credit Card Programs window: define your credit card program, including the card issuer, card type, and credit card code set.

3. Credit Card GL Sets window: define GL account sets

4. Credit Card Profiles window: define credit card profiles that you assign to credit cards. Attributes of a credit card profile include credit card program, GL account set, default GL account, exception clearing account, employee verification options, and manager approval options.

5. Credit Cards window: assign a card to a card holder and assign a credit card profile to the card


Steps to process credit card transactions:
Procure to Pay process:
You can streamline your procure-to-pay process by implementing a procurement card program in which your employees purchase items directly from suppliers using a credit card. The credit card issuer then sends transaction files directly to you (the employer). You can import credit card transaction files from your card issuer directly into Payables. Then, you can automatically generate transaction accounting distributions and create invoices to pay the card issuer.

1. You can create a SQL*Loader program that uses a flat file containing the credit card transaction details you want to transfer into the AP_EXPENSE_FEED_LINES table

2. Credit Card Transaction Validation and Exception Report:
   Use this program to validate the credit card transactions you imported into AP_EXPENSE_FEED_LINES.  This program identifies   exceptions such as undefined credit card numbers, invalid transaction or posted currency codes, and invalid credit card codes.

3. Employee verification. This initiates the Credit Card Transaction Employee Workflow, and it executes as you have defined it. If verification is required, an employee can verify transactions directly from a workflow notification.

4. Manager approval or notification. This inititates the Credit Card Transaction Manager Workflow, and it executes as you have defined it. If approval is required from the manager, a manager can approve an employee's credit card transactions directly from a workflow notification.

5. Credit Card Invoice Interface Summary: This program creates invoices for your credit card issuers in the Payables Open Interface tables. This program selects all records for a given date range in AP_EXPENSE_FEED_DISTS with a status of at least Validated.

6. Use Payables Open Interface Import Program to create the invoices for data in Payables Open Interface tables.

iExpense Credit card transactions process:
1. Load Employee credit card expense data into ap_credit_card_trxns_all.

2. Run the "Credit Card Transactions Validation Program" to validated the credit card transactions data.

3. Once data is validated the lines become available in iExpense for employees to select and submit the Expense reports.

Comments

Popular posts from this blog

Oracle Subledger Accounting (SLA) Tables, Views

Oracle Subledger Accounting (SLA) Tables, Views Oracle Subledger Accounting Tables: TABLE NAME DESCRIPTION XLA_AAD_GROUPS The XLA_AAD_GROUPS table stores the merge dependencies analyzed during the merge analysis.  All application accounting definitions with the same GROUP_NUM must be merged together. XLA_AAD_HDR_ACCT_ATTRS The XLA_AAD_HDR_ACCT_ATTRS stores standard, system and custom sources assigned to an accounting attribute at the AAD level. XLA_AAD_HEADER_AC_ASSGNS Store the analytical criteria for the application accounting definitions. XLA_AAD_LINE_DEFN_ASSGNS This table stores the journal lines definitions for the application accounting definitions. XLA_AAD_LOADER_DEFNS_T The XLA_AAD_LOADER_DEFNS_T table is the interface table that facilitates the data transfer from data files and the database. XLA_AAD_LOADER_LOGS The XLA_AAD_LOADER_LOGS table stores the errors and logs generated by the application accounting definitions loader. XLA_AAD_SOURCES XLA_AAD_SOURCES table stores a...

Oracle Fusion Cloud: Supplier Import Process using File Based Data Import (FBDI)

 Supplier Data Migration or Upload to Oracle Fusion environment File-Based Data Import for Oracle Procurement Cloud Supplier import in oracle fusion   In this post , We will discuss about Supplier import in oracle fusion. Oracle has provided the FBDI tool to import suppliers from External  Source  to the Oracle fusion. Supplier Import in Oracle fusion we first need to  Download  the Supplier Import FDBI  templates  given by the Oracle fusion to import suppliers. Oracle has given 5 Different FBDI templates to Import supplier in Fusion. Here in this post , I will share the Complete steps for Supplier import in oracle fusion. You can refer this post for Supplier Import.   Steps for Supplier import in oracle fusion     Step1- First we need to download Supplier Data  Template  from Oracle Repository. Go to this path for Oracle Repository. ( select Based on your Cloud version) https://docs.oracle.com/en/...

Unbilled Receivables and Unearned Revenue Accounting in Oracle Projects

Unbilled Receivables and Unearned Revenue Accounting in Oracle Projects Introduction When it comes to contractual billing, invoice and revenue generation are two separate processes, which during the lifespan of a project may or may not always coincide with each other and so do the balances in revenue and receivables accounts.  This interim difference between revenue and invoice account balances is bridged using Unbilled Receivables (UBR) and Unearned Revenue (UER) Accounts. Unearned Revenue (UER) Unearned Revenue (also termed as deferred revenue or UER) signifies money received for the goods or services, which are yet to be delivered.  As per the principles of Revenue Recognition, UER is recorded as on the balance sheet unless it is converted to Revenue upon delivery of goods or services For Example XYZ Consulting Ltd. receives an annual maintenance contract of $ 12,000 on Dec 31, 2014 for the period of Jan 01, 2015 to Dec 31, 2015. At the start of the contract as of Dec 31, 2...