A few weeks ago, a colleague of mine, ask me how he can get the calendar week to use it in the Analysis Office API SAPSetFilter. I developed a short macro which defines the calendar week to use it in 0CALWEEK. Maybe someone has another solution for this.
First we need different variables:
Dim lresult As Long
Dim week As Integer
Dim today As Date
Dim yearCalWeek As String
In this thread on blogs.sap.com, Michael Hamm asked how to hide or deactivate the Customize User Interface button. At first, at the moment SAP doesn't offer any checkbox which you can check and uncheck in the settings.
But there is a solution how you can hide or deactivate the Customize User Interface button. It is called MinorVersion. The official admin guide define MinorVersion like this:
You use this setting to specify the minor version that should be used. The default value is the integer value of the installed version, for example value 3 for version 2.3. If you change the value to 1, version 2.1 will be used.
In the comments of this blogpost on blogs.sap.com, Stephen Hobbs showed his idea of insert a product Image besides the crosstab in combination with the new Customize User Interface function. So I make my own thoughts how I can realize a thing like this.
My first thought was, where can I store the pictures and how can I get a product number and the picture together. The solution is very easy, I created a folder on my hard drive and put the pictures in it. The name of the pictures are the same like the product numbers.
In Analysis Office 2.4 SAP improved the Table Design Editor. You can now create and edit formulas. In an earlier post, I described how to work with Excel formulas in a crosstab. You can add a new column with the table design functionality.
There are also some changes in the User Interface Customization.
You can now create, delete and reorganize groups and elements. A nice feature too is when you create a toggle button, you can get the button state. This I haven't tested yet, but it could be very useful. About the file system settings:
In my current project, we have a copy of the productive system as a maintenance system, because we made huge changes in
the development system in case of the project. So if there is an error in the production, we can easily repair it.
Some changes have also be transported into the development system, so we have the same state and our future request can be transported into production. For this we use the functionality Transport of Copies. All objects of the originally request are still locked. If you want to create a transport of copies, open the transaction SE01. Check the option “Transport of Copies” and click on Display.
After we created in Part 1 the transparent tables and in Part 2 all BAdI implementation, we can now maintain and create our SPO. First we have to fill our table ZSPOPATTERN with a PATTERNID and a corresponding INFOOBJECT. Go to the se16 and create a new table entry. As PATTERNID enter a unique id for example CALYEAR and as INFOOBJECT 0CALYEAR. For TXTLG and TXTSM enter a useful text. Depending on how many InfoObject are used for a partition, create the other pattern.
After we created in part 1 all tables and objects, we can now create a new BAdI to generate the partitions. Go to the transaction se19 and create a new implementation with the Name RSLPO_BADI_PARTITIONING.
At my current project I needed a way to create Semantic Partitioning Object (SPO) via BAdI to reduce the end-of-year work. After a little search via Google (you cannot find anything on the new SAP Community Page), I found these threads.
Both were not perfect, so I build a solution between them. I also put everything via control tables, so it would be easier for the users to manage them. So let's get started.
After I started my BW/4HANA instance on cal.sap.com and everything was working, I logged on and typed RSA1. But there was no modeling tab anymore. Then I rememberd, I need the BW Modeling Tools. So I installed the latest Version of Eclipse and the BW Modeling Tools. After that I need a Project. The project is the binder for all activities in our BW system. Make a right-click in the Eclipse Project Explorer and choose BW Project.
A new feature of Analysis Office 2.4 is workbook or sheet protection. It is similar to the Microsoft Excel Protect Sheet / Workbook function, but it is also different. When you need to protect your workbook or sheet and you use the Excel functionality, you can not refresh or drill down your Crosstab. But when you want to refresh your data or give the users the opportunity to drill down or filter, you have to use the workbook / sheet protection from Analysis Office.
And also these parameters:
Only then AppBuilderCompanyProfileDirectory is a PerMachine parameter, the others are UserRoaming. How the other parameters exactly work has to be tested. The Ao_app.config also provides new parameters:
So it can be possible that the user can choose between the old BEx Query Designer and the new BW Modeling Tools. The default parameter is "0", so at the moment I cannot say what exactly has to be the value for other query designers. The parameter DoSelectorHierarchyExplicitSelection should select only the child nodes of a node and the parent node is not automatically checked. But I haven't got a chance to test this. So I can't confirm this. I don't know at the moment how the parameter AutoCompleteFetchMemberLimit works, I only know the default value is 30. But as soon as possible I add these information to this post.
So after I read a lot about BW/4HANA, I decided to create a own SAP BW/4HANA 1.0 [Developer Edition] instance on my Amazon AWS account. First I had to extend my normal AWS account with a IAM user. For this you choose under Security, Identity & Compliance >> IAM. Under Users you click on Add user.
Dim boInfoStore as InfoStore
Dim boEnterpriseService as EnterpriseService
Dim boInfoObjects as InfoObjects
Dim boEnterpriseSession as EnterpriseSession
A new feature of Analysis Office 2.4 is that you have a function called Customize User Interface. On the first view it looks similar to the Excel customize ribbon function. But it has more flexiblity to switch between different interfaces. First you have to open the Customize User Interface dialog via File >> Analysis. The following dialog appears.
Since yesterday Analysis Office 2.4 is available. You can download it with a S-User under Support Packages and Patches >> By Alphabetical Index (A-Z) >> A >> SBOP Analysis Office >> SBOP Analysis MS Office 2.4.
The SAP help page isn't updated yet. But I think it would be updated in the next days.
After you added these two dlls, we can build a test application in Visual Studio. We need a new button, which test if we have a connection to the BI platform. First we need a session manager.
This week I want to test the integration of a BI Platform to my .Net program. So I want to install a test version of the BIP, but my virtual machine hadn't enough space. The first step was to extend the space of the disk. It is very easy in VirtualBox to extend the disk.
After my VirtualBox was ready I could install the BIP. But the next issue was found very soon. I need a license key.
So it is done, Part 2 finally is written and an example is uploaded to github. It took me about 8 months to release Part 2 of these series. Part 1 was released in March 2016 and now I had time to write an example for Part 2 and upload it to github. Part 1 discover the basics about a RFC Server with the SAP NCo Connector, part 2 now explain how to build a RFC Server more flexible.
First you have to create a new Microsoft Visual Studio project. In my case it was a Windows Form Application. I add some labels and textboxes so it look like this: