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

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.

  • Pulling the Header text  for all the purchase orders

    Hello,
    Please help in resolving the below:
    Is there any code in SAp to pull theHeader text for all the purchase orders in the data base,
    Any tcode to pull the specific text automatically to pull the text from the requsition ( Plant wise in sourcing).
    Thanks

    STXH Text header 
    STXL Text detail
    Chk the below message thread
    Table to read PO Header text and item text
    BR,
    Krishna

  • 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

  • Wrap text for all-day events

    I've seen this question floating around, unanswered, since 2005...
    How can I get iCal to show the full text of an all-day event in Month View? There's lots of blank white space, but it seems that iCal never wraps the text of all-day events, and just cuts off the text that doesn't fit on one line.
    Am I missing something? Is there any way to get Apple to implement something so basic?

    I have the same question, but need to add one odd observation about my own experience...
    When I enter new events, sometimes the text wraps to two lines and sometimes the text is cut off after one line. It appears to be about 50-50. I can find no explanation for this behavior anywhere nor any way to control it. Very strange.

  • User in hr can able to create records in PA30.But will give read only access for all infotypes

    Hi Team,
    I have created one test role in HR. It will give Read access to all info types.
    But user can able to create Info type records in PA30. Please find the P_ORGIN values below.
    Authorization level            R
    Infotype                       *
    Personnel Area                 US
    Employee Group                 1
    Employee Subgroup              U*
    Subtype                        *
    Organizational Key             *
    OOAC values.
    AUTSW ADAYS       15
    AUTSW APPRO 0
    AUTSW DFCON 4
    AUTSW INCON 0
    AUTSW NNCON 0
    AUTSW NNNNN 0
    AUTSW ORGIN 1
    AUTSW ORGPD 4
    AUTSW ORGXX 0
    AUTSW PERNR 1
    AUTSW XXCON 0
    Note : user does not have access to any structural profile.
    I suspect is this bcz, if any user has proper 0105 and 0001 in HR master data can able to create records.Bcz user will be assigned to default sap structural profile "ALL"  in OOSB ?
    I can see user was not assigned to "ALL" profile in OOSB or in T77UA. and user cant able to write or change infotype data in pa30.
    Please suggest how the user can able to create  inftotype records in PA30.(Info :0002 for example)
    Appreciate Quick response.
    Regards,
    Venu.

    Sorry did not get the below comment.
    "The maintain flag in the structural profile does not relate to any maintenance authorization in PA.  It only affects the OM objects authorized by the structural profile.  For example the user may be able to delimit a position.  It will never grant any write authorization for any PA infotype "
    Do you mean , suppose if we give Org unit and evaluation path like attached screen ,user will get access to only the ORG UNIT  as its object type (can able to perform activities as mentioned in the role PLOG ) but cant perform any activity like address infotype change on the person (P) (as mentioned in P_ORGIN) who comes under the org unit mentioned in Structural profile ?
    My understanding is that i believe user total auth is an intersection of general +structural authorization.lets take HR admin wanted to change 0002 data   for some imps in org.We need to give access to that particular org to which the emps belongs to (through structural auth) and SHOULD CHECK the maintenance box in strucural auth and will access change access via role.
    And user cant able to edit his own data.
    Please find the Screens as requested. Please let me know if my understanding is correct or not ?
    Regards,
    venu.

  • Maintaining subtypes  for 210 infotype federal withholding

    Hi Gurus,
    I would like to know, if subtypes are not maintained for infotype 210? will this impact calculation of federal taxes for any state? .Help is appreciated.
    Thanks,
    Fred

    I dont think,, you will be able to create the record for infotype 210 without any subtype
    You can try by removing all subtypes :). then u will not be allowed to create the record.
    Regards
    Pradeep

  • Service Orders gets saved but text at item level are not saved for all item

    Hi All,
    We have configured service order scenario. The service order gets saved in GUI and in WebUI. But we are facing issue that not all the text entered at item level are getting saved.
    Example if we maintained text for 4 line items and save the SO.
    We open the saved SO, we get only 3 line items with proper text
    one of the line item text is not getting saved.
    The issue happens at both GUI and WebUI.
    Any pointers to fix this issue?
    Thanks and Regards,
    Gauri.

    Hi,
    You can try clearing the buffer using 'CRM_ORDER_INITIALISE' followed by CRM_ORDER_MAINTAIN" or TEXT_SAVE and TEXT_COMMIT, followed by BAPI_TRANSACTION_COMMIT with wait.
    Prerna

  • How to create new subtypes for OM infotype 1002?

    Gurus,
                I have a requirement to create four new subtypes (to different texts ) for OM infotype HRP1002.
    Let me know the procedure to achieve this.
    I looked in subtype table T591A and T591S, but couldn't find any subtype (even the standard ones like 0001,0002,0003 etc) for 1002 infotype.
    Thanks,
    Amit Jain

    Hi Amitkumar Jain,
    I am also facing same problem, i need create Infotyes with Subtypes in OM.Check below steps how i created
    1. I create Structure in se11.    HRI9119
    2.  In PPCI , i create infotype 9119
    3.In SM30 ,  I Maintain table  T777i,  here i selected my infotype (9119),  then i clicked  on infotype per object type and assign    subtype (9229, 9339) to the my infotype .
    4.   After that, in same screen, i selected my infotype  and assign TIME CONSTANT to my all subtype and infotypes.
    After this , any think required to maintain , Plz tell me.. i didn't find my subtype in  PP01.
    Thanks and Regards ,
    Venkatesh.M

  • 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

  • Read text for multiple entries(eg: for multiple customers) in XD03

    Hello all,
                       I have some (50) customer numbers (XD03) for which i need to find out whether any text is maintained or not.
    We can read the text using FM READ_TEXT, by passing Text ID, Name , object..etc.
    But the problem is we can just read one by one at a time for each coustomer
    Without writing a custom program is there any way to find the text for all the customers or for mutpliple entries.?
    do we have any FM where in we can pass multiple text names  ...and then we should get all the text assigned to it.
      Please let me know. Thanks in advance.

    Hi alll,
                  I am sorry, the requirement is just to know whether the text is maintained or not.
    (not to read the text)
    There are two ways to find:
    --> STXH table will give the result only if it has the text .
    -->There  is a standard report name is RVTEXTE...
       We have to give the values as below
    Text object: KNA1 (CUSOTMER)
    Text type  : *
    Text lan    : *  (or EN)
    Text name  : * or ( 352*) like this.
    I think we all are in the same page......
    Also I agree that we have to use FM REAd_TEXT to read the text...through programitically by loop endloop.
    Thanks for everyone for your time and response
    Thanks Rob for giving an idea to find the standard report...........

  • Default  header text for PO

    Hello,
    Mine client requirement is like they want default header Text for all PO.Please guide me, what is the customization required?
    Regards,
    Jyoti

    Hi jyoti,
    As per my understanding of your requirement, you can try to maintain the default PO Text in the "Vendor Master Record" or in "Contract" if applicable and then you need to do the following customisation to adopt these texts in the Purchase Orders.
    IMG -> Material Management -> Purchasing -> Purchase Order -> Texts for Purchase Orders -> Define Text Types for Header Texts and Define Copying Rules for Header Texts.
    In Define Copuying Rules for Header Texts -tab you can maintain that in which Target Header Text, the deault PO text should be adopted and from where i.e. From Vendor Master Record or Contract or RFQ. Check which of this satisfy your requiremnt to the maximum extent.
    Please check this and see if your requirement is fulfilled or not.
    Regards,
    Ankit
    Edited by: Ankit Patodi on Jan 12, 2011 11:55 AM

  • BAPI for updating infotype 0019 - Date Monitoring

    Hi,
    Does anyone know if there a BAPI for creating/updating infotype 0019 - Monitoring of Dates?
    Many thanks,
    Paul

    Hi Paul,
    1. HR_INFOTYPE_OPERATION
       This is the FM (for all infotypes, even 0019)
    2. If u want something like BAPI (RFC Enabled),
       what u can do is that
      create a new Z Fm,
      and call the FM
    HR_INFOTYPE_OPERATION
    in this.
    regards,
    amit m.

  • Retrieve Text in an Infotype Record

    Hi ,
    My query is with regards to Infotypes in SAP-HR.
    There is a provision of storing texts for individual records in an Infotype - for example in Infotype 30 (Powers of Attorney ). I need to retrieve this text for individual records for reporting purpose.
    How do we retrieve this text for individual records ?
    Thanks ,
    Sujata

    Hi Sujata,
    In order to get the text for any infotype field.
    The general approach is you fetch the data from the text table.
    To find out the text table, double click on the Data Element (for the field which u want to fetch the text).
    You will get Dictionary : Display Data element screen, double click on the DOMAIN name,another screen would come up, click the Value Range tab,
    You will have VALUE TABLE screen field, next to that u'll have the table name, click on the table name, the table fields would be displayed.
    Now click on GOTO-->Text Table,the text table would be displayed.
    hmm!!! i Guess this shd be helpful.
    let me knw if u need further clarificaton on this.
    Regards,
    krishna

  • ML85 - approval overwrites Reference text in all SES

    Hi,
    Why is the reference text is overwriting with the text from first SES to all SES approved in ML85 screen ?  For instance, in below screen, the pop-up appears only once with the text from first SES and when the approver goes ahead, it applies the text for all three SES approved in this session.  Ideally, looks like this pop-up should appear three times with header data from three SES in this case because three SES are involved.  Is this a bug ?
    Thanks,
    Sankar

    Hi Prasoon,
    Thanks for that note.  It perfectly explains the system design.  However I would call SAP's recommendation as workaround to manage product limitation, not the solution :).  Thanks again for your help.
    Cheers,
    Sankar

Maybe you are looking for