Nakisa 4.0 OrgManager - Created position not showing / not linked to Org Unit

[Former Member]

Systems:

Nakisa OrgManager 4.0 build 0901009600

SAP ECC6 Ehp6

Hi,

I'm configuring OrgManager in addition to OrgChart which is operational.

I have done the basic setup according to what I have done for OrgChart.

The user that I user to log in is mapped to the role Executive and nothing is protected.

When I log in I get my org structure.

When I right click on an org unit, I can choose the option "create position".

I create the position on date of today.

When I add, the systems gives message

However, the position is not shown in the org structure.

When I look in SAP, the position exists, but is not linked to any org unit.

When I manually link the position to the correct org unit in SAP, it shows just fine.

Any ideas what I might me doing wrong here?

Kr,

Gerrit

[Former Member · Accepted solution]

Hi,

So, my analysis was correct. SAP makes no check in SPECIFIC_INITIAL_COMPUTATIONS on l_p1001 whether it is initial or not before calling method check_external_relation.

That's a bit uncareful because if for some reason, somebody was tinkering with table T77EV and accidently saved a value without a key, this erronous value gets returned every time the method check_external_relation and no hrp1001 entries will be saved anymore. Hence, breaking the whole of Org Modeler. The quick solution is to remove the entry with an empty key from the table.

I'll also communicate this to Nakisa, because maybe it is useful form them to pressure SAP to add this simple check in the ABAP code since not having that check can mess up Org Manager.

Kr,

Gerrit

[lukemarson · Accepted solution]

Thanks for the update Gerrit!

[Former Member]

Hi,

As suggested I have opened an OSS note for this.

I could have solved it by making a repair to SAP standard code, but I prefer logging an official message so hopefully the problem can be solved in an official way. That way hopefully future implementors of OrgManager don't run into the same issue.

When I have feedback on the note I will post the replay or suggested solution here.

Kr,

Gerrit

[lukemarson]

Hi Gerrit,

Did you get a response from SAP yet?

Best regards,

Luke

[Former Member]

Hi Luke,

Both SAP and Raagi Pandya from Nakisa have been/are looking at this now.

I'm looking at a possible solution now that could resolve the issue (but that still would not prevent it from happening again in the future).

Anyway, I will test this asap and formulate an answer here on the forum.

Kr,

Gerrit

[lukemarson]

Thanks for the update Gerrit!

[lukemarson]

Hi Gerrit,

What does the log say after you perform this action?

Best regards,

Luke

[Former Member]

662. 09 apr 2013 15:22:23 ERROR com.nakisa.Logger  - Nakisa.SAP.EP5Processor.Hrpdv_Service_Create_Position : Position has been successfully created. (Assisstant Test)

663. 09 apr 2013 15:22:23 ERROR com.nakisa.Logger  - Nakisa.SAP.EP5Processor.Hrpdv_Service_Position : External relationship could not be edited (->T77EV)

I have checked the implementation guides, but no mention of T77EV. Is there something that should be added in that table?

Kr,

Gerrit

[lukemarson]

Hi Gerrit,

This is an SAP settings table for External Relationships. You should check that the S B 003 O / O A 003 S relationship is in the table. I recommend that you speak to an OM consultant if you are unsure.

Best regards,

Luke

[Former Member]

Actually I am an OM consultant.

The table contains

And both AB relationships between S and O are allowed.

But indeed they are not in the external relationships list.

This is also logical because O and S objects are part of the organizational management and thus not external.

So I have no idea why I would add them there, and if I had an idea, I have no idea what to fill out for the class/program/routine.

Do you have a system where OrgManager is installed, and what values are stored in T77EV for A/B 003 between O and S?

Kr,

Gerrit

[StephenBurr]

I'm in an ECC 6.0 EhP4 system and have no entries in T77EV for 003 between O and S.  I'm 99.9% sure you don't need to be adding entries to this table to support this.

The create position form calls function module "/NAKISA/HR_CREATE_POSI" which then calls a create method in a Nakisa class.  In this create class it creates the object then updates the attributes. Part of this update, then updates the relationships using

      /nakisa/cl_hrpdv_com_pdobj_up5=>update_relations

Try debugging this call to see where the issue is ... or perhaps you should raise an OSS if you haven't customised this area and are replicating on the "out of the box" build.

Stephen

[Former Member]

Hi Stephen,

Thanks for the tip. Actually I put some external breakpoints in the method of the class you mention, but the system doesn't go through there.

However, it does goe through the update_relations method of class CL_HRPDV_COMMON_PDOBJECT_UTILS.

Sadly, I don't really see an error there but somehow the relation between the S and O is not created.That's a bit weird because a bit deeper in GENERAL_UPDATE_FOR_INFOTYPE, the method  io_bo_object->create_relation is called succesfully...

Yet, still nothing in SAP, hence nothing in Nakisa.

I'll debug a bit further and post my findings here, but if in the meantime you might hit onto a reason for this strange behaviour, please do let me know.

Kr,

Gerrit

[Former Member]

Hi Gerrit,

Know you, you've already checked the user permissions, but can you confirm for our benefit that this issue is not authorization based?

Thanks,

Matthew

[Former Member]

Hi Matthew, Stephen,

I can confirm that the problem is not authorisation related.

After some further debugging in SAP I thing I have found the problem. It actually seems to be an SAP problem that occurs at the moment the relationship in infotype 1001.

At that point, the method CHECK_EXTERNAL_RELATION is called in class CL_HRBAS_INFTY_1001.

This should return that the relationship we are trying to create is NOT between external objects (in fact that we are indeed creating a relationship between real OM objects).

Instead the method returns that there IS a value found for our S-O relationship in the T77EV table.

Like indicated before, this is NOT the case, so I investigated even deeper.

In the method CHECK_EXTERNAL_RELATION is called from SPECIFIC_INITIAL_COMPUTATIONS  and I think the problem resides in this SAP code.

METHOD specific_initial_computations.
DATA l_p1001                      TYPE p1001.
DATA l_t77ar                      TYPE t77ar.
DATA l_pad_bl TYPE REF TO if_hrbas_1001_padnnn.
FIELD-SYMBOLS <padnnn>            TYPE ANY.
******************************************************
*check external relationship
******************************************************
CALL METHOD me->check_external_relation
EXPORTING
p1001           = l_p1001	-> Used here
message_handler = message_handler
RECEIVING
is_ok           = is_ok.
CHECK is_ok = true.
************************************************************
*check initial computations for addional data (PADnnn)
************************************************************
l_p1001 = pnnnn.	-> Filled here… makes no sense
l_t77ar = cl_hr_t77ar=>read( l_p1001-relat ).

So l_p1001 is already used to check the external relationship BEFORE it is actually filled with the correct data that needs to be checked!

If I go into debug mode and fill l_p1001 at the right moment manually, the whole thing works like a charm...

I hope I'm not being to abap technical here, but I wondered if any of you could chek that piece of code in your systems to see if there was maybe an OSS note implemented to solve this?

Thanks in advance guys!

Cheers,

Gerrit

[lukemarson]

Hi Gerrit,

There have been no SAP Notes issues for OrgManager. I recommend that you raise an OSS message. Nakisa have only implemented the solution once or twice so you are unlikely to get much support elsewhere.

Best regards,

Luke