Kontakt

Ansicht
Dokumentation

MPE_SAS_XPRA - Data Conversion Status and Action Schema

MPE_SAS_XPRA - Data Conversion Status and Action Schema

ROGBILLS - Synchronize billing plans   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

The status and action schemas predefined by SAP and customer-defined status and action schemas are not separated in several databases any more but are now stored in common databases.

This simplifies the application, increases performance during runtime, and improves the customizing, for example, by introducing the copy functionality.

Data conversion copies the status and action schemas from the old to the new tables.

Selection

The new tables are filled as follows:

  • Table MPE_SAS_SCHEMA contains all status and action schemas.
  • It is filled from MPE_SAS_S_SCHE and MPE_SAS_C_SCHE.

  • The corresponding language-dependent texts are stored in MPE_SAS_SCHEMA_T.

  • Table MPE_SAS_STATUS contains all statuses.
  • It is initially filled from MPE_SAS_S_STAT and MPE_SAS_C_STAT.

  • Categories of statuses are determined from MPE_SAS_S_ST_CAT and MPE_SAS_C_ST_CAT.

  • Status criticalities are determined from MPE_SAS_S_AS_STA and MPE_SAS_C_AS_STA.

  • The corresponding language-dependent texts are stored in MPE_SAS_STATUS

  • Table MPE_SAS_ACTION contains all actions.
  • It is filled from MPE_SAS_S_ACT and MPE_SAS_C_ACT.

  • The corresponding language-dependent texts are stored in MPE_SAS_ACTION_T.

  • Table MPE_SAS_AS_ACT contains the assignments of actions to status and action schemas.
  • It is filled from MPE_SAS_S_AS_ACT and MPE_SAS_C_AS_ACT.

Integration

Prerequisites

Features

Selection

Standard Variants

Output

Activities

Example






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

Length: 2444 Date: 20240531 Time: 114411     sap01-206 ( 27 ms )