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_CFMENUGCU0GCS1 | Maintain Integrated Master Data |
| Transaction Code | S_ALR_87006372 | IMG Activity: SIMG_CFMENUGCU0GCS1 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUGCU0GCS1 | Maintain integrated master data |
| Customizing Activity | SIMG_CFMENUGCU0GCS1 | Maintain Integrated Master Data |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUGCU0GCS1 |
The term integrated master data refers to all master data that has been created for FI-SL dimensions and other SAP application areas. In this step, you can define how the validation is to be carried out for the master data whose dimensions are affected by direct postings and other FI-SL functions.
Standard fields are validated when a table group is installed.
There are two types of validation:
- Normally, dimensions of other SAP application areas are validated against a master data table of the respective application area using exit routines or user exits.
- Otherwise, dimensions of the FI-SL system are validated against a FI-SL master data table.
Recommendation
You should check if a "1" (exit for period-independent values) is in the field "Additional information" for the field BUKRS or RBUKRS (company code) in the master data validation. Only then can the local currency be determined from the company code.
Note
The transactions "Enter FI-SL Document (local)" and "Enter FI-SL Document (global)" are always validated against table GLU1. Master data entries for table GLU1 must therefore exist in the master data table (T800D).
If the master data table only contains entries for your own FI-SL database table, master data validation will not take place when you enter local or global FI-SL documents.
If, for example, you add a new field "License plate number" (RCARNR) to your FI-SL table, the system validates this new field against the master data table. The entry GLU1 RCARNR must be maintained in the master data table.
Actions
Check and maintain the validation entries as required by entering either a FI-SL master data table or an exit number.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional 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_CFMENUGCU0GCS1 | 0 | HLA0001335 | Integrated Master Data |
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_T800D | V - View | GCS1 | 9999999999 | Change Integrated Master Data |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
