HRMD_A - inbound

We have an inbound interfaces that reads a flat file and creates IDocs to create employees (0000, 0001, 0002, 0006, 0105, 0041), positions (1000, 1002, 1011, 1013) and relationships between these objects (1001).
This results in numerous IDocs in error due to the employee or position being locked and requires reprocessing. THe problem however is that it takes hours reprocessing (hundreds of iterations) to elminate these errors due to locked objects. There must be a better way.
I would appreciate assistance from anyone who has used message type HRMD_A for inbound processing of IDocs and experienced this problem.
Thanks in anticipation.
Jill

Hi
Authorizations might be one of the reason.
So IDOC transfered but no records to be writeen to DB.
regards
vijay

Similar Messages

AEDTM + UNAME not filled via HRMD_A inbound idoc

Sorry if this is the wrong forum but I couldn't find any forum related to IDocs.
I have an inbound idoc:
message type: HRMD_A
basic type: ZHRMD_A0701
Processing the idoc is working, however, AEDTM and UNAME isn't filled (the fileds are empty). I would assume that those fields are filled automatically with sy-datum and sy-uname. I did some debugging and found the corresponding INSERT:
IDOC_INPUT_HRMD
- IDOC_PROCESS_HRMD
- RH_IDOC_OBJECTS_SAVE
    - inbound_objects_block
      - RH_CREATE_INFTY_PA_PB
        - SAVE_PA_PB_INFTY
          - insert_pa_pb_objects
            INSERT (dbname) FROM <f_prel_db>.
AEDTM and UNAME are emtpy in <f_prel_db>. Any idea why? Is this a known issue?

HR inbound idocs actually do not override change date / time (aedtm, uname) with date/ user id of the user who processes the inbound idoc. These info should automatically be populated in the oubound idocs as is from sending SAP system.
I guess the reason being is this is meant to replicate data (with all original info from sending system) to receiving system. If you notice in the receiving system, when HR inbound idocs are processed, change pointers are not recorded.
Therefore, if the inbound idcocs are not senf from SAP, these info would need to be populated when outbound idocs are created. Otherwise, you may have to look at inbound user-exit to see if these fields can be populated in the idocs segments.

HRMD_A Inbound Authorizations

Dears,
we are configuring two R3 systems to transfer OM data from one system to another.
the receiving system user which will be CPIC ID must have authorization for posting the data, can anybody help me with authorizations required for this user.
Regards

Hi Jilly,
I hope you must have got the answer by now. but for the benefit of others I just want to highlight that Inbound Idoc (HRMD_A) doesn't delimit the infotype records instead crates a new record that means you would end up having 2 rows for the same record which is not we want. So the options available are either use an additional function to post process the Idoc before updating the infotype or go with a proxy integration. We have used Proxy integration to achieve the same. Hope this helps.
Edited by: Krishna Tamminani on Apr 12, 2010 11:51 AM

HRMD_A Inbound Idoc with process Code:HRMD not updated in SAP

Dear friends,
I'm facing a problem with Personnel data creation in SAP (this is not a SAP HR system).
I have a data file with Personnel data, in WE19, I use idoc_input_hrmd to process the data (with basic type: hrmd_a06). Idoc has been created with status '53'. However, when I check in SAP, t-code PA30 with the Personnel number, the record does not exist. Checked infotype tables PA0000, PA0001, PA0002 and PA0003 as well, no luck.
I wonder where does the data go? Is it sitting somewhere in the system and waiting to be processed?
Please help!!!!!

Hi
Authorizations might be one of the reason.
So IDOC transfered but no records to be writeen to DB.
regards
vijay

Update HRMD_A infotypes from inbound Idoc

Hi again all,
I am trying to send inbound HRMD_A06 idocs to SAP to update infotypes for employees. The idocs are received by SAP, processed by the correct application and stored in the database for the employee. But the values already stored in the infotypes should be delimited based on the new data, and it is not!
The new value, ie. IT0105 subty 0010 (email) has the previous values:
BEGDA: 20040101
ENDDA: 99991231
INFTY: 0105
SUBTY: 0010
USRTY: 0010
USRID_LONG: [email protected]
The idoc sent to SAP contains the following values (which are stored successfully in the database):
BEGDA: 20050201
ENDDA: 99993112
INFTY: 0105
SUBTY: 0010
USRTY: 0010
USRID_LONG: [email protected]
The new values are stored correctly for the correct employee, but the previous values are not delimited! SAP only adds the new value to the list of infotypes for the employee. The previous values should be set so ENDDA = 20050131.
Currently there is no way to know which value is the valid one, as both values are currently valid. We are using time constraint 2 (only one value valid at any time), but this seems not to be functioning.
Does anyone have any experience with this?
Any help is highly appreciated.
Br,
Kenneth

Hi Senthil,
That was apparently a typo from me... The ENDDA is set as 99991231. But according to OSS note 134085 the inbound HRMD_A idocs are bypassing all consistency checks and time constraint checks. But I have managed to overwrite the previous value if the new BEGDA and ENDDA at least covers the previous BEGDA and ENDDA, and BEGDA >= hire-date. Even though I can't delimit records, I can live with this solution.
Thanks for your reply.
-Kenneth

BD87 idoc inbound error for message type HRMD_A

Hello there,
I am getting below error while fetching Inbound idoc in tcode BD87, see log below from ST22
Short text
    An SQL error occurred when executing Native SQL.
What happened?
    The error "-10328" occurred in the current database connection "LCA".
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
How to correct the error
    Database error text........: "Mismatch of number of stream members for
     parameter (3) (application 6, database 9)."
    Database error code........: "-10328"
    Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_CONTROL""
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
    "/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU07"
    "SIMSCTRL_EXEC_COM"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
   Display the system log by calling transaction SM21.
   Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
   In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"SIMSCTRL_EXEC_COM" "(FORM)", or its possible occurrence must be declared in
the
Do we need SAP_APO in order to install LiveCache?
We have below landsacpe
- SAP ECC 6 EHP4 with SQL server 2005 S BACKEND
-LCAPPS Component release 2005_700 with SP
SAPKIBHD05.
- We dont have SAP_APO component
-SAP LiveCache system have MAXDB 7.7.04.29 as backend.
- Live cache client is installed on same SAP ECC system where we have SAP ECC EHP4 system.
any suggestion how to resolve it?
Mani

>
Mani wrote:
> I installed a standalone server and i need it only for SAP HR (specifically Idoc processing in SAP HR Human capital management module). But i am getting error while running ibound idoc process.
> So Do i still need SAP_APO component?
I never heard of this specific scenario for liveCache usage in the past 7 years working in SAP support on the liveCache component.
Might be useful if you provide some more details (documentation, notes, links) that describe this usage scenario.
In any case you will need to have a liveCache version that is compatible to your application ABAP coding.
The error message you posted indicates that your liveCache version does not fit your application version (or vice versa).
> I installed SAP MAxDB and LiveCache buid using Installation master DVD for SAP ERP. So i think i followed the right method as specified in installation guide.
Be precise, please. Which installation guide? There are hundreds of them - not THE installation guide.
> Secondly can you help me something specific to my problem in coding form?
Already did.
> i tried in LC10, using LCA monitoring i am not able to run SQLDBC trace under
> LCA >> LiveCache Monitoring >> Tools
> but i am not able to execute the same, is it a error or we need to configure something?
Well, the liveCache needs to be integrated into the LC10. You'd do this in transaction SM59 - but as you've followed an installation guide, this would have been covered in it...
> Operational status is active green light, below is file status.
>
>
KNLMSG     KnlMsg     1.098.697     28.01.2011     06:59:55     Database Messages     ASCII
> KNLMSGARC     KnlMsgArchive     8.192     28.01.2011     06:59:50     Database Errors     ASCII
> KNLMSGOLD     KnlMsg.old     342.663     28.01.2011     06:59:50     Database Messages (OLD)     ASCII
> KNLTRC     knltrace     6.209.536     28.01.2011     06:59:56     Database Trace (Raw/Binary)     BINARY
> BACKHIST     dbm.knl     570     10.01.2011     06:18:41     Backup History     ASCII
> DBMPRT     dbm.prt     133.843     29.01.2011     11:41:27     Database Manager Log File     ASCII
> DBMPAHI     L00.pah     214.225     10.01.2011     06:18:16     Database Parameter History     ASCII
> LCINIT     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Initialisation     ASCII
> LCINITCMD     lcinit.bat     3.047     28.10.2008     14:45:51     LiveCache Initialisation Script     ASCII
> LCINITHIS     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Initialisation History     ASCII
> INSTPRT     dbm.ins     863.981     10.01.2011     06:18:47     Installation Log File     ASCII
> DIAGDIR     File     0     10.01.2011     06:18:18     Diagnose History     DIRECTORY
> ANALYZER     analyzer     0     29.01.2011     00:00:36     DB Analyzer File     DIRECTORY
> LCTRC#init.his     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
> LCTRC#init.log     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
> LCTRC#_apo_version.txt     lc_apo_version.txt     164     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
>
> any clue whats wrong?
> Mani
The only thing this tells us is: the liveCache instance itself apparently comes up and writes out the standard log files.
That's it.
As I already tried to explain, the problem seems to be the dependence between your application and the liveCache version.
Usually I'd recommend to open a support message for this, but the colleagues would (hopefully) ask the same questions as I did.
regards,
Lars

Error while processing inbound Idoc (HRMDA_07) with FM IDOC_INPUT_HRMD

Hello,
I have a inbound Idoc of type HRMD_A (basistype HRMD_A07) which is processed by Function module (FM) IDOC_INPUT_HRMD with proofing. After processing an Idoc the status Monitor for ALE messages (BD87) tell me that my Idoc has status 53, which should be the result i would like to have.
Unfortunately when i go to transaction PA20 and check the infotypes, i see that infotype 0302 isn't created. When analyzing this problem i see that during the processing the Infotypes are posted with HR_MAINTAIN_MASTERDATA (dialog mode is 0 and luw_mode = 0 from include LRHA2F02 FORM save_pa_pb_infty) When this is done for infotype 0302 sy-subrc <> 0 the message is A complex application error has occured. This error message is placed in Export parameters
Return and Return1
of HR_MAINTAIN_MASTERDATA. When the program returns to the calling Form it checks if there is message of type E in HR_RETURN (see below) :
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
          EXPORTING
            pernr                          = ins_objects-objid       "#EC DOM_EQUAL
            actio                           = 'INS'
            tclas                           = tclas
            dialog_mode               = dial_mode
            luw_mode                  = '0'
            no_existence_check = $cross
            no_enqueue              = $cross
          IMPORTING
            return1                       = return
            hr_return                    = hr_return
          TABLES
            proposed_values    = proposed_values.
        REFRESH proposed_values.
     IF hr_return-msgty = 'E'.                           "note 984409
      CLEAR protocol_error.
      protocol_error-msgty = hr_return-msgty.
      protocol_error-msgid = hr_return-msgid.
      protocol_error-msgno = hr_return-msgno.
      protocol_error-msgv1 = hr_return-msgv1.
      protocol_error-msgv2 = hr_return-msgv2.
      protocol_error-msgv3 = hr_return-msgv3.
      protocol_error-msgv4 = hr_return-msgv4.
      READ TABLE t_hrobjinfty WITH KEY objid = hr_return-pernr
                                       infty = hr_return-infty
                                       subty = hr_return-subty.
      protocol_error-segnum = t_hrobjinfty-segnum.
      protocol_error-routid = 'create_prf_pa_pb_object'
As mentioned above, the error message is only placed in the parameters Return and Return1 and not in HR_RETURN.please read the first reply

Hi,
I think you have preety much done from your end itself .
Could you please tell me what you got in this parameters:
     protocol_error-msgty = hr_return-msgty.
      protocol_error-msgid = hr_return-msgid.
      protocol_error-msgno = hr_return-msgno.
      protocol_error-msgv1 = hr_return-msgv1.
      protocol_error-msgv2 = hr_return-msgv2.
      protocol_error-msgv3 = hr_return-msgv3.
      protocol_error-msgv4 = hr_return-msgv4.
It may help us to track down the issue in more better way .
Thanks!

HRMD_A status 53 with NO ACTUAL DATA TO SAP t-code PA30

Hi,
We are trying to load the HR minimaster reocord from a flat data file to R/3.
I have created an iDoc through WE19 for message type hrmd_a and basic type hrmd_a06.
Populated infotypes for 0000, 0001, 0002 and 0003.
idoc created with status 53 (green light) 'Application documention posted' and information note 'HR: ALE inbound processing for HR master data'.
HOWEVER, when I go to transaction PA30, the personnel record is not being created in R/3.
I wonder if it has to do with the partner profile setup. Currently I have pointed the receiver information to my system.
Please kindly help on this. THANK YOU SO MUCH!
Rgds, MP

Hi MP,
Did you look in the PAXXXX tables to verify if any data truly made it into the infotypes?
You may also want to check the settings in table T77S0 under group HRALX as there are some entries that control how the HR module and IDOC's work together. For example setting "HRALX MERID" impacts error handling within the IDOC. You can use F1 on these to get more information.
Paul

How to add custom infotype in ALE for HRMD_A message type

Hi Friends-
Pls help me for our req we are using HRMD_A Message Type for HR master data but now we need to add one custom infotype ( 9902 ) also in standard ALE filters for this message type how i can do that pls let me know ?
<<removed_by_moderator>>
Regards
Meeta & Glory
Edited by: Vijay Babu Dudla on Dec 14, 2008 11:38 PM

Hi
Thanks for your support,
Pls let me know which steps i should go ? my secanrio is inbound side only,
step 1 ) Define idoc extension for HRMD_A01 using WE30 transaction and define it in partner profiles
step 2) do i need to write some code in BADI also to update information for my custom infotype also if yes then where and which BADI pls let me know ? because already am working on one badi HRALE00INBOUND_IDOC for few validation for incoming data.
step 3 ) add this new custom infotype in my standard ALE filters.
Pls let me know if am mistaking some where or if i have to do some thing else ?
Regards
Meeta & Glory

Message Type HRMD_A or HRMD_B or HRMD_ABA

Hi,
We have a requirement to update HR Master Data into our SAP System from
an External System via Middleware (TIBCO in this case)
Our SAP System details are as follows: -
ERP 6.00, HR 6.00, WebAS 701
By Updating Master Data into the system we mean: -
1) Update existing PA and PD InfoType records
2) Insert new PA and PD Infotype records
3) Update data into Custom Infotypes / Custom fields in standard
infotypes
I have read quite a few SAP Notes and Support Messages (Application Area
BC-BMT-OM-ALE and others) and even the Documentation in SALE
transaction, but I am not fully convinced which one to use for my
requirement
Here's my observation on these message types: -
HRMD_A   > is quite exhaustive (has maximum number of infotypes) and SAP
recommends to use this for SAP HR to SAP HR distribution
HRMD_B   > Support Message 1082157_2005 says to use this for External
System Transfers which is what I need but has only a few PD infotypes
and nothing else (I would not like this either)
HRMD_ABA   > Contains limited number of PA and PD infotypes e.g. some
very basic infotypes like 0027 are not present. Also SAP recommends this
to use for SAP HR to SAP system without HR components such as CRM, EBP,
etc.
But the Documentation in SALE appears speaks something different. It
says
HRMD_B   > Distribution from SAP HR to an SAP Basis System. This is
quite different from what is mentioned in message 1082157_2005 which
says it can be used for legacy data transfer
So what would be the right message type for...
A) Inbound HR Master Data / Org. Dataposting
B) Outbound Master Data / Org. Data distribution from SAP
especially when a non-SAP system is involved
Please note that the Idoc must be flexible and support updates into any
PA-PD infotypes (through Idoc extensions and BADI/customer exit
implementations if needed which is fine with me)
Thanking You in advance
Regards,
Aditya

Hi,
The message types used for HR are:
HRMD_B: transfer data from legacy systems, non SAP system. (E.g. People Soft).
HRMD_A: transfer data between 2 HR systems.
HRMD_ABA: transfer data from an HR system to a #non-HR# system (CRM, SRM, etc..)
You should use message type HRMD_B to transfer data from HR system to external system (Northgate Arinso) but it has only a few PD infotypes and nothing else.
Hope it helps,
Regards
Christine

ALE Message type HRMD_A Infotype 0001 is incorrect using PROOF flag = X

Hi
We have an issue using HRMD_A for Infotype 0001 with the PROOF flag swithed on. Using the PROOF flag triggers a call of HR_MAINTAIN_MASTERDATA instead of a direct write to db tables. However sometimes the update of Infotype 1 is incomplete and records are lost. The data goes through a transformation in the inbound BAdi, here I have checked the sequence is still correct. But when the data is written to Infotype 1 it seems to overwrite the last entries.
If anyone has any experience with this, I would be very interested for any input.
Thanks in advance
Sonny

Hi Sandip
Thx for your response. If I understand you correctly you suggest I use the HR_INFOTYPE_OPERATION. This could be an alternative, but I would prefer to understand the reason behind the error.
HR_INFOTYPE_OPERATION actually calls HR_MAINTAIN_MASTERDATA, so this FM might not solve the issue, but it does give the option for updating one record at a time.
Sonny

ALE - Status 52 Idocs for HRMD_A message type

HRMD_A Idocs in target system are not completely posted, turning into status '52'. Most of the times the infotype 1001 idoc with relations ship 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 help on this appreciated.

Hi Santosh,
If you haven't found by now the .... here is the Solution:
First change the size of table T77S0 check out note 305688
Then process the IDOCS again - check out note 363187
Regards
Luis

HRMD_A IDOC Question

Hi,
I am fairly new to this whole thing and I hope I could explain as clearly as possible and if someone could help me please, much appreciated.
1) If using HRMD_A or a reduced message type based upon HRMD_A for INBOUND loading, will that flag change pointer to pickup the data so that a separated reduced message type could pick the data from the RBDMIDOC extraction from change pointers?
2) I have created the the partner profile and all the rfc connection. I am trying to use WE19 to test the INBOUND. Using HRMD_ABA, I only activates E1P1000. In there I've populated the appropriated fields, click on "Standard Inbound" and got a green light successful. From there I've checked WE02 and it showed green light. However, when I check in HRP1000 table, I can't seem to find the record I was trying to do the test INBOUND on. Any suggestion or ideas?
3) Anyone here done OUTBOUND w/change pointers against HRMD_A06 and have that feed over to XI? I am trying to write a functional spec and would much appricated to know if this has been done and could contact you for questions.
Thanks a mill!
KN

anyone?

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

HRMD_A - inbound

Similar Messages

Maybe you are looking for