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

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

How to reduce idoc type HRMD_A?

Dear All,
We need to reduce the HRMD_A idoc. We have taken the following steps:
1- created message type ZHRMD_A using transaction BD53 (Idoc reduction maintenance) wit reference to HRMD_A message type
2- Activated the segments and fields of the required segments
3- Activated change pointers using the Active Change Pointers push button on the initial screen of BD53
We can see that our ZHRMD_A message type is active in table TBDA2 (using transaction BD50. Message type HRMD_A is still active in the same table.
When we run transaction BD21 (to evaluate change pointers) with message type ZHRMD_A, we do not get any idocs created. However BD21 will generate idocs when run with HRMD_A message type.
Are we missing a step in our configuration?
We are on ERP 2005 (WAS 7:00) SPS 6
Thx/Farshad

Fatin,
Have you activated Change Pointers - Generally? If no then in Customizing for Distribution (ALE), choose Modeling and Implementing Business Processes -> Master Data Distribution -> Replication of Modified Data -> Activate Change Pointers - Generally. Set the change pointer status to Active, and save this setting.
Choose Modeling and Implementing Business Processes ® Master Data Distribution -> Replication of Modified Data -> Activate Change Pointers for Message Types. Set the change pointer status to Active for the appropriate message type (which is ZHRMD_A in this example), and save this setting.
Also do not forget to maintained Distribution model ( TC : BD64) & partner profile(WE20) for message type ZHRMD_A.
Cheers,
Nilesh

Sending reduced IDOC from XI to R/3 with nodata markers

Hi !
I need to update a VERY FEW Vendor fields data in R/3 from XI (FILE-XI-IDOC). I'm using the standard IDOC type CREMAS04 (I need to update fields of the E1LFBWM segment...withholding tax fields).
The problem is, that if I disable the not needed IDOC fields in the XI message mapping, when the IDOC reaches R/3, it blanks all the fields that were empty as result of the mapping...I verified it using XI and using the IDOC test tool (we19). For example, if the vendor had data in fields such as "salutation", "phone number", etc. after the IDOC processing, those fields change to BLANK.
One solution is to send the NODATA marker ("/") in those not needed fields, and that works!!!!...BUT, there are hundreds of IDOC fields.
I made a reduced IDOC type, based on CREMAS, enabling only the segments and fields needed, but tnx-WE19 and XI keep sending blank data in the not needed fields instead of the NODATA marker.
How could I send by default, the NODATA marker ("/") to all the fields NOT mapped or disabled, without having to map each field manually ?!?!?
Should XI send those fields as "/", or the R/3 should detect that the incoming IDOC is a reduced IDOC type, and complete all the not existing fields with NODATA ??
The goal is to update some data, and not overwrite with blanks, those fields that should remain untouched.
Thanks !!
Matias.

Matias
Is ur intention /equirement to send the NODATA for the rest of the IDOC elements or just send the reduced IDOC for the required sender elements..
if it is only for sender file elements, as sravya said Note 709400 describes
The integration repository provides a new function: "export reduced XSD" to reduce the XML schema of an IDoc.
To use this function in the mapping tool, proceed as follows:
1) Open the relevant IDoc in the object editor of the XI Repository.
2) In the menu "Tools", select the menu option "Export reduced XSD".
3) Assign a file name in the subsequent dialog box and save the data on the hard disk of your local PC.
4) Use this exported file in the message mapping instead of the IDoc by using the function "Import XML or XSD" in the mapping tool to select the source or target message. So you must use this function to import the reduced XML schema stored under
3) of the IDoc in question, and use this XML schema instead of the complete IDoc.
Note: The XML schema generated using the function "export reduced XSD" does not contain the full information in the repository on the IDoc and should only be used for the mapping.
option2: if you want to send the NO DATA, you got to develop UDF in Java or XSLT..
Here is a sample Java code:
obj = inputModuleData.getPrincipalData();
msg = (Message)obj;
XMLPayload xmlpayload = msg.getDocument();
DocumentBuilderFactory factory;
factory =DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
// parse the XML Payload
Document document = builder.parse((InputStream)
xmlpayload.getInputStream());
var x=document.getElementsByTagName("<rootnode>");
for(i=0;i<x.length;i++)
//the attlist variable will hold a NamedNodeMap
var attlist=x.item(i).attributes;
if (attllist.getvalue.equals("") { //pseudo
attlist.setvalue("/"); //pseudo
document.write(att.value + " ");
Good luck
Thanks-Gopal
Message was edited by:
gopal srinivasan

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.

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

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.

ALE: reduced IDOC type

I have 4 systems, i.e.: PLM and R3-1, R3-2, R3-3
I want to send a reduced IDOC for material master (MATMAS) from the R3 instances to PLM
I created a reduced IDOC type for MATMAS and created a transport request of ALE tables of reduced message type in PLM.
However, I am unable to import the transport request from PLM to the R3 instance, because PLM is unicode and R3 is non-unicode.
As a workaround until I resolve the unicode issue, I re-create the reduced IDOC in the R3 instance and I am able to send the material master data correctly.
Is there a simpler workaround than re-creating the reduced idoc in each R3 instance?
Also, when I send material master data from R3 using BD10, it does not send associated material class even though, I specify 'send material in full'. Where does that association take place?
Any thoughts?

The table is maintained with BD69 - Assignment of message type to IDOC type.
In my case I added one line with values:
Message type: {my reduced message type}
Basic type: HRMD_A06
Extension: {my HRMD_A06 extension}
Also it looks like there is another (better?) way of making the assignment. It is done with WE82, described in sap help here http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7db043d711d1893e0000e8323c4f/frameset.htm and also discussed in this topic.
SAP ERP Human Capital Management (SAP ERP HCM)

Reduced IDoc

Hello evryone,
I created reduced Idoc in BD53 of message type PORDCR. PORDCR05 idoc is assigned to it.
when i open the reduced message type in WE19, it is still showing all the segments.
After creating reduced idoc in BD53 and activating, is there any other steps left?
Why it is showing all the segments in WE19, not the only selected segments and selected fields?
Regards,
manish

Hi,
The mandatory segments cannot be reduced.The Fields present in the Idoc with reduced message type can be viewed in BD52. And please see the below links, it might be useful to you.
http://help.sap.com/saphelp_46c/helpdata/en/66/1c4b6e5733d1118b3f0060b03ca329/content.htm
https://wiki.sdn.sap.com/wiki/display/ABAP/ReducedMessageTypes
Regards,
P.Rajesh

ALE: setting up reduced IDoc type for use in 4.7 and ERP 2005 problem

I need to set up a reduced HRMD_A message type and then use it to send HR data from a 4.7 system to an ERP 2005 system.
To define the reduced type in both systems I use transaction BD53 (Idoc reduction maintenance).
The problem is that the transaction offers HRMD_A06 as the basic type on a 4.7 system and HRMD_A07 on ERP 2005. Thus i cannot set up identical definitions.
I suppose I should 'step back' to A06 at the ERP 2005 system somehow, but where to look for?..
Thank you in advance!

The table is maintained with BD69 - Assignment of message type to IDOC type.
In my case I added one line with values:
Message type: {my reduced message type}
Basic type: HRMD_A06
Extension: {my HRMD_A06 extension}
Also it looks like there is another (better?) way of making the assignment. It is done with WE82, described in sap help here http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7db043d711d1893e0000e8323c4f/frameset.htm and also discussed in this topic.
SAP ERP Human Capital Management (SAP ERP HCM)

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

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 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.

Need to reduce idoc for PO

Hi all,
we have a requirement to send PO details when new po is crated in SAP,
but we need to send only 13 fields from PO , so how to reduce the fields and how map the fields,
the below are the fields needs to send to legacy system.
EBELN
WERKS
LGORT
AEDAT
BSART
EBELP
MATNR
MENGE
MEINS
BANFN
EINDT
MENGE
REVNO
ERDAT
which idoc needs to use , there are 3 idocs are available in SAP( PORDCR04, IMPINV01, ORDERS05)
we are using ECC 6.0
Regards,
Suresh

HI,
there are a lot of ways.
IF you are using ORDERS05 (ORDERS).
Implement Exit "EXIT_SAPLEINM_002" and remove all unanted value in the Segments.
Note: Each Segment is used by that exit.
another way.
Wait if the ORDERS is complete.
Implement BADI "IDOC_DATA_MAPPER" and use Method "PROCESS" to get rid of all unwanted data.
Note: this badi is called after IDOC_OUTPUT_ORDERS.
Note: take care of using this Badi cause every created IDoc is running through that function ? You have to restrict for each IDoc Type and maybe Partner.
example.
Case CONTROL-IDOCTP or RCVPRN or ....
when 'ORDERS05' ...
endcase.
Regards,
Gordon

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">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Reducing IDOC HRMD_A

Similar Messages

Maybe you are looking for