Ansicht
Dokumentation

/MRSS/CUP_DEMAND_ASSIGNMENT - Deletion of Demands and Related Assignments

ROGBILLS - Synchronize billing plans RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.

Purpose

You use this report to delete demands and the assignments that are related to these demands in SAP Multiresource Scheduling.

If you want to delete resources in SAP Multiresource Scheduling, you must execute this report first in order to delete all assignments that exist for the resources to be deleted.

Integration

Prerequisites

Before you can delete demands and assignments in SAP Multiresource Scheduling, make sure that the following requirements are met:

You are authorized to delete data in SAP Multiresource Scheduling (authorization object/MRSS/CUP).

The following Customizing settings are in place:

A residence time for demands and assignments has been defined under Basic Settings → Define Residence Time for Deletion Objects.

If you want to store a log file, log profiles for deletion have been created under Basic Settings → Define Logging.

You have archived the underlying orders (notifications, roles) in the source system of the demand using the following archiving classes:

PM_ORDER for PM/CS orders

PM_QMEL for PM/CS notifications

CRM_SERORD for CRM service orders

CPROJECTS for cProject roles

Features

You can delete demands (and all related assignments) of the following demand types:

PM/CS orders

PM/CS notifications

CRM service orders

cPro roles

Note:
To delete demands that are based on PS networks or RM Web requests, you use archiving class PS_PROJECTS in the source system of the demand. Once you have archived the relevant PS network or Web request in the source system, all data related to the demand is deleted in SAP Multiresource Scheduling.

Selection

To select the data to be deleted, you have the following options:

Enter a desired deletion end date. The system compares the entered date with the earliest possible deletion end date. To determine this date, the system does the following:

The system compares the residence times for demands and for assignments and chooses the residence time that has the larger number of days.
The system determines the current date based on the global time zone and subtracts one day from this date.
The system subtracts the residence time in days (determined in step a) from the previously determined date (step b) and subtracts one day. This date is the earliest possible deletion end date.
The system compares the desired deletion end date with the earliest possible deletion end date.

If the date you entered is before or equal to the earliest possible deletion end date, the system considers the date you entered. If the date you entered is after the earliest possible deletion end date, the system considers the earliest possible deletion end date.

Note that the date you enter is considered to be in the global time zone that is defined in Customizing for SAP Multiresource Scheduling under Basic Settings --> Configure Basic Settings. If no global time zone has been defined, the date is considered to be in the system time zone.

You can specify the package size, that is, the number of demands that the system is to delete simultaneously.

You can specify whether or not you want to run the report in production mode. If you deselect the checkbox, the system executes the report in simulation mode.

You can specify whether or not you want to store a log file.

Note that you have to enter an appropriate logging profile when you select this checkbox.

You can specify whether or not you want to display the log after running the report.

Note that this checkbox must be deselected if you want to run the report in batch mode.

Standard Variants

Output

Activities

You can access this report by using transaction/MRSS/DELETE_DEMAND.

Example

BAL Application Log Documentation General Material Data
This documentation is copyright by SAP AG.

Length: 5239 Date: 20240419 Time: 172110 sap01-206 ( 73 ms )

Ansicht Dokumentation