IDOC - HRMD_A - Infotype 35

Guys , everytime i change infotype 2 for example a new idoc is created with this new information, however i want to do this for infotype 35 , i mean send the idoc again but without send any information of the infotype 35. how could i achive this ?
thank you very much for your advice .

Hi,
make sure infotype 0035 is included in the filter in your distribution model. Change pointers are just created for infotypes included there.
Regards,
Ana

Similar Messages

IDOC HRMD_A + Change pointers + Infotypes change objects doesnt exist???

Hi guys,
I Have to send master data from infotypes 0002, 0006, 0032 and 0105 from HR to SAP PI. I've configured BD61, BD50 and BD53 to reduce Idoc HRMD_A. Then in BD52 I've tried to put this fields to activate change pointers when data from this infotypes is changed.
But in BD52 doesnt exist infotypes 0002, 0006, 0032 and 0105. I tried with object HR_IT1002, table HRP1002 and fields BEGDA and ENDDA, then run program RBDMIDOC and the Idoc is sent, but is possible with infotypes metioned????
Regards,
Pablo

Pablo,
are you able to see entries getting created in BDCP* tables
did you activate change pointers in BD53
Thanks
Bala Duvvuri
Edited by: Bala Duvvuri on Jul 29, 2010 10:35 AM

Idoc hrmd_a doesn't create infotype 0003 automatically

Hello !
When a new Person is created in One R3 system -
we send It's infotypes to another R3 system
with idoc hrmd_a.
We send only these infotypes :
0000,0001,0002,0006,0105,0041,0900.
We expect infotype 0003 to be created automatically in the new system ,
but it does not happen and for that reason
The Person is not created fully in the target system.
only 0000,0001,0002 are created and for each of the other infotypes we got a message like this :
"You have tried to create infotype XXXX for the following object: plan version 01, object type P, object ID 00XXXXXX. However, the object does not exist.
PA objects exist if infotypes 0000, 0001, 0002, and 0003 have been created. "
How can we make 0003 infotype to be created automatically
without sending it by the Idoc ?
Is there a flag in the idoc declarations or
a customization we can fill to make this happen ?
Thanks ,
Nitzan S.

Hi Nitzan,
I don't think there is any easy way to get 0003 infotype being created automatically on idoc input. At least I have none in Release 4.6 c.
Why not send it? IMHO there is no sensitive data in it? Besides there are ways to manipulate that data when replicated via ALE.
If you really need that infotype to be created, you could check EXIT_SAPLRHA0_003 of RHALE001 via transaction CMOD. There you can code your requirements in ALE-user-exit.
Regards
Herbert
Message was edited by: Herbert B.

IDoc HRMD_A

Hi,
In order to send employee maseter data like infotypes like IT0000, IT0001, IT0002, IT0105 (Sty 0001/0010), HRP1000 and HRP1001 , which are the fields on which filtering should be used for the iDoc HRMD_A.
Points will be rewarded.
Thanks & Regards,
Soumya.

Hi,
You have to do the configuration in both the systems. You can transfer the data between two systems using Transaction code PFAL (HR :ALE distribution of HR Master data)
Regards
Vinod

HR Programming : Problem with IDOC HRMD_A

Hello ,
We use Idoc HRMD_A for transferring PA records from
one R3 system (ECC5) to another R3 system (46d).
We have a problem - The Idoc doesn't check the data
inserted against the database check tables and
inserts wrong values into the target system database.
(At least that what has happened when we transferred
wrong value of MASSN in 0000 records).
Is there something we can do ?
Maybe - Some flag we can sign in order a check against check tables will be done ?
Is it a problem with this IDOC ?
Thanks .
I appreciate any help.
Nitzan S.

Consultancy note 134085 :
"Ultimately you are responsible for consistency of this data. SAP saves this data directly on the database without checking the single fields and consistency of the data records (time constraints check, writing change pointers, value check) because the consistency for an R/3 - R/3 lingage is of course ensured."
The IDOCs were intended for R3->R3 data replication, and not for data loads/interfacing. Since you're having problems, I'm guessing in addition they require the same SAP version as well.

Reducing IDOC HRMD_A

I want to reduce IDOC HRMD_A.
I have
1) created a copy ZHRMD_A & marked the fileds that I want to send in the IDOC via tocde BD53
2) activated the change pointers for ZHRMD_A
3) updated the partner profile & distribution model.
But when the IDOC is created it still has all the fields without any reduction.
Any help would be greatly appreciated.
Thanks

Hi,
I have the same problem! Does anybody know how to solve it?
Regards,
André Avilla

Update HRMD_A infotypes from inbound Idoc

Hi again all,
I am trying to send inbound HRMD_A06 idocs to SAP to update infotypes for employees. The idocs are received by SAP, processed by the correct application and stored in the database for the employee. But the values already stored in the infotypes should be delimited based on the new data, and it is not!
The new value, ie. IT0105 subty 0010 (email) has the previous values:
BEGDA: 20040101
ENDDA: 99991231
INFTY: 0105
SUBTY: 0010
USRTY: 0010
USRID_LONG: [email protected]
The idoc sent to SAP contains the following values (which are stored successfully in the database):
BEGDA: 20050201
ENDDA: 99993112
INFTY: 0105
SUBTY: 0010
USRTY: 0010
USRID_LONG: [email protected]
The new values are stored correctly for the correct employee, but the previous values are not delimited! SAP only adds the new value to the list of infotypes for the employee. The previous values should be set so ENDDA = 20050131.
Currently there is no way to know which value is the valid one, as both values are currently valid. We are using time constraint 2 (only one value valid at any time), but this seems not to be functioning.
Does anyone have any experience with this?
Any help is highly appreciated.
Br,
Kenneth

Hi Senthil,
That was apparently a typo from me... The ENDDA is set as 99991231. But according to OSS note 134085 the inbound HRMD_A idocs are bypassing all consistency checks and time constraint checks. But I have managed to overwrite the previous value if the new BEGDA and ENDDA at least covers the previous BEGDA and ENDDA, and BEGDA >= hire-date. Even though I can't delimit records, I can live with this solution.
Thanks for your reply.
-Kenneth

IDOC HRMD_A for Infotype 0002 (Personal Data)

Hello,
I'm trying to send the modifications that I make in a person in the transaction PA30 in the table PA0002 automaticly. But when I go to thew program "RBDMIDOC" and select the message type "HRMD_A" (HR: Plan data and HR master data) it says that it doesn't have anything to send. But when I modify a Object (o, c, s), and I execute the program it send information. The object(o,c,s) has sent correctly. But when I want to send the Personal Data (P), it doesn't send anything. I have the trigger activated.
Have I selected the message type correctly?
PM

updating id for malasian employee is not working.
Q0002-perid. it come only for malasian employee.
screen no 2044
Use transaction PA30,
Enter infotype number 2 or select Personal Data (0002) on the Personal Data tab
You can use any Malaysian employee #
Click on change button
Enter in an ID number. (There is no validation on ID number field.)
Click either the enter or save button. The ID number disappears and a message says No change found.

Transferring inactive personnel numbers via IDOC (HRMD_A) - how?

Hello everyone,
we are using IDOCs of type HRMD_A to transfer some infotypes (0,1,2,3 and a few others) of all employee numbers from the HR system to the FI system. The transfer is initiated using transaction PFAL with transfer type "Insert". So far, so good.
Now we find that employees that have gone inactive (e.g. left the company) are not being transmitted, not even if in PFAL the time period selection is set to "ALL". As the consequence, these personnel numbers remain active in FI because their exit action is never being transmitted.
Since transaction PFAL uses object type and object id parameters for identification of the objects to be transmitted, I reckon that object-selection is OM-based. By setting object type to 'P' and leaving object ID blank, I choose to transfer all personnel numbers that are known in OM. Once an employee exits the company, however, he is effectively leaving the OM, seeing that he no longer occupies a position. I take it that this causes this personnel number no longer to be transmitted, even though in past periods she existed in the OM, and even though time period "all" was selected in the selection-screen of PFAL.
A possible factor in this may be that sometimes exits of employees are maintained in the HR system retrospectively, i.e. after they have already left the company.
How can I deal with this and make sure all personnel numbers are being transmitted including the information that they have left the company? As it is now, these personnel numbers remain "active" in the FI system forever, because PFAL on the HCM system stops transmitting them for good once they have become inactive.

1. start BD61 and active globaly change pointers
2. start sm31 and maintain V_TBDA2 for activation change pointers for HRMD_A message
3. start we20 and check you linked system for message HRMD_A
4. start bd64 and check you distibution model for HRMD_A.
if all this step is configured you can chang master data via ppome or pa30 and check via re_rhalecps generated changepointers.
than you can use bd21 for hrmd_a message for generated master hr data in outbound idoc (use we02 to see outbound idocs)

IDoc HRMD_A.HRMD_A07 mapping

Hi,
I am doing a File to Idoc mapping using HRMD_A.HRMD_A07 Idoc, I see the Idoc segments as E1P0001,E1P0002,E1P0003......I see the same fields(personal no, start date,end date etc) repeating in all the above segments.I would like to know which segment I need to use for mapping.
Thanks

you might have received the Functional specs or the mapping sheet in which you will have the details of which info type to be filled and sent as an idoc to sap.
to know segment wise details in case your file structure doesn't have detailed info, run Tcode We60 -> give the basic type
HRMD_A07 and read documentation for each info type segment .
or download this PDF
http://help.sap.com/printdocu/core/print46b/en/data/en/pdf/HRINF.pdf
other useful tcode from sap point of view .
Pa30 , pa 40 and in se11-> give info type line pa0001 ,pa 0002 etc and check the details of each info type and fields req.
if a custom info type is there then i think it will have name something like Pa9XXX.
Best Regards,
Srinivas

Mapping not sufficiently defined FILE TO IDOC(HRMD_A.HRMD_A06) scenerio

Hello friends,
In message mapping part from File to IDOC. I am doing mapping of infotype 14 message type with the corresponding idoc. But when I activate it I am getting the following error:
Activation of the change list canceled Check result for Message Mapping MM_INF14_LS | urn:tcs:test: Mapping not sufficiently defined
As far as I know I have properly mapped the fields which I am picking from the file. But I am not very sure what to do woth few fields in the IDOC which appear to be red in message mapping
Kindly give me the solution.
Regards,
Lokesh

Thanx guys...I tried changing the description of other mappings whch were already activated. And thn I tried activating I got the same error:
Activation of the change list canceled Check result for Message Mapping MM_02IT | urn:tcs:payroll: Starting compilation Source code has syntax error: java.lang.NoClassDefFoundError: com/sun/tools/javac/Main Exception in thread "main"
what possibly can go wrong? Is there any way to activate it.
Looking forward for ur reply.
Regards,
Lokesh

IDOC HRMD_A to Files

Hi,
I have change pointers activated on an HR system, and I need to transfer the changes to an external application via XI.
The external application accepts 3 different types of messages (e.g I have 3 distinct message type in my design rep.) but on the HR we have only 1 type: HRMD_A idoc.
I could do multimapping 1:3 but depending on the content of the Idoc, not all 3 types of outgoing messages.
Would it be enough just to set the occurrence of the target messages to 0::1 and therefore if the mapping has no values for a certain message type, that one is not created ?
I just don't want to have empty files..
Cheers,
greg

The external application accepts 3 different types of messages (e.g I have 3 distinct message type in my design rep.) but on the HR we have only 1 type: HRMD_A idoc.
-->if you have only one type then simply map that one type and ignore the others, this shd not create empty files.
Would it be enough just to set the occurrence of the target messages to 0::1 and therefore if the mapping has no values for a certain message type, that one is not created ?
-->you can do this too...but if you are able to change the target sturcture y don't you remove the other two structures that you will never use? i think there is no need to include any of the other type structure other than HRMD_A in your target message.

ALE Message type HRMD_A Infotype 0001 is incorrect using PROOF flag = X

Hi
We have an issue using HRMD_A for Infotype 0001 with the PROOF flag swithed on. Using the PROOF flag triggers a call of HR_MAINTAIN_MASTERDATA instead of a direct write to db tables. However sometimes the update of Infotype 1 is incomplete and records are lost. The data goes through a transformation in the inbound BAdi, here I have checked the sequence is still correct. But when the data is written to Infotype 1 it seems to overwrite the last entries.
If anyone has any experience with this, I would be very interested for any input.
Thanks in advance
Sonny

Hi Sandip
Thx for your response. If I understand you correctly you suggest I use the HR_INFOTYPE_OPERATION. This could be an alternative, but I would prefer to understand the reason behind the error.
HR_INFOTYPE_OPERATION actually calls HR_MAINTAIN_MASTERDATA, so this FM might not solve the issue, but it does give the option for updating one record at a time.
Sonny

XI 3.0 does not receive idoc HRMD_A.HRMD_A01

Hi,
I am sending the idoc type HRMD_A to XI and ECC shows that the status record is 03 that the idoc have been passed to the port OK but the idoc never reaches the XI when i look at the processed XML messages (SXMB_MONI). Partner Profiles and Distribution model should be configured ok. I am using ta PFAL to send the idoc from ECC. What could be the problem why idoc never reaches the XI? Could the problem be in the mappings?

hi,
check transaciton SM58 on the R3
do you see any errors over there?
you can find IDOC configuration examles
in my book too (step by step):
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Out of Memory problem at large IDocs (HRMD_A.HRMD_A06)

Hello,
we need help at the following problem:
We send HRMD_A.HRMD_A06 IDocs in a IDOC->XI->IDOC Scenario.
In this scenario there is a small graphical Mapping. When
we send 100 Idocs, after 15 - 30 Minutes all queues are stopped and the error "Out of Memory" is showing.
We have configured that Large IDocs are running in own queues (Max. 3 parallel), but the error is still there.
Only Solution this time is to restart the queues repeatly and at anytime the Idocs are all going through.
Has anyone a idea what we can do ?
Regards,
Christian

Thanks for answers,
now after 15-30 Minutes a new Error shows:
"Timelimit Overstepped" - In German Original "Zeitlimit Überschritten".
and all Queues stopped.
What can i do ?
Regards
Christian

IDOC - HRMD_A - Infotype 35

Similar Messages

Maybe you are looking for