Skip to Content
Technical Articles
Author's profile photo Malika Bathla

Long text CDF in MDUG and Reporting – Known issues and Solutions

This blog post will target the solution for some of the known issues with long text custom fields when they are uploaded via MDUG tool or when they are displayed via report.

CDFs are custom-defined/user-defined fields which can be added on the application on top of existing standard fields if there is a need to have additional field which is not provided in standard set.

Based on the requirement, user can maintain HR or Non HR fields which can be configured as per configuration information provided in SPRO configurations under path-
Governance, Risk and Compliance->General Settings->User-Defined Fields.

As per note#1169555 – User-Defined Fields, CDF can be created.

After creation of subtype of long text CDF, CDF will be visible at front end and one will be able to save the data as well.
However, some or all activities which are mentioned below may not work as required which are the known issues of Long Text CDF:

  • Upload CDF value from MDUG
  • Sync between central and local field.
  • Customization of CDF.
  • Display CDF in report through ‘Personalization’.

Follow following steps to make them work as well.

Step1: Generate subtype for long text CDF

For this document I have created long text CDF for central control and local control:
Subtype =
Subtype Text = Additional Information (This will be used as field Label)


  • Sub type should be same as field name for long text CDF fields which we will see below while making field related configuration.
  • Same subtype can be assigned to other object types. For example: Local Control and central control can have same subtype, if there is a requirement to share same field.

Step 2:  Configuring CDF – Standard and long text fields

  1.  Addition of CDF in database table GRFNFLD using view GRFNV_FLD via “SM30” transaction code.


    Insert Custom field ID in table GRFNFLD

    • Click ‘New Entries’.
    • Field ID = Subtype ID that was created in Step 1.
    • Description = Same description that was created in Step 1.
    • Field Cat = HR Field because ZCTL is being created as HR field. For non-HR field/normal field, this can be selected as DB Field or Normal Field.
    • Field Type = GRFN_LONG_TEXT for the long text CDF and for other CDFs, field type can be selected same as the data element created for them.
    • Multi Lang = Mark ‘X’ if there is a requirement to upload this field in multiple languages.
  2. Mark this field customizable in database table GRFNFLDLCHG by adding fields in this table using view GRFNV_FLDLCHG via “SM30” transaction code.


    Mark the field customizable in table GRFNFLDLCHG

    • Click ’New Entries’.
    • Field ID = Subtype ID
    • Press Enter, it will fill the description automatically.
    • Checkmark the ‘Customize’ so that this field can be customized to allow local change.
    • Press enter and save.
  3.  Relate this field to the entity to which it belongs by adding this field in database table GRFNENTFLD using view GRFNV_ENTFLD via “SM30” transaction code.


    Insert entry in database table GRFNENTFLD to create field to entity relationship

    • Click ‘New Entries’.
    • Entity ID = Entity for which CDF is created.
    • Field ID = Subtype ID.
    • Data Part = ‘DATA’.
    • Position = Where CDF needs to be positioned at the entity screen.
    • Is Key = If this CDF should be a key.
  4. Add the fields in database table GRFNFLDLCHGC using view GRFNV_FLDLCHGC via “SM30” transaction code.


    Insert entry in table GRFNFLDLCHGC

    • Click ‘New Entries’.
    • Field ID = Subtype ID.
    • Local Change Allowed = ‘ ’ if the requirement is to sync changes of central with local else it will be ‘X’.
  5. Add the attributes of fields in GRFNFLDHR using view GRFNV_FLDHR via “SM30” transaction code.


    Insert field attributes in GRFNFLDHR

    • Position the CDF using ‘Position’ button.
    • Field ID = Subtype ID
    • Provide IT = 1002.
    • Provide STy. = Subtype created in Step 1.
    • Field Name = For long text CDF, it should be ‘DESCR’ and for others it can be as required or field label.

Step 3: Maintain Field-Based Configuration

  1. Make entry in database table GRFNAPPFLD through view GRFNV_APPFLD via transaction SM30.


    Maintain field configuration with application component

    • Click ‘New Entries’ and create entry as follows:Entity ID = Entity for which CDF is created.
      Field ID = Subtype ID created in Step 1.
      Component = GRC/GRC-PC/GRC-AC/GRC-RM as per the requirement
      Status = Default status that needs to be set out of – Optional/ Required/Display/Hidden
      Customize = If this field should be allowed to be customized.
    • Press Enter and Save.
  2. To make field-based configuration, go to SPRO transaction and do the following in ‘Maintain Field-Based Configuration’:
    • Click ‘Choose Entity’ at left panel and position the entity for which CDF is created and select that line item.
    • Select ‘Field Status Configuration by Appl. Component’ from left side panel to make application component related change. Click ‘New Entries’ and search for your field ID through F4 help.
      Note that only those field IDs which are marked ‘Customize’ as in above step will be available here.
    • Press Enter and Save.


Now you will be able to upload long text CDF from MDUG tool and display the same in report as well.
Moreover, you will be able to sync central CDF with local CDF from front end via master data.


I would love to hear your thoughts, questions, and feedback. Feel free to do so !

Malika Bathla.

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.