SAP ABAP IMG Activity MIC_FOPCS_SHM_CUST (Activate Shared Objects Memory)

Hierarchy

☛ FINBASIS (Software Component) Fin. Basis
   ⤷ FIN-CGV-MIC (Application Component) Management of Internal Controls
     ⤷ FOPC_CUSTOMIZING (Package) Customizing

IMG Activity

ID	MIC_FOPCS_SHM_CUST	Activate Shared Objects Memory
Transaction Code	S_SE3_50000227	(empty)
Created on	20050308
Customizing Attributes	MIC_FOPCS_SHM_CUST	Activate Shared Objects Memory
Customizing Activity	MIC_FOPCS_SHM_CUST	Activate Shared Objects Memory

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	MIC_FOPCS_SHM_CUST

Use

In this IMG activity, you can activate the use of the Shared Objects Memory for the following data:

• Central Organizational Hierarchy
• Central Account Group Hierarchy
• Central Management Control Catalog
• Central Process Catalog
• Processes of the Organizational Unit

  It is not possible to use the Shared Objects Memory for all other objects transferred from organizational units (such as account groups or management controls).

Using the Shared Objects Memory improves system performance when calling up data in the corresponding Web applications. When the Shared Objects Memory is activated for the organizational hierarchy, for example, and a user calls up the organizational hierarchy, the system creates a buffer for the organizational hierarchy in the relevant timeframe and loads the data into the buffer. When another user then calls up the organizational hierarchy in the same timeframe, the data is loaded from the buffer, not from the database. However, if the personalized timeframe of the user does not agree exactly with the timeframe of the buffer, then, instead of accessing the buffer, the user accesses the database directly.

When the Shared Objects Memory is activated for the central structures and catalogs, the system creates a separate area instance for each timeframe. When the Shared Objects Memory is activated for the processes transferred from an organizational unit, the system creates a separate area instance for each organizational unit and timeframe.

To guarantee that performance is actually improved, you should only activate the Shared Objects Memory if users generally call up the data with read-only access.

Requirements

Structure setup is complete so that users only call the data using read-only access (such as for assessments and tests).

Standard settings

Activities

1. Activate the Shared Objects Memory (if needed) by entering each object type and timeframe for which you want to use the memory.
2. You deactivate the Shared Objects Memory by deleting the given entry for the object type and timeframe. Doing so invalidates all existing area instance versions.
3. In the IMG activity Monitor Active Areas (transaction SHMM), you can monitor which area instances exist in the system.

For more information about Shared Objects Memories, see Help -> Application Help in transaction SHMM.

Example

You activate the Shared Objects Memory for the processes transferred from the organizational units and specify the timeframe Year 2006.

Users with the personalized timeframes below access the data as follows:

• Year 2006 -> Shared Objects Memory
• 2nd Quarter 2006 -> Database

Business Attributes

ASAP Roadmap ID	250	Define Number Range and Basic Structures
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	MIC_FOPCS_SHM_CUST	0	XS40000002	Management of Internal Controls

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
FOPCSHM2	S - Table (with text table)	SM30		☐	☐

History

Last changed by/on	SAP	20060814
SAP Release Created in	600