SAP Library - Find your answers

Data suppliers deliver values that are displayed in the Alert Monitor. They each belong to the individual system components and create monitoring objects that report values to the monitoring architecture. These values are displayed in the monitor sets.

It can be useful to check the status of the data collection methods if problems occur in the monitoring architecture. You can find out the most important information about the assigned data collection methods on one hand by choosing Properties, if you choose the data collection method in the Methods tab page by double clicking it. On the other hand, you can find out the definition and runtime status of the data collection method of an MTE by choosing Display Details ()

This method is very time-consuming for obtaining an overview of the data collection methods and their status for the MTEs of an entire monitor. The technical view Status Data Collector exists as an alternative for this purpose.

In this technical view, you can also manually start the data collection method for any MTE to which a data collection method is assigned. To do this, choose the relevant MTE by double clicking it. This is useful, for example during test phases or for MTEs for which you require the current value, even if it is not yet time for the next start of the method.

Note that when you start a data collection method manually, it runs under your user name and therefore also under your authorizations. As the method runs under the SAPSYS user when it is started automatically, and this user has only very few authorizations, you can assume from a successful test with a manual start that the method will also run without problems during normal operation.

Procedure

To activate the Status Data Collector technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Status Data Collector. The alert tree now no longer displays the alert status and reported values, but information about the data collection methods of the MTEs of the monitor.

Result

The view displays the following information about the data collection methods that are assigned to the individual MTEs of the monitor:

· Assigned data collection method: If the MTE is assigned an active data supplier, the system will display in the corresponding column, as the active data suppliers are not defined in the monitoring architecture

· Type of the data collection method; depending on the definition of the method, the following types are possible:

· Definition status of the method:

· Runtime status of the method:

The time specification after the runtime status shows the time since which the method has been in this status.

· Frequency of the method call in seconds (Cycle):

The color of the nodes is not passed upward in the alert monitoring tree. Monitoring objects and summary nodes therefore always have the color Green.

Reasons For Archiving Financial Accounting Data

What is financial archiving? Where it is used? Why? Where is it configured in IMG?

There are both technical and legal reasons for archiving Financial Accounting data.

Archiving:
1) Reduces storage and runtime problems caused by the constant growth of transaction data.
2) Makes master data easier to manage and to keep up to date.
3) Enables data to be accessed at a later date.

You can archive data no longer required in the online system using certain standard functions. This data is then stored in archive files and deleted from the online system. For legal and commercial reasons, it is important that you are able to access archived data files online again, and the reloading function allows you to do this.

Data must meet certain conditions before it can be archived. Some of these controls are already defined in the system, for instance the fact that you cannot archive documents that contain open items. Certain other controls are user-defined.
Every archiving function can be accessed from archive management (SARA).

To reach archive management, choose:
Tools --> Administration --> Archiving or from the Accounting --> Financial Accounting --> General Ledger, Accounts
Receivable, Accounts Payable or Banks menus --> Periodic processing Archiving .

When you access archive management from these menus, the archiving object is defaulted by the system in the field Object name. Otherwise you must enter the name of the archiving object manually.

What is financial archiving? Where it is used? Why? Where is it configured in IMG?

There are both technical and legal reasons for archiving Financial Accounting data.

Archiving:
1) Reduces storage and runtime problems caused by the constant growth of transaction data.
2) Makes master data easier to manage and to keep up to date.
3) Enables data to be accessed at a later date.

You can archive data no longer required in the online system using certain standard functions. This data is then stored in archive files and deleted from the online system. For legal and commercial reasons, it is important that you are able to access archived data files online again, and the reloading function allows you to do this.

Data must meet certain conditions before it can be archived. Some of these controls are already defined in the system, for instance the fact that you cannot archive documents that contain open items. Certain other controls are user-defined.
Every archiving function can be accessed from archive management (SARA).

To reach archive management, choose:
Tools --> Administration --> Archiving or from the Accounting --> Financial Accounting --> General Ledger, Accounts
Receivable, Accounts Payable or Banks menus --> Periodic processing Archiving .

When you access archive management from these menus, the archiving object is defaulted by the system in the field Object name. Otherwise you must enter the name of the archiving object manually.

Data suppliers deliver all of the values that are displayed in the Alert Monitor. They each belong to the individual system components and create monitoring objects that report values to the monitoring architecture. These values are displayed in the monitor sets.

The monitoring architecture is delivered with the data suppliers for the most important components of your SAP system and its environment and can therefore be immediately used. When starting the Alert Monitor, you can see that the data suppliers for reporting for the following components are already active:

· The host systems on which your SAP system is running

· The database

· SAP instances (application servers) and their services and components

· Components outside the system

You do not need to prepare or activate the monitoring architecture. The data suppliers in your system are either started automatically when the system is started, or are started as they are required. There are two different types of data suppliers:

· Passive Data Suppliers are started by the monitoring architecture, which is why they must be defined there. “Passive” describes the behavior of the data supplier in relation to the monitoring architecture: it does not start itself, but rather must be started by the monitoring architecture. Passive data suppliers are also known as data collection methods.

· Active Data Suppliers are started by the monitored application rather than the monitoring architecture. These data suppliers are active in their start behavior in relation to the monitoring architecture.

A data supplier writes the values for the monitored objects in a segment of the shared memory known as the monitoring segment. This monitoring data can be transferred to the monitoring architecture in two ways:

· Using a defined ABAP interface, in the case of an SAP instance ‑ a free work process is required for this

· Using a CCMS agent, for any server; the transfer is performed using a Remote Function Call (RFC)

As the connection method using a CCMS agent does not require a free work process, the access method is therefore independent of error states of the SAP instance and therefore more robust. The CCMS agents also use push technology with which the agents report alerts automatically, if the central monitoring system is running SAP Web Application Server 6.10 or above. This helps to ensure a good performance, as the central monitoring system then no longer needs to periodically query the agents for alerts. We therefore recommend that you use CCMS agents when connecting remote systems to the central monitoring system.

Use the Transaction code SCMP to compare the tables. You need an RFC connection for the
comparison server client.
Parameters for this Tcode are:
View/Table: Please give the Table name which you want to compare.
R/3 Connection: Give the RFC connection name (Use F4).

...then there are some options, select the options to meet your requirement

Is there a way to determine the amount of data in a client for a given company code (client size by company code)?

Yes there is -- have a look at OSS NOTE 489690: CC INFO, copying large production clients. You can also determine the size and the storage requirement of your clients with reports RSTABLESIZE or RSSPACECHECK (see also note 118823).

Keyword: BASIS
Title : Data Archiving - Requirements & Importing Archving Technology

Goto SE14

In the field "Obj.name" mention the table name and select "Tables", click on EDIT.

Select the "Delete Data" radio button and click on "Activate and Adjust Database"

The data segment size restricts the size of a user context that is executed as an R/3 background job. The default value is 64 MB, which is however, not sufficient and should be increased.

Set the data segment size for a process to the following values:

You can check data segment sizes using the R/3 test program memlimits. (You must stop the R/3 server to do this.) Note the output row that appears as follows: Process xxxxx allocating. The segment size is displayed in the row Size = .

For more detailed information, also refer to the R/3 installation guide in the section covering UNIX kernel parameters.

SAP Workload Analysis: Data Requested from Database (KB)

Amount (KB) of database data transferred


A number of interfaces are used to provide data for various uses by the SAP application. The requested data is differentiated according to the following interfaces and data types:


Screen sources

Screen load

ABAP sources

ABAP load

CUA sources

CUA load

Nametab interface

CPIC interface

DDIC interface

DSQL interface (user data from the database)

"Roundtrips" is used to display the number of communication steps.

Data dictionary is a central source of information for the data in a data management system.

The main function of the dictionary is to support the creation and management of data definitions (METADATA).

Print data are usually stored temporarily in TemSe before output request are created for them. The parameter rspo/store_location is used to define where spool data are stored in SAP. Two possible values can be defined for the parameter. They are db – Database and G – Global directory at operating system level. These options have their respective merits and demerits. While I intend to explore the peculiarities of these options, I’d like to say that they have common attributes in some senses. For example, reports RSPO0041 and RSPO0043 which checks spool consistency and delete old spool respectively can be applied to both options – db or G.


Storing spool data in the database – db When db is specified for the rspo/store_location parameter, spool request are stored in the database. The table TST03 houses the spool data in the database. A major merit of this method is that data can be backed up and restored using conventional database management tools. It is worthy to mention too that consistency is guaranteed. The obvious demerit of this option is the high load on the database and possible high database maintenance cost and of course, the consequent performance degradation.


Storing data in the global directory at OS level – G When G is specified for the rspo/store_location parameter, spool requests are stored at OS level in the SAP global directory. The strength of this approach is that it ensures that the system is faster and performs better. The downside of this approach is that backup and restore operation is performed independent of the databases at OS level. Also restoring consistency can be a nightmare.

Conclusively, caution must be exercised in adopting spool storage location method especially in an environment where you have multiple application servers. A thorough evaluation of available resources and business need is important. It is pertinent to mention that SAP recommends the use of same spool storage location option across board.
Source Kehinde Eseyin

Keyword: BASIS
Title : SAP MaxDB :: Displaying Information About the Data Area

Keyword: BASIS
Title : Data Structure and Data Types of an R/3 System

Central catalog that contains the descriptions of an organization's data and provides
information about the relationships between the data and its use in programs and screens.

The data descriptions in a Data Dictionary is also called metadata, i.e., data that
describes other data.

The ABAP/4 Dictionary stores system-wide data definitions. When you create a new data
definition, the Dictionary tool does all the processing necessary to create the definition.

You can use the Dictionary tool to look up the "definition" of objects in your R/3 System.

Procedure

If you want to use the "assign then store with bar code" scenario to assign a document to an applicant after initial data entry, proceed as follows.

1. On the SAP R/3 System screen, choose Human resources
® Personnel management ® Recruitment, and then Appl. master data ® Maintain.

This takes you to the Maintain Applicant Master Data screen.

2. Enter the applicant number.
3. Choose Extras
® Assign facsimile.

The Document Type dialog box is displayed.

4. Place the cursor on the document type you require and choose Copy.

The Assign Facsimile dialog box is displayed containing information on the current assignment, such as the document type, infotype, and applicant number.

5. Enter the date of origin, if necessary, and choose Continue.

The Confirm Assignment of Facsimile dialog box is displayed.

6. Confirm the assignment.

The Enter Bar Code dialog box is displayed.

7. Stick a bar code on the original document and use an optical scanner to read it into the system. Choose Continue.

A message informs you that the bar code has been assigned successfully.

8. Forward the original document to the scanning department.

Result

Prerequisites

Procedure

If you want to assign a document to an applicant after initial data entry, proceed as follows.

1. On the SAP R/3 System screen, choose Office
® Inbox.

This takes you to the initial screen of your integrated inbox.

2. Use the appropriate function to choose the list that you require.

The system displays the applicant documents sent to you by the scanning department.

3. Select a document and choose Document
® Execute.

4. Place the cursor on the document type you want to process and choose Process.

The Enter Applicant Number dialog box is displayed.

5. Enter the applicant number and choose Continue.

This accesses the entry screen of the infotype linked to the document type you have chosen, or the Maintain Applicant Master Data screen.

6. Maintain the applicant’s infotype record as required.
7. On the infotype entry screen, choose Environment
® Assign facsimile.

The Assign Facsimile dialog box is displayed containing information on the current assignment, such as the document type and applicant number.

8. Enter the date of origin, if necessary, and choose Continue.

The Confirm Assignment of Facsimile dialog box is displayed.

9. Confirm the assignment.

A message informs you that the facsimile has been processed and stored successfully.

10. Confirm the message.
11. If you have made changes, save the infotype record.

Result

You can only use this procedure if the document type to be processed is linked to infotype 4001 Applications.

Procedure

If you want to assign a document to an applicant during initial data entry, proceed as follows.

1. On the SAP R/3 System screen, choose Office
® Inbox.

This takes you to the initial screen of your integrated inbox.

2. Use the appropriate function to choose the list that you require.

The system displays the applicant documents sent to you by the scanning department.

3. Select a document and choose Document
® Execute.

4. Place the cursor on the document type you want to process and choose Process.

This accesses the Initial Entry of Basic Data screen because the document type is linked to infotype 4001 Applications.

5. Maintain the basic data.
6. Save your entries.

A message informs you that the facsimile has been processed and stored successfully.

7. Confirm the message.

Result

Keyword: SAP HR
Title : Batch Data Communication (BDC) in SAP R/3

Keyword: SAP HR
Title : HR Master Data - Training Steps