How to use BUCN - BP Cust: Field Grps f. Authorization

SAP Transaction Code - Details

• Transaction Code: BUCN

  Description: BP Cust: Field Grps f. Authorization

  Release: S/4HANA and ECC 6

• • Program: BUSVIEWS

    Screen: 1000

    Authorization Object:

  • Development Package: BUPA

    Package Description: SAP Business Partner

    Parent Package: ABA_AP

  • Module/Component: AP-MD-BP

    Description: SAP Business Partner

Smart SAP Assistant

• SAP Tcode: BUCN - BP Cust: Field Grps f. Authorization

  
  Overview: 
  The SAP transaction code BUCN is used to manage field groups for authorization in the Business Partner (BP) Customer component. This code allows users to assign authorization fields to a field group, which can then be used to control access to certain BP customer data. 
  
  Functionality: 
  The BUCN transaction code allows users to create, change, and delete field groups for authorization in the BP Customer component. It also allows users to assign authorization fields to a field group, which can then be used to control access to certain BP customer data. Additionally, users can view the authorization fields assigned to a field group and view the authorization objects assigned to a field group. 
  
  Step-by-step How To Use 
  1. Enter the BUCN transaction code into the SAP command field. 
  2. Select the “Create” option from the menu bar. 
  3. Enter a name for the new field group and select “Save”. 
  4. Select the “Assign Authorization Fields” option from the menu bar. 
  5. Select the authorization fields that you want to assign to the field group and select “Save”. 
  6. Select the “View Authorization Objects” option from the menu bar. 
  7. Select an authorization object from the list and select “Save”. 
  8. Select “Activate” from the menu bar to activate the field group for use in BP Customer authorization checks. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with SAP authorization concepts before using this transaction code, as it is important to understand how authorization works in order to properly use this code. Additionally, it is recommended that users test their changes in a non-production environment before making any changes in production systems.