topic Re: Master data distribution using message type HRMD_A in Application Development and Automation Discussions

Master data distribution using message type HRMD_A

Former Member — Mon, 10 Jan 2011 10:46:32 GMT

Hi all,

I'm using HRMD_A message type for infotype master data distribution,

I want use different IDOCS for benefits data, compensation data,Is this achieved by using filters?

Re: Master data distribution using message type HRMD_A

SuhaSaha — Mon, 10 Jan 2011 11:09:14 GMT

Hello,

If you check in WE82 the associated basic type with HRMD_A is HRMD_A07.

This idoc type has different segments corresponding to different ITs e.g., E1P0001 for PA0001 etc. I don't understand why you need to use different idoc types for diff. ITs?

BR,

Suhas

Re: Master data distribution using message type HRMD_A

Former Member — Mon, 10 Jan 2011 11:42:04 GMT

I want to use Different IDOC types for each module, like one for Benefits ,one for compensation etc.

Can this be achieved by using filters at message types?

Thanks,

Sudha

Re: Master data distribution using message type HRMD_A

Former Member — Wed, 12 Jan 2011 16:01:06 GMT

Why would anyone use different IDOC types? User Message type HRMD_A in BD64 use the filter on Infotype. It should work.

Re: Master data distribution using message type HRMD_A

Former Member — Tue, 22 Mar 2011 10:04:57 GMT

Hi shital phadake,

I am working on the message type HRMD_A and have seven Basic types.

Currently I am try to Extend one of the seven Basic types. when I am trying to generate an IDOC using PFAL I am not getting the extended Information.

Please help us...

Regards

Chakri

Re: Master data distribution using message type HRMD_A

Edith-Cuellar — Wed, 13 Apr 2011 22:09:15 GMT

Hi,

The message type to send HR data is HRMD_A, i don't think that filtering this only message you achieve what you describe.

In this message type, yo can define filters to send only the relevant infotypes that you need, but all of them will be send in the same idoc, for one employee.

So I think to achieve what you want, you should create customer Message types (Z's) as reductions of HRMD_A standard message type and then in BD64 create one different Model for each one. So in each model you can put only the infotypes you want. You should very carefull with the updating in your destination system, because if you process all the message type at the same time, there will be a lot of blocking in employee objects.

It is weird what you want to do, but this could be the solution.

Regards,