Oracle’s Release 12 of the E-Business Suite is also called the “ Global Business Release ”, as it has numerous enhancements designed to make it easier to do business on a global basis. A more flexible, centralized global accounting structure has been introduced which makes it easier to operate between and across operating units and legal entities. Overall, R12 contains 18 new modules and 2443 enhancements to existing functionality.

Oracle's Release 12 (R12) of their E-Business Suite continues to extend the functionality of the Receivables arena , in addition to incorporated new financial architecture and new products , Oracle Receivables is now very natured product.As part of this post, we will look at Oracle's newest/enhanced offerings in Oracle Receivables.

Revenue Recognition

In R12 revenue recognition is based on Rules and Events, and they are:

• Time-Based Revenue Recognition
  • Ratably Over Time
  • Upon Expiration of Contingencies
• Event-Based Revenue Recognition
  • Payment
  • Customer Acceptance
• Rule-Based Revenue Recognition
  • Payment Term Thresholds
  • Refund Policy Thresholds
  • Customer Credit worthiness

Lets take a quick look on some of the new changes:

• Daily Revenue Recognition
  • Revenue distribution over full as well as partial accounting periods.
  • Fulfills stringent accounting standards
  • Accuracy to the number of days in the accounting period.
• Enhanced Revenue Contingencies :
  • Fully Supports US GAAP and IAS
  • User definable contingencies
  • User definable defaulting rules for contingencies assignment
  • Supports parent-child (e.g. Product and Service) relationship
  • Integration with Order Management and Service Contracts
  • User Interface as well as Programming Interface (API) support
  • Access control through seeded Revenue Managers Responsibility
• Deferred Revenue Management

Event-Based Revenue Management in Oracle Receivables allows users to define revenue deferral reasons or contingencies and corresponding revenue recognition events. In Release 12, revenue contingencies for customer acceptance that are applied to goods sold in Order Management are now applied to services sold to cover those goods. Revenue is deferred for service ordered in both Order Management and Service Contracts. Acceptance contingencies associated with an item instance are automatically applied to service revenue associated with the item instance when it is covered in a Service Contract as a Covered Product. Revenue for services on other covered levels, subscriptions and usage is not impacted by contingencies applied to goods associated with those services.

Global Architecture

As we know, with in global architecture , these new things has been introduced.

• Sub ledger Accounting - Journal Creation takes place prior to GL.
• Bank Model - This unified model enables to park customer Bank as well as Internal bank information into there new model, so that working capital cash flow should be enhanced.
• EBusiness Tax - Oracle E-Business Tax is a new product that uniformly delivers tax services to all Oracle EBusiness Suite business flows. In Release 12, Receivables is enhanced to support
  integration with the E-Business Tax product.
• Intercompany - This is enhanced by automatic balancing,

MOAC Control

This enhance you by enabling and performing tasks across operating Units (OUs), where you have access to without changing responsibilities.As we know , MOAC enables companies that have implemented a Shared Services operating model to efficiently process business transactions by allowing them to access, process, and report on data for an unlimited number of operating units within a single applications responsibility.

In nutshell, once MOAC is enabled, then you can:

• Perform Setups for any OU
• Enter invoices across OUs
• Receive Cash for any OU
• Manage Customer Credit across all OU
• Run reports across OUs

Because of this greatly enhanced Role based security options, the ability to access multiple operating units with a single responsibility can simplify SOX compliance monitoring from finance controller side.

Line Level Cash Applications

The Line Level Cash Applications solution allows the application of receipts to specific transaction items such as individual lines, groups of lines, or tax or freight buckets. From the receipt workbench,you are able choose whether to allocate cash to the entire transaction or to apply amounts against specific items according to the customer remittance.

• Apply to specific lines or groups of lines
• Indicate when tax, freight or finance charges only are paid
• Make changes as needed
• Easily view activity against receipts
• Know what historical activity affects your receipt
• See what prior activity affects a new application

Enhanced Customer Screen

We have seen 11i Customer standard forms makes easier by simple navigation. This times there is clearer separation of the party and account layers, which makes a consist ant look and feel.More over full backward compatibility with 11i UI Bill Presentment Architecture has been provided.

The AR Create Customer page in R12 has eliminated the navigation to separate windows. Now, users can specify the following on a single page:

• Customer Information
• Account Details
• Address
• Account Site Details
• Business Purpose
  

Refunds

Oracle Receivables is fully integrated with Oracle Payables to deliver a seamless, automated process to generate check and bank account transfer refunds for eligible receipts and credit memos.

Late Charges

As we know oracle receivables delivers enhanced Late Charges functionality enabling the creation of standard late charge policies that can be assigned to customer accounts or account sites.Flexible policy configurations include multiple interest calculation formulas, transaction and account balance thresholds, and currency-level rate setups. With new changes these are the enhanced functionality:

• Expanded assessment and calculation capabilities
• Tiered charge schedules
• Penalty charge calculation
• Integration with Balance Forward Billing
• Centralized setup and maintenance of late charge policies
• Calculation performed independent of Dunning and Statement processing

AR-AP Netting

The matching of open receivables and open payables is automated.

Balance Forward Billing

This makes easy transaction processing.

Balance Forward Billing is an enhanced version of the existing consolidated billing functionality for industries where customers are billed for all their account activity on a regular, cyclical basis.

Balance Forward Billing provides the ability to setup cycle-based billing at the account or account site levels, enable event based billing, and leverage user configurable billing formats provided by Oracle Bill Presentment Architecture.

A typical case can be best understood as

• Payment Term defaults
• from Site profile if Bill Level = Site
• from Account profile if Bill Level = Account
• Billing Date derived from transaction date and billing cycle
• Due Date derived from billing date and payment term
• Optionally select non-Balance Forward term if Override Terms = Yes

Lot of people requested some more information for customer import. So I decided to clubbed together, so here to go:

Lets start with Customer ..why it is important in your business.

As per encyclopedia the customer is defined as:

"A customer is someone who makes use of or receives the products or services of an individual or organization." Its means it is one who become a entity in your business world, irrespective of your line of business. If you are manufacturer the customer is one to whom you provide the product and get the money or services for which your get paid.

Time to time the customer definition has been changed and now in today economy it can be redefined as:

A customer..may include users, consumers, demanders, commanders, and requestors. Any person or entity who interacts directly or indirectly with any business system, thus it can be a client within internal departments, a supplier from the procurement process, an employee, or someone who is ringing up the cash register.

What information is important to keep in Business?

Typical information required for any customer is address, contact, bank , profile,class. Oracle standard form does have more than 8 tabs which hold most of the information. A typical flow of customer setup in Oracle is as;

Fig: Standard Setup process for customer

Fig : Entity Model for Customer Setup

What is Customer Interface ?

Customer Interface is a oracle seeded tool that is used to import and validate current or historical customer information from other systems into Receivables. Once customer information is imported into the system, you can use Customer Interface to import additional data for that customer (such as additional contacts or addresses) and to update existing information. This is yet another options to enter Customer information other than manually update and enter new information using the Customer windows.

Customer Interface and Customer in pre 11i and 11i

If you are coming from some old version, if have been noticed few things has been changed:

• Customer tables have changed, to move customer in TCA model, it means
  • The HZ tables
  • The role of Parties
    • Note:Added in order to track prospective customers Due to CRM integration and adds “benefit” of having all customer “groups” stored in one location.

11i tables used by Customer Interface

• Pre 11i versions used only 12 tables
• 11i version uses 23+ tables
• Only 4 of those tables remain the same
• Main Customer tables have changed
• Revised look and feel to Customer screen, too

The Change

Here is significant changes has been noticed from pre 11i and r11i version.

FIND screen

in 11i Find window automatically appears while calling customer screen.

most important , the Match Results window now is included in 11i, and it represnt multiple lines due to Parties and Accounts:

Customer screen

Customer Tables

• Previous Tables that have changed
  • RA_CUSTOMERS
  • RA_ADDRESSES
  • RA_SITE_USES
  • RA_PHONES
  • RA_CONTACTS
  • AR_CUSTOMER_PROFILES
  • RA_CUSTOMER_RELATIONSHIPS
  • AR_CUSTOMER_PROFILE_AMOUNTS
• Tables that remain the same
  • RA_CUST_RECEIPT_METHODS
  • AP_BANK_BRANCHES
  • AP_BANK_ACCOUNTS
  • AP_BANK_ACCOUNT_USES

TCA model - how its drived

• RA_CUSTOMERS, previously the main customer table is now a view.This become view which consists of data in HZ_CUST_ACCOUNTS and HZ_PARTIES tables.
• New Customer Tables - also known as HZ Tables
• The new HZ Customer Tables have tables for Customer Accounts and Parties

Customer Table Vs HZ Tables

Here is summarize information for both for them:

Considering Customer as Parties

• HZ_PARTIES stores information about organizations, groups, and people.
• If a party becomes a customer then the information for the customer is stored in the HZ_CUST_ACCOUNTS table.
• A Party record in the Parties table can have multiple customer account records in the Customer Accounts table.
• One row is created in HZ_PARTIES for every customer record that is imported through the Customer Interface.
• CRM uses the customer module making it a requirement for all customers to have a party id and customer id.

Customer Interface : The Flow:

The following diagram shows how customer information is imported into the customer tables.

11i Customer Interface Vs Oracle Base table

Here is summarize information for interface Vs base table. Once Customer Import get completed successfully , the data moved to these tables:

Please take a note, the bank model has been changed in r12, this will have till 11.5.10.2. If you are looking for R12 , refer to trm guide.

Where to start for Customer Interface

1.The first steps would be your is preparing Receivables setup activity

• Be sure to set up new data in Receivables that the Customer Interface should import. For example:
  • AutoCash Rule Sets
  • AutoInvoice Grouping Rules
  • Collectors
  • Customer Addresses
  • Customer Bank Information
  • Customer Exemptions
  • Customer Profile Classes
  • Demand Classes
  • Dunning Letter Sets
  • Freight Carriers
  • Payment Methods
  • Payment Terms
  • Statement Cycles
  • Tax Codes
• Be sure to also set up Lookups in Receivables that the Customer Interface should import. These are the lookups:
  • Countries
  • Site Use Codes
  • Credit Ratings
  • Risk Codes
  • Account Statuses
  • Communication Types
  • Customer Classes

2. Next is to map the Interface Tables

3. RUN the Import Program

• Run Import after AR Customer Interface tables have been populated
• Program will validate the data in the interface table before creating records in Receivables
• Run the Customer Interface process through the Submit Request window
• But, a separate navigational path is also provided
  Interfaces -> Customer
• Check output file for errors

• Make corrections and repeat import process

Not Surprise , if you get these....Common Errors..very common

• a3: Bill_To_Orig_Address_Ref is not a valid bill-to address
  • Verify the Bill-To address reference is valid. Keep in mind that when using the bill-to reference with a ship-to address record... the bill-to must already exist in Receivables.
  • Note: Ran into this issue. Try running bill-to records through the interface first and ship-to records as second batch - this will resolve the error. Do not Interface with both in the same batch.
• a1:Customer record for insert must have validated profile record defined
  • New customers and each Bill-To record must have a customer level profile in the RA_CUSTOMER_PROFILES_INT_ALL table.
• a8: Conflicting profile classes specified for this customer/site
  • Profile classes for customer and bill-to must be the same. Sites cannot have a profile class different from the customer.
• J1: Site_USE_CODE is not updateable.
• J3: LOCATION is not updateable.
• J2: PRIMARY_SITE_USE_FLAG is not updateable.
  • Keep in mind that site_use_code, primary_use_flag, and location may not be updateable through the Customer Interface
• A3: Customer reference for insert is already defined.
• A5: Customer Number already assigned to a different customer.
  • Customer reference and Customer number are values that must be unique. Verify the customer reference or customer number does not already exist for another customer.

Tips and Technique

1. Check out some of the Profile Options hitting Customer Import

• HZ: Generate Party Number
  • This the profile option can be updated at Site, Application, Responsibility and User levels.This profile option determines whether party number should be auto-generated. If value is 'No',means party number must be passed in by the user else if 'Yes' or if the value is not set, party number will be auto-generated.
• HZ: Generate Party Site Number
  • same as above for party site number set at all leval.
• HZ: Internal Party
  • This profile option is used as a part of CRM setup. This must be set if CRM is installed. It is used for data migration purpose.
• HZ: Generate Contact Number
  • This profile option determines whether contact number should be auto-generated.If the value is 'No', contact number must be passed in by the user. If the value is 'Yes' or if the value is not set, contact number will be auto-generated.

2. Automatic sequence number for customer number

Many times AR department is not like oracle seeded number which start by default 1000.Options are there:

From R11 and 11i, you cannot change the sequence via the forms and therefore any change that you make to the sequence would have to be
through SQLPlus and that would not be supported.

To set the sequence number

Step 1. In the Application Developer responsibility,
Menu: Application=>Database=>Sequence
Step 2. Query on sequence RA_CUSTOMERS_NUM_S
This will bring up the sequence for the customer numbers and you can enter the number that you want it to start from.

To set automatic numbering for customer after setting the sequence:

Step 1. Menu:=>System=>System Options
Step 2. Region - Invoicing and Customers
Step 3. Check the box for Automatic Customer Numbering.

3. When doing Migration from other system, adviced to use TRIM Function

• When loading interface tables remove all trailing spaces from import data.
  Example: LTRIM(RTRIM(customer_name))

4.If importing large number of customers, run in smaller batches instead of all at once.

Oracle benchmark is about 10,000 records per batch is ideal, it is suggested to keep the batch size small.

5.When rolling out in Multi-Org , then you must populate the org_IDs in the interface tables and run the customer interface for each organization set-up responsiblity.

Overview
Auto Lockbox is a service that commercial banks offer 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 your bank. You 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

What is inside the lockbox process

This consist of 3 steps process, viz

1. 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.

2. 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.

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

Process Flow
Here is schematic data flow and process flow of lockbox process

Set Up
These are the Normal Set Required for Auto lockbox. This is part of AR Set up:

• Define Banks
  • Define Remittance Bank with Account use Internal where checks from customer are deposited.
• Define Receipt Class
  • Define a Receipt class to determine the required processing steps for receipts to which you assign payment methods with this class.
• Define Payment Methods
  • Define a payment method with all receipt accounts.
• Define Receipt Source
  • Define Receipt Batch Source and attach receipt class, payment method and remittance bank account information to the Receipt Source.
• Define Lockbox
  • Define Lockboxes to use the Receivables Autolockbox program.
• Define Transmission Format
  • Define the Transmission Format which Auto Lockbox uses when importing data into Receivables.
• Define AutoCash Rule Set
  • autocash rule sets determine how a quickcash receipt is applied to open debit items.
  • enter a sequence for automatiocally applying receipts
  • select one or more autocash rules for receipt application from the list of autocash Rule options
  • Define AutoCash Rule Sets to determine the sequence of rules that Post
  • QuickCash uses to update Customer's account balances.
• Control file
  • Create a control file which is used by SQL * Loader to import the data into interface table and it is placed in the directory $AR_TOP/bin
• Data file
  • data are kept into directory $AR_TOP/bin

This is in continuation to API’s availability,Here are the API’s availability in AR.

Invoices

• Manual Entry and Updating: Manual entry or update of invoices requires the user to have access to the Oracle Application's Accounts Receivable module and specifically the Enter Invoices form. You can enter and update invoices for valid customers. AR uses AutoAccounting to create the revenue accounting combination based on the invoice line information.
• AutoInvoice Interface: AutoInvoice interface provides a mechanism for transferring large volumes of invoices, credit memos, debit memos, and on-account credits from third-party and legacy systems into Receivables. Information is loaded into the RA_INTERFACE_LINES_ALL (which stores information about each interface line imported) and RA_INTERFACE_SALESCREDITS_ALL (containing the sales credit information) tables then imported into the Oracle Applications by the AutoInvoice Import process.You can also refer my old post for autoinvoice details.

Receipts

• Manual Entry and Updating: Manual entry or update of receipts requires the user to have access to the Oracle Application's Accounts Receivable module and specifically the Enter Receipts form. You can enter and update receipts for open and future accounting periods.
• AutoLockbox Interface: AutoLockbox interface provides a mechanism for transferring large volumes of payments from bank files or third party systems into Receivables. Information is loaded into the AR_PAYMENTS_INTERFACE_ALL table then imported into the Oracle Applications by the AutoLockbox Import process.
  The AR_PAYMENTS_INTERFACE_ALL table stores imported lockbox information that has not been validated. AutoLockbox creates one row in this table for each record in a transmission. When the validation step of AutoLockbox is run, Oracle Receivables transfers the information from the AR_PAYMENTS_INTERFACE_ALL tables to the AR_INTERIM_CASH_RECEIPTS_ALL and AR_INTERIM_CASH_RCPT_LINES_ALL tables.

Customers

• Manual Entry and Updating: Manual entry or update of customers requires the user to have access to the Oracle Application's Accounts Receivable module and specifically the Enter Customers form. You can enter and update customers, multiple customer addresses (sites), and multiple contact(s) for each address.
• Customer Interface: The customer interface provides a mechanism for transferring large volumes of customers from third party and legacy systems into Receivables. Information is loaded into the RA_CUSTOMER_INTERFACE, RA_CONTACT_PHONES_INTERFACE, RA_CUSTOMER_PROFILES_INTERFACE, RA_CUSTOMER_BANKS_INTERFACE, and RA_CUST_PAY_METHOD_INTERFACE tables then imported into the Oracle Applications by the Customer Import process.
• TCA API's: The customer information can also be loaded into application by TCA API's.

Sales Tax Rates

• Manual Entry and Updating: Manual entry or update of sales tax data requires the user to have access to the Oracle Application's Accounts Receivable module and specifically the Tax Locations and Rates form. You can enter and update location and rate information through this form.
• Sales Tax Rate Interface: The Sales Tax Rate Interface lets you load sales tax records into your Oracle Receivables application from your sales tax feeder system. Information is loaded into the AR_TAX_INTERFACE table then imported into the Oracle Applications by the Sales Tax Rate Interface process.
  The AR_TAX_INTERFACE table is used to import location, postal code and sales tax rate information into Oracle Receivables. Rows are inserted in this table and then the Sales Tax Interface Program is run to create records in AR_LOCATION_VALUES and AR_LOCATION_RATES. Each row can define a new location and assign to it multiple postal code and effectively date ranges, and each range may have an optional sales tax rate.

Tax Vendor Extension

Oracle provides a Tax Vendor Extension to integrate external tax calculation programs with the Oracle Application's Accounts Receivable module. This extension allows you to provide for complex tax calculation requirements while retaining the full power of Receivables to create and store other tax data. The tax extension is called whenever a tax rate is calculated by the Receivables Tax Engine.

Understanding the profile options and some parameter is essential for autoinvoice execution. Understanding is especially helpful when trouble shooting is required to figure out why and where the processing has failed for certain data scenarios. Here is some informative information for profile Options and parameter required for autoinvoice.

As we know system setup can be done from system options, which is as below.

 1.Max Memory (in bytes)
  As marked 1 in above picture. This is memory setting for allocating autoinvoice program for validation. It is recommended to set Value to 3,000,000 Bytes.

2.Log File Message Level

This is at 2 in above picture. This is number represents the amount of detail we wish to display Auto Invoice log file.

• Message Level 0
  This will gives the following entries in the log file:
  Product Version, Program Name, Auto Invoice Start Time, AutoInvoice Concurrent request Arguments, Error and Warning Messages, AutoInvoice End Time, auto Invoice logical Steps.
•  Message Level 1
  This gives all of the above entries plus:  Time-Stamped function labels
•  Message Level 2
  This gives you all of the above entries plus:  Sizes of Allocated Arrays, Dynamic SQL Statements, Number of Rows Updated, Inserted and Deleted
•  Message Level 3
    This gives you all of the above entries plus: Method IV SQL Array Values.

3. Purge Interface Tables
This is marked 3 in above picture. If this is checked then

• Purges records that are successfully imported into receivables.

It recommended to avoid getting interface tables filled with data that is no more required

4.AR: Autoinvoice Gather Statistics
Specify whether AutoInvoice process analyzes the interface tables or not

• Null is taken as Yes
• This profile should be set to "Yes" if type of data populated in the interface tables changes

5.Number of Instances
This is for Load Balancing.

• Number of CPU -1
• Maximum allowed 500

6.AR: Maximum Lines per Autoinvoice worker
This is setting for let worker know how many records need to pick. This setting is more important, if you are loading very huge set of data. If any one is doing conversion, it is essential to check this value.

The default value is 100000,But the optimal value should be 10000.

Hope this will give a fair idea who is going to utilize autoinvoice First time.

Why set up is important for transaction flex field in autoinvoice? Does my Autoinvoice get failed if I would not do set up or not passing information for Transaction flex field? Yes, You can't. The way the auto invoicing works is designed it worked to Uniquely identify for each transaction.

Then what are those Transaction Flex Fields?

Transaction flexfields are descriptive flexfields that AutoInvoice uses to identify transactions and transaction lines. Oracle Receivables lets you determine how you want to build your transaction flexfield structure and what information you want to capture. There are four types of transaction flexfields:

• Line Transaction Flexfield
• Reference Transaction Flexfield
• Link-To Transaction Flexfield
• Invoice Transaction Flexfield

The key point is the Line Transaction Flexfield must be defined if AutoInvoice is being used. The Line Transaction Flexfield can be used to reference and link to other lines because the Line Transaction Flexfield is unique for each transaction line. AutoInvoice always uses the Line Transaction Flexfield structure for both the Link-to and Reference information when importing invoices. It is only necessary to explicitly define the Link-to, Reference, and Invoice Transaction Flexfield structures if this information is to be displayed on a custom window.

You must define both the line-level and header-level Transaction Flexfield. To define the line-level Transaction Flexfield, query 'Line Transaction Flexfield' in the Title field of the Descriptive Flexfield Segments window and enter the context and segments associated with this Transaction Flexfield. To define the Transaction Flexfield at the header-level, query 'Invoice Transaction Flexfield' and enter the context and segments associated with this Transaction Flexfield. All segments in the line level transaction flexfield that refer to header information must also exist in the header level transaction flexfield. For example if you define a line-level Transaction Flexfield with 4 segments and only the last 2 segments refer to line-level information, define the header Transaction Flexfield using the first two segments.

Where to setup
AR gives you the option of using QuickPicks to display reference information for imported invoices. You can use the System Profile Option AR: Transaction Flexfield QuickPick to select the Transaction Flexfield Segment you want to display in Invoice QuickPicks throughout Oracle Receivables.

Business Case:

Lets say my autoinvoice having two sources,

1.More4Apps - where data is coming from excel based More4apps.
2.PROJECTS INVOICES - for Creating Project invoices.

So to process these, we have set up like this:

If Source is More4Apps then required INTERFACE_LINE_ATTRIBUTE1 till 2 (Fig :2)
If source is PROJECTS INVOICES then required INTERFACE_LINE_ATTRIBUTE1 till 8 (Fig :3)

Fig 2: Setup for Fisrt source as above

Fig 3: Setup for second source as above

What is mean, pretty simple based out of source the respective column should be populated. At the time of validation auto invoice will try to validate first the DFF field, based out of Context Value, The value in context field would be the same which appears while defining. And the process should take the value as reference and create a transaction in the AR.

Here is note on one of most efficient tool used in Oracle application. It is Auto Invoice, most industry accepted tool in Oracle apps.

What is Auto Invoice??

Auto Invoice is a tool that can be used to import and validate transaction data from other financial systems from which one can create invoices, debit memos, credit memos, and on-account credits. It rejects transactions with invalid information to insure the integrity of the data.

Where its fits 

 This fits well with in Oracle ERP or to integrate with any third party application< ?xml:namespace prefix ="" o />

What Module data can be integrated?

• Oracle Order Management
• Oracle Project Accounting
• Oracle services

To make fully functional  what else required

• Loader program
• Validation program

Top 10 reasons for using Auto Invoice

1. Powerful Interface Tool

2. Supports Oracle & Non-Oracle Systems

3. Import Large Amount of Data

4. Calculate or Import Tax

5. Group Lines & Invoices

6. Online Error Correction

7 .Lines Validation

8. Derive GL Date

9 .Import Flex fields

10.Import or Derive Accounting Info

What is inside AutoInvoice

AutoInvoice is a tool consists of 3 main programs. Each program will have unique nature of work to do and they are called internally except Purge program whose execution is derived on the setup otherwise ready to execute stand alone.

§         Master (RAXMTR)

§         Import (RAXTRX)

§         Purge (RAXDEL)

1.       Auto Invoice Master program RAXMTR

Selects and marks records in the interface tables to  be processed based on the parameters the user entered and then calls the AutoInvoice Import program. Auto Invoice Master program has no report output.

 

•Gathers statistics, it means it gathers the stats on interface tables and set the stats on certain indices on interface tables

•Marks interface records for processing by marking request_id

•Submits multiple workers for Parallel Processing by creating instances for request.

 

2.       Auto Invoice Import Program Validates the selected record and creates transaction if it passes validation. Any record that fails validation is left in the interface table with an error code. Depending on the setup, related records may be rejected as well. This program has an output file called Auto Invoice Execution report, which you can view by clicking the View Report button in the Requests window.

 

• Workhorse of Auto invoice
• Validates data
• Inserts records
• Deletes interface data
• Only when system option purge set to ‘Y’

 

3.       Auto Invoice Purge Program Deletes records from the interface tables. If you set the Purge Interface Table system option to No in Define System Option window, Auto Invoice does not delete processed records from the interface tables after each run,and we must submit Auto Invoice Purge Program periodically to clean up the interface tables. This program only deletes transaction lines that have been successfully imported.

•Deletes all rows where interface_status =‘P’

•Ra_interface_lines

•Ra_interface_distributions

•Ra_interface_salescredits

How to start

As discussed above, oracle Receivable’s Auto Invoice program will be used to import and validate Invoices.

A custom feeder program is required to transfer data from the Advantage extract files and populate the Auto Invoice interface tables (RA_INTERFACE_LINES_ALL and RA_INTERFACE_DISTRIBUTIONS_ALL).If there is need to run populate sales credit into RA_INTERFACE_SALESCREDITS_ALL table.

When run, AutoInvoice produces the AutoInvoice Execution Report and the AutoInvoice Validation Report.

Any entries which failed validation can be reviewed in Oracle Receivables’ AutoInvoice Interface Exceptions window. Depending on the error, changes may need to be made in Receivables, the feeder program or the imported records in the interface tables.

How Autoinvoice Execution works

Normally, Auto Invoice can be divided into three major phases

• Pre-grouping: here the validates all of the line level data takes place
• Grouping: groups lines based on the grouping rules and validates header level data
• Transfer :validates information that exists in Receivables tables

 What happen when Auto invoice run

Once the Auto invoice Program gets called, the following activity takes place is part of execution process. This can be analyzed by debug options.

• Line, accounting, and sales credit information for each line populates 3 interface tables
• Lines are ordered and grouped
• Tax is calculated
• GL date is determined
• GL accounts are assigned using Auto Accounting
• Tax, freight, commitments, and credit memos are linked to transaction lines
• All transactions are batched
• Validated lines are used to create the transaction

 How Data is flowing

Select, insert and update and delete take place on certain tables once it is logged out.

Selects

            – RA_INTERFACE_LINES_ALL

            – RA_INTERFACE_DISTRIBUTIONS_ALL

            – RA_INTERFACE_SALESCREDITS_ALL

Updates/Insert

            – RA_INTERFACE_ERRORS_ALL

            – RA_CUSTOMER_TRX_ALL

            – RA_CUSTOMER_TRX_LINES_ALL

            – AR_PAYMENT_SCHEDULES_ALL

            – AR_RECEIVABLE_APPLICATIONS_ALL

Inserts

            – RA_INTERFACE_ERRORS_ALL

AutoInvoice Exception Handling

Records that fail validation are called ‘Exceptions’

• Exceptions stay in Interface Tables which is RA_INTERFACE_ERRORS_ALL
• Errors can be corrected in the Exception Handling window
• Once corrections are made, Auto invoice must be resubmitted
• Records that pass validation get transferred to Receivables tables 

AutoInvoice Exception Handling Windows

• Interface Exception window displays exception messages associated with all invalid records