Show TOC

Function documentationCopy Planning Version

 

You can use the Copy Planning Version transaction (/SAPAPO/VERCOP) to completely or partly adopt the data of one planning version in another. The program copies data from one planning version to another one within a model.

The program supports parallel processing. If you use parallel processing, the program performs different tasks not one after the other but simultaneously. With parallel processing, you can usually improve performance considerably when copying the planning version. However, due to the greater number of tasks to be performed in parallel, the load on the system is likely to be higher.

The Copy Planning Version transaction allows you to specify the scope of the data you want the system to copy. The performance of the transaction is improved in the following ways:

  • Improved parallel processing logic that results in better runtime

  • Partial copy option for copying master data and transactional data

To benefit from the enhanced performance of the Copy Planning Version transaction, you must activate the business function SCM-APO, Version Simulation (SCM_APO_VERSION_SIM). For more information, see SCM-APO, Version Simulation.

Prerequisites

If you want to make use of the parallel processing option, you must have created a parallel processing profile in Customizing, under Start of the navigation path Advanced Planning and Optimization Next navigation step Master Data Next navigation step Model and Version Management Next navigation step Create Parallel Processing Profile for Planning Version Copy End of the navigation path.

To use the partial planning version copy function, you must activate the business function SCM-APO, Version Simulation (SCM_APO_VERSION_SIM). For more information, see SCM-APO, Version Simulation.

If you have activated the business function SCM-APO, Version Simulation (SCM_APO_VERSION_SIM), and you want to run the transaction in background processing mode, make sure that you enter the report /SAPAPO/VERSION_COPY_RESTR. The report /SAPAPO/VERSION_COPY_PAR only works if the business function is inactive.

Features

If you copy master data, the version-specific master data in the target version is created as follows:

  • Based on the version-specific master data of the source version, if it exists, and if the source version is not the active version

  • Based on the version-independent (model-specific) master data, if the source version is the active version

The system always copies all resource master data from the source version to the target version.

Note Note

If you copy from the active (000) version, depending on the master data object you copy, the system copies the data from model 000, or from the model and version-independent data (in some types of master data, this means the master data entries from the 000 version).

End of the note.
Copy Modes

The program can operate in two modes:

  • Full

    If you choose this option, the system copies version-dependent master data resulting in new version-dependent entries for all master data elements, all orders, and all SNP and DP time series.

  • Partial

    If you choose this option, the system provides you with several options to specify exactly what kind of data you want to copy.

Partial Copy

If you choose the partial copy option, you can specify the scope of the copy in the following tab pages:

  • Location Product Selection

    You can define the range of location products by the following criteria:

    • Location Product

      You provide the range of location products to be copied explicitly, by entering either the location, the product, the planner, and so on. In the Selection Extension field, the system provides the option of extending the selection to include related location products.

    • Transportation Lane

      The system selects location products that are transported on the set of transportation lanes you specify.

    • Production Resource

      The system selects location products with production activities on the set of production resources you specify.

    • SNP Selection Profile, and CTM Master Data Profile

      The system reuses selection profiles you defined in Supply Network Planning (SNP) interactive planning, and Capable-to-Match (CTM) to determine the range of location products to be copied.

  • Master Data Objects

    On this tab page, you can choose for each master data object type to copy all or none of the master data objects. You can also choose to apply the location product selection, except in the case of locations. The system interprets the location product selection as follows:

    • Location products

      The system copies only the location products included in the selection.

    • PPMs and PDSs created by Supply Network Planning (SNP), Capable-to-Match (CTM), or Production Planning and Detailed Scheduling (PP/DS)

      The system copies only the PPMs and PDSs that contain any of the selected location products as main output component.

      Note Note

      If, on the Location Product Selection tab page, you have specified production resource as the basis of location product selection, the result might be a wider set of PPMs and PDSs than your original selection.

      End of the note.
    • Transportation lanes

      The system copies only the transportation lanes that can be used for transporting any of the selected products to any of the selected locations.

      Note Note

      If, on the Location Product Selection tab page, you have specified transportation lane as the basis of location product selection, the result might be a wider set of transportation lanes than your original selection.

      End of the note.
    • Quota arrangements

      The system copies only the quota arrangements that apply to any of the selected location products.

  • Transactional Data

    On this tab page, you can specify the transactional data you want the system to copy. You can choose from the following options:

    • For SNP and DP time series, you must specify a list of planning areas. The system applies the location product selection to SNP time series. It copies only the time series that are related to the selected location products.

    • For order data and stock, you can specify the Available-to-Promise (ATP) categories and the horizon. The system copies only the orders that have at least one element with the given ATP category within the given horizon.

    • For project order, you can specify the numbers of orders to be copied.

    • For Maintenance and Service Planning (MSP), maintenance, and transport orders you can specify whether or not you want them to be copied.

Test Mode

In test mode the system does not make any changes to the target version. In other words, the system does not delete or create the target version, and does not copy any data. The system only simulates the copy of master data and writes and displays the detailed log. The system does not simulate the copy of transactional data.

Parallel Processing

If you use parallel processing, the system copies most of the master data, time series, and orders in parallel to each other. Parallel processing allows the application server to connect to the database server and the SAP liveCache server in parallel, and insert entries into more database tables at the same time, which improves performance.

Application Log

The system creates a detailed application log that displays a list of the master data objects that were copied. To create the detailed log, select the Detailed Results checkbox in the Application Log screen area. You can also specify that you want the system to display the detailed log immediately after the planning version copy has finished, by selecting the Display Log Immediately checkbox.

Business Add-Ins (BAdIs)

To prevent inconsistencies arising from transfers by the APO Core Interface (CIF) that take place in parallel to the copying of the active planning version, two Business Add-Ins (BAdIs) are available:

  • BAdI: Deactivate CIF Before Copying Planning Version (/SAPAPO/MVM_COPY1)

  • BAdI: Activate CIF After Copying Planning Version (/SAPAPO/MVM_COPY2)

You can modify the possibilities of extending the location product selection by implementing the BAdI BAdI: Location Product Extension (/SAPAPO/MVM_COPY_EXTEND).

You find the BAdIs in Customizing, under Start of the navigation path Advanced Planning and Optimization Next navigation step Master Data Next navigation step Model and Version Management Next navigation step Business Add-Ins for Planning Version Copy End of the navigation path.

Activities

  1. To access the Copy Planning Version transaction, on the SAP Easy Access screen, choose Start of the navigation path Advanced Planning and Optimization Next navigation step Master Data Next navigation step Planning Version Management Next navigation step Copy Planning Version End of the navigation path.

  2. In the Source Version field, enter the planning version whose data you want to copy.

  3. In the Target Version field, enter the planning version to which you want to copy the data.

    If a planning version with this name already exists, its data is overwritten with the data of the source version. The name and the GUID of the planning version are retained so that you can continue to use it in variants and profiles.

    If no planning version of this name exists yet, the system creates it automatically.

  4. To use parallel processing, specify a parallel processing profile under Profile.

  5. Define the scope of copying.

    You can choose between the full copy and partial copy options.

  6. If you choose the partial copy option, you must specify the criteria based on which you want the system to copy the planning versions.

Example

You want to optimize your planning by changing the data of your active planning version. Before making these changes to the active planning version, you simulate a planning run. To do so, copy the data of the active planning version into a new planning version. You change the data of this planning version and execute simulation runs. Where appropriate, adopt the optimized data in the active planning version.