CMS_CUS_OMS_BDT_007 - Pilotage SGG : événements

SAP Transaction Code - Details

• Transaction Code: CMS_CUS_OMS_BDT_007

  Description: Pilotage SGG : événements

  Release: S/4HANA and ECC 6

  Menu Path:

  • Accounting > Bank Applications > Collateral Management > Environment > Collateral Objects > CMS-Object Control > Events

• • Program: BUSVIEWS

    Screen: 1000

    Authorization Object:

  • Development Package: CMS_OMS_COMMON_UI

    Package Description: Objects in Coll.Management: User Interface Common Services

    Parent Package: FS_CMS

  • Module/Component: FS-CMS-MD

    Description: Master Data

Smart SAP Assistant

• SAP Tcode: CMS_CUS_OMS_BDT_007 - Pilotage SGG : événements

  
  Overview: 
  CMS_CUS_OMS_BDT_007 is a SAP transaction code used to control events in the Customer Order Management System (CMS). It is used to monitor and manage the events that occur in the system, such as order creation, order changes, and order cancellations. 
  
  Functionality: 
  This transaction code allows users to view and manage events in the CMS. It provides an overview of all events that have occurred in the system, including order creation, order changes, and order cancellations. It also allows users to view detailed information about each event, such as the date and time it occurred, the user who initiated it, and any associated messages. 
  
  Step-by-step How to Use: 
  1. Enter CMS_CUS_OMS_BDT_007 into the SAP command field. 
  2. The Events Overview: screen will appear. 
  3. Select an event from the list to view detailed information about it. 
  4. To view more detailed information about an event, select the “Details” button. 
  5. To view a list of all events that have occurred in the system, select the “List” button. 
  6. To filter the list of events by date or user, select the “Filter” button. 
  7. To delete an event from the list, select the “Delete” button. 
  8. To exit this transaction code, select the “Back” button or press F3 on your keyboard. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with this transaction code before using it in production environments. Additionally, users should be aware of any security restrictions that may be in place for this transaction code before using it in production environments.