SAP ABAP Data Element WISP_REORG_TEST (Indicator: Test Run of Reorganization Program WISP_KEYS)
Hierarchy
☛ EA-RETAIL (Software Component) SAP Enterprise Extension Retail
   ⤷ LO-MAP (Application Component) Merchandise and Assortment Planning
     ⤷ WIS_PLANB (Package) Merchandise and Assortment Planning, Enterprise Add-On
Basic Data
Data Element WISP_REORG_TEST
Short Description Indicator: Test Run of Reorganization Program WISP_KEYS  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type XFELD    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Test Run 
Medium 15 Test Run 
Long 20 Test Run 
Heading 20 Test Run 
Documentation

Definition

If the indicator is set, the program performs a test run. The structure WISP_KEYS is analyzed and the current status is displayed in a log. The corresponding includes are not updated.

If the indicator is not set, the changes are carried out in the ABAP dictionary and the corresponding objects are created or activated.

Use

We recommend that you always perform a test run first. Analyze the log before you perform an update run of the program. Depending on which you select, a test or update run of the reorganization program is performed for either a comparison with information structures or a conversion of the structure WISP_KEYS. The log generated reflects the include structure of WISP_KEYS. It is saved as an application log under the object "WMAP"/ subobject "REORG". Using transactions SLG1 and SLG2 you can display and delete old logs. Select object "WMAP" and subobject "REORG" to process the logs for the application.

Dependencies

The structure WISP_KEYS contains characteristics and key figures and has information relevant for the planning processor from the Data Dictionary, including texts and foreign key relationships. This structure contains a large number of characteristics and key figures provided by SAP. It also contains prepared Customer Includes (beginning with CI), which include new characteristics and key figures. If you define your own characteristics and key figures, the structure WISP_KEYS is updated accordingly when you activate a scenario and the fields that have not yet been taken into consideration are generated in the includes provideded. The relevant information from the ABAP Dictionary is used by the information structures used in the planning scenario.

For structuring the large number of fields, WISP_KEYS has a hierarchical structure and is divided into several includes. Only the includes that are relevant for the reorganization report are displayed:
WISP_KEYS
|
|--> WISP_KEYS_SAP
| |
| |--> WISP_KEYS_SAP_M00
| |--> ...
| |--> WISP_KEYS_SAP_MCU
| |--> ...
|
|--> CI_WISP_KEYS
|--> WISP_DATF
|
|--> WISP_DATF_SAP
| |
| |--> WISP_DATF_SAP_K40
| |--> WISP_DATF_SAP_KCU
| |--> ...
|--> SI_WISP_DATF_ADDON
|--> CI_WISP_DATF

There is no obligatory customer namespace for defining your own characteristics and key figures. Nevertheless, when activating scenarios a distinction is made between the following:

  1. Characteristics that begin with ZZ or YY are generated in the include CI_WISP_KEYS .
  2. Key figures that begin with ZZ or YY are generated in the include CI_WISP_DATF .
  3. Characteristics that do not begin with ZZ or YY are generated in the include WISP_KEYS_SAP_MCU .
  4. Key figures that do not begin with ZZ or YY are generated in the include the Include WISP_DATF_SAP_KCU .

The following problems only arise in connection with the structure WISP_KEYS and with activating planning scenarios in Merchandise and Assortment Planning:

  • Changing an info structure:
    New characteristics and key figures are only included in the structure WISP_KEYS once when activating the corresponding planning scenario. If the information structures are then changed again (for example, a new foreign key table for characteristics that are used), the structure WISP_KEYS does not change. Even if you reactivate the planning scenario, no comparison takes place. In this case, perform a test run with the indicator Compare with Information Structure set. Analyze the log and then, if necessary, carry out an update run.
  • Release Upgrade:
    Customer includes, such as CI_WISP_KEYS and CI_WISP_DATF, are protected during release upgrades and remain unchanged. This is not the case for the includes WISP_KEYS_SAP_MCU and WISP_DATF_SAP_KCU. If you have defined your own characteristics and key figures that do not begin with YY or ZZ, convert these into the corresponding customer includes CI_WISP_KEYS and CI_WISP_DATF before the release update. Carry out a test run with the indicator Convert Structure set. Analyze the log and, if necessary, perform an update run afterwards.

Example

History
Last changed by/on SAP  20020219 
SAP Release Created in 110