topic Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE) in Application Development and Automation Discussions

EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Former Member — Tue, 16 Jun 2009 11:32:07 GMT

Hi,

I'm trying to various infotype 2001,2002,2006 ecc to another SAP system via ALE and since they are not part of message type "HRMD_A" I have created the extension ZHRMD_A06. I've already created the new segments(we31) and put these segments (with names Z1P2001, Z1P2002 ecc ecc) into the extension(we30). And I've assigned the extension to the message and basic type (we82).

The new segment are processed correctly in the idoc creation via transaction PFAL, but via transaction BD21 i meet the abend message : B1 070 - Internal Error : program....command... for argument Z1P2001 (for example)

In other words, BD21 do not process the custom segment but the PFAL yes...how it is possible?

I've activate the change pointer in every customizing table intersting.

Many thanks in advance for any reply

Achille

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Former Member — Tue, 16 Jun 2009 14:02:45 GMT

Hi, Welcome to SDN.

I'm trying to various infotype 2001,2002,2006 ecc to another SAP system via ALE and since they are not part of message type "HRMD_A"

 My understanding tells me otherways,all standard infotypes are part of HRMD_A. Pls Check 
your filters in BD64.

I have created the extension ZHRMD_A06. I've already created the new segments(we31) and put

these segments (with names Z1P2001, Z1P2002 ecc ecc) into the extension(we30). And I've assigned the extension to the message and basic type (we82).

The new segment are processed correctly in the idoc creation via transaction PFAL, but via

transaction BD21 i meet the abend message : B1 070 - Internal Error : program....command...

for argument Z1P2001 (for example)

 Did you required to write code for populating the custom code. I think *No* ?, 
If Yes (i.e. my statements above is not correct) you need to find Exits for Function 
module MASTERIDOC_CREATE_SMD_HRMD to populated Custom segments

I've activate the change pointer in every customizing table intersting.

Check CDOPS, CDHDR before BDCP2

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Former Member — Tue, 16 Jun 2009 14:45:30 GMT

Hi, thanks for the welcome

unfortunately, the standard do not provide the infotypes for the HR-TM (Time Management), that are between the structures i must send in the other system sap.

Ok,now i've checked the filter in BD64 and the tables BDCP2, CDHDR and CDPOS but it seems all correct!!

Try with an user exit it's a good idea, but why in the PFAL the idoc (with the custom segments) is created without problems and in the BD21 no??? This is very strange

I'don't understand....

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Former Member — Tue, 16 Jun 2009 17:50:32 GMT

unfortunately, the standard do not provide the infotypes for the HR-TM (Time Management), that

are between the structures i must send in the other system sap.

 Ok, I have never delt with Time data in HRMD_A. Probably this is the case then

Ok,now i've checked the filter in BD64 and the tables BDCP2, CDHDR and CDPOS but it seems

all correct!!

 By checking Filters I mean that confirm if you have added Time Infotypes there (just 
making sure). If data is appearing in BDCP2 that means there is no problem in Change
pointer creation, Just ruling out possibility.

Try with an user exit it's a good idea, but why in the PFAL the idoc (with the custom segments)

is created without problems and in the BD21 no??? This is very strange


1) Well BD21 uses the Function module (TBDME for HRMD_A) which read change pointers and 
create IDOCs. So now if you have extended Segment you have to add your population code 
here somewhere.

2) PFAL is Push program, my assimption here is you have wriiten some piece of code to 
populate Additinal segments data here? Otherwise IDOC will not be populated 
automatically.
Let me know what you think.

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Former Member — Wed, 17 Jun 2009 07:57:18 GMT

Hi Shital,

i've checked the fillter and all the infotype (related the custom segments) for the send are inserted!!

I assure you that in the PFAL there aren't user exit implemented, but it work.

However, i will follow your suggestion and try to use the user exit for the BD21....after i'll inform you about the problem if it is solved!!

Thanks for the help

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Former Member — Wed, 17 Jun 2009 18:23:34 GMT

I assure you that in the PFAL there aren't user exit implemented, but it work.

I wonder how SAP gets to know what data to populate in your custom segments, but I dont want

to confuse you. Best of luck.

You may want to close this thread as per new understanding so that Others also can have suggestions

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Former Member — Mon, 22 Jun 2009 16:00:43 GMT

Hi Shital,

i discovered that if use the basic message hrmd_a with a custom implementation ZHRM_06, the BD21 not work very well. So i've created a custom basic message zhrmd_a with the same implementation ZHRMD_06 and now BD21 work(after the various new customizing needed)!!!! MAH...

Now i have problems with the infotype 2011 (TEVEN) and infotype 9022(too long for idoc segment)....

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Former Member — Mon, 22 Jun 2009 18:17:22 GMT

I discovered that if use the basic message hrmd_a with a custom implementation ZHRM_06, the

BD21 not work very well. So i've created a custom basic message zhrmd_a with the

same implementation ZHRMD_06 and now BD21 work(after the various new customizing needed)!!!! MAH...

 Got you, But for me quesion still remains as to how the data for custom segments was 
getting populated, you see you were required to write code for 
BD21 Anyways good job that you achived it all thru customization

Please close this thread and open new one with new question.

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Former Member — Tue, 23 Jun 2009 11:00:20 GMT

Hi Shital,

now, with the basic message custom linked to the extend custom, the custom segments related to the infotypes are filled correctly, without user exits implemented, in both transactions: PFAl and BD21 !! It's strange, but it'so.

Other problem: the IT 9022 is too long for the system. I've created a subsegment custom of Z1P9022, Z1Q9022 for the fields in excedence, but these fields aren't transported in a subsegment...but only for the segment Z1P9022...i don'understand it....

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

Omid — Wed, 03 Jul 2013 14:28:19 GMT

This message was moderated.

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

I833978 — Mon, 11 Jan 2016 13:30:22 GMT

Hello Achille,

I apologize for bringing this topic back again.

But currently I am trying to use PFAL transaction to use a custome message type (ZHRMD_A) I created as a copy of HRMD_A. But can't make that happen. I keep getting an error message "Message Type ZHRMD_A can't be used".

Do you know what I am have to done?? Because as far as I can tell, I have done all ALE Configuratoins so far.

Many thanks

Martin

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

JL23 — Mon, 11 Jan 2016 13:43:28 GMT

you better open your very own discussion instead of reanimating this old discussion to get a useful response. E.g. you should have clicked Achille's user name and you would have seen that he was last here Dec 21, 2009 9:34 AM

It is unlikely that you kiss him alive after 6 years of absence.

Re: EXTEND BASIC TYPE HRMD_A FOR TRANSFER IDOC DATA (HR MODULE)

I833978 — Mon, 11 Jan 2016 13:53:50 GMT

I apologize.

Will open new thread as indicated.