Populate child segments of E1EDL24

All,
I want to populate the child segments of E1EDL24 (E1EDL41 001 and E1EDL41 002) at the time of shipment creation with some
data.
Please help.
Meghna

Hello Meghna
The User-Exit you are looking for is SAPLV56K_002.
Below you see a sample implementation where a Z-extension of the SHPORD IDoc is filled:
FUNCTION zexit_saplv56k_002_zukrrp_cond.
*"*"Local Interface:
*" IMPORTING
*"     VALUE(CONTROL_RECORD_OUT) LIKE EDIDC STRUCTURE EDIDC
*"     VALUE(MESSAGE_TYPE) LIKE EDMSG-MSGTYP
*"     VALUE(SEGMENT_NAME) LIKE EDIDD-SEGNAM
*"     REFERENCE(DATA) TYPE TR_IDOC_SHPMNT_INDATA
*"     VALUE(TAB_IDOC_REDUCTION) TYPE TR_TAB_IDOC_REDUCTION
*" TABLES
*"      IDOC_DATA STRUCTURE EDIDD
*" EXCEPTIONS
*"      ERROR_MESSAGE_RECEIVED
*"      DATA_NOT_RELEVANT_FOR_SENDING
CHECK ( segment_name = 'E1EDL24'                  AND
          control_record_out-idoctp = 'DELVRY03'    AND
          control_record_out-cimtyp = 'ZDELVRY03' ).
ls_zukrrp_cond-zuk_rrp_cond = ls_konv-kbetr.
idoc_data-segnam = lc_segnam_zukrrp. " 'ZUKRRP_COND'.
idoc_data-sdata = ls_zukrrp_cond.
APPEND idoc_data." TO INT_EDIDD.
ENDFUNCTION.
If you requested segments exist already in the IDoc then you most likely have to MODIFY the idoc_data[] itab.
Regards
Uwe

Similar Messages

FILE to IDOC using node functions; IDOC parent, child segment

I have file with 10 recors.
Each record has f1,f2 (two fields)
The target IDOC segments are
E1PARENT1 occurance 0 to 99
E1PARENT1-field_p1
E1PARENT1-E1CHILD1 occurance 0 to 5
E1PARENT1-E1CHILD1-field_c1
I have to map
FILE field1 to E1PARENT1-field_p1
and
FILE field2 to E1PARENT1-E1CHILD1-field_c1
I tried
RemoveContext -> SplitByValue(value change) -> CollapseContext ->E1PARENT1
RemoveContext -> SplitByValue(value change) -> CollapseContext ->E1PARENT1-E1CHILD1
With above i'm getting output
a) parent IDOC segment E1PARENT1 repeated 10 times (source FILE got 10 records) .. .This is correct
b) The first parent segment E1PARENT1 got 5 child segments E1CHILD1. -- this is incorrect
c) The second parent segment E1PARENT1 has NO child segments E1CHILD1 -- this is incorrect
I want
first parent segment E1PARENT1 to have 1 child segment E1CHILD1 having 1st record field2 of input FILE
2nd parent segment E1PARENT1 to have 1 child segment E1CHILD1 having 2nd record field2 of input FILE
3rd parent segment E1PARENT1 to have 1 child segment E1CHILD1 having 3rd record field2 of input FILE
I think by changing occurance (ECC value is 0 to 5) of child IDOC segment E1PARENT1-E1CHILD1 to 1 could solve this issue. (I tried to change the text file, but it is no confusing where to change using Notepad). Basically i don't know how to control the queue context of CHILD segment of IDOC matching with PARENT segment of the IDOC.
Any better alternative. Please help. Thanks

This is the IDOC target
E1PARENT1 (o to 99 occurance)
E1PARENT1-field_p1
E1PARENT1-E1CHILD1 (0 to 5 occurance)
E1PARENT1-E1CHILD1-field_c1
I resolved using standard function of message mapping. The mistake was SplitByvalue(value change), when changed to SplitByvalue(each value) got desired result. Here is the mapping to benefit others. Please correct or add if any, thanks.
a) Target - Parent segment
SOURCE-RECS->RemoveContext -> E1PARENT1
SOURCE-RECS-F1->RemoveContext -> E1PARENT1-field_p1
b) Target - Child segment
SOURCE-RECS->RemoveContext -> SplitByValue(each value) -> E1PARENT1-E1CHILD1
SOURCE-RECS-F1->RemoveContext -> SplitByValue(each value) -> E1PARENT1-E1CHILD1-field_c1

Idoc to jdbc :On the basis of field WERKS, the child segments should get re

We are working on IDOC to JDBC scenario.
In my IDOC INFREC.INFRECMASS01 has one segment E1E1NAM( parent segment), inside this parent segment we have one child segment E1E1NEM containing two lines. On the basis of one field WERKS, the child segments should get repeated in the target but in the target side we are getting only one of the values of WERKS .
We have used SPLIT BY VALUE(each value) on WERKS but still only one of the values are coming on the target side .
pl help
rgds
arun

ahi arvind ,
i sent the source /target every thing in ur rediffmail id , we tried to change the context of WERKS TO E1EINAM ,removed split by value , but got an error
Cannot produce target element /ns0:MT_IB_VENDORISL/STATEMENTNAME[2]/si_sku_vendor_link/ACCESS. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
pl suggest ...
rgds
arun

Create Individual Idocs Based on Parent and Child Segment type

Hi Experts,
I have a scenario IDOC to FILE , Split Single IDOC into Multiple IDOC's based on parent and child Segment Type
For example If 3 child segments are same and 1 segment is different under parent segment then 3 same child segments are clubbed and create single idoc under parent segments and 1 different child should create in individual idoc under parent segment.
Note : Same logic should work for N number of Parent Segments and Child Segments.
Outbound:
ZIdocName
Control Record
Data Record
Parent Segment A
   Child Segment 1
   Child Segment 1
   Child Segment 1
   Child Segment 2
Parent segment B
   Child Segment 3
Status Record
I should get output like below
Inbound:
ZIdocName
Control Record
Data Record
Parent segment A
Child Segment 1
Child Segment 1
Child Segment 1
Status Record
ZIdocName
Control Record
Data Record
Parent segment A
Child Segment 2
Status Record
ZIdocName
Control Record
Data Record
Parent Segment B
Child Segment 3
Status Record
Please suggest me step by step process to achieve this task.
Thanks.
Ram

Hello,
Segment won't hold any value, so filter criteria should be there on some field wich exist in Parent node and chile node?
Paste ur XML?
Try this(Assuming u have some fields in parent/child segment on which u want to define filter criteria):
Parent Field--UseOneAsMany----RC----
                                  ------------------Concat ----splitbyvalue(value change)--collapse context --- ZIdoc
Child field-- RC----------
Child field--RC--splitbyvalue(valuechange)--CC -Splitbyvalue(each value) -- ParentSegment
Child field--RC--splitbyvalue(valuechange)--- ChildSegment
RC -> Remove Context
CC - Collapse Context
Note - i haven't tested ur mapping, so make sure to adjust context in mapping
Thanks
Amit Srivastava
Message was edited by: Amit Srivastava

Do any standard functions populate all segments?

I have been using the ALE Send transactions for MATMAS and BOMMAT. But now I am discovering that all of the segments in the IDOC it creates are there. Is there a different mechanism (other than writing ABAP) to get more of the segments populated? I'm especially interested in the E1CUCFG that is not available in MATMAS05.
I would also like to have the BOMMAT IDOC generated for all effectivities instead of just one. Is this possible, and how?

Hi Paul,
Please check this links which will help you to know more detail on how to use user exits.
http://sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://sap-img.com/abap/what-is-user-exits.htm
http://sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
The best user exits to populate E1CUCFG segments is EXIT_SAPLMV01_002.
It depends on your business requirements. You can use change pointers to send MATMAS and BOMMAT IDocs if there are master data changes by running or schedule program RBDMIDOC.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if very helpful.

IDOC: How to create child segment with abap code.

Hi,
I'am trying to write an abap code to create segments for an Idoc which structure is the following:
ZLE_00060_DLVY
> E1EDL20
> Z1DEL_CONS
>Z1DEL_MAT_HEADER
> Z1DEL_MAT
> E1EDL20RET2
> E1EDL22
> E1EDL21
> E1EDL23
> E1EDL51
I receive a sintax error: Error in IDoc with status 26 .
Checking the result I note all segment at the same level and an error about the segment E1EDL22
EDI: Syntax error in IDoc (segment cannot be identified)
     Message no. E0078
Diagnosis
     The segment E1EDL22 does not occur at the current level of the basic
     type DELVRY05 (extension ZLE_00060_DLVY).
     This error can have several reasons:
     o   The segment E1EDL22 is assigned to a group whose header segment does
         not occur.
     o   The segment E1EDL22 does not exist in the syntax description of the
         basic type DELVRY05 (extension ZLE_00060_DLVY).
     o   The sequence of segments in the group in which the segment appears
         is incorrect.
     Previous errors ('mandatory' segment or group missing) may be due to
     this error.
Procedure
     Please check the IDoc or the syntax description of the basic type
     DELVRY05 (extension ZLE_00060_DLVY).
After the error I have:
data records
E1EDL20
Z1DEL_CONS
Z1DEL_MAT_HEADER
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
Z1DEL_MAT
E1EDL20RET2
E1EDL22
E1EDL21
Abap code:
        idoc_data-segnam = 'Z1DEL_CONS'.
        idoc_data-sdata = s_z1del_cons.
        append idoc_data.
          idoc_data-segnam = 'Z1DEL_MAT_HEADER'.
          s_z1del_mat_header-tsegment = 'MATERIAL'.
          idoc_data-sdata = s_z1del_mat_header.
          append idoc_data.
        clear idoc_data-sdata.                            <<<<<<<<<<< how to indent the structure because this is a child.
         idoc_data-sdata = s_Z1DEL_MAT.
         idoc_data-segnam = 'Z1DEL_MAT'.
         append idoc_data.
         idoc_data-segnam = 'E1EDL20RET2'.
         idoc_data-sdata = s_E1EDL20RET2.
         append idoc_data.
         clear idoc_data.
         idoc_data-segnam = 'E1EDL22'.
         idoc_data-sdata = s_e1edl22.
         append idoc_data.
         clear idoc_data.
         idoc_data-segnam = 'E1EDL21'.
         idoc_data-sdata = s_e1edl21.
         append idoc_data.
Any help will be well appreciated.
Thanks in advance.
Regards,
    Giovanni

Hi,
following in debugging mode the abap code of the INCLUDE ZXTRKU02 where is defined the TABLES IDOC_DATA STRUCTURE EDIDD, I find that all field of the table IDOC_DATA are not set. More exactly my expectation is to find values for SEGNUM, HLEVEL, PSGNUM.
In a few words I need to execute an enhancement, via abap code, of the struscure of the idoc before sending it out since I have a requirement to test this enhancement in my XI environment, receiving as input this ideoc modified.
Then, I need to add a new segment and one child.
Any suggestion will be well appreciated.
Thanks in advance.
Regards,
    Giovanni

How to populate IDOC segments...

Hello Experts,
I was just tasked to add new fields in an IDOC segment. My question is, how do I populate
those newly created fields? The data will be coming from a purchase order.
Thank you guys and take care!

Hi,
U cannot edit the existing segment u have to create a zsegment with the fields and then under the main segment u have to add this new segment..also u have create a extended idoc in ur case...then only u can add this new segment..also once u create a segment u have to release it...
u have to write the code in the userexit only...
check the sample code which i have done for my requirement for sales order..
*& Include           ZXVEDU02
Program:        Function Module:EXIT_SAPLVEDC_002     Creation Date: 12-04-2006          *
Program Type : Outbound IDOC Enhancement                                                *
Program Description:OutBound IDOC Enhancement                                            *
Modification ID:001                                                                      *
Date         : 25-05-2006                                                                *
Description : 1.The sales organization master data needs to be sent as supplier party
                 details.New segment ZZSALORG is created and attached to the parent
                 segment E1EDK01
               2.Data required to be sent are:
                  1.NAME1- Sales organization name
                  2.STRAS- Address
                  3.TELFX- Fax number
                  4.TELF1- phone number.
               3.ZZSALORG is filled with the above information.
Modification ID:002                                                                      *
Date         : 09-06-2006                                                                *
Description : A new field zstceg added to the segment zzdochdr and it was populated     *
                by selecting stceg field from Kna1 table                                 *
Modification ID:001                                                                      *
Date         : 15-06-2006                                                                *
Description : 1.New segment ZZE1EDP01 is created and attached to the parent segment E1EDP01
               2.Data required to be sent are:
                  1.POSEX- Item number
                  2.UEBTO- Overdelivery tolerance
                  3.UNTTO- Underdelivery tolerance
               3.ZZE1EDP01 is filled with the above information.
*-- Data Declaration--
*-- Constant Declaration--
CONSTANTS: c_1(1)          TYPE c VALUE '1',
           c_langu         LIKE t005t-spras VALUE 'E',
           c_parvw         LIKE vbpa-parvw VALUE 'RG',
           c_e1edk01(7)    TYPE c VALUE 'E1EDK01',
           c_e1edk02(7)    TYPE c VALUE 'E1EDK02',
           c_e1edk17(7)    TYPE c VALUE 'E1EDK17',
           c_e1edka1(7)    TYPE c VALUE 'E1EDKA1',
           c_e1edk14(7)    TYPE c VALUE 'E1EDK14',
           c_004(3)        TYPE c VALUE '004',
           c_001(3)        TYPE c VALUE '001',
           c_002(3)        TYPE c VALUE '002',
           c_re(2)         TYPE c VALUE 'RE',
           c_we(2)         TYPE c VALUE 'WE',
           c_ag(2)         TYPE c VALUE 'AG',
           c_0010(4)       TYPE c VALUE '0010',
           c_zzdochdr(8)   TYPE c VALUE 'ZZDOCHDR',
           c_ze1edk02(8)   TYPE c VALUE 'ZE1EDK02',
           c_zze1edk17(9) TYPE c VALUE 'ZZE1EDK17',
           c_zze1edka1(9) TYPE c VALUE 'ZZE1EDKA1',
           c_pe(2)         TYPE c VALUE 'PE',
           c_y(1)          TYPE c VALUE 'Y',
           c_zze1email(9) TYPE c VALUE 'ZZE1EMAIL',
           c_zzsalorg(8)   TYPE c VALUE 'ZZSALORG',
           c_zze1edp01(9) TYPE c VALUE 'ZZE1EDP01',
           c_e1edp01(7)   TYPE c VALUE 'E1EDP01'.
*-- Variables Declaration--
DATA: lv_vbeln   LIKE vbak-vbeln,
      lv_country LIKE t005t-landx,
      lv_text1   LIKE t042z-text1,
      lv_vzskz   LIKE knb1-vzskz,
      lv_inco    LIKE tinct-bezei,
      lv_cadnr   LIKE akkp-cadnr,
      lv_pernr   LIKE pa0105-pernr,
      lv_parvw   LIKE tpar-parvw,
      lv_adrnr   LIKE tvko-adrnr,
      lv_zinso   LIKE t056z-zinso,
Begin of Mod-002
      lv_stceg   TYPE stceg.
End of Mod-002
Begin of MOD-003
     lv_min_tol TYPE KWMENG,
     lv_max_tol TYPE KWMENG.
End Of MOD-003
TYPES:BEGIN OF t_vbfa,
        vbelv LIKE vbfa-vbeln,
        erdat TYPE erdat,
      END OF t_vbfa.
DATA: i_akkp TYPE akkp.
*-- WorkArea Declaration--
DATA : wa_zdochdr   TYPE zzdochdr,
       wa_ze1edk02 TYPE zze1edk02,
       wa_ze1edk17 TYPE zze1edk17,
       wa_zze1email TYPE zze1email,
       wa_zzsalorg TYPE zzsalorg,
       wa_zze1edp01 TYPE zze1edp01,
       wa_e1edk02   TYPE e1edk02,
       wa_e1edk17   TYPE e1edk17,
       wa_e1edka1   TYPE e1edka1,
       wa_e1edk01   TYPE e1edk01,
       wa_e1edp01   TYPE e1edp01,
       wa_adrc      TYPE adrc,
       wa_pa0105    TYPE pa0105,
       wa_zze1edka1 TYPE zze1edka1,
       wa_zzdochdr TYPE zzdochdr,
       wa_vbfa      TYPE t_vbfa,
       wa_vbpa      TYPE vbpa.
*-- Move data to ZZDOCHDR Segment--
CASE int_edidd-segnam.
WHEN c_e1edk01.
    MOVE int_edidd-sdata TO wa_e1edk01.
*--Begin of MOD001+(Modification ID 001)--
*-- Filling of ZZSALORG segment--
    SELECT SINGLE adrnr
    FROM tvko
    INTO lv_adrnr
   WHERE vkorg EQ dxvbak-vkorg.
    IF sy-subrc EQ 0.
      SELECT SINGLE *
               FROM adrc
               INTO wa_adrc
              WHERE addrnumber EQ lv_adrnr.
      wa_zzsalorg-salorg = dxvbak-vkorg.
      wa_zzsalorg-name1   = wa_adrc-name1.
      wa_zzsalorg-name2   = wa_adrc-name2.
      wa_zzsalorg-stras   = wa_adrc-street.
      wa_zzsalorg-telf1   = wa_adrc-tel_number.
      wa_zzsalorg-telfx   = wa_adrc-fax_number.
      wa_zzsalorg-land1   = wa_adrc-country.
      wa_zzsalorg-strs2   = wa_adrc-str_suppl1.
      wa_zzsalorg-street2 = wa_adrc-str_suppl2.
      wa_zzsalorg-street3 = wa_adrc-str_suppl3.
      wa_zzsalorg-ort01   = wa_adrc-city1.
      wa_zzsalorg-pstlz   = wa_adrc-post_code1.
      wa_zzsalorg-regio   = wa_adrc-region.
      int_edidd-segnam = c_zzsalorg.
      CLEAR int_edidd-sdata.
      MOVE wa_zzsalorg TO int_edidd-sdata.
      APPEND int_edidd.
      CLEAR: wa_adrc,
             wa_zzsalorg.
    ENDIF.
*--End of MOD001+(Modification ID 001)--
    SELECT SINGLE text1
             FROM t042z
             INTO lv_text1
             WHERE land1 EQ dxvbpa-land1
               AND zlsch EQ dxvbkd-zlsch.
    READ TABLE dxvbpa INTO wa_vbpa WITH KEY vbeln = dxvbpa-vbeln
                                      parvw = c_parvw.
    IF sy-subrc EQ 0.
Begin of Mod-002
      SELECT SINGLE stceg
      FROM kna1
      INTO lv_stceg
       WHERE kunnr = wa_vbpa-kunnr.
End of Mod-002
      SELECT SINGLE vzskz
               FROM knb1
               INTO lv_vzskz
               WHERE kunnr EQ wa_vbpa-kunnr
                 AND bukrs EQ dxvbak-bukrs_vf.
      IF sy-subrc EQ 0.
        SELECT SINGLE zinso
                 FROM t056z
                 INTO lv_zinso
                 WHERE vzskz EQ lv_vzskz
                   AND waers EQ wa_e1edk01-curcy.
        wa_zzdochdr-zdoctitle = dobject-objky.
        wa_zzdochdr-zdate      = dobject-erdat.
        wa_zzdochdr-zmestyp    = dobject-kschl.
        wa_zzdochdr-zmedium    = dobject-nacha.
        wa_zzdochdr-zlang      = dobject-spras.
        wa_zzdochdr-zttype     = dxvbkd-kdkg1.
        wa_zzdochdr-zpaymethod = dxvbkd-zlsch.
        wa_zzdochdr-zpaytext   = lv_text1.
        wa_zzdochdr-zintonpymt = lv_zinso.
Begin of Mod-002
        wa_zzdochdr-zstceg     = lv_stceg.
End of Mod-002
        int_edidd-segnam = c_zzdochdr.
        CLEAR int_edidd-sdata.
        MOVE wa_zzdochdr TO int_edidd-sdata.
        APPEND int_edidd.
        CLEAR : wa_zzdochdr.
      ENDIF.
    ENDIF.
*-- Move data to ZZE1EDK02 Segment--
WHEN c_e1edk02.
    MOVE int_edidd-sdata TO wa_e1edk02.
    IF wa_e1edk02-qualf EQ c_004.
      SELECT SINGLE vbelv FROM vbfa INTO wa_vbfa
                         WHERE vbeln EQ lv_vbeln
                         AND   vbtyp_v EQ 'B'.
      IF sy-subrc EQ 0.
        SELECT SINGLE erdat FROM vbak INTO wa_vbfa
        WHERE vbeln EQ wa_vbfa-vbelv.
        int_edidd-segnam = c_ze1edk02.
        CLEAR int_edidd-sdata.
        MOVE wa_vbfa TO int_edidd-sdata.
        APPEND int_edidd.
        CLEAR wa_vbfa.
      ENDIF.
    ENDIF.                                  " IF ended for "IF wa_e1edk02-qualf = '004'" condition.
**-- Move data to ZZE1EDK17 Segment--
WHEN c_e1edk17.
    MOVE int_edidd-sdata TO wa_e1edk17.
    IF NOT dxvbkd-lcnum IS INITIAL.
      SELECT SINGLE inco1
                    inco2
               FROM akkp
               INTO i_akkp
              WHERE lcnum EQ dxvbkd-lcnum.
      IF sy-subrc EQ 0.
        IF wa_e1edk17-qualf EQ c_001.
          wa_ze1edk17-lkond = i_akkp-inco1.
          wa_ze1edk17-qualf = wa_e1edk17-qualf.
          SELECT SINGLE bezei
                   FROM tinct
                   INTO lv_inco
                  WHERE spras EQ 'E'
                    AND inco1 EQ i_akkp-inco1.
          IF sy-subrc EQ 0.
            wa_ze1edk17-lktext = lv_inco.
          ENDIF.
        ELSEIF wa_e1edk17-qualf EQ c_002.
          wa_ze1edk17-qualf = wa_e1edk17-qualf.
          wa_ze1edk17-lktext = i_akkp-inco2.
        ELSE.
        ENDIF.
        int_edidd-segnam = c_zze1edk17.
        CLEAR int_edidd-sdata.
        MOVE wa_ze1edk17 TO int_edidd-sdata.
        APPEND int_edidd.
        CLEAR wa_ze1edk17.
      ENDIF.
    ENDIF.                                       " IF ended for not initial condition.
*--Move data to zze1edka1 Segment--
WHEN c_e1edka1.
    MOVE int_edidd-sdata TO wa_e1edka1.
*--Checking the wa_e1edka1-parvw field for 'RE'--
    IF wa_e1edka1-parvw EQ c_re.
      IF NOT dxvbkd-lcnum IS INITIAL.
        SELECT SINGLE cadnr
         FROM akkp
         INTO lv_cadnr
        WHERE lcnum EQ dxvbkd-lcnum.
        IF sy-subrc EQ 0.
          SELECT SINGLE *
                   FROM adrc
                   INTO wa_adrc
                  WHERE addrnumber EQ lv_cadnr.
          wa_zze1edka1-parvw = wa_e1edka1-parvw.
          wa_zze1edka1-partn = wa_e1edka1-partn.
          wa_zze1edka1-land1 = wa_adrc-country.
          wa_zze1edka1-name1 = wa_adrc-name1.
          wa_zze1edka1-name2 = wa_adrc-name2.
          wa_zze1edka1-stras = wa_adrc-street.
          wa_zze1edka1-strs2 = wa_adrc-str_suppl1.
          wa_zze1edka1-ort01 = wa_adrc-city1.
          wa_zze1edka1-pstlz = wa_adrc-post_code1.
          wa_zze1edka1-regio = wa_adrc-region.
          int_edidd-segnam = c_zze1edka1.
          CLEAR int_edidd-sdata.
          MOVE wa_zze1edka1 TO int_edidd-sdata.
          APPEND int_edidd.
          CLEAR: wa_adrc,
                 wa_zze1edka1.
        ENDIF.
      ENDIF.
    ENDIF.                                               " IF ended for "IF wa_e1edka1-parvw EQ 'RE'" condition.
*--Checking the wa_e1edka1-parvw field for 'WE'--
    IF wa_e1edka1-parvw EQ c_we.
      IF NOT dxvbkd-lcnum IS INITIAL.
        SELECT SINGLE cadnr
          FROM akkp
          INTO lv_cadnr
         WHERE lcnum EQ dxvbkd-lcnum.
        IF sy-subrc EQ 0.
          SELECT SINGLE *
                   FROM adrc
                   INTO wa_adrc
                  WHERE addrnumber EQ lv_cadnr.
          wa_zze1edka1-parvw = wa_e1edka1-parvw.
          wa_zze1edka1-partn = wa_e1edka1-partn.
          wa_zze1edka1-land1 = wa_adrc-country.
          wa_zze1edka1-name1 = wa_adrc-name1.
          wa_zze1edka1-name2 = wa_adrc-name2.
          wa_zze1edka1-stras = wa_adrc-street.
          wa_zze1edka1-strs2 = wa_adrc-str_suppl1.
          wa_zze1edka1-ort01 = wa_adrc-city1.
          wa_zze1edka1-pstlz = wa_adrc-post_code1.
          wa_zze1edka1-regio = wa_adrc-region.
          int_edidd-segnam = c_zze1edka1.
          CLEAR int_edidd-sdata.
          MOVE wa_zze1edka1 TO int_edidd-sdata.
          APPEND int_edidd.
          CLEAR: wa_adrc,
                 wa_zze1edka1.
        ENDIF.
      ENDIF.
    ENDIF.                                             " IF ended for "IF wa_e1edka1-parvw EQ 'WE'" condition.
*--Checking the wa_e1edka1-parvw field for 'AG'--
    IF wa_e1edka1-parvw EQ c_ag.
      IF NOT dxvbkd-lcnum IS INITIAL.
        SELECT SINGLE cadnr
          FROM akkp
          INTO lv_cadnr
         WHERE lcnum EQ dxvbkd-lcnum.
        IF sy-subrc EQ 0.
          SELECT SINGLE *
                   FROM adrc
                   INTO wa_adrc
                  WHERE addrnumber EQ lv_cadnr.
          wa_zze1edka1-parvw = wa_e1edka1-parvw.
          wa_zze1edka1-partn = wa_e1edka1-partn.
          wa_zze1edka1-land1 = wa_adrc-country.
          wa_zze1edka1-name1 = wa_adrc-name1.
          wa_zze1edka1-name2 = wa_adrc-name2.
          wa_zze1edka1-stras = wa_adrc-street.
          wa_zze1edka1-strs2 = wa_adrc-str_suppl1.
          wa_zze1edka1-ort01 = wa_adrc-city1.
          wa_zze1edka1-pstlz = wa_adrc-post_code1.
          wa_zze1edka1-regio = wa_adrc-region.
          int_edidd-segnam = c_zze1edka1.
          CLEAR int_edidd-sdata.
          MOVE wa_zze1edka1 TO int_edidd-sdata.
          APPEND int_edidd.
          CLEAR: wa_adrc,
                 wa_zze1edka1.
        ENDIF.
      ENDIF.                                       " IF ended for "IF NOT dxvbkd-lcnum IS INITIAL" condition.
    ENDIF.                                         " IF ended for "IF wa_e1edka1-parvw EQ c_ag" condition.
*--Checking the wa_e1edka1-parvw field for 'Y'--
    IF wa_e1edka1-parvw+0(1) EQ c_y.
      SELECT SINGLE parvw
              FROM tpar
              INTO lv_parvw
              WHERE parvw EQ wa_e1edka1-parvw
                AND nrart EQ c_pe.
      IF sy-subrc EQ 0.
        SELECT SINGLE pernr
          FROM vbpa
          INTO lv_pernr
          WHERE vbeln EQ dxvbpa-vbeln
          AND   parvw EQ lv_parvw.
        IF sy-subrc EQ 0.
          SELECT SINGLE usrid_long
           FROM pa0105
           INTO wa_pa0105-usrid_long
           WHERE pernr EQ lv_pernr
             AND usrty EQ c_0010.    " communication type email
          wa_zze1email-zparvw = wa_e1edka1-parvw.
          wa_zze1email-zname   = wa_e1edka1-name1.
          wa_zze1email-zemail = wa_pa0105-usrid_long.
          int_edidd-segnam = c_zze1email.
          CLEAR int_edidd-sdata.
          MOVE wa_zze1email TO int_edidd-sdata.
          APPEND int_edidd.
          CLEAR: wa_adrc,
                 wa_zze1email,
                 wa_pa0105.
        ENDIF.
      ENDIF.
    ENDIF.                              " IF ended for "IF wa_e1edka1-parvw EQ 'Y'" condition.
*--Begin of MOD003 (Modification ID 003)--
*-- Move data to ZZE1EDP01 Segment--
WHEN c_e1edp01.
    MOVE int_edidd-sdata TO wa_e1edp01.
    wa_zze1edp01-posex = wa_e1edp01-posex.
     wa_zze1edp01-uebto = dxvbap-kwmeng + ( dxvbap-kwmeng * dxvbap-uebto / 100 ).
     wa_zze1edp01-untto = dxvbap-kwmeng - ( dxvbap-kwmeng * dxvbap-untto / 100 ).
    wa_zze1edp01-uebto = dxvbap-uebto.
    wa_zze1edp01-untto = dxvbap-untto.
    int_edidd-segnam = c_zze1edp01.
    CLEAR int_edidd-sdata.
    MOVE wa_zze1edp01 TO int_edidd-sdata.
    APPEND int_edidd.
    CLEAR: wa_zze1edp01.
*--End of MOD003 (Modification ID 003)--
WHEN OTHERS.
ENDCASE.
Regards,
Nagaraj

Pre-populate Child Forms

Hi Gurus,
Does anyone knows how can I prepopulate child forms?
I need to associated the provisioned user to some AD groups, depending on his attributes (Position, Department,etc). I'm able to create an adapter with the logic to add the user to related group, but don't know how to add this group in the child form.
When I attach my prepopulate adapter in the child form, the Group field is populate properly, but how can I simulate a click on "Add" button to add this group, which starts the process task "Add User To Group"?
Additionally, I must not use the access policies to do this feature (just because some customer's business rules).
Any idea will be helpful.
Thanks

Hi Alex,
1. Implement the Java class to put your logic using addProcessFormChildData under tcFormInstanceOperationsIntf.
2. Create the process task adapter using this java class.
3. Create an unconditional process task (i am assuming you required it only once), set Allow multiple instances to false and integrate the adapter create in step 2.
4. Under the task dependency tab put 'Create User' as preceding tasks.

In exit EXIT_SAPLKD01_001 populate custom segment of idoc ext. cremas05

Hi,
I am using EXIT_SAPLKD01_001 where I need to populate 2 custom segments for idoc extension cremas05.
I have created a function module separately where I have populated the 2 structures that is of same type as the segment structure.
In the exit I have called the function module where the structures are populated.
Now my question is how to populate the custom segments from the function module structures directly in the exit.
Thanks and Regards
P

Hi
Now I'm able to do this.... closing the thread.

Fill / populate customer segments in extension of ARTMAS05

hi,
currently looking for a solution to this.
1) I need to add customer segments to an extended version of ARTMAS05.
Name to clear yet. But it will e a cimtype of ARTMAS05.
2) system is a retail system.
- SAP ECC 6.0
- SAP_APPL 6000 / level 9
I have looked for enhancement spots and user exits. The only thing close to it is enhancement project MGV00003. There I got a component( EXIT_SAPLMV01_003) to populate the EXT segments / containers. But I cannot fill / populute own segments there.
I want to sent the data using tcode BD10 (report RBDSEMAT). No exits found in there I could need.
Anybody done something like this? Knows the right enhancment section or spot? Or did you just modify the thing which I would really want to avoid. If possible.
Thanks for an anwer.
Rob

Hello Freinds,
Can Some body help me. I am facing the same problem as in this post. I have extended Orders05 Idoc and followed below steps.
Created Segment - Created Extended Idoc with Custom Segment created - Released both Segment and Idoc - Attached Idoc to ORDERS message type - Added message type to model view - maitained partner Profiles with extended idoc u2013 I have written my custom code in User Exit u2018EXIT_SAPLEINM_002u2019 - activated my project.
The problem I am facing is u2013 When I keep a breakpoint at the user exit u2013 it never stops u2013 it just creates an basic idoc. I have tried keeping breakpoint at all the places where I can think but no where it is stopping.
Thanks for the help.

To add field in the segment of an IDOC

Hi,
Is there any impact on other IDOC types, if a field is added in the segment of an basic IDOC type.

Hi,
You can add the field VGBEL in the custom segment ZE1EDL24 and add this segment as a child segment to E1EDL24 and save it as an extension for the basic idoc type.
You can populate the VGBEL field using custom code in the function exit.
This would solve your problem.
Please let me know if you have any further queries.
Thanks,
Mahesh,

Create IDOC Based on an Event Being Triggered

I have a BOR object that when changed - triggers event 'Change'
I would like to code the event linkage such that an IDoc is created everytime the event is raised.
Has anyone done this before?
The message type I am using is a standard one and is associated with the same BOR object.
Which function module should I use in the event linkage for that 'change' event?
The IDoc doesnt have an outbound function module.
Please indicate steps or point me to related weblogs/threads
Thanks

hi!!!!!!!!!!!!!!
this is the sample code which may help u,
*BAsic type ZMARA
*Extension ZMARA
*Message type ZMatmas
REPORT zi_material_idoc
        NO STANDARD PAGE HEADING
        MESSAGE-ID b1.
TABLES: z1maram, z1mara_desc, z1marcm.
                    TYPE DECLARATION
TYPES: BEGIN OF ty_data,
        matnr TYPE matnr,
        ernam TYPE ernam,
        ersda TYPE ersda,
        mtart TYPE mtart,
        mbrsh TYPE mbrsh,
        spras TYPE spras,
        maktx TYPE maktx,
        werks TYPE werks_d,
        lgort TYPE lgort_d,
       END OF ty_data.
DATA: w_data TYPE ty_data,
      w_edidd TYPE edidd,
      i_edidd TYPE STANDARD TABLE OF edidd,
      w_edidc TYPE edidc,
      i_edidc TYPE STANDARD TABLE OF edidc.
                     SELECTION SCREEN                               *
PARAMETERS: p_matnr TYPE matnr.
                   AT SELECTION SCREEN
*Validate Material
AT SELECTION-SCREEN ON p_matnr.
PERFORM check_matnr.
                   START-OF-SELECTION
*Start of selection
START-OF-SELECTION.
PERFORM get_data_from_selection.
                    END-OF-SELECTION
*End of selection
END-OF-SELECTION.
IF NOT i_edidd IS INITIAL.
    PERFORM generate_idoc.
ENDIF.
*&      Form check_matnr
      text
FORM check_matnr .
DATA l_matnr TYPE matnr.
IF NOT p_matnr IS INITIAL.
    SELECT SINGLE matnr FROM mara INTO l_matnr
                        WHERE matnr = p_matnr.
    IF sy-subrc NE 0 OR l_matnr IS INITIAL.
      MESSAGE e000 WITH text-004.
    ENDIF.
ENDIF.
ENDFORM.                    " check_matnr
*&      Form get_data_from_selection
      text
FORM get_data_from_selection .
SELECT SINGLE a~matnr
                a~ernam
                a~ersda
                a~mtart
                a~mbrsh
                b~spras
                b~maktx
                c~werks
                c~lgort
                INTO w_data
                FROM mara AS a
                INNER JOIN makt AS b
                ON amatnr = bmatnr
                INNER JOIN mard AS c
                ON amatnr = cmatnr
                WHERE a~matnr = p_matnr AND
                      b~spras = 'EN'.
IF sy-subrc = 0.
    MOVE: w_data-matnr TO z1maram-matnr,
          w_data-ernam TO z1maram-ernam,
          w_data-ersda TO z1maram-ersda,
          w_data-mtart TO z1maram-mtart,
          w_data-mbrsh TO z1maram-mbrsh,
          w_data-spras TO z1mara_desc-spras,
          w_data-maktx TO z1mara_desc-maktx,
          w_data-werks TO z1marcm-werks,
          w_data-lgort TO z1marcm-lgort.
Populate Parent Segment
    w_edidd-segnam = 'Z1MARAM'.
    w_edidd-sdata = z1maram.
    APPEND w_edidd TO i_edidd.
    CLEAR w_edidd.
Populate Extn Segment
    w_edidd-segnam = 'Z1MARCM'.
    w_edidd-sdata = z1marcm.
    APPEND w_edidd TO i_edidd.
    CLEAR w_edidd.
Populate Child Segment
    w_edidd-segnam = 'Z1MARA_DESC'.
    w_edidd-sdata = z1mara_desc.
    APPEND w_edidd TO i_edidd.
    CLEAR w_edidd.
ENDIF.
ENDFORM.                    " get_data_from_selection
*&      Form generate_idoc
      text
FORM generate_idoc .
Populate Control Record
w_edidc-direct = '1'.
w_edidc-rcvpor = 'A000000021'.
w_edidc-rcvprt = 'LS'.
w_edidc-rcvprn = 'ZMATMAS'.
w_edidc-sndprt = 'LS'.
w_edidc-sndprn = 'LOG950R3'.
w_edidc-mestyp = 'ZMATMAS'.
w_edidc-idoctp = 'ZMARA'.
w_edidc-cimtyp = 'ZMARA'.
Data Distribution
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      master_idoc_control            = w_edidc
    TABLES
      communication_idoc_control     = i_edidc
      master_idoc_data               = i_edidd
    EXCEPTIONS
      error_in_idoc_control          = 1
      error_writing_idoc_status      = 2
      error_in_idoc_data             = 3
      sending_logical_system_unknown = 4
      OTHERS                         = 5.
IF sy-subrc = 0.
    CLEAR w_edidc.
    READ TABLE i_edidc INTO w_edidc INDEX 1.
    IF sy-subrc = 0.
      WRITE:/ w_edidc-docnum.
    ENDIF.
ENDIF.
ENDFORM.                    " generate_idoc
this link may help u,
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6702507d11d18ee90000e8366fc2/content.htm
reward if useful.

Find the enhancement in DELVRY03

I created an extended IDOC for standard DELVRY03 and added a new child segment to E1EDL24 to pop up new fields. This IDOC will be created when VL01/2N its used.
My question is: What is the user-exit that I need to pop up new child segment?
Your help will be rewarded.
Thanks

Hello Vivek
The function module for outbound processing is IDOC_OUTPUT_DELVRY. Within its coding you will find all the user-exits. In addition, check the package VTRK to which this function module (function group) is assigned.
There you will find the exit function groups: XTRK & XV56KBAPI
Regards,
Uwe

Adding field in standard IDOC Segment E1EDL24

Hello Friends,
I have an urgent requirement that I have to extend IDOC segment E1EDL24 with two fields PABNR and LFSNR.
When I tries to change the segment in WE31, it shows an error message that you can only modify the segments of customer namespace and cannot modify Standard IDOC Segments.
Can we modify the standard IDOC segments, and if yes, how can we modify the standard IDOC segments. Please clarify.
Points will be rewarded generously.
Regards,
Navin

Hi Naveen,
We cannot Modify the Standard segments. But we have to Create a new Segment and Add these fields.
Then Create an Extended Idoc type
Implement User Exits in Outbound And Inbound ..
This is the Complete Steps and Info on this...with an Example...
Enhancing ALE
For example, if in an outbound interface you find that the IDOC type does not contain all the data you need to pass to the other system, you can extend the IDOC to accommodate the additional fields and enhance the ALE function modules to populate the fields. Similarly, if in an inbound interface, there is additional data that needs to be posted to the R/3 application, you can extend the IDOC type to have additional fields populated by the external system or translator or the other R/3 system and then enhance the inbound ALE function modules to post the additional data to the R/3 application.
let us use the SAP Customer Master application as an example. Specifically, letâs focus on the IDOC extension and ALE function module enhancement of IDOC type DEBMAS02 and message type DEBMAS (Customer Master) and the IDOC reduction of message type MATMAS.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Error handling is a very important consideration when making enhancements to inbound ALE/EDI objects. In ALE and EDI inbound processing, workflow is used for handling errors at different levels such as technical and application. If workflow has been configured for the interface, the error messages and workflow items flow to the inbox of the named recipient(s).
It is also critical to enhance the workflow that handles notifications of the inbound ALE/EDI process. In most scenarios this is not a very difficult task because SAP lets you influence the workflow parameters and messages in function exits (customer functions). You typically do this using flags and message codes to trigger certain workflow actions. If you conform to the status codes and flags stipulated for workflow processing, the enhancement could be error-free and seamless. In the case of an inbound IDOC with an extension, you should populate the EDIDC fields IDOCTYP (new IDOC type) and CIMTYP (extension type) accordingly.
Reward if Helpful

Custom IDoc Type missing segment parent/child relationships

Hi.
I copied the standard ORDERS05 IDoc type to a custom type and cut out quite a few segments. My new IDoc type is setup with parent/child segment relationships, similar to many of the original relationships in ORDERS05.
When I use the standard FM IDOC_OUTPUT_ORDRSP to generate an IDoc, it's not creating with parent/child segment relationships. It's placing the children at the same level as the parent.
Anyone know what I'm doing wrong?
Thanks!
Cal

figured out the problem. was missing a required segment used to establish the parent/child relationship.

Populate child segments of E1EDL24

Similar Messages

Maybe you are looking for