IDOC HRMD_A07 delimit of records

In ECC 6.0, we are using HRMD_A07 Idoc to update infotype 0169 using update data received from a third party application. In XI,
We are creating the Idoc with Update Code "U" with E1PLOGI, E1PITYP and E1P0169 segments.
E1P0169 has the data for the latest record.
When the IDOC is posted the new record is created but it does not delimit the previous record. Which should happen because the infotype 0169 is time constrain '2'.
Is there a piece of config that controls this?
Experts please advise.
Regards,
Jilly

For this I have got a solution as in the E1PLOGI segment there is a field 'PROOF'. If I select is i.e. have its value as 'X' then the records are getting delimited.
SAP in its note 134085 says that the PROOF flag should remain empty and then there is no refernce about the PROOF flag. So what i still want to know is has anybody tried using it and has faced any issue using the PROOF field byt keeping it selected.
Thanks,
Jilly

Similar Messages

Inbound IDoc(HRMD_A07) problem in delimiting the infotype records

Hi All,
I am using Inbound IDoc (HRMD_A07) approach to update infotypes. I found that I am able to create a record in an infotype, but there is a problem in delimiting the infotype.
Please help me out in case I am missing something.
Thanks,
ABAP_DEV

Hi,
Did you get this resolved. Even i'm facing this issue. Is it a config or do we have to do something in the IDOC.
Thanks,
Jilly

Qualifcation text in IDOC HRMD_A07

Hi Gurus,
We are able to trigger IDOC HRMD_A07 with message type HRMD_A. The integration switch between PA & PD is active (PLOGI Quali). Now whenever qualification is deleted, the idoc records only the object id of qualification. Is there any way for getting text of the qualification along with the object id.
We are avoiding customization, hence please share only a standard way ( without abap code) to resolve the issue.
Regards
Minal

Dear Minal,
the idoc inbound process does not need a text for deletion, the key is sufficient, but I think your intension is something different.
I asume you want the text to be part of the idoc for identification (nobody remembers the id of a qualification, but the description).
In that case I have bad news.
As the idoc creation process (e.g from change pointers) is executed after the deletion has taken place and change pointers do not contain data like text, no text is present anymore that could be added to the idoc.
Regards,
Michael

Fm to create, modify delimit the records in master data for org mag

hi,
    There is a fm hr_infotype_operation to create, modify, delimit the records for one infotype of pernrs.
Like this I want fm through which i can create, modify the records to master data of organisational management (OM). Whatever the infotype i will enter in that fm and data it will create a new record in OM master data.
          If anybody know this, please tell me.
thanks & regards,
    Sekhar.

Hi,
Try RH_UPDATE_INFTY.
RH_INSERT_INFTY.
RH_DELETE_INFTY.
Regards,
Dilek

Mandatory fields for inbound - idoc HRMD_A07

Hi All,
I need to create an Employee master record in R/3 by triggering an idoc .
i came to know ,i can use "HRMD_A07" .
can any one help me giving the mandatory datas to trigger the HRMD_A07.
Thanks & Regards,
Arun

Hi,
PA objects exist if infotypes 0000, 0001, and 0003 have been created.
So fill the segment accordingly, but I am not sure whether you can directly create the employee from Idoc, you may have to take the Idoc option of LSMW.
Br/Manas

How to get IDoc number using sdata records

Hi Experts,
I have executed a report program in background. Its generating few IDoc's. I can view those idoc's in WE05 also. But now i want to display those idoc number in the result output of the report. One of the segment having materrial number and plant details in the IDoc. Using this details i want to display the IDoc number in the output screen. Even i have tried with EDID4 table its taking huge time to get a single IDoc. Is there is any simplest way is there to get those idoc's .
Otherwise how to achive this?
Thanks and Regards,
Mohana

Hi,
1.)If you want the ouput in the same report program which triggers the idoc, it is better to use the control record information.
You will get IDoc Number from XEDIDC(check the below code) and you can store the idoc number into an internal table if more idoc is expecting to be triggered.
     call function 'MASTER_IDOC_DISTRIBUTE'
          exporting
            MASTER_IDOC_CONTROL        = EDIDC
          tables
            COMMUNICATION_IDOC_CONTROL = XEDIDC
            MASTER_IDOC_DATA           = XEDIDD
          exceptions
            others                     = 5.
   read table xedidc index 1.
append xedidc-docno to it_docno.
And finallly use this to display in the output.
2.) if u want it in a seperate report, then select based on date, idoctype, messagetype
Regards,
Sajith

IDOC to FIle multiple records

HI Experts,
My scenario is IDOC-FILE and i need to collect idocs and send it to XI. So i am using XML PORT.
The vendor master file is reaching the directory that i specified in receiver communication channel.but only one record is existing in that even i send multiple idocs.
i had configured the messege mapping with the external message that i imported as XSD(changed the idoc occurence max= unbounded) and i used the same for interface mapping.
what can be the problem .
Thanks in Advance,

HI,
This problem due to occurance mapping, check sender and receiver structure occurance fields mapping.
In sender partner profile outbound configuration select collection idoc option
source                 target
segment (0..un)-----> row(0..un)
             field1................field1
             filed2................field2
this mapping will sort out your problem

IDOC Number for a record

Hello All,
I am working in HR. If I have a record created by IDOC, is ther any way for finding IDOC number that has created this record.
Regards,
Rahul

Hi Sergie
The ALEAUD is a separate IDoc, so naturally it must have a different number than the original IDoc. However, the field E1STATE/DOCNUM in ALEAUD is a reference to the original IDoc.
How is your ALEAUD generated? If you are doing this "manually" via a message mapping, you need to include the original IDoc number in the message to your receiving system so that it can send an audit message back containing the original IDoc number. From this audit message you should be able to map a correct ALEAUD message.
Regards,
Thorsten

BAPI or IDOCs for Quality info records

I want to know which BAPI or IDOCs is used to upload the Quality info records data from legacy system to SAP.

Hi Raghu
Below is the BDC program I was used for the same.
Program Name : YX30_UPLOAD_QUALITY_INFO
Author : Rameshwar Yadav *
Date : 2006-11-27 *
Description : The purpose of this program is to upload the *
Quality Info Record for I30 System *
Original Transport Number : I30K903055 *
SYS id: SYS_30_1502_03_41_Upload Quality Info Records *
TDS id: TD_30_1502_03_41_Upload Quality Info Records *
UT ID: UT_30_1502_03_41_Upload Quality Info Records *
======================================================================
Change History *
Date | Change No | Name | Description *
yyyy/mm/dd | AAAYYYYMMDD | xxxxxxxxxxxx | *
REPORT YX30_UPLOAD_QUALITY_INFO MESSAGE-ID yx30_conversions
no standard page heading line-size 255.
include yx30_upload_quality_info_top. "Include for Variable Declaration & Selection Screen
include yx30_upload_quality_info_data. "Include for File read & Authority Check
*& At Selection Screen Output *
AT SELECTION-SCREEN OUTPUT. "PBO
PERFORM fill_parameters.
*& Start Of Selection Event *
start-of-selection.
Perform Authority_check. "Subroutine for authority check
Perform prepare_file. "Subroutine for preparing file
perform file_read. "Subroutine for File read
perform update_qi01. "Subroutine for Uploading data
perform write_error_log1. "Subroutine for writing error log
*& Form write_error_log
text
--> p1 text
<-- p2 text
*& Include YX30_UPLOAD_QUALITY_INFO_TOP
Type Declaration
Types: Begin of type_qtyinf,
matnr type matnr, "Material No
lieferant type char10, "Vendor
werk type werks_d, "Plant
frei_dat type char10, "Frei_Dat
stsma type char8, "Stsma
anwso_01 type char1, "ANWSO(01)
anwso_02 type char1, "ANWSO(02)
anwso_03 type char1, "ANWSO(03)
end of type_qtyinf.
Internal Table Declaration
Data: itab_qtyinf type standard table of type_qtyinf. "Internal table for QTYINF.
Work Area Declaration
Data: wa_qtyinf type type_qtyinf. "Work Area for QTYINF.
Variable Declaration
Data: v_file_qtyinf type string, "Source File Name
v1 type string,
v2 type string,
v3 type string,
v_file_return type string,
v_lin TYPE n.
*Selection Screen Declaration
selection-screen *
SELECTION-SCREEN BEGIN OF BLOCK blk1
WITH FRAME TITLE text-s01.
PARAMETER:
p_sysid(3) TYPE c OBLIGATORY , "Source System
p_bukrs(4) TYPE c OBLIGATORY , "Source CompCode
p_samshr type char30 lower case obligatory default '/sap_upload/' , "Samba Share Drive
p_object TYPE CHAR10 OBLIGATORY default 'MAT' . "Migration Data Object
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN SKIP 3.
PARAMETER:
cb_pfill TYPE c AS CHECKBOX DEFAULT 'X' . "Prefill values?
SELECTION-SCREEN COMMENT /1(79) text-s1a.
SELECTION-SCREEN BEGIN OF BLOCK blk3
WITH FRAME TITLE text-s03.
PARAMETER:
pa_filn1(500) TYPE c LOWER CASE
VISIBLE LENGTH 50 , "Filename AppServer
pa_dlimt TYPE c DEFAULT ';' . "Field Delimter
SELECTION-SCREEN END OF BLOCK blk3.
include bdcrecx1. "Include for the subroutine
*& Include YX30_UPLOAD_QUALITY_INFO_DATA
*& Form file_read
Subroutine for reading the source file into internal table
--> p1 text
<-- p2 text
FORM file_read .
DATA:
single_line TYPE string .
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_qtyinf FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
DO.
READ DATASET v_file_qtyinf INTO single_line. "Reading the content of file into line
IF sy-subrc = 0.
IF sy-index > 1. "skip header-line
SPLIT "Split the content of line into work area
single_line
AT ';'
INTO
wa_qtyinf-matnr "Material No
wa_qtyinf-lieferant "Vendor
wa_qtyinf-werk "Plant
wa_qtyinf-frei_dat "Frei Date
wa_qtyinf-stsma "STSMA
wa_qtyinf-anwso_01 "ANWSO_01
wa_qtyinf-anwso_02 "ANWSO_02
wa_qtyinf-anwso_03. "ANWSO_03
APPEND wa_qtyinf TO itab_qtyinf. "Appending Work Area to internal table
ENDIF.
ELSE.
EXIT.
ENDIF.
ENDDO.
CLOSE DATASET v_file_qtyinf. "Closing the files
ELSE.
MESSAGE e015 .
ENDIF.
DESCRIBE TABLE itab_qtyinf LINES v_lin.
IF v_lin LT 0.
MESSAGE e016 .
ENDIF.
ENDFORM. " file_read
*& Form fill_parameters
Subroutine for getting the file name
FORM fill_parameters .
IF cb_pfill = 'X'.
Preparing QTYINF File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO pa_filn1.
ENDIF.
ENDFORM. " fill_parameters
*& Form Authority_check
Authority Check
--> p1 text
<-- p2 text
FORM authority_check .
Authority Check For the Migration
AUTHORITY-CHECK OBJECT 'YX30_MIGR'
ID 'SYSTEM' FIELD p_sysid
ID 'BUKRS' FIELD p_bukrs
ID 'YX30_DMOBJ' FIELD p_object
ID 'ACTVT' FIELD '16'.
IF sy-subrc <> 0.
MESSAGE e010 WITH p_sysid p_bukrs p_object.
ENDIF.
ENDFORM. " Authority_check
*& Form prepare_file
text
--> p1 text
<-- p2 text
FORM prepare_file .
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO v_file_qtyinf.
CLEAR v3.
CLEAR v2.
Prepare Return File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_RETRUN_LOG_' p_bukrs '.CSV' INTO v2.
CONCATENATE '/sap_upload/' v3 '/' 'MAT' '/' v2 INTO v_file_return.
ENDFORM. " prepare_file
*& Form update_qi01
text
FORM update_qi01.
PERFORM open_group. "Opening a session
CLEAR wa_qtyinf.
LOOP AT itab_qtyinf INTO wa_qtyinf.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0100'. "Subroutine for mapping data
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-MATNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'QINF-MATNR'
wa_qtyinf-matnr. "Mapping the material
PERFORM bdc_field USING 'QINF-LIEFERANT'
wa_qtyinf-lieferant. "Mapping the vendor
PERFORM bdc_field USING 'QINF-WERK'
wa_qtyinf-werk. "Mapping the plant
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=STAN'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-STSMA'.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma. "Mapping the status
PERFORM bdc_dynpro USING 'SAPLBSVA' '0201'.
PERFORM bdc_field USING 'BDC_CURSOR'
'J_STMAINT-ANWSO(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=OKAY'.
IF wa_qtyinf-anwso_01 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01. "Mapping the anwso(01)
ELSEIF wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02. "Mapping the anwso(02)
ELSEIF wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03. "Mapping the anwso(03)
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ENDIF.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-FREI_DAT'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=QMBU'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma.
PERFORM bdc_transaction USING 'QI01'.
ENDLOOP.
PERFORM close_group. "Closing the session
ENDFORM. "update_qi01
*& Form write_error_log
text
--> p1 text
<-- p2 text
FORM write_error_log1 .
DATA:
single_line TYPE string,
v_msg TYPE string,
v_msg1 TYPE string.
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_return FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
CONCATENATE text-020 v_lin INTO v_msg SEPARATED BY space.
CONCATENATE text-021 v_lin INTO v_msg1 SEPARATED BY space.
TRANSFER: v_msg TO v_file_return.
TRANSFER: v_msg1 TO v_file_return.
WRITE:/ v_msg.
WRITE:/ v_msg1.
ENDIF.
ENDFORM. " write_error_log
Regards,
Sree

Can IDocs Hold only status records?

Hello,
Can IDOCS (inbound/outbound) hold only status records ? If yes, then pls give details.
Many Thanks,
Kishan

I understand the question like...
1.You recieve an Inbound Idoc in to the system.
2.Now, you need to send the status value of the above inbound Idoc to the middleware system(biztalk)
3.You can create custom Idoc with the segment having field as Status values and send it as outbound Idoc to the target system
(OR)
4.Run the stadard program which I have metioned above and you will get a ALEAUD Idoc generated automatically and it will be sent to the destination based on the partner profile assignment that you have done in WE20.
5. For partner profile assignment, go to we20 select the target logical system and add the ALEAUD message type as outbound Idoc
Hope everything is clear. You can get all the above details by giving a search in ABAP Data transfers section in SDN.
Thanq

Idoc HRMD_A07

Hi Friends,
Present requirement is like this using message type HRMD_A & Change pointers with Distribution model generate the IDOC &
transfer to the extenal system.
Kindly guide the below condition how to work.
" If you want to distribute HR master data infotypes, infotypes 0000, 0001, 0002, and 0003 must be distributed. Infotype 0003 is only distributed by change pointers if it has been changed in combination with one of the other HR master data infotypes that are supported".
Thanks and Regards,
Sai

This cant be done with ABAP, only with customizing.

IDOC HRMD_A07 - E1PAD31

Hi All,
We are using the global message type HRMD_A to transfer the data to local system. But i am not getting the expected results in following 2 scenarios
Scenario 1)
Additional relationships for LSO. e.g. A032. when a employee is hired the qualification for the employee is also maintained and when we try generate the IDOC using the change pointers 2 IDOC gets generated.
1) with all the infotype except the IT0024 data
2) Only the data related to the relationship A032 and segment E1PAD32
Same is happening for other additional relationships like A025 etc.
Scenario 2)
When a future dated position (position validity date starts in future) is created in SAP system No IDOC gets generated from the change pointers.
But if we create the position as on today or back dated (position validity date starts from today or back dated) the IDOC gets generated.
we already checked the filter group and we think there is no problem in the filter groups.
Please let us know if any one has already faced the similar issues.
Regards,
Umesh Chaudhari

Hello All,
Any help on this?
Regards,
Umesh

Outbound Idoc HRMD_A07

Hi Friends,
Kindly help me any one know about how to work outbound interface using Idoc type HRMD_07 message type HRMD_A in PA& any one have details design process document please help me.
Thanks and Regards,
Sai .

You can trigger the IDOC for the PA* infotypes using the change pointer. This will trigger the OUTBOUND idoc for master data changes in teh PA30/40 tracnasactions.
Activities to be done:
1. Enable change pointers globally
2. Activate the change pointer for the message type HRMD_A
3. Run RBDMIDOC program to generate the IDOCs. This would create IDOCS for the changed/Created HR master data
Thanks,
Saibaba
Edited by: Saibaba Kondani on Aug 5, 2009 1:50 PM

CLFMAS IDoc - Issue in Data Record Population

Hi Experts,
My SAP systems are configured in such a way where CLFMAS Idoc is triggered based on Change Pointers.
The field 'Class Type' (KLART) is filled in the IDoc as '022' whereas the actual value is '023'.
I debugged through the function module generating the IDoc. I see that the value being passed to 'MASTER_IDOC_DISTRIBUTE' is correct, but once IDoc gets generated, the value seen in transaction WE02 is wrong.
Where might the value possibly be getting changed?
Kindly help me here.
Thank you.
Regards,
Keerthi

Hi,
I understand your point.
But wont such Customer Functions be called before the function module MASTER_IDOC_DISTRIBUTE gets called?
I see that the values in EDIDD are consistent till they are passed to MASTER_IDOC_DISTRIBUTE. Its only when the IDoc is actually created that I see the values are changed.
Thanks & Regards,
Keerthi

IT0169 and delimit the records

Hi Experts,
I have 4 plans A,B,C,D (subtype) under IT 0169 (Savings plans)
My requirement is:
IF i have a record for subtype A and I want to create a new record for subtype B than Subtype A should be delimited with end date = start date of subtype B and vis-a-versa.
Pls let me know how to achive this scenario.
Regards
Sachin

There is a user exit you can implement for modifying IT0169. Go ahead implement that for your custom needs. I had used the same for other purposes related to IT0169. Hope it helps

IDOC HRMD_A07 delimit of records

Similar Messages

Maybe you are looking for