How to use MCKI - Selection version tree: Purchasing

SAP Transaction Code - Details

• Transaction Code: MCKI

  Description: Selection version tree: Purchasing

  Release: S/4HANA and ECC 6

  Menu Path:

  • Logistics > Materials Management > Purchasing > Purchase Order > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Materials Management > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Materials Management > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Logistics Execution > JIT Outbound > Environment > Purchasing > Purchase Order > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Logistics Execution > JIT Outbound > Environment > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Logistics Execution > JIT Outbound > Environment > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Logistics Execution > JIT Inbound > Environment > Purchasing > Purchase Order > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Logistics Execution > JIT Inbound > Environment > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Logistics Execution > JIT Inbound > Environment > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Production > Kanban > Environment > Purchasing > Purchase Order > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Production > Kanban > Environment > Purchasing > Outline Agreement > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Production > Kanban > Environment > Purchasing > RFQ/Quotation > Request for Quotation > Reporting > Purchasing Information System > Standard Analyses > Selection Version > General Overview
  • Logistics > Production > Kanban > Environment > Warehouse Management > Environment > Rough workload estimate > Logistics Information System > Standard Analyses > Purchasing > Selection Version > General Overview
  • Logistics > Logistics Controlling > Logistics Information System > Standard Analyses > Purchasing > Selection Version > General Overview
  • Logistics > Logistics Controlling > Purchasing Information System > Standard Analyses > Selection Version > General Overview

• • Program: RMCSSLVS

    Screen: 1000

    Authorization Object:

  • Development Package: MCR

    Package Description: R/3 application development: Logistics Info Sys. (Reporting)

    Parent Package: APPL

  • Module/Component: LO-LIS-REP

    Description: Reporting

Smart SAP Assistant

• SAP Tcode: MCKI - Selection version tree: Purchasing

  
  Overview:
  The SAP transaction code MCKI is used to select a version tree in the Purchasing module. It is used to create and maintain version trees for purchasing documents. 
  
  Functionality: 
  The MCKI transaction code allows users to create and maintain version trees for purchasing documents. This includes creating new versions, copying existing versions, and deleting versions. It also allows users to assign a version tree to a purchasing document, and to view the version tree of a purchasing document. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code MCKI in the command field. 
  2. Select the “Create” option to create a new version tree. 
  3. Enter the name of the version tree and select “Save”. 
  4. Select the “Copy” option to copy an existing version tree. 
  5. Enter the name of the existing version tree and select “Save”. 
  6. Select the “Delete” option to delete an existing version tree. 
  7. Enter the name of the existing version tree and select “Delete”. 
  8. Select the “Assign” option to assign a version tree to a purchasing document. 
  9. Enter the name of the purchasing document and select “Save”. 
  10. Select the “View” option to view the version tree of a purchasing document. 
  11. Enter the name of the purchasing document and select “Display”. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all of the options available in this transaction code before using it, as it can be complex and time-consuming if used incorrectly or without proper knowledge of its functionality. Additionally, users should ensure that they have appropriate authorization before using this transaction code, as it can be used to make changes to important purchasing documents that could have significant impacts on business operations if not done correctly or without authorization.