By Tim Dexter on Dec 20, 2013
This is a great overview of the Financial Statement Generator (FSG) engine from GL in EBS and how Publisher fits into the picture.Thanks to Helle Hellings on the Financials PM team.
With some help from the EBS folks, I recently re-ran a report on the latest EBS environment that stores the seeded content that we ship to customers. The document here (sorry,I had to zip it), lists the reports and their publisher templates. The vast majority are still based on an Oracle Reports extract rather than a publisher extract. I can not say that 100% of the reports have a Publisher template but its close. Hopefully it'll be a useful reference.
For more information on the reports check the specific products' documentation.
There's an urgent update from Steven Chan over on the EBS Apps blog that you need to check out!
Gareth Roberts, founder of Virtuate, a consulting outfit based in New Zealand, came up with a doh! moment for me this week. He has been working with Publisher and trying to get images into his reports that are sitting behind a proxy server. This is all inside E Business Suite so no means to use the JVM proxy settings when the concurrent manager starts up. The support folks found the solution that I had completely forgotten about ... I have been away from EBS too long :(
When the concurrent manager (CM) starts a java based job (concurrent program) such as a Publisher one. It fires up a new JVM instance for it. In their wisdom the CM development folks left an 'options' field on the concurrent program definition where you can add JVM start up parameters.
So to allow Publisher to reach the proxied images adding the following to the options field:
did the trick. Why a Doh! moment? Because we also used the same field when we knew a report was going to be BIG and wanted to increase the memory heap available to that particular report at runtime i.e. -Xmx, -Xmn, etc. You can catch Gareth over on his blog waxing lyrical about all things EBS.
Pieter from support pointed out that if the application requires a proxy server then it can be done at
a more global level, that is via the context file using these CP
[vispb12@pbreugel4 ~]$ grep s_afjsmarg $CONTEXT_FILE
<AFJSMARG oa_var="s_afjsmarg" osd="Linux">-server -Xmx384m -XX:NewRatio=2 -XX:+UseSerialGC -Doracle.apps.fnd.common.Pool.leak.mode=stderr:off -verbose:gc</AFJSMARG>
[vispb12@pbreugel4 ~]$ grep s_afjcparg $CONTEXT_FILE
<AFJCPARG oa_var="s_afjcparg" osd="Linux">-client</AFJCPARG>
More on that approach here -
Friends of BIP, STR Software have put together a great web based resource 'BIP University'
Focused on the E Business Suite flavor and their own integrations with BIP under EBS R12; its a great resource and well worth a few clicks and a read. Check it out here - http://www.bipuniversity.com/
It's here, its been here for a while and I have only just found out! You can delivery your concurrent request outputs using BIP in EBS! You can print, email, fax, ftp! There is a caveat, you need to be on 12.1.3.
Being the lazy or perhaps smart cookie that I am, I'm not going to re-invent the blog post. Im going to blatantly link to friend of BIP, Brent Lowe's series of posts on the integration:
BI Publisher has always supported the EBS (Oracle E-Business Suite) security as one of the security model options. However, when it comes to the EBS data level security there was no straight forward way to support it before. And this has prevented many folks from moving to BI Publisher Enterprise Server for the EBS reporting even when we know that BI Publisher Enterprise Server would provide a great deal of benefits that come with it such as Data Model Editor, Layout Editor, Interactive View, just to name a few. So, we added the EBS data level security support with the latest release of 126.96.36.199 to help our EBS customers to move to BI Publisher Enterprise Server and take advantage of such benefits. I created a quick video demo for this new feature, if you are interested check the following video.
If you prefer reading or like to know more detail please continue.
If you are familiar with EBS you probably know the data level security comes with the responsibility and org_id combination. Each responsibility is associated with an org_id and the user selects a responsibility before running a report. And many of the EBS database views, which typically many of the EBS reports query against, use the org_id to filter the data. Therefore, based on your selection of the responsibility you will get a different set of the data for a single report. And of course this means that another user with a different responsibility would see a different set of the data from the one you would see.
And that’s exactly what we did with BI Publisher Enterprise Server with the release of 188.8.131.52. Now the user can select one of the responsibilities that are assigned to the user at the login time or from the My Account profile setting. Once the user select it BI Publisher automatically takes care of that by setting an application context passing the org_id when it opens a EBS database connection for the user.
There is no extra configuration to enable the Role Based Data Security at all. Once you have integrated your BI Publisher Enterprise Server with your EBS by selecting ‘Oracle E-Business Suite’ as the security model and upload the EBS application dbc file, then BI Publisher will take care of all the security related stuff from there based on the user’s selection of the responsibility!
Right after you login to BI Publisher Enterprise Server with your EBS user id and password, you will be asked to select one of the responsibilities assigned to you. Once you select one then it’s all set. Any following database query will have the application context with the org_id that is associated with your responsibility. 1. Login to BI Publisher Enterprise Server with EBS user id and password.
2. When you login you’ll be asked to select one of the responsibilities you have. And BI Publisher will use this information to support the EBS role based security.
If you want to change the responsibility after you have logged in then you can go to ‘My Account’ dialog by clicking your username at the right hand side top and select one of the responsibilities listed under ‘Group’ tab.
Here is a sample report ‘Customer Open Balance Report’, which I have migrated from the EBS instance by using the BI Upgrade Assistant Utility and added some report layouts. The following screenshot shows when I select a responsibility ‘Receivables Vision Germany’.
When I change the responsibility to ‘Receivables Vision France’ in the My Account dialog box, now I get a different set of the data.
The above example is based on the RTF template that I have downloaded from the EBS instance, which is one of the out-of-box report layout templates that come with EBS R12, and uploaded to this report. Now, because I’m in BI Publisher Enterprise Server I can use the Layout Editor, which is the pure web browser based report design tool, so I created a similar layout with the Layout Editor. Here is the one.
And, one step further, since I can now use the Interactive capability of BI Publisher Enterprise Server why not create another layout that takes full advantage of that ! And here is the one.
This sample layout actually shows the Role Based Data Security much more obvious. The above example is when I select ‘Receivables Vision Germany’ where you can see the Country list shows ‘DE’ and ‘US’. The below example is when I select ‘Receivables Vision France where you can see the Country list is showing ‘FR’ and other components in the report showing a different set of data compares to the above.