Professional Documents
Culture Documents
Fusion Financial Accounting Hub V 1.0
Fusion Financial Accounting Hub V 1.0
B) SCOPE/OUT OF SCOPE................................................................................................................................................3
BUSINESS CASE............................................................................................................................ 4
D) METHODOLOGY..........................................................................................................................................................4
E) BUSINESS EXAMPLE....................................................................................................................................................4
SET UP STEPS.............................................................................................................................. 7
F) STEP BY STEP GUIDE TO FAH CONFIGURATION..........................................................................................................7
B) Scope/Out of Scope
This white paper will cover followings:
c) Upload csv file containing transactions from Custom Application to Fusion Application
E) Business Example
Customer uses fusion financials to perform her standard financial transaction and its accounting.
Additionally Customer has custom application to handle her specific business transactions. To have
central repository of accountings customer need to pass accountings of transaction from custom
application, to Fusion General Ledger.
Customer creates two invoices in custom application. From Custom Application, transactional details
would be interfaced to FAH. By using FAH configuration for the custom application, FAH would create
compatible (compatible to Fusion GL) accounting of the interfaced transactions and post to GL.
In custom application there are two standard invoices and details of those are as below
o First invoice is for below items purchased from a domestic supplier for
Requirement is, create accounting of above invoices. The generated accountings should be compatible
to Fusion GL.
To understand compatibility of accounting to Fusion GL in the example explained, let’s review Account
Structure of Fusion GL, (In other words Chart of account (COA)) has following 5 segments:
Segment1: Company
Segment2: Department
Segment3: Account
Segment5: Product
In our example, derivation of value for Segment3 will depend on transactional data in custom
application and for all other segments we will use following default values:
Segment1: 01
Segment2: 000
Segment4: 0000
Segment5: 000
Invoice#2
a) FAH Configuration - Configure FAH to generate expected accountings for transaction from
custom application.
c) Account the transactions using FAH configuration and review the same.
This will download excel template to local drive. Open the file and enter application data as per
instruction provided in template.
After that click on Upload Setup File and upload the zip file stored in local drive.
This will create application and related data model as per setup data entered in excel template.
We are going to use XXINV event type in test case used in this paper.
TRANSACTION_TYPE H XX_INV
LEDGER_NAME H SPL
TXN_TYPE H INV
TXN_SUBTYPE_1 H STD
After defining custom application and its source data, next step is to define accounting configuration.
Above set up maps Type of item purchased (LN_ID_1) to respective natural accounts in Fusion GL.
Above accounting rule is to derive natural account for Charge line based on Mapping set
XX_CHARGE_NATURAL
Above accounting rule is to derive natural account for Charge line based on Mapping set
XX_LIAB_NATURAL
This completes configuration for Account rules. We defined three account rules shown as below:
Navigation: Define Accounting Entry Configuration for Rapid Implementation> Define Accounting Rules
for Rapid Implementaion>Manage Journal Line Rules
One by one add both Journal Line Rules defined in previous step to Journal Line Rule Set.
For Journal Line Rule XX_LIAB, account would be derived by overlaying natural account from rule
XX_LIAB_AR on account derived by account rule XX_CONSTANT
For Journal Line Rule XX_CHARGE, account would be derived by overlaying natural account from rule
XX_CHARGE_AR on account derived by account rule XX_CONSTANT
Note: Status is Incomplete for Rule set XX_JER assigned to accounting method
Activate the edited Accounting method by navigating to Action drop down
Set Respective Data Access Set and navigate to “Review Subledger Journals”
Verify journal entries created isa same as described in Business Example Section.
Similary we can import data file for Invoice from Domestic supplier and review its journal.