WEEK – 6 (Major project)

In non-production systems, you can make changes to system profiles as often as you like. In production SAP systems, it is only rarely necessary to make changes to the system profiles. In both cases, you should carry out your maintenance tasks using the CCMS profile maintenance.

The profile maintenance tool has the following advantages:

•   Convenience of use
•   Extensive profile checks
•   Testing of (several) individual profiles for consistency
•   No inconvenient profile editing at operating system level
•   Changes to profiles are logged
•   Profile data is held in the SAP database (security, consistency)
•   Provision of basic data for operation mode switching

We make changes in instance profile in extended mode.

A good number of parameters in the RSPARAM table define how security is enforced in the SAP system. These parameters have default values defined for them. If many of these default values are not changed, the integrity of the system can be compromised. The different parameters we changed are as follows:-

1. Login/min_password_letters :-

This parameter sets the minimum number of letters the password must contain. The parameter is valid for both assigning new passwords and for changing and resetting password.

2. Login/min_password_specials :-

This parameter sets the minimum of special characters the password must contain. This parameter is valid both for assigning new passwords and for changing and resetting passwords. All characters that are not digits , ASCII letters are regarded as special characters. This include characters- !, @, #, $, %, ^, &, *,{, }, _, -, +, =, <, >, ?, /, \, [, ], :, ;, .

3. Login/min_passowrd_digits :-

This parameter sets minimum number of digits ( 0-9) that the password must contain. This parameter is valid both for assigning new passwords and for changing and resetting passwords.

4. Login/min_password_lng :-

This parameter determines the minimum number of lower case letters that are to be contained in the password. It affects both assigning of new passwords and changing or resetting passwords. This parameter is not evaluated if the profile parameter login/password_downwards_compatibility is set to the value 5.

5. Login/min_password_uppercase :-

This parameter defines the minimum number of uppercase letters that passwords are to contain. It affects both assigning of new passwords and changing or resetting passwords. This parameter is not evaluated if the profile parameter login/password_downwards_compatibility is set to the value 5.

6. Login/min_password_lowercase :-

This parameter determines the minimum length of the login password. The password must have at least 3 characters. The administration can change the setting so that a longer password needs to be entered. This change affects all new passwords and whenever an existing password is changes or reset.

7. Login/fails_to_user_lock :-

Every time a user enters an incorrect password, the counter is raised for that user’s master record. The logon attempts can be logged in the security audit Log. When the limit set by this parameter is surpassed, the user is locked. This is also in the SysLog. The incorrect logon counter is reset when the user logs on with the correct password. Logons that do not require a password do not change this counter. Active user locks have effect for all logons.

8. Login/fails_to_session_end :-

This parameter defines the number of times a user may enter a wrong password before the login session is terminated. Recommended value is 3.

9. Login/gui_auto_logout :-

This parameter defines the number of inactive seconds after which a user is automatically logged out of the system. Recommended value is 1800 sec.

1. Rec/client :-

This parameter activates or deactivates automatic table logging. It is recommended to switch it on, however, resource utilization, table(s) to be logged and log volume should be critically analyzed

Changing parameter

WEEK- 5 (Major Project)

PRINTING ADMINISTRATION

All devices, servers, and so on that are involved in printing are defined and managed in spool administration.The SAP spool system is responsible for the output of forms and documents. Spool Administration (SPAD) and the Output Controller (SP01) are the tools for managing the spool system. Each ABAP system has its own spool system. Administration of printing is specific to each SAP system.All hardware and software components involved in printing are combined in the print architecture. Depending on the order of these individual components, an architecture that fulfills different purposes and requires a specific print method, such as those listed below, is produced:

• Local printing
• Remote printing (network)
• Frontend Printing

The print process has two main steps -a spool request is created followed by an output request. Spool request data is administrative data, spool data is the document content. When the document is to be sent to a particular output device, the spool request data and spool data are combined. A spool request can be reused to  create new output requests – for example, to resend a document to a different printer.

SWIN is a generic, that is device independent, device type for Microsoft Windows printers. When you create a device definition in SAP system, you can use the generic device type SWIN instead of the printer specific device type .You can use SWIN as a device type for any printer for which a driver is installed in the Microsoft Windows system. There are restrictions in comparison to a printer specific device type for example, performance may not be as good.

• We configured front end printer
• The device type we assigned is SWIN and access method we used is F.
• After this we assigned the user with authority of printing the printer.
• Step 1. A dialog user or a background process initializes a print request.Step 2. The print requests are stored in a location which is determined by a parameter ‘RSPO/Store_location = G’………(G- Global directory at OS level) or
  ‘RSPO/Store_location = DB’……(DB- In database tables)This location is referred as “Temse”( Temporary Sequential File).
  ‘Temse’ stores spool requests
  Temse is stored in Global directory when it is referred as ‘G’. It is stored in database tables TST01 ; TST03. If it is referred as ‘DB’ .

  By default the value is ‘DB’.

  G: (Global Directory on Application Server):

  1. If G is specified it is stored at OS level
  2. The printing will be faster if there are less no of documents. Because from file system to spooler

  The communication faster than database to host spooler

  Advantages:

  1. No special attention is required to backup the spool requests.
  2. RDBMS rules are inherited to spool requests, because they are in the Database

  Disadvantages:

  1.A dedicated backup has to be planned to save the contents of Global directory.
  2. When the records are more the printing consumes more time because of ‘Lack of indexes’ at file system.

  Step 3 Spool process gets initiated and reads the contents from ‘TST01’ name of the Author, no of copies name of the printer and spool data from ‘TST03’. And converts spool requests into “Output Requests’ (Printer specific requests). 

  

  Defining device type

   

  

  defining access type

  System monitoring

• Column	Meaning
  Number (Work Process Number)	The internal ID of a work process. Used to identify messages that belong to a work process in the system log.Internal ID numbers are assigned in ascending order after the server has started. However, because dynamic processes can be started or terminated while the system is running, this consecutive numbering can contain gaps.
  Type (work process type)	There are the following work process types: DIA Work processes to execute: – UI requests – RFC requests – Internal requests UPD: process to execute update requests UP2 process to execute deferred update requests ENQ process to execute lock requests BTC process to execute background jobs SPO process to execute print requests
  Process ID (Process Identification)	Process ID of the operating system.With this number the process can be processed using operating system commands (e.g. ps or kill in UNIX).
  Info (Work Process Status Info)	Current status of the work process. Possible statuses are: Waiting: Process is waiting for requests Running: The process is processing a request. Stopped: The process is stopped for an individual user. Process is waiting for a message. Column Work Process Status indicates what the work process is waiting for. If too many processes have status Stopped, then system performance suffers. Ended: An error has terminated the process Shutdown: Process terminated because of a shutdown Standby : Process is only used in special situations (for example, for load situations or executing requests with high priority).
  Info (Work Process Status Info)	If a work process has status Stopped, the reason is displayed. Typical reasons include the following: Debugging, CPIC activity, locks, updates, GUI (system waits for response from the SAPGUI front-end program, for example, for a remote function call (RFC)). For an overview of the possible parameters, refer to the F1 help in the system.You may also see PRIV (PRIVate use) as a reason for holding a work process. PRIV indicates that a work process is reserved for a single user for memory management use. The work process has exceeded the limit of the SAP memory that is used by other processes. The process is stopped for as long as the current user requires local memory. If more than a certain percentage of work processes are in PRIV hold state, then PRIV transactions are automatically terminated if the user is not active in the transaction for a set period of time. You can set this timespan in the SAP system profile.
  Restart (after error)	Specifies whether the process should be automatically restarted if a process ends prematurely.You can change the restrat status of a process from the menu:  Administration  Process  Restart After Error   Yes/No . Normally, leave Restart set to Yes. If a work process aborts during its startup, the system automatically sets the restart status to No. This measure protects against endless attempts to restart a process if a database system is not available or another serious problem is affecting the system. As soon as the problem is fixed, you can set the restart status to Yes so that the system starts the work processes.
  Failures (Work Process Failures).	Indicates how many times a work process has failed since the instance was started. A work process can be terminated by the administrator or due to an error. The termination counter can be reset from the menu:  List  Reset  Failures .
  locked Sem. (Locked Semaphore)	Specifies the number of the semaphore held by the work process. If the process has stopped several semaphores, the numbers are separated by inverted commas. For a detailed list of possible semaphores, refer to the F1 help in the system.
  (Semaphore To Be Locked)	Specifies the number of the semaphore to be locked. Normally, this field should be empty. If the sempahore appears again after refresh, you can see in the Locked Semaphores column whether the semaphore is being held by another work process. F1 help provides a list of all semaphores used by SAP.
  CPU Time	CPU time since a work process was started. The CPU time of the work process is the sum of CPU system time and CPU user time. The time units are seconds and hundredths of seconds.
  Time (runtime)	This column shows the current runtime of a request in seconds.
  Priority	Priority with which requests are executed for this session. If there are work process bottlenecks, a request can be displaced by another request with higher priority. Presently, the following priorities are supported: High: Priority for online sessions and internal system processes Medium Priority for RFC calls from online sessions. Low: Priority for background processing (batch) and RFC calls from background programs (batch jobs)
  Client	Client in which the current request is being processed.
  User Name	User whose request is being processed.
  Work Process Action (Current Action of the Work Process)	Action being executed by the active program. The actions that are displayed are those that are recorded by the SAP performance monitor. The performance monitor must be active (SAP profile parameter stat/level = 1 (default)) for actions or database table accesses to be displayed. F1 help provides a list of all possible Current Actions of the Work Process.
  Current Action Info	If the database is being accessed, this column contains the name of the table that is being accessed. If it is an AD opcode, this information is the number and name of the AD opcode.
  Server name	Name of the server. This name usually consists of the host name, database name, and system number. The default value should not be changed.
  CPU Time (CPU system time)	Current CPU system time used in the kernel at operating system level since the process was started. The time units are seconds and hundredths of seconds.
  CPU Time (CPU user time)	Current CPU user time used in the application program of the user since the process was started. The time units are seconds and hundredths of seconds.
  Session Type	Type of session executed, e.g. GUI, HTTP, RFC. F1 help provides a list of all possible session types.
  Main Program	Name of the main program.
  Session Key	Internal key of a session The internal key of a session consists of three parts: Logon handle: index in the logon table Logon ID: unique ID of the logon Session handle: internal number of the session The session key is displayed in the form T<logon handle>_U<logon ID>_M<session handle>, (for example, T15_U234_M2) and is also written in this format within the developer trace.

  
   

WEEK -4 ( Major project)

Role maintenance

After creating users we assigned them roles according to their respective departments and authorities for instance the role for human resource department is z_humanresource_shingora with transaction codes pb10, pb20, pb30, pb40, pb50, pb60, pb80 and su53. The transaction code su53 is used to check the last authorization. It basically checks the authority assigned to a user. If there will be any error or the user is not authorised to use the transaction code then we use this t-code to check the object for which the authorisation is not given. If we cannot perform certain tasks using SOA Manager, we may not have the appropriate authorization.

Purpose

We can use the role administration functions to manage roles and authorization data. The role management tool creates authorization data automatically based on selected menu functions, and presents it for postprocessing. It is also integrated with organizational management.We  use the role maintenance functions (transaction PFCG) to maintain our roles, authorizations and profiles. Although we can continue to create profiles manually, we need detailed knowledge of all SAP authorization components.

The role administration functions support we in performing our task by automating various processes and allowing we more flexibility in our authorization plan. We can also use the Central User Administration functions to centrally edit the roles delivered by SAP or our own, new roles, and to assign the roles to any number of users.With the roles, we assign to  the user menu that is displayed after they log on to the SAP system. Roles also contain the authorizations that users can use to access the transactions, reports, Web-based applications, and so on that are contained in the menu.

Features

In the role maintenance you can:

• Changing and Assigning Roles
• Creating Roles
• Creating Composite Roles
• Transporting and Distributing Role

Assign the job descriptions to transactions.

Define job descriptions for each application area in your company (for example, in a job description matrix). Determine for each description the menu paths and transactions that the users with this job require. Determine both the required access authorizations (display, change) and any restrictions.

Maintain activity groups or roles with the role maintenance and the Profile Generator (transaction PFCG).

Use the role maintenance functions to create the roles or activity groups that correspond to the individual job descriptions. For each role or activity group, choose the tasks (reports and transactions) that belong to the job.

Generate and maintain authorization profiles.

In this step, the profile generator automatically generates the authorization profile for the activity group or role. To accept or change the proposed profile, you must work through the tree structure of the profile and confirm the individual authorizations that you want to assign to the activity group or role.

Assign users.

In this step, you assign the users that belong to the relevant roles or activity groups.

Update the user master records.

The user assignment and the generated profile must be updated in the user master records. There are a number of ways in which you can do this.

Role maintenance

Giving detail description of the profile of the user

Assigning roles

Assigning transactions

If any transaction is not working we can check it in su53

 

Giving full authorization

WEEK- 3 (Major project)

Creating new user

TYPE OF USER

• Dialog User
• System User
• Communication Data
• Service User
• Reference User

Dialog User

Dialog User is used for all logs on times by exactly one person. User has the permission to change his password.

System User

System User is used the system user type for dialog free communication between systems. It is used for background processing.

Communication Data

Communication User is used for dialog free communication between systems. We cannot change password or cannot login.

Service User

A Service User is like dialog user that is basically used for anonyms group of users.

Reference User

Reference User is used to provide addition authorization.

SAP users can be created using transaction code SU01. While creating SAP users there are only 2 mandatory fields User name on the Address tab and Initial Password field on the Logon Data tab page. Main tasks that can be performed using transaction code SU01 are:-

• Creating a User
• Copy an Existing user to a new user
• Modifying a Use
• Deleting a User
• Lock/Unlock a User
• Modifying a User’s Password
• Add a Role to a User

After creation of client we have given the responsibility of making different users as per the departments.

Different users we made:-

• Material management – MM01 (create material), MM02 (change material).
• Production planning- MD02 (Execute MRP), MDBT (Execute total MRP), MD04 (Current Stocks).
• Finance and controlling – ob15 (Maintain Table T004R), ob16 (Maintain table), ob04 (Maintain table), oby6 (customizing), oba4 (defining tolerance groups), fbn1 (Number Range), ob52 (defining variant), su53 (Analyzing authority checks).
• Sales and distribution- VT00 (Transportation), VF00 (Billing), VS00 (Master data).
• Business intelligence- DB20 (Update DB statistics), DB16 (Display DB check results), DB14 (Display DBA Operation Logs).
• Quality management- QSR6 (deleting routing), QISR (Internal service request).
• Human resource – PB10, PB20, PB30, PB40, PB50, PB60, PB80, su53 (Analyzing authority checks).
• Planned maintenance- IP10 (Schedule maintenance plan), IP02 (Change maintenance plan), IPCS (Maintenance Planning).

Creating new user

Maintaining user

Creating user for finance department

 

OPERATION MODES

A work process is where an individual dialog steps are actually processed and the work is done. Each work process handles one type of request. There are five types of work processes:-

Work Process Type	Use
Dialog	Executes dialog programs (ABAP). Its parameter is rdisp/wp_no_dia.
Update	Asynchronous database changes (is controlled by a COMMIT WORK statement in a dialog work process). Its parameter is rdisp/wp_no_vb and rdisp/wp_no_vb2.
Background	Executes time-dependent or event-controlled background jobs. Its parameter is rdisp/wp_no_btc.
Enqueue	Executes locking operations (if SAP transactions have to synchronize themselves). Its parameter is rdisp/wp_no_enq.
Spool	Print formatting (to printer, file or database) . Its parameter is rdisp/wp_no_spo.

 

 

Creating profiles for shingora

 

Specifying number of work processes

Implementing profile

Assigning time slots

In SAP we have memory limitations. So, we cannot define very high number of dialog or background work processes. Usually in SAP system, dialog activity will be more during day time and batch activity will be more in the night time. Operation modes are a concept provided by SAP to take advantage of this fact. The transaction code is RZ04. In SAP, we can define operation modes like day and night and configure more dialog work processes and less background work processes during day time and more background work processes and less dialog work processes during night time. We can define duration for day and night operation modes so that operation mode switch will happen at defined time and dialog work processes will be converted to background work processes in the night and vice versa and thus improves performance of the system. For this operation mode switch restart of the SAP system is not required and system automatically does this at the mentioned time.

In first step we created different profiles for different time periods in a day according to the load of activities at that particular time period for instance morning Shingora profile was designed to be implemented in morning and evening Shingora profile at evening. As the dialog activity is more in morning therefore morning Shingora profile had more dialog work processes to cope up with the load and less background work processes. Similarly evening profile had more background work processes as the dialog activity will be less in the evening as there will be less number of users.

After creating profiles we have to select it through transaction code RZ03. We can also assign time to the profiles using transaction code sm63.

Week -2 ( Major project)

Client creation

A SAP client is and independently accountable business unit. Each client is identified by a three-figure number

A client is organizational and legal entity in the SAP system. All the business management data is protected here because other clients cannot access them. The main objective of the client is to keep the data isolated. The data in a client can be only visible within that client; it cannot be displayed or changed from another client. In a physical SAP system there can be multiple clients. Each of these clients can have different objective or each client represents a unique work environment.

Customizing is a method in the SAP R/3 system that helps the user to configure the functionality from SAP, according to the customer requirements. When the SAP objects are just used by only one client, we define them as client dependant data. We must know the fact that client independent customizing can create problems if the authorizations and the client strategy are not defined properly. For example if we have three clients in a development environment then the role of each client should be defined properly. One of these three clients should be used for client independent customizing and in other clients, users will not have the authority to do any client independent configuration.

Types of clients:-

About SAP client

With a standard installation, SAP delivers 000, 001 and 066 clients.

Client 000

Client 000 is considered to be a SAP reference client and it should not be changed or deleted at anytime from the system. After a SAP system is installed, we can create other clients from 000 by using the client copy procedure.  For some important configuration we have to logon to client 000. For example, if we want to configure our CTS system then this client must be used. Client 000 also plays a very important role in upgrade process.

Client 001

The customer uses client 001 as a SAP sample client. After a new installation both 000 and 001 clients are identical, but after an upgrade 000 will have additional customizing data. Lot of customer sites does not use 001 client at all.

Client 066

Client 066 is there for SAP Early Watch service. This client enables SAP to remotely access the customer system. SAP provides this service to the customer to improve the system performance. After Early Watch group goes through the checking methodology, a system performance summery and recommendations to improve performance report are provided to the customer.

How to Create a New Client

SAP uses logical system concept in ALE (Application Link Enabling), workflow and EDI areas. The logical system must be unique throughout the company and any other ALE system grows up cannot use it. We must be careful changing the logical system entry. SAP treats a logical system as a client. We can use transaction BD54 to create a logical system and then enter that entry in the logical system box while creating a client.

In this “Changes and transports for client-dependent objects”, there are four options environment to protect our system. “No transport”option is used when we do not want any user to create a transport from this client.The“Client-independent object changes”category determines if the client independent data maintenance is allowed in this new client. We get following four options in this category:

• Changes to Repository and customizing allowed
• No changes to client-independent customizing objects
• No changes to Repository objects

Changes to Repository and client-end customizing allowed: Both client independent customizing objects and SAP repository objects can be maintained. Usually this option is selected in a master-customizing client.

No changes to client-independent customizing objects: No change is allowed for client independent customizing objects but changes to repository objects are allowed. This option can be used for a sand box client.

No changes to Repository objects: If we select this option, then no changes are allowed to the Repository objects but the client independent customizing is allowed. When we want to protect the repository objects in a client, this is the right option to use.

T-code used to make new client is scc4.  The newly-created client contains the initial user ID SAP* with the password PASS, which you can use to copy a client. The user SAP* is inactive by default in a new client. To activate the user SAP*, set the profile parameter login/no_automatic_user_sapstar to 0, and restart the application server. After copying client we can also export client. In first step we export quality, development and production configuration in a request then import to any client. Where as in copying client only tables are copied in new client. We can export only after copying client because SAP* user does not have authority to import. We created client 009.

After this we copy client and then export it.

Client copy is done using sccl transaction code.

scheduling client copy procedure

Steps for client export /import :-

Client Export:
1.  Run SCC8
2.  Select Profile for desired copy type (Usually All [SAP_ALL] or user master only [SAP_USER].  You will need direction from the requester as to the correct selection here.  Use Profile -> Display Profile to display profile details.)
3.  Select target System (or group)
4.  De- Select “Test Run” (If selected)
5.  Run Export

client import:

1. Create client (scc4)
2. Login to client (sap* – pass)
3. Manually add “O” transport then “X” then “T” to TMS buffer
4. Highlight #1 and use “Request -> Import” to launch import tool
5. Monitor “I” file in OS “/usr/sap/trans/tmp” dir for progress info
6. After Import is complete perform “post processing steps” from client tool (SCC7)

client copy logs are created. From here we can import client into the new client.

WEEK -1 (Major project)

Whole project is based on SAP user administration and configuration which is worthy helpful in creating clients and users, assigning them different roles, providing them authorities along with proper authentication and security. Project is implemented using SAP BASIS module. Responsibilities of BASIS administrator is:-

• STMS (System Transport Management Server)configuration
• Transport organiser
• Client administration(HR,MM,PP)
• User administration
• Operation modes
• Role administration
• Authority administration
• Printing administration
• Security

Objectives :-

• System driven methodology-Everything will be driven by system for example if a person applies for new connection it is registered in SAP system and a job order is created and user id is generated and given to person using which he can track the status of his current application
• Proper monitoring-Everything will be monitored properly and easily for example if a chief engineer wants to know the number of connections pending in his district he can know it from SAP system through MIS(Management Information System)
• Transparency Maintained-System will be transparent to customer for example if a person applies for new connection his connection id is been generated and he will be able to track his application by sitting at home by logging on to website of P.S.P.C.L and putting his connection id.
• Assistance to Customer – Assistance will be provided to customer for example if a customer registers complaint with P.S.P.C.L he is given complaint number and he will be able to track the status through  SMS , through web etc
• Centralized control – Centralized control will be provided by SAP since it links all the sub-divisions of P.S.P.C.L and person will be able to get any information of any office in Punjab using his SAP screen.
• No Manipulated Reports- Reports will be manipulated since everything is done on SAP and it stores  everything in database which cannot be manipulated and BI(Business Intelligence) module will be used for generating reports in SAP

 

STMS Configuration

First step is to disable the existing route using transaction SE06 and then creating servers in client 000.

Creating development server

Like this after creating production and quality server we edit the transport routes.

Deleting existing routes

Then we create new routes

Creating new routes

1. Consolidation routes

To make your changes transportable, set up a consolidation route for each transport layer. Specify your development system as the starting point (source) of these consolidation routes. Specify the quality assurance system as the transport target (in a two-system landscape, specify the production system as the transport target). Any modified objects that have a consolidation route set up for their transport layer are included in transportable change requests. After the request has been released the objects can be imported into the consolidation system. If you make changes to objects which have no consolidation route defined for their transport layer, then the changes are made automatically in local change requests (or in Customizing requests without a transport target). You cannot transport them into other SAP Systems. You can set up one consolidation route only for each SAP System and transport layer.

2. Delivery routes

After you have imported your development work into the quality assurance system, you then want to transport it into your production system. You may even want to transport it into several SAP Systems (for example, additional training systems). To do this, you have to set up delivery routes. Delivery routes have a source system and a target system. When you set up a delivery route, you are making sure that all change requests that are imported into the route’s source system are automatically flagged for import into the route’s target system.

 

After configuring the servers create transport request in Transport Organizer using t-code Se09. This is particularly useful if you want to move the object from development to quality or production or to another system. Each TR contains one or more change jobs, also known as change Tasks (minimum unit of transportable change). Tasks are stored inside a TR, just like multiple files are stored in some folder. TR can be released only once all the tasks inside a TR are completed, released or deleted. Change requests are named in a standard format as: <SID>K<Number>

• SID –System ID
• K –Is fixed keyword/alphabet
• Number –can be anything from a range starting with 900001

Example: DEVK900030

Two types of request can be created:-

1. Workbench Request – contains repository objects and also ‘cross-client‘ customizing objects. These requests are responsible for making changes in the ABAP workbench objects.
2. Customizing Request – contains objects that belong to ‘client-specific‘ customizing. As per client settings these requests are automatically recorded as per when users perform customizing settings and a target system is automatically assigned as per the transport layer.

After creating TR Position the cursor on the TR name or a Task name & choose the Release icon (Truck), a record of the TR is automatically added to the appropriate import queues of the systems defined in the TMS. Releasing and importing a request generates export & import logs. After the request owner releases the Transport Requests from Source system, changes should appear in quality and production system; however this is not an automatic process. Now to perform the import, we need to access the import queue and for that we need to execute transaction code STMS -> Import Button OR select Overview -> Imports. It will show the list of systems in the current domain, description and number of requests available in Import Queue and the status.

After the transport has been performed, system administrator must check whether it was performed properly or not, for that SAP has provided us with the following type of logs (SE01 -> GOTO -> Transport Logs) :

• Action Log –which displays actions that have taken place: exports, test import, import and so forth.
• Transport Logs –which keep a record of the transport log files.

One of the important information provided by logs are the return codes:

• 0: The export was successful.
• 4: Warning was issued but all objects were transported successfully.
• 8: A warning was issued and at least one object could not be transported successfully.

12 or higher: A critical error had occurred, generally not caused by the objects in the request

 

FUNDAMENTALS OF ENQUE PROCESSING IN SAP

Business objects must not be changed simultaneously by different users if consistency is to be maintained.

 

Note: The SAP Web Application Server whose main memory contains the lock table is also known as the enqueue server.

In order for the system to execute lock requests, the lock object must be defined in the ABAP Dictionary. The lock object contains tables whose entries are to be locked. A lock mode can be defined for a lock object.

The different types of lock mode are
· Exclusive locks (lock mode .E.; only assigned if no other locks exist for the data records required; no additional locks are then permitted for these entries)
· Shared locks (lock mode .S.; further shared locks . but no exclusive locks . can be requested for this object)

When a lock is requested, the system checks whether the requested lock conflicts with existing entries in the lock table. If the lock table already contains corresponding entries, the lock request is refused.

When a lock object is successfully activated in the ABAP Dictionary, 
the system generates an ENQUEUE function module and a 
DEQUEUE function module with the names
 ENQUEUE_ and 
DEQUEUE_ respectively.

SM12
(Tools –> Administration –> Monitor –> Lock Entries) displays locks held in the update process in blue and those held by the dialog work process in black.

· Ending the user session in the user overview (transaction SM04, Tools –> Administration –> Monitor –> System Monitoring –> User Overview)
· Manually deleting the lock entries in SM12

Monitoring Tree Element

The alert monitoring tree consists of individual monitoring tree elements (MTEs). They are either components of your IT landscape that are to be monitored (monitoring objects), or values, statuses, or texts that are reported for these objects (see Monitoring Objects and Attributes). These MTEs are assigned to MTE classes and attribute groups in the monitoring architecture:

• An MTE class describes the general properties and method assignments that are common to a particular group of monitoring tree elements.
• An attribute group describes the common threshold values for alerts for a particular attribute type.

Use

MTE classes and attribute groups simplify the Customizing of the Alert Monitor, as you do not need to change threshold values, properties, or methods individually for every MTE, but only for the corresponding attribute group or MTE class.

MTE classes also simplify the creation of your own rule-based monitors, as you do not need to specify every MTE individually when constructing the alert monitoring tree, but rather only the corresponding MTE classes.

The classification of the MTEs to MTE classes and attribute groups is already fully predefined. You do not need to make any changes to be able to use this classification.

If you want to change the properties, methods, or threshold values, the system displays a message informing you whether the change refers only to an individual MTE or to the corresponding MTE class or attribute group. You can change this default value (see Changing Properties and Method Assignments).

Examples

• MTE Class:

The Space Management monitoring object and the Free Space monitoring attribute both belong to the MTE class CCMS_DB_Freespace_MT. This means that both MTEs have the same general properties and method assignments.

• Attribute Group:

All instance-specific occurrences of the Response Time monitoring attribute belong by default to a single attribute group. This means that the same threshold values are set in all of the instances of an SAP R/3 System and that changes to the threshold values apply to all instances.

SAP Support Packages

A Support Package corrects errors in the SAP System or makes necessary adjustments, for example, due to legal changes. The objects affected are replaced in your system.

Each Support Package is valid for only one release (but for all databases and operating systems) and requires an exactly defined number of predecessors. The upgrade of the following release or correction release contains all the Support Packages of the previous versions that were available up to the delivery of the upgrade.

SPAM makes sure that Support Packages are imported only in the specified order.

To prevent errors from occurring, you should import every Support Package as soon as it becomes available. This keeps your system up-to-date.

Use

The following types of Support Packages are available:

• SPAM/SAINT Update

A SPAM/SAINT Update (PAT) contains updates and improvements to the SAP Patch Manager and the SAP Add-On Installation Tool.

• FCS Support Package

An FCS Support Package (FFD) updates an FCS system to its General Availability release so that other Support Packages can be imported.

• Component Support Package

This type of Support Package (COP) is valid for one software component (SAP_BASIS, SAP_HR, SAP_APPL, …) and contains corrections to errors in the Repository and Dictionary in this software component only. In addition to these corrections, Support Packages for the SAP_HR component also contain adjustments due to legal changes.

Naming Convention:

Software Component	Name
SAP_APPL	R/3 Support Package
SAP_BASIS	Basis Support Package
SAP_ABA	Application Interface Support Package
SAP_HR	R/3 HR Support Package
SAP_APO	APO Support Package

 

• BW Support Package

 

A BW Support Package (BWP) is a Support Package for the software component SAP Business Information Warehouse (SAP_BW) and only contains corrections for this component.

• Add-On Support Package

An Add-On Support Package (AOP) is valid for an add-on with a particular release and contains corrections for this add-on.

• Conflict Resolution Transport

A Conflict Resolution Transport CRT is exclusively used for add-ons, for example, IS-IS or IS-OIL. It resolves conflicts that can occur between Support Packages and an add-on.

Start Profile

Naming (START__)
This profile determines how where and under what name the individual R/3 services or process are started. For example it give the location where the Message server.

The processes that can be started include:

1. Application server
2. Message server
3. SNA Gateway
4. System log send demon
5. System log receive demon

Or to start SAP

To run a program on the local host, place the word ‘ local ’ in front of the relevant parameter value:

Execute_00 = local sapmsesa 53 remove

To execute a program on a remote host, place the host name in front of the parameter value.

Execute_00 = hs0011 sapmsesa 53 remove

You can choose any name for a start profile. The start profile files generated by SAP are structured as follows: START_ or START__ .

START_DVEBMGS53, START_DVEBMGS53_hs0311

To start the same SAP service processes on several hosts, you can use a single start profile. Each SAP instance does not have to have its own start profile.