2.  One or more of the following are right
Customising is a method in SAP which supports
Upgradation
Implementing SAP
Enhancing SAP
Testing

3.  One or more of the following are right
Customising in SAP HR means
Populating the master tables required in infotypes
Defining defaults values for infotypes
Making Infotypes
Setting up HR processes
Writing additional reports
Setting up Standard Queries

4.  One or more of the following are right
In a customising table for a key field
More than one entry with the same value can exist
Exactly one entry with the same value can exist
 
5.  One or more of the following are right
In a customising table , if more than one field make up the key then
for each key field the value has to be unique
for each combination of the key field the value has to be unique

6.  One or more of the following are right
In a customising table , function fields
must have unique values
there could be multiple fields with the same value

7.  One or more of the following are right
When the hrly rate for an employee group changes, you would
delete the exisiting record and make a new one with a new rate
change the rate in the existing record
make a new entry with new value
Delimit existing record and make a new record

8.  One or more of the following are right
Delimiting enteries means
ending a period of validity by changing end date of exisitng record
deleting the entry which is not valid

9.  One or more of the following are right
You can delimit in tables which have
From and To dates as part of key fields
To date as part of key field
To date as a function field
No dates as part of key field

10. One or more of the following are right
Tables that can be delimited are known as
Client independent tables
Time dependant tables
Structure tables
Client Specific tables

11. One or more of the following are right
Master data valid for an infotype field can be viewed by
Pressing the F1 key on the relevant field
Pressing F4 on the relevant field
going to the relevant node in the IMG
 
12.  One or more of the following are right
The following customising enteries can be maintained from the infotype itself
Master Data
Features
 
13. One or more of the following are right
If one building houses many companies of a group company you would
Make one personnel area for each company
One common personnel area for all the companies
Make one personnel area and make the sub areas reflect the various companies

14. One or more of the following are right
Which component of the enterprise structute is unique to HR
Personel Area
Personnel Sub Area
Client
Company
Cost Center
Employee Group
Employee Sub group

15. One or more of the following are right
Groupings which define validity of enteries for employee is defined at the following levels
Personel Area
Personnel Sub Area
Client
Company
Cost Center
Employee Group
Employee Sub group

16. Right or Fake
Personnel Area need not be divided into personnel subareas for a small one location company
Right 
FAKE

17 One or More could be right
Holiday Calendars are set up for
Company
Personnel Area
Employee Subgroup
Employee  
Organisation Unit

18. One or More could be right
Country Grouping is done at
Company
Personnel Area
Employee Group
Employee Subgroup
Employee  
Organisation Unit

19. One or More could be right
You can assign Employee to the enterprise structure in
Organisation Chart
PD Infotype “Account assignment”
PD Infotype “Employee Group/subgroup
Pa Infotype “Action”
Pa Infotype “Organisation Assignment”:

20. One or More could be right
Company Structure in SAP R/3 for HR consists of the following
Organisation Chart
Reporting relationships
Enterprise Structure
Personnel Structure
Payroll Structure

21. One or More could be right
Company Structure in SAP R/3 for HR consists of the following
Organisation Chart
Reporting relationships
Enterprise Structure
Personnel Structure
Payroll Structure

22. One or More could be right
Client number ’000′ is to be used to
implement the prototype for the customer
used as the productive client
used to refer standard settings

23. One or More could be right
Table enteries made in client-dependent table in client 600 is
viewable in client 500
changeable in client 600
vieable in cleint 600
changeable in client 500

24. One or More could be right
To ensure a smooth running productive ‘live’ system, we should allow
Customising in productive system
restricted customising in productive system
disallow customising in live system

25. One or More could be right
ESG for Personnel calculations rule determines
How an employees payroll is processed
the wage types which an employee is eligible for
determines wether employee is paid monthly or other period

26. One or More could be right
ESG for Collective Agreement Provision determines
which collective agreement and employee sub group belongs to
which pay scale groups are valid for the employee sub group
which wage types and employee sub group is eligible for
which wage types are indirectly evaluated
valuation of indirect wage types

27. One or More could be right
Activity, employment and Training status is attached to
Personnel Sub area
Employee Sub group
Employee directly in infotype ‘Actions’

28. One or More could be right
If the value for ESG for Primary Wage types is ’1′ it means
ESG is a hourly wage earner
ESG is a salaried wage earner
that certain wage types are valid in infotype 0008 – Basic Pay
none of the above

29.  One or More could be right
Payroll Accounting area  groups all people
who belong to same location
who should be processed for payroll on the same day
who have the same period eg. Monthly semi, monthly
who belong to same Personnel Calculation rule
who belong to the same Collective Agreement provision
all of the above

Server configuration is 104GB HDD, 2GB Ram.
OS:Win 2003 server.
Database:Oracle.

I manage SAP R/3 4.6C systems on Risc 6000 machines, under Oracle 9.2.

The overall performance problem for me is to know if SAP response time is acceptable ; if not, do this :
- at AIX level : utilities are topas, to catch what’s incorrect : Disk I/O ? CPU bottleneck ? Too much swap ?
- at Oracle level : tkprof but don’t know much about this.
- at SAP level : you can manage SAP memory, Oracle and OS too.

If SAP response time is acceptable, then try this :

Try to have a look at OS response time : ST06 : look at CPU, Memory, Swap, Disk and Lan response time.

Try to have a look at buffer quality : ST02, if many fields are red, investigate each fields dependant parameters.

Try to have a look at DB response time : ST04N, databuffer quality (SGA zone), how much physical reads / logical reads Ratio, wait times, number of user calls, Shared Pool cache hit ratio should be >96%, Sort usage, Redo logging.

I use this kind of procedure to manage my systems.

SAP Tips by: Christophe Rabeau

It depends how much you allocated for SGA (database buffers, shared pool buffer, redo log buffers), how much you allocated for SAP buffers esp. Program buffers and whether the server have any other external processes/programs running.

How many Dialog Work Processes you allocated…I reckon your problem most likely is you don’t have enough of these Dialog processes. Also maybe users running inefficient reports/programs which are holding the Dialog processes, goto SM50 & check all DIA (Dialog) with status “waiting”…if ALL are “running” then you have wait time (problems !) for other users wanting to process transactions .

To troubleshoot performance, you need these tcode tools:-

ST04 – Database  ß in here, check especially for Expensive SQLs (Detail Analysis à SQL Request)

ST02 – SAP buffers

ST06 – OS stats

ST05 – SQL trace

SE30 – Abap runtime analysis

SAP Tips by: Derek Phung

A few step which you can exercise to sort/identify performance issues.

* ST03, ST02, ST04 are the tcode for workload, tuning and DB Performance Monitoring codes.

* ST06 FOR Operation System Monitoring.

** SM51 OR SM50 is process overview which tells you the workprocess sequence. ( Ideally 10-15 process with  OLTP and batch process scheduled at peak and off peak times respectively) say 8-17 hrs and 17-8 hrs for Batch Process)

Operation Mode can be configured in RZ04 tcode.

** Check for top CPU in ST06 tcode.  CPU should not exceed more than 60% for long time for any process.

** Based of No. of instances ( Application Servers ) should have adequately sized.

** Most resources intensive process have to be scheduled in Batch Process ( in Background in Non Peak Hours )

** Look for unnecessary Jobs Active During Prime  Time
** Look for Parameters Set To Your Business Process.
( RZ10, RZ11 ) Check Snote:0124361

** Refer Early Watch Alert Periodically for Overall System Performance.. ( Tcode SDCC )

So, if you can group all of the users hitting the same tables, onto (or one set of) App server(s), then you can tune the App server buffers to a much greater extent.  If the FI users (generally) never hit against the HR tables then the App servers in the FI group don’t (generally) have to buffer any HR data.  That leaves you free to make memory and buffer adjustments to a more drastic extent, because you don’t have to worry (as much) about screwing the HR users (as an example), when you’re adjusting the FI server group.

So, (in opinion only) you should start with a buffer hit ratio analysis / DB table & index access analysis (by user group) to see where you would get the best benefit from this kind of setup.  If you don’t have this kind of info, then making logon groups by line-of-business may have no benefit (or worst case, may make performance degrade for the group with the highest load %).  You need some historical information to base your choice on, for how to best split the users up.

You may find that 50% of the load is from the SD users and so you may need one group for them (with 3 App servers in it) and one other group for everyone else (with the other 3).

The logon group(s) will have to be referenced by SAP GUI, so SAP GUI (or saplogon.ini + maybe the services file, only) will have to change to accomodate any new groups you make in SMLG.  Also consider that there’s variables for time-of-day (load varies by time-of-day) and op-mode switches (resources vary by op-mode).

All Work process are running? What will be our action?

Are all the work processes (dia,btc,enq,upd,up2,spo) running or just all the dialog work processes?

If all the work processes are running, then you may want to look at SM12 (or is SM13?) and see if updates are disabled.  If they are, look at the alert log (if it’s an Oracle database) and see if you have any space related errors (e.g. ORA-01653 or ORA-01654).  If you do, add a data file or raw device file to the applicable table space and then, re-enable updates in SM12.

If only all the dialog work processes are running, there are several possible causes.  First, look to see if there’s a number in the Semaphore column in SM50 or dpmon.  If there is, click once on one of the numbers in the Semaphore column to select it and then, press F1 (help) to get a list of Semaphores.  Then, search OSS notes and, hopefully, you’ll find a note that will tell you how to fix the problem.

If it’s not a semaphore (or sometimes if it is), use vmstat on UNIX or task manager on Windows to see if the operating system is running small on memory which would cause it to swap.  In vmstat, the free column (which is in 4k pages on most UNIX derivatives) will be consistently 5MB or so and the pi and/or po columns will have a non- zero value.  The %idle column in the cpu or proc section will be 0 or a very low single digit while the sys column will be a very high double-digit number because the operating system is having to swap programs out to disk and in from disk before it can do them.

In task manager, look at free memory in the physical memory section under the performance tab.  If it’s 10MB or 15MB (I reckon), then the operating system will be swapping.

Usually, when all the dialog work processes are running, you won’t be able to log in via SAPgui and will need to do the dpmon utility at the command line level.  The procedure is basically the same on UNIX and Windows.

On UNIX:

telnet to server and login as sidadm user.
cd to /sapmnt/SID/profile directory
do “dpmon pf=SID_hostname_SYSNR” (e.g. PRD_hercules_DVEGMS00) select option “m” and then, option “l”

On Windows:

Click on START, then RUN
Type “cmd” and press enter
change to drive where profile directory resides (e.g. f:)
cd to \sapmnt\SID\profile
do “dpmon pf=SID_hostname_SYSNR” (e.g. PRD_zeus_DVEGMS00) select option “m” and then, option “l”

On both operating systems, you’ll see a screen that looks like what you see in SM50.  Depending on what you see here, will depend on what you do next, but checking the developer trace files (e.g. dev_disp) in the work directory (e.g. /usr/sap/SID/DVEGMS00/work) is never a terrible thought.

Please find the process of running the reports. Please take care on the following points to complete the Audit.
We require measurement for all systems except IDES and Backup Systems for the audit purpose.
1. Development Systems ( use Transaction USMM)
a. Select only client where the developer is working
b. Select SAP Individual Solution Pricelist
c. Select the user types SAP ERP Developer (code BA) , and Test Users (code 91)
d. Click on User Classification button , do the query and you would get a list of User types , please Identify developers only and classify the developers as SAP ERP Developer and rest of them under Test users
e. After the classification , go back to the main screen (usmm screen) and click on System measurement button
f. Wait for 10-15 minutes until the background jobs are complete
g. Send the results online by clicking on the Send to SAP button and open the router for some time.
2. Production System ( use Transaction USMM)
a. Select only production clients
b. Select SAP Individual Solution Pricelist
c The relevant User types are the following-
SAP ERP Professional User – AX
SAP ERP Limited Prof. User – AY
SAP ERP Employee – AZ
Test – 91
Multiclient – 11
d. Click on User Classification button and classify the users as per the nature of job of the users in the system.
e. After the classification , go back to the main screen (usmm screen) and click on System measurement button
f. Wait for 10-15 minutes until the background jobs are complete
g. Send the results online by clicking on the Send to SAP button and open the router for some time.
Multi-client (code 11): The concept of Multi-client user classification is as follows: If a user exists in more than one system then, on the system the user has highest authorized role classify to the relevant contractual user type and as Multi-client/system user in the other systems. (refer to page 35 of the System Measurement Guide for details). If you are using LAW, please do not use Multiclient User type
Online Transfer of Results
Due to security reasons we currently change to an online transfer of system measurement results. The measurement results should be transferred to SAP directly from your SAP system with immediate effect.

Please transfer your recent and all future system measurement results online to SAP.
Prerequisites for online transfer:
SDCC or SDCCN is activated (see SAP notes 178631 or 763561)
Authorisations are required:
SDCC_DEV = Read
SDCC_RUN = Read, write for objects S_SDCC (for data transfer )
Procedure for online transfer from LAW:
1. Call LAW (transaction SLAW or license_admin)
2. Choose option Transfer directly to SAP in the Control LAW box
3. For individual comments use the dialog box
4. To show the list of all transfers, choose the Show Transfers option in the Control LAW box
Procedure for online transfer from USMM:
1. Call USMM (transaction USMM) in each system
2. For individual comments use the button Comments
3. Choose option Transfer to SAP
4. To check the status of the transfer, call transaction SDCC/SDCCN

Follow these steps:

- Go to T-code SM19.

- Click on Profile (from menu) make a new profile.

- Under filter1 tab, place the client # and under user place “*”

- Click on Detail configuration.

- Check all boxes of  “Transaction Start“

- Go back and then check the “Filter Active”  check box

- Click on Profile (from menu)  and make sure your profile should be activated

- Click on Environmentà profile parameter

- You will see 12 parameters but  you define 10 parameters in your Default parameter (leave FN_AUDIT and DIR_AUDIT as default)

- During those above parameter you might receive a message something like “incorrect value define” (I ignore this message though)

- Restart your SAP system

- Login again and go to any t-code, then go to SM20 and check if audit works fine

Note: if it does not work in any case, then delete your profile, make it again. You do not need to define parameters though.

Here is a list of items most commonly reviewed by internal/external auditors when reviewing your R/3 system.

It is always a excellent thought to review this list a couple times a year and to take the appropriate steps to tighten your security.

Review the following :-

* System security file parameters (TU02) (e.g. password length/format, forced password sessions,  user failures to end
session etc.) have been set to ensure confidentiality and integrity of password.

Security-Parameter-Settings-Documentation

* Setup and modification of user master records follows a specific procedure and is properly approved by management.

* Setup and modification of authorizations and profiles follows a specific procedure and is performed by someone
independent of the person responsible for user master record maintenance.

* An appropriate naming convention for profiles, authorizations and authorization objects has been developed to help
security maintenance and to comply with required SAP R/3 naming conventions.

* A user master record is made for each user defining a user ID and password. Each user is assigned to a user group, in
the user master record, commensurate with their job responsibilities.

* Check objects (SU24) have been assigned to key transactions) to restrict access to those transaction.

* Authorization objects and authorizations have been assigned to users based on their job responsibilities.

* Authorization objects and authorizations have been assigned to users ensuring segregation of duties.

* Users can maintain only system tables commensurate with their job responsibilities.

* Validity periods are set for user master records assigned to temporary staff.

* All in-house developed programs contain authority check statements to ensure that access to the programs are properly
secure.

Select a sample of :-

* Changes to user master records, profiles and authorizations and ensure the changes were properly approved.
(The changes can be viewed with transaction (SECR).

* Ensure that security administration is properly segregated. At a minimum there should be separate administrators
responsible for:

- User master maintenance. (This process can be further segregated by user group.)

- User profile development and profile activation. (These processes can be further segregated.)

* Verify that a naming convention has been developed for profiles, authorizations and in-house developed authorization
objects to ensure:

- They can be easily managed.

- They will not be overwritten by a subsequent release upgrade (for Release 2.2 should start with Y_ or Z_ and for
Release 3.0 by Z_ only.)

* Assess through audit information system (SECR) or through a review of table USR02, whether user master records have
been properly established and in particular:

- The SAP_ALL profile is not assigned to any user master records.

- The SAP_NEW profile is not signed to any user master records. Verify that procedures exist for assigning new
authorization objects from this profile to users following installation of new SAP releases.

* Assess and review of the use of the authorization object S_TABU_DIS and review of table authorization classes
(TDDAT)  whether :-

- All system tables are assigned an appropriate authorization class.

- Users are assigned system table maintenance access (Through S_TABU_DIS) based on authorization classes
commensurate with their job responsibilities.

* Assess and review of the use of the authorization objects S_Program and S_Editor and the review of program classes
(TRDIR) whether:

- All programs are assigned the appropriate program class.

- Users are assigned program classes commensurate with their job responsibilities.

* Ensure through a review of a sample of :-

- In-house developed programs that the program, code either:

- Contains an Authority-Check statement referring to an appropriate authorization object and valid set of values;

or

- Contains a program Include statement, where the referred program contains an Authority-Check statement referring to
an appropriate authorization object and valid set of values.

I reckon an auditor would want to know what methods you are using to approve who gets what profile and what method you are using to document it so that if you review your documentation you could compare it with what authorization the user currently has and determine if the user has more authorizations (roles) than he has been approved for by the approval system in place.

If the user wants to continue with the multiple logon the following message is part of the option:

“If you continue with this logon without ending any existing logons to system, this will be logged in the system. SAP reserves the right to view this information.”

If you have users who are logging in with other users login and need to view where this information is stored, check the table ‘USR41_MLD‘ via transaction code ‘SE16‘.

The field ‘Counter‘ tells you how many times the user have done a multiple logon.

Making a User Audit Profile
1. Log on to any client in the appropriate SAP system.
2. Go to transaction SM19.
3. From the top-most menu bar on the Security Audit: Administer Audit Profile screen, click Profile -> Make.
4. On the Make new profile popup, type in a new Profile name and click the green Enter picture-icon.
5. On the Filter 1 tab of the Security Audit: Administer Audit Profile screen, click the BOX to the left of Filter active to place a TICK in the box.  In the Selection criteria section, select the Clients and User names to be traced.  In the Audit classes section, click “on” all the auditing functions you need for this profile.  In the Events section, click the radio button to the left of the level of auditing you need.  Once you have entered all your trace information, click the Save picture-icon.  You will receive an Audit profile saved in the status bar at the bottom of the screen.
6. Please note that while the user trace profile has been saved, it is not yet active. To activate the user trace, see the next section Activating a User Audit Profile.
7. You may now leave the SM19 transaction.

Activating a User Audit Profile
1. Log on to any client in the appropriate SAP system.
2. Go to transaction SM19.
3. On the Security Audit: Administer Audit Profile screen, select the audit profile to be activated from the Profile dropdown. Click the lit match picture-icon to activate it. You will receive an Audit profile activated for next system start in the status bar at the bottom of the screen.  The audit will not start until after the SAP instance has been recycled.
4. You may now leave the SM19 transaction.

Viewing the Audit Analysis Report
1. Log on to any client in the appropriate SAP system.
2. Go to transaction SM20.
3. In the Selection, Audit classes, and Events to select sections of the Security Audit Log: Local Analysis screen, provide your information to filter the audit information. If you need to trace the activities of a specific user, be sure to include that user’s ID. Click the Re-read audit log button.
4. The resulting list is showed. This list can be printed using the usual methods.
5. You may now leave the SM20 transaction.

Usually the (minimum) resident time (how long data has to be stored) is fixed by law or in long business discussions – so everything older should be archived, nothing newer is allowed to be archived.  Based on this, I doubt that anyone really needed a detailed space analysis.

Because of a lot of dependencies between the different parts of an archiving object, it’s not so simple to fetch all data to be archived -> there is a test mode, where objects are only gathered and analyzed.

From these test runs in transaction SARAyou can see the number of archivable entries per object (-> table), with the line size you can calculate the amount, but already the number (1458 of 57899 documents) will be helpful. In this example roughly 2.5% could be deleted -> you will win 2.5% of current used space -> or just the space for additional 1458 documents.

But it can be simpler! If all documents are closed correctly, then you can estimate by total volume of documents per year and resident time: when you have 1 million docs per year, you have to store for 2 years, everything above 2.2 Mio can be deleted – the 0.2 for some open stuff, which has to be closed before deletion.

Situation: I am preparing an approach document to show it to management.
Problem: I want to show to management total space likely to get free if we start archiving process. Bifurcated amongst different archiving objects and amongst years so that we can show how much one particular business object is taking space and I can show which all archiving objects we should start with.   If I don’t want to run the archiving object in PRD in test mode. I want to know is there any other alternative for finding the same except consolidation of different table size a particular archiving object is hitting.

There is no simple tool to get this numbers. But on the other hand, you don’t need exact numbers, estimations will do.

It’s a excellent thought to start with the largest objects: take DB02 , make a detailed analysis where you select the largest tables -> corresponding archive objects should be your main focus (for the beginning).

Count for the largest tables in each objects the entries per year (or month, whatever periods you are interested in). Most tables have creation date to do so, otherwise go for number range. For some numbers you could search the creation date, the rest is estimation again.  Then you will have an thought, which volume was made in which time frame.

Still you need some test archive runs (in PRD or an (ancient) copy, at least for an example amount of data): you need to know, which % of the documents can technically be archived, how much will stay open because of missing closing. That’s critical information (maybe 90% will stay in system) and can only be analyzed by SARAtest runs – if you identify the missing object status, you can go on selecting this directly, but in the beginning you need the archive run.

With the volume / time frame and the percentage, which can be deleted you should be able to give estimations based on current total object size. Make clear, that you talk about estimations: every single object will be checked for having right status – before this isn’t done (in a test run), no one can tell exact numbers.

To start the archiving:
Process, follow the menu path:
Logistics – Materials Management –Material – Master – Other – Reorganization – Special Stock – Choose to select the records to delete and
Logistics – Materials Management – Material Master – Other – Reorganization – Special Stock – Reorganize to make archive file.

Make Archive File: Consignment Record: Data selection
a) Select Action: Archive and enter a new Variant, for example: Z_CONS_SELE_01, press ‘Maintain’
b) On selection screen enter the data range (Vendor, Material, etc.) you want to archive.
c) Select the ‘Make Output File’ if you want the selected records outputted
d) Press the green back-arrow and enter the description of this new variantt on the screen which follows.
e) Save the variantt which brings you again to the selection screen. Press green the back arrow again.
f) To start archiving process (batch-job), press the ‘Start Date’ button and select the time when you want to start this process. Select ‘Immediate’ for instant processing and press the ‘Save’ button on the bottom of the ‘Start Time’ window.
g) Select the ‘Spool Parameter’ button and save entries. Eventually enter a valid printer to have the result outputted.
h) You are ready now to start the process. Press the ‘Start’ button and monitor the success with the ‘Job Overview’ button
You can also go the ‘quick path’ by using transaction SE38, program MMREO002 for selecting the data to archive. For large data archiving, use the background jobs and run those during off-peak times.  Make Archive File: Consignment Record:

Archiving process:
a) Select Action: Archive and enter a new Variant, for example: Z_CONS_ARCH_01, press ‘Maintain’
b) On selection screen, select the ‘Sequential Dataset’ if you selected data as described in the Data Selection step, otherwise enter the material number and plant for the deletion of a single record.
c) Select the fields ‘Consignment’ and ‘Special Stock’ and Test mode, if you want to try out first.
** This applies for SAP systems prior to release 3.1H: Select also the flag called ‘BATCHES’. The SAP program MMREO020 has a bug which can be worked around with this selection. Without selecting ‘BATCHES’, the archived records cannot be deleted. For systems with applied Hotpackages for 3.1H this workaround is not necessary
d) Press the green back-arrow and enter the description of this new variantt on the screen which follows.
e) Save the variantt which brings you again to the selection screen. Press green back arrow again.
f) To start archiving process (batch-job), press the ‘Start Date’ button and select the time when you want to start this process. Select ‘Immediate’ for instant processing and press the ‘Save’ button on the bottom of the ‘Start Time’ window.
g) Select the ‘Spool Parameter’ button and save entries. Eventually enter a valid printer to have the result outputted.
h) You are ready now to start the process. Press the ‘Start’ button and monitor the success with the ‘Job Overview’ button
You can also go the ‘quick path’ by using transaction SE38, program MMREO020 for selecting the data to archive. For large data archiving, use the background jobs and run those during off-peak times.  If you run the program online, you will see a confirmation on the status bar telling ‘New Archive file made:….’

Delete Archived Records: Info Record
a) Follow the menu path: Tools – Administration – Administration – Archiving
b) Select the Object Name MM_SPSTOCK for consignment / Special Stock
c) Select the menu button ‘Delete’
d) Select the menu button: ‘Archive Selection’
e) Click the archive made in previous step
f) Select Start Date for process and Spool Parameters for output
g) Submit selection.
h) Check status by pressing the Job Overview button

Archive a Material Master Record

When a material is no longer required in a company or plant, you can archive and delete the material master record.

You have to Flag the material master record for deletion. This is known as logical deletion.

Before a material master record can be archived and deleted, other objects (such as purchasing documents) that refer to this material must themselves be archived. You can see which objects these are and the dependencies between them in the network graphic.

If a material master record cannot be archived and deleted at a given organizational level, the reason is given in the log (for example, a buy order exists for the material). The log also contains technical data such as the number of material master records read and the number deleted.

Some of the archive error log message :-

• Costing data exists
• Use in routing
• Use in sales and distribution
• Use in bill of material
• Delivery exists
• Costing data exists
• Info record exists
• Buy order exists

The Archiving steps :-

Archiving object MM_MATNR for archiving material master records.

You can show the archived data, but not reload it.

To archive the material master, first goto transaction MM71.

Type in a variant name and click Maintain.  (Tick the Test Mode for archive simulation).

Save the variant.

Maintain the Start date and Spool parameters and click do.

Click Goto Job Overview to check the archive status.

To do a permanent delete, goto transaction SARAand click Delete button.

Maintain the Archive Selection, Start date and Spool parameters.

Click Test Session for testing or click do to start the deletion program.

Click Goto Job Overview to check the delete status.

Now, if you goto MM02/MM03, you will not be able to find the record in the material master.

Reorganization basically removes deleted data from tables. During different transactions you delete some records, which are deleted virtually but not physically. Even Archive process delete those records virtually.
So you run Reorganization to free up the space consumed by deleted records.

This make the difference between the two clear.

Now about reorganization.

It depends on which OS and DB you are using.

If Oracle, SAPDBAis best tool to reorganise.

In addition to above, you can reorganise the whole database, but it takes time depending upon your database.  Some times it can be more than a day or you can reorganise a table suggested in Early Watch system.

It all depends on you.

I came across with a situation that there is program which is fetching about 2 million records of total size around 190MB. But system could not allocate this much memory so the program aborted. I suggested them to process only 50,000 records at a time which worked fine. But I want to know if my suggestion was excellent enough. Can’t the system with below configuration allocate 190MB for a program. There was no much load on the system at that time.

Our configuration:
SAP 46c on Win 2K
RAM: 4GB
Virtual memory: 8GB.

Do you guys know what are all the things to be done to enable ZERO MEMORY MANAGEMENT in 46C ?

You can get an overall estimate by looking in SM04 and switching on the MB size beside the users so so you will see how much memory the current transactions are using. Take into consideration that there is a huge difference between dialog transactions (with several steps) and mass processing or lists. The latter two consume usually a lot more memory.

190 MB is not much, our usercontextes can become as huge as 2 GB per user (which is the limit on 32bit platforms)  several times a day. This is not uncommon on systems that have a lot of data in them, but, it’s impossible to give a general advise here since this is VERY different on what applications you are running, how many systems are connected (BW,
CRM, APO etc.) and so on.

Start with note 88416, there is clarified in depth what it is and how it works.

For Windows you also should look in note 129813 which will describe the rebasing process since M$ has the start addresses of their DLLs loaded into the PXA. This is one reason why we switched to a non M$ operating system because after each IE patch (in fact after each patch) you need to check if the new DLLs will fragment your PXA/shared memory.

Note 546361 can also be helpfull. If you have “hangs” in the system read note 530871 which will describe the problem (and finally recommend upgrading to Windows 2003).

What is Zero Administration Memory Management?

The zero administration memory management on Windows requires no manual settings and adapts itself dynamically to the memory requirements of the users. Even hardware changes (for example memory enhancement) are detected and the parameters set correspondingly.

The basis for zero administration memory management on Windows is the dynamically self-extending extended memory. An “infinitely” large memory resource is made available with this method. The extended memory is initially set to the size of the profile parameter PHYS_MEMSIZE ([PM]). If more memory is required by the user, the extended memory extends itself in steps of “[PM] / 2″ up to the set limit of the profile parameter em/max_size_MB or until the address space in the Windows pagefile is used up.

By setting the standard value for em/max_size_MB to 20000 MB (100000 MB for 64 bit), it is the size of the Windows pagefile that finally represents the actual limit for the extension of the extended memory. The profile parameter PHYS_MEMSIZE determines how much of the entire main memory is to be used by SAP. The parameter is entered during installation in accordance with the entry. The standard valuefor PHYS_MEMSIZE is the size of the main memory [HS]. Even with zero administration management, the Windows system should be configured in such a way that it keeps the file cache to a minimum size. Therefore, make sure that indicator “Maximize Throughput for Network Application” is activated under ‘Control Panel’ -> ‘Network’ -> ‘Services’ -> ‘Server’ -> ‘Properties’.

What tcode can I used to find out how much memory is allocated to R/3 in total? I know for Oracle I can get the SGA memory.  I am using SAP 4.7 / Oracle 9i on Unix AIX.

Go to ST02 –> Detailed analysis –> Sap memory. This will let you know memory allocated for that app server.  You can also find out memory allocated for user (mode list) and Quotas.

You can also use report RSMEMORY to find out how sap alloctes memory to Dia and Non Dia work processes.

I’m worried that is incorrect. The question is also not a simple answer.

Go to ST02 –> Detailed analysis –> Storage is the right path. The Virtual memory allocated line shows SAP’s allocated memory.

This memory does not include what the DB uses or the OS or other things running on the server. More importantly it does not include heap (private memory) allocated by WP’s. It also does not include the executable size of the GW, the ICM and the dispatcher but it does include most of their memory in the shared memory areas.
It also does not allow for additional memory that a Windows system may dynamically allocate to extended memory if the users use it all up.

Question on Shared Memory and IMODE

Can someone tell me about Shared memory (Code Definition) and IMODE?
I have never heard these terms in SAP R/3, Shared momey sounds like its related to Operating System.

All memory is OS memory I’m worried there is small distinction in that regard.

Shared memory is memory that can be addressed by different processes as opposed to private memory that can only be addressed by the process that makes it. A excellent examlpe would be the Program Buffer (PXA) this buffer hold the recently used programs in memory for quick access and needs to be read by all work processes. A more impotrant shared memory area is extended memory. In 32 bit processing you need to keep shared memory areas at a minimum because otherwise you limit the amount of space in the address space that your program can use for its own data. I won’t get into a sad chat about all this bat thats hared memory.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

An IMODE is an internal mode. An example may be best, log onto a SAP system, make a new session and leave one at the main menu and with the other go to ST02. In ST02 near the bottom of the screen double click on the extended memory line. In the next screen click on the Mode List button. You will see you have the ST02 session marked with an X for being attached and another session in IMODE 0.

With the other session got to SM36 then swap back to ST02, press enter and you will see the session has an IMODE 0 and an IMODE 1 use. Now from the SM36 screen click on the button Job Selection and jump back to St02 and press enter, you will see the session has an imode 0 1 and 2 active.

Imode 0 is not really an IMOde but the main mode that all your information relevant in any transaction is available. As you call transactions inside transactions you need new memory and the ancient stuff needs to be save for when you green arrow back. This is why you have imodes so that when you green arrow back from the job selection screen above (I mode2) it is no longer the active mode and imode 1 is reactivated.

For those that are not locked, the report will list down the number of incorrect login that the users have done.

If you have lots of affiliates to your main company, this will result in lots of users. Out of them, there might be lots of inactive users who have left the company.

You may wish to delete those inactive users.

Use SA38 to run RSUSR200.

This report is part of the AIS (Audit Information System) and will report users who have not logged on for a specified period of time.

To know how many users are viewing and maintaining a particular transaction use transaction ‘ST03‘, in3.0x:-

• Performance database
• Select instance
• Select desired period
• Choose Transaction profile

To find the Frequently Used Programs or Transactions in 4.6x :-
ST03 —> Detail analysis Button –> Under Global- One recent period then select day or week or month —> Transaction profile Button

In 4.6x, you can also try the new Workload Analysis tcode ‘ST03N‘.

The SAP standard retention period is 3 months.  You can change the Standard Statistics via clicking :-
Goto -> Parameters -> Perfomance Database

To analyze the Statistics by users for transactions and programs use transaction STAT

STATlooks at the STAT file made by each SAP Instance.

It is by default 100 MB.  Every hour there is a COLLECTOR_FOR_PERFORMANCE job RSCOLL00aggregating this data into MONI table.  It will truncate STAT file once the specified  limit is reached.

So, you can see details for but many days in this 100 MB using STAT, or ST03to see the MONI aggregated data.

To change the 100 MB limit, ST03 -> Goto -> Parameters -> Performance Database.

Why data was not showing in ST03?

Problem:
Last one month I face this problem when I am taking full system o/s backup of production server stopping all the oracle automatic serveice with SAPOSCOL &  SAPPRD_00 , STOP SAPMMC.  When backup was completed, I started all the service.  But, after some time data was not showing in ST03.  When I stop & start this sap services SAPOSCOL & SAPPRD_00, then data will start showing for some time but after 2 day same problme comes again.

All sap pjobs are running well.  What could be the problem in SAP.
Details of server:
O/S : Windows 2003
SAP : 4.7 EE
Oracle : 9i

Solution:
1. Ensure that the job COLLECTOR_FOR_PERFORMANCEMONITOR executes the report RSCOLL00 hourly. Furthermore, the report RSSTAT80 should be executed every hour. You achieve this by maintaining the table TCOLL with transaction SM31. Enter “X” in every hour for the report RSSTAT80 (column “Time of day”).
2. The report RSSTAT80 should be executed every hour. You achieve this by maintaining the table TCOLL with transaction SM31. Enter “X” in every hour for the report RSSTAT80 (column “Time of day”). You should then increase the maximum number of statistics records read in each run of RSSTAT80. You can set this value with transaction ST03, Goto -> Parameters -> Performance database. Press “Modify parameters” and enter at least 10,000 for the value “Max. number of records cumulated per call”. You must then save the settings.
3. Using transaction ST03, Goto -> Parameters -> Performance database, pushbutton “Modify parameters”, increase the value of “Max. number of records cumulated per call” to at least 10,000 and save the change. If this or a larger value is already set, please proceed as in point 2.

Why data was not showing in ST03?

Problem:
Last one month I face this problem when I am taking full system o/s backup of production server stopping all the oracle automatic serveice with SAPOSCOL &  SAPPRD_00 , STOP SAPMMC.  When backup was completed, I started all the service.  But, after some time data was not showing in ST03.  When I stop & start this sap services SAPOSCOL & SAPPRD_00, then data will start showing for some time but after 2 day same problme comes again.

All sap pjobs are running well.  What could be the problem in SAP.
Details of server:
O/S : Windows 2003
SAP : 4.7 EE
Oracle : 9i

Solution:
1. Ensure that the job COLLECTOR_FOR_PERFORMANCEMONITOR executes the report RSCOLL00 hourly. Furthermore, the report RSSTAT80 should be executed every hour. You achieve this by maintaining the table TCOLL with transaction SM31. Enter “X” in every hour for the report RSSTAT80 (column “Time of day”).
2. The report RSSTAT80 should be executed every hour. You achieve this by maintaining the table TCOLL with transaction SM31. Enter “X” in every hour for the report RSSTAT80 (column “Time of day”). You should then increase the maximum number of statistics records read in each run of RSSTAT80. You can set this value with transaction ST03, Goto -> Parameters -> Performance database. Press “Modify parameters” and enter at least 10,000 for the value “Max. number of records cumulated per call”. You must then save the settings.
3. Using transaction ST03, Goto -> Parameters -> Performance database, pushbutton “Modify parameters”, increase the value of “Max. number of records cumulated per call” to at least 10,000 and save the change. If this or a larger value is already set, please proceed as in point 2.

Double click on the application modules for more information breakdown.

If there are no analysis data is available for the history in ST07, it is because the program RSAMON40, which generates snapshots of the application monitor data and saves them to the database, has not started yet. If RSAMON40runs regularly, the data may sometimes be deleted again by a reorganization program.

For releases lower than 31I, schedule the program RSAMON40periodically (hourly) as a background job.

As of Release 31I, this report is automatically carried out by the performance collector (RSCOLL00). Check the scheduling of RSAMON40 in table TCOLL as described in note 12103.

To prevent the data from being deleted again by a reorganization program, you must still make the following entry in the SAPWLREORG  table:

CI ID =
MONIKEY = –<DATE__>+++++++
RESIDENCY = 0

It is Request task that allows objects from repository or customizing to be managed with in the system and between the SAP systems. What ever the changes you make in SPRO will be recorded in a Transport request. System will prompt you for a request when you does the changes in customizing.

2) How many changes you can make in one request?

We can do any number of changes to Transport request.

3) Who will make transportation request?

System will prompt you for Transportation request when you do any changes saved for fist time.

4) How the screen looks like inside (what are the fields)?

Each screen is built by a program (module pool program in ABAP terms), which consists of number of fields. This program will consist of the events which need to done on these fields, like updating the entries of the fields to the Database, or getting entries form the data base….

5) What is the parent & child relation ship?

Each table will have primary key, which will be linked to other tables with foreign keys. Eg: material number is primary in MARA table, but it is foreign key in MAKT table.

6) What is the t code for release? And who will Release?

SE01 or SE09 or SE10 and basis consultant will release and transport in generally, in some cases any consultant may release but the transportation will be done by basis consultant.

7) From which server you will release to production?

Development -> Quality server -> Production

8) What are the tools that companies use for support? Give some examples?

Solution manager, Remedy Tool and Lotus notes.

9) In a support environment, How we get tickets? Who will assign tickets?

Once a end user/ Business users stuck any where in between executing a transaction, he makes the a Ticket, which will be routed to concerned persons by help-desk/PM.

10) Tell process of ticket flow from client side to technical consultant?

Mails mostly

11) What are the statuses?

It tells whether a transaction is completed or in-process or open at a given time.

12) If its development (service request) what is the Process? After solving how you will communicate to Client?

Mails mostly
13) What are the deliverables in a blue print?

The blueprint consists of requirements form the business, which needs to be mapped in the system through customizing or developments; these are called deliverables in realization phase.

14) What is cut over strategy?

It is strategy of any company to go the data and making Transaction activities to SAP system from legacy system.

15) Client dependent & client independent?

Each server can have more than one client, like 200, 230, and 300. If you maintain some settings it will affect all the client then it is client independent, otherwise client dependent.

Steps for transporting SAP standard text.

Make a work bench CR in the transaction SE09.

Modify the task to Development correction / Repair.

Go to the program RSTXTRAN.

In the name of correction give the task number (Not the CR number).

Give the Text Key.  Your standard text name.

Press F8.

Press select all.

Then Press enter.

Then press the button “Trsfr texts to corr”.

Now the standard texts will be went to a CR.

Then release the CR and go it to QA.

or

Procedure for transporting standard text:

1. In se38 run program RSTXTRAN

2. Enter the following entries
Name of correction (in which request number you want to place) -> DV3k590456
Text key – object -> Text
Text key – name (your standard text name)
Text key – ID -> ST
Text key – language -> EN

3. Click do button (F8)

4. Select your standard text and press enter

5. System will question whether to place the standard text in request number e.g. DV3k590456 then, press Yes button

6. Your standard text will be placed in e.g. DV3k590456

By: Markus

“Renaming” a system is not supported officially and thus not fully documented.

It’s not about just renaming a SID, SAP internally there need to be ran jobs (to make the “own” RFC destinations, jobs as RUTTTYPACT and others), make rfcexec.sec etc. etc. – those things are handled nicely by sapinst.

The system may work at the first sight but you will start getting distress if you try to connect that system to another system using RFC (e. g. transports) because of a missing “secure store” etc.

The following places come to my mind where manual changes has to be done:

- profile changes (start- instance-)
- OPS$-user changes
- IGS RFC destination
- local filesystem permissions of the kernel files(if you change the user)
- operating system user permissions (speaking of gpedit.msc)
- permissions on registry keys (yes, they have also permissions) etc. etc.

As part of our upgrade we need to rename our existing development system from DR1 to DR2. What is the impact of renaming an existing system from an ongoing development/configuration standpoint?

You need to change the SID before upgrade or after Upgrade through System Copy etc. There is not harm in changing the SID, make sure all the POST System Copy activities are carried out before the upgrade, eg. Instance Profile Names, etc.

If you have deleted from SAP level. Then you need to check at the OS level in /usr/sap/trans/log directory else you can check for the SLOG and ALOG folder also.
If total request has been deleted then you can also do the transport manually at OS level.

or

If you have simply deleted the the requests from import queue through “Extras-> Delete imported requests” in transaction STMS_IMPORT and have not deleted the logs at OS level, then you can check in “Goto-> Import History” in the same transaction to view the requests.

Just double click on the request you want and you enter the “Show Object List” screen for the particular request.
Here you can click on the secong “Spectacles” icon to show the transport steps of the request in each of your SAP system.
Just double click on a step, e.g. ‘Import’, ‘Check Version’,'Export’ etc. to show the log for that particular step.

You can also view the logs from operating system in the directory <TRANSDIR>/log. The logs are named in the format:
<Source SID><Step ID><Request no>.<Target SID>, where step ID is a single alphabet denoting a particular transport action.                                                                                                      *– Krishna

Find Request Number