Z - HRMD_A IDOC

hi Friends,
         I have created a Custom Basic type ZHRCRM based on HRMD_A. and configured in WE81, WE82, BD60 and BD59.
         but when i give the message type ZHRCRM in PFAL Transaction it gives the error message.
         even distribution model was created in BD64.
         You cannot use message type ZHRCRM - Error Message.
          Please help me to correct this problem soon.....
Thanks,
Bala.

Similar Messages

Custom status message in ALE HRMD_A IDOC

Hi,
We are using HRMD_A idoc for integrating two SAP systems. We want a custom check to be included in the ALE outbound processing, where for example if a field of an infotype is some value then we want to stop the IDOC from being transferred to the target SAP system. IDOC should stop with a custom error message in the status record. Is this possible using any of the user exits?
Thanks in advance,
Shravan

Requirement looks bit strange to me, if at all the IDoc is not needed to be sent for error message then why to Generate them, just filter out creation of IDocs by setting the Filters in Distribution model.
For your requirements you may want to take a look at Badi HRALE00OUTBOUND_IDOC.
Regards
Shital

HRMD_A Idocs sent to XI has status 39

Hi,
Our HRMD_A idocs used to have status 03, but after we started using XI , most of them have status 39 and they are being processed correctly. But some other programs are checking for status 03.
How does this Idoc status gets changed or effected after using XI?
Any ideas on that?
Thanks in advance.

Hi Anjana
We are trying to integrate HR master data with a legacy system and we are using chnage pointers for that. Did your scenario use change pointers to trigger HRMD Idocs ? if so I would appriciate ur help. I did all steps for setting up change pointers , but can't get the change points trigered when some thing is changed.

HRMD_A IDoc in error not raising an event

I have workflows enabled for IDocs in error.
If an inbound order IDoc (ORDERS) arrives in status 51, it triggers a workflow.
If an HR master data IDoc (message type HRMD_A) arrives in status 51, no workflow is triggered.
Here is what I have checked:
Partner profile has me as responsible agent in both cases.
Both type linkages are active for IDOCHRMD and IDOCORDERS event InputErrorOccurred.
Both IDocs types are posted in with the test tool and end up in status 51.
When I investigate the event trace, I can see that an event is raised for the ORDERS IDoc but not for the HRMD_A IDoc.
There are no errors in the type linkage status column.
So why would it be that the event is not being raised for the HRMD_A IDoc?
How can I find out what should be raising the event? I guess that there is a function module call to SWE_EVENT_CREATE or SAP_WAPI_CREATE_EVENT.
Kind Regards,
Tony.

Hi Tony,
I am a complete novice to workflow but I have a requirement liek yours to trigger workflow for idocs in error, so I was hoping you could point me in the direction of some documentation/steps on how to do this?

Problem in HRMD_A Idocs: Object is Locked

Hi Everyone,
I would like to ask for assistance on the problem below.
We've encountered almost everyday failed HRMD_A idocs. Almost all of the idocs have the same error message: "Object is Locked. A locked key has been set for the object."
The object type is "P".
Can you help us on how to solve this problem?
Thanks in advance!

Hi,
For the locked object the sender system itself will not send the idoc.
and hence the error for the lock object might have been seen in the sender system and not the receiver system.
Yes you can process the idocs which are in error in the receiver system by frequently scheduling reports like
RBDMANI2-Schedule update of idocs with errors and
RBDAPP01- for ready for transfer idocs
I suggest you use the bapi way of transferring data, where the receiving system reads data from the sender system once a day and reads only that data which is changed during that date.
Regards,
Divya

ALE HRMD_A Idocs in status 52

HRMD_A Idocs in target system are not completely posted, turning into status '52'. Most of the times the infotype 1001 idoc with relationship P->S arrives before the idoc which has the actual objects(P, S) causing 'Relationship imposible because the object does not exist".
We use program RBDAPP01 for inbound processing of Idoc which should take care of Serialization based on the time stamp of idoc creation in source system.
Change pointors for Message type HRMD_A are processed using program RBDMIDOC in source system.
It is unlikely that relationship P->S is created without object P being created in the source system. So the change pointors should create the idocs in the same sequence. But it is not happening. Any body experinced similar problem?
Any help on this appreciated.

The question here is if all necessary data has been already transferred to target system . If data is selected based on change pointer than only data that has changed in source system is send to target.
Example: imagine you have change employee position using one of already created positions in the system. Change pointer will take than only the new assignment between employee and positions. It will not actually transfer the existing position it-self. In this case you must be sure that all existing positions are already transferred to target system.
In your example only new relationship between P->S is transfered to target. Employee data should already been there. The change here is not about creating new employee but only about the new relationship P->S.
Best Regards,
Andrzej

HRMD_A idocs sent and processed, but Org chart doesn't reflect it sometimes

From our HR box, we send HRMD_A idocs to our FI box - We have an intermittent issue where we have a position change & the idoc gets created & sent over.
On the inbound side, the idoc gets posted successfully with Status 53. However, this EE does not appear in the org chart as it does on the HR side.
We have these IDocs set up to process immediately, so it passes to the FI port and is processed all within a few seconds.
We come across this issue once about every 3-4 weeks and I can't seem to get anywhere trying to resolve it.
any ideas?

There are two main annoying problems with Flash Builder and swc's:
1. Flash Builder doesn't reflect changes made to swc files
Solution : First of all - keep your swc files inside your project folder, you can also disable global swc cache: change as3api.cpp code,refresh swc in flashBuilder bug!
2. Flash Builder breakes content inside swc files (and also popular problem "TypeError: Error #1034: Type Coercion failed: cannot convert flash.display::MovieClip@1f21adc1 to...")
Solution : locate the project .actionScriptProperties file and set useFlashSDK=”false” : Flash Builder 4.7 – useFlashSDK | In Flagrante Delicto!
In this case you can also download latest Apache Flex SDK to target new Flash player versions: http://flex.apache.org/
Hope this helps!
P.

HRMD_A IDocs in Error Status 02

Dear SAP Peeps,
Upon generation of outbound HRMD_A idocs, an error occurs. Error status is "02 - Could not find code page for receiving system".
Can you guys assist me here? What does code page mean? How the error will be solve? The error occurs in every two weeks upon sending the idocs. Sending system is a unicode system while the receiving system is a non-unicode system.
Thanks!

i Think u have run some personnel acitons
than u need to check the table T529A and check have u assigned the feature which standrad in sap for certain acions
for Ex MSN20 MSN10 check these thr PE03
in IMg
check SEt up personnel Acitons

HRMD_A idoc generation with all infotypes

Dear All,
I have a requirement where in I want to generate HRMD_A idoc with all the infotypes. We have created change pointers and any change that we do, generates idoc but it contains the data of only the changes done. Is there a way, whcih will enable the generation of idocs of the changes OBJID and it should have the data of other infotypes of the OBJID.
Eg. Suppose i do change for infotype 1 of say OBJID 00001. I want that the idoc should send info abt other info types also.
Is there anything standard...???
Thanks!!
Cheers
Sunita

Unfortunately not. You'll need the help of a developer to create a Z extension to the standard Message Type, add the extension to the standard Message Type and finally fill the (custom) fields of that Z extension via a BAdI provided by SAP to customers so that when the IDocs are created by the applications it will also create & add the Z extension as an appendix to the standard segments of the IDoc (which you would normally view via WE02/05).
Hope it made sense and it helps your issue.
Cheers,
Sougata.

Possible to trigger HRMD_A IDoc immediately

Hi experts,
Can you please let me know if it is possible to trigger an Outbound HRMD_A IDoc immediately i.e. as soon as someone creates a new record for any of the infotypes associated with this IDoc the IDoc is sent; without having to schedule PFAL or BD21.
Thanks and regards,
Brendon

Can you please let me know if it is possible to trigger an Outbound HRMD_A IDoc
immediately i.e. as soon as someone creates a new record for any of the infotypes
associated with this IDoc the IDoc is sent; without having to schedule PFAL or BD21.
Well I think some confusion out here, PFAL or BD21 does not have any control on when the IDOC
is sent they will just read the infotype data and create IDOCs. WE20 Partner Config has got the
setting to tell system whether COLLECT the IDOCs in ready state or dispatch as soon as they
gets creates (PFAL/WE21) Without scheduling BD21/ PFAL you will not have IDOCs itself
triggering comes later.
Hope this clarifies.

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

Populating the custom segments for the Basic type attached to HRMD_A (IDOC)

Hi,
I've enhanced a few infotypes and want the new fields to be available in an IDOC created through the program RHALEINI.
Here are the steps I followed.
Step 1 :(we31)
We created new segment Z1IT023 , containing all the fields from infotype 0023 along with the custom fields added.
Step 2 :(we30)
We created an extension of IDOC type HRMD_A07 by name HRMD_EX to include this segement.
Step 3 :
We added an entry in table EDIMSG against message type HRMD_A , with base type : HRMD_A07 , extension : HRMD_EX , version : 700
Step4 :(we20)
Now , we made changes to partner profile by adding entry for message type HRMD_A with base IDOC type as HRMD_A07 and extension as HRMD_EX
Step5:
We changed the entry in table T777D and specified the IDOC segment as Z1IT023.
Step6.
We then tried to execute the report RHALEINI to generate the IDOC. The IDOC got created, but it didn't have the data for the segment Z1IT023.
In fact, there is a different solution to this... by adding the custom segment(containing nly the new infotype fields) as a child of the original segment E1P0023 and then writting code in the user-exit to populate the segment, but our intension is to have a single segment with all the infotype 0023 data. Besides, I believe in HR, making an entry in T777D should free us from writing any code for populating the IDOC segments.
Can anybody please suggest me, where am I going wrong. How can the new segments be populated automatically.
Thanks in advance.
Sujit.
Responses will be suitably rewarded.

Hi,
Did u get any exit to populate the custom segment?
Thanks,
San

Problem regarding HRMD_A IDoc as outbound posting

Hi,
I have a requirement to post the data for HIRING (PA40 - hiring action) as IDOC, for which i am using HRMD_A.
Client's specific requirement is to Post the data, as soon as the user completes with the hiring of the employee through PA40.
I tried to add the logic in the Save of the Infotype, but which infotype is the last screen, how we can confirm, because all the Infotypes are not compulsory, he may skip the screen.
How to trigger the IDoc creation....
Can anyone help to find the triggering point for the same or any other alternative.
Basically client dont want to schedule a job that would take care of the posting at particular decided time and neither for Change Pointers....
Is there any work around for the same?
Any suggestions would be of great help.

Set change pointer active for HRMD_A, turn direct processing on in the partner profile, schedule a job every n minutes to create idocs from change pointers. And choose the correct forum for this, cause this has nothing to do with abap.

How to send single person-records with HRMD_A Idoc and change Idoc header?

Hello group,
we have different companies in our SAP system (BUKRS). Now when an infotype is changed the changepointers are activated and using program RBDMIDOC we can send Idocs of type HRMD_A to f.i. files. In order to have these files distributed to different parties depending on BUKRS of the person we would like to have HRMD_A to deliver single records, an Idoc for each person and the Idoc header fields for variant and function should be filled so that the partner profile would distribute the Idoc to the partie.
Is this possible? And if yes how?
Regards, Léon Hoeneveld The Netherlands

Transaction PFAL lets me trigger the Idoc manually, but with a job for RBDMIDOC this is automatically.
I found fm RH_HRMD_BLOCK_SIZE in wich you can enhance the code to set the block size for an Idoc-type to 1.
But now I still have to change the Idoc header with an enhancement of user-exit.
HRALE00OUTBOUND_IDOC BADi does not have the functionallity.
Regards, Léon Hoeneveld

HRMD_A IDoc Error Handling

We are distributing organization data to another system from our HR system using ALE with message type HRMD_A. In the target system, under transaction BD87, we have a few IDocs in status 51 and 52.
For status 51, I currently have the following error: "Error in subroutine read_namtb for structure of infotype", and also "HR: ALE inbound processing for HR master data" - This last one is the name of our distribution model. Neither error message gives much detail - How do I go about finding out the cause of the problem?
Fpr status 52, I also have the error "HR: ALE inbound processing for HR master data" - Again this is the name of the distribution model. Not sure what to do with these..?
What should be done about these? I can't reprocess either status, so what do I need to do to correct the problem?

Dear David,
Regarding status 51, the most common reason is that the link 007 between position and job cannot be distributed using ALE with the HR standard system. Please implement note 661605. It applies whenever relationship 007 is distributed. Remove the entries detailed in the note in T77AR as explained there in the source system. This way this additional segment will not be distributed and the IDOC will be able to be sent with no errors. So, please make sure that in the source system in T77AR Substructure for additional data and Screen additional data are empty (as they should be also in the target system).
Please can you check out table T77s0 for switch HRALX HRAC if it is activated in your target system? If not please set it up to 'x' and try again.
Best Regards
Christine Morin
Senior Support Consultant

HRMD_A IDoc Serialization Help

Hi,
I have a client that wants to activate IDoc serialization for HRMD_A. They have a global system that sends HR master data to multiple regional systems, MDM and SRM.
The requirement is to serialize the IDocs for all regional systems, but not for MDM or SRM.
My understanding is that we would need to activate both outbound and inbound serialization through SALE->Modelling and Implementing Business Processes->Configure Predefined ALE Business Processes->Human Resources->Master Data Distribution->Serialize HR Master Data.
We would activate outbound in the global sending system, and inbound in each regional target system, but not in MDM or SRM.
By activating serialization, will it activate for HRMD_A only, or for HRMDA_ABA as well?
We would then need to make sure that the serialization counters are all initialized in both source and target systems. We can do this with transactions RE_RHALE_HRMDRGOUT and RE_RHALE_HRMDRGIN.
Please correct me if any of the above is incorrect?
Once serialization is activated, how will this effect the system? If for example an IDoc is sent with 100 objects, and one fails, then what status will the IDoc go into? Will all other objects process correctly? How would the error object affect subsequent IDocs?
What steps need to be taken in order to resolve the following potential IDoc errors:
- Change for person xxxxxxxx extends too far into past
Delete IDoc? What to do with counters?
- Object 01 ,z ,xxxxxxxx does not exist: infotype 1001 cannot be created.
Resend missing objects with PFAL and then reprocess IDoc?
- Relationship starting from 01 y xxxxxxxx impossible u2013 01 w zzzzzzzz does not exist/is not active.
Resend missing objects with PFAL and then reprocess IDoc?
- Personnel number xxxxxxxx is locked
Will this sort itself out, or do we need to manually reprocess the Idoc?
- Payroll area yy is locked for master data maintenance.
Reprocess the IDoc after payroll areas is unlocked?
Thanks very much for your help
Edited by: David Bann on Sep 22, 2011 4:52 PM

Hi,
If change pointers are to be written for custom fields then the change document flag at the domain level should be checked for that field. Then maintain an entry for this field in transaction BD52. Object name will be the same as the original fields. Changes to custom fields will be only picked if the change document for such fields is maintained in table BDCP.
Try now!
Reddy

Z - HRMD_A IDOC

Similar Messages

Maybe you are looking for