Skip to Content
author's profile photo Former Member
Former Member

New added fields in ESS Address webdynpro application not getting saved in

Hello,

I have addeed extra fields in ESS Addreess iview like Relationship, COM01, TELN1 etc through webdynpro modification. Though the fields are fetching values from backend, while saving the values from portal after making any changes, the values are not getting saved in backend.

On debugging the function module for Modify which is getting called from the webdynpro application while saving, the folowing messages are displayed for the additional fields added.

Changes to field "Relationship", which is not designed for use, are deleted

Changes to field "COM01", which is not designed for use, are deleted

Do I need to perform any other configurations in backend for these extra fields added so that its values get saved.

Note that the fields are displayed properly under transaction PA30, Relationship Address.

Any suggestion what is missing.

Regards

Deb

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Mar 27, 2009 at 05:12 PM

    First, if you are getting the error message you listed below:

    Changes to field "Relationship", which is not designed for use, are deleted

    Changes to field "COM01", which is not designed for use, are deleted

    You need to add configuration for that country you are working with in T588MFPROPC. That error message is displayed because the fields are delivered in T588MFPROPS as being not used. You need entries to overwrite the delievered state of those fields.

    If you are adding in fields to the application that are a 1:1 mapping to the backend fields, you do not need to implement the UI BADI for moving data.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 22, 2009 at 10:32 PM

    Hi debasish,

    You need to implement BADI HRPAD00INFTYUI to enable this. Methods INPUT_CONVERSION and OUTPUT_CONVERSION should be implemented.

    Hope this helps.

    Rgds

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 10, 2015 at 04:55 PM

    The topic is obsolete, but maybe my solve will be useful. In "INPUT" (from screen to infotype) we have to do reverse operation than in "OUTPUT" (from infotype to screen).

    METHOD if_hrpa_ui_convert_standard~input_conversion.
    
      FIELD-SYMBOLS <p0006>      TYPE p0006.
      FIELD-SYMBOLS <r0006>      TYPE hcmt_bsp_pa_nz_r0006.
    
       CASE screen_structure_name.
    
        WHEN 'HCMT_BSP_PA_PREF'.
          MOVE-CORRESPONDING screen_structure TO pref.
       
       WHEN 'HCMT_BSP_PA_NZ_R0006'.
          ASSIGN pnnnn               TO <p0006>.
          ASSIGN screen_structure    TO <r0006>.
    
          MOVE-CORRESPONDING <r0006> TO <p0006>.
    
          MOVE <r0006>-TELN1 to <p0006>-NUM01. "" TELN1 is additional field in CI_NZ_0006 structure, NUM01 is field from IT0006
    
         WHEN OTHERS.
                MOVE-CORRESPONDING screen_structure TO pnnnn.
                IF pnnnn2 IS REQUESTED.
                      MOVE-CORRESPONDING screen_structure TO pnnnn2.
               ENDIF.
    
      ENDCASE.
    
    ENDMETHOD.
    

    Best regards

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.