SAP ABAP IMG Activity OKCM_TKCUM (Conversion to Release 4.0)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
KC (Package) Cost Accounting Controlling EIS

⤷

⤷

⤷

IMG Activity
ID | OKCM_TKCUM | Conversion to Release 4.0 |
Transaction Code | S_ALR_87000250 | IMG Activity: OKCM_TKCUM |
Created on | 19981222 | |
Customizing Attributes | OKCM_TKCUM | Conversion to Release 4.0 |
Customizing Activity | OKCM_TKCUM | Conversion to Release 4.0 |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OKCM_TKCUM |
The change to the fixed part of the Aspect structure for release 4.0 requires a conversion of the aspect tables.
Example
Requirements
You have created the necessary Versions.
Standard settings
Recommendation
Activities
Proceed as follows:
(The activity list can be found in the implementation guidelines in the menu path EIS -> Tools)
- In conversion table TKCUM set how the new fields plan / actual indicator and the version depending on the values of the fields value type and data area should be filled. Assign a combination of plan / actual indicator and version uniquely to each combination of value type and data area (will be checked). Please also remember to maintain the tables in all clients in which the aspect has data.
- Save the aspect structure in the aspect editing. The aspect now has the structure of Release 4.0 in the saved version. If the aspect contains data, you are informed that the aspect has been entered for the conversion for the mass processing.
- Using the database utility of the ABAP dictionary for the conversion of the aspect table, schedule a job in the background processing.
When converting the data, a copy of the original table is generated, the data in the original table is deleted, the original table in the ABAP dictionary is activated and the data reloaded from the copy. In reloading a conversion routine of EIS is run, that determines the values for the new fields independent of Customizing. The status of the conversion can be seen from the job overview and in detail from the object log of the database utilities. If errors should occur, you can restart the job after removing the cause. - After successful database conversion go back to the aspect editing and select the pushbutton 'Release upgrade', in order to convert the formulas for the aspect (for the data entry and for reports). Therefore, the new fixed characteristics are inserted in all places in which the value type occurs and provided with a variable or a fixed value depending on what value type was set. The fixed value is determined from the conversion table.
- Next generate the aspect environment.
Further notes
Business Attributes
ASAP Roadmap ID | 308 | Transfer Data to Live System |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OKCM_TKCUM | 0 | HLA0100255 | Extras |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
KCA0 | T - Individual transaction object | KCA0 | EIS2 | Edit aspect | ||
V_TKCUM | V - View | SM30 | 0000000000 | Maintenance of the conversion table 30 -> 40 | ||
V_TKCVS | V - View | SM30 | EIS2 | Maintain EIS versions |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |