CMS_CUS_RE_BDT_104 - Cust SGG-RE : configuration dynpro

SAP Transaction Code - Details

• Transaction Code: CMS_CUS_RE_BDT_104

  Description: Cust SGG-RE : configuration dynpro

  Release: S/4HANA and ECC 6

  Menu Path:

  • Accounting > Bank Applications > Collateral Management > Environment > Real Estate BDT Development > Structure > Screen Configuration

• • Program: BUSVIEWS

    Screen: 1000

    Authorization Object:

  • Development Package: CMS_RE

    Package Description: Collateral Management System: Real Esate

    Parent Package: FS_CMS

  • Module/Component: FS-CMS-MD-RE

    Description: Real Estate

Smart SAP Assistant

• SAP Tcode: CMS_CUS_RE_BDT_104 - Cust SGG-RE : configuration dynpro

  
  Overview: 
  CMS_CUS_RE_BDT_104 is a SAP transaction code used to configure the customer screen in the Real Estate (RE) module. It is used to customize the customer screen for the RE module, allowing users to tailor the screen to their specific needs. 
  
  Functionality: 
  This transaction code allows users to customize the customer screen in the RE module. It enables users to add, delete, or modify fields on the customer screen, as well as set up default values for certain fields. Additionally, it allows users to define which fields are mandatory and which are optional. 
  
  Step-by-step How to Use: 
  1. Enter CMS_CUS_RE_BDT_104 into the SAP command field and press enter. 
  2. Select the “Screen Configuration” tab. 
  3. Select the “Fields” tab and select the field you wish to modify or add. 
  4. Make any desired changes and click “Save” when finished. 
  5. Repeat steps 3 and 4 for any additional fields you wish to modify or add. 
  6. When finished, click “Back” to return to the main screen configuration page. 
  7. Click “Save” to save your changes and exit the transaction code. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all of the available fields before making any changes in order to ensure that they are making the desired modifications correctly. Additionally, it is recommended that users test their changes in a test environment before applying them in a production environment in order to avoid any potential issues or errors.