Ideas for VBA coding

[PW25]

Hi all,

in case you have new ideas for VBA coding, enhancements or use cases, please post them right here.

[vvdor]

Possible idea: draw separator-lines between a group of key figures, i.e. whenever the product ID changes, or Customer ID changes, etc. Like that, the data in large views is visually separated and is easy to read.

[PW25]

Thanks for your feedback. Let me follow-up on that topic.

[PW25]

We would like to provide this feature native using the IBP formatting sheet. I added it to our backlog.

[ayanbishnu]

@PW25 thanks a lot for adding it int he backlog. For the meantime i have coded in VBA and it is working fine. only downside for the development is user have to refresh the planning view as i have provided them with a activex checkbox, where if checked the custom format will be executed and if unchecked standard format is displayed.

I have attached the excel macro templates and also the modules has been saved separately as .BAS file.

Redbull.zip

[ayanbishnu]

We have a formatting enhancement for our planning views. We would like to activate the option "repeat row headers" but in a way that only the first row is shown. All repeated rows should have the same text color as the background.
Please refer to the attachment. The headers should be repeated only in the yellow rows (not in the ones between as well). Please help and advice.

[PW25]

We would like to provide this feature native using the IBP formatting sheet. I added it to our backlog.

[ayanbishnu]

@PW25 thanks a lot for adding it int he backlog. For the meantime i have coded in VBA and it is working fine. only downside for the development is user have to refresh the planning view as i have provided them with a activex checkbox, where if checked the custom format will be executed and if unchecked standard format is displayed.

I have attached the excel macro templates and also the modules has been saved separately as .BAS file.

Redbull.zip

[Verheyen-Vincent]

@PW25 @JVotteler Would it be possible to provide a snippet of how it would be possible to unallow the removal of a filter from a certain Planning View Template's worksheet (after having opened it via New View > From Template ...).

Perhaps code-inspiration could be found in the IBP web UI Global Configuration parameter "FORCE_PLANNING_VIEW_FILTER" (Description: Force user to set up an attribute-based filter in planning views)?

The goal is, that one can disallow the removal of a Planning Filter's attribute, for a certain Planning View's sheet only. The default Planning Filter that comes with a Planning View Template, for example, might be called PRODUCT GROUP XYZ, and might be defined as Product Group = XYZ. The requirement for business now is that users (when loading a Planning View from the template) are not able to remove this filter (of Product Group).

[Verheyen-Vincent]

Please see #13

[PW25]

Hi @Verheyen-Vincent. Sorry for the huge delay. At the moment there's no ideal option to achieve this scenario. We only have the filter options defined in https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/b28ffdd739bf45678ef36c44e64652d7/fb0633785cc94fc8a3776827e6338df0.html?locale=en-US. Improving this feature is on our list, but not yet assigned to a release. Ideally you can define during the template creation what attributes and values shouldn't be removed from the planning view.

[Verheyen-Vincent]

@PW25 + Another question I have would be on how, best-practice, to throw an error message when, in a certain Planning View, there is 1 of a certain amount of pre-defined attributes (the base planning level of a certain Key Figure) not present in the Planning View.

https://github.com/SAP-samples/integrated-business-planning-excel-addin-vba-samples/blob/main/VBA%20samples/SAP%20IBP%20Hooks/Sample%20code%20for%20SAP%20IBP%20Hooks.pdf already shows a code for 'If the opened worksheet includes the master data type "Product"

However, this is for Master Data Workbooks. My question is how to do the same for a Planning View.

[Verheyen-Vincent]

I have created a seperate for discussion for this topic here: #12