Ansicht
Dokumentation

Route ( RELNISU_472_WA_ROUTE )" /> Route ( RELNISU_472_WA_ROUTE )" />

Enhancement for Route ( RELNISU_472_WA_ROUTE )

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Short text

Enhancement for Route

Use

As of SAP Utilities Release 4.72, new functions are now available within the route master data object. These functions improve the inclusion of the route and subsequent processes in SAP standard components. The following enhancements exist:

• General Status Management

Up until now you have been able to create, change or display a route in the system. You can now also use the general status management to delete routes. You need to delete routes if they become obsolete, due to grouping or similar processes, and are no longer to appear in the system. In particular, it must be possible to restrict or completely prevent the option of allocating further waste disposal orders or services to these routes.

The general status management makes various statuses available to restrict the use of the route, or to make the route only permissible for certain processes. The statuses are provided by SAP, and cannot be changed or enhanced.

From now on, the status of the route is displayed in the maintenance screen for the route. There, you can also change the status of the route (for example, you can set the status to inactive, or can set a deletion flag).

• Location and Account Assignment

From now on, you can assign location and account assignment data to the route. This has the following effects on the subsequent processes:

• The location and maintenance plant fields describe the organizational assignment of the route. You can use these fields to select waste disposal orders (when creating, planning, confirming, or deleting routes). In the waste disposal industry the 'location' and 'maintenance plant' fields can often be equated with the depot.

• The delivering plant and storage location fields describe the location at which the route delivers or removes containers that are intended for container transport.

• The waste disposal facility describes the location at which the collected waste is disposed of. Here, you must differentiate between whether the logistic component or the enhanced logistic component is to be used. If you use the enhanced logistic, the waste disposal facility object is available, and can be entered here. In addition, you should only use the plant and storage location fields for defining the waste disposal facility. This location data is used as the destination for a subsequent material posting using weighing record creation within the confirmation.
  
  

All this location data is transferred as default values to the waste disposal order. There, it can be changed during the planning or confirmation.

• You can use the account assignment data to allocate the route to organizational areas within your company that are relevant to account assignment. These allocations are effective during the CO account assignment for waste disposal orders. Here, you can decide whether the waste disposal order costs are grouped at route level (header record for waste disposal order) or at order item level (item record for waste disposal order). You use the Cost Collector for Waste Disposal Order field in the route to control this. In addition you can, during the account assignment at route level, distinguish which account assignment object is to be used. The cost center, standing order and billing order objects are available.

• Route Archiving

For information on route archiving, see the release information Connecting the Route and Waste Disposal Order Objects to the Archiving Workbench.

• Waste Disposal Calendar

You can now enter a specific appointment postponement in the waste disposal calendar (transaction EWACAL) and, when maintaining non-workdays, directly in the route. This removes the restriction that meant that the postponement of non-workdays was restricted.

In the future it will no longer be possible to enter a correction indicator for the postponement of a non-workday.

• Modifying dependent services when changing the service frequency for a route

It is now possible, when changing the service frequency for a route, to modify dependent services (services in which the route is entered as the productive route). You can use the BAdI ISU_WA_ADAPT_SERVICE for this purpose.

Effects on Existing Data

To integrate existing routes in the general status management, an initial status must be assigned for each route. The ISU_XPRA_ROUTE_STATUS_CREATE XPRA is used for assigning the initial status. For further information, see the XPRA documentation and the documentation for the report ISU_XPRA_ROUTE_STATUS_CREATE.

Use the report REWA_ROUTE_DATES_CORRECT to modify existing waste disposal calendars and non-workday definitions for a route. This report converts the correction indicator for the non-workday to a specific date. For further information, see the documentation for the report.

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information

You can find further information on general status management in the online help.

Vendor Master (General Section)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 6669 Date: 20240603 Time: 163227     sap01-206 ( 120 ms )