Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBAS (Package) FI-SL Customizing / integration / Basis
IMG Activity
| ID | SIMG_CFMENUGCU0GCM1 | Convert Tables |
| Transaction Code | S_ALR_87006213 | IMG Activity: SIMG_CFMENUGCU0GCM1 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUGCU0GCM1 | Convert tables |
| Customizing Activity | SIMG_CFMENUGCU0GCM1 | Convert Tables |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUGCU0GCM1 |
In this step, you can convert FI-SL pool tables to transparent tables. You access an overview of all pool tables used in the FI-SL system using the "Overview of pool tbl" function on the initial screen of the conversion.
The main advantages of conversion are as follows:
- Transparency of the FI-SL tables
The converted summary and line item tables can, for example, also be edited by external means.
- Table definition can be changed easily
Due to the structure of FI-SL object tables and tables with objects, it is very easy to make changes to the table definition (for example, entering a new key field). For the pool tables, this would require considerable effort.
- Master data check with the help of the object table
With the help of the object table that is assigned to each FI-SL summary table, you can validate the master data, for example, check the validity period of specific code combinations.
- The following table types should be converted in Release 3.0, if they have already been used since an earlier system release:
FI-SL summary tables of type 'pool'
FI-SL line item tables of type 'pool'
Since the names of these tables, as well as some field names have changed during the conversion of the summary and line item tables, all FI-SL control tables must be converted accordingly.
The summary tables GLT2 and GLTPC, as well as their dependent line item tables, MUST be converted in Release 3.0.
Actions
- Specify the source and the target table.
- Perform the preliminary measures.
- Carry out the conversion.
- Delete the sets and transaction data, if required.
Carry out the functions listed on this screen step by step. You will find more detailed information on the conversion under Additional Information for Release 3.0.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| 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 | SIMG_CFMENUGCU0GCM1 | 0 | HLA0009741 | Basic Functions |
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 |
| IMGDUMMY | D - Dummy object | GCM1 | 515 | Convert Tables |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
