FAHRCS EBS and Accounting Hub

Procedures for a Fusion P2T

Contents
Pre-Requisite Functional Procedures in Accounting Hub Before PT2 Refresh: ............................................ 3
After P2T Refresh – Procedures Before Re-initialization of EBS Test to Accounting Hub Test:................... 3
EBS Procedures ......................................................................................................................................... 3
Accounting Hub Procedures ..................................................................................................................... 5
Re-initialize EBS Test to Accounting Hub Test .............................................................................................. 6
Accounting Hub: Post PT2 Refresh: Additional Functional Procedures ...................................................... 7
Post P2T Refresh: Functional Procedures - If you are not live with FAHRCS (EBS Prod to Fusion Prod) ..... 7
Final Functional Procedures (After all other EBS and Fusion Technical Procedures): .................................. 8
Important Note: Our recommended approach is to do a P2T refresh of FAHRCS Cloud at the same time
as EBS P2T refresh and is documented on My Oracle Support Doc ID 2034564.1 in the Known Issues
section. See issue called Environment Strategy.

This following document describes the process to follow if you have done a P2T Refresh on FAHRCS
Cloud without doing a refresh of EBS test from production, which is not Oracle’s recommended
approach.

Pre-Requisite Functional Procedures in Accounting Hub Before PT2

Refresh:
--There are no functional procedures necessary unless the 'Test environment' has certain FR reports that
are the latest versions. If this is the case, you need to backup FR reports from test.
--See this link:

http://docs.oracle.com/cloud/latest/financialscs_gs/FAIGL/toc.htm

-Then select link for Chapter 16 Financial Reporting

-Then select link for topic called ‘Migrating Financial Reports: Instructions’

After P2T Refresh – Procedures Before Re-initialization of EBS Test to

Accounting Hub Test:

EBS Procedures

EBS Step 1: Clear FAH related profile option values

Go to System Administrator responsibility and clear profile option values for below profile
options.
GL: Applications Coexistence Fusion User
GL: Applications Coexistence System Identifier

EBS Step 2: Bump up FAH related sequences on EBS

DECLARE
l_seq NUMBER;
BEGIN

FOR l_idx IN 1..10000

LOOP
SELECT GL_COEXIST_XFR_S.nextval
INTO l_seq FROM dual;

SELECT GL_INTERFACE_CONTROL_S.nextval
INTO l_seq FROM dual;
END LOOP;

EBS Step 3: Clean up FAH related tables on EBS

a) Backup following tables

gl_xfr_ledgers
gl_xfr_system_ledgers
gl_xfr_ledger_mappings
gl_xfr_periods
gl_xfr_led_map_periods
gl_xfr_segment_values
gl_xfr_cloud_systems
gl_xfr_coa_values
gl_xfr_fr_accounts
gl_xfr_ledger_options
gl_xfr_source_systems
gl_xfr_tracking
gl_xfr_interface
wf_event_subscriptions

b) Delete data from previous integration

delete from gl_xfr_ledgers;

delete from gl_xfr_system_ledgers;
delete from gl_xfr_ledger_mappings;
delete from gl_xfr_periods;
delete from gl_xfr_led_map_periods;
delete from gl_xfr_segment_values;
delete from gl_xfr_cloud_systems;
delete from gl_xfr_coa_values;
delete from gl_xfr_fr_accounts;
 delete from gl_xfr_ledger_options;
delete from gl_xfr_source_systems;
delete from gl_xfr_tracking;
delete from gl_xfr_interface;
delete from wf_event_subscriptions where event_filter_guid in (select guid from wf_events
where name like 'oracle.apps.gl.CoEx%');

c) Commit the changes

commit;

Accounting Hub Procedures

NOTE: If Accounting Hub PROD instance was integrated with EBS Prod environment, perform
steps AH1 through AH3 on the refreshed Accounting Hub TEST environment

If you did never integrated EBS Production to Accounting Hub Production, skip AH1 through
AH3, and proceed to the section called ‘Re-initialize EBS Test to Accounting Hub Test ‘..

AH1: Delete Registration Record in the refreshed Accounting Hub Environment

- Sign into Oracle with a user that has access to Setup and Maintenance work area.
- Navigate to Setup and Maintenance work area in the Functional Setup Manager.
- Search on the task called ‘%Coexistence%’.
- Select the task called: Register Applications Coexistence Instances for E-Business Suite.
- Select the Go to Task icon.
- Delete the registration record that has Cloud in the name.
- Save the changes.

AH2: In Accounting Hub, rename the EBS transferred ledgers that are present from previous
integration.

- Sign into Accounting Hub.

- Navigate to Setup and Maintenance work area.
- From the Task panel, select Manage Implementation Project.
- Select the New icon.
- Provide a name.
- Save and Open the Project.
- Select the Add ion (green plus).
- Add the Task list called Financials.
 - Select Apply.
- Wait until the task list appears in the background.
- Select Done.

NOTE: You can rename as many ledgers as you need within 1 implementation project.
However, each time you re-initialize from EBS to Fusion Accounting Hub, and you need to
change the ledger names, you must define a different implementation project.

a) Expand the Task List: Financials > Define Common Applications Configuration for Financials >
Define Ledgers > Specify Ledger Options.
b) Select Scope.
c) Select Specify Ledger Options radio button.
d) From the Primary Ledger drop down, select the Select and Add option.
e) Click Apply and Go to Task.
f) Select your EBS Ledger.
g) Click Save and Close button at the very bottom.
h) Rename the ledger.
i) Save and Close.

AH3: Rebuild the GL balances cubes.

--The reason this is necessary is that P2T refresh copies the database , however, it does not refresh the
Essbase server. The old Test Essbase cubes will still remain, and will still have cubes with data from Test
before it was refreshed.

--See this link: https://docs.oracle.com/cd/E51367_01/fa_lcm_gs/OACLO/cloning.htm#OACLO333

-Run the ESS request called "Create Balances Cube" to rebuild the cube (Navigator-->Scheduled
Processes-->New Request)

Re-initialize EBS Test to Accounting Hub Test

In EBS, navigate to SetupOtherFusion Accounting Hub Reporting Cloud Service.

Fill in information similar to how you did previously. Follow procedures in white paper on My Oracle
Support Doc ID 2034564.1 to re-initialize.
Accounting Hub: Post PT2 Refresh: Additional Functional Procedures

1) Migrate FR reports from Production to Test:

--The reason this is necessary is that P2T will remove the FR reports on Test. They will not appear until
they are migrated from Production (or restored from a backup for certain report if necessary that you
take from Test before PT2)
--See this link:

http://docs.oracle.com/cloud/latest/financialscs_gs/FAIGL/toc.htm

-Then select link for Chapter 16 Financial Reporting

-Then select link for topic called ‘Migrating Financial Reports: Instructions’

2) For any FR reports where test had the latest version, and you backed up those FR reports in Test (in
Pre-Requisite Functional Procedures), now migrate them to 'Refreshed Test environment' now.
--See this link again:

http://docs.oracle.com/cloud/latest/financialscs_gs/FAIGL/toc.htm

-Then select link for Chapter 16 Financial Reporting

-Then select link for topic called ‘Migrating Financial Reports: Instructions’

3) Migrate Allocation Rules - If you have created allocations rules in test that you want to keep you will
need to migrate them

--See this link:

http://docs.oracle.com/cloud/latest/financialscs_gs/FAIGL/toc.htm

-Then select link for Chapter 10 Period Close

-Then search in browser on this: Migrating Allocation Rules: Instructions ‘’

Post P2T Refresh: Functional Procedures - If you are not live with
FAHRCS (EBS Prod to Fusion Prod)
If you are not yet live with FAHRCS, then you may not have any financial reports in Production.
Therefore, the copy from Production to Test will not have any FR reports.
In this scenario:

1) Migrate FR reports from the backup of FR reports from Test before Test got refreshed. See
Step 3 in Section above
2) You can also re-generate the seeded Autogenerated Financial Reports in your refreshed
Accounting Hub Test environment. Run the following ESS request in Accounting Hub (Navigator-
>Scheduled Processes->New Request). Submit the request called ‘Create Autogenerated
Financial Reports’.

Final Functional Procedures (After all other EBS and Fusion Technical
Procedures):

1) Run an FR report in Accounting Hub Test environment.

--Verify Drillthrough to Detail Balances in Accounting Hub and drill to EBS, and ensure that it is the
correct EBS environment.

2) If you don’t have a working FR report yet (for some reason), you can immediately go to the
Accounting Hub Inquire on Detail Balances user interface, and test drill to EBS from there.

-Navigator->Financial Reporting Center-> Inquire on Detail Balances.

-Enter query criteria, and Search on balances. Select link on Period Activity to Drill to EBS. Very that it is
the correct EBS environment.

NOTE: You still should complete #1 Running an FR report and drill to EBS.

3) Post a simple 2 lines $.01 entry in EBS Test environment.

--Run EBS concurrent program 'Transfer Setups and Balances to Accounting Hub Reporting Cloud
Service'
--Run an FR report and drillthrough to Detail Balances (or navigate to Inquire on Detaill Balances)and
ensure that incremental balances were posted to Accounting Hub. Then drill to EBS (and ensure that it
is the correct EBS environment). You can reverse this journal later in EBS if you wish.