Show TOC

 Delete Transaction Data

Use

You use the Delete Transaction Data function to delete transaction data that was planned in SAP APO from the SAP APO system and a connected SAP R/3 system. It is generally not recommended to use this function in the production system ; instead, you should use it for testing and correction purposes. Apart from a few exceptions, it is not necessary to run the function in the production system. For example, you do not need to run this function before an SNP heuristic run, SNP optimization run, or real-time deployment run because the system automatically deletes all orders from previous planning runs during these planning runs.

You can run the function in the production system under the following (exceptional) circumstances:

  • To delete deployment stock transfersafter a deployment run before you perform a new SNP run . Otherwise, the deployment stock transfers would not be modified during the SNP run. However, this only applies if you specified in Supply Network Planning Customizing that the deployment stock transfers are to be transferred to the SAP R/3 system as purchase requisitions (not purchase orders).

  • To periodically delete stock in transit quantities during the Vendor-Managed Inventory (VMI) process

You can use this function to delete data from the time series live Cache (by specifying planning areas, planning object structures, and key figures) and to delete orders from the order live Cache (by specifying ATP categories or order numbers, for example). Note, however, that you can only delete SNP orders (and not PP/DS orders).

To access the function from the SAP Easy Access menu, choose Start of the navigation path Supply Network Planning Next navigation step Environment Next navigation step Delete Transaction Data End of the navigation path .

Integration

You can also delete the data in SAP R/3 by using the APO Core Interface (CIF) to transfer the deletion activities to SAP R/3.

Features

  • This function provides four main data deletion options:

    • Delete data by key figures

      With the Select Objects By Key Figures option, you can delete data from both the time series live Cache and the order live Cache (by specifying key figures that contain time series or order data). However, time series key figures can only be deleted if they have been assigned with key figure semantic 001 or have not been assigned a key figure semantic.

      Choose a planning area and, if necessary, a planning object structure plus one or more key figures. If you only select a planning area and do not select any key figures, the system deletes all the key figure data from this planning area. However, you can significantly improve performance by specifying specific key figures.

    • Delete orders by ATP categories

      With the Select Objects By Categories option, you can delete orders from the order live Cache by choosing one or more ATP categories. However, note that you cannot delete all order types (see below).

    • Delete orders by order numbers

      With the Select Objects By Order Numbers option, you can delete orders from the order live Cache by choosing one or more order numbers. You can specify order numbers from both SAP APO and SAP R/3 for deletion.

    • Delete orders for a PPM

      If you wish to delete a PPM that still has orders assigned to it, you first have to delete the assigned orders. You use the Select Objects By PPM (All Planning Versions) option to delete all the orders for a specific PPM in all planning versions to which this PPM has been assigned.

  • You can significantly improve performance of the deletion report by specifying the products and locations whose data you want to delete. You can also improve performance by specifying a horizon for the data to be deleted.

    You can select specific products and locations by specifying the planner to which they are assigned.

    To further restrict the selection of location products, you can specify a consumption group. As a result, the system only deletes orders for location products that were assigned with this consumption group.

  • You can improve performance by specifying the number of orders and location products to be processed by the system at the same time. To do this, choose Performance and enter the package size. The default value if 100. You can increase this value if you are using a larger live Cache. However, you can only determine the optimum value by testing.

  • You can either delete data in SAP APO only or transfer the deletion activities to SAP R/3 using the Core Interface. To delete data in APO only, go to the Delete Transaction Data screen area and set the Only in APO indicator. To also delete data in R/3, set the In R/3 and APO indicator.

    Note that only deleting orders in SAP APO can result in inconsistencies if these orders are linked to orders in a SAP R/3 system.However, it can be advisable to only delete orders in SAP APO if you no longer want to plan orders in SAP APO and instead want to use SAP R/3 exclusively.

    Orders can only be deleted in SAP APO and SAP R/3 simultaneously in the active version 000 because CIF can only be used to transfer data for this version. Due to CIF limitations, you cannot delete orders from the following categories. You should delete these orders directly in the R/3 system:

    • AA - Process order (open)

    • AB - Process order (released)

    • AC - Production order (open)

    • AD - Production order (released)

    • BF - Purchase order delivery schedule line

    • BG - Purchase order returns item

    • BI - Stock transport order

    • BL - Customer quotation

    • BM - Sales order

Execution Mode

You can run the function in test mode, dialog mode, or as a background job:

  • Dialog mode or background job: The delete operation is run immediately or in the background. Choose (with quick info Execute ) or Start of the navigation path Program Next navigation step Execute in Background. End of the navigation path

    You can then view a log (see below) by choosing Log . If you run the report in dialog mode, the associated messages are also displayed in the status bar in the lower screen area.

  • Test mode: The delete operation is not run immediately; you are first shown a log of the data to be deleted. You can then check this data and decide whether you really want to delete or whether you want to cancel the process. If you choose Delete , the data is deleted. If you choose (with quick info Back ) , the data is not deleted.

    To activate test mode, set the Test Mode indicator.

Deletion Log

Depending on the execution mode chosen, the generated log contains information either about the data that has been deleted or that is to be deleted. The individual logs are displayed on the left-hand side of the screen, listed by creation date, time, and user.

The individual messages for each log are displayed on the right-hand side of the screen with creation date and time. You can display detailed information about the logs and messages.

The messages are displayed with the message type specification (termination message, error message, warning message, and information message). You can sort the messages by message type or in ascending or descending order. You can also set different filters; by message type or message text, for example.

The following standard messages are displayed:

  • Selection parameters chosen by the user

  • The number of key figures that were included

  • The number of location products that were included

  • The number of orders that were deleted for the selected planning version

  • The total number of deleted objects

  • A description of each deleted object showing the following information (choose with quickinfo Detail exists) :

    • Planning version

    • Product

    • Location

    • ATP category and category type

    • Order number

    • Quantity

    • The order date and time

You can also specify for how long the generated log is to be stored. To do this, go to the Delete Transaction Data screen and enter the number of days in the Log Availability field.