Oracle Accounts Payable & Receivable

- Release 12 Migration Considerations

Date: 20-Feb-08 Location: Hyderabad
1
Confidential. All trademarks appearing herein belong to their respective owners.

Objectives

Describe and use the new features in Release 12 of Oracle Payables & Receivables Set up the new features in Release 12 of Oracle Payables & Receivables

2
Confidential. All trademarks appearing herein belong to their respective owners.

Agenda for Payables

Supplier Related Enhancements Enhanced Invoice Workbench Enhanced Asset Tracking Multi-Org Access Control in Payables

3
Confidential. All trademarks appearing herein belong to their respective owners.

Suppliers in the Trading Community Architecture (TCA)

The Trading Community Model: Is a highly flexible architecture Allows you to model real world entities in your trading community Allows you to accurately represent complex relationships among entities Is the core data model for trading partners used by Oracle EBusiness Suite applications

4
Confidential. All trademarks appearing herein belong to their respective owners.

TCA Security by Functional Areas

Function Security

Payables Attributes

Purchasing Attributes

Receivables Attributes

5
Confidential. All trademarks appearing herein belong to their respective owners.

11i Vs R12

We have seen in 11i

Suppliers defined in AP. Supplier contacts replicated for each supplier site.

Where as in R12
Supplier becomes as TCA Party. Suppliers Sites as TCA Party Site for each distinct address. Contacts for each supplier/address , it means Single supplier address and contact can be leveraged by multiple sites, for each OU
A single change to an address can be seen instantly by all OUs No longer need to manually push updates across.

6
Confidential. All trademarks appearing herein belong to their respective owners.

Supplier Creation

7
Confidential. All trademarks appearing herein belong to their respective owners.

Supplier Creation Contd..1

8
Confidential. All trademarks appearing herein belong to their respective owners.

Supplier Creation Contd..2

9
Confidential. All trademarks appearing herein belong to their respective owners.

Supplier Creation Contd..3

10
Confidential. All trademarks appearing herein belong to their respective owners.

Enhanced Asset Tracking

Enhanced Asset Tracking

Item Description Manufacturer Model Serial Number Warranty Number

Enhanced Mass Additions

Asset Book Asset Category IPV/ERV distributions

11
Confidential. All trademarks appearing herein belong to their respective owners.

Enhanced Asset Tracking Benefits

Increased efficiency and reduced costs

Asset information typically entered on a purchase order can now flow seamlessly into Payables and Assets.

Improved accuracy of information

The Create Mass Additions process can now be submitted to select invoice distributions by specific Asset Book.

12
Confidential. All trademarks appearing herein belong to their respective owners.

Enhanced Asset Tracking Process

PAYABLES PROCESS
Enter Payables Invoice and match to Purchase Order or Import Purchasing matched invoice Payables retains asset information such as: manufacturer, serial number, asset book and category Optionally update asset information on invoice line or distribution, including asset book and asset category

Automated process

Submit Create Mass Additions process to transfer assets to Oracle Assets

13
Confidential. All trademarks appearing herein belong to their respective owners.

Invoice Lines

Invoice Lines Represent goods or services as lines with distributions tied to each line Facilitates the capture and transfer of pertinent information from Oracle Projects and Oracle Assets Enables line level approval and matching between an invoice line and a purchase order shipment pay item

14
Confidential. All trademarks appearing herein belong to their respective owners.

11i Vs R12

We have seen in 11i

Had only distributions line. Allocation of freight and special charges are captured at the distribution level only Tax and payment and Project accounting Payment was captured through global Descriptive Flex fields.

Where as in R12
Invoice Lines as a new additional line accommodated in Invoice data model. Allocate freight and special charges are captured to the lines on the invoice Invoice distributions created at the maximum level of detail similar to 11i.

15
Confidential. All trademarks appearing herein belong to their respective owners.

Payables Setup: Financial Options

Setting up Retainage Account for the Operating Unit.

Responsibility: Payables Navigation: Setup:Options > Financial Options

You can define one retainage account for the Operating Unit The retainage distribution account on the invoice is used in the seeded accounting setup in Subledger Accounting.

16
Confidential. All trademarks appearing herein belong to their respective owners.

Payables Setup Payables Options

Payables Option settings

Responsibility: Payables Navigation: Setup:Options > Payables Options

Payables Option settings are not specific to this feature, however you may want to evaluate the Approval, Invoice, and Account tab options Use the Payables Options window to enable Payables Invoice Approval

17
Confidential. All trademarks appearing herein belong to their respective owners.

Multi-Org Access Control in Payables Description

Multi-Org Access Control (MOAC) enables cross organizational processing and reporting on Operating Units in subledgers. For example, you can select invoices across operating units for payment processing within a single pay run. A security profile determines a users set of accessible Operating Units. Enhanced Multi-Org Reporting Run several Payables reports at ledger or ledger set level

18
Confidential. All trademarks appearing herein belong to their respective owners.

Multi-Org Access Control in Payables Description

MOAC allows users of a single responsibility to perform task in multiple operating units without having to switch responsibilities. Possible tasks include:
Invoice Processing Payment Processing Run Reports, such as Posted Invoice and Payment Registers, Open Account Balance Listing Run Concurrent Programs, such as Validation and Invoice Import Close Periods

19
Confidential. All trademarks appearing herein belong to their respective owners.

Multi-Org Access Control Process

PAYABLES PROCESS
Open Payables setup form or Payables transaction form Application checks access privilege

Enter data for operating unit and proceed to next task

Submit Concurrent Program Or Standard Report Automated process

20
Confidential. All trademarks appearing herein belong to their respective owners.

Multi-Org Access Control Process, Invoice Entry

There is now an OU field on the Invoice Workbench Select an Operating Unit, or enter another field, such as PO or Supplier Site, from which the system will default the OU The application automatically provides the operating unit of new (uncommitted) invoices during entry.

21
Confidential. All trademarks appearing herein belong to their respective owners.

Multi-Org Access Control Process, Controlling Payables Periods

On the Control Payables Periods form, with Multi-Org Access Control you can close periods for all Operating Units in a given Ledger. Each Payables accounting calendar is associated with one ledger and its accounting calendar, defined in GL.

You can now access the Control Payables Periods window for all ledgers that correspond to the operating units that you have access to, as determined by your security profile.

22
Confidential. All trademarks appearing herein belong to their respective owners.

Multi-Org Access Control Process, Submitting Concurrent Request

There is a new OU parameter that you will when you submit a concurrent request in R12 When submitting the Invoice Validation routine, if you leave the OU parameter null, the routine will process data for multiple operating units in a single run Oracle Payables will process data for your set of accessible Operating Units, as determined by you Multi-Org Security Profile, defined in Oracle HRMS.

23
Confidential. All trademarks appearing herein belong to their respective owners.

Multi-Org Access Control Setup

GENERAL MOAC SETUP

Define security profile & assign operating units

Run Security List Maintenance

Assign security profile to responsibility or user

Automated process

24
Confidential. All trademarks appearing herein belong to their respective owners.

Agenda for Receivables

Customer Creation Enhanced Transaction Work bench AP/AR Netting MOAC

25
Confidential. All trademarks appearing herein belong to their respective owners.

Customer Creation
Customer Standard User Interface Redesign Redesigned as an HTML-based user interface Provides a more streamlined and intuitive customer data management flow Customer data entry is coupled with data quality management tools to maintain the integrity of customer data TCA (Trading Community Architecture) takes care of Customer Majority functionality is same, except Tax profile is linked to the

customer site level. This helps to pick up required Tax Code at the time of creation of Invoices as well as Receipt.
Adding Customer Details Adding Customer Account Details Adding Customer Account Site Details Creating ac Customer Account Relationship

26
Confidential. All trademarks appearing herein belong to their respective owners.

AP/AR Netting Description

AP/AR Netting automatically compares Payables to Receivables

and creates the appropriate transaction in each system to net supplier invoices and customer invoices
A receivables user can View netted receipt details directly from the receipt Create Netting Agreements and Netting Batches The AR Customer Supplier Netting Report has been retired

27
Confidential. All trademarks appearing herein belong to their respective owners.

AP/AR Netting Process Access

User can now access forms for creating and updating: Netting Batches Netting Agreements After Querying a netted receipt, user can view details about the

batch by selecting AP/AR Netting from the Action menu Netted Receipts are created automatically by the AP/AR Netting process User cannot update Netted Receipts from the Receipts Workbench

28
Confidential. All trademarks appearing herein belong to their respective owners.

Receivables & Multi-Org Access Control

The Operating Unit field: Is mandatory Defaults from the value that has been set for profile MO: Default Operating Unit Is attached to a list of values that lists all operating units that you have access to Is not used with:
Payment terms Aging bucket forms

29
Confidential. All trademarks appearing herein belong to their respective owners.

Receivables & Multi-Org Access Control

Multi-Org Access Control functionality is also available on the Receipts form. Receipt Methods have remittance banks, which are defined per operating unit
The list of values for Receipt Method shows all Receipt Methods that have banks in the operating units that exist for the user session

30
Confidential. All trademarks appearing herein belong to their respective owners.

Multi-Org Access Control Process

You can submit Concurrent requests for all operating units in the user session or for a specific operating unit that you select. You can select the operating unit from a list of values that lists all the Operating Units to which you have access. Many concurrent processes can run for all operating units in your security profile, including:
Auto Invoice Auto Receipt Creation Statements Revenue Contingency

31
Confidential. All trademarks appearing herein belong to their respective owners.

Multi-Org Access Control Reporting

All reports can be submitted for just one operating unit Cross organization accounting reports can still be submitted for a whole ledger
These reports now run for all operating units to which you have access when the reporting level is set to Ledger

32
Confidential. All trademarks appearing herein belong to their respective owners.

Thank You

www.genpact.com
33
Confidential. All trademarks appearing hereinto belong to their respective owners. Confidential. All trademarks appearing herein belong their respective owners.