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

Similar Messages

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

  • Difference in idoc adapter header mapping between SP14 and SP19

    Hi All,
    i have a very strange problem.......i have 2 XI systems : XI-sandbox and XI-dev.....
    XI-sandbox is on XI3.0 SP19 whereas XI-dev is on XI3.0 SP14...........
    I have a file->XI->idoc scenario which is same on both XI-sandbox and XI-dev....
    in receiver idoc adapter, i am using header mapping for sender service and in the sender service i am using XPATH of a field of control rec of idoc.........
    this scenario works fine on XI-sandbox which is on SP19 and the idocs are sent to SAP R/3 sandbox...........but this scenario on XI-dev gives error in SXMB_MONI in XI-dev of Call adapter - "No party conversion found".........
    So my question is that is there any difference in idoc adapter header mapping between SP14 and SP19.........
    Thanks,
    Rajeev Gupta
    Message was edited by:
            RAJEEV GUPTA

    ><i>so i cant use apply control rec values from payload.........</i>
    rajeev,
    I know this has nothing to do with the original problem but please do bear.
    If I undertood you posts correct, the Sender Partner Name is set in the Idoc Control record in the field SNDPRN in the mapping using some mapping logic.
    Now, this is the partner name with which the idoc is to be posted to thge R3 system.
    if yes, then like I have pointed above, using "Take Sender From Payload" in the Receivcer Idoc Adapter is a better option as pointed in the SAP help as well.
    As you are already populating the idoc control ecord with SNDPRN just make the SNDPRT as LS and then select "Take Sender from Payload" in the receiver Idoc adapter and the Sender Partner Name will not be taken from SDNPRN just as you want.
    This is different from "Apply Control Records From Payload" .
    Regards
    Bhavesh
    PS : you can ignore this reply if the situatios is too late to make this change and thanks for the patience.

  • 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 + 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 - to - JDBC mapping..

    Can any one help me on  step-by-step   Idoc to JDBC  mapping ..

    Check this link for jdbc receiver adapter. and follow the instructions. If you need more assistance let us know with your requirement
    For configuring JDBC adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
    For creating jdbc structure on the inbound side
    http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

  • Retreive IDOC number and map it to a field in Target XML

    Hi Experts,
    IDOC to file scenario
    I have a requirement where I have to retreive the number of the IDOC generated and map it to a field ID in the target XML.
    Do i have to use a UDF for this? can ne one pls explain?
    Regards,
    Teja

    Hi Ravi,
    You dont need use a UDF for this.
    this is a very simple requiremen.
    You can get the IDOC number from source IDOc
    under EDI_DC40 node field name DOCNUM.
    This DOCNUM fielsd will contain the IDOC number
    Map this DOCNUM field from source IDOC to target XML structure.

  • 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

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

  • 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 with XSLT Mapping ALE service error

    Hi all,
    I have the same problem with "converting to an ALE logical system".
    In this case I have a Business System without logical system name in the SLD. This information for the IDoc control record, like SNDPOR, I will map with a xslt mapping.
    In weblogs from Michael are the properties for the directory described.
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    I selected in the comminication channel the last two check boxes, as described in SAP help.
    "Take Sender from Payload
    If you want to take the sender of the message from the payload and not from the configuration information in the Integration Directory, set this indicator.
    If you do not set the indicator, the information is taken from the configuration in the Integration Directory.
    Take Receiver from Payload
    If you want to take the receiver of the message from the payload and not from the configuration information in the Integration Directory, set this indicator.
    If you do not set the indicator, the information is taken from the configuration in the Integration Directory.
    If you set both of the above indicators, you do not require a heading mapping and do not need to set the alternative identifiers.
    However, you must ensure that the SNDPRN, SNDPRT, RCVPRN, and RCVPRT fields are set in the IDoc control record.
    Setting the senders and receivers of a message from the payload simplifies configuration and speeds up processing.
    If the sender and receiver are not set correctly in the payload, the resulting error is only visible in the receiving system. "
    In my XSLT-Mapping I set the appropriate Idoc fields:
    <?xml version="1.0" encoding="iso-8859-1"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="xml"/>
    <xsl:preserve-space elements="*"/>
    <xsl:template match="DATEN">
    <_-XXX_-018_XXXXX_XIDATEN>
    <IDOC>
    <xsl:attribute name="BEGIN">1</xsl:attribute>
    <EDI_DC40>
    <xsl:attribute name="SEGMENT">1</xsl:attribute>
    <TABNAM>EDI_DC40</TABNAM>
    <DOCREL></DOCREL>     
    <DIRECT>2</DIRECT>
    <IDOCTYP>_-XXX_-018_XXXXX_XIDATEN</IDOCTYP>
    <MESTYP>_-XXX_-018_XXXXX_XIDATEN</MESTYP>
    <SNDPOR></SNDPOR>
    <SNDPRN>XXXXX01IN</SNDPRN>     
    <SNDPRT>LS</SNDPRT>
    <RCVPOR>xxx</RCVPOR>
    <RCVPRN>xxx</RCVPRN>
    <RCVPRT>LS</RCVPRT>
    </EDI_DC40>
    <xsl:variable name="pid" select="substring(.,1,1)"/>
    But in the sxmb_moni the message is red with the error message :" converting to an ALE logical system"
    Have you any idea?
    With another interface I used a graphic Mapping and the same properties in the directory and it works.
    Bye
    Stefan

    Hi togehter,
    it works now, after cpa_cache and sxi_cache.
    and and ...
      <IDOCTYP>/XXX/018_XXXXX_XIDATEN</IDOCTYP>
      <MESTYP>/XXX/018_XXXXX_XIDATEN</MESTYP>
    Without: _-...
    I would write a blog.
    Does know one how that goes here?
    Thanks
    SDN is great
    Stefan

  • JDBC to IDoc ( error when mapping multiple JDBC records to IDoc)

    Hi,
    I am working on JDBC to IDoc scenario, I have declared row as 0 to unbounded and by default the IDoc structure is 1..1.
    Inorder to map multiple rows from JDBC to get multiple IDoc's, I have changed the occurrence of IDoc in "Messages" tab of Message mapping to 0 to unbounded.
    I have mapped "row" to "IDoc".
    When I test the mapping, it works fine, giving the same number of IDoc's with that of row.
    When I test end to end, in SXMB_MONI, it gives me following error:
    <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>MSGGUID 54A3A64E895D48EC3F20C69FEFE2E82B: Tag found instead of tag IDOC BEGIN=</SAP:P1>
    can any one help me out with this.
    Thanks in advance.

    Hi Jwalith,
    Check this blog from Michel
    The specified item was not found.
    Make sure that you changed occurance as per this blog.
    hope this is helpful
    regards,
    Venkat.

  • Problem in idoc to file mapping

    Hi Experts,
    I am doing a idoc to file scenario...
    There is a single idoc with multiple header and line items .
    I am using multi mapping for header and lineitems.
    The problem i am facing is regarding the occurences in target strucure...
    at which level they should be specified so all the headers come in one strucure and line items in another...or should the occurences be o to unbounded at each field level.
    Kindly help me regarding the same ...

    hi
    i have the same scenario : IDOC (orders) to Flat File. can you plz help in mapping. the input format to XI is in the given way
    idoc
        a1---(0-1)
        a2---(0-1)
           b1--
        a3---(0-1)
           b1---(0-n)
             c1---
           b2---
             c1---
        a3---(0-n)
           b1---
           b2---
        a3---
          b1---
          b2---
        a3
          b1---
          b2---
    i have created the same output DT in the same format (parent-child) for flat file. and my questions are
    1. is that correct, do i need to create the same DT as the above idoc (like parent and child) or different?
    2. how to map the idoc fields to my file DT..do i need to map parent to parent and child to child...or different.
    plz help me out
    Thanks
    ram

Maybe you are looking for