What is Auto Lockbox ?

Auto Lockbox is a service that commercial banks offer to corporate customers to enable them to outsource their accounts receivable payment processing. Auto Lockbox eliminates manual data entry by automatically processing receipts that are sent directly to the bank.

We can also use Auto Lockbox for historical data conversion. For example, you can use Auto Lockbox to transfer receipts from your previous accounting system into Receivables. Auto Lockbox ensures that the receipts are accurate and valid before transferring them into Receivables.

Benefit of Auto Lockbox

• Eliminates manual data entry
• Streamlines the application of receipt to outstanding transactions
• Effectively manages cash flow by reducing turnover for converting checks into cash

When can I use Lockbox

• apply receipt to outstanding invoice
• import historical receipt data
• auto lockbox report , such as the post quick cash Execution Report, are a good tool to reconcile auto lockbox receipt with the bank transmission

Lockbox Process

Import
During this step, Lockbox reads and formats the data from your bank file into interface table AR_PAYMENTS_INTERFACE_ALL using a SQL *Loader script.

Validation
The validation program checks data in this interface table for compatibility with Receivables. Once validated, the data is transferred into QuickCash tables (AR_INTERIM_CASH_RECEIPTS_ALL and AR_INTERIM_CASH_RCPT_LINES_ALL) . At this point, you can optionally query your receipts in the QuickCash window and change how they will be applied before submitting the final step, Post QuickCash.

Post QuickCash
This step applies the receipts and updates your customer's balances.

 
Main Tables for Auto Lockbox

• AR_PAYMENTS_INTERFACE_ALL
• AR_INTERIM_CASH_RECEIPTS_ALL
• AR_INTERIM_CASH_RCPT_LINES_ALL
• AR_CASH_RECEIPTS_ALL
• AR_CASH_RECEIPT_HISTORY_ALL
• AR_DISTRIBUTIONS_ALL
• AR_RECEIVABLE_APPLICATIONS_ALL
• AR_PAYMENT_SCHEDULES_ALL

So far Applications developed with Application Development Framework had a lot of specifics and ADF components have consisted of large number of parts. Each of these parts had his specific CSS class, which needed to be overridden in order to implement new design. Results were often large number of CSS classes regarding only one component.

To make things easier for developers, Oracle introduced some of default skins of applications and Skin Selector with their JDeveloper IDE. Skin Selector gave developers possibility to visually check out all components included in ADF and see of which parts are they assembled.

As Oracle saw the need for visual improvement of ADF applications, they introduced Alta User Interface.

UI in Desktop/Laptop

UI in Mobile

WHAT MAKES ORACLE ALTA UI DIFFERENT?

 - Fewer elements and cleaner designs
 - Minimal UI chrome with fewer nested borders and lines
 - Multi-device support with flowing page layout
 - New icon system complements clean page design
 - Mobile-friendly, with larger touch targets and flexible page widths

WHY IS ORACLE ALTA UI IMPORTANT?

 - Simplified component structure and more open space keep focus on data
 - Less chrome means faster loading of critical content
 - Browser and mobile technology support
 - Flexibility with simpler, modular, components

Check here  for Online Demo

http://jdevadf.oracle.com/workbetter/faces/index.jsf

First create a value set called READ_ONLY_DFF with the validation type as Special.

Event Type	Function
Edit	FND SQL “BEGIN NULL; END;”
Validate	FND SQL “BEGIN NULL; END;”

 

Next by Application Developer responsibility navigate to Flexfield and select the Application and Title where need to enable the DFF segment as read-only.

Here the value set of Reporting Date (Attribute3) is specified as READ_ONLY_DFF

The Reporting Date would display the system current date as specified below

Now finally once we view the DFF segment the Reporting Date is displayed as READ ONLY.