manager of the org.unit in HRMD_A

[Former Member]

Hi All

I would like to send manager of the org.unit by using HRMD_A.

As I have setup HRMD_A with filter on Infotypes 0000, 0001, 0002, 0006, 1000 & 1001.

I thought the manager relationship will be send in IT 1001. But I don't see that information include in HRMD_A.

Any information or experience on this matter will be highly appreciated. Any other suggestions to how this problems can be solved are also welcome.

Thanks in advance.

Best regards,

Anpan

[Former Member]

Try setting up HRMD_A with two filters, one with the PA infotypes with the object type P. The other filter will have the OM infotypes with the objects C, O, S, P. You will then need to create an evaluation path that just selects the chief/manager relationship.

Everett

Message was edited by:

Everett Chandler

[Former Member]

Hi Everett,

Thanks for your replay.

When you say filters is that mean in transaction BD64? My understanding is that we could make it in first push via PFAL transaction by using an evaluation path. But what will happen when we use a change pointer and create a IDOC by using change pointers. Do we still have the information I need in IDOC.

The information I need is weather the employee is manger for an organization or not if so he/she is a manger which dep.

Best regards,

Anpan

[Former Member]

Yes as part of transaction BD64 you can create a filter for this. In fact I think you can limit it even further so that it filters just the managers. You can do this by not only selecting the infotype and object, but you can also limit is by 'related object' and subtype. So you can put the B12 as the subtype ( I think this is the chief subtype).

You could also use the evaluation path, but if your evaluation path generates too much data then you can limited using the filters in BD64.

As for using the change pointers programs versus PFAL I am not sure, I am currently having the same delima on which one to use.

Everett

[Former Member]

All HRMD_A contains is the structure to produce IDOCS out of. You have to produce the logic, read eval path to pass it to the IDOCS