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.

Similar Messages

  • 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

  • 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

  • Whether any bapi is available or not for infotype 0019(monitoring of dates)

    Dear abapers,
    can u plz guide me whether any bapi is available or not for infotype 0019(monitoring of dates)
    i need to upload data from the text file to sap with the following fields.
    *Pers No.     *
    *Task Type     *
    *Date Type     *
    *Processing Indicator     *
    *Reminder date     *
    *Lead/follow-up time     *
    *Lead/follow-up time     *
    Comments
    regards,
    manoj

    Hi,
    Use this FM HR_INFOTYPE_OPERATION
    Regards,
    Shan

  • 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

  • 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

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

  • SaveAs and maintain "optimized for web view" via javascript???

    I am trying to do a SaveAs via javascript, but I need to maintain the linearized (optimized for web view) state of the PDF.
    I would get this via the SaveAs menu item, but I need to do it silently and rename the file (replace _H.pdf with .pdf).
    Is there anything that I can read that will help me do this? I have looked through the API reference, AcrobatUsers.com, web search, etc.
    Or, if it cannot be done, stop me now.
    Here is what I am doing currently wtih help from this forum.
    XXX_DoSaveLoRes = app.trustedFunction(function()
    app.beginPriv();
    this.saveAs(this.path.replace(/\_H.pdf$/i,"") + ".pdf");
    app.endPriv();
    Thanks,

    I don't think it can be done.

  • Updating value of for taxonomy attributes via ABAP API

    Hi ,
    We have table Product hierarchy repository in that we have Products table and ProductHierarchy table which is of type taxonomy .
    The product hierarchy is assigned to each product as lookup taxonomy field.
    Can anyone please let me know how we can update the values assgined to the attribute throght ABAP API.
    Example we have the attribute called color which assigned to Product Hierarchy 'A' and this product hierarchy 'A' is attached to Material '111' and the attribute color will have value 'Blue' for material '111' now I want to update the value of color to 'Red' . How we can achieve this via the MDM ABAP API.
    Regards,
    Amar Kamat

    If your question is how to change the value of an attribute for a specific product this is the solution:
    Use IF_MDM_CORE_SERVICES->RETRIEVE( ) to retrieve the product record so that you have a populated structure of type MDM_PARAMETER. In this structure you will find the entry relating to the taxonomy field. The VALUE attribute of this line entry will be a reference to type MDM_TAXONOMY_ENTRY.
    At this point you will want to take the TAXONOMY_ENTRY_ID and TAXONOMY_TABLE_CODE of this structure to retrieve the attributes. Using IF_MDM_CORE_SERVICE->RETRIEVE_ATTRIBUTES( ) and the attributes mentioned before you will get the results into a table of line type MDM_ATTRIBUTE_INFORMATION_SL.
    Select the appropriate line from the result table based on the attribute name (ATTR_NAME). In the record of type MDM_ATTRIBUTE_INFORMATION_SL you will now want to select the appropriate line from the table found in field ATTR_FEATURE_DOMAIN. Find the appropriate attribute (in this case color) by VALUE_NAME and copy the VALUE_ID (type MDM_UNIQUE_ID).
    Now back to where we left off in the original record (MDM_PARAMETER), loop through the table found at field TAXONOMY_ATTRIBUTES of the MDM_TAXONOMY_ENTRY looking in ATTR_INFO for the correct ATTR_NAME. When the correct entry is found, update the ATTR_FEATURE_DOMAIN with the new VALUE_ID and viola, you've got a mdm record ready to be updated.
    Simply call IF_MDM_CORE_SERVICE-UPDATE( ) with the modified record and you've updated your attribute assignment.
    In short:
    Navigate to the MDM_TAXONOMY_ENTRY of the product record
    Retrieve the attributes from the corresponding taxonomy table and navigate to the unique ID of the desired attribute
    Navigate to the attribute within the record's MDM_TAXONOMY_ENTRY and update the VALUE_ID with the new unique ID
    Update the product record
    Regards,
    Brian Dennett

  • Standard Workflow for Infotype 0019

    is there any SAP standard WF for monitoring of task IT 0019

    Hi,
    There is no standard flow for the down payment request generally in many projects down payment requests are rarely created process starts with Down payment request F-47 then Down payments F-48
    then clearing of Down Payment f-54
    Down PAyment request is just a template.If you want to use then use then u can skip this step.
    regards
    Deepa

  • 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

  • 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

  • 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

  • Query regarding Infotype maintain text

    Hi,
      Since I am totally new to HR I would like to know the expert opinion from you guys.
    Suppose for pers.no - 1000, I have Infotype 0019 having various task-types - Z3, Z6, Z5. Is it possible using following methods below to insert the texts only for task type Z6 ???
    Also, would the statements below work for records where NO TEXT WAS MAINTAINED AT ALL. My observation is that records with text maintained previously are only updated others are not...any reasons why so ??? Please reply back.
    Method 1 - EXPORT ptext TO DATABASE pcl1(tx) ID tx-key.
    Method 2 - RP-EXP-C1-TX.PERFORM PREPARE_UPDATE USING 'V'.
    Thanks,
    Rajeshree

    Hi Rajeshree,
    My opinion is as below.
    1. You can do this by ABAP coding. You can check the key where you have subtype also. Write a simple 'IF' statement & skip the record for other subtypes.
    For e.g if key-subtype eq 'Z6'
             EXPORT ptext TO DATABASE pcl1(tx) ID key.
            endif.
    2. I also tried the same program, for me also if text already exists, then the program is inserting values in the text. Till now I also did found why this is happening.Will let you know if I get the answer.
    Hope so Santosh solution of BDC might solve your issue.
    Please let me know if you have solved your issue & how.
    All the Best!!!
    Thanks,
    Sarika.

  • Post long text for document line item via FI-GL Inbound IDoc

    Hi guru,
    I am trying post extension ZFIDCP02 linked basic type FIDCCP02 and message type FIDCC2 IDoc in R/3 (4.6c) via IBM Websphere (Inbound IDoc),
    I am use inbound function module IDOC_INPUT_FIDCC2 and activate exit 008 (EXIT_SAPLF050_008) and exit 002 (EXIT_SAPLF050_002),
    In the extension ZFIDCP02 and under E1FISEG, I am add my segment  ZITEXT include field TDSPRAS, TDID, TDOBJECT, TDLINE.
    I am send  ZFIDCP02 IDoc via IBM Websphere no error  but all field TDSPRAS, TDID, TDOBJECT, TDLINE in my segment  ZITEXT not post in FI-GL.
    How can I  post long text for document line item (ZITEXT) in FI-GL ?.
    and I'm mean post ZITEXT to bank statement via IDOC.
    Please throw light on this  and  may be I  'm want solution or example ABAP code for exit 002 (EXIT_SAPLF050_002).
    Thanks in advance,
    Akkapong Pirachai
    CAT Telecom
    Edited by: Akkapong Pirachai on Aug 20, 2008 7:40 AM

    Close question because long time for answer.

Maybe you are looking for