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.

Similar Messages

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.

Problem in filling Custom segment data using User Exit for ZORDERS05

Hi,
I am using Process Code SD10 to generate the custom Idoc ZORDERS05.
The function module used is IDOC_OUTPUT_ORDRSP.
I am able to succesfully generate the Custom Idoc (VA02->Extras->Header->Edit) but unable to populate the custom segments in the IDOC.
I have tried to write the code in User Exit EXIT_SAPLVEDC_003 -> ZXVEDU15. But still I'm unable to populate the Z segments.
Even though I place a break point in the FM or in the User Exit during the generation of Idoc the control doesn't stop in FM nor in the User Exit.
I am unable to understand how to go about this.
Can anybody please help me with this?
Thanks in Adavance,
Rohan.

Okay I under what you are speaking about NACE.
Yes that configuration has been done and I am sucessfully able to generate the IDOC.
But even though I know that in FM IDOC_OUTPUT_ORDRSP, I have to write code in User Exit EXIT_SAPLVEDC_003 to populate the Z segments; I'm unable to understand y the control doesn't pick the FM and Exit.
Right now I have code in the Exit to fill Z segments.
Thanks
Rohan.

Custom segments to basic IDOC type without extension

Hi,
Is it possible that an IDOC has custom segments which are getting populated and the basic type does not have any custom segments.
How should we find from where the custom segments are getting populated and displayed?
Regards,
Subhashini

Hello,
Lets say in DELVRY05 Idoc Type, we have a Segment Called E1EDL20 and since this is a Standard SAP Provided Basic Type, it will not have any Custom Segments ( Z-Segments). Now, If I want some additional Information to be populated as part of a Custom Segment, what I would do is to Create an IDoc Extension ZDELVRY05 with reference to the Basic Type DELVRY05 and Create a Custom Segment Z1EDL20 (Per Say) in which I'll populate the Custom Data Fields using an Exit. So, unless we create an IDoc Extension for a Basic Type, the Standard SAP Basic Type will not have any Custom Segments-Fields (Z-Segments).
Thanks,
Venkata Phani Prasad K

Populating the custom segments for the Basic type attached to HRMD_A (IDOC)

Hi,
I've enhanced a few infotypes and want the new fields to be available in an IDOC created through the program RHALEINI.
Here are the steps I followed.
Step 1 :(we31)
We created new segment Z1IT023 , containing all the fields from infotype 0023 along with the custom fields added.
Step 2 :(we30)
We created an extension of IDOC type HRMD_A07 by name HRMD_EX to include this segement.
Step 3 :
We added an entry in table EDIMSG against message type HRMD_A , with base type : HRMD_A07 , extension : HRMD_EX , version : 700
Step4 :(we20)
Now , we made changes to partner profile by adding entry for message type HRMD_A with base IDOC type as HRMD_A07 and extension as HRMD_EX
Step5:
We changed the entry in table T777D and specified the IDOC segment as Z1IT023.
Step6.
We then tried to execute the report RHALEINI to generate the IDOC. The IDOC got created, but it didn't have the data for the segment Z1IT023.
In fact, there is a different solution to this... by adding the custom segment(containing nly the new infotype fields) as a child of the original segment E1P0023 and then writting code in the user-exit to populate the segment, but our intension is to have a single segment with all the infotype 0023 data. Besides, I believe in HR, making an entry in T777D should free us from writing any code for populating the IDOC segments.
Can anybody please suggest me, where am I going wrong. How can the new segments be populated automatically.
Thanks in advance.
Sujit.
Responses will be suitably rewarded.

Hi,
Did u get any exit to populate the custom segment?
Thanks,
San

How to populate custom fields in SAP standard Basic type DELFOR01(E1EDK09)

I've a requirement to include and populate 2 custom fields in SAP standard basic type DELFOR01 and Segment E1EDK09 (it is at hierarchy level 1 ) .
The requirement looks very simple but for this, as per my knowledge, I have to create a new Basic type with the copy of segment E1EDK09 and attach it to outbound process code and write my own function module to populate the segments.
It seems ok but the there are some existing codes in the user-exits for the SAP standard function module.These codes will not get triggered.(Or I've copy the user-exits code in my FM)
Can we do it any other way to handle this kind of situation?
Thanks in advance for your suggestions and help.

Hi Phani,
You have done it correctly. ECC additional data to be moved to EWM, 1. you need to enhance the CIF for master data/ bapi to populate the data in the custom field in EWM. 2. Make your your are not enhancing only one structure. You need to do it in the CI includes so that the field is available in all the related tables/structures.
3. The BAPI/FM which updated these tables will take care automatically to update the custom field data if the field is correctly added in all the tables.
4. If the custom fields are added correctly and still the data is not getting saved , then need to check the mapping of the custom field and bepi extension.
Let me know if this helps.

IDoc - Custom segments added?

Hi,
I am new to IDOC and working on Sales Order BOM inbound interface. Using BOMORD01 Idoc and filling E1STZUM, E1KDSTM and E1STPON segments. Getting a message saying "Segment cannot be identified" (ZE1FIKP) and also "Custom segments added" but actually my intention is not to add any custom segments, why I am getting this message and how to correct it.
Thanks in advance.
Regards,
Balaji Viswanath.

Hi,
Just For your understanding...
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDoc
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
create IDOC Type
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
for futher info check the below links
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
<b>if u find it useful plz mark the points</b>

Custom Data Processing Extension and Parameters

Hello,
I have successfully implemented a custom data processing extension. Now I'm trying to add parameters, but the documentation is very weak on this topic. Also all examples of custam data processing extensions I have found so far are working without parameter support. Using a search engine I have found a custom data processing extension's sequence diagram during report execution. The related article also gives some hints about the IDbCommandAnalysis interface.
The GetParameters implementation creates a parameter collection based on the current command text and returns this collection. So far no problem.
My question is how to implement the IDbCommand's CreateParameter method and Parameters property? In CreateParameter I just return a new instance of my IDataParameter implementation, and the Parameters property returns a new parameter collection based on the current command text.
Is this ok so? At least this is the first implementation which seems to work in the data designer. If I share an instance variable for GetParameters and Parameters I will either get all parameters twice or BIDS will crash when pressing the execute button in the dataset designer - depending on my actual implementation.
What I'm still missing is how to get the parameters added automaticall to the dataset's properties parameter register?
thanx in advance and kind regards, Gerald

I think that finally (after some days of trying) I could make it work. The dataset and report parameters are reflecting the command text's parameters now (BTW: to answer my last question - the dataset's properties are updated after pressing the refresh button only). The road to success was not to use the same member variable for the collections returned by IDbCommandAnalysis:GetParameters() and IDbCommand:Parameter and not to fill the latter one with the command text's parameters (see partial source code below).
public sealed class MyCommand : IDbCommand, IDbCommandAnalysis
    private string m_commandText;
    private MyParameterCollection m_parameters = new MyParameterCollection();
    public string CommandText
        get { return this.m_commandText; }
        set { SetCommandText(value); }
    public IDataParameterCollection Parameters
        get { return m_parameters; }
    public IDataParameter CreateParameter()
        return new MyParameter();
    public IDataParameterCollection GetParameters()
        return GetParameterCollection();
    private void SetCommandText(string commandText)
        m_commandText = commandText;
    private MyParameterCollection GetParameterCollection()
        // ... create parameter collection based on m_commandText
Still there are some open questions:
How can I update the report parameter's properties? Now the parameter's data type is always string, but I'd like to assign the right data type. I'd also like to tag the parameters as hidden and supply a non-queried default value. Is this possible? How?
Although I my implementation of IDbCommandAnalysis:GetParameters() returns a collection containing the parameter names and values the "prompt query parameters" dialog (after pressing the query designer's execute button in the toolbar) shows a "<blank>" value for the parameters. What could be the problem?
Thanx in advance and regards,
Gerald

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

Material Master Upload though LSMW - How to add new custom segments to LSMW

Hi,
I have an existing LSMW to create material master idocs (ZMATMAS) from legacy file. Now I need to add new custom segment under E1MARCM, for example say ZMARC1 which will have 2 new custom fields.
1. I created the segment through WE31 and released it.
2. I created an extension to ZMATMAS using WE30 and released it.
Now Im trying to change the LSMW so that I will have the new segment ZMARC1 under E1MARCM so that I can do the field mappings. But I am not able to get it done. i.e. I dont know what should I do so that I can get the new segment in LSMW.
I tried giving the extension in the first step of LSMW. i.e. Maintain Object Attributes but its not allowing me to give an extension. Do I need to add to the basic type ZMATMAS05 and release it to get it reflected in LSMW.
Please give your suggestions.
Thanks a lot in advance.

Hi
U can not add u r 'Z' program in Maintian attributes of LSMW.
But U can create the BAPI and assign Business object, Then u can use u r Business Object in Lsmw.
Regards,
Raghu.

Custom segments to HRMD_A

Hi,
I am using the HRMD_A message type and it does not contain certain infotypes part of its schema for ex infotype 77, so we extended the IDOC HRMD_A07 and added few fields from infotype 77. Using SCDO tcode we created a custom change document for table PA0077 and using tcode BD52 we included the fields from the table PA0077 which were added to the extended segment. In the user exit which gets triggered when infotype 77 is udpdated we are writing it to the change documents now my question is how will the custom segment ZP0077 get updated when there is a change in the infotype 77 data. Do we have to write a custom code to populate the custom segments , if we need to then how can we retreive the latest data, populate the custom segments and in which user exit does it have to go. We have written some logic to popuate some other custom segments in the following user exits, do we have to use one of them.
EXIT_SAPLRHA0_001
EXIT_SAPLRHA0_002
EXIT_SAPLRHA0_003
EXIT_SAPLRHA0_004
EXIT_SAPLRHA0_005
EXIT_SAPLRHA0_006
EXIT_SAPLRHAL_001
EXIT_SAPLRHAL_002
EXIT_SAPLRHAL_003
EXIT_SAPLRHAL_004
All inputs will be appreciated and rewarded suitably.
Thanks
Vick
FYI: This is a duplicate thread, I will make sure that i delete the other thread

Hi,
With change documents an event might be triggered check tcode
swels and switch on event trace
now change the infotype (assuming you have attached/activated change documents)
go to tcode swel and execute to see if any event is triggered.
now you can call the workflow and in the workflow in the business object put the code necessary for fetching the data and call pfal or other tcodes u using to export data.
Regards,
Divya

ZHRMD_A Custome message type issue with custom segments.

Hi Experts,
We have implemented ALE in HR system, we have all other ALE using HRMD_A and we have jobs scheduled for HRMD_A message type. We dont want this job should trigger our model and distribute the data. So we have reduced the HRMD_A messae type to ZHRMD_A for basic type HRMD_A06. Every thing fine. After upgrade of SAP FROM ECC6.O to EHP4, PFAL is not creating IDOC segements for custom segments Z*. for example Z1P0002....ETC, though there is personal data for PERNR.
Please guid if you have come across such situation and solution.
Thanks & Regards.
Venkat.

Hi Venkat,
In the same way i too have one situation like...have different model view with same message types( and same extension type) for various countries from one sender system.
Should i create reduced message type for each model view?
Or can i use same message type HRMD_A for various model views?
If i can use same message type and same extension type for various model views is there any restriction we need to write in USER EXIT EXIT_SAPLRHA0_004?
Regards,
Lava.

How to enhance DEBMDM06 to add custom segments and do mass message transf

Hi Team,
I have a requirement to transfer multiple IDocs(Customers) as a single IDoc to PI (Earlier XI) system. As I know this could be done by doing necessary config in ALE and execute the transaction MDM_CLNT_EXTR(MDMC specific to customer master day) by creating a variant with proper Extraction Object details. This works perfect with only standard idoc type DEBMDM05/06.
1. I have extended the IDoc type DEBMDM06 to ZEUDEBMDM06
2. Created a new message type ZDEBMDM (using WE81)
3. Assigned the message type to IDoc type(using WE82).
4. Created a new extraction object ZCUSTOMER_EXTRCT from CUSTOMER_EXTRACT by executing
program 'MDM_METADATA_MAINTAIN'.
5. Maintained the view 'VMDMMETA' using SM30 to add custom segments and altered the positions according to new IDoc type.
6. Found a user exit to fill custom segments.
7. Executed the transaction MDMC, in the debug managed the hord coded extraction object from 'CUSTOMER_EXTRACT'
to 'ZCUSTOMER_EXTRCT'.
This has generated a single IDOC for 2 customers but ulike one segment for one customer, it has addes somany segments at same level.
Can we enhance the mass message transfer concept so that we can use it for extended IDOC type so that I can have custom segment types added ?
Thanks in advance...
Arun
Edited by: Arunkumar Ponnoju on Sep 8, 2009 11:31 AM

hi Caíque ;
Firstly thanks for your answer.But your badi is at CRM side, I want to fill BDOC with custom fields from ECC to CRM when I changed them in IE02 of ECC.
Do you know there is any badi after BDOC is filled in ECC.
Regards.

SAP ER Connector 9.1.2.2 IDOC Data Parser Error to read custom segments

Hi,
We are in the trouble to find out the root cause of the issue in SAP Employee Reconciliation Connector 9.1.2.2 for processing idoc. As per our requirment, we need to retreive the field values in the custom segments(ZHR) other than the base segments(E2P). As we tried a lot for the couple of days and identified the custom segment filednames are not parsing by SAP HRMS Listener (in tRFC mode of communication).. The same idoc file works properly to retreive the value in the reconciliation event at "SAP User Reconciliation" (in file port). Its strange why it is not reading the idoc through listener. Will there be any db refresh or any configuration on SAP system required to do in tRFC mode of idoc file transfer?
OIM Log :-
INFO,11 Apr 2013 12:16:53,513,[OIMCP.SAPH:info],oracle.iam.connectors.sap.common.parser.HRMDAParser : parse() : process_IDOC ROOT:General root segment
DEBUG,11 Apr 2013 12:16:53,514,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: STARTED
DEBUG,11 Apr 2013 12:16:53,515,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue() : returned value is: 12507708
DEBUG,11 Apr 2013 12:16:53,516,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: FINISHED
DEBUG,11 Apr 2013 12:16:53,516,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isValidRecord():: FINISHED
DEBUG,11 Apr 2013 12:16:53,517,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isValidRecord():: FINISHED
DEBUG,11 Apr 2013 12:16:53,518,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isValidRecord() : return value is TRUE
DEBUG,11 Apr 2013 12:16:53,518,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isDeletedUser():: STARTED
DEBUG,11 Apr 2013 12:16:53,519,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isDeletedUser():: FINISHED
DEBUG,11 Apr 2013 12:16:53,520,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
DEBUG,11 Apr 2013 12:16:53,520,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
DEBUG,11 Apr 2013 12:16:53,521,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : Personnel Number set to 12507708
DEBUG,11 Apr 2013 12:16:53,522,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: FINISHED
DEBUG,11 Apr 2013 12:16:53,522,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
DEBUG,11 Apr 2013 12:16:53,523,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
DEBUG,11 Apr 2013 12:16:53,524,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: FINISHED
DEBUG,11 Apr 2013 12:16:53,524,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
DEBUG,11 Apr 2013 12:16:53,525,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: STARTED
DEBUG,11 Apr 2013 12:16:53,526,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue() : returned value is: Sat May 25 00:00:00 PDT 1985
DEBUG,11 Apr 2013 12:16:53,527,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: FINISHED
DEBUG,11 Apr 2013 12:16:53,529,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
DEBUG,11 Apr 2013 12:16:53,529,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : First Name set to SRI
DEBUG,11 Apr 2013 12:16:53,530,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : Middle Name set to RAM
DEBUG,11 Apr 2013 12:16:53,531,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : Last Name set to RAM
DEBUG,11 Apr 2013 12:16:53,531,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: FINISHED
DEBUG,11 Apr 2013 12:16:53,532,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
DEBUG,11 Apr 2013 12:16:53,533,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: STARTED
INFO,11 Apr 2013 12:16:53,534,[OIMCP.SAPH:info],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue() : (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "BEGDA" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=BEGDA
DEBUG,11 Apr 2013 12:16:53,534,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
ERROR,11 Apr 2013 12:16:53,535,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,536,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
ERROR,11 Apr 2013 12:16:53,537,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,538,[OIMCP.SAPH:error],================= Start Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,539,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord()
ERROR,11 Apr 2013 12:16:53,539,[OIMCP.SAPH:error],(5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
ERROR,11 Apr 2013 12:16:53,540,[OIMCP.SAPH:error],Description : (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
ERROR,11 Apr 2013 12:16:53,541,[OIMCP.SAPH:error],com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
at java.lang.Thread.run(Thread.java:662)
ERROR,11 Apr 2013 12:16:53,542,[OIMCP.SAPH:error],================= End Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,542,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,543,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :
ERROR,11 Apr 2013 12:16:53,544,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,545,[OIMCP.SAPH:error],================= Start Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,546,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment()
ERROR,11 Apr 2013 12:16:53,546,[OIMCP.SAPH:error],
ERROR,11 Apr 2013 12:16:53,547,[OIMCP.SAPH:error],Description :
ERROR,11 Apr 2013 12:16:53,547,[OIMCP.SAPH:error],oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
... 18 more
ERROR,11 Apr 2013 12:16:53,548,[OIMCP.SAPH:error],================= End Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,549,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,550,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :
ERROR,11 Apr 2013 12:16:53,550,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,552,[OIMCP.SAPH:error],================= Start Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,552,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment()
ERROR,11 Apr 2013 12:16:53,553,[OIMCP.SAPH:error],
ERROR,11 Apr 2013 12:16:53,554,[OIMCP.SAPH:error],Description :
ERROR,11 Apr 2013 12:16:53,554,[OIMCP.SAPH:error],oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
... 17 more
Caused by: com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
... 18 more
ERROR,11 Apr 2013 12:16:53,555,[OIMCP.SAPH:error],================= End Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,556,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,556,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :
ERROR,11 Apr 2013 12:16:53,557,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,558,[OIMCP.SAPH:error],================= Start Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,559,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment()
ERROR,11 Apr 2013 12:16:53,559,[OIMCP.SAPH:error],
ERROR,11 Apr 2013 12:16:53,560,[OIMCP.SAPH:error],Description :
ERROR,11 Apr 2013 12:16:53,561,[OIMCP.SAPH:error],oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
... 16 more
Caused by: oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
... 17 more
Caused by: com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
... 18 more
ERROR,11 Apr 2013 12:16:53,561,[OIMCP.SAPH:error],================= End Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,562,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,563,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :

Now i am able to configure but i am seeing this error
java.lang.UnsatisfiedLinkError: /opt/Oracle/jco/libsapjco3.so: /opt/Oracle/jco/libsapjco3.so: ELF file data encoding not little-endian (Possible cause: endianness mismatch)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1732)
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:1028)
at com.sap.conn.jco.rt.DefaultJCoRuntime.loadLibrary(DefaultJCoRuntime.java:444)
at com.sap.conn.jco.rt.DefaultJCoRuntime.registerNativeMethods(DefaultJCoRuntime.java:310)
at com.sap.conn.jco.rt.JCoRuntime.registerNatives(JCoRuntime.java:1027)
at com.sap.conn.rfc.driver.CpicDriver.<clinit>(CpicDriver.java:956)
at com.sap.conn.rfc.engine.DefaultRfcRuntime.getVersion(DefaultRfcRuntime.java:43)
at com.sap.conn.rfc.api.RfcApi.RfcGetVersion(RfcApi.java:261)
at com.sap.conn.jco.rt.MiddlewareJavaRfc.<clinit>(MiddlewareJavaRfc.java:198)
at com.sap.conn.jco.rt.DefaultJCoRuntime.initialize(DefaultJCoRuntime.java:75)
at com.sap.conn.jco.rt.JCoRuntimeFactory.<clinit>(JCoRuntimeFactory.java:23)
at com.sap.conn.jco.rt.About.<init>(About.java:42)
at com.sap.conn.jco.rt.About.main(About.java:81)

Custom segment does not exist for message type Debmas_cfs

Hi,
I have created a custom segment YEXTRA for basic type DEBMAS06.
I have done the configuration in We82 and We20.
I have implemented the segment in User Exit "EXIT_SAPLVV01_001". Now when I am executing the TCODE BD12 then it is creating the Idoc with custom segment. But when I apply the filter on sales org in BD64 then it starts giving me error that " Segment Y**** does not exist for message type DEBMAS_CFS.
Kindly suggest if I need to do some other configuration also.
Thanks.
Regards,
SAurabh

Hi Gearge,
To add custom segments, you should create an extension.
the TCODE is we30.
Refer this link:
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/frameset.htm
Regards,
Ravi

Fill / populate customer segments in extension of ARTMAS05

Similar Messages

Maybe you are looking for