How to use OKYK - Types de CCR - Seiban

SAP Transaction Code - Details

• Transaction Code: OKYK

  Description: Types de CCR - Seiban

  Release: S/4HANA and ECC 6

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: CKJ1

    Package Description: Customizing for Product Costing

    Parent Package: APPL

  • Module/Component: CO-PC-PCP

    Description: Product Cost Planning

Smart SAP Assistant

• SAP Tcode: OKYK - Types de CCR - Seiban

  
  Overview:
  The SAP transaction code OKYK is used to maintain costing types for Seiban. It allows users to define and maintain the costing types used in the Seiban system. This transaction code is part of the Logistics-General module in the SAP ERP system. 
  
  Functionality: 
  OKYK enables users to define and maintain costing types for Seiban. This includes setting up the costing type, assigning it to a company code, and defining the cost elements associated with it. Additionally, users can also view and edit existing costing types, as well as delete them if necessary. 
  
  Step-by-step How to Use: 
  1. Enter transaction code OKYK in the command field. 
  2. Select “Create” from the menu bar. 
  3. Enter the costing type name and description in the corresponding fields. 
  4. Assign the costing type to a company code by selecting it from the drop-down list. 
  5. Define the cost elements associated with this costing type by selecting them from the list of available cost elements. 
  6. Save your changes by clicking on “Save” in the menu bar. 
  7. To view or edit an existing costing type, select it from the list of available costing types and make your changes as necessary. 
  8. To delete a costing type, select it from the list of available costing types and click on “Delete” in the menu bar. 
  
  Other Recommendations: 
  It is important to note that only users with appropriate authorization can access this transaction code and make changes to existing costing types or create new ones. Additionally, users should be aware that any changes made to existing costing types may have an impact on other areas of the system, so it is important to ensure that all changes are thoroughly tested before they are implemented in production environments.