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

Similar Messages

  • 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.

  • 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

  • Maintain Text

    Hi All,
    I want to maintain text in infotype 0102 grievances and i am also maintaining the same but i want to maintain 2 t0 3 different texts in the same entry will it be possile ?
    Thanks
    Giri

    Hi
    In the infoobect -> master data/texts select short,medium,long texts then u can maintain 3 different texts.
    Siri

  • 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

  • How to create a day type in Infotype 0041 (Want to maintain EE Retirement date)

    Dear Consultants,
    Can any buddy tell how to create a day type (Retirement date) in Infotype 41,
    My client want to maintain employees retirement date in Infotype 0041, please share your Ideas.
    Thanks & Regards,
    Navesh

    Hi Sridevi,
    Thanks for quick reply.
    Regards,
    Navesh

  • Maintain text for all infotype

    Hello,
    Is someone knows why in some infotype the option "maintain text" is active and for others it isn't.
    Can i active it for all infotype?
    Thanks.
    Edited by: marc frenay on Aug 20, 2009 12:43 PM

    Hi,
               You can change any standard Infotype text as per your requirment.Go the table view V_T582S & change the text for any infotype as per your requirement.
    Snita

  • "Maintain Text" (press F9) in LSMW

    How to handle "Maintain Text" (press F9) in LSMW. The problem is when converting String to Character. Anyone have experience for this?
    rgds,
    Handoko

    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

  • Unable  to view the message in PA30 maintain text in workflow

    Hi All,
    We have developed a workflow which gets triggered when ever a record gets created in PA30 infotype 0267.
    At the time of record creation the user can maintain his comments in Goto=> Maintain text.
    After the record gets created the workflow gets trigerred,
    the record gets locked and a workitem appears in the users
    inbox.
    The user doubles clicks on the workitem and a decision screen appears. Using the objects and Attachments the user can vie the record and also the icon  for maintain text.
    my problem is that  after the record gets locked I am not able to view the text maintained in the maintain text editor,
    whereas after that record gets unlocked  I am able to view the text.
    Are there any settings via which we can view the text irrespective whether it is created at the time record is locked or not.
    Thanks and Regards
    Shraddha

    Hi,
    By looking at the word 'Maintain text', it looks to me that it doensn't make sense to have this option up when that particluar record is locked. Or there should be an option saying 'Display Text'.
    Anyway, what is the purpose of the comments written by the creator of the record? is it only to facilitate the next approver to take his decision or Do you need this comment always attached with record for some proof?
    If comment is only to facilitate the next approver to take his decison and not really required to be attached along with record, then may be you can do the following
    1. Once the record gets created, the first workitem send it to creator only. In the description mention to add comment and click to continue to go for approval. So, when work item comes to creator he can add the comment using 'Create' option with workitem and this comment will be there as an attachment through out the workflow. So approver will also be able to see the comment.
    2. If at all it is required to store these comments along with record, once the whole approval process gets over, in the last step write a method to extract the attachments from workflow container and assign aginst the record. We have FM's to extract attachments ( SAP_WAPI_GET_ATTACHMENTS) and also FMs to store against an object (ARCHIV_CREATE_TABLE,ARCHIV_CREATE_FILE).
    Hope this helps you !!
    Regards
    Krishna Mohan

  • Problem in PA30 Maintain Text

    Hi All,
    We have recently encountered a problem with maintaining text via PA30. I have searched for solutions for this and the answer i got is to remove the concern infotype from the grouping table V_T582G. This eventually worked. Problem solved, we can now maintain text for concern infortypes.
    However, when maintaining infotypes via ESS, there seems to be a problem. Pointing that the infotype is not maintained in V_T582G.
    Can anyone please advice us on how to go about this problem? Any suggestion would be greatly appreaciated.
    Regards,
    Ranilo

    Hi Ranilo,
    If you maintain ths infotype via ESS then you will need an entry in T582G as ESS use the new infotype framework.
    In the past there was a technical restriction which prevents to maintaint text for shared infotypes (ITs with an entry in T582G).
    This restrictions has been removed recently via note 1468564 T582A: Cannot activate text maintenance for infotype.
    Implement this note, it will allow you to have the text maintenance allowed on shared infotypes.
    Hope this help
    Sarah

  • DAte not available in infotype 0041(date specification)

    Hai All,
    In our place we are using 4 type of "date type"
    Z1 Hired date.
    Z2 Seperation Date
    Z3 Leave quota start
    Z4 Service entry date
    for all employees date specification maintain by dynamic action.
    for some employees date specification is not maintain by the system.they are having only Z1 Hiring date only. others not available.
    how can i rectify this problem?
    Kind regards.
    Dinesh.

    Hi
    You have to check your Dynamic action.
    While querying dynamic ation how did you quaried, on which grouping you quried ?
    The employee who dont get the details are members in that group are not?
    if you give it in feature you must have all 4 dates to all the employees, otherwise you will be in trobuble
    becuase SAP wont allow you fill the type only without date in infotype 0041
    Regards
    Adi

  • Maintaining Text data for IT0102 in Ad Hoc Query

    We use the "Maintain Text" function to store comments and additional data for Grievance information on IT0102.  I need these comments to be included in a query for IT0102, however I only see the indicator for if text exists...there's no "field" to select to show the actual text - mainly because it's a note and not a field.
    Any suggestions???

    Hi,
    you could make a custom field in your infoset for infotyp 0012. Then you could append code to this field and read the text with function module
    HR_ECM_READ_TEXT_INFOTYPE into this field. 
    Regards Bernd

  • Reading infotype 0041 in PCR

    I need to read the date of joining in PCRs. i am maintaining date specification infotype 41. how to get this date from IT 41 in PCR. What operation i need to use.. Or is there any operation which can directly give hiring date of person without maintaining 41 infotype.
    pls tell its urgent.
    Thanks in Advance.

    I sent you this information, words in bold I think would help you
    Evaluating Date Specifications in Payroll
       Object
         Operations NUM, AMT and RTE evaluate date specifications for the
         calculation of deadlines. Retrieval takes place using the function
         DATES.
         Two dates are determined. These are interpreted as the start and end
         dates of a period. The evaluation of deadlines can return incorrect
         results if the second date lies before the first date. Therefore, for
         deadline calculation purposes, the first date should always be smaller
         than the second date.
         Date types with the following short names can be used for the
         evaluation. All date types other than 'X' are only taken into account if
         they are before the end of the current payroll period.
         In the operations NUM, RTE und AMT, specification of the date type
         follows the operand F directly.
         A, B  First entry from infotype 0000
         C    Last entry, or reentry
         D  Last change of individual working time from infotype 0041
             In table T530, if the field KUNBZ (indicator for irregular payments)
             is 05, then the start date of the work center is taken for D.
         E    Last change of capacity utilization level from infotype 0008
         F    Last change of weekly working hours from infotype 0007
             A comparison is carried out with date type C for the date types D, E
             and F. If the value determined for C is greater than the values
             determined for D, E or F (that is, a later date), the value of C is
             used for D, E or F. Any changes in the capacity utilization level or
             the like before the last reentry are not evaluated. The date of the
             last reentry is taken instead of this date.
         G    Birth date from infotype 0002
         W    Reentry
             The last reentry date is entered in this date specification. If no
             reentry data exists, the initial entry date is used. This date has
             the short name 'A' in the evaluation.
         X     Employee leaves after the end of the period in accordance
         with infotype 0000
             The system checks whether there is a record for infotype 0000
             (Actions) has a record where the Stat2 field has the value 0 (=
             left). The start date (BEGDA) of this record is the leaving date.
             This date type always has an entry. If an employee leaves after the
             end of the period in question, this date will be used. If no leaving
             date exists, the date December 12, 9999 is used.
         Z     Leaving before the end of the period in accordance with infotype
         0000
             The system checks whether there is a record for 0000 (Actions) where
             the Stat2 field has the value 0 (= left). The start date (BEGDA) of
             this record is the leaving date.
             This date type always has an entry. If an employee leaves before the
             period in question, this date is used. If no date is given, the date
             December 31, 9999 is used.
         nn    Date type 'nn' from the Date Specifications infotype (0041)
             Date types are taken from table T548Y.
       Syntax
         The operands are constructed as follows:
             Operation NUM= is taken as an example: Processing is identical for
             RTE and AMT:
          NUM=Faaesb
              F          Fixed indicator for deadline calculation
               aa           Date type: Start date of period to be
                            calculated; if the date type is not 'nn,'
                            the second position is left blank.
                 e          Unit, in which the duration is calculated:
                            T = days
                            W = week
                            M = months
                            C = complete months
                            K = complete calendar months
                            N = complete calendar months (rounded up)
                            J = Years
                            Y = Complete years
                           The difference between the individual
                           units is explained in
         Calculation Examples
                           in more detail.
                  s         End date of period to be calculated:
                            (blank)  End of current payroll period
                            J        End of current calendar year
                            A        Start of current calendar year
                            B        Start of WPBP period
                           No other specifications are possible.
                   b        If the date type specified in parameter aa
                            does not exist for the person in question,
                            an alternative fixed identification is
                            selected. If 'SPACE' is entered, the
                            date 31.12.9999 is used. However, you can use
                           one of the date types listed above as
                           an alternative or enter 0
                           0 to set the alternative value to 0.
       Example
         NUM=FA_M_
               F         Identifier for deadline calculation
               A             Date type A, initial entry from infotype 0000
                _            Blank; placeholder for 2-character
                             date type from infotype 0041
                 M           Deadline calculation is in months
                  _          Blank; key date for deadline calculation
                             End of payroll period
                   _         Blank; If no specification exists for date
                             type A, the date 31.12.9999 is used as an
                             alternative.
         NUM=F01M_A
             F                Identifier for calculation deadline
              01              Date type for technical entry date from
                              infotype 0041
                M             Deadline calculation in months
                 _            blank, key date for calculating the
         deadline
                              End of payroll period
                  A           Alternative date: if no specification exists
                              for date type 01, the first entry from
                              infotype 0000 is used.
         Under Calculation Examples for Evaluating Date Specifications you can
         find more information and case studies regarding how to calculate the
         period between a start and end date for the operations NUM, RTE and AMT.
    Regards. Manuel Campos

  • 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

  • Maintain Text PA - Authorization issue?

    Hi experts,
    I'm having a problem when updating text in infotypes using "Maintain Text" (F9). Most user's SAP GUI block when trying t access the text window (after clicking Maintain text). SAP GUI just freeze (no message). It's the only time I have got an error like this.
    Since some users are able to maintain text, do you think it could be an authorization issue?
    Could you please show me which authorization object should be customized to let them to maintain text?
    If you think is not an authorization issue, any idea?
    I would really appreciate your help since I run out of ideas...
    Thank you very much
    Chema

    Hi Dilek,
    thank you for your help. SU53 shows a problem with authorizations for P_ORGXX (R, ,,,,) for people who can't maintain text, but it also show a problem with P_ORGINCON (R,,,,,,,) for people who can.
    I know these two authorization object are related to infotype read/writing, but it is also related to maintain text feature?
    MS Word comment seems a posible explanation, because since SAP GUI blocks should be any local configuration issue, but still all computers has the same version and instalation.
    Thank you again for your help
    Cheers,
    Chema

Maybe you are looking for