Sapdatabase for all sap modules

sapdatabase provides you all sap modules information,latest updates

Sapdatabase for sap education

sapdatabase provides you all sap modules material,interview needs

Sapdatabase for all sap information

Sapdatabase makes you as a sap professional

Sapdatabase for outsourcing and online training

Sapdatabase provides you online training,outsource services for all sap modules in econamic fee

Sapdatabase for sap jobs

Sapdatabase makes job searching for you

Showing posts with label s. Show all posts
Showing posts with label s. Show all posts

Saturday, February 18, 2012

Assign Operation Modes to Instances & Advantages of Operations ModeAssign Operation Modes to Instances

An operation mode defines a resource configuration for the instances in your R/3 System. It can be used to determine which instances are started and stopped, and how the individual services are allocated for each instance in the configuration.

Operation modes define:
• The number of work processes used for each service in the instance
• The times that the services are available
Operation modes support automatic switching of work process types.

Advantages of Operations Mode:
• The instance need not be restarted
• The switch between two operation mode
• Efficient utilization of resources
To configure Operations Mode go to
Sap Menu -> Tools -> CCMS -> Configuration -> Operation Modes/Instances
On enter Transaction code: RZ04

There are four steps for configuring Operation Mode:
Define an Operation Mode
Define the Instance
Assign the instance and the work process distribution to the Operation Mode.
Maintain the Operation Mode time table.
A Operation Mode should initially be defined to which the instance file parameters and the corresponding Work Process allocation will be allocated.
The fields in the create Operation Mode screen:
SAP System Name: The name of the system for which the Operation Mode is being created (SID)
Operation Mode: Name of the Operation Mode.
Short Description: A Short description about the Operation Mode.

Assign Operation Modes to Instances
To assign the Operation Mode to the instance profile, from the initial Maintain Operation Mode and Instance screen click on Instance/Operation modes.
Next to each Operation Mode a distribution of work processes for that operation mode is given. Note that the sum for all the Operation should be the same.


Assign Operation Modes to Instances
To assign the Operation Mode to the instance, select any of the instance and go to Instance à Maintain Instance à Work process Distribution. The below window is displayed.
This gives the details of the Operation Mode.
Click on the Other Operation Mode at the button of the window.
Put the name of the New Operation Mode
Adjust the number of WP as per your requirement.
Click on the Save Button.

Thursday, February 9, 2012

Errors During Support Package Manager Phases or installation in sap


If an error is recognized during a phase, Support Package Manager stops the import process until the error is corrected. You can get information about the reason the SPAM transaction was stopped and in which phase by choosing Queue ® Status.

Error Types

Support Package Manager displays the following types of error messages:
...
       1.      Support Package Manager Security Checks
A typical example is the OBJECTS_LOCKED_? phase. Support Package Manager stops the import process if objects that need to be overwritten by the queue are still locked in requests.
       2.      Error messages from programs tp and R3trans
You can always find the cause of the error in the relevant transport log. A typical example is the TEST_IMPORT phase. This step checks whether there are unconfirmed repairs to objects that need to be overwritten by the queue. The objects in question are listed in the test import log.
       3.      Incorrect configuration of the Change and Transport System
Errors here often include not having the relevant authorizations for accessing files in the Change and Transport System, or using old versions of the tp or R3transprograms. Check the configuration of the transport tools by choosing Utilities ® Check transport tool.
A typical example is the DISASSEMBLE phase. If <sid>adm does not have write authorization for directory /usr/sap/trans/data (UNIX), Support Package Manager stops at the DISASSEMBLE phase with CANNOT_DISASSEMBLE_R_DATA_FILE.
Support Package Manager requires the Structure linkChange and Transport System to be configured correctly.
For more information on known problems, see the OCS Notes referred to in SAP Note 97620.

Known Errors

PROLOGUE
In this phase, a dialog box prompts you to confirm the import of the Support Package. If you are not authorized to use Support Package Manager, or if the current queue has not yet been confirmed, Support Package Manager stops with a message to this effect.
CHECK_REQUIREMENTS
This phase checks various requirements for importing a Support Package. It may terminate for the following reasons:
       TP_CANNOT_CONNECT_TO_SYSTEM: tp cannot log on to the database of the system.
       QUEUE_NOT_EMPTY: The tp buffer contains incompletely processed OCS requests. Use the following tp command to display these requests:
     tp SHOWBUFFER <SID> -D SOURCESYSTEMS= TAG=SPAM
You can only continue to import the queue after these requests have been completely processed, or deleted from the tp buffer.
DISASSEMBLE
In this phase, files from the corresponding EPS parcels are unpacked and stored in the directory /usr/sap/trans/data (UNIX). It generates the command files (cofiles) from the accompanying files and saves them to directory /usr/sap/trans/cofiles (UNIX). It may terminate for the following reasons:
       CANNOT_SKIP_ATTRIBUTE_RECORD: The attributes could not be read in the EPS parcel. The reason that the file cannot be read is either because it has been deleted or because your authorizations at operating system level do not allow this.
       CANNOT_DETERMINE_EPS_PARCEL: The EPS parcel is not in the EPS Inbox, because it may have been deleted. You need to download the relevant Support Package again.
       CANNOT_DETERMINE_DATA_FILES: The name of a data file could not be determined, because a profile parameter was not correctly configured. Use report RSPARAM to check the settings.
       CANNOT_DISASSEMBLE_R_DATA_FILE: An R3trans data file could not be unpacked.Possible errors include a missing EPS parcel or a data file that could not be written to. An error occurred while transmitting a 20K block from the EPS Inbox to directory /usr/sap/trans/data(UNIX).
       CANNOT_DISASSEMBLE_D_DATA_FILE: An ADO data file could not be unpacked. The reasons are the same as for CANNOT_DISASSEMBLE_R_DATA_FILE.
       CANNOT_CREATE_COFILE: The cofile could not be created from the corresponding data file. One possible error source is that <sid>adm does not have write authorization for the directory /usr/sap/trans/cofiles (UNIX). Check whether the data file has been created. If it has not been created, check that the option Create new data file is activated in the settings.
ADD_TO_BUFFER
This phase adds the queue to your system’s transport buffer. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called. An RFC error has occurred.
       CANNOT_ADD_PATCH_TO_BUFFER: A Support Package could not be added to the transport buffer. For more information, see the SLOG log file in the directory /usr/sap/trans/log (UNIX).
MODIFY_BUFFER
This phase prepares the transport buffer so that the subsequent import phases can be processed correctly. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called. An RFC error has occurred.
       CANNOT_MODIFY_BUFFER: An unsuccessful attempt was made to modify the transport buffer.
IMPORT_OBJECT_LIST
This phase imports the object lists for the Support Packages in the queue into the system. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, see the SLOG or ALOG log files.
       COMMAND_FILE_IMPORT_FAILURE: The object list for one or more Support Packages could not be imported. You can find the source of error in the command file import log.
TEST_IMPORT
This phase checks whether any objects overwritten by the import are still in unreleased tasks. You can find the source of error in the log of the test import.
You can skip test import errors and continue the import by choosing Extras ® Ignore Test Import Errors. However, depending on the type of error, this may cause the error to reappear with very serious consequences during the real import. You therefore always need to check test import errors first, and correct them wherever possible.
OBJECTS_LOCKED_?
This phase checks whether any objects overwritten by the import are still in unreleased requests. It may terminate for the following reasons:
       CANNOT_GET_OBJECT_LIST: The object list for a Support Package could not be found, since the Support Package does not exist.
       CANNOT_CHECK_LOCKS: An error occurred when checking the locks for an object in the queue.
       OBJECTS_LOCKED_IN_REQUESTS: Objects were found that are still in requests that have not yet been released. Release these requests before continuing importing the Support Packages.
ADDON_CONFLICTS_?
This phase checks for conflicts between objects in the queue and installed add-ons. If it finds any, Support Package Manager stops and prompts you to import the relevant Conflict Resolution Transports (CRTs). It may terminate for the following reasons:
       CANNOT_GET_OBJECT_LIST: The object list for a Support Package could not be found, because the Support Package does not exist.
       CANNOT_GET_LAST_UPGRADE_INFO: The information about the component upgrade could not be determined.
       UNRESOLVED_ADDON_CONFLICTS: Conflicts with add-ons could not be resolved, because the relevant CRTs are missing from the queue.
SCHEDULE_RDDIMPDP
This phase schedules the transport daemon (program RDDIMPDP). It may terminate for the following reasons:
       CANNOT_SCHEDULE_RDDIMPDP: Job RDDIMPDP could not be scheduled. Call Transaction SM37 (job selection), enter the following parameters and choose Continue:
Job name
RDDIMPDP
User name
<User name>
Trigger event
SAP_TRIGGER_RDDIMPDP
       Parameter ein und wählen Sie Weiter:
Wählen Sie den abgebrochenen Job aus und zeigen Sie das Jobprotokoll an.
Select the job that was terminated and display the job log.
       Problems with the SAP lock mechanism: Call transaction SM12 and make sure that there are no programs listed with the name RDDIMPDP.
CREATE_VERS_BEFORE
This phase creates versions in the version database of the objects that you want to import and for which versions can be created (ABAP coding, screens, and DDIC objects). It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
If the return code is 0152 (nothing done), check in the configuration of the transport tools in the Transport Management System (transaction STMS) whether the VERS_AT_IMP parameter is set as ALWAYS. If it is not, set this value and continue importing the queue.
       TP_STEP_FAILURE: tp step CREATE_VERS_BEFORE could not be performed successfully. To find the exact cause of the error, choose Goto ® Log ® Queue, and look at the version log.
SPDD_SPAU_CHECK
In this phase, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).
DDIC_IMPORT
This phase imports the ABAP Dictionary. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
       CANNOT_IMPORT_DDIC: The ABAP Dictionary could not be imported. You can find the source of the error in the Dictionary import log.
AUTO_MOD_SPDD
This phase checks whether all modifications to ABAP Dictionary objects can be adjusted automatically.
RUN_SPDD_?
In this phase, you are prompted to adjust your modifications to the ABAP Dictionary objects by calling transaction SPDD.
LOCK_EU (only for import mode downtime-minimized)
This phase locks the development environment. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
INACTIVE_IMPORT (only for import mode downtime-minimized)
This phase imports program code and program texts in an inactive state. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
       TP_STEP_FAILURE: The tp step INACTIVE_IMPORT could not be executed successfully. The cause of the error is in the relevant log (SAPBxxxxxx.<SID>). This log is in subdirectory log in the transport directory. To display this file, run report RSPUTPRT, or call transaction AL11.
DDIC_ACTIVATION
This phase activates the imported ABAP Dictionary objects. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
       TP_STEP_FAILURE: tp step DDIC_ACTIVATION could not be executed successfully. To view the cause of the error in the activation log, choose Goto ® Log ® Queue.
If you import two or more Support Packages in a queue, activation errors can result from an incorrect activation sequence for Dictionary objects. If this is the case, the activation errors disappear if the objects are activated again. To do this, choose Support Package ® Import queue.
IMPORT_PROPER
This phase imports all Repository objects and table entries. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
       TP_STEP_FAILURE: A tp step could not be performed successfully. You can find the source of error in the relevant log, for example, in the import log.
If a tp step 6, N or S is in the termination message, it is a step independent of the transport request. The corresponding logs are contained in the log overview under the node Import steps not specific to the transport request.
You can also find these logs in the following files in the log subdirectory of your transport directory (usually /usr/sap/trans/log):
tp step 6: P<YY><MM><DD>.<SID>
tp step N: N<YY><MM><DD>.<SID>
tp step S: DS<YY><MM><DD>.<SID>
To display these files, run report RSPUTPRT or call transaction AL11.
PREPARE_XPRA
This phase prepares the execution of the XPRAs and after-import methods. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding buffer file. For more information, read the SLOG log file.
UNLOCK_EU (only for import mode downtime-minimized)
This phase unlocks the development environment. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
AUTO_MOD_SPAU
This phase checks whether modifications can be adjusted automatically.
XPRA_EXECUTION
This phase executes the XPRAs and after-import methods. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
       TP_STEP_FAILURE: tp step XPRA_EXECUTION could not be performed successfully. To find the cause of the error, read the method execution log. To view the cause of the error in the log, choose Goto ® Log ® Queue.
       CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer file. For more information, read the SLOG log file.
       CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding buffer file. For more information, read the SLOG log file.
ABAP_GENERATION
This phase generates the runtime objects for the imported Repository objects (ABAP source code and screens). It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
       TP_STEP_FAILURE: The tp step could not be executed successfully. To view the cause of the error in the generation log, choose Goto ® Log ® Queue.
Remember that objects delivered in Support Packages have already been imported completely. If the return code is 0008, all objects without syntax errors have been generated.
The persistence of syntax errors can be due to one of the following reasons:
       Systems that have been developed over a long period of time often contain many objects that are not longer used or maintained. These objects are still active in the Repository and can reference or use other objects (such as includes). If these includes are modified, syntax errors might occur in the obsolete objects. However, these errors have no effect on the SAP System, and can be ignored.
       Generated includes or programs can contain syntax errors after an import. You can usually ignore these errors, since the source code of the generated objects is generated again when the corresponding transactions are started (a special generation transaction might exist).
       If SAP objects have been modified, or if customer objects use SAP objects, there are may also be syntax errors in the modified SAP objects and the customer objects. If this is the case, you must adjust the modifications or customer developments.
       Buffer synchronization problems can also cause generation errors.
Generation errors do not necessarily indicate inconsistencies in the system. However, you should investigate them using the criteria above. If the errors are non-critical, or temporary, ignore them by choosing Extras ® Ignore generation errors, and continue the import of the queue. Choose Support Package ® Import queue.
       CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer file. For more information, read the SLOG log file.
       CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding buffer file. For more information, read the SLOG log file.
RUN_SPAU_?
This phase prompts you to adjust your modifications to Repository objects by calling transaction SPAU.
CLEAR_OLD_REPORTS (only for import mode downtime-minimized)
This phase deletes obsolete versions of program code and program texts from the system. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
       TP_STEP_FAILURE: The tp step CLEARREPORTS could not be performed successfully. The cause of the error is in the corresponding log (PZ<yy><mm><dd>.<SID>). This log is in subdirectory log in the transport directory. To display this file, run report RSPUTPRT, or call transaction AL11.
EPILOGUE
This phase completes the import process. The system checks if the queue has been completely processed. If it has, there should be no more transport buffer entries for the queue. It may terminate for the following reasons:
       TP_INTERFACE_FAILURE: The tp interface could not be called.
       TP_FAILURE: The tp program could not be executed. For more information, read the SLOG or ALOG log files.
       QUEUE_STILL_IN_BUFFER: The queue has not been processed completely, since there are still incomplete Support Packages from the queue in the transport buffer.

Wednesday, February 1, 2012

What are the most important OS level Commands in sap? Sap Os level commands



dpmon d
Dispatcher queue monitor
Sapdba (up to SAP R/3 -4.7)/ brtools
database administration
PS
Running work process
ps -eaf|grep dw
process overview
ps -eaf|grep ora
check oracle service is running
Ps –eaf | grep dw kill -9
Kill work process
msmon pf=profile path name=sid
to check the message server status
gwmon pf=profile path nr=num
to check the gateway status
Ps –eaf | grep lsnrctl
Listener status
Rslgview pf =-r –ft | pg
System logs
Disp + work –v
to check the version of r3 kernel
R3trans –d ,tnsping
Checking the connection with database
Df –k
File system monitor
Du –k
Display all directories and size of current directory
Svrmgrl
Connect internal//(old versions)
---------------------------------------------
Sqlplus
“/as sysdba” (new versions)
SQL prompt and database connection

-------------------------------------------------
SQL prompt and database connection

Saplicence  -get
to get hardware key
saplicense -install
to install license
sappfpar all pf=profile path
display all profile parameters
sappfpar check path=profile path
checks the required space for memory
memlimits
to check the available space for heap and swap memory
telnet
Remote system login
telnet <ipaddress><dispatcherportnum>
to check the remote sap system is up and running
ftp
file transfer protocol
rcp
remote copy of files
Start/stop sap
Start / stop Sap instance
ping
check destination host reachable
niping
check connection between server and a client by transferring packets
systeminfo
check the configuration of system
Ps -aef
Processes status
lsps -a
Swap space
topas
Memory

Tuesday, January 31, 2012

Automatically logged off the frontend SAPGUI


You can set Parameter : rdisp/gui_auto_logout in transaction RZ11.
If no entry is made for rdisp/gui_auto_logout (in seconds), the frontend is automatically logged off.
If the parameter has the value 0, there will be no automatic logoff.
To change the parameter value,
First, display the parameter value with transaction RZ11.
Once in the display screen, you will be able to click the Change Value button to modify your desired value. 

See Related posts

Thursday, January 26, 2012

Mopz,logical system creation & approving support packages step by step screen shots in solution manager

 The prerequisite for this is
Check the RFC SAP-OSS .
The user using this solution should assign by a  SuserID.
 If not we can assign from tcode AISUER.










Creation of System
The system defined in the smsy tcode.
For creation of logical system just go to smsy tcode.






















Then select on type of system creating .
Enter the logical component name.









Enter the logical component name











Creation of solution.
Go to solution_manager tcode
Click on create.












Enter the solution name.















Assign the logical system to the solution.






















































If we get this error check the snote 1242931
Please perform the following SPRO activity:
-> SAP Solution Manager
  -> Scenario-Specific Settings
   -> Change Management
    -> Extended Configuration
     -> Change Transaction
      -> Change Transaction Types
       -> Assign Implementation to Change Transaction Types

In the following screen, please enter CL_CHM1_MAINT_OPT_INSTANCE as the 'Class/Interface' of transaction type SLMON