Hierarchy
⤷ CA-MDG-APP-ISS (Application Component) Internal Self-Services
⤷ UISS_MDG_CONTENT (Package) Internal Self Services: MDG Content
IMG Activity
ID | ISS_FIN_DM | Data Modeling |
Transaction Code | S_SE5_45000051 | (empty) |
Created on | 20100318 | |
Customizing Attributes | ISS_FIN_DM | Data Modeling |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ISS_FIN_DM |
Use
In this Customizing activity you can change the data modeling settings in Customizing for Master Data Governance (MDG) that are required to facilitate Internal Self-Services (ISS) for Financials. This is required for master-data and account-posting self-services, as both use the MDG self-service process type (which is based on MDG technology).
Requirements
Standard settings
It is important to note that in a standard implementation of Internal Self-Services for Financials, changes are executed immeadiately in the connected backend system. Unlike in the standard MDG implementation, there is no replication of data.
The data model IS is included as part of the standard delivery of ISS for Financials. This data model contains a number of predefined entities and relationships that you can use directly or after some modification, for your own implementation.
Note: While it is techically possible to use your own data model, SAP recommends that you do not do so. SAP recommends that you use the delivered data model IS and modify it to suit your specific implementation. Alternatively, you can also copy the data model IS and use this copy as the basis of your own data model.
Activities
You need to consider the following activities if you change the delivered data model or are using your own data model:
- Edit Data Model
The data model required for Internal Self-Services for Financials is IS. All the necessary entity types are defined in this data model. For example, these can be a cost center or profit center structure.
When editing the data model (if you change the delivered data model, for example by adding a new entity type), or if you use your own data model you need to consider the following:
- Entity Types: If you add a new entity type, you need to select a usage type. There are four available for self-services:
- Changeable via Change Request: This is the most common setting. This is used for all MDG based self-services.
- Changeable without Change Request
- Cannot be changed by MDG: There are no generated tables
- Changeable via Other Entity Type
- The editions are not used by self-services. Here, you select No Edition.
- Entity Type Attributes: For each entity type, a set of entity type attributes is defined. An entity type is defined by these attributes. Each attribute is associated with a data element. These attributes control the available fields on the UI for entities that are defined as changeable via change request.
- Entity Type Relationships: The entity types are predefined for the data model IS. You only need to use this activity if are using a entirely new data model that is not a copy of the data model IS. You also need to use this Customizing activity if you add a new entity type. You can define the type of relationship that links each entity type (leading, referencing or qualifying) and the cardinality for each relationship.
- Reuse Active Area: You only need to use this customizing activity if you want to use an access class other than the one contained in the standard delivery. In most cases, you do not need to change this setting.
- This setting enables the direct update of the entity in the connected back-end system. This is defined at the data model level for Internal Self-Services for Financials. This means that you should not change this setting in a standard implementation. This setting ensures that the authorization to change an object using a self-service is defined in the backend of the connected application system. In other words, self-service users also need to be assigned the role for changing an object. This means that the self-service users need to have the correct authorizations for the object that is changed.
- For the standard implementation of Internal Self-Services for Financials, the reuse area is IS_PPACCESS and the access class is CL_UISS_PPADAPTER. This setting establishes the connection between MDG and the tables that are used for active data.
- Note: Before you can implement your access own class , you need to define it in the customizing activity Define Access and UI Handler Class. The access class customizing for MDG does not change. If you do make an entry in this table, the predefined classes delivered by SAP are no longer used. For more information see the Customizing activity document.
- Define Prefix for Temporary Keys
In some cases the posting key for the posting in the back-end system is only specified when the back-end system is updated. This is the case for account posting self-services; for example. The document number is only specified when the posting is executed in the back-end system. This is also the case for the internal order self-service, where SAP assumes that internal numbering is activated in the back-end system. In all of these cases a temporary key is generated. In this Customizing activity you need to define a prefix for these keys.
- Generate Data Model-Specific Structures
Once the data model has been configured for self-services, you need to generate the technical structure from the data model settings. This Customizing activity generates the structures that are used in the system coding. SAP delivers the structures generated by the data model IS by default. These are used in the Reuse Activity Area access class.
Thus, you only need to reuse this activity if you create a new or change an existing data model and need to create your own access handler classes to read data from the fields on your own UIs that are defined in the new or changed model. If this is the case, you can use this Customizing activity to generate structures that are based on your own model and are used in your own access classes.
- Define Authority for Data Model
In most cases, the authorization settings for the data model IS should not be changed. For the standard implementation of ISS for Financials, the authorization is defined by the reuse active area settings.
Note: For a standard implementation, IS_PPACCES is the reuse area and the checkbox MDG Auth is not selected. This ensures that the back-end authorizations are used instead of the MDG authorizations.
However, if you have defined your own data model you may need to use this Customizing activity to define the authorization settings for your data model. In this case, you can enter your own reuse area while ensuring that the MDG Auth checkbox is not selected. This ensures that the authorization logic is based on the back-end authorizations that are assigned to the user. For more information about roles and authorizations in ISS for Financials, see Customizing ISS for Financials Overview.
- For information about settings for derivation and validation, see:
Example
Business Attributes
ASAP Roadmap ID | 105 | Define functions and processes |
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 | ISS_FIN_DM | 0 | SE50000001 | Internal Self-Services |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20100913 |
SAP Release Created in | 605 |