Tagging of department/group/division/section/unit in org. unit

[paoloneric1]

Hi Experts,

I have a requirement from a client to tag organizational objects as either a Department/Group/Division/Section/Unit. Because HCM: Organizational Management doesn't distinguish Organizational Units from one another, only by relationships, I would need to store this additional information per org. unit in another infotype. Is there a standard infotype that can hold this information? I am currently looking at Structure Information infotype 1986.

Regards,

[Stephen_B · Accepted solution]

Hi Paolo,

No, these tagging is not supported in SAP standard OM. So just go ahead re-purpose any OM infotype as long it can store these information on there.

The issue with storing this information in infotypes is that there is no graphical interface (like PPOME) where the user can automatically identify which is the department, which is group etc. without checking  this information for each individual org unit in PP01.

Cheers

Stephen

[paoloneric1 · Accepted solution]

Ok thank you Stephen.

I have no requirement to display this grouping in PPOME. But I know that if I can maintain this in an infotype, I can display it perhaps in the standard ad-hoc query?

Also would you suggest an OM infotype I can re-purpose? I just need to configure 5 dropdowns.

Regards,

Paolo

[Stephen_B · Accepted solution]

Use IT1010 - Authorities and Resources (as long it's not currently in use in your system) Create a subtype, something like 'Org Level' and then create the categories for these: department, group etc

This is normally assigned to Position objects. I'm not sure if this infotype is assigned to Org Unit objects in vanilla SAP but you can configure it as required.

Sure, you can report it in ad-hoc query but it's not going to be a pretty report. You won't see a Org Units in hierarchical view in nested levels (division reports to group etc) as it should be. But as long is this will suffice for your users, then why not.

Please mark this comment if helpful.

Cheers

Stephen

[yury_sichov]

IT 1010 or 1222 or expand 1003.

[Sanky]

Hi Paolo,

I think you go with Custom object with different number series and then make the relationship and store all are in custom infotype.

Let see other's view on this.

Regards,

Sankarsan

[paoloneric1]

Hi Sankarsan,

Can you please elaborate on your proposed solution?

Regards,

Paolo