Problem in Extended Idoc

Hi All,
I have Extended ORDERS05 for adding custom fields for inbound process,
Steps i have fallowed to create Extend Idoc:
1,Created new segment with all Z-fields and released,
2,Created Extension Idoc with reference standard Idoc ORDER05, and added custom segment under standard segment E1EDP01,
released Extend Idoc,
am able to see all Z-fields in Z-segment,
but my problem is am unable to see any standard fields under any standard segment in my Extended Idoc?
why am not able to see all standard fileds?
Regards
suresh.d

Hi,
Are you checking in WE30 or in WE02?
In WE30 you cans ee only Segment names.
Give the segment name in SE11 and then see if you are able to see the fields.
Regards,
Sravan

Similar Messages

Problem about extended IDOC(urgent)

Hi experts,
i have idoctype,extended idoc,and one include.. i need modify that according to the requirement.. here i will give the idoctype and extended idoc type and include program .. please help me where exactly i need to do the change and what are the steps required for the requirement..
Exact Requirement: Modify the program which populates the idoctype invoice02 and extension zinvoice02 , if netvalue is zero(vbrp-netwr = 0) then populate the idoc segment E1EDP01.E1EDP26 , BETRG WITH QUALF = # 011' WITH ZERO VALUE. curently segment is not populated.
Please help me in this and explain the steps required for this.
idoctype:invoice02
extended idoc:zinvoice02
include:ZXEDFU02
 Here i am giving the include program
CASE dobject-kschl.
WHEN 'ZGRI' OR 'ZGDF' OR 'ZGRN' OR 'ZGAE'.
 t_int_edidd[] = int_edidd[].
 t_xtvbdpr[] = xtvbdpr[].
 ta_xvbdkr = xvbdkr.
 CASE int_edidd-segnam.
 WHEN 'E1EDK01'.
 ta_e1edk01 = int_edidd-sdata.
 PERFORM get_shipment_data.
 PERFORM get_route_data.
 int_edidd[] = t_int_edidd[].
 WHEN 'E1EDP01'.
Update segment E1EDP01
1. Update field E1EDP01-PSTYP
2. Accumulated net weight & quantity of batch split items against
E1EDP01 segment of the main invoice item.
 ta_e1edp01 = int_edidd-sdata.
 i_tabix = sy-tabix.
 CLEAR: ta_e1edp02. "DIAG01+
 PERFORM update_segment_e1edp01.
 MOVE ta_e1edp01 TO t_int_edidd-sdata.
 MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
Populate segment Z1EDP08
Fields: ZZDESPACTY_A, ZZACTYUOM
 PERFORM validate_segment USING control_record_out-idoctp
 control_record_out-cimtyp
 'Z1EDP08'
 CHANGING n_subrc.
 CHECK n_subrc EQ 0.
 PERFORM calc_invoice_item_zzdespacty_a. "DIAG02+
 int_edidd[] = t_int_edidd[]. "DIAG02+
 WHEN 'E1EDP02'. "DIAG01+
 IF int_edidd-sdata(3) = '016'. "DIAG01+
 ta_e1edp02 = int_edidd-sdata. "DIAG01+
 ENDIF. "DIAG01+
 WHEN 'E1EDP19'.
Populate segment Z1EDL24
Fields: Material Characteristics or Material Class '001'.
 PERFORM validate_segment USING control_record_out-idoctp
 control_record_out-cimtyp
 'Z1EDL24'
 CHANGING n_subrc.
 IF n_subrc EQ 0.
 ta_e1edp19 = int_edidd-sdata.
 CASE ta_e1edp19-qualf.
 WHEN '002'.
 PERFORM get_mat_characteristic USING ta_e1edp19-idtnr.
 PERFORM fill_segment_z1edl24.
 int_edidd[] = t_int_edidd[].
 WHEN OTHERS.
 ENDCASE.
 ENDIF.
 WHEN 'E1EDP26'.
Populate segment E1EDP26
Fields: BETRG
 i_tabix = sy-tabix.
 ta_e1edp26 = int_edidd-sdata.
 IF ta_e1edp26-qualf = '001'. "Gross Price which is always present
 PERFORM fill_segment_e1edp26.
 int_edidd[] = t_int_edidd[].
 ENDIF.
 WHEN 'E1EDP08'.
Populate Segment Z1EDL37 *
Fields: Bespoke fields from Handling Unit (VEKP)
 PERFORM validate_segment USING control_record_out-idoctp
 control_record_out-cimtyp
 'Z1EDL37'
 CHANGING n_subrc.
 CHECK n_subrc EQ 0.
 ta_e1edp08 = int_edidd-sdata.
 PERFORM fill_segment_z1edl37.
Populate Segment Z1EDP08 *
Fields: Total Despatch Activity *
 PERFORM validate_segment USING control_record_out-idoctp
 control_record_out-cimtyp
 'Z1EDP08'
 CHANGING n_subrc.
 CHECK n_subrc EQ 0.
 PERFORM calc_invoice_item_acty_total.
 int_edidd[] = t_int_edidd[].
 WHEN OTHERS.
 ENDCASE.
WHEN 'ZGDW'.
Line above added line below removed - Assyst 73789
WHEN 'ZGIN'.
 t_int_edidd[] = int_edidd[].
 t_xtvbdpr[] = xtvbdpr[].
 ta_xvbdkr = xvbdkr.
 CASE int_edidd-segnam.
Start SU02
 WHEN 'E1EDK01'.
 ta_e1edk01 = int_edidd-sdata.
 i_tabix = sy-tabix.
Get the conversion factor
 PERFORM modify_exchange_rate.
 MOVE ta_e1edk01 TO t_int_edidd-sdata.
 MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
 int_edidd[] = t_int_edidd[].
End SU02
*************************************************************SAM01 START
 WHEN 'E1EDP02'.
Populate segment Z1EDP02
Fields: Reason code for sales order
 ta_e1edp02 = int_edidd-sdata.
 CASE ta_e1edp02-qualf.
 WHEN '002'.
 PERFORM fill_segment_z1edp02.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDP02'
 ta_z1edp02.
 int_edidd[] = t_int_edidd[].
 WHEN OTHERS.
 ENDCASE.
***************************************************************SAM01 END
 ENDCASE.
Start of JvdM01
WHEN 'ZGII'. "JvdM01
 t_int_edidd[] = int_edidd[].
 t_xtvbdpr[] = xtvbdpr[].
 ta_xvbdkr = xvbdkr.
 CASE int_edidd-segnam.
 WHEN 'E1EDK01'.
Populate segment Z1EDKSH and Z1REM_STE_CDE
Fields: Shipment Number for Invoice
 Reason code for sales order
 ta_e1edk01 = int_edidd-sdata.
 PERFORM fill_segment_z1edksh_ds.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDKSH'
 ta_z1edksh.
 PERFORM fill_segment_z1rem_ste_cde.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1REM_STE_CDE'
 ta_z1rem_ste_cde.
 int_edidd[] = t_int_edidd[].
 WHEN 'E1EDKA1'.
Populate segment Z1EDKA1
Fields: Customer Account Group
 ta_e1edka1 = int_edidd-sdata.
 CASE ta_e1edka1-parvw.
 WHEN 'RE'. "Bill To Party
 PERFORM fill_segment_z1edka1.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDKA1'
 ta_Z1EDKA1.
 int_edidd[] = t_int_edidd[].
 ENDCASE.
 WHEN 'E1EDP01'.
Read segment E1EDP01 for use later "JVDM02
 ta_e1edp01 = int_edidd-sdata.
 WHEN 'E1EDP02'.
Populate segment Z1EDP02
Fields: Reason code for sales order
 ta_e1edp02 = int_edidd-sdata.
 CASE ta_e1edp02-qualf.
 WHEN '002'.
 PERFORM fill_segment_z1edp02.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDP02'
 ta_z1edp02.
 int_edidd[] = t_int_edidd[].
 WHEN OTHERS.
 ENDCASE.
 WHEN 'E1EDP19'.
Populate segment Z1EDL24 and Z1EDP01 "JVDM02
Fields: Pack Size Activity for Material
 Total Activity for Invoice Item
 ta_e1edp19 = int_edidd-sdata.
 CASE ta_e1edp19-qualf.
 WHEN '002'.
 PERFORM fill_segm_z1edl24_and_z1edp01.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDL24'
 ta_z1edl24.
 PERFORM append_int_edidd TABLES t_int_edidd
 USING 'Z1EDP01'
 ta_z1edp01.
 int_edidd[] = t_int_edidd[].
 WHEN OTHERS.
 ENDCASE.
 ENDCASE.
End JvdM01
ENDCASE.
Start SU02 Code Comment for implementing IR 340
**mpc01 - start of insert
start assyst 73789
*IF dobject-kschl = 'ZGDW'."amersham invoices
**IF dobject-kschl = 'ZGIN'."amersham invoices
end assyst 73789
CASE int_edidd-segnam.
for the organisation data header
 WHEN 'E1EDK14'.
 MOVE int_edidd-sdata TO ta_e2edk14.
 where is qualifying organisation = 003 (delivering company code).
 IF ta_e2edk14-qualf = '003' AND ta_e2edk14-orgid NE space.
 SELECT SINGLE waers
 INTO t001-waers
 FROM t001
 WHERE bukrs = ta_e2edk14-orgid.
 IF sy-subrc = 0.
 t_int_edidd[] = int_edidd[].
 get the billing date for the invoice
 LOOP AT t_int_edidd WHERE segnam = 'E1EDK02'.
 MOVE t_int_edidd-sdata TO ta_e1edk02.
 IF ta_e1edk02-qualf = '009'."billing date
 w_fkdat = ta_e1edk02-datum.
 EXIT.
 ENDIF.
 ENDLOOP.
 if no invoice date use current date
 IF w_fkdat IS INITIAL.
 w_fkdat = sy-datum.
 ENDIF.
 change the general document header
 LOOP AT t_int_edidd WHERE segnam = 'E1EDK01'.
 i_tabix = sy-tabix.
 MOVE t_int_edidd-sdata TO ta_e1edk01.
 set the field to the default currency code for the company
 ta_e1edk01-hwaer = t001-waers.
 if the default value equals the idoc currency then exit
 IF t001-waers = ta_e1edk01-curcy.
 EXIT.
 ENDIF.
 get the exchange rates
 SELECT *
 INTO TABLE t_tcurr
 FROM tcurr
 WHERE kurst = 'NYB1' " SU01
 WHERE KURST = 'GEBU' " SU01
 AND fcurr = ta_e1edk01-curcy
 AND tcurr = t001-waers.
 IF sy-subrc NE 0."no values found
 error the idoc
 MESSAGE e400(vf) WITH c_exchange_rate_error
 RAISING error_message_received.
 EXIT.
 ENDIF.
 LOOP AT t_tcurr.
 convert to date from inverted date to normal date format.
 CALL FUNCTION 'CONVERSION_EXIT_INVDT_OUTPUT'
 EXPORTING
 input = t_tcurr-gdatu
 IMPORTING
 output = w_datum.
 CONCATENATE w_datum+6(4)
 w_datum+3(2)
 w_datum(2)
 INTO t_tcurr-datum.
 MODIFY t_tcurr.
 ENDLOOP.
 sort the exchange rates with the newest first.
 SORT t_tcurr BY datum DESCENDING.
 read the first value in the table ie the newest.
 LOOP AT t_tcurr WHERE datum <= w_fkdat.
 EXIT.
 ENDLOOP.
 IF sy-subrc NE 0."no values found
 error the idoc
 MESSAGE e400(vf) WITH c_exchange_rate_error
 RAISING error_message_received.
 EXIT.
 ENDIF.
Start SU01
Get the Exchange rate from the function module and populate
E1EDK01 TABLE
 w_fcurr = ta_e1edk01-curcy.
 call function 'CONVERT_TO_LOCAL_CURRENCY'
 exporting
 date = w_fkdat
 foreign_amount = '0'
 foreign_currency = w_fcurr
 local_currency = t001-waers
 type_of_rate = 'GEBU'
 importing
 exchange_rate = t_tcurr-ukurs
 exceptions
 no_rate_found = 1
 overflow = 2
 no_factors_found = 3
 no_spread_found = 4
 derived_2_times = 5
 others = 6.
End SU01
 ta_e1edk01-wkurs = t_tcurr-ukurs.
 change the header data in segment
 MOVE ta_e1edk01 TO t_int_edidd-sdata.
 update the current idoc segment
 MODIFY t_int_edidd INDEX i_tabix TRANSPORTING sdata.
 EXIT.
 ENDLOOP.
 update all of the idoc segments
 int_edidd[] = t_int_edidd[].
 ENDIF.
 ENDIF.
ENDCASE.
*ENDIF.
**mpc01 - end of insert
End SU02 Code Comment for implementing IR 340

Hi Venu,
Try with this code.
If vbrp-netwr = 0.
 WHEN 'E1EDP26.
CASE ta_e1edp26-qualf.
ta_e1edp26 = int_edidd-sdata.
WHEN '011'.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'e1edp26'
ta_e1edp26.
int_edidd[] = t_int_edidd[].
ENDCASE.
ENDIF.
Thanks
Manju.

Problem creating extended IDOC

Hi Experts,
I am currently working on CRM 5.0. I need to create segment and attach it to the standard basic IDOC type CRMXIF_PARTNER_SAVE01. I am able to create segment in WE31 but i am unable to add that to the basic standard IDOC type.
It is displaying message "Action is not possible for generated idoc types".
Is there any other way to add this segment to the standard IDOC.
It will be great help if u can send me some documents on this...
Thanks,
Samm

Hi,
Create Extended IDOCe using transaction WE30.
-If u want to extend idoc type which already exists then use the radio button extension(where we can add few new fields
-After this click on create button as described above. It takes you to a popup screen where you fill the description and also select the radio button accordingly and say ok
-we go to next screen select idoc type and click on create new It gives a pop up window
-Once you are done with the addition save the IDOC type and release the idoc type
Goto-> Edit -> Set release.
This completes the creation of Ext IDOC type.
- Then assign this extension to the IDoc type in WE82.
Reward with points if helpful.
Regards,
Vijay

Extended Idoc FIDCCP02 - getting status code 02

Hello Friends,
I am extending Idoc FIDCCP02 with an custom segment. I have followed this steps
Created Segment - Created Extended Idoc with Custom Segment created - Released both Segment and Idoc - Attached Idoc to FIDDC2 message type - Added message type to model view - maitained partner Profiles with extended idoc - created port type 'G' - Added necessary code in user exit (I am able to view data in my custom segment)
The Problem is - If I do not maintain Extended Idoc in partner profiles - I get Idoc XML created in external system with status code 03
But once I add extended idoc to the partner profiles - I get Status Code 02 with error saying Error in passing data to HTTP Port 500 internal Server error
Kindly can some body help me if I am missing some steps.
Thanks for help.

Dear Vasu,
I am creating Z message type, when I am creating that idoc (I have used XML Port) its initially comes in status 30 (IDoc ready for dispatch (ALE service)).
Now when I process this idoc with tcode WE19 then it give status 02 (Error passing data to port). Please suggest where i am doing mistake.
Your help will be appreciated.
Regards, Vicky M. Khambhati

Extended idoc codding

hai friends now iam doing extended idoc
in that iam extending matmas 03 idoc .
in that iam added some new segments
up to this evry thing working write .
the problem is
now i want to wrte the user exit for this extended segments
where can i write this exit
and
how to write this exit
plse help me .
with regards
srikanth vipparla

Srikanth,
You can use the exit EXIT_SAPLMV01_002 which is in MASTERIDOC_CREATE_MATMAS to populate the data for extended segments..
Hope this helps.
Chandra.

Import extended IDOC to Integration Builder

Hi All,
I´m faced with the following situation using an Idoc with customer extension from a SAP R/3 40B System with my scenario:
IDX2 - Import works fine, basistype and extension in place
Integration Builder: Can ´t see the extension with or without the idoctype but the standardidoctype only.
Thanks for any help.
regards
Carsten

Thanx very much for your reply,
the problem actually is in detail:
I try to import the IDOC-structure into the Design of Integration Builder - what did work for some other - but non-extended IDOCs earlier.
When I start the import I can ´t find the extended IDOC in the list of downloadobjects, but the (related) non-extended standard-IDOC only.
When I import the object that is listed as being non extended it actually is.
I wondered whether the IDOC-extension or the IDOC itself might not be valid so I checked Releasestatus in R/3-Systems what looks good and tried to upload the metadata with IDX2 - it worked.

How to extend idocs

hi gurus
 this is phaneendra i know how to extend the idoc
 ie we31, we30, we82,we57..........ie segment creation,
 adding it to basic idoc type and linking it
 but what exactly i want is coding for extended idoc
 in outbound and inbound ie in the customer exits what
 we have to write
can any body send me the code required for this in inbound and
in outbound dont send that present in arvind nagpal book that already i know
best regards
phaneendra punukollu
<removed_by_moderator>
Edited by: Julius Bussche on Jul 27, 2008 8:18 PM

Hi Phaneendra.
I would like to suggest a few references,
[SDN - Reference for Extending an existing IDOC|How to extend an existing IDOC!;
[SDN - Reference - Extending IDOC step by step|How to extend an IDOC step by step;
[SDN - Reference for populating segments of IDOC|How to populate IDOC segments...;
[SDN - Reference for Problem while Extending the HR IDOCS|Problem while Extending the HR IDOCS;
[SDN - Reference for Segments getting suppressed in Extended Idoc for Customer (change pointes) |Segments getting suppressed in Extended Idoc for Customer( change pointes);
[SDN - Reference for Setting attributes for segment types in IDOCS|Setting attributes for segment types in IDOCS;
Hope that's usefull.
Good Luck & Regards.
Harsh Dave

Extending Idocs.

Hi,
I am using an Idoc of message type Cond_a and basic type Cond_a04.The problem is that the segments in the idoc have a max no. of 1.I need to have a max of 30000.How can change the number?Can I do it by extending the idoc?Please explain to me.

>create customized data
>create new segment for customized data
>create Idoc as extending idoc to basic one
>got to partnerprofile in message control double click on process code .
>find out the function module
>find out exit program
>add the required logic save and activate.
>process the idoc and check the idoc.

Extending idoc

Iam having some problem in extending an idoc. I want to extend an Idoc for customer master DEBMAS01 . I successfully created the custom segment. But there is a confusion in the next steps. Iam working under 4.7 version of SAP.
"Creating an Idoc Extension" and "Connecting the exension to a basic idoc type to create an IDOC".
While creating an Extension i understand that we choose the development object as "extension". When you click on "create" , on the next screen , under "Linked basic type" i suppose i should enter "DEBMAS01 ".
1) After this step, how do i go?? I did not see any option where the system prompts for reference segment type.
2) Moreover, if somehow i create an extension idoc. To attach this idoc, do i have to create another basic idoc in the idoc editor (development object "basic type"). If so where is the option of entering the extension idoc name.
I guess everthing is simple here, but i dont know iam a little confused. Can someone pls explain in simple steps. I would be very thankful.
Regards,
Mahesh.

Hi Mahesh,
The following are the steps to extend a standard IDOC.
1) Create a new segment with the required fields using T.code WE31. Now release the segment.
2) Create the IDOC extension( staring with "Z" ) using T.code WE30 by selecting the radiobutton extension, provide the linked Basic Type eg DEBMAS01 in your case.
Now select the standard segment to which you want to add the new fields. After selecting, click on the create Button and give the name of the custom segment( That you have created with the new fields). Provide the min and max occurences.
3) You have to use this extension in the partner profile entry along with the Basic type , otherwise these fields will not be visible in the IDoc.
Regards,
Monika

Problems with extended features. I can no longer fill out my documents in the fields provided. The

Problems with extended features. I can no longer fill out my documents in the fields provided. The error message I get is "This document enabled extended features in Adobe Reader. The document has been changed since it was created and use of extended features is no longer available. Please contact the author for original version of this document."

Yes. I don't have the version you pay for. I also tried the free version
of EchoSign. Maybe that caused the problem.
Any more suggestions would be greatly appreciated.
Estelle Oliansky
Estelle OlianskyRealtor, SRESCell (734) 748-2329
*3DX Real Estate *| www.3dxonline.com* | (v) 888.304.1447 ext.
102 | (f) 888.304.1456 | 42705 Grand River Ave. Ste. 201 | Novi, MI 48375*
P Please consider the environment before printing this e-mail
This electronic mail message and any attachments contain information
that(a) is or may be LEGALLY PRIVILEGED, CONFIDENTIAL, PROPRIETARY IN
NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended
only for the use of the Addressee(s) named herein. If you are not the
intended recipient, an addressee, you are hereby notified that reading,
using, copying, or distributing any part of this message or any information
transmitted herewith is strictly prohibited. If you have received this
electronic mail message in error, please contact us immediately and take
the steps necessary to delete the message completely from your computer
system.

How to find out the inbound function module in the extended idoc

Hi,
how to find out the inbound function module in the extended idocs
Thanks .

through we41/we42 you can find the inbound function module.......
or
thorough we19(idoc test tool) ....
give the input as message type or basic idoc..
press exec...
then you can find th button on application tool bar as inbound funtion module....
from here also you can find..........
<REMOVED BY MODERATOR>
Khasimsa
Edited by: Alvaro Tejada Galindo on Apr 14, 2008 1:34 PM

Creation of New Message Type for Extended IDoc

Dear Friends,
I want to create New Message Type for MATMAS and want to Active Change Pointers accordingly. Thru this Message Type how can I able to use Extended IDoc which I have created for Basic Idoc Type MATMAS05.
I am Sending Data from SAP to XI ; Any one can help me in this How can I create the Message Type with the IDoc Extn .
for Change Pointers.
Warm Regards,
Naveen Mutyapu.

Hi naveen mutyapu,
see these links
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
http://www.allinterview.com/rss/interview-questions/new/SAP-ALE-IDocs.xml
happy learning.
thanks
karthik

PROBLEM IN CUSTOM IDOC CREATION

Hi Friends,
                I'm facing a problem in custom idoc creation plz try to assist me
1.As per the information i have i'm creating segment in we31
for cremas01 idoc.But when i enter the name for segment i'm getting message "Name range Voilation particular name which i had given is not permitted in customer system?
Plz clarify this,and are there any formalities which i should look for before creating custom idoc?
Good answers will be rewarded.
                                                                          Regards,
                                                                           Vinod.

The Problem might be.... with the naming of the segment.
Standard segments should be created with 'E1' and all the custom segments are created using 'Z1' and the name with 8 characters long only is permitted.
Reward Points if useful.

XI Problem: File to Idoc Scenario - IDOC_INBOUND_ASYNCHRONOUS

Hi,
I'm having problems with inbound IDOCS in R/3. The idocs from XI are sent as tRFC using the FM IDOC_INBOUND_ASYNCHRONOUS and this is a problem because i have like 200 or 300 idocs to be sent at the same time and each IDOC takes like 5 minutes to process, hence the system crash due the amount of simultaneous logins (error message ThISend: ThRollout ).
I need to fix this problem using some kind of serialization and the use of the function module IDOC_INBOUND_IN_QUEUE.
Does anyone know how to achieve this?.
The scenario configuration in XI and R/3 is as follows: (PI 7.0 SP15) - (R/3 SAP ECC 6.0)
File to Idoc.
Sender CC->
File content conversion
Exactly once in order
Receiver CC->
IDOC protocol
Queue Processing
R/3 Partner profile config.
Message type BOMMAT
Trigger immediately
Thanks.

Hi,
You have to split the messages in the sender file adapter, by using the parameter "Recordsets per Message".
I hope that it will solve your problem. Please see the below link, it might be useful to you.
http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Regards,
Rajesh

Problem with HRMD_A06 idoc

Dear All,
I am using the IDOC HRMD_A06 for carrying out various operation on the available HR infotypes.Kindly go thru the below mentioned details for further insight of the problem
1.Scenario:
a.An interface to SAP HR system needs to be built
b.The interface will supply incremental master-data in
form of flat-files
c.An integration broker ,SAP XI will then convert the
flat-files to I-Docs and send I-Docs to SAP HR system
d.The I-Doc chosen for this purpose is HRMD_A.HRMD_A06
e.However this I-Doc is not supporting different
operations on incremental data like modify, delete etc
f.Further validations are also not being supported
g.Also segments for certain info-type records are missing
Example for Delete Operation mode:
Operation Delete: Delete existing infotype record
Expected Result: Only the particular info-type record, as supplied in the I-Doc should be deleted and not the entire personal number with all the info-types
Actual Result: The entire personal Number is deleted.
Is it that the Idoc behaves in this fashion or there is some other flag apart from OPERATION, which needs to be set.
Regards
Vinay

Hi Vinay,
Have you found a solution ?
Because I'm a similar problem by using IDoc HRMD_A06. I have not a segment E1P0021 when I delete the infotype 0021 on an employee. I have only its segment E1PITYP.
Regards
Mickael

Problem in Extended Idoc

Similar Messages

Maybe you are looking for