SAP HR Org. Structure excluded from integration to SRM

[Former Member]

We have not set up the automatic integration of HR org changes into SRM organization (report RBDMIDOC, message type: HRMD_ABA).

In SAP HR some new org units with its positions and employees will be assigned.

We would like to exclude this new part of HR Organization Structure from

integration to SRM. In the transaction BD64 we can filtrer object type,

subtype, infotype and relationship but this is not sufficient for us.

¿How could we exclude from copying to SRM a whole part of the organizatonal tree, for example excluding a root org. unit (one ID) and all its dependets org. units (evaluation path)?

Thank you in advance.

Best regards.

[Former Member · Accepted solution]

Thanks Laurent for a fast reply.

I'm fresh in this topic. I've got one more question. We execute program RBDMIDOC message type HRMD_ABA. I can modify the selection screen of RHALEINI and save a variant I need. But I don't know how and where I indicate that we should use our custom variant of RHALEINI. ¿I mean, where is the connection between our job RBDMIDOC already planned and the PFAL?

Thank you again.

[laurent_burtaire · Accepted solution]

Hi again,

Forget the PFAL transaction.

Using BAdI HRALE00OUTBOUND_IDOC in R/3, you should be able to filter out Organizational Units you don't want to send by IDocs to SRM even if modification pointers exist.

Regards.

Laurent.

[Former Member · Accepted solution]

Hi Malgorzata Kaminska,

We had similar kind of requirement which we could acheive with

01) Write a custom program which calls the standard SAP T-code PFAL or (RHALEINI)

02) In the Exit R/3 outbound IDOCs, filter the PERNRs to exclude the list you do not want to. If the list is static, you can maintain in a custom table one time and in the outbound idoc exit, check an entry exists in the table and exclude the PERNRs. If the PERNRs are dynamic, then when the PERNR gets created, write another exit to populate in this custom table for PERNRs exclusion.

03) The custom program of point 01) will pick all the necessary PERNRs for replication and submit in the PFAL as select single.

04) The variant in the PFAL can have an evaluation path as P-S-O and executed under update mode.

Hope this helps!!!

DV

[laurent_burtaire]

Hello Malgorzata,

You can use PFAL transaction.

In the frame 'Objects', you can choose Object ID from which you want to replicate data and the reporting period. Maybe, with those settings, you can cover your requirement.

If not, have a look at R/3 BAdI (HR*) in order to not process R/3 Organizational Units you do not want.

Regards.

Laurent.