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

Similar Messages

Filter Infotypes based on Company Code for the Message Type HRMD_A

Hi,
I have a requirement to send different infotypes for different Company codes using the same distribution model for the message type HRMD_A.
Example :
For the BUKRS 2500 I need to send infotype 0000 ,0002,0006
For the BUKRS 2600 I need to send infotype 0000 ,0008,0009
It will be a great help for me if any one can guide me on that.
Regards,
Raka

Hi ,
Thanks for the reply.
I alredy have done that . But its not working.
Its working only for infotype 0001.
If the infotype is there in any of the filter groups, the data will be sent irrespective of the Com Code.
Regards,
Raka

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

Problems with PROOF field in idoc (message type HRMD_A)

Hello,
I'm using the standard message type HRMD_A with IDOC base type HRMD_A06 and the function module IDOC_INPUT_HRMD.
I have a doubt with field 'PROOF' when I fill the IDOC. Does anybody know for what is it used? For example, what's going to happen if I put PROOF = 'X' in an update operation?
In my case I have tested that when PROOF = 'X', I receive the following warning in intotype 0001:
    The EMPLOYEE_ORG_ASSIGNMENT-ADMINISTRATOR_GROUP field is not maintainable in dialog, so it is ignored
    The EMPLOYEE_ORG_ASSIGNMENT-ORG_UNIT field is not maintainable in dialog, so it is ignored
    The EMPLOYEE_ORG_ASSIGNMENT-COSTCENTER field is not maintainable in dialog, so it is ignored
but I cannot be sure if these warnings are due to PROFF.
In the change data record screen, I have filled the following fields: plan version ('01'), object type ('P'), object id (employee number), PROOF ('X'), Operation ('U'). Structure for the idoc is EDIDC->E1PLOGI->E1PITYP.
Any help on this?

Hello,
I'm using the standard message type HRMD_A with IDOC base type HRMD_A06 and the function module IDOC_INPUT_HRMD.
I have a doubt with field 'PROOF' when I fill the IDOC. Does anybody know for what is it used? For example, what's going to happen if I put PROOF = 'X' in an update operation?
In my case I have tested that when PROOF = 'X', I receive the following warning in intotype 0001:
    The EMPLOYEE_ORG_ASSIGNMENT-ADMINISTRATOR_GROUP field is not maintainable in dialog, so it is ignored
    The EMPLOYEE_ORG_ASSIGNMENT-ORG_UNIT field is not maintainable in dialog, so it is ignored
    The EMPLOYEE_ORG_ASSIGNMENT-COSTCENTER field is not maintainable in dialog, so it is ignored
but I cannot be sure if these warnings are due to PROFF.
In the change data record screen, I have filled the following fields: plan version ('01'), object type ('P'), object id (employee number), PROOF ('X'), Operation ('U'). Structure for the idoc is EDIDC->E1PLOGI->E1PITYP.
Any help on this?

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

How to send inforecord conditions using ALE (message type COND_A)?

Hi,
I have sent Purchasing Inforecords through ALE using t-code ME18.
Now, I would like to know how to transfer the conditions through ALE (message type is COND_A).
Thanks a lot,
Kaveri

Hi,
Please go through this thread.
[Pricing Condition Records initial upload - COND_A]

Why my iphone produces a bug after it renew for OS5.1.1. The bug is when I use message, type a Chinese word, and then using a releveant word, then the program automately closes. Every time I try the same procedure, it definitely closes.

Why my iphone produces a bug after it renew for OS5.1.1. The bug is when I use message, type a Chinese word, and then using a releveant word, then the program automately closes. Every time I try the same procedure, it definitely closes.

Nobody knows? Not even administrators?
Please it would be really nice to have help on that to take all the benefit of the remote app.
Thank you very much in advance.

ALE message type WMTORD sending ST meins

good morning/afternoon to all,
we are in the process of setting up a 3rd party warehouse/miniload system and they connect using ALE. the 3rd party system is not a SAP system. our system is 4.7C. we are being asked to use this message type (WMTORD - standard) to send transport orders. they receive the idoc successfully with correct information, except for the unit of measure field meins. they receive the untranslated unit of measure ST, instead of EA.
is there a fix for this? can this be changed with standard code, or is a user exit needed. and, if the user exit is needed, why does for example the message type MATMAS send a EA and not the ST? i do have the global unit or measure ST setup to send EA in spro.
thanks in advance.

it looks like no one knows the answer...
here is what i found (for future reference)
enhancement MWMIDO01
component(fm) - EXIT_SAPLLIDO_001
include - ZXLIDU01
code example
tables: e1ltori.
loop at t_idoc_data.
if t_idoc_data-segnam = 'E1LTORI'.
    move t_idoc_data-sdata to e1ltori.
    if e1ltori-meins = 'ST'.
      move 'EA' to e1ltori-meins.
    endif.
    move e1ltori to t_idoc_data-sdata.
    modify t_idoc_data.
endif.
endloop.
*****solved*****

Details for ALE Message type 'INVOICE' for intercompany billing ?

Hi all,
I have a requirement that i have to create the Invoice receipt for FI when the billing document is created ( VF01) in the same client?
Please provide me the details for this
such as output type , process code and other master data settings that have to fill?
Thanks,
Vamshi.

Hi prakash,
Thanks for the reply and it is very helpful.
But i am using message type RD00 and shall i use this?
Else, please specify the details that i have to maintain to use RD04 clearly stap-by-step?
Thanks,
Vamshi.

Distribution Model (ALE) - Message type has to be deleted from model view

Hello,
I want to delete a message type from an existing model view in the distribution model (of the maintenance system).
But when I mark the concerning message type and press Edit->Delete the message 'Action cannot be carried out on the nodes selected' occures. Deleting the complete model view would work...
Does anyone know how I can get this without setting up a new model view?
Many thanks in advance,
Juergen

hi,
>>'Action cannot be carried out on the nodes selected'
you get this message if you try to delete a message type
from a model view that was not created on your system
(it has been replicated and it's maintained on another system)
so you can only delete this message type on the system that has
"master" distribution model
if it's not master then it's usually grey and you can only delete if it's black in change mode
>Deleting the complete model view would work...
if you try that you will see info that it's not the "master" system for this model
check it and let me know
Regards,
Michal Krawczyk

ALE-message type

Hi all
I have created a z-message tyoe and attatch with the basic and extention idoc type in WE82 .
Now if i go to database table TBDME or in EDP13 i did not found my enteries.
How can i acheive that. Please suggest me.
Thanks

Hi
no it wont worked with BD57 i already Tries with that.
othere solutions?

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

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

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

Same message type in Diffrent Interface IDoc-HRMD_A

Hi All.
i am using standard message type HRMD_A iin one IDoc and have done coding in one of the Function Exit ..EXIT_SAPLRHA0_001
now if some other interface is also running using same satndard message type then how can i restritct my EXIT code to run for the 1st one only..like 1st one is running for country say Alaska and 2nd one for Ohio then how to make a check to diffrentiate between these two...as there is no Control data is populated before triggering this Function exit.i have done filteration in the exit like it will pass the data for the Alaska country only rest will be filtered out.but for the Ohio i want some other filyteration.Please assist.
Mona singh.

Hi Mona,
One question, just to see if I understood, the filter you want to use is by Company Code? or which is the field you want to use as a filter? You want some information to be sent to the destination and the other don't ?
Or you just want that the internal code in that Exit is to be executed for especific filter?
I ask, because there is a way to filter by company code the whole IDOC.
Regards
Edith

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

Similar Messages

Maybe you are looking for