Maintenance text  in infotype 102 (HR Module)

Dear All,
We got trouble to find the maintenance text in infotype 102 (grievances).  I mean how do we know in which field in database the data is stored ? We need to create a report that using that field. Thanks a lot for the response.
Regards,
Revhad

Infotype texts are stored in the PCL1 Cluster.. pl check the following  <a href="https://forums.sdn.sap.com/click.jspa?searchID=456564&messageID=2364513">Thread</a> to read such texts..
~Suresh

Similar Messages

  • Posting HR Text for Infotype 2004

    Hello Friends,
    I am using RP-EXP-C1-TX to write text for Infotype 2004(Availability) and then updating it using below Routine:
    IF sy-subrc = 0.
    PERFORM prepare_update(sapfp50p) USING 'V'.
    COMMIT WORK and WAIT UP TO 3 SECONDS.
    ENDIF.
    My issue is that the text is getting updated properly but it is quite intermittent, meaning it posts sometimes and sometimes not. When I run it in debugging mode and execute each statement in PREPARE_UPDATE, it updates the text properly. But when I run it all at once, it updates at its own mood. I assume there is no issue with the code as it creates text many a times.
    I have given a WAIT of 3 seconds also after the PREPARE_UPDATE call which has already made it very slow. The fact that through PA61 everything gets updated pretty quickly,  makes me worry even more.
    Please let me know what should I do or if I am missing something somewhere. Or this can be a system/Database issue? I am afraid if I move this to Production assuming that it is a system issue and it does not work there either.
    Any help would be appreciated and rewarded.
    Thanks.

    Resolved myself

  • Use of text elements in wirte_form function module.

    Hi guru's,
    Could any one tell me  what is the use of text elements in write_form functional module SAP SCRIPTS. As per my knowledge text elements are used for multi language purpose is there any other advantage other than that.
    Thanks in advance.
    Vardhan.

    Hello.
    A text element is a block in script that can be written several times in your document. You can put fixed texts, variables, include texts, images, etc etc
    When you see WRITE_FORM, element 'X', you know that everything that is inside element /E X of your script is writen. It's very usefful to organize your script, and it eases to construct a very complex script.
    It's also usefull to translations in SE63.
    Best regards.
    Valter Oliveira.
    Edited by: Valter Oliveira on May 27, 2008 10:05 AM

  • Maintain Text in Infotype 0041 via LSMW

    Hi,
    Has anyone had success loading text into Infotype 0041 via lsmw?
    I am trying to create an lsmw to maintain text in infotpye 0041. I follow the route PA30, then when in IT0041 I go to edit and maintain text.
    The problem is that I get a syntax error because the field I am trying to update is RSTXP-TDLINE which is a length 0 and format type string. LSMW won't accept string fields so in the generated program for the lsmw the line reads: "tdline_01(000000) type c,". This obviously doesn't pass the syntax check.  
    Any help greatly appreciated.
    Regards,
    Warren.

    Hi
    I just tried to create a LSMW in my DEV environment. I didnt get any error when recording. I entered the text in IT41 without any issue. What I am getting in the source code is:
    RSTXP-TDLINE(01)               Abcde                TDLINE_01            ABAP Source Line
    Am I missing what you are seeing?
    Cheers
    Pramod

  • Upgrade from 4.6C to ECC 6.0 - change text of infotype 0002 screen

    Hello Guru,
    My client is upgrading from 4.6C to ECC 6.0. In 4.6C the field RUFNM text in infotype screen for 0002 is "Know As"  where in ECC 6.0 is now "Nickname". The field is P0002-RUFNM? If I want to change the text in ECC 6.0 from 'Nickname' to "Know As". What is the best option? Modify the screen? or change the Data element? or any better way?
    Thanks

    Hi Bob,
    To change the Field Text, Data Element would be the better option.
    Good Luck
    Om

  • Maintain text for Infotype 0015

    Hi,
    I want to upload the text to infotype 0015 via Maintain Text.
    Can any one help me how to upload the text using export or macros.
    Thanks & Regards,
    Mohan

    Hi Murali,
    I haven't tried it.. but may be you can look at the logic in HR_READ_INFTY_NOTE & try to do the opposite.. ie something like
    export ptext = text
                   to database pcl1(tx)
                   id key ignoring conversion errors.
    You may have to read the infotype record first to get the key.. also remember to update the field ITXEX for eahc record.. otherwise, the text cannot be displayed via pa20/30..
    ~Suresh

  • Export Text into Infotype text cluster

    Hi,
    I am trying to insert some text into the infotype text (Edit -> Maintain Text) for infotype 40 programmatically.
    I have written the sample code below but the text is not inserted into the infotype. Can someone advise me what could be wrong with the code ?
    Many thanks in advance.
    Regards
    KC
    =============================================
    REPORT ZTEXTO .
    TABLES : PERNR, PCL1, pcl2.
    INFOTYPES : 0040.
    INCLUDE RPPPXD00.
    DATA : BEGIN OF COMMON PART BUFFER.
           INCLUDE RPPPXD10.
    DATA : END OF COMMON PART BUFFER.
    INCLUDE RPC1TX00.
    GET PERNR.
       LOOP AT P0040.
         MOVE-CORRESPONDING P0040 TO TX-KEY.
         REFRESH PTEXT.
         PTEXT-LINE = 'THIS IS A TRAIL INSERT INSERT INTO INFOTYPE TEXT'.
         APPEND PTEXT.
         RP-EXP-C1-TX.
       ENDLOOP.
       PERFORM PREPARE_UPDATE USING 'V'.
    BUFFER ADMINISTRATION ROUTINE.
    INCLUDE RPPPXM00.

    Hi,
    I have this same issue.  I have the infotype field ITEXT is set to 'X'.  I am trying to update the record in infotype 0672.  I am using the following code, it executes well. But it is not updating the infotype with the text.
    REPORT  zven_insert_text_infotpe                .
    TABLES : pernr, pcl1, pcl2.
    INFOTYPES : 0672.
    Data: gs_0672 TYPE STANDARD TABLE of pskey with header line.
    INCLUDE rpppxd00.
    DATA : BEGIN OF COMMON PART buffer.
    INCLUDE rpppxd10.
    DATA : END OF COMMON PART buffer.
    INCLUDE rpc1tx00.
    gs_0672-pernr = '00010053'.
    gs_0672-infty = '0672'.
    gs_0672-subty = '0001'.
    gs_0672-endda = '04042005'.
    gs_0672-begda = '04042005'.
    append gs_0672.
    clear  gs_0672.
    *GET pernr.
      LOOP AT gs_0672.
        MOVE-CORRESPONDING gs_0672 TO tx-key.
        REFRESH ptext.
        ptext-line = 'THIS IS A TRAIL INSERT INSERT INTO INFOTYPE TEXT'.
        APPEND ptext.
        rp-exp-c1-tx.
      ENDLOOP.
      perform prepare_update using 'V'.
      include RPPPXM00.
    Please let me know ASAP.
    Appreciate.
    Thanks.
    vgoy

  • Maintain texts for Infotype 0019 via ABAP.

    Hi,
      The issue is related to maintaining texts for Infotype 0019. I have a program below. The main problem is I am facing is for some records it inserts text in Infotype (0019) but for some it does not. Can anyone suggest why so or a way to resolve this problem ???
    REPORT  ytbctest009.
    TABLES: pernr, pcl1.
    INFOTYPES: 0019.
    DATA:  key LIKE pskey.
    DATA: BEGIN OF ptext OCCURS 200.
    DATA:   line(72).
    DATA: END OF ptext.
    SELECTION-SCREEN BEGIN OF BLOCK abc WITH FRAME TITLE text-001.
    PARAMETERS:               p_pernr LIKE pernr-pernr.
    SELECTION-SCREEN END OF BLOCK abc.
    ptext-line = 'TEST 1'.
    APPEND ptext.
    ptext-line = 'Test 2'.
    APPEND ptext.
    ptext-line = 'Test 3'.
    APPEND ptext.
    rp-read-infotype p_pernr 0019 0019 '18000101' '99991231'.
    SORT p0019 DESCENDING.
    READ TABLE p0019 INDEX 1.
    p0019-itxex = 'X'.
    MOVE-CORRESPONDING p0019 TO key .
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
      EXPORTING
        infty         = '0019'
        number        = p_pernr
        validityend   = p0019-endda
        validitybegin = p0019-begda
        record        = p0019
        operation     = 'MOD'.
    EXPORT ptext TO DATABASE pcl1(tx) ID key. 
    Thanks in advance.

    Hi Rajashree,
    I hope , below code will solve the problem.
    <b>Main Code</b>
    FUNCTION zhr_mustus_update_it0019.
    *"*"Local interface:
    *"  IMPORTING
    *"     VALUE(IM_PERNR) TYPE  P0019-PERNR OPTIONAL
    *"     VALUE(IM_USRID) TYPE  PA0105-USRID OPTIONAL
    *"     VALUE(IM_SUBTY) TYPE  P0019-SUBTY
    *"     VALUE(IM_TERMN) TYPE  P0019-TERMN OPTIONAL
    *"     VALUE(IM_MNDAT) TYPE  P0019-MNDAT OPTIONAL
    *"     VALUE(IM_BVMRK) TYPE  P0019-BVMRK OPTIONAL
    *"     VALUE(IM_TEXT) TYPE  CHAR30 OPTIONAL
    *"  EXPORTING
    *"     VALUE(EX_RETURN_MESSAGE) TYPE  STRING
    *"     VALUE(EX_MESSAGE_ID) TYPE  ARBGB
    *"     VALUE(EX_MESSAGE_NUMBER) TYPE  MSGNR
    *"  EXCEPTIONS
    *"      SYSTEM_FAILURE
    *"      COMMUNICATION_FAILURE
      REFRESH bdcdata.
      REFRESH it_bdc_message.
    * Validations
      PERFORM validations USING im_usrid im_subty im_mndat
                       CHANGING im_pernr
                                g_task_date
                                g_rem_date.
    * Return message
      MOVE:
        g_message TO ex_return_message,
        'ZMSGHR'  TO ex_message_id,
        g_msgno   TO ex_message_number.
    * If there any error don't process
      CHECK ex_return_message IS INITIAL.
    * If reminder date is missing then its creation
      IF im_mndat IS INITIAL.
    * Fill BDC for PA30 Creation
        PERFORM fill_bdc_for_creation USING im_pernr
                                            im_subty
                                            im_text
                                            g_task_date
                                            g_rem_date.
      ELSE.
    * Its a change, Fill BDC for PA30 change
        PERFORM fill_bdc_for_change USING im_pernr
                                          im_subty
                                          im_termn
                                          im_bvmrk
                                          im_text.
      ENDIF.
    * Call transaction PA30
      PERFORM bdc_call_transaction.
    * Return message
      MOVE:
        g_message TO ex_return_message,
        g_msgid   TO ex_message_id,
        g_msgno   TO ex_message_number.
    ENDFUNCTION.
    <b>All Above Subroutines,</b>
    *& Form  Validations
    *  Validations for MUS/TUS
    *      -->U_USRID      User id for TUS
    *      -->U_SUBTY      Subtype 10 - MUS, 11 - TUS
    *      -->U_MNDAT      Reminder date
    *      <--PERNR        Person for MUS
    *      <--U_TASK_DATE  Task date
    *      <--U_REM_DATE   Reminder date
    FORM validations USING u_usrid     LIKE pa0105-usrid
                           u_subty     LIKE p0019-subty
                           u_mndat     LIKE p0019-mndat
                  CHANGING u_pernr     LIKE p0019-pernr
                           u_task_date LIKE sy-datum
                           u_rem_date  LIKE sy-datum.
      DATA:
        BEGIN OF it_tmp_0019 OCCURS 0,
         termn LIKE pa0019-termn,
        END OF it_tmp_0019.
      CLEAR g_message.
    * Validations for MUS
      IF u_subty EQ c_subty_10.
        MOVE sy-datum TO u_task_date.
        IF u_pernr IS INITIAL.
    * Person number is missing
          MOVE:
            text-001 TO g_message,
            '003' TO g_msgno.
        ELSEIF u_mndat IS INITIAL.
    * Its creation, check if there is already a open item
          SELECT pernr
            FROM pa0019
            INTO u_pernr
           WHERE pernr EQ u_pernr
             AND subty EQ u_subty
             AND bvmrk NE '2'.
            EXIT.
          ENDSELECT.
          IF sy-subrc EQ 0.
    * Throw an error if there is already a open item
            MOVE:
              text-006 TO g_message,
              '004'    TO g_msgno.
          ENDIF.
        ENDIF.
      ENDIF.
    * Validations for TUS
      IF u_subty EQ c_subty_11.
        IF u_usrid IS INITIAL
       AND u_pernr IS INITIAL.
    * User/Person number is missing
          MOVE:
            text-002 TO g_message,
            '005'    TO g_msgno.
        ELSEIF NOT u_usrid IS INITIAL.
          SELECT pernr
            FROM pa0105
            INTO u_pernr
           WHERE usrid EQ u_usrid.
          ENDSELECT.
          IF u_pernr IS INITIAL.
    * Person number is missing
            MOVE:
              text-001 TO g_message,
              '006' TO g_msgno.
          ENDIF.
        ENDIF.
        IF g_message IS INITIAL.
          SELECT termn
            FROM pa0019
            INTO TABLE it_tmp_0019
           WHERE pernr EQ u_pernr
             AND subty EQ u_subty
             AND bvmrk NE '2'.
          READ TABLE it_tmp_0019 WITH KEY termn = sy-datum.
    * There is no open task for today
          IF sy-subrc NE 0.
            MOVE sy-datum TO u_task_date.
          ELSE.
    * There is a open task for today, new task should be created next
    * available date and reminder date is yesterday's date
            SORT it_tmp_0019 DESCENDING.
            READ TABLE it_tmp_0019 INDEX 1.
            u_task_date = it_tmp_0019-termn + 1.
            u_rem_date = sy-datum - 1.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDFORM.                    "VALIDATIONS
    *& Form  Fill_bdc_for_creation
    *  BDC data for creation , Transaction PA30
    *      -->U_PERNR      Person
    *      -->U_SUBTY      Subty MUS - 10, TUS - 11
    *      -->U_TEXT       Text
    *      -->U_TASK_DATE  Task date
    *      -->U_REM_DATE  Task date
    FORM fill_bdc_for_creation USING u_pernr LIKE p0019-pernr
                                     u_subty LIKE p0019-subty
                                     u_text  TYPE char30
                                     u_task_date LIKE sy-datum
                                     u_rem_date  LIKE sy-datum.
    * Scree1
      DATA:
        l_task_date(10),
        l_rem_date(10).
    * Use system date as Task date
      WRITE:
        u_task_date TO l_task_date,
        u_rem_date TO l_rem_date.
      PERFORM bdc_dynpro      USING 'SAPMP50A' '1000'.
      PERFORM bdc_field       USING 'RP50G-PERNR'
                                    u_pernr.
      PERFORM bdc_field       USING 'RP50G-CHOIC'
                                    '0019'.
      PERFORM bdc_field       USING 'RP50G-SUBTY'
                                    u_subty.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=INS'.
    * Screen2
      PERFORM bdc_dynpro      USING 'MP001900' '2000'.
      PERFORM bdc_field       USING 'P0019-TMART'
                                    u_subty.
      PERFORM bdc_field       USING 'P0019-TERMN'
                                     l_task_date.
      IF NOT u_rem_date IS INITIAL.
        PERFORM bdc_field       USING 'P0019-MNDAT'
                                       l_rem_date.
      ENDIF.
      PERFORM bdc_field       USING 'RP50M-TEXT1'
                                    u_text.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '/00'.
      PERFORM bdc_dynpro      USING 'MP001900' '2000'.
      PERFORM bdc_field       USING 'P0019-TMART'
                                    u_subty.
      PERFORM bdc_field       USING 'P0019-TERMN'
                                     l_task_date.
      IF NOT u_rem_date IS INITIAL.
        PERFORM bdc_field       USING 'P0019-MNDAT'
                                       l_rem_date.
      ENDIF.
      PERFORM bdc_field       USING 'RP50M-TEXT1'
                                    u_text.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=UPD'.
    ENDFORM.                    "fill_bdc_for_creation
    *& Form  fill_bdc_for_change
    *  BDC data for change , Transaction PA30
    *      -->U_PERNR    Person
    *      -->U_SUBTY    subtype MUS - 10 , TUS - 11
    *      -->U_MNDAT    Reminder date
    *      -->U_BVMRK    Status
    *      -->U_TEXT     Text
    FORM fill_bdc_for_change USING   u_pernr LIKE p0019-pernr
                                     u_subty LIKE p0019-subty
                                     u_termn LIKE p0019-termn
                                     u_bvmrk LIKE p0019-bvmrk
                                     u_text  TYPE char30.
    * Scree1
      DATA l_termn_date(10).
      WRITE u_termn TO l_termn_date.
      PERFORM bdc_dynpro      USING 'SAPMP50A' '1000'.
      PERFORM bdc_field       USING 'RP50G-PERNR'
                                    u_pernr.
      PERFORM bdc_field       USING 'RP50G-CHOIC'
                                    '0019'.
      PERFORM bdc_field       USING 'RP50G-SUBTY'
                                    u_subty.
      PERFORM bdc_field       USING 'RP50G-BEGDA'
                                    l_termn_date.
      PERFORM bdc_field       USING 'RP50G-ENDDA'
                                    l_termn_date.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=MOD'.
    * Screen2
      PERFORM bdc_dynpro      USING 'MP001900' '2000'.
      PERFORM bdc_field       USING 'P0019-TMART'
                                    u_subty.
      PERFORM bdc_field       USING 'P0019-TERMN'
                                     l_termn_date.
      PERFORM bdc_field       USING 'RP50M-TEXT1'
                                    u_text.
      PERFORM bdc_field       USING 'P0019-BVMRK'
                                    u_bvmrk.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=UPD'.
    ENDFORM.                    "fill_bdc_for_change
    FORM bdc_call_transaction.
      DATA:
        l_mode(1) TYPE c VALUE 'N',
        l_lines   TYPE i,
        l_msgvar1 LIKE balm-msgv1,
        l_msgvar2 LIKE balm-msgv2,
        l_msgvar3 LIKE balm-msgv3,
        l_msgvar4 LIKE balm-msgv4.
      CALL TRANSACTION 'PA30'  USING bdcdata  MODE l_mode
                               MESSAGES INTO it_bdc_message.
    * Get last message
      DESCRIBE TABLE it_bdc_message LINES l_lines.
      READ TABLE it_bdc_message INDEX l_lines.
      MOVE:
        it_bdc_message-msgid TO g_msgid,
        it_bdc_message-msgnr TO g_msgno,
        it_bdc_message-msgv1 TO l_msgvar1,
        it_bdc_message-msgv2 TO l_msgvar2,
        it_bdc_message-msgv3 TO l_msgvar3,
        it_bdc_message-msgv4 TO l_msgvar4.
    * Prepare message
      CALL FUNCTION 'MESSAGE_PREPARE'
        EXPORTING
          language               = sy-langu
          msg_id                 = g_msgid
          msg_no                 = g_msgno
          msg_var1               = l_msgvar1
          msg_var2               = l_msgvar2
          msg_var3               = l_msgvar3
          msg_var4               = l_msgvar4
        IMPORTING
          msg_text               = g_message
        EXCEPTIONS
          function_not_completed = 1
          message_not_found      = 2
          OTHERS                 = 3.
      IF sy-subrc <> 0.
        MOVE text-005 TO g_message.
      ENDIF.
    ENDFORM.                    "BDC_FIELD
    *        Start new screen                                              *
    FORM bdc_dynpro USING program dynpro.
      CLEAR bdcdata.
      bdcdata-program  = program.
      bdcdata-dynpro   = dynpro.
      bdcdata-dynbegin = 'X'.
      APPEND bdcdata.
    ENDFORM.                    "BDC_DYNPRO
    *        Insert field                                                  *
    FORM bdc_field USING fnam fval.
      CLEAR bdcdata.
      bdcdata-fnam = fnam.
      bdcdata-fval = fval.
      APPEND bdcdata.
    ENDFORM.                    "BDC_FIELD
    Cheers.
    Santosh.

  • Reading Texts from Infotype

    Hi,
    How can we read texts from the Infotype. There is this function module HR_ECM_READ_TEXT_INFOTYPE, but we need the Employee Number, Begin date and End Date as inputs.
    I just want to check if a field with a particular value exists or not.
    just like this works to check whether the field DAT35 with value 99991231 exits or not.
    SELECT PERNR FROM PA0035 INTO V_PERNR WHERE DAT35 = '99991231'.
    IF SY-SUBRC = 0.
    ENDIF.
    the same way for a text, but this text actually gets stored in a structure thats why we cannot use a select for infotype
    Thanks in advance.

    Hi,
    What i am getting from ur explanation is that u are having a probelm in accessing a text field from the infotype, i.e: the value field in included in the infotype table (PA0035) but its text is in another table.
    If this is the problem, u should first use select statement on PA0035 to get the required infotype record. Then use F1 help on the required text field on the infotype screen to get the table and field name. Then u can use select statement on that table by specifying the relavant value field from the previous select in the where clause.
    Hope this hepls

  • Help to get "text" from infotype

    Hi Everybody,
    I need to read data from "maintain text" (PA20/PA30, Access path: Edit-Maintain text (function button - F9).) for some infotype.
    So, Iu2019m using the piece of code below.
    tables: pernr.
    infotypes: 0657.
    data: key like pskey.
    data: begin of ptext occurs 200.
    data: line(72).
    data: end of ptext.
    get pernr.
    rp-read-infotype pernr-pernr 0657 '18000101' '99991231'.
    sort p0657 descending.
    read table p0657 index 1.
    move-corresponding p0657 to key.
    import ptext from database pcl1(tx) id key.
    My problem is that I have sy-subrc = 4. u201CThe specified data cluster was not found.u201D
    I also used the HR_READ_INFTY_NOTE and got the same problem, sy-subrc = 4 but I know that the pernr I use has text in his data, the field itxex = 'X'.(flag checked)
    Please help me to find out what it can be???
    Thanks a lot!
    Sasha.

    Hi Sasha,
    In the function module HR_READ_INFTY_NOTE
    You have to give the key as the following,
    PERNR 
    000XXXXX
    INFT
    0105
    SUBT
    0001
    OB
    nothing
    S
    nothing
    ENDDA
    enddate (check date format)
    BEGDA
    begin date (check date format)
    SEQ
    000
    and Tclass as 'A'
    I executed and got the text.
    Please let me know if you are not able to.
    thanks,
    krishna
    Edited by: krishna reddygari on Sep 17, 2008 5:13 PM

  • Extracting Text Field using a function module

    Hi Experts,
          We are trying to extract a test field from the R3 using a Function Module.
                  The Text from R3 Looks like this
                 Input Parameters
                  ID -1
                  SEQ 2
    It displays
              Column 1 Column2
               This is test
               strategy for Function
               Module xxxx
    So we put in some parameters to get this test field displayed. As you see the above is just one field but they are in different lines
            So what happens when we put in the database is it adds a new field
    Eg
    ID SEQ Column 1 Column2
    1   2        *            This is test
    1   2        *            strategy for Function
    1   2        *            Module xxxx
    The result that we need is
    D SEQ Column 1 Column2
    1   2        *            This is test strategy for Function Module xxxx
    How can we handle this in the Query Transform
    Your help in advance is appreciated.
    Thanks
    Edited by: alangilbi on Nov 17, 2010 3:49 AM

    Have you considered using a pivot transform to get your rows into columns and then a query transform to concatenate the columns together?

  • Display long text in i/o field(Module Pool)

    Hi all,
    I am using "CATSXT_SIMPLE_TEXT_EDITOR" function module
    to type long text in module pool.
    I did it successfully but my requirement is how to move
    long text i entered in "CATSXT_SIMPLE_TEXT_EDITOR"
    to my "input/output field text box".
    can anyone plz help me to solve this problem.
    Regards,
    Ranjith C.

    hi
    The long text ur giving is getting stored in CH_Text.
    So, declare a field and pass that to the FM.. so after that FM executes, then pass it on to the screen..using internal table.
    data: text type CATSXT_LONGTEXT_ITAB.
    CALL FUNCTION 'CATSXT_SIMPLE_TEXT_EDITOR'
      EXPORTING
        IM_TITLE              =
    *   IM_DISPLAY_MODE       = ' '
    *   IM_START_COLUMN       = 10
    *   IM_START_ROW          = 10
      CHANGING
        CH_TEXT               = text. " it will fill the long text here.
    Then move it to a internal table...
    Regards,
    Vishwa.

  • How to update other infotype from source infotype via function module?

    Want in source infotype to call a func.module, which shall update other infotype(s) in background.
    Have tried out with HR_INFOTYPE_OPERATION, but without success - gives mitchmatch of source it and target it in the internal it buffer tables.
    How to do?
    Requirements also are to secure rollback, if update of the last of ex. 3 target its fails.
    Anyone has experience on this issue?
    Regards Søren

    Know this functionality - also by means of own coding in the PAI by filling the int. tables dynmeas + initial_values. However the issue remains, i.e. the update has to be done by a function module called from PAI of own infotype, and from a function module you can't trigger the T588Z-functionality.
    The update of it0003 from own it9300 is only an example, have general requirements that:
    - from own infotype PAI a function module shall be called
    - from the function module update of other infotypes 
      shall take place (modify as well as insert and delete)
    - if more infotypes shall be updated from source infotype,
      rollback shall take place if ex. update of last target
      infotype fails (all to be updated or none!).
    Regards Søren

  • Maintaining / Displaying Text for Infotype record

    Hi,
    How do we maintain infotype text for the record. Or how to display the text maintained for infotype record (I used PA20/PA30 for IT0001 record but could not locate infotype text).
    Regards,
    Avinash Josalkar.

    Hi,
    If you want to know the text of a infotype then goto the table
    V_T582A.
    eg:0000  actions
    0001 organisation assignment.
    But if you want to change the standard text of a infotype then you need to have access key to change.
    But if you are asking the text table for the fields in 0001.
    then goto se11
    enter Pa0001--dislay
    click the tab entry help/check then you can see the table names in the column check table for each field.

  • Change text on infotype 8

    I want to change the text of one of the fields on the infotype 8 screen (Date of next increase).  Is there a way for me to do this?

    hi sara
    go to pa30 and go for 0008 infotype click on change and select which text you want to change press f1 key and technical information and note down the data element and go to TCODE CMOD there GOTO in menu bar under that select text enhancements- keywords-change then give data element which you have noted earlier and tick mark then change the text you want and tick mark again GOTO-text enhancements-keywords-restore cust version there give the version name 620 or 640 this you come to know from sap log on pad heading and save go to same and you can see that it is changed ok
    bye
    naveen

Maybe you are looking for