what is Dialog work process Multiplexing

                     Generally large number of users log into SAP sytem. The dialog work processes (wp) available to the users are limited due to performance & system limits. The objective of a dialog work process is to handle the user requests quickly and display the results. Dialog work process also takes large resources relatively to background processes for display purposes. So it is not wise to have a dialog work process running for each user logged in. A dialog work process is not assigned to a single user for longer time. When a dialog user fires a request, the dispatcher assigns a dialog WP to handle the request. When the request is processed, it relieves the work process from that user so that other users can use it. This helps in handling requests from a large no of users with small no of dialog work process and optimum use of resources.

SAP Authorization Concept Modules

The SAP authorization concept modules are color-coded in the hierarchy display.
The basic SAP authorization concept terms are displayed below, before you specify the authorization field values. The colors of the SAP authorization concept modules are the standard colors in the following hierarchy display.

Explanation of terms:    Click here to know more...

What is transport domain controller in SAP

              Transport domain is the collection of transport controller, trans directory and all other systems in the group.
          Transport domain controller is a system which has trans directory, and in which the total landscape is designed and  maintained



The transport domain contains all SAP systems whose transports are to be administrated jointly. One of these SAP systems is chosen as the transport domain controller.
Since all activities relevant to the entire transport domain, such as configuring transport routes or RFC connections, can only be carried out on the domain controller, the SAP system selected to be the domain controller should have:
High availability
A high level of security
A high level of maintenance

The domain controller is normally configured on a production system or a quality assurance system. Out of several reason you may choose to set up an SAP System dedicated to tasks that may be carried out CENTRALLY. This includes the task of the TMS domain controller.
The system load on the SAP system that is chosen as the domain controller is low, and only increases for a short period when the TMS configuration is changed.

How to troubleshoot SAP authorization issue

                    use "SU53" to troubleshoot the authorization issue face by the user and 
follow by using "PFCG" to resolve it.

1) Login to the client where user had encounter authorization error


2) "SU53" to check the authorization error encounter by the user


3) Click  to switch user  to view the authorization error4) Example of error that cause by "object A_S_KOSTL" and the missing authorization value is either "BUKRS" (1132) or "KOSTL" (0001132000) 


5) To identify which role that relevant to the above object that causing the authorization error, 
Run TCODE: "SUIM" and expand “Roles”, select “Roles by Complex Selection Criteria”

6) Enter user ID and authorization objectthen click "Execute" icon


7) The result show only one role match these filtering criteria


8) From this point, there are 2 options available:

     a. Make all the necessary authorization changes in QAS and once UAT is ready re-
         download the role to DEV and create transport report to deploy the
 role to QAS and DEV

     b. Make the authorization changes in DEV and transport to QAS for UAT and follow by 
         transport to PRD later on


9) Either option, run "PFCG" and enter the relevant role name for modification and click 
the "Pencil" icon

10) Click find "find" icon to search the authorization object that caused the error
 e.g. A_S_KOSTL, S_CTS_ADMI or BC_A

11) Add the missing value in the relevant authorization object parameter, then 
click "generate "icon" and exit


12) Done

What is Spool Administration In SAP

It is used to output the document to a printer, fax, email and SMS etc.
It is only the process which is used to display the documents before they get printed.
Once a spool request is generated in the system, It can be printed to any printer with n no of copies, at any time.
Where as normal printing, the document will not be available once it is printed.
We can change the output format at any time.


work process used for spool administration is 
 
SPOOL 'S' 



It is used to print the documents to a printer or output to a fax machine etc. There should be atleast 1 Spool process in the entire system. It is also possible to configure more spool process depending on the print/ spool volume


The spool process are configured by parameter ‘RDISP/WP_NO_SPO’
Depending on the resources as many no of spool processes can be configured.

What are Status of Spool Requests SP01 in SAP




       The lists of spool and output requests (transaction SP01) display, the status of the requests. 
        The request can have the following statuses:

Indicator
Processing Status
Spool request has not yet been sent to the host spool system (no output request exists)
+
Spool request is being generated (stored in the SAP spool system)
Waiting
The output request is awaiting processing by the SAP spool system and has not yet been sent to the host spool system.
Waiting in host spooler
The output request is to be sent or is being sent to the spool work process, or for formatting, in the host spool system.
If this status is displayed for a request for an extended period of time (more than one minute), the corresponding spool work process may have terminated, or there may have been a problem establishing a connection to a remote output device.
The spool work process automatically reprints the output request affected by the problem.
In Processing
The spool work process is formatting the output request for printing.
Print. (Printing)
The request has been passed to the host spooler or to an output device, and a final status has not yet been returned to the SAP spool system.
Compl. (Complete)
The output request has been successfully printed. In systems in which the SAP spool system cannot get information from the host spooler, the status becomes Complete as soon as the output request has been passed to the host spooler.
<F5>
More than one output request has been generated and the requests have different statuses. Some requests may not yet have a final processing status.. To display the status of individual requests, choose This graphic is explained in the accompanying textOutput requests or double-click the request status.
Problem
There is a minor problem; the output request was printed, but probably contains errors.
Example: If the printer character set is incomplete, a missing character is replaced with another (#).
Errors
There is a problem with severe consequences. Requests of this type could not be printed and remain in the spool system until you delete them or the retention period is exceeded and they are deleted by a reorganization.
Example: The system cannot find the printer in the network.
Use the error log to determine the cause of the error.
Archive
(For spool requests sent to an archiving device.) The spool request has been processed by the spool system and is waiting to be archived.
Time
or
Scheduled
The user who created the request specified a time when the request is to be output.

What is Transport Management System(TMS) in SAP

  Transport Management System(TMS)
It acts like central system to transfer data from one system to another
Data can be modification in tables, customize program
From Dev To QA(test)…..Then from QA(test) To PROD




Memory Management in SAP




Memory allocation

  1. User submits request.
  2. Dispatcher assigns the workprocess.
  3. Workprocess requires memory to roll In the user context
  4. Workprocess gets memory from local memory which is defined in the parameter Ztta/roll_area  it gets only a part of it which is defined by perameter Ztta/roll_first(20KB)
  5. If the allocated memory is not sufficient then it gets allocated from extended memory Ztta/roll_extension.
  6. If that is also not sufficient then it uses the remaining ROLL Area.
  7. If that is also not sufficant then it uses HEAP/PRIVATE Memory and Workprocess goes into PRIVATE Mode.
  8. Heap memory is defined by the parameter