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.

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

  • Link between control record and infotype 0003.

    Hi all,
    Can anybody explain me, what is the link between control record and infotype 0003?
    Thanks & Regards,
    Lucky.

    Hi,
    Control record is a heart of payroll area(pa03)
    Conrtol record alswa based on payroll area where it determines the current payroll period for the exact date
    It defines the payroll past for retro active accounting recongnation.
    It lock the master data and teh time data to prevent changes from being made during the payroll run, this lock is valid for the paryroll past and the payroll present changes with effect the future can still be made.
    It determines the earliset retrocatice a/cing period.
    In simple control record is to control the payroll status of the employee
    Payroll Status:(IT 0003)
    The Payroll Status infotype (0003) contains data for Payroll Accounting and Time Evaluation.
    The system automatically creates this infotype when the employee is hired. In general, the system updates the infotype and writes the changes to the payroll past.
    You can change the payroll status of an individual employee using Payroll/Retroactive Accounting and Time Evaluation.
    Thanks
    Vibin

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

  • Error in VT04 - Doesn't create Shipments

    Error in VT04 - Doesn't create Shipments
    We have this function module that automatically creates delivery and shipment base from the Goods Receipt.
    The problem is it doesn't createe shipment document because the delivery doc doesn't exists.
    Upop debugging, the delivery has been created. And appends the delivery number into TVARV table (found in PERFORM CHANGE_VARIANT_VALUES). Then there's this code that it doesn't recognized the delivery that it was created.
    PERFORM CHANGE_VARIANT_VALUES USING VBKOK-VBELN_VL.
          SET UPDATE TASK LOCAL.
          SUBMIT RV56TRGN WITH P_OUT  EQ C_X
                         WITH V_PSEL EQ 'RV56LFSL'
                         WITH V_PSP0 EQ 'RV56TRSP'
                         WITH V_PTR0 EQ ZVXXAUTOGRDN-DATA_OPTS
                   AND RETURN EXPORTING LIST TO MEMORY.
          COMMIT WORK AND WAIT.
    Though in the production this program works. But in QA server it doesn't. I am not sure if this is the effect of a Unicode issue also.
    Help me guys.. I just couldn't find in program RV56TRGN on how the values will get from TVARV.
    I am not familiar with the command SET UPDATE TASK LOCAL. If this is related to Memory storage that might get the last value.
    Points will be given for the helpful ideas. Thanks!

    Hi,
    The service contracts guide also says to run 'Installed Base Interface' concurrent program for shippable items. Even after running this concurrent program no contracts is created.
    Any step to be done further??
    Regards,
    Nithya

  • 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

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

  • 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

  • Error while creating infotype message no. pg293

    Hi guys,
    I am creating a new infotype after creating the PS structure when i click on generate objects i get an error saying "An internal error has occurred" message no. PG293.
    kindly provide a solution.
    points will be rewarded.
    thanks

    INFOTYPE CREATION WILL BE TAKEN CARE OF THE ABAPER AS RAO SAID
    AS THE OUT PUT WILL HAVE TO SEEN IN ALL THE SERVERS THIS IS A LITTLE BIT TECHNICAL WORK
    Start transaction PM01, Create Infotype, by entering the transaction code.
    You access the Create Infotype screen:
    2. In the Infotype no. field, enter the four-digit number of the infotype you want to create.
    When you specify the infotype number, please remember to enter any leading zeros.
    3. Choose IT characteristics.
    This accesses the Display View “Infotypes”: Overview screen.
    4. Choose Table view   Display   Change.
    This accesses the Change View “Infotypes”: Overview screen.
    5. Create a new entry for your infotype.
    You can create new entries by
    – choosing Edit   New entries or
    – copying an infotype entry with similar characteristics.
    If you want to copy an existing entry, select the entry you want to copy and choose
    Edit   Copy as.
    6. Check the entries in the individual fields.
    Result: You have maintained the characteristics of your infotype.
    Please check the above config for maintaining your infotype in PA30 and also check your entries in T582A & S.
    Edited by: Sikindar on Mar 9, 2008 8:23 PM

  • Disable Create Serial No. automatically Check box in MIGO

    Hi,
    I have a problem where in I need to disable Create Serial No. automatically check box in MIGO while posting GRN. And I could not do anything with the profile of the serial nr in t-code OIS2.
    You can give me some information that help in this question.
    Thanks in advance.
    Ramesh

    Hi,
      Thanks for ur answer Sheshu.
      Sorry for the delay.
      I have created screen variant for that Serial number tab sub screen and assigned Output only option for that check box. Thn i created a transaction variant and assigned that Screen variant to it. At last i assigned and activated that Transaction variant to Standard Variant of MIGO. All these are done in SHD0 tcode.

  • How to create the Batch Automatically during creation of Production order

    Hi All,
    I wanted to create the Batch Automatically for the Specific order type during creation.
    Not for all order type so OPKP transction will not work for me.
    Please suggest any way or user exit any production order.
    Thanks,
    Amit Shah

    Hi All,
    Thanks for your inputs.  
      1. Why we want create the Batch Auto -
          For Std Production Order type we want to generate Batch Automatically.
          For Re-work Production Order type we don't want Batch Created Auto.
          If you have better solution please let me know.
    2.  Scheduling profile.
          I think I misunderstood your solution.
          You want to say that mainatin the Schd profile in the SPRO with repect to Sub Schdler.
          Already client is maintaining the Schd Profile in the Material Master.
           please correct me if i am wrong.
    Thanks,
    Amit Shah

  • Stop Inbound IDOC's from being created

    I want to stop inbound IDOC's for a particular partner (type LS) from being created in our R/3 system. Is there a way to do this? I am aware these can be stopped in the middleware, but this is not possible in our case.  I am also aware that I can stop these IDOC's from being processed via the partner profile, however, there will be a huge number of useless IDOC's that will be created in our system and I want to avoid that.
    Hence, I do not want the inbound IDOC's to be created in the first place even though they are transmitted to SAP. Is this possible?
    Any inputs will be highly appreciated.
    Thanks,
    Raghu.

    Hi Satwik,
    Choose Idoc in WE02.
    Get port name, Then in WE21 get RFC name.
    Go to transaction SMQS - Here we can block this RFC instead of blocking the queue.
    Thanks,
    Anil

  • JDBC -- XI -- IDoc Scenario... IDoc Extension not being created...

    Hi,
    I hope you can help with this issue... I have a scenario which involves mapping to an IDoc which we have extended. From IDX5 I can see the outbound message from XI and in the XML I can see the extension segments have been properly created. But when the IDoc is posted to the destination system these segments are not there.
    I have checked so far...
    - The correct IDoc definition with extension has been imported
    - The IDoc which is being created contains the extension in the control record
    - Refreshed all caches
    - Deleted and reimported IDoc metadata
    If anyone has come across this issue before, please let me know...
    Thanks,
    Pete

    Hi Pete,
    Please check the Idoc receiver communication channel. Apply Control Record Values from Payload should be checked.
    Thanks,
    Shubhankar

  • Create purchase order automatically from Sales order.

    Hi,
    I have ticked  Create purchase order automatically check box in item category TAS and TAB but still not able to generate Purchase Order automatically.???
    any clue.
    thanks/ashu

    You need to have your prerequisites in place for the automated creation of the purchase requisition before the purchase order can be raised:
    You may already have done this, but check that your material has the purchasing information on it (trxn MM02, purchasing tab), that a purchasing information record exists for that material and vendor in that purchasing org (trxn ME12), check that a source list exists as well (trxn ME02). If you have created the source list or purchasing info record after the sales order has been created then you will need to go into trxn ME56 to assign them manually. That should release the PO to be created.
    In standard 3rd party, the PO is created using ME59 (prog RM06BB20), which can be run as a batch job.
    Jon

  • Can't get my 3rd Party Sales Order to create the PO automatically...

    I'm trying to get the 3rd Party Sales Order process to work and I would like it to create the PO automatically (it is already creating the requisition without issue). I have:
    i) Set the Auto PO on the Item Category
    ii) Set the ALE paramenters asociated with the Sales Org definition
    iii) Set the Auto PO on the Vendor Master
    iv) Set the Auto PO flag on the Purchasing tab of my NLAG material
    v) Created a Vendor Info record
    BUT I still don't get a PO being created automatically .... can anyone see where the problem may be?
    Thanks.

    Hi Dennis - I really appreciate the feedback but I started this thread with ....
    I'm trying to get the 3rd Party Sales Order process to work and I would like it to create the PO automatically (it is already creating the requisition without issue). I have:
    i) Set the Auto PO on the Item Category
    ii) Set the ALE paramenters asociated with the Sales Org definition
    iii) Set the Auto PO on the Vendor Master
    iv) Set the Auto PO flag on the Purchasing tab of my NLAG material
    v) Created a Vendor Info record
    BUT I still don't get a PO being created automatically .... can anyone see where the problem may be?
    I have since confirmed that I can trigger a PO creation by running ME59N BUT the PO is not created automatically when I save the sales order despite what the help text on the item category implies.
    I think I have already done every you have suggested and even a little more, or maybe I'm missing something? Do I need to do something with ALE - turn something on perhaps? Have you actiually seen this functionality working? I'd love to hear from someone who has.
    Regards.
    Patrick

Maybe you are looking for