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
Basic Data
| Data Element | UMS_CUST |
| Short Description | Ind.: Convert control tables |
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 | Cntrl tab. |
| Medium | 20 | Convert control tbl |
| Long | 30 | Convert control tables |
| Heading | 13 | Conv.ctrl tab |
Documentation
Definition
With this function, all FI-SL control tables are converted to the new summary table names.
This conversion includes almost all the FI-SL components and can take a long time. If you have defined a large number of sets and/or reports, you can expect processing to take a long time. When timed, it was found that the conversion of 1000 sets took approximately 8 minutes. The time required for the conversion depends on the definition and structure of your reports and sets and cannot therefore be predicted here.
After the conversion has been successfully completed, you receive a detailed log on the conversion process in the individual components. The log is either displayed as a dialog box (online execution) or is available as a list in the spool file (background processing). Analyze this log carefully and make any necessary corrections straight away.
Note: The sets and substitutions/validations/rules that are defined for table GLU1 are changed during the conversion of a summary table (for example, GLU1-BUKRS -> GLU1-RBUKRS). For this reason, you should make sure when using several summary tables that these tables are all converted in one go because otherwise inconsistencies could occur in the sets and substitutions/validations/rules for the fields for GLU1.
Another special feature occurs during the conversion of sets when fields are omitted or if 'Summarization of fields' is used (see field movements for the conversion): these sets no longer exist after the conversion and are therefore no longer available in higher-level multi-dimension sets.
After the conversion of the control tables, check whether the main functions in the individual FI-SL components still work. Checking reports, the diagnosis tool (posting test) and checking rollups are proven ways of checking the functionality.
Procedure if an error occurs
If the program that performs the conversion of the FI-SL control tables cancels processing for some reason, you can restart this program any time. The conversion then continues from where it was interrupted.
If after the conversion of the components, however, the errors that occurred during the conversion (for example, incorrect field movements for the conversion) prevent you from working with the 'new' system, you must access the available off-line database backup. In this case, you must repeat the entire conversion (at a later date).
History
| Last changed by/on | SAP | 19940827 |
| SAP Release Created in |
