cancel
Showing results for 
Search instead for 
Did you mean: 

How can exclude the FICA’s structure from HR’s reports that doesn’t ask for a root organization unit?

Former Member
0 Kudos

Hi.

We need your help with FICA an HCM Structures:

FICA created a structure in Tx PPOME with those objects:

(see image 1)

FICA's structure has an independent root organizational unit, but still affecting some HR's reports, that the structure was created with another root organizational unit. An example of this it's the report “Vacancies” that shows the position that aren't occupied, this report doesn’t verify the root organizational unit, it just take the vacancies of the entire structure:

S_AHR_61015516 – Vacancies

(see image 2 and 3)

How can create a structure for FICA that doesn't affect the HR structure and the HR reports?

How can exclude the FICA’s structure from HR’s reports that doesn’t ask for a root organization unit?

We tried to limit the object ID authorization through OOSB and OOSP transactions, but in the reports that doesn’t ask for a root organization unit the report shows all the information in OM (including FICA’s structure)

The process to view vacancies in the company include the execution of this HR transaction (S_AHR_61015516), if the HR's analyst can't exclude the root organizational unit that FICA use for their process the information showed is incorrect, because those position that was defined in FICA aren't a real position in the company.

Thanks in advance,

Rebeca.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

From your description of the issue, it sounds like this FICA structure is just a dummy structure. Operating under that assumption, I can suggest few options:

1. You could look to create all the objects within that structure in "planned" status (HRP1000-ISTAT = '2'). Most standard reports and PPOME/PPOSE interface only look at/display objects in "active" status (HRP1000-ISTAT = '1').

2. Vacancy report pulls data from table T750X which I believe gets written to it when a vacancy record is created for the position on the OM side (infotype 1007). You can delimit that record and it should drop off from the report unless you run a wide open historical report. You can also delete the vacancy record.

I'll keep thinking other options but it would help if you can let us know if FICA structure is used in any process that requires those objects to be available in active status.

Hope this helps.

Donnie

Former Member
0 Kudos

Hi Donnie!...Thank you for your answer, I'm going to test those options, I will let you know the result.

Former Member
0 Kudos

Hi Donnie! We made a test with you suggestion number 1, but the result was unsatisfied.

1-            We can’t create a root organization unit with object status planned, you can do this only for children organization unit in detail maintenance mode. The root organization unit always is created as Active status.

2-            We tried to change the object status by the program RHAKTI00, but the program created both object status, Active & Planned, this options doesn’t fit, because the object status Active has been showed in the PPOME and other HR's reports related to OM.

Do you know the process to create a root organization unit with object status “Planned”?

In other hand, FICA structure is used like a WF, they draw like a map to indicate a process approval, FICA's consultant asked to SAP if we can use an alternative plan but they answered that must be an active plan. I'm not sure if the status object must be active too.

Thank you!

Rebeca