Kontakt

Ansicht
Dokumentation

SAPMRSAU - Module Pool for Update Rule Maintenance

SAPMRSAU - Module Pool for Update Rule Maintenance

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

Description

Check

There are three types of check: One check that is performed during program execution and two checks that are started by user actions.

The LEDs are defined by the check during program execution. Error messages occurring in checks during user actions are either output directly or collected in the Application Log and displayed from there. A success message appears if there were no errors.

  1. Checks during program execution (set LEDs)
  • Green: Rule correct

  • Yellow: Rule inactive

  • Red: Rule incorrect

When you begin the update rules (screen 201), first the key figures and then the corresponding characteristics are checked. If you 'scroll' within the detailed maintenance screen (screen 210), all the key figures and characteristics are checked, as at startup.
  1. Checks by user actions (application log)
Check in the selection screen (screen 200): Database tables are checked here. Only the SAVED version is checked (see also Generation/Activation).
Check in the overview screen (screen 201): Internal tables are checked here (see also Generation/Activation). See also the Word document Check.doc about both issues.
  1. Checks by user actions (direct output of errors)
When you check rules within the detailed maintenance screen (screen 210), there is only a single check for the corresponding key figure and its characteristics. The order of the checks depends on which tab page is in the foreground.

Generation

Two versions are managed internally. The SAVED version is created when update rules are saved for the first time. The GENERATED version is stored as a copy of the SAVED version during generation/activation.

An update rule is always processed based on the SAVED version. This means that the SAVED version is loaded if it is called again and the SAVED version is saved during storage.

Revised rules are also stored in the SAVED version. If a revised rule is generated/activated, the old GENERATED version is deleted and created again as a copy of the SAVED version.

When can you perform a generation?

Generation is always permitted. However, if the generation status is 'generated' or 'revised', there is a prompt before a new generation.

What status combinations are there?

New Generated Revised
Inactive X X X
Active - X X

Generation includes storing (if necessary), checking only in connection with generating.

See also the Word document Generation.doc.

Activation/Deactivation

Only the #Updating Active# flag is set during activation. This flag is removed during deactivation.

When can you perform an activation?

Activation is always permitted. However, if the activation status is #Active#, there is a prompt before a new activation.

When can you perform a deactivation?

If the activation status is 'Inactive', deactivation is not possible. Otherwise deactivation is possible at any time.

Activation includes storing (if necessary), checking only in connection with generating (only if necessary; if generating, then also storing) and activating.

Units

Units belong to the characteristics. They are stored in database table RSUPDKEY. For greater clarity, however, units are maintained with the key figures (unit for key figure).

If a key figure has a unit, it must always be maintained. If there is a direct assignment between the source key figure and the target key figure, the proposed value from the communications structure is set for the target unit. You can change this value with the F4 help.

If a direct assignment is not possible, the target values remain initial. You can select values with the F4 help if they exist.

If the source and target units are not compatible, a warning message is output.

If the target key figure is changed, the target unit is also changed automatically. The target unit can then be changed again. Since the units are not compatible, a warning message is output.

Which combinations of unit are allowed?

Targ KF Fx Unit Targ Unit Srce KF Fx Unit Srce Unit
allowed K1 - HWAER K1 - HWAER
allowed K1 - HWAER K1 - BWAER
allowed K1 - HWAER K2 - BWAER/HWAER
not allowed K1 - HWAER K1 X -
not allowed K1 - HWAER K2 X -
conversion K1 X - K2 - BWAER/HWAER
conversion K1 X HWAER K1 - BWAER

The update with fixed units and the resulting conversions are not yet coded or finalized.

Routines

You must distinguish between key figure routines and characteristic routines. The basic principle is identical, but they are used differently in the subroutine.

General

When you create a routine, the global data definition is always stored (even if it is not used). When you create routines, the numbers are assigned one after the other.
When you save a routine, a syntax check is executed for this routine. The further processing is identical to the ABAP Editor.
The created routines are currently only valid for this combination of InfoCube/InfoSource.

Key figure routine

A key figure routine can only be created for a key figure. Only one routine can be created for each key figure. You can change this routine at any time.

Characteristic routine

You can create multiple routines for a characteristic. Select them using the F4 help. A characteristic routine can be copied. This means that at creation you are asked whether this routine should only be used for this key figure or whether it can be used for all key figures of this combination of InfoCube/InfoSource. You can only change this routine if it is used actively in the subroutine.

Global data definitions

Global tables

All the listed tables are tables without a header.
Only read access

Information about the InfoCube

g_t_cob_pro

Information about the InfoSource

g_t_csfieldtxt

Update rules

g_t_upddat, g_t_updkey, g_t_updinfo, g_t_updabap, g_t_updafml,

g_t_updafmlt

Internal tables

Update rules

g_t_dat, g_t_key, g_t_info, g_t_abap, g_t_afml, g_t_afmlt,

g_t_hlpkey -> Output table for screen 212

F4 help

Tables for FB HELP_VALUE_GET_FOR_TABLE

g_t_field_tab, g_t_value_tab

Screen editing

g_t_dvu

F4 help

g_t_ickyff4, g_t_f4csiobj, g_t_unityf4

Requirements

Output

Example






RFUMSV00 - Advance Return for Tax on Sales/Purchases   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 8159 Date: 20240520 Time: 104556     sap01-206 ( 105 ms )