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_CFMENUGCUOGCI3 | Maintain Table Directory |
| Transaction Code | S_ALR_87006437 | IMG Activity: SIMG_CFMENUGCUOGCI3 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUGCUOGCI3 | Maintain Table Directory |
| Customizing Activity | SIMG_CFMENUGCUOGCI3 | Maintain Table Directory |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUGCUOGCI3 |
In this step, you can call up a directory of all the tables used in the Special Purpose Ledger system and display or maintain these tables.
Caution
The table directory is updated automatically when you install an FI-SL table. You should only maintain it manually if absolutely necessary. In such cases, follow the directions under "Actions". Changes to the table directory will only be effective after the code in FI-SL had been regenerated.
Entries in the table directory containing errors will only be visible with the next release upgrade, since in this case the entire code in FI-SL is always regenerated.
Actions
- Enter the table name.
- Specify the table type (for example, summary table, line item table, external table).
- Specify the maximum number of periods.
- Specify whether the table is to be assigned to a global company or a company code.
- Define which currencies (transaction currency, second currency, third currency) or quantities are to be stored in the table.
- Specify the name of the corresponding table, if necessary.
The corresponding table completes the table entered. If for example, you have entered a summary table, you can only use a line item table as the corresponding table. Similarly, a line item table can only be completed by the summary table.
- If you create or maintain a summary table, you can specify the respective plan line item table, if necessary.
- If the FI-SL table is a table with object numbers and the variable key information is stored in an object table, specify the name of this object table.
- Specify whether line items are also to be written for the data records summarized using rollups.
If you have used the Report Writer to create a report in which rollup data records are used, you can only drill down to these records if line items have been written.
- Enter the name of the lock object that is assigned to the table. If you work with FI-SL planning or rollups, you must assign a lock object to each summary table in the ABAP/4 Dictionary.
The "Planning" and "Rollup" functions use the lock object to block the planned or rolled-up dataset while the program is running.
- Enter a program group.
You normally use program group 1. You should only use a different program group if you maintain a large number of tables.
- Deactivate the table, if required.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 3 | Nonrequired 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_CFMENUGCUOGCI3 | 0 | HLA0001336 | Table Definition and Installation |
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 |
| V_T800A | V - View | GCI3 | 9999999999 | Change FI-SL Table Directory |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
