Hello Hello!!! So you want to write back to Oracle Fusion Cloud. Well lucky for you someone has done this before. Oh by the way, you should probably stick to the Oracle instructions below if you do not like 90’s Hip Hop music (this sentence was written after finishing this post, apologies in advance to all who proceed)…
To their credit the Oracle Documentation on this isn’t too bad (there are minor errors, but should be fine), for reference here is a pretty good link for the Oracle Documentation.
Also here is a sales video, no doubt someone might want a high-level overview, this will do the trick for you:
Now I assume you just want the low down, so I will stop wasting time and get to the “this is how we do it”, wow I feel like Montell Jordan and its 1995. Wow song is really stuck in my head.
- Log in to Data Management in PBCS -> Setup Tab ->Source System (back of my mind tune playing “this is how we do it, this is how we do it, La Ra Ra “)
- If you haven’t done so as part of loading data to PBCS; go to Configure Source Connection, this should be to an Oracle Fusion Cloud Service, ensure to Test Connection -> Configure -> Initialize (You will need to update the WSDL URL format: https://server/publicFinancialCommonErpIntegration/ErpIntegrationService?WSDL). Go to Workflow->Process Details and confirm initialization ran successfully. Go to Setup->Target Application and confirm the new Fusion GL Essbase application exists, will be called something like <cubename>AccountingFlexfieldStr (“It’s Friday night, and I feel alright, The party is here on the West side”)
- Go to Setup->Import Format, then click Add to Create an Import Format. Ensure your source is EPM Planning Application or ASO Cube. Save and apply the required mapping. You will not map scenario as this is handled via the Category Mapping in FDMEE/Data Management (“I’m Kinda buzzed and it’s all because, this is how we do it”).
- Go to Location and Add/Create a Location, no rocket science here. (“South Central does it like nobody does, this is how we do it”).
- For Period Mappings I assume you have loaded from Fusion so won’t go into detail about what this needs to be as the default period should apply (“To all my neighbors you got much flavor, this is how we do it”).
Go to Workflow->Data Load Rule, select Location and choose the location created above. Then Add and create a new Rule to Write-Back data to Fusion. Ensure to select the appropriate Category, if not present you will need to create in Category Mapping and ensure you select the appropriate source plan type (“Let’s flip the track, bring the old school back, this is how we do it”).
- Start applying the filters on the source data coming from Hyperion to get the exact output you would like. Ensure you apply filters for all dimensions, this is best practice to ensure you are getting exactly what you want. Most of the time you will be extracting either level zero of a dimension or a specific member or members, so being precise now means the right data ends up in Fusion.
- You will need to create mappings, go to Data Load Mapping and create there. A lot of times dimension members in Hyperion are prefixed to distinguish the dimension members across dimensions for example Account 1001 in Hyperion maybe A1001 and Project 1000 maybe P1000. Now that we are going back to Fusion we must provide the codes as they exist in the source. What this means is that on the way in the members would be given a prefix, but on the way out it needs to be removed. I am not going to go through FDMEE mappings in detail, this knowledge is assumed. A mapping like A_* to * would usually be all you need (refer to this link for more mapping information ).
- In the Data Load Workbench run the import fish to check your mappings are as expected. Once happy export the data to Fusion by clicking Export.
- Login to Fusion to verify the data. Tip you can do this check via a Smart View connection to Fusion.
A key thing to note is that there is no way at present from PBCS to clear the data in Fusion prior data load/write-back to Fusion, this has to be done manually in Fusion via reversing existing numbers or entering zeros. Hope this gets improved in the future as would be really nice for this to be one process or actioned as part of the write-back.
You may think the force is not with you, but it is!
Hi Jedi, do you know whether there is a way to export zeroes from PBCS into Fusion?
I have not tested this but you can try disabling zero suppression with instruction in this link: https://docs.oracle.com/cloud/latest/epm-common/ERPIA/disabling_zero_suppression.htm.
I am not a fan of this approach as the data in fusion is stored in an Essbase ASO cube and in PBCS is stored in Essbase ASO/BSO and sending back zero’s is not ideal in the target or even to store in source for send to target.
I think I know why you are asking this (my guess is you want to clear the write-back values in the scenario you are writing back to with the updated/changes values in PBCS). Whatever you are doing proceed with caution and please test in your test environment. I would suggest reviewing this Oracle article and see if that helps you process. https://support.oracle.com/epmos/faces/DocContentDisplay?id=2301945.1
This approach will give you the ability to delete all data in the target scenario in fusion prior write-back (key words in the above “all data”), it is not selective.
Hyperion Jedi (Ahmed Hafez)
May the force be ever in your favour
1) Can we take PBCS ASO cube as Source to writeback to Oracle Financials.
2) Can we do writeback to high level members of Oracle Financials from BSO PBCS cube?