Cash Management

Oracle Cash Management helps you manage your enterprise liquidity and cash positions.

• Manage and control your cash cycle
• Upload and reconcile bank statements
• Forecast your cash needs
• Transfer funds between bank accounts
• Manage Bank, Bank Branch and Bank Account information

Per new Bank Account Model, Banks and Bank Branches are created as Trading Community Architecture (TCA) parties (as opposed to Payables owning them in previous releases). Bank Accounts reside within Cash Management application and we can define in which applications this bank account can be used.

Reconciliation Flow:

Step 1. Receive Bank Statement --&gt Manually or automatically (via Bank Statement Open Interface). Each bank statement can refer to one or more payments, receipts, open interface, misc transactions and consists of one header and multiple bank statement lines. Bank statement line status can be - Reconciled, Unreconciled, Error, External.

Step 2. Load and Verify Bank Statement --> 

Step 3. Perform Reconciliation --> 

Step 4. Review --> 

Step 5. Create JEs and Post to GL

Cash Management and External Systems:

You can include cash flows from external systems using the External Cashflow Open Interface.

Reconciliation Open Interface can find external transactions available for clearing and reconciliation. 

Open interface view --> CE_999_Interface_V

SEPA

The Single Euro Payments Area (SEPA) is a self-regulatory initiative for the European banking industry championed by the European Commission (EC) and the European Central Bank (ECB). SEPA promises to simplify and harmonize the processes related to cross-border payments in the European community, making it easier for citizens to complete financial transactions with less cost and inefficiencies. 

The aim of the SEPA initiative is to improve the efficiency of cross border payments and the economies of scale by developing common standards, procedures, and infrastructure. The SEPA territory currently consists of 33 European countries -- the 28 EU states, together with Iceland, Liechtenstein, Monaco, Norway and Switzerland.

Part of that infrastructure includes two new SEPA instruments that were introduced in 2008:

• SEPA Credit Transfer (SCT) - a Payables transaction in Oracle EBS
• SEPA Core Direct Debit (SDD) - a Receivables transaction in Oracle EBS

The SEPA Cards Framework (SCF) allows competing banks to create new SCF-compliant debit and credit card 

offerings, within the guidelines laid out by the SEPA authorities. 

Within the Oracle E-Business Suite of applications, Oracle Payables (AP), Oracle Receivables (AR), and Oracle Payments (IBY) provide SEPA transaction capabilities.

Oracle Payables (AP) - Elementary

• Payables Accounting Process - to create accounting entries in Payables.

1. The Payables Accounting Process APACCENG writes to the following tables:
   
   ap_accounting_events_all
   ap_ae_headers_all
   ap_ae_lines_all
   
   For invoices it updates the accounting_event_id in ap_invoice_distributions_all
   For payments it updates the accounting_event_id in ap_invoice_payments_all
   For Clearing events it updates the accounting_event_id in ap_payment_history_all

2. Parameter Submit Transfer to GL. If you want to initiate the Payables Transfer to General Ledger program immediately after the accounting entries are created, then enter Yes.
3. The Payables Accounting Process is obsoleted in R12 and replaced by the Create Accounting Program.

• P

Period End Close - Payables

1. Check on Invoice on Hold Report – To ensure all of the invoices is not on Hold. This can be done by using ‘Invoice on Hold Report’

2. Check for Unapproved invoices – To ensure all invoices are approved before the month end closing. This can be done by using ‘Invoice Register’ with option of unapproved only.

3. Check for any unaccounted invoice or payment – To ensure all of the approved invoices and payments are accounted in the system. This can be done using ‘Unaccounted Transaction Report’.

4. Transfer all accounted invoices and payments to GL – To consolidate all of the invoices and payments to GL. This can be done using the ‘Payable Transfer to GL’ Program. At this stage the program will also automatically call up another program ‘Journal Import’ to import the Program to GL.

5. Run ‘Account Payable Trial Balance’ Report to reconcile with GL ‘Account Analysis with Subledger’ Report, with parameter “Source: Payables”. All of the amount in each account should be equal. If it is not equal, then AP and GL need to investigate, also GL Interface table has to be investigated

6. Run ‘Account Payable Trial Balance’ Report for last period.

7. Run ‘Posted Invoice Register’ report to view the invoice posted in this period.

8. Run ‘Posted Payment Register’ report to view the payment posted in this period.

9. Reconcile these reports according to this manner:

A/P Trial Balance (Current) = A/P Trial Balance (last month) + Posted Invoice Register – Posted Payment Register.

10.Close Current month period.

11.Open Next Period.

12.Sweep all of the left over invoices to next period.

Tables Info - Purchasing

PO_HEADERS_ALL
PO_LINES_ALL
PO_LINE_LOCATIONS_ALL
PO_DISTRIBUTIONS_ARCHIVE_ALL

PO_RELEASES_ALL

PO_CHANGE_REQUESTS

• Document_Header_ID (PO_Header_ID)

PO_HEADERS_ARCHIVE_ALL
PO_LINES_ARCHIVE_ALL
PO_LINE_LOCATIONS_ARCHIVE_ALL
PO_DISTRIBUTIONS_ARCHIVE_ALL
PO_RELEASES_ARCHIVE_ALL

PO_VENDORS

• Segment1 - Vendor number is unique

PO_VENDOR_CONTACTS

PO_VENDOR_SITES_ALL

PO_UNIQUE_IDENTIFIER_CONTROL

• Current_Max_Unique_Identifier
• Table_Name

RCV_SHIPMENT_HEADERS
RCV_TRANSACTIONS_INTERFACE

Period End Close - General

Periods represent non-overlapping consecutive date ranges. Every Financials customer needs to successfully close the accounting books each period.
General Steps
Here are some guidelines, from a general perspective, how you can perform the close process for every subledger:
a) Complete transactions
b) Create accounting
c) Reconcile transactions
d) Post to General Ledger
e) Reconcile accounting
f) Close period

Step b), Create Accounting, is a new step in Release 12, as it is an SLA feature. The accounting can be created immediately online, or can be run as a process in the background e.g. as a batch job at a time that matches your business needs.
The important thing to note, is that the accounting is not the distribution on the transaction. The final accounting by SLA could result in different accounting entries being generated based on the accounting rules you have configured. Therefore, you need to ensure that all your accounting for your transactions is created before you post to General Ledger, in order to update the balances correctly.

In Release 11i, when you close your periods in each of the subledgers, Oracle General Ledger will automatically create the balancing lines for journals posted to General Ledger. This changes in Release 12 as subledger accounting creates the balancing lines at the time you account for the subledger transactions.

The subledger accounting journal represents your REAL accounting and the balancing lines are created as part of these subledger accounting journals. When you close a period in Release 12, you’re actually closing subledger accounting. The journals can then be posted to the general ledger to update the GL balances.

Period End Close Dependencies

Interfaces

Inventory

• Item Import
  
  
  
  
  

Legacy System --> Mtl_System_Items_Interface --> Item Import Program --> Mtl_System_Items_B (or Mtl_Interface_Errors)

• Material Transactions

Interface Tables to be used are:
MTL_TRANSACTIONS_INTERFACE
MTL_TRANSACTION_LOTS_INTERFACE
MTL_SERIAL_NUMBERS_INTERFACE

Transaction Type ID should be 2 (for "Subinventory Transfers") and "Material Transactions Manager" will process the records from the Interface tables.

If there are any errors while processing, the details of the errors will be available in MTL_INTERFACE_ERRORS table.

Cost Management

• Item Cost Import

Sample insert statement to populate the Item Cost Interface table

INSERT INTO CST_ITEM_CST_DTLS_INTERFACE
(INVENTORY_ITEM_ID
,ORGANIZATION_ID
,COST_TYPE_ID
,LAST_UPDATE_DATE
,LAST_UPDATED_BY
,CREATION_DATE
,CREATED_BY
,LAST_UPDATE_LOGIN
,Process_Flag
,Item_Cost
,Cost_Element_ID
,USAGE_RATE_OR_AMOUNT
)
SELECT INVENTORY_ITEM_ID
,ORGANIZATION_ID
,COST_TYPE_ID
,SYSDATE
,1441
,SYSDATE
,1441
,14411441
,1
,5
,1
,5
from cst_item_costs where inventory_item_id = 13433714 --12456335
AND Cost_Type_ID = 3

Payables

• Invoice Import

Interface Tables
AP_INVOICE _INTERFACE is the header info
AP_INVOICES_LINES_INTERFACE is the lines table.

RUN PAYABLES INVOICE IMPORT CONCURRENT PROGRAM

Base Tables
AP_INVOICE_ALL is also the header information is stored.
AP_INVOICES_DISTRIBUTIONS_ALL is the lines information table.
AP_PAYMENTS_SCHEDULES_ALL (AMOUNT_REMAINING stores balance amount to be paid)
AP_INVOICE_PAYMENTS_ALL (INVOICE_ID)
AP_CHECKS_ALL (CHECK_ID)

AP_INTERFACE_REJECTIONS (REJECT_LOOKUP_CODE stores the error occurred during the invoice import ex: account required, invalid supplier site )