We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.
Showing posts with label Standard. Show all posts
Showing posts with label Standard. Show all posts

Basis-Maintaining Collection and Reorganization Schemata (Standard Setting)

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Use

Collection and reorganization schemata specify how long data assigned to this schema are to be stored in the Central Performance History (CPH) with which resolution. Predefined schemata are delivered with the CPH. These fulfill most requirements. You have two options for creating new schemata, or displaying or changing existing schemata:

· Use the expert setting (see Maintaining Collection and Reorganization Schemata (Expert Setting)).

· Use the standard setting described here.

In the standard setting, you cannot create new schemata from scratch. Instead, you can use an existing schema as a template for your own schema, by changing the storage period of the various aggregates. If you want to create your own schema, we recommend that you use one of the predefined SAP schemata as a template. You can recognize these templates, as they always have the prefix SAP. You will only have to use the expert setting in rare cases.

Procedure

...

1. You can call the standard setting for maintaining collection and reorganization schemata from several functions:

¡ In the overview screen of the CPH (transaction RZ23N), choose, in the Data Collection and Reorganization group box, the Maintain Schema pushbutton.

¡ On the Assign Collection and Reorganization Schemata screen (see Assigning Collection and Reorganization Schemata to Performance Values), choose the desired schema in the Collection/Reorganization Schemata subscreen, and then choose Display Schema (This graphic is explained in the accompanying text).

¡ In the Alert Monitor, with the maintenance functions activated, select a node, and choose Collect MTE Class in Central Performance History(This graphic is explained in the accompanying text). A screen displaying a list of the existing schemata appears. To display one of these schemata, select the schema and choose Display Details (This graphic is explained in the accompanying text).

2. In all of these cases, the Display Collection and Reorganization Schema screen appears. On this screen, you can see which schemata exist. If you want to edit a schema or to create a new schema on the basis of an existing schema, choose the desired schema by double clicking it, and choose Display « Change (This graphic is explained in the accompanying text).

3. The screen now has the following structure:

This graphic is explained in the accompanying text

Creating or Editing a Collection and Reorganization Schema

4. At the left side of the screen, there is a list of existing schemata. The system displays the name of the selected schema in the Selected Schema field. If you want to use this schema as a template for your own new schema, enter the desired name in this input field.

5. In the Collection and Reorganization Process group box, the system displays the resolution of the data that is collected, and when it is reorganized into which resolution. If you want to change one of these times, choose Change Time (This graphic is explained in the accompanying text). The system displays a separate dialog box, in which you can enter the new period.

6. In the Advanced Settings group box, you can specify the time zone for the collection or the reorganization of the data and a day and calendar schema. For more information, see Aggregation, Day Schema, and Calendar Schema).

7. Save your entries.

Delete a Collection and Reorganization Schema

8. Select the desired schema and choose Delete Schema (This graphic is explained in the accompanying text).

9. Confirm the command.

Caution

If there are assignments for this schema, the system informs you of this. If you delete the schema despite this warning, the MTE classes that are assigned to this schema are no longer collected and are deleted from the CPH during the next run of the reorganization job.

See also:

Delivered Collection and Reorganization Schemata

This graphic is explained in the accompanying text Central Performance History of the Monitoring Architecture start page



Keyword: BASIS
Title : Basis-Maintaining Collection and Reorganization Schemata (Standard Setting)

Manually Applying OSS note on SAP Standard Program

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Manually Applying OSS note on SAP Standard Program

What is mean by OSS how to work on that?

OSS are online sap support notes. These notes are available online for solving critical problems in sap system.We may use the already existing notes or may add our own quaries.

In order to apply any OSS note, you have to be authorized by your company and be assigned an OSS ID and password.

For any SAP standard program modification, you are required to login to OSS and request for a repair program Access key.

Access the SAP Support Portal:

http://service.sap.com/

- Keys and Requests

-- Request license key

--- Follow the Steps 1 to 5 of the License keys for SAP Business Suite

--------------

Follow this step to obtain the Program Access key:

Menu Path: System -> Services -> SAP Service (Transaction code OSS1)

Login in with your OSS ID and Password

Click the Registration button

Click Register Object

Double click R/3 Value Contract

Fill in the Object Registration for Installation:

For e.g.
PGMID/Object/Name: R3TR FUGR MIGO
SAP release: 46C

Finished, click the Register button

Select the Key number and use the Copy and Paste short key to copy the Access key

You are now able to modify the SAP standard program.

Finished the modification, do remember to transport it to the production system after all the necessary testing.



Keyword: BASIS
Title : Manually Applying OSS note on SAP Standard Program

Manually Applying OSS note on SAP Standard Program

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

What is mean by OSS how to work on that?

OSS are online sap support notes. These notes are available online for solving critical problems in sap system.We may use the already existing notes or may add our own quaries.

In order to apply any OSS note, you have to be authorized by your company and be assigned an OSS ID and password.

For any SAP standard program modification, you are required to login to OSS and request for a repair program Access key.

Access the SAP Support Portal:

http://service.sap.com/

- Keys and Requests

-- Request license key

--- Follow the Steps 1 to 5 of the License keys for SAP Business Suite

--------------

Follow this step to obtain the Program Access key:

Menu Path: System -> Services -> SAP Service (Transaction code OSS1)

Login in with your OSS ID and Password

Click the Registration button

Click Register Object

Double click R/3 Value Contract

Fill in the Object Registration for Installation:

For e.g.
PGMID/Object/Name: R3TR FUGR MIGO
SAP release: 46C

Finished, click the Register button

Select the Key number and use the Copy and Paste short key to copy the Access key

You are now able to modify the SAP standard program.

Finished the modification, do remember to transport it to the production system after all the necessary testing.



Keyword: BASIS
Title : Manually Applying OSS note on SAP Standard Program

SAP BASIS Standard Reports

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Keyword: BASIS
Title : SAP BASIS Standard Reports

Standard SAP Audit Reports

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

The SAP system has some in built reports that are invaluable for SAP system auditors. By providing simple or complex combination of selection criteria, you can generate reports that make your audit job easy. These reports come with the RSUSR prefix followed by three digit codes. Reports that fall under this category are RSUSR003, RSUSR005, RSUSR007, RSUSR008, RSUSR009, RSUSR100, RSUSR101 and RSUSR102.

In order to objectively analyze these reports, it is important to understand the company policies. Policy areas that need familiarization and understanding includes the following but not limited to segregation of duties, delegation of authority, password policies and user access and management procedures.

The work method to generate these reports is to provide details of the selection criteria in transaction SE38 (ABAP Editor) or SA38 (ABAP Execute Program).

RSUSR003: The SAP system comes with a number of standard users that are used to perform specific administrative tasks. These users include SAP*, DDIC, SAPCPIC and Earlywatch . These users are created with default passwords. It is expected that their user password be changed to a non trivial password after installation to guide against misuse and enforce control in the SAP system. Report RSUSR 003 allows you to know from a glance whether these accounts have been appropriately maintained or not.

RSUSR005: This report displays users with critical authorizations in the SAP system. Some transactions are considered critical in the SAP system and it is expected that their assignment to users should be tightly controlled. Critical authorization does not only apply to technical or basis individual, it also applies to functional users. This report allows an auditor to review users that have critical authorizations.

RSUSR006: User management in SAP can be quite challenging especially in a large organization. Typically, the system can be configured in such a way that a user gets locked after entering a wrong password on a defined number of times. Furthermore, via system parameter setting, it is possible to define how the user gets unlocked…either automatically at midnight or explicitly by the system administrator. Report RSUSR006 provides a list of all users that have been locked as a result of entering incorrect password in the system.

RSUSR007: When users are created in the SAP system, their details including address are entered into the system. For some reasons or the other, it is possible to have users that have incomplete address data. Report RSUSR007 is used to generate a list of such users. These users can be reviewed and their address data completed appropriately. It is good practice to have complete address for all users. It helps user organization and management.

RSUSR008: It is not impossible to have users with complex combination of authorization or transactions in the SAP system especially where duties are not appropriately segregated. Also this might be the case where a matrix of incompatible transaction does not exist. The implication therefore is concentration of powerful roles with some individuals that can perform activities that are not properly controlled or conflicts with the rule of segregation of duties. It is important to review report RSUSR007 in such situation. The report lists users that have incompatible combination of critical authorizations and/or transaction.

RSUSR009: This report is similar to what is obtained with RSUSR005 aforementioned, however, it offers more flexibility. The report displays users who posses’ critical authorization and it allows you to explicitly specify the critical authorization in the selection criteria.

RSUSR100: This report is generated when you need to review change documents for users. It shows modifications to the user’s security.

RSUSR101: This report is generated when you need to review change document for profiles. it shows modifications made to profile security.

RSUSR102: This report is generated when you need to review change documents for authorization. It shows modifications made to authorization security.

Source "Kehinde Eseyin's SAP Library"



Keyword: BASIS
Title : Standard SAP Audit Reports

T r a n s l a t e to your language