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

Similar Messages

How to extend IDOC type "HRMD_A" for infotype 2001?

Hi,
I'm trying to send infotype 2001 to another SAP system via ALE and since it is not part of message type "HRMD_A" I have tried to create an extension. I've already created a new segment(we31) and put this segment into the extension(we30). And I've assigned the extension to the message and basic type (we82) but it still doesn't work. Is there anything else I have to do?
Many thanks in advance
Christopher

Hello Christopher,
I don't think any coding is required in your case if I understand your issue correctly.
Just create a Z segment (say Z1P2001...make it same structure as P2001) then insert it as a child segment type of E1PITYP in your customer extension which should be attached to Basic Type HRMD_XX (as per your SAP release).
Make sure in the partner profile you have specified the name of your customer extension and in table T777D you have maintained the value of your Z segment (Z1P2001) in the field IDOC segment.
Now, as long as you have change pointers activated globally as well as for the message type you are using, change pointers will be auto triggered for infotype 2001 and when you run BD21 to process the change pointer, you'll see the system has automatically populated your customer segment Z1P2001.
Let me know if it solved your case.
Cheers,
Sougata.
Edited by: Sougata Chatterjee on May 23, 2008 1:41 PM

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)

How to garantee IDOC types are the same on two communicating sap systems.

Hi all:
    how to garantee IDOC types are the same on two communicating sap systems, including segments and versions, using bd64?
    what's more, what bd64 using for besides generating parter profiles, must we use bd64 for outbound idocs?
    Thank you very much
best regards ?

Hi jingying Sony
You can compare the Idoc type and Version between Sender System and Reciver System.
Use TCode SCMP and Compare the Table EDIMSG in Both System.
This will solve your issue.
Thanks
Ramesh

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)

How to Transfer IDoc Type to Data Type in XI

Dear All,
I am working on scenario to transfer data(IDoc) from SAP System to Non SAP system through XI.
While Defining "Data Type" in XI i want to create Data Type as of IDoc type(CREMAS05).There is any direct method to import IDoc type into "Data Type" in XI.
thanks,
RP

Hi Rp,
External definitions enable you to import WSDL, XSD, and DTD documents to the Integration Repository so that you can access the message definitions they contain as external messages.
If a description of the message structure already exists in one of the above formats, you can use it in the Integration Repository by importing it as an external definition rather than re-entering it manually using the data type editor.
Prerequisites
The document to be imported must conform to the WSDL, XSD, or DTD standard.
Chk out all the details + how to import Ext Def:
http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
Also refer...
Connection Using Adapters and Imported Interfaces
http://help.sap.com/saphelp_nw04/helpdata/en/4a/576d219c340844aaa12ce9bbc2c3ee/frameset.htm
Incase u want to chk out the details of Idoc scenario.....
IDoc to File:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Handling different partners for IDoc:
/people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/file%2bto%2bidoc
Hope this was helpful..
kanan

PLANNEDORDER_GETDETAIL Msg type how to create IDOC TYpe

I have copied the BO BUS2004 to a ZBUS2004 along with Messagt type ZPLANNEDORDER_GETDETAIL, FM ZBAPI_PLANNEDORDER_GET_DETAIL, what I cannot do if create a copy of the required IDOC TYPE.
PLANNEDORDER_GETDETAIL01 does not exist, I want to make a ZPLANNEDORDER_GETDETAIL01.
Can someone please guide me in makeing this IDOC type to go with message type PLANNEDORDER_DETDETAIL
<promise removed by moderator>
Thanks
MJ Franzo
Edited by: Thomas Zloch on Mar 9, 2011 3:44 PM

Marcia, you may have to generate your own IDOC type/Message type for this... You can use BDBG to achieve this,
Search in SDN/Google for BDBG.. you can also check out this link,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6943dc85-0601-0010-beab-e2ce1eb16f25?overridelayout=true

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!!!!...<b>BUT</b>, 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 + "<br />");
Good luck
Thanks-Gopal
Message was edited by:
gopal srinivasan

Basic IDoc type ZSAB008 is unknown

We just completed a client copy of our Production landscape to our Test landscape including R/3, BW and SRM. In BW we have a source system of type File System that is used to upload data from flat files. Prior to the client copy uploads using this source system worked fine. Now when trying to upload a file I get the error above.
I manually created a source system of this same type in our Sandbox system to test this functionality prior to using in our "real" systems and I do not recall having to create any Idoc Types manually. I'm not sure how to fix this.
I'm looking at Source System > Restore but I can't find any good documentation to tell me if that is what I should do. Can someone tell me what "Restore" does and how the ZSABxxx Idoc types were created in the first place? In our BW SBX system we have 3 ZBASxxx types, one for each Source System, in BW TST we only have 2 one for the R/3 source system and one for the internal BW system. Are they automatically generated in the process of activating the Source System in the first place?
Thanks for your help.

Hi,
This is problem normally occurs,if you had not handled properly the system copy. Recently we also faced this problem . We solved it by the help of notes : 325470 and 184322
So Sit with Basis guy and use these notes.
With rgds,
Anil Kumar Sharma .P

When do we ceate custom messagae type apart for custom idocs type

Hi all.
Can u pls let me know when do we create custom message type in ALE/IDOCS. what I know is we can create a custom message when we create custom idoc type & when we have reduced idoc type.Pls let me what are other cases in which I need to create a custom message type.Thanks in advance.
Kind regards,
sami.

I think these are the only cases where we need to create. Its basically when we dont have standard SAP message type available.

How to Reduce HRMD_A IDOC?

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

Hi Fatin,
Instead of reducing the Idoc, u can use XSD of the idoc by reducing the idoc .... After importing the idoc click Tools--> Export reduced XSD...
Now u can import this XSD in external definitions and use this one instead of usin the idoc...
Hope it may help u....
Regards,
Sridhar...

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

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

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.

IDoc generation with Message Type HRMD_A with filter on Personnel Area

Hello All,
We are facing an issue in generating IDoc using the standard message type HRMD_A.
When we have no filters on the Distribution Model, the IDoc is generated through RBDMIDOC. When we use the filter on BUKRS, it generates the IDoc but gives an error status "Cross-system company code XXXX does not exist". I know to how resolve this issue. But, we tried to filter the changes with Personnel Area this time. So I have used the field PERS_AREA in BD59 with segment type E1PLOGI. When I run the standard report RBDMIDOC it gives the message "No data selected for distribution".
I have checked the field name PERS_AREA from table TBD10, and it is mapped to T500P-PERSA. Change pointers are triggered and stored in BDCP2. Request experts to suggest what could be wrong with this.
Thanks,
Anil

Hello Michele,
If you have added BUKRS in BD59 for the message type, you will see Company Code (not filter1) in your filter criterion in BD64.
Have you included the following code in FILTER_VALUES_SET method of the BADI implementation.
CHECK OTYPE = 'P '.
SELECT * FROM PA0001
           INTO PA0001 WHERE PERNR = OBJID
                       AND   BEGDA <= SY-DATUM
                       AND   ENDDA >= SY-DATUM.
record is valid today, no authorization check
    EXIT.
ENDSELECT.
IF SY-SUBRC = 0.
    FILTER1 = PA0001-BUKRS.   ELSE.
    CLEAR FILTER1.
ENDIF.
Lastly, just make sure the record you are testing for has your desired company code PGPB.
Regards,
Anil

Reduced message type - Idoc without conversion rules

Hi Friends,
Am facing a strange situation while converting the Material Master data from 4.7b to ECC using BD21 transaction with reduced custom message type. I have reduced the standard msg type MATMAS05 using BD53 for the required field mapping both systems and I written the code using the exit EXIT_SAPLMV01_002 based on client req.
The situation is that sometimes IDocs are failing and the error shows that some fields which I have not selected in E1MARAM segment of the reduced msg type are populated with some values(ex: zeroes-0, slash-/,spaces)
Note: Conversion rules are not needed for this scenario.
Please help me out how to get rid of this '/ ' or spaces which appear for unselected fields in outbound Idoc using reduced message type ?
Thanks
Saravanan

Hi,
Please check the documentation in WE60 tcode and see if the fields are required to be passed...
Regards,
Nagaraj

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

How to reduce idoc type HRMD_A?

Similar Messages

Maybe you are looking for