Accounting Method Builder (AMB) ,Event Classes and Event Types

Subledger Accounting is a new set of tools, accounting engines and repsoitory. Accounting Method Builder is a part of Subleger accounting.

Accounting Methods Builder:

• Toolset to define Journal Entry rules for the transactions and events of a subledger application.
• Allows defining multiple sets of rules to be used concurrently for different requirements.

How Accounting Methods Builder works Journals are split into three main components:
1.Description
2.Line Types
3. Account Derivation Rules.

Event:
Subledger Accounting introduces the concept of events for the transactions. An event is the recording of a change of status in the transaction life cycle (for example, an invoice has been approved, a payment has been cancelled, a period has been closed, etc.). This is a fundamental component of the design to allow a clear separation between transactions and their accounting representations.Since events are the bridge between the transactions and the journal entries.


Event Model: Definition of the subledger transactions types and lifecyle.
Event Class: Classifies transaction types for accounting rule purposes.

Payables - Invoice, Debit Memo, Prepayment, Payments, Refunds.

Receivables - Invoice, Deposit, Receipt and Bill Receivables.

Purchasing - Requistion, Purchase Order.

Event Type: Accounting event types represent the business operations that can be performed on the event class. An accounting event always has an associated event type.

For each transaction type, defines possible actions with accounting singnificance.

- Payables Invoice - Validated, Adjusted, Cancelled.

-Receipt - Created, Applied , Unapplied , Updated , Reversed. Adjusted.

-Purchase Order - Created, Distributed, Cancelled, Rejected, Finally Completed.

Oracle Subledger Accounting introduces a new Subledger Accounting Rules Detail Listing Report to provide detailed information about accounting rules defined for a subledger accounting method. The report can be submitted from the individual subledger applications or from Oracle General Ledger.
In addition, the report can be submitted for custom applications registered within Oracle Financial Accounting Hub.Users can now use the new report to easily review the following setup details:
• Subledger Accounting Method
• Journal Line Definition
• Journal Line Type
• Account Derivation Rule
• Journal Header Description
• Journal Line Description.

R12.1.X New Features

Ledger Architecture
- Ledgers: Define by Chart of Accounts, Calendars, Currency and Accounting Conventions.
- Ledger Sets: Group of Ledgers sharing the Same Chart of Accounts and Currency.

Centralized and Flexible Rules based Accounting Engine
- Ruled based engine with configurable accounting rules
- Single source of truth for accounting, reconciliation and reporting with common data model and repository and posting engine.
- Consistent data model and user interface across all subledgers.

Centralized Legal Entity Management
- Manage Legal Corporate Structure
- Link tax, intercompany, bank account and accounting functions
- Isolate legal compliance issues at legal entity from the management and security issues at operating Unit.

Centralized Banking and Payments
-Single user interface for all setup and maintenance related to banks and internal bank accounts.
-Centralized management of all funds capture and disbursements
-Centralized credit card management.

Centralized Global Tax Processing
-Centralized Tax Engine with single data model for rules and transations across geographes and applications
-Centralized tax repository for global visibility
-Simplified tax configuration across legal entities and oracle apps.

Advanced Global Intercompany system
- Centralized intercompany and intracompany accounts setup
- Fully configurable approval rules and invoicing options.
- Physical Payables and Receivables intercompany invoice generation.

Oracle General Ledger:

- Single Page for all accounting setup with Accounting Setup Manager.
- Prevent Accounting errors with Alternate accounts
-Replacement for Disabled Accounts
-Prevent unauthrized posting with Control Accounts
-Simplify security and Data Access and Definition Access sets.
-Sequential numbering of accounting entries
-Journal line reconciliation-Journal Batch Copy
-Historical Data initialization for new reporting currencies and secondary ledgers.

Oracle Payables:

- Pay on behalf of a different party with 3rd party payments
- Greater flexibility in defining and calculating discounts for quick payments.
-Application of withholding taxes at time of invoice validation and during payment
-Improved resolution for dispute processing with suppliers.
-Imporve invoice data entry and management with line level entry, approval, matching and tax calculation.
-Automated netting of Customer and Supplier balance
-Self-Service invoivce allows employees and suppliers to enter various invoice type online.
-New interface and data model for supplier managment in TCA.


Oracle Receivables:
-Streamlined receipt porcessing with cash application work queue.
-Enhanced performance for high volume receivables processing.
-Synchronize Cost of Goods Sold(COGS) with Revenue.
-Increased efficiency with line level cash application.
-Improved billing communcation with balance forward billing.
-Create standard late charge polices that can be assigned to customer accounts or account sites.

Oracle Advanced Collections:
- Assign bankruptcy status at the customer level
- Effetively manage later stage delinquency status assignment at case and contract level.
- Internal only comment visibility for dispute processing.
- Streamline system setup and operational maintenance with implementation checklist.
-Consolidation of collections features provides collections workbench
-Improved ability to collect with enhanced dispute management.

Oracle Assets:
- Flexible accounting configuration
- Automated depreciation rollback for selected assets
- Enhanced mass additions interface for legacy conversions
- Unplanned depreciation(impairments) for energy industry
- Unit of production and straight line depreciation methods for O&G industry.
- Flexible reporting with BI Publisher.

Source: My Oracle support

Auto Invoice Performance Improvement

Setup Considerations for Performance:
===============================
System Options Setup
-Log File Message Level-Message Level 0 shows the following in the log file:

• Product Name & Version
• AutoInvoice Start Time, End Time, & Logical Steps
• AutoInvoice Concurrent Request Arguments
• Error and Warning Messages

-Message Level 1 shows time stamped function labels plus all of the above.
-Message Level 2 shows above entries plus:

• Sizes of Allocated Arrays ,Dynamic SQL Statements , Number of Rows Updated, Inserted and Deleted

-Message Level 3 shows above plus Method IV SQL Array Values

Scenarios: You have number of transactions in the AR Interface table which are ready to get invoiced for the source order Management, you have run the auto invoice program and the process is taking long time to complete e.g more then 6 hrs for 3000 lines . What do you do and how do you improve the performance of the Auto invoice program.

To increase performance during the validation portion of AutoInvoice:

NOTE: You may want to back up this table before truncating if you need to review prior errors. Errors will be re-submitted into this table from any unprocessed invoice lines

1. Ensure that all indexes for the transaction flexfield are set up i.e indexes should be created on Transaction Flexfield columns.


2. Unique, concatenated indexes should be created on the following tables and columns:

• RA_CUSTOMER_TRX_ALL
• RA_CUSTOMER_TRX_LINES_ALL
• RA_INTERFACE_LINES_ALL
• RA_INTERFACE_DISTRIBUTIONS_ALL
• RA_INTERFACE_SALESCREDITS_ALL
• OE_ORDER_LINES_ALL

1.Truncate the table RA_INTERFACE_ERRORS_ALL.

sql> connect AR/AR

sql> truncate table RA_INTERFACE_ERRORS_ALL;

2. If your Line Transaction Flexfield is ORDER ENTRY. You need to create indexes for ALL columns used in the Line Transaction Flexfield.

First, drop existing custom indexes if you have any:

sql> drop index XXX_RA_CUSTOMER_TRX_LINES_A1;

sql> drop index XXX_RA_INTERFACE_LINES_A2;

Second, create the following indexes:

NOTE:You can use CREATE INDEX instead of CREATE UNIQUEINDEX if necessary.

SQL> CONNECT AR/AR

SQL> CREATE UNIQUE INDEX XX_RA_CUST_TRX_U1 ON RA_CUSTOMER_TRX_ALL (INTERFACE_HEADER_CONTEXT, INTERFACE_HEADER_ATTRIBUTE1, INTERFACE_HEADER_ATTRIBUTE2, INTERFACE_HEADER_ATTRIBUTE3, INTERFACE_HEADER_ATTRIBUTE4, INTERFACE_HEADER_ATTRIBUTE5, INTERFACE_HEADER_ATTRIBUTE6, INTERFACE_HEADER_ATTRIBUTE7, INTERFACE_HEADER_ATTRIBUTE8, INTERFACE_HEADER_ATTRIBUTE9, INTERFACE_HEADER_ATTRIBUTE10, INTERFACE_HEADER_ATTRIBUTE11, INTERFACE_HEADER_ATTRIBUTE12, INTERFACE_HEADER_ATTRIBUTE13, INTERFACE_HEADER_ATTRIBUTE14, INTERFACE_HEADER_ATTRIBUTE15);

SQL> CREATE UNIQUE INDEX XXX_RA_CUST_TRX_LINES_U1 ON RA_CUSTOMER_TRX_LINES_ALL (INTERFACE_LINE_CONTEXT, INTERFACE_LINE_ATTRIBUTE1, INTERFACE_LINE_ATTRIBUTE2, INTERFACE_LINE_ATTRIBUTE3, INTERFACE_LINE_ATTRIBUTE4, INTERFACE_LINE_ATTRIBUTE5, INTERFACE_LINE_ATTRIBUTE6, INTERFACE_LINE_ATTRIBUTE7, INTERFACE_LINE_ATTRIBUTE8, INTERFACE_LINE_ATTRIBUTE9, INTERFACE_LINE_ATTRIBUTE10, INTERFACE_LINE_ATTRIBUTE11, INTERFACE_LINE_ATTRIBUTE12, INTERFACE_LINE_ATTRIBUTE13, INTERFACE_LINE_ATTRIBUTE14, INTERFACE_LINE_ATTRIBUTE15);

SQL> CREATE UNIQUE INDEX XXX_RA_INT_LINES_U1 ON RA_INTERFACE_LINES_ALL (INTERFACE_LINE_CONTEXT, INTERFACE_LINE_ATTRIBUTE1, INTERFACE_LINE_ATTRIBUTE2, INTERFACE_LINE_ATTRIBUTE3, INTERFACE_LINE_ATTRIBUTE4, INTERFACE_LINE_ATTRIBUTE5, INTERFACE_LINE_ATTRIBUTE6, INTERFACE_LINE_ATTRIBUTE7, INTERFACE_LINE_ATTRIBUTE8, INTERFACE_LINE_ATTRIBUTE9, INTERFACE_LINE_ATTRIBUTE10, INTERFACE_LINE_ATTRIBUTE11, INTERFACE_LINE_ATTRIBUTE12, INTERFACE_LINE_ATTRIBUTE13, INTERFACE_LINE_ATTRIBUTE14, INTERFACE_LINE_ATTRIBUTE15);

SQL> CREATE UNIQUE INDEX XXX_RA_INT_DIST_U1 ON RA_INTERFACE_DISTRIBUTIONS_ALL (INTERFACE_LINE_CONTEXT, INTERFACE_LINE_ATTRIBUTE1, INTERFACE_LINE_ATTRIBUTE2, INTERFACE_LINE_ATTRIBUTE3, INTERFACE_LINE_ATTRIBUTE4, INTERFACE_LINE_ATTRIBUTE5, INTERFACE_LINE_ATTRIBUTE6, INTERFACE_LINE_ATTRIBUTE7, INTERFACE_LINE_ATTRIBUTE8, INTERFACE_LINE_ATTRIBUTE9, INTERFACE_LINE_ATTRIBUTE10, INTERFACE_LINE_ATTRIBUTE11, INTERFACE_LINE_ATTRIBUTE12, INTERFACE_LINE_ATTRIBUTE13, INTERFACE_LINE_ATTRIBUTE14, INTERFACE_LINE_ATTRIBUTE15);

SQL> CREATE UNIQUE INDEX XXX_RA_INT_SALESCREDITS_U1 ON RA_INTERFACE_SALESCREDITS_ALL (INTERFACE_LINE_CONTEXT, INTERFACE_LINE_ATTRIBUTE1, INTERFACE_LINE_ATTRIBUTE2, INTERFACE_LINE_ATTRIBUTE3, INTERFACE_LINE_ATTRIBUTE4, INTERFACE_LINE_ATTRIBUTE5, INTERFACE_LINE_ATTRIBUTE6, INTERFACE_LINE_ATTRIBUTE7, INTERFACE_LINE_ATTRIBUTE8, INTERFACE_LINE_ATTRIBUTE9, INTERFACE_LINE_ATTRIBUTE10, INTERFACE_LINE_ATTRIBUTE11, INTERFACE_LINE_ATTRIBUTE12, INTERFACE_LINE_ATTRIBUTE13, INTERFACE_LINE_ATTRIBUTE14, INTERFACE_LINE_ATTRIBUTE15);

Note: You only need to create the following indexes, if these tables are being populated with interface data. If you are not using sales credits or accounting distributions, then you do not need to create these indexes

SQL > create index ONT.OE_ORDER_LINES_A1 on ONT.OE_ORDER_LINES_ALL (to_char(line_id)) tablespace APPS_TS_TX_IDX;

3. Set the Log File Message Level = 1 Navigate to Setup > System > System Options and set this value = 1.

4. Set the Profile option AR:Maximum lines per AutoInvoice worker : 1000 (At Site level). Please set this to a value that approximates an even distribution of invoices lines per worker. For example if each invoice has approximately 800 to 1000+ lines and you process 5 invoices per Autoinvoice run (approximately 5000 invoice lines) you could set the value of this profile to 1000 which should distribute 1 invoice (800 to 1000+ lines) per worker, if you run with 5 workers. If you are unsure of the distribution, do NOT set this profile.

Note:

1. AutoInvoice inserts data into the tables, but never changes the data that is fed into the tables.
2. Review the RA_INTERFACE_ERRORS table for details on what is failing during import. Use this information to quickly search for known issues.
3. Review the Invalid Objects and Disabled Trigger Section to confirm correct setup.
4. Run Gather Schema Statistics from the SYSADMIN responsibility

5. If you do NOT see a performance gain after making these changes, Please raise an SR with Oracle Support and upload the log files and execution report from a run of Autoinvoice and the Auto invoice diagnostics script.

6. SQL Query to check the time taken to complete by Autoinvoice import prgram.

SELECT request_id, TO_CHAR(request_date,'DD-MON-YYYY') "Date", RPAD(user_concurrent_program_name,60) "Program Name", RPAD(argument_text,20) "Arg", RPAD(TO_CHAR(a.ACTUAL_START_DATE, 'hh24:mi:ss'),10) "Start", RPAD(TO_CHAR(a.ACTUAL_COMPLETION_DATE, 'hh24:mi:ss'),10) "End", RPAD(TO_CHAR( (TRUNC(SYSDATE) + ( a.ACTUAL_COMPLETION_DATE - a.ACTUAL_START_DATE)), 'hh24:mi:ss'),10) "Actual", c.user_name, status_code "S"FROM applsys.fnd_concurrent_requests a, applsys.fnd_concurrent_programs_tl b, apps.fnd_user cWHERE b.user_concurrent_program_name like 'Autoinvoice Import Program' AND a.concurrent_program_id = b.concurrent_program_id AND a.request_date >= 'DD-MON-YYYY' AND a.requested_by = c.user_idORDER BY request_id desc;

Note : 197213.1-Autoinvoice Performance Is Slow. Note:169935.1 - Troubleshooting Oracle ERP Apps Performance Issues.

Source: My OracleSupport

Oracle Application Patch Types

Standalone (one-off) Patch:
Addresses a single fix or enhancement. Standalone patches are released only when there is an immediate need for a fix or enhancement that cannot wait until an aggregate bundling is available.The One-off patch category was common in the older versions R11 (11.0.x) and early releases of 11i. Typically, they fix single or isolated set of bugs.

Rollup Patch (RUP):
An aggregation of patches that may be at the functional level, or at a specific product/family release level. Roll-up patches are a special kind that started to become more common as 11i matured. They are collection of bugfixes for a specific product and relate to specific patchset level.

For example, a Receivables rollup patch contains all the latest patches related to Receivables at the time the patch was created. A Marketing Family 11.5.10 rollup patch contains all the latest Marketing patches released since, and applicable to, 11.5.10.

Product Patch sets /Minipack:
An aggregation of patches at the product level.Standalone patchsets were common in early releases of 11i. They can enhance functionality and typically fix a large number of bugs for a single product. Once a patchset is applied, it increments the patchset level of a product (the product is sometimes also referred to as module). There are around 250+ products integrated in EBS, and each product has specific patchset level. Minipacks are named in alphabetical sequence such as 11i.AR.M, 11i.AR.N 11i.AR.O, and so on.

Family Pack:
An aggregation of patches at the product family level. For example, Financials Family Pack G(11i.FIN_PF.G) contains all the latest patches for products in the Financials family at the time the family pack was created. Family product codes always end in "_PF" and family packs are given alphabetical sequence such as 11i.FIN_PF.E, 11i.FIN_PF.F and 11i.FIN_PF.G. Family packs are cumulative. Family packs are seta of product patchsets for a particular family (Financials, SCM, Project Suite, and so on). The family pack’s advantage is that the patchset levels were tested together, and should therefore be more stable.

Release Update Packs (R12) /Maintenance Pack:
An aggregation of patches for all products in the E-Business Suite. For example, Release 11.5.10 Maintenance Pack contains all the latest code level for all products at the time 11.5.10 was created. Maintenance packs are numbered sequentially such as 11.5.8, 11.5.9, 11.5.10, and are cumulative. In other words, 11.5.10 contains everything in 11.5.9, which contains everything in 11.5.8, and so on. Maintenance packs deliver a new version of a product. Unlike major release upgrades, maintenance packs change the release number, which is the third number in a version name (for 11i). They are still considered patches, but the changes they introduce are system-wide. Often they also bring in brand new products.

Diagnostic Patch:
Used to gather additional information when a product failure cannot be reproduced by Oracle. The additional information assists Oracle Support Services and Oracle Development in resolving the failure.

Interoperability Patch:
Allows Oracle Applications to function properly with a newer version of the technology stack. Interoperability patches are typically required with new versions of the database or Applications technology stack.

Translated Patch:
A non-English version of a patch. Release 11i supports 30 non-English languages. Customers who are using languages other than English, need to apply the corresponding translated patch(es) for the languages they are using in addition to any base US patch(es).

Merged Translation Patch:
Provided in real time (without requiring a translator) in the event a translated patch is not available when a customer needs it. A merged translation patch is applied just like a fully translated patch. The fully translated patch is escalated and is usually available within 24 hours. It can be applied safely on top of a merged translation patch.

Translation Fix:
Provided in the event a translation word choice is inappropriate. A translation fix is applied just like a translated patch, except there is no corresponding base US patch.

New Feature Patch:
Introduces new functionality and/or products. It is applied using standard patching utilities.

Consolidated Update (CU):
Improves and streamlines the upgrade and maintenance processes by consolidating certain post-release patches. Most recommended patches and rollups for a particular maintenance release are consolidated into a single patch that is installed immediately following application of a maintenance pack or a new installation of Rapid Install. Updates in the CU are predominantly error corrections.

Family Consolidated Upgrade Patch:
Consolidates all upgrade-related patches from all the products within a product family. Family consolidated upgrade patches are released as needed and are applicable only if you are upgrading to Oracle is now introducing a new method for patching, patch set updates, or PSU. According to Metalink notes 854428.1 and 850471.1, An Oracle PSU contains recommended bug fixes and "proactive" cumulative patches, a nice change that makes it simple for the DBA to chose to apply "priority" patches. Starting each quarter, Oracle Cumulative Patch Updates (CPU) will now contain both the PSU and CPU, so the DBA may choose to apply a whole CPU or only the selected patches in the PSU patch bundle.The naming conventions for CPU and PSU is the last-order digit, so it's easy to see of you are patching with CPU or PSU

The PSU supports Oracle's zero-downtime patching, a method for RAC databases whereby each node is patched independently with no downtime.

R12 Changes:

R12 introduces some new terms, codeline and codelevel and changes the meaning of several established terms.

Codeline:

This refers to a point release. Every codeline delivers a unique set of features. So release 12.0 is a understood as codeline A; release 12.1 is understood as codeline B; release 12.2 will be understood as codeline C, and so on.

Codelevel:

Codelevel can resemble patchset level from 11i. For each codeline, there can be a set of updates, which deliver mostly bugfixes and reflects the particular product codelevel after the codeline letter.

Example R12.AR.A.6 means Account Payables product on codeline A (Release 12.0) on codelevel 6 (Part of release 12.0.6).

The important thing to understand is that if you install a specific R12 release such as 12.0.6, all products will not only be on the same codeline (A), but also on the same codelevel (6). The codelevel is incremented via Release Update Packs

Recommended Patch List(RPL):

The Recommended Patch List (RPL) is a tool available via My Oracle Support (formerly called MetaLink), which provides a list of recommended patches pertaining to a selected Family Pack for all the EBS product families. The RPL is available for both 11i and R12 code lines.

The tool is been updated regularly in MySupport/Metalink by EBS development. The well-maintained data in the RPL helps you to easily identify the required patches for the patch set level. As the tool is being standardized across EBS product family, the HRMS patch information is also updated for 11i (FP.K Rup 1, 2 & 3) and R12 code lines. You can now use all the features of the RPL tool

Advantages of applying CPCs over one-off fixes and RUPs are as follows:

• CPCs are fully quality assured against current RUP levels. Individual one-off patches are not.
• CPCs are consolidated and only contain critical patches that apply to broad customer usages. They are smaller in footprint and therefore much easier to apply and uptake than RUPs.
• CPC Readmes have detailed business and functional information about the fixes included. Customers can leverage the Readmes to determine impact and testing required for specific process flows and software components involved.

Important points:

• One-off patches, the 7-digit number is their only identifier.
• The Patchset level naming convention has an alternative to the patch number for easier identification. It consists of version number, product abbreviation, and a letter.
• 11i.AR.N refers to patchset N for product AR for version 11i and it can be found under patch number 9054532 (7 Digit Number)
• Family packs add an additional component to the short name which is “_PF” after the product name abbreviation. For example: the Financails family pack is referred to as 11.FIN_PF.G
• Consolidated updates were introduced after release 11.5.10. They append another number after the version number. So consolidated update 2 is referred to as 11.5.10.2 or simply CU2 .
• Maintenance packs and their alternative names are same as the version number, so it’s 11.5.9, 11.5.10 etc.
• R12.AR.A.6 means Account Receivables product on codeline A (Release 12.0) on codelevel 6 (Part of release 12.0.6).
• RUP5 is equivalent to R12.0.5, RUP6 is equivalent to R12.0.6 etc.

Short names and their meaning:

• CPC: Critical Patch Collection
• RUP: Release update Packs
• RPL: Recommended Patch List
• ARU: Automated Release Update
• CP: Concurrent Processing
• UPC: Upgrade Patch Collection
• PSU:Patch Set Update

Source: Oracle MySupport

Using Personalization how to make Warehouse Field Mandatory on Order Entry Screen

Personalization steps to make Warehouse field mandatory on Order entry screen with a condition to be mandatory for specific Order line type (eg Backorder):

Navigation: Help>Diagnostics>Custom Code > Personalize.

1. Enter Seq:10
Description : Warehouse Mandatory
Level:Function
Condition:
Trigger Event:WHEN-NEW-FORM-INSTANCE
process:Both



Context:
Responsibilites: please assign the responsibilites (order management) as required.
Actions Tab:
Seq:1
Type: Property
Language: All
Enabled:Checked
Object Type:Item
Target Object:LINE.SHIP_FROM_MIR
Porperty Name:Required
Value:TRUE




2.Enter Seq:20
Description:Show message when trying to save with null value in mandatory warehouse field
level:Function
Condition:
Trigger Event:WHEN-VALIDATE-RECORD
Trigger Object:Line



Condition:
:LINE.SHIP_FROM_MIR IS NULL
and ((:LINE.ORG_ID=X and :LINE_TYPE<>1001)
OR(:LINE.ORG_ID=Y and :LINE_TYPE<>1025
Processing Mode: Both

Note: please check the line_type or order type id which need to be included in the above condition in this for back order line type id.

Context:
Responsibility: assign the list of responsibilities as required.

Action Tab:
Enter Seq:10
Type:Message
Language: All
Enabled:checked
Message Type:error
Message Text:Please Enter a Warehouse



When users enter orders with out a warehouse they cannot book the order and they get a popup message please enter a warehouse.

Responsibility Not Visible to user in the list of responsibilites assigned to User:

Recently came to know that though the system adminstrator is given the responsibility access to users, users are not able to view the responsibilities in the list of responsibilities assigned.


1. Check if the responsibility is not end dated.
2. Run the request " Syn responsibility role data into the WF table".
3. Run the request " Synchronize WF LOCAL tables" enter the paramters
- Orig System: ALL
- Parallel Process:0
- Logging Mode: LOGGING (Logging Activated)
- Temporary Tablespace : Blank
- Riase Errors: Yes
4. Run the request "Workflow Directory Services User/Role Validation" enter the paramters
- p_BatchSize:10000
- Fix dangling user/roles : Yes
- Add missing user/role assignments : Yes
- Update WHO columns in WF tables: Yes
5. Log off and login back and verify that the responsibility appears.

That should resolve the issue.

If the problem is not resolved still ask the sysadmin to start the following servives
Navigation: System Administrator > Workflow > Oracle application manager > Workflow Manager
- Workflow Deffered Notification Agent Listner
- Workflow Error Agent Listner
- Workflow Java Deffered Agent Listner
- Workflow Java Error Agent Listner.

In case still there is a issue please raise a Service request with Oracle.

R12 Mutli Org and MOAC

What is Multi-Org:
--------------------
•Multi-Org is a server-side (applications and database) enhancement that enables single installation of Oracle Applications.
•Multi-Org keeps transaction data and some setup data separate and secure by different lines of business.
Business needs:
-----------------
The Multi-Org enhancement provides features that enable you to:
•Support multiple business units even if they use different ledgers
•Secure access to data on a single instance by line of business
•Define different organizational models
•Sell and ship from different legal entities
•Procure and receive from different legal entities
•Produce reports across entities or within a single entity


Types of Organizations supported in Multi-Org Model:
---------------------------------------------------------
Business Group :
- HR

Leger:
- GL, FA

GRE/Legal Entity:

Operating Unit:
- AR, OM, AP, PO etc

Inventory Oranziation:
- INV, MFG Ship

Naming Considerations:
------------------------
Ledger:
Ledger_ ; COB_, ROB_, BG_, HR_, LE_, OU_,

Inventory Organization:
IO_

Organziation:
GM_


Mutlti-Org Access Control (MOAC):
------------------------------------------
User Access to Multiple operating units is called Multi-Org Access Control.
Multi-Org Access Control 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. This increases the productivity of shared service centers, as users no longer have to switch responsibilities when processing transactions for multiple operating units at a time. Data security and access privileges are still maintained using security profiles that now support a list of operating units.

•Access one or more operating units using single responsibility.
•Enhanced reporting capability using:
–Reporting level parameter
–Reporting context

Benefits:
----------
Using MOAC, a user can perform tasks for multiple operating units (OU) without changing their responsibilities.

Tasks users can perform using MOAC in multiple OUs:
•Enter Payables Invoices
•View Consolidated Requisitions
•Perform Collections
•Process Receiving and Drop Shipments
•Customer Data Management
•Accounting Setup

MOAC Setups and Process:
-----------------------------
Setup:
1. Define Operating Unit
2. Create Security Profile
3. Run Security List Maintenance
4. Setup Profile Options.

Process:
1. Login and select a responsibility
2. Launch a Form
3. Application Checks Users Access Privileges
4. Process data for Operating Unit.


Leveraging Multi-Org Access Control feature:

Accounting Setup Manager :
Create ledgers and operating units through the Accounting Setup Manager.

Payables:
Reduce processing time with the ability to enter invoices for multiple operating units without switching responsibilities. Reduce processing cost with the ability to pay invoices for multiple operating units in a single pay run.

Receivables:
Provide global information for decision making purposes with new cross organization reports

Purchasing:
Ability to negotiate discounts armed with consolidated requisition demands

Collections:
Global collections agency with consolidated view of customer accounts and collection tasks for multiple operating units

R12.1.x Features and New Modules in R12.1.x

New Modules in R12.1.x
===================
-Oracle Landed Cost Management
-Oracle Site Hub
-Oracle Price Protection
-Oracle Manufacturing Operations Center
-Oracle Supplier Ship and Debit
-Oracle Advanced Planning Command Center
-Oracle Demand Signal Repository
-Oracle Manufacturing Operations Center
-Oracle Service Parts Planning.

Oracle Landed Cost Managment:
=========================
Oracle’s Landed Cost Management application is a new product released on EBS R.12.1.Landed Cost Management enables organizations to gain insight into all of the “real”costs associated with acquiring products including broker, terminal, insurance, and transportation fees as well as duties and taxes. These costs are initially estimated andupdated with actual amounts as they become known allocating them to shipments,orders, and products. Cost methods and inventory valuations are accurately maintained providing better visibility into an individual product’s profitability and an organization’soutstanding exposure. This data provides better insight for product forecasting andbudgeting and provides clear evidence of the detailed accumulation of expenses for regulatory requirements and reporting. Oracle Landed Cost Management (LCM) gives organizations financial visibility into their extended supply chain costs, including transportation and handling fees, insurance, duties, and taxes. Since these types of charges can compose a significant portion (upwards of 40%) of an items' cost, it is important to accurately incorporate them into overall financial processes and decision making activities. Oracle LCM initially estimates these costs and later updates them with actual amounts as they become known, allocating them to shipments, orders, and products. This allows companies to maximize profits, improve visibility into outstanding liabilities, enhance competitiveness, and ensure that complex trade activities are compliant with regulatory mandates

Oracle Site Hub:
=============
Oracle Site Hub is a location mastering solution that enables organizations to centralize site and location specific information from heterogeneous systems, creating a single view of site information that can be leveraged across all functional departments and analytical systems. Oracle Site Hub helps organizations eliminate the problem of distributed, fragmented, incomplete and inconsistent site data resulting from isolated silos of data, lack of centralized data repository, rapid business expansion or mergers and acquisitions. Oracle Site Hub is an enterprise site lifecycle management solution that enablescustomers to consolidate all site-specific information from heterogeneous systems,creating a single source of truth of site information that can be leveraged across allfunctional departments. Oracle Site Hub leverages web services and integration withother Oracle E-Business Suite applications to provide a holistic data hub for site data.



Oracle Site Hub delivers:
--------------------------
1.A prebuilt extensible data model for mastering site information both internal and external such as competitor, supplier, customer sites
2.A single enterprisewide 360-degree view of the sites
3.Unlimited number of predefined and user-defined attributes for consolidating site-specific information
4.Mass maintenance capabilities to manage updates to multiple sites
5.Site mapping and view using Google Maps®
6.Prebuilt integration with Oracle Inventory, Oracle Property Manager, and Oracle Enterprise Asset Management to manage site-specific inventory, property lease, and assets
7.Web services to consolidate and share site data across disparate systems and processes

R12 Oracle Application Footprint

Release 12 is defined as “The Global Business Release.” Global is
not just a geographic perspective, but also a comprehensive
perspective; release 12 functionality spans across both industries
and business functions.

R12 Foot Print:
============






Key Business Flows :
---------------------
Oracle business flows are a collection of application components
designed for end-to-end business processes. They identify the
critical business processes an organization utilizes to support a
complete business strategy for managing operations, customers,
suppliers, partners, and employees.


Oracle business flows map business processes across multiple
organizations and many applications to represent a streamlined,
efficiently integrated information flow throughout business
organizations and across geographies.

R12 Architecture:
----------------------
Business Architecture: The R12 EBS has 5 principles that drives its business architecture:
-Modern Foundation
-Complete
-End to end Intergration
-Global
-Rapid Implementation.

1. Oracle has embedded all of its new R12 development into open,
scalable standards. These standards include using Java/J2EE,
HTML, JavaScript (JSP), Internet-accessibility, and centralized
management.

2. R12 E-Business Suite is accessible via global networks. It
accommodates multiple languages and currencies; supports
international features, such as flexible date formats and multiple
radix support; supports data in the Unicode Character Set (UTF-8)
and has accounting and business localizations built into it.

Technical Architecture:
PHP (Personal Home Page) or Portal becomes the gateway through
which the user has rights to access all the information to which they
have been granted access. Thus, R12 administrative tasks are
simplified while operations costs are reduced.

- Form based: Forms-based users are typically people involved
in the transactional operations of an organization.
- HTML/JSP's (Self Service): Self-service users are infrequent
users who want their interface with R12 to be as simple and as quick
as possible.
- Business Intelligence: Business intelligence users are senior
executives and managers who want an easy-to-use interface that
can be used to reveal critical business information and reports.
- Mobile: users whose jobs are likely to keep them away from a
readily available, network-connected computer. example : sales
representatives, field representative. By utilizing the mobile
interface, they are able to send and receive information at points
where it is important and convenient for them.

AutoLockbox:

Overview of AutoLockbox:

•Process where customers mail payments to a post office box near

your remittance bank and the bank deposits the payments in your

account at regular intervals.

•Bank provides you with computer files detailing about the receipts

and their application. •Receivables uses Auto Lockbox to import

details about receipts directly into the system.

What is AutoLockbox:

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.

Benefits of AutoLockbox:

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

checks into cash.
•Apply receipts to outstanding invoices
•Import historical receipt data
•Autolockbox reports, such as the Post Quikcash Execution Report,

are a good tool to reconcile autolockbox receipts with the bank

transmission reports.

AutoLockbox is 3 Step Process:

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.

•Data is imported into interface tables •Imported data does not affect accounts receivables balances
•Import automatically generates the Lockbox Execution Import report
•Use report to check the imported data

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

•Ensures that each receipt complies with application and customer

requirements
•Customer must have a primary billing location
•Bank can provide a MICR or a customer number to identify customer
•Validated data is transferred to QuickCash tables
•Transfer does not affect accounts receivables amounts
•Receivables can use AutoAssociate or a billing address to identify customer
•Use the Lockbox Execution Import report to review the validation

3.Post QuickCash: This step applies the receipts and updates your

customer’s balances.

•Data is transferred from QuickCash tables to Receivables tables
•Posting updates the account balances to reflect the imported receipts
•View and update receipts in the Receipts window

These steps can be submitted individually or at the same time from the submit Lockbox Processing window. After you run Post QuickCash, Receivables treats the receipts like any other receipts, you can reverse and reapply them and apply any unapplied, unidentified, or on-account

amounts.

MICR Number:

What is a MICR Number:
–Magnetic Ink Character Recognition (MICR)

MICR # Consists of two segments
1st segment - Transit Routing Number (Customer’s Bank) this

identifies the bank from which your customer draws their check.
2nd Segment - Bank Account of the customer (Customer’s Account)
MICR Number Can Only Be Used For One Customer Only!
MICR Number is used to identify the Customer.

The bank account number and the transit routing number makeup

your customer’s MICR number. If a MICR number is shared with

more than one customer, the receipt is rejected.Customers that are

associated must have unique MICR numbers.

By default the lockbox validation program uses an invoice or debit

memo number to determine the customer.

How AutoLockbox Identifies Customers for Receipts:

AutoLockbox can validate your customer data based on the

following attributes . If no match is found, the receipt is imported

as Unidentified receipt. This unidentified receipts can be identified

and then applied from the Quick cash window or the receipt window.

1. Customer Number: If you provide a customer number for

receipts that you import through AutoLockbox, Receivables can

identify the customer to which the receipt belongs .

2. MICR Number: The MICR number that appears on each

receipt relates the customer to a bank. Lockbox only uses MICR

numbers to associate a customer with a receipt if both of the

following are true:
a). The customer number is not included in the transmission

format
b). The MICR number is passed

3. AutoAssociate: If the customer cannot be identified from either

the MICR number or the customer number (for example, if the

transmission does not include this information), you can use

AutoAssociate to determine the customer using matching numbers.

A matching number can be a transaction number, consolidated

billing invoice number, sales order number, purchase order number

or another custom defined number.

4. Associate Receipts with Billing Locations: Receivables also lets

you track receipts for each of your customer’s billing locations.

To use this feature, you must include a billing location in your

transmission format, data file and the flag Require Billing Location

should be set to Yes. This option should be set to yes both at system

options and at the setup of Lockbox. If the box is checked at the

Lockbox, the receipt will be validated only if the billing location is

provided. The setting at the system options level determines

whether Post QuickCash can process receipts with /without billing

locations.

How AutoLockbox Applies Receipts:

If Lockbox is able to identify the customer for a receipt and the

transaction number is provided , Lockbox applies the receipt to this

transaction.

If the transaction number is not provided and Auto associate is

set to Yes, Post QuickCash uses the matching rules defined for the

customer site, customer or Lockbox to apply the receipt.

The setting of Match Receipts By Option tells what type of matching

number is passed in the transmission. If Matching Rules fail, Post

QuickCash applies the receipt using the AutoCash rules set .

If AutoCash rules also fail, Lockbox assigns the receipt a status

of Unapplied. If the transaction number is not provided and Auto

associate is set to No, Post QuickCash assigns the receipt a status

of Unapplied.

AutoLockbox Receipts Matching:

Receivables applies the receipt using:
•Transaction number
•Sales order number
•Purchase order number
•Consolidated bill number
•User-defined number

Maintain Transmission Data:

Use the Lockbox Transmission Data window to delete and edit

transmission data imported into Receivables from your bank

using Lockbox.

You can correct your lockbox data in this window for receipts that fail

validation, then resubmit the validation step again .

Running AutoLockbox:

To Import and apply receipts using AutoLockbox, run each step individually or run them as a group.

Import:
a) If you are importing a new bank file, check the New Transmission check box, then enter a new Transmission Name.

b) If you are resubmitting an existing lockbox transmission, you can select a name from the list of values.
c) Enter the name of the datafile along with path and extension.
d) Enter the name of the control file with out extension. Make sure that

the control file in $AR_TOP/bin directory.
e) Select the transmission Format from list of values.

Validation:

a) Check the Submit Validation Check box.
b) You must enter a lockbox number if Submit Validation is Yes and

the lockbox number is not specified in your bank file.
c) To apply receipts to transactions belonging to unrelated customers,

check the Allow Payment of Unrelated Invoices check box.

d) If you defined your GL Date as ’Constant Date’ in the Lockboxes

window, you must enter a GL Date; if you specified a GL Date of

’Deposit Date’ or ’Import Date’, Receivables uses this as the GL date.
e) Enter a Report Format. Enter ’All’ to include all records processed

in this transmission. Enter ’Rejects Only’ to include only records

that failed validation.
f) To transfer only the lockbox batches in which all records pass the

validation step to the QuickCash tables, check the Complete Batches

Only check box. If you do not check this check box, Receivables will

transfer any receipts within a batch that pass validation, even if

others are rejected.

Post Quick Cash:

a) To apply the receipts and update your Customer’s balances, check

Submit post QuickCash check box.
b)Choose how lockbox should handle invalid transaction numbers.
c) Post Partial Amounts as Unapplied or Reject Entire Receipt

Save your work. Receivables displays the Request ID of your

concurrent process and generates the Lockbox Execution report.

VSOE and Revenue Recognition

What is Vendor specific objective evidence(VSOE)
==========================================
Vendor Specific Objective Evidence, is Fair Value for Software.
SOP 97-2 was designed for Software companies, and works fairly
well for certain traditional business models.
The concept was introduced in 1997 by the AICPA in their Statement
of Position (SOP) 97-2: It governs how any company that licenses,
sells, leases or otherwise markets software (unless it’s incidental to
the product or service as a whole) must recognize the revenue.

In particular, it governs how companies must recognize revenue from
so-called “multiple-element arrangements” – bundles of software and
related products or services sold as a unit at a single price.

Today, more and more companies find themselves dealing with
VSOE as embedded software becomes an increasingly essential
element in traditionally non-software sectors - consider cell
phones, medical devices, computer networks, even cars with GPS
services, etc.

According to SOP 97-2: you allocate relatively, splitting the fee
amongst the products and related elements based upon VSOE –
which is the price established by the vendor for the separate sale
of each element. Each VSOE price is usually established through
accumulation of a quantity of discrete sales “sufficient” to prove
that the market, in it’s willingness to pay that price, thinks the
price is fair. And here’s the big catch:

You can not recognize revenue for any element either until VSOE
exists for each and every element, or until all of the elements
have been delivered.

Sec's Statement of Postion (SOP) 97-2, Software Revenue
Recognition and SOP 98-9, Software Revenue Recognition with
respect to certain transactions, applied to all entities that license,
sell, lease or market computer software. It specifies that revenue
from an arrangement involving multiple elements should be
allocated to the various elements based on VSOE fair values to
the customer.

Sections of SOP 97-2 were amended with SOP 98-9, Software
Revenue Recognition with respect to certain transactions,
SOP 98-9 states that the residual method of revenue recognition is
required when:
1. There is vendor specfic objective evidence of the fair values of all
undelivered elements in a multiple-element arrangment that is not
accounted for using long-term contract accounting.
2. VSOE of fair value does not exist for one or more of the delivered
elements in the arrangement and 3. All Revenue recognition criteria
in SOP 97-2 other than the requirment for VSOE of the fair value of
each delivered element of the arrangement are satisfied.
Elements of VSOE:
==================
-Software Licenses
- Warranty
- Installation
- Support and professional Services
- Training
Fair Market Value (FMV):
========================
The FASB defined 'fair value' in FAS 159 as "The price that
would be received to sell an asset orpaid to transfer a liability
in an orderly transaction between market participants at the
measurement date. " The key points in this definition are
'orderly transaction' and 'market participants.' Thus fair value
can't be established by looking at an exchange of assets in a
bankruptcy or between 'related parties' as defined by the SEC.

Fair value is established by multiple, non- related market
participants in 'normal, orderly transactions. ' VSOE, on the other
hand, is fair value as established by looking at the historical
transactions of a specific vendor and does not consider what other
vendors are charging for similar products.

Revenue Recognition:
====================
Revenue recognition in today's regulatory and business
environment involves sophisticated revenue scheduling and
allocation, Vendor- specific Objective Evidence (VSOE) carve-outs
and Sarbanes-Oxley compliance. Thus having a common system
for global compliance is key to reducing complexity.
Revenue recognition is a principle prescribing that revenue is
recognized when earned.

It has two considerations - when to recognize revenue, and how
much to recognize. Revenue recognition is relevant for companies
to be able to adhere to legal compliance as per the US GAAP
requirements.

Improper revenue recognition increases the risk of financial
restatement, and financial restatements. Revenue for ISV's is
typically divided into three categories: Software, Maintenance, and
Services. Assuming that software customization is not required,
revenue can be recognized when all of the following criteria are met:

There are four basic criteria that must be met to recognize
revenue
- Evidence
- Delivery
- Fixed or determinable fee
- Collectibility.

Revenue Accounting:
===================
Use the Revenue Accounting feature to quickly and easily adjust
revenue and sales credits at the transaction or line level. You can
make manual adjustments using the Revenue Accounting and
Sales Credits window. Alternatively, use the Revenue Adjustment
API to automatically perform these adjustments. Revenue
Accounting uses the Actions Wizard to guide you through the process
of making and modifying revenue adjustments.
You can also use the wizard to record early acceptance for an
invoice line, if the line is associated with a contract that offers an
acceptance clause.

Invoicing Rules:
===============
Use Invoicing Rules to specify whether to record receivables
amounts in the first (Bill in Advance) or Last (Bill in Arrear)
Period.
Invoicing rules determine when to bill the customer in relation to
the accounting rule Periods. Accounting rules determine the
accounting periods for revenue recognition and Billing.
Two invoicing rules are available:



Bill in Advance: Use this rule to recognize receivables immediately.

Bill in Arrears: Use this rule to recognize the receivable at the end of

the revenue recognition schedule.


•Invoicing rules determine whether to recognize receivables in the first or in the last accounting period.
•Once the invoice is saved, you cannot update an invoicing rule.
•If Bill in Arrears is the invoicing rule, Oracle Receivables updates the GL Date and invoice date of the invoice to the last accounting period for the accounting rule.

Accounting Rules:
=================
Use Accounting Rules to determine when to record revenues.
Accounting Rule determine the number of periods and percentage
of total revenue to record in each accounting period.

Each invoice can have different accounting rule.
Use the Accounting, Fixed Duration type to recognize revenue evenly
over a specific number of periods. Revenue can be spread evenly or a
percentage can be specified for each period.












Variable Duration type to recognize revenue by a percentage for
the first period. The remaining revenue is spread evenly across
the number of periods you specify during transaction entry.

Accounting rules determine when to recognize revenue
amounts. Each invoice line can have different accounting rule.

Oracle Receivables uses the First GL Date field in the Transactions
window to determine when to start recognizing revenue. The number
of periods in which revenue is recognized is determined by the
value in the Number of Accounting Periods field in the Transactions
window.Value defaults from fixed ruleValue must be entered for
variable rule. Accounting distributions are created only after you run
the Revenue Recognition program.

•Accounting distributions are created only after the Revenue
Recognition program is run.
•For Bill in Advance, the offset account to accounts receivable
is Unearned Revenue.
•For Bill in Arrears, the offset account to accounts receivable i
s Unbilled Receivables.
•Accounting distributions are created for all periods when
Revenue Recognition is run.

Revenue Recognition Program Execution Report :
=======================================
Use the Revenue Recognition Execution report to review all
revenue distributions created for invoices that use invoice and
accounting rules.

This report displays the account class, GL Date, Accounting
Flex field, the currency, amount, and accounted amount for
the revenue distributions Revenue Recognition creates for
each transaction.

Receivables automatically creates the Revenue Recognition
Execution report whenever you run the Revenue Recognition
program, the Revenue Recognition Master program, or the
General Ledger Interfaceprogram.

When the Revenue Recognition program encounters transactions
with problems that prevent the creation of distributions, the
program completes with a status of Warning, and Receivables
includes these transactions at the bottom of this report.

•The Revenue Recognition program gives control over the creation
of accounting entries.
•Submit the Revenue Recognition program manually through the
Run Revenue Recognition window.
•The Revenue Recognition program will also be submitted when
posting to Oracle General Ledger.
•The program processes revenue by transaction, rather than by
accounting period.
•Only new transactions are selected each time the process is run.

Automated Revenue Recolonization Tools in the Market:
-RevPro
-RevStream
-Revenue Edge.

Oracle iReceivables

Overview of i Receivables:

Oracle iReceivables is an online invoice presentment, dispute, and payment solution that enables external and internal users to inquire about their accounts and transactions, pay invoices, and dispute invoices via a streamlined credit memo workflow and it helps you reduce the cost of billing and collections while improving overall customer service.
Oracle iReceivables gives the customers self-service access to their accounts with real-time balance and transaction information. T
he Home page gives customers quick access to their account information with drill down capability to specific details. It shows transaction balance and aging information, supports print requests, gives discount alerts, and shows credit memo status



iReceivables Features:
-Customer Search
-Accont Details
-Interactive Invoice
-Payment and Credit memo display
-Dispute a bill
-Credit Memo Workflow
-Automatic Credit memo creation.
-Credit memo Request Confirmation Page


Oracle iReceivables gives your Customers Self-Service Account Management

• Export transaction data to spreadsheet
• Attach documents to transactions
• Manage Payments and Ensure Data Security
• Duplicate dispute warning
• One-time credit card payment
• Configurable service charges
• Customizable transaction search.

Simplify the Payment Processes:

• Anonymous user login:
  The Anonymous User Login feature allows external customers to log in by only entering an account number. Therefore, customers can access their customer account data without having to register for a username and password. Companies can customize this feature to take the users directly to the page they need to access the most, for example, the Account Details page or the Home page.
  The benefits of Anonymous User Login are: 1) it removes the registration overhead for users accessing Oracle iReceivables on the one-time basis. 2)It also speeds up the log-in and navigation process for them. As a result, customers are encouraged to make online payments in a more timely manner.
• Multi-pay and multi-print:
  -The Multi-Pay feature allows the customers to select multiple invoices and pay all of them at once using credit card or bank account transfer. With this feature, customers no longer have to navigate into each invoice and pay them one by one. Instead, they can just select all the invoices they want to pay in the Account Details page and pay them all at once.
  -The Multi-Print feature allows customers to select multiple invoices and print all of them at once. The print format is defined in Oracle Receivables, including PDF, HTML, text, XML, PostScript, etc. Once the print job is completed, the customers will receive an e-mail notification containing a link for accessing the printed documents. The link allows for one-time access only.
  

Why do companies want to use Oracle iReceivables?

1. To remove their paper invoices and reduce the mailing and faxing overhead for their invoices. 2. To reduce the manual payment applications and receive payments from their customers more quickly. 3. To reduce phone calls and automate their collections and customer services. 4. To be able to resolve bill disputes quickly and improve their customer satisfaction.

Oracle iReceivables supports :

• A paperless enterprises It streamlines the dispute processes to help reduce the DSO (Days Sales Outstanding)
• It provides customers with self-service payment options such as credit card or bank account, and payment scheduling.
• It enables companies to collaborate with their customers through the self-service account management.
• It automates user administration and registration and expedites online access for one-time users.
  

Oracle iReceivables Modules Intergration:

1. It integrates with Oracle Receivables to provide real-time transaction status and details.

2. It with Oracle Trading Community Architecture to provide real-time account access and customer information.

3. It integrates with Oracle iPayment to enable online payment application and processing.

4. It integrates with Oracle Workflow to provide automated credit memo and multi-print processing.

5. integrates with Bill Presentment Architecture, which provides customizable bill presentment templates.

6. It integrates with Oracle Application Framework to enable personalized display of account information.

• Set the Profile option, Currency:Negative Format correctly so that negative numbers have the negative sign not brackets to facilitate exporting to Microsoft Excel.
• Set the profile option FND:View Object Max Fetch Size, so that all transactions can be viewed on a single page rather than scrolling pages.
• setup of External users is done by the party number assigned to a contact.
  

Mobile Accounts:

• Provides anytime, anywhere access to the application via a web enabled mobile device
  Designed specifically for mobile devices
• For internal (Management , Collection Agents and sales reps) and external users (customers)
• Access for internal and external users can be restricted based on configurable function security Integrated with Mobile Customer Directory
  

Mobile Accounts provides the following information about a customer :
–Account Overview
–Credit Information
–Recent Activity
–Aging

Features:
–Robust Customer Search using Mobile Customer Directory
–Powerful Transaction Search
–Ability to drill down to the Transaction Detail
–Pay an invoice
–Configurable access control
–Efficient non-hierarchical navigational menus

setups:

1. Defind iReceivables Internal Users2

. Defind iReceivables External users and customer Access

3. Define Function Security

4. Index the Customer Database

5. Set up for Self Registraion

6. Setup for Anonymous user login

7. Define Service Charges

8. Review and update Receivables lookups

9. Set the proifle option fo agining buckets

10.Define currencies for customers and customer bill to sites.

11. Define Receipt Class and Payment methodl

12. Set receivables system option for ireceivables payments.

13. setup document sequencing for ireceivables receipts.

14. Set Profile option for ACH Bank accoun transfer payments

15. Modify the dispaly of account information

16. Set profile option for bill presentment architecuture.

17. intergra ireceivables into your business processes.

for more information pls go through the implementation guide and user guide.

Ramification of Invoice Match to PO and Invoice Match to Receipt

Oracle Payables shares purchase order information from your purchasing system to enable online matching with invoices. Invoiced or billed items are matched to the original purchase orders to ensure that you pay only for the goods or services you ordered and/or received. If you are billed for an item over the amount and quantity tolerances you define in the Invoice Tolerance window, during Approval, Oracle Payables applies a hold to the invoice, which prevents payment.
Oracle Payables supports three levels of matching which verify that purchase order and
invoice information match within defined tolerances.

Match Approval Level: 2-Way , 3-Way, 4-Way.

In 2-way: what ever you have ordered for the PO you will make the payment for the suppliers in 2- way i.e we will compare two documents PO and Invoice.
2-way matching verifies that Purchase order and invoice information match within your tolerances:
Quantity billed <= Quantity Ordered Invoice price <= Purchase order price Eg:Suppose we Had given PO for 100 items ,for that we will receive invoice for 100 items. so that we will make payment for that 100 items.
 In 3-Way you will compare 3 documents i.e PO+receipt+Invoice.
3-way matching verifies that the receipt and invoice information match with the quantity tolerances defined:
Quantity billed <= Quantity received. Eg:Suppose we have ordered 100 items in PO. But we had received only 75 items ,But we had received invoice for 100 items. so, we will make payment for only 75 items.
 In 4-Way you will compare 4 documents i.e PO+Receipt+Invoice+Inspection.
4-way matching verifies that acceptance documents and invoice information match within the quantity tolerances defined:
Quantity billed <= Quantity accepted. Eg:Suppose we have 100 items in PO. Suppers send us 75 items We will do inspection on those items what ever we have received, If 15items got damaged. finally, we are going to make payment to the 60 items only. When you match to a purchase order, Payables automatically checks that the total of PO_DISTRIBUTIONS.QUANTITY_ORDERED = AP_INVOICE_DISTRIBUTIONS.QUANTITY_INVOICED (2-way matching). Payables only checks QUANTITY_RECEIVED (3-way matching) if the RECEIPT_REQUIRED_FLAG is set to Y and only checks QUANTITY_ACCEPTED (4-way matching) if the INSPECTION_REQUIRED_FLAG is set to Y.

Invoice Match Option:
The Invoice Match Option determines whether or not you intend to match invoices for this supplier against purchase orders or receipts.
Invoice Match option to PO Match:
--------------------------------------------
•Payables must match the invoice to the purchase order.
•If the Invoice is matched to a PO rather than to the Receipt when the AP team do a match they have the full PO available to match rather than just the specific lines on the PO that were received.
•There is a possibility someone in payables matching to the wrong distribution if they use Match to PO.

•The accrual is valued at the PO exchange rate date.

Invoice Match option to Receipt:
----------------------------------------------
•Payables must match the invoice to the receipt.
•Receipt Match Option is recommended if you want accounting to use exchange rate information based on the receipt date or if you want to update exchange rate information on the receipt.
•If you use the match to receipt option AP team can't match until the goods are received. If the receiving doesn't happen there is no way to associate the invoice with the PO.
•Invoice processing will be on hold till a receipt is entered into the system.
•Receipt Match option determines the cost with more accuracy i.e. Match to Material item receipt and link other invoice charges to receipt and You can now also associate freight, tax, and miscellaneous charges from invoices to the related receipt.
•Run the Matching Detail Report from Other -> Request -> Run. This report will show you detail of how an invoice, purchase order, or receipt was matched. This report is especially helpful when an invoice is on hold and you are trying determine why the hold was placed.

The Invoice Match Option defaults from the Supplier Sites window. You can change the Invoice Match Option on the shipment until you receive against the shipment.

Financial Options - Invoice Match Option:
For purchase order shipments, indicate whether you want to match invoices to purchase orders or to purchase order receipts. If the supplier was created automatically during Expense Report Import, the default value is Purchase Order, and you can change it to Receipts as appropriate.

The decision to set the Invoice match option to Receipt or Purchase Order depends on Business Needs.
•If you are using Multi Currency Functionality for Purchase Order and if like to have the rate based on Receipt date you need to go with Receipt Match at the invoice match option.
•The main advantage is the Exchange Rate factor i.e. Receipt/Current Date instead of Purchaser Order date.
•Receipt Match gives much closer control of the matching process,Particularly where you have multiple receipts of large purchase order.

If a Business is using Invoice Match option Purchase Order and like to change from Purchase Order to Receipt Match, then what would be the impact?

•All Supplier sites need to be updated with Invoice Match option to Receipt.
•Purchase orders which are already approved with Invoice Match Option of Purchase order should continue with the same existing process.
•All existing Open PO, which need a change from Purchase Order to Receipt, should be corrected by changing the invoice match option in the purchase order shipment to Receipt. Payables team should match invoices to Receipt for all Purchase Orders created after the cut-off date.
•Training to AP/PO users.

In order for the receipt to use the current exchange rate and not the PO exchange rate, the Invoice Match Option at the system level and on the suppliers should be Receipt, not Purchase Order.

Overview on Financial Accounting Hub

What is Financial Services Accounting Hub (FSAH pronounced as F-SAA):

Oracle Financials Accounting Hub (FAH) allows you to efficiently create detailed, auditable, reconcilable accounting from a variety of source systems and it address the complex demands of centralizing financial operational data, standardizing accounting and reporting policies, and accelerating regulatory information and management reporting cycles.

It is basically standalone Subledger Accounting (SLA), it allows you to use Oracle SLA and GL to perform the accounting for third party applications.

Financial Services Accounting Hub is a separately licensable product.

What is in the hub?
-Transformation of information from disparate systems into centrally and consistently maintained accounting repository.
-Create and store rules for the transformation of data.
-Secure both information and setup definitions.
-Load journal entry information into the accounting repository.

In 11.5.10, the Oracle AP, AR, FA modules have their own respective accounting engines to derive the accounting to Oracle GL. However, in R12, AP, AR, FA and many of the eBusiness Suite modules will use Subledger Accounting (the FSAH engine) to derive the accounting to Oracle GL. The version of FSAH that you have is not setup to derive the accounting from the subledger products (AP, AR, FA) at this time, so FSAH plays no role in interacting with the Oracle Subledgers in 11.5.10.

FSAH is only available in Release 12. FSAH requires the R12 General Ledger.
The E-Business Suite for Release 12 will use subledger accounting (SLA), which is the engine for FSAH and it will allow integration from AP, AR, and FA to GL.

FSAH is designed to work with Oracle and non-Oracle Applications; therefore, with some customization, FSAH can also work with EBS 11i--i.e., you can integrate the two ledgers from 11i and R12.



Note: FSAH is renamed and it is now called as FAH, FAH is only available in Release 12. FAH requires the R12 General Ledger.FAH is only available in Release 12. FAH requires the R12 General Ledger.

Financials Accounting Hub (FAH) is an offering that enables financial institutions to address the complex demands of centralizing financial operational data, standardizing accounting and reporting policies, and accelerating regulatory information and management reporting cycles. Financials Accounting Hub is a separately licensable product. It is basically standalone Subledger Accounting (SLA). This solution is being offered to Oracle and non-Oracle customers. It was originally intended to fill a market need in the financial services industry -- i.e., banks and financial institutions; however, it is now being offered to customers in other industries such as paint manufacturers, insurance companies, and the healthcare industry.