cancel
Showing results for 
Search instead for 
Did you mean: 

Nakisa OrgChart 3.0 SP3 Role/Security

Former Member
0 Kudos

We are using OrgChart 3.0 SP3 Build 0703030900 using SAP_Live2. 

We have created two org charts both using static Org Unit Root.  One (custom) is configured to start at the top of the Org Structure and the other at an Org Unit that is deemed logical for the company.  The custom one is using the same logic as the SAPOrgUnitOrgChart.

The SAP roles created are just shell roles i.e. no authorization and are mapped to the Nakisa Roles.

When I assign the user (with SAP_ALL) the SAP role that corresponds to the Nakisa Role – ROLE_MANAGER, I get a short dump in the backend when I select the custom org chart - CONVT_NO_NUMBER - Unable to interpret "ID" as a number.

When I assign the user the SAP role that corresponds to the Nakisa Role – ROLE_HR, I do not get the short dump.

I initially thought it was because the Nakisa ROLE_MANAGER only allowed user to view Org Unit assigned and down, but the one that is configured to start at the logical fixed Org Unit does not dump.  This org unit is not the assigned to the user.

Any ideas/thoughts....

Thanks

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Luke

OK - I switched the starting root for the standard to start at the top of the hiearchy and the custom to start at the org unit defined by the customer.  It does not produce any more dumps. 

However, I do fine this odd that switching the units does not cause a dump.  If it was configuration or bad data, the dump should still occur.   

Thanks for the help.

Kim

lukemarson
Active Contributor
0 Kudos

Hi Kim,

Did you resolve this?

Best regards,

Luke

Former Member
0 Kudos

Hi Luke

The custom org unit is using the same data element as SAPOrgUnitOrgChart i.e. SAPOrgUnitOrgChartTypeOHierarchyDataElement.

All I did was create a custom org chart that has the same information as the SAPOrgUnitOrgChart one.  Then in the hierarchyconfiguration file - told it to use the same information as the SAPOrgUnitOrgChart (so, I would not have to create the data element, since it is using the same data, the difference is where I am starting the hierarchy).

Please note when I select the SAPOrgUnitOrgChart hierarchy I do not get a dump.  It is only when I select the custom one.

Thanks

Kim

lukemarson
Active Contributor
0 Kudos

Hi Kim,

If you change the OrgUnit root of your new custom OrgChart to the same as the standard, do you still get the error? If you don't, then it is likely that there is some bad data in your org structure. If you do get the error then there is probably something wrong with the configuration.

Best regards,

Luke

Former Member
0 Kudos

Hi Luke

The new org chart is basically a copy of the SAPOrgUnitOrgChart except it starts at org unit 1, where as SAPOrgUnitOrgChart would start at 50.

The hierarchyconfiguration file, is a copy and paste job of the SAPOrgUnitOrgChartTypeOHierarchy file. 

The xsl files are a copy and paste of the standards i.e. ou_standard, where it would mention the original configuration, just changed it to point to the custom one.

Thanks

Kim

lukemarson
Active Contributor
0 Kudos

Hi Kim,

The problem is in the data element or the data itself. What did you do to create your data element?

Best regards,

Luke

lukemarson
Active Contributor
0 Kudos

Hi,

Can you provide an overview of the configurations you have performed for the new orgchart?

Best regards,

Luke