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_CFMENUGCU0GCIN | Define Table Group |
| Transaction Code | S_ALR_87006422 | IMG Activity: SIMG_CFMENUGCU0GCIN |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUGCU0GCIN | Define Table Group |
| Customizing Activity | SIMG_CFMENUGCU0GCIN | Define Table Group |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUGCU0GCIN |
In this step, you can create table groups for the FI-SL system. You can define the variable dimensions for two object tables; the system automatically generates the tables assigned to these object tables. A summary table, an actual line item table and a plan line item table are generated (all tables contain the fixed dimensions such as "Ledger", "Fiscal year" or "Version").
This function prevents the redundant maintenance of object tables and their dependent tables. Only the object tables are maintained. The information needed for the summary and line item tables is derived from the object tables.
Caution
Cross-client objects are maintained when you use this function. Therefore, when you maintain these objects, all clients in the system are affected.
Actions
- Enter a name for the table group and choose "Create".
Table groups you create must begin with ZZ up to Release 3.0E. Beginning with Release 3.0F, the naming conventions for FI-SL table groups have been enhanced such that you can use table group names with the form Y..... and Z......
- Specify whether it is a local (company codes) or a global (global companies) table group.
- The standard setting only allows you to maintain one object table. If you want to work with a second object table, choose "Extras" -> "Use object 2".
If after an additional test you decide that you do not need the second object table, you can remove the table using the function "Extras" -> "Remove object 2".
- Specify which fields should be contained in the object tables of your table group.
When you create or maintain an object table, the corresponding summary, actual line item and/or plan line item tables are automatically created or updated. The automatically generated summary and line item tables contain the fixed fields such as "Fiscal year", "Ledger", "Version", and so on.
- Enter a data element for each field.
The fields "Type", "Length", "Check Table" and "Text" are automatically filled by the system when you enter the data element.
The "Copy field" function helps you search for existing data elements for a table field. You can search for data elements and fields from other systems (for example FI, CO).
If required, you can create data elements directly in the transaction. (Menu path: "Environment" -> "Data element" -> "Create".)
- If you want to create a sender field for a field in the summary, actual line item table and plan line item table, select the "S" field.
You should select this field when, for example, you want to store the sender information for an assessment or distribution in an allocation. If you want to perform a distribution between cost centers, for example, you can store the sender cost center in the data record.
- Using the function "Extras" -> "Tech.characteristics", you can check whether all currencies and quantities are needed in your table group. To save storage space, you should deselect the checkboxes for all currencies and quantities that you do not want to use.
In the "Maximum number of periods" field, enter the maximum number of period data fields. 16 periods (12 periods + 4 special periods) is the suggested default value. If, for example, you only want to have quarterly ledgers, enter a '4' in this field. If you want to use more than 16 periods, you should still enter 16 as the maximum number of periods.
The "Field length" field determines the length of the currency and quantity fields, depending on the figures (to be displayed). The field lengths 15 and 17 are permitted. Check the length of the maximum amounts and quantities that you expect. If you choose the smaller field length, you will once again save storage space.
- Maintain the indices for your table group.
It is very important that you define suitable indices for subsequent system performance. Please proceed cautiously here or ask your database consultant how to define efficient indices.
- If required, maintain additional fields for the summary table, actual line item table and/or the plan line item table. Use the pushbuttons on your screen to switch to the respective table.
- You can call up further information on table group maintenance under "Information".
- Save the table group. When saving, the system automatically performs a consistency check of the tables contained in your table group.
When you save the table group, a dialog box appears in which you are required to enter a development class. The development class enables you to install and transport the table group. (You should not define the table group as a "Local object".)
After you have saved, a dialog box appears in which you are asked whether the table group table should be activated. Click on "Yes" only when you want to permanently save your table group. Changes to active tables are often problematic since in some circumstances, manual conversions must be performed in the ABAP Dictionary.
After you have created your table group, you can directly install the group. The system calls up the same function as in the "Install Table With Object Table" step. You do not, however, need to enter a table name for the individual tables.
Note
In exceptional cases, it is possible to manually reprocess the tables in the table group from the inital screen of this transaction (Menu path: "Environment" -> "Reprocess in Repos.").
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | 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_CFMENUGCU0GCIN | 0 | HLA0001336 O HLA0001331 |
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 |
| DWBDUMMY | D - Dummy object | GCIN | 75 | Define FI-SL Table Groups |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
