Lockbox in AR

AutoLockbox (or Lockbox) is a service that commercial banks offer corporate customers to enable them to outsource their accounts receivable payment processing. A lockbox operation can process millions of transactions a month. AutoLockbox eliminates manual data entry by automatically processing receipts that are sent directly to the bank. 

AutoLockbox is a three step process: 

1. Submit Import: During this step, Lockbox reads and formats the data from your bank file into AutoLockbox tables using an SQL *Loader script.

2. Submit Validation: The validation program checks data in the AutoLockbox tables for compatibility with Receivables. Once validated, the data is transferred into QuickCash tables. At this point, we can optionally query the receipts in the QuickCash window and change how they will be applied before submitting the final step, Post QuickCash. 

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

These steps can be submitted individually or at the same time from the submit Lockbox Processing window. After we run Post QuickCash, Receivables treats the receipts like any other receipts; 

Lockbox Process Flow

Lockbox Interface Table:

When you run the Import step of AutoLockbox, Receivables stores receipt data from the bank file in the Lockbox Interface table AR_PAYMENTS_INTERFACE. 

Read more »

Oracle Autoinvoice Interface Tables

AR Invoice Interface Tables

• RA_INTERFACE_LINES_ALL

- This table stores transaction header and line information.

- AutoInvoice uses Transaction Flexfields to uniquely identify each transaction that we import  into Receivables.

- AutoInvoice always uses the Line Transaction Flexfield structure for both the Link-to and Reference information when importing invoices

• RA_INTERFACE_DISTRIBUTIONS_ALL

-  If we do not use AutoAccounting, we must enter accounting distributions for the transactions.

- If the accounting distributions are for transactions that use accounting rules, we must enter the percentages, but not the amounts.

- If the accounting distributions are for transactions that do not use accounting rules, we can enter either the percentages or amounts, depending on the value we entered for the batch source.

- Distributions in this table are linked to the appropriate transaction lines in the ra_interface_lines via the transaction flexfield. Though the distribution for 'REC' account class is at the invoice level, it may be linked to any transaction line of the invoice in ra_interface_lines. AutoInvoice will then correctly transfer all distributions to RA_CUST_TRX_LINE_GL_DIST_ALL.

• RA_INTERFACE_ERRORS_ALL

- This table stores information about interface lines that failed validation and were not imported into Receivables tables.

- Receivables uses the information in this table to generate the AutoInvoice Validation Report - - AutoInvoice identifies all errors for each transaction line, thus reducing multiple validation and correction cycles. When we resubmit AutoInvoice, the program deletes the errors for each line selected for processing. When all of the records have been successfully processed, AutoInvoice purges any remaining data in this table.

- Use the Interface Exceptions window to view all of the errors in

 RA_INTERFACE_ERRORS_ALL.

• RA_INTERFACE_SALESCREDITS_ALL

- This table stores sales credit information for the transactions.

- This table must be populated if the AutoAccounting is set up to derive segment values based on the salesrep. If AutoAccounting does not depend on salesrep, then the value we enter in the Required Salesrep field of the System Options window and Allow Sales Credits field in the Transaction Sources window will determine whether we must enter sales credit information.

Read more »

Sequence Of Firing Triggers In Oracle Forms

Navigational events occur at different levels of the Form Builder object hierarchy (Form, Block, Record, Item). Navigational triggers fire in response to some navigational events in the below order:

- Logon Triggers are fired first in below sequence:

1.PRE-LOGON
2.ON-LOGON
3.POST-LOGON

- After that, Pre Triggers are fired

1. PRE-FORM

2. PRE-BLOCK

3. PRE-TEXT-ITEM

- After that, WHEN-NEW Triggers are fired

1. WHEN-NEW-FORM-INSTANCE

2. WHEN-NEW-BLOCK-INSTANCE

3. WHEN-NEW-RECORD-INSTANCE

4. WHEN-NEW-ITEM-INSTANCE

- After this focus is on the first item of the Block. If we type some data and press the tab key following trigger will fire in sequence

1.KEY-NEXT-ITEM (This trigger is present on the item level).

2.POST-CHANGE (This trigger is present on the item level).

3.WHEN-VALIDATE-ITEM (This trigger is present on the item level).

4.POST-TEXT-ITEM (This trigger is present on the item level).

5.WHEN-NEW-ITEM-INSTANCE (Block Level Trigger).

- After That, POST TRIGGERS are fired

1. POST-BLOCK
2. POST-FORM

Read more »

Applying for an L2 EAD(Employment Authorization Document) on your own

Form I-765

I was talking to a friend recently and she is also working in US with L2 EAD. She had applied for EAD for the first time with the help of the lawyers at her husband's company. Well, it was sponsored by the company itself at that time. She got an EAD in FEB, 2015 for 2 years and she had to apply for renewal a few months back. During the conversation, it came up that she had to pay a $1000 for the renewal. I was surprised because I remember to pay around $400 for the same and then we realized that she had paid the rest for the lawyers' fees. That's why I thought of writing my experience of getting an EAD without paying anything extra.

This Link https://www.uscis.gov/i-765 has all the information needed for applying an EAD.  I just printed the I-765 Form and the checklist and took a print of all the required documents and wrote a cheque and sent across to the address and got my EAD in 3 months. So, I had applied for L2 EAD for the first time on August, 2015. I got my EAD copy on November, 2015. My current EAD is valid till Oct, 2017 and I applied for renewal recently. 

So, below is the step by step directions to apply for a L2 EAD or renewal of L2 EAD.

1. Download the form I-765 from Form I-765 (PDF, 289 KB). Take a print.

2. Download the instruction sheet to fill the I-765 form from Instructions for Form I-765 (PDF, 332 KB)

3.  Download the form G-1145 to get an email notification or a notification on your mobile number once received.  Form G-1145, E-Notification of Application/Petition Acceptance (PDF, 229 KB)

4. Fill in the I-765 form.
    For fresh application:
    Tick off ' Permission to accept employment' at 'I am applying for:' section
    Put I-94 Number at 10 (Alien Registration Number)
 
   For renewal application:
   Tick off ' Renewal of my Permission to accept employment' at 'I am applying for:' section
   Put A- Number at 10 (Alien Registration Number)
The Eligibility Criteria, for L2 EAD is a(18)

5. Check for filing fees at https://www.uscis.gov/forms/our-fees and write a cheque for the same amount. As of today's date, the fee is $410.

6. Get ready with the below supporting documents:

• Filled Application form I-765
• Filing Fee Cheque for $410
• A copy of I-94 (front and back)
• A copy of last EAD copy (front and back) for renewal
• 2 recent color photographs
• L1 Visa copy
• L2  Visa copy
• L1 I-94
• Marriage Certificate Copy

7. Send all the documents to the USCIS lockbox address. Address depends on the category that you have chosen.For category a(18) address is available at : USCIS Phoenix and Dallas Lockbox facilities chart

8. Check the EAD status at https://egov.uscis.gov/casestatus/landing.do

Edit1: Got my renewed EAD copy in exactly 2 months. But since my L2 Visa was valid for 1 year (11 months to be precise), got my EAD for 11 months this time.

Read more »

Kill Session in Oracle

Retrieve session identifiers and session serial number (which uniquely identifies a session's objects):

select sid, serial# from v$session where username = 'USER'

kill the session:

alter system kill session 'sid,serial#'

Disconnect the session:

alter system disconnect session 'sid,serial#' post_transaction;

alter system disconnect session 'sid,serial#' immediate;

Read more »

Collection and Record In Oracle

A collection is an ordered group of elements, all of the same type. 

In a collection, the internal components are always of the same data type, and are called elements. We can access each element by its unique subscript. e.g. Lists and arrays.

A record is a group of elements, which can be of different types. 

In a record, the internal components can be of different data types, and are called fields. We can access each field by its name. A record variable can hold a table row, or some columns from a table row. Each record field corresponds to a table column.

PL/SQL has 3 collection types as below:

• Index-by tables, also known as associative arrays,  are sets of key-value pairs, where each key is unique and is used to locate a corresponding value in the array. The key can be an integer or a string.
•  Nested tables hold an arbitrary number of elements. They use sequential numbers as subscripts. We can define equivalent SQL types, allowing nested tables to be stored in database tables and manipulated through SQL.
• Varrays (short for variable-size arrays) hold a fixed number of elements (although we can change the number of elements at runtime). They use sequential numbers as subscripts. We can define equivalent SQL types, allowing varrays to be stored in database tables. They can be stored and retrieved through SQL, but with less flexibility than nested tables.

Collection Type	Number of Elements	Subscript Type	Dense or Sparse	Where Created
Associative array (or index-by table)	Unbounded	String or integer	Either	Only in PL/SQL block
Nested table	Unbounded	Integer	Starts dense, can become sparse	Either in PL/SQL block or at schema level
Variable-size array (varray)	Bounded	Integer	Always dense	Either in PL/SQL block or at schema level

Read more »