How to use F9CSO2 - SO Control: Field Groups

SAP Transaction Code - Details

• Transaction Code: F9CSO2

  Description: SO Control: Field Groups

  Release: S/4HANA and ECC 6

  Menu Path:

  • Accounting > Financial Supply Chain Management > In-House Cash > Environment > Development BDT > Standing Orders > Structure > Screen layout > Field Groups
  • Accounting > Bank Applications > Bank Customer Accounts > Environment > Development BDT > Standing Orders > Structure > Screen layout > Field Groups

• • Program: BUSVIEWS

    Screen: 1000

    Authorization Object:

  • Development Package: FKBSTOR

    Package Description: Bank Customer Accounts: Standing Order

    Parent Package: FS_BCA

  • Module/Component: IS-B-BCA

    Description: Bank Customer Accounts

Smart SAP Assistant

• SAP Tcode: F9CSO2 - SO Control: Field Groups

  
  Overview:
  The SAP transaction code F9CSO2 is used to control the field groups in Sales and Distribution (SD) documents. It allows users to define which fields are visible in the SD documents, and which fields are mandatory or optional. This helps to ensure that all relevant information is captured in the documents, and that the data is consistent across all documents. 
  
  Functionality: 
  The F9CSO2 transaction code allows users to define field groups for SD documents. These field groups can be used to control which fields are visible in the document, as well as which fields are mandatory or optional. This helps to ensure that all relevant information is captured in the documents, and that the data is consistent across all documents. Additionally, users can also define default values for certain fields, which can be used to speed up data entry. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code F9CSO2 into the command field. 
  2. Select the field group you want to edit from the list of available field groups. 
  3. Select the fields you want to make visible, mandatory or optional in the document. 
  4. If desired, enter default values for certain fields. 
  5. Save your changes and exit the transaction code. 
  
  Other Recommendations: 
  It is important to note that changes made using this transaction code will only take effect after a system restart. Additionally, it is recommended that users test any changes made using this transaction code before implementing them in a production environment.