Release 12 features work arounds and Upgrade

Release12 Obscure features, workarounds

and Upgrade Approach

PRASAD GUDIPATY

MAGDALIE ADOLPHE

RATNAGIRISH NORI

ROHIT PRASAD

Agenda

• R12 upgrade Approach

• Select Features and Workarounds in R12

1. Assign Images to Items display in iProcurement

2. R12 Role Based Access Control (RBAC):

Concurrent Program Output and Log file sharing

using

3. Workaround to use custom payment format without

re-implementing the format using XML Publisher

4. Use Sub-ledger accounting to obtain the required

accounting entries. Case study for Receivable

Invoices

5. AR Refund Functionality

R12 Upgrade Approach

Discovery Phase

• Functional

• Technical

Project

Kick Off

Build &

Test

End user

learning &

Adoption

Cutover

Functional Discovery

• Module leads assess new features of each module

• Initial discovery & team presentation

Examples:

– AP Invoices have lines

– Buyer work center in Purchasing

– Sub-ledger Accounting

– Banks moved under Cash Management

– Employees & Suppliers are moved under TCA architecture

– Customer screen changed from forms to OA Framework pages(HTML)

• Identify Training needs WHAT’S NEW

Technical Discovery

• Create a complete inventory of all CEMLI(Customizations, Extensions, Modifications, Localizations, Integrations)

• CEMLI Review & Analysis

• Identify the customizations that can be replaced by the standard functionality

• Document and create a repository of all the CEMLI changes required with complexity rating

• Identify most recent CPC (critical patch collections) by module that need to be

applied.


Discovery Phase

• Functional

• Technical

Project

Kick Off

Build &

Test

End user

learning &

Adoption

Cutover

Project Kick off

• Determine the project duration and level of effort

based on initial Discovery phase

• Training needs

• Preview the new features and changes to the

Stakeholders

• On going Stakeholder communication is critical

for a successful implementation


Discovery Phase

• Functional

• Technical

Project

Kick Off

Build &

Test

End user

learning &

Adoption

Cutover

Build Phase

• Perform functional set ups

• Retrofit CEMLIs

• Redo customizations

• Make Descriptive Flexfield (DFF) changes for

the new OA Frame work pages. E.g Some core

forms were replaced with OA Framework pages

• Any public Form folders have to be dropped

and re-created due to underlying object

changes

• Report modifications Contd…..

Build & Test –Things to consider

• Test critical interfaces, FSGs, long running jobs

to check the performance

• 3rd Party integrated software may need to be

upgraded as well

• Test for potential Database Space Issues – Sub

Ledger Accounting will add millions of new rows

• Tables Sequences – Default cache size is 1000

in R12 compared to 20 in 11i. This can cause

sequences to jump by 1000

• Verify Responsibilities and Menu functions

R12 – JRE dependencies

• Desktop and Server JRE compatibility. Dependencies due to

multiple desktop JRE versions unrelated to Ebusiness. Refer

to Oracle Note Id: 393931.1 for detailed certification matrix

and known issues

• When using multiple versions of the JRE between Server and

desktop, you need to use either the Family classid or the

Dynamic classid for IE browsers.

• The Family classid in appsweb.cfg will let you launch any

version of the JRE within that JRE family

E.g:

The JRE 6 family refers to JRE 1.6.x.

The classid "CAFEEFAC-0016-0000-FFFF-ABCDEFFEDCBA" is the family classid value for JRE 1.6.

The JRE 7 family refers to JRE 1.7.x.The classid "CAFEEFAC-0017-0000-FFFF-ABCDEFFEDCBA" is the family classid value for JRE 1.7.


Discovery Phase

• Functional

• Technical

Project

Kick Off

Build &

Test

End user

learning &

Adoption

Cutover

End User Learning & Adoption

• Identify new or changes to existing

processes from 11i

• Identify training effort by module and train

users

• Create customized help manuals

• Train the Trainer approach


Discovery Phase

• Functional

• Technical

Project

Kick Off

Build &

Test

End user

learning &

Adoption

Cutover

Cutover

• Document detailed cutover plan

– Perform multiple test instance upgrade

iterations to document time taken for each step

– Calculate the downtime window

• User Access during downtime

– Clone an instance closest to the downtime and provide to

users to run reports if needed

• Confirm/close all open payments, receipts, perform

month end processing and posting to GL

• Clone a 11i instance to retain many months for

comparison and verification after R12 upgrade

GO LIVE!

Select R12 Features

Adding Item Images

in iProcurement

Adding Item Images in iProcurement

Sample Item Image in iProcurement


• Place Item image files in OA_MEDIA directory

• Via Quotation

– Enter the items into a Quotation

– Choose any “Catalog” Quotation class

– Add a Price break line

– Set the status to “Active” and approve

• Via Blanket Purchase Agreement

– Create BPA Header

– Create Lines

– Submit BPA for Approval


• Navigate to iProcurement Catalog Administrator

Download

Excel

Template


All the highlighted have to be entered manually as

per Oracle standard process using the earlier

created Quotation or the BPA. If BPA has 100

lines, this information needs to be filled in for all

100 lines.

Instead of manually filling in the template, we created a report to output the

template with all the data pre-filled, except for the image file name

This report query joins the catalog table ICX_CAT_ATTRIBUTE_VALUES

to list any previously uploaded image file names along with the new ones


• Recommended size 400 x 400 pixels

• Set the Thumbnail image size by setting

the below Profile Options to 200

– POR_THUMBNAIL_HEIGHT

– POR_THUMBNAIL_WIDTH


Oracle R12 Select features

Concurrent Requests Security


• In 11i, concurrent request log and output files

sharing amongst users was possible via a profile

option. This is obsolete in R12.

• R12 uses Role Based Access Control (RBAC)

We can control users access in viewing requests (Doc ID

736547.1)

All requests submitted by users

All requests submitted by users for a given application

All requests belonging to a program submitted by a user

All requests belonging to a user irrespective of the owning

application

All requests belonging to a user with same Responsibility

(11i functionality)

Instance Set

1


1. Create Instance Set (Responsibility: Functional Developer)

Instance set to allow access of Concurrent Requests run by other users with the

same Responsibility.

&TABLE_ALIAS.request_id in (select cr.request_id from fnd_concurrent_requests cr

where cr.responsibility_id = fnd_global.resp_id and cr.responsibility_application_id =

fnd_global.resp_appl_id)

Role2


2. Create Role (Responsibility: User Management)

Role to associate Grants and Users

Create Grant (next step)

Instance Set

1

Instance Set1 Role2


3. Create Grant (Responsibility: Functional Administrator)

Grant will hold the Instance Set created in step 1.

Assign Object Concurrent Requests

Grant3

Instance Set1 Role2 Grant3


3. Assign Instance set to the Grant (cont..)

4. Assign Role to users (Responsibility: User Management)

Assign Role4

Select R12 Features

Custom Payment formats in R12

Payments in R12

- Payments is a new module

- Payments Manager enables you to process a

payment batch from start to end

- From payments manager you can add/remove

individual payments from the payment batch

- Payment format programs are now in XML

Publisher

- Banks are in Cash Management

Workaround to use existing Custom payment

formats

1

• Invoice Selection

2

• Build Payments

3

• Format Payments (Custom)

4

• Confirm Payments

-Custom Payment formats are not defaulted from 11i

11i

R121

Invoice Selection

2

Build Payments

4

Run additional concurrent

program and re-use 11i

custom format programs

5

Confirm Payments

3

Format Payments (XML Publisher)

Payments in R12

• Table level changes

11i R12

Suppliers PO_VENDORS AP_SUPPLIERS

Invoices

AP_INVOICES_ALL, AP_INVOICES_ALL,

AP_INVOICE_DISTRIBUTIONS_ALL AP_INVOICE_LINES_ALL(new),

AP_INVOICE_DISTRIBUTIONS_ALL

Payments

AP_INV_SELECTION_CRITERIA_ALL, IBY_PAY_SERVICE_REQUESTS,

AP_PAYMENT_SCHEDULES_ALL, IBY_DOCS_PAYABLE_ALL,

AP_SELECTED_INVOICES_ALL, IBY_PAYMENTS_ALL,

AP_SELECTED_CHECKS_ALL IBY_PAY_INSTRUCTIONS_ALL

Banks

AP_BANK_ACCOUNTS_ALLCE_BANK_ACCOUNTS(internal bank accounts),

IBY_EXT_BANK_ACCOUNTS(external bank accounts)

AP_BANK_ACCOUNT_USES_ALLCE_BANK_ACCT_USES_ALL

IBY_ACCOUNT_OWNERS

AP_CHECK_STOCKS_ALL CE_PAYMENT_DOCUMENTS

Banks structure in R12

Cash ManagementTrading Community

Architecture (TCA)

Bank

Bank BranchBank Account

Payables

Receivables

Treasury

Payroll

Select R12 Features

• Sub-ledger accounting - Case

study for AR Invoices

• AR Refund Functionality

Current vs. Required Process

• Current Process:

Oracle Receivables standard functionality does not

allow users to enter multiple receivable account

distributions on an invoice transaction.

• Requirement:

Generate receivable accounting entries based on

Revenue distribution accounts. All segments, except

for the natural account, should be derived from the

revenue distribution accounts.

Current vs. Required Journal Entries

• The requirement is explained below using the following illustration for an Invoice

Transaction. The accounting flexfield has the following five segments:

• Funding Source, Responsibility Center, Account, Program Phase, and Project

– Example: Invoice number “94118” is generated in Receivables for customer “John

Doe” in the amount of $500.00. The Receivable

account is F001-0000000-1126050000-000000-000000 and the Revenue accounts

are as follows:

» A001-B020200-3301100000-CCOA14-140600

» A001-K012800 -3301100000- TPAMNN -300200

– The above illustration would generate the following accounting entry: Current

– The above illustration should generate the following accounting entry: Required

Account Type Account Combination Debit Credit

Receivable F001-0000000-1126050000-000000-000000 500.00

Revenue A001-B020200-3301100000-CCOA14-140600 200.00

Revenue A001-K012800-3301100000-TPAMNN-300200 300.00

Account Type Account Combination Debit Credit

Receivable A001- B020200-1126050000-CCOA14-140600 200.00

Receivable A001-K012800-1126050000-TPAMNN-300200 300.00

Revenue A001-B020200-3301100000-CCOA14-140600 200.00

Revenue A001-K012800-3301100000-TPAMNN-300200 300.00

SubLedger Accounting (SLA)

• In Release 12, Oracle introduces the following relating to SLA:

– New schema called XLA that stores the accounting events within a

centralized repository

– New functionality called Accounting Method Builder (AMB) that

enable users to define and maintain custom accounting rules

• Oracle Release 12 comes with seeded Subledger Accounting Methods

(SLAM). If any of those methods meets your accounting requirements,

you can assign one of the seeded accounting methods to the general

ledger. However, if special accounting rules are required per business

requirement, you can use the Accounting Method Builder (AMB) to

define those rules along with the supporting components to capture

additional information for the journal entry, if necessary.

SLA Component

(AMB)

Supporting

Components

New

Functionality

AAD

JED

Journal Line Types (JLT)

Copy the seeded JLT for the events

which require a user-defined rule.

SLAMSubledger Accounting Method (SLAM)Copy the seeded Subledger Accounting Method and assign

the user-defined Subledger Accounting Method to the general ledger (ex: Accrual with Encumbrance Accounting)

Application Accounting Definition (AAD)Copy the seeded Application Accounting Definition for the

application (ex: Receivables) where the accounting rules has

to be customized. This Includes all the Receivables Event s.

JLD

Journal Line Definitions (JLD)Copy the seeded Journal Line Definitions for only the events

which require a user-defined rule per business requirement.

You can utilize the Oracle-defined rule, if a user-defined rule is

not required.

JLT ADR

AMB

Accounting Method Builder (AMB)

Journal Entry Descriptions (JED)

Copy the seeded JED only if you want to

provide your own description for the

journals

Account Derivation Rule (ADR)

Created new ADR for accounting

segments that should be derived from

the invoice Revenue Distributions .

1. Funding Source or use Oracle

2. Responsibility Center

3. Program Phase

4. Project

AR Invoice Transaction

Example: Invoice number “94118” is generated in Receivables for customer “John Doe” in the amount of $500.00.

User Defined Rules

Note: Oracle seeded rules are not updatable. They have to be copied and customized, if required.

Create Accounting Process

Refund Functionality in R12

AR Customer Refund

-1-Reduce

Revenue and

Transfer the

Amount Owed to

a Clearing A/C

-2-Create

Customer as a

Supplier in

Payables

-3-Create an

Invoice In Payables

for the Customer/

Supplier using

the same Clearing

A/C

-4-Issue Payment

To Customer

11i

-2-

Click on the

Refund Attribute

Tab and Enter

Refund Details

R12

The complexity of issuing customer refunds in 11i no longer exists In R12.

Customer Refund is tightly integrated with Payables. Invoices and refund payments

are generated based on the customer information from Receivables. The supplier

information is not required. Oracle uses the Receivables Activity coupled with

workflow to create the refund invoice automatically in Payables.

-4-Select Refund

Status to view

the Customer

Refund Invoice/

Payment Info

-2-Use the

Refund Attribute

Tab to Enter

Refund Details

-3-Save the Receipt

and Receivables

Automatically Sends

a Refund Request

to Payables

-1-Select the

Refund Activity

From the Receipts

Application

Window

Conclusion

• Communication and end-user participation

are crucial

• In-depth testing

• Ensure compatibility with 3rd party systems

• Multiple upgrade iterations until consistent

results

Documents

Release 12 features work arounds and Upgrade