HOW TO SAP

How to Implement support packages Execute SPAM. Choose Support Package

January 11, 2008  
How to Implement support packages

  1. Execute SPAM. Choose Support Package > Load Packages > From Front End
    0016-SPAM-SPackage-01

  2. Locate the CAR file and click OPEN
    0016-SPAM-SPackage-02

  3. Select decompress
    0016-SPAM-SPackage-03


  4. In case of you get following message, just press Yes to all
    0016-SPAM-SPackage-04

  5. Click Display/Define button
  6. Click on your component (eg: SAP_BASIS)
  7. Select the highest level and click OK
  8. It will load the SP to the Queue.
  9. Now click Transport (truck) button
  10. Here you choose to start in dialog or backround
  11. Finish and confirm Queue
  12. Done




 Continue Reading

Step by step how to create a batch file to replace saplogin.ini

January 09, 2008  

Step by step how to create a batch file to replace saplogin.ini


Steps:



  1. At times we might need to update items in Sap Logon pad.
    0015-saplogon-batch

  2. The fastest way to do so is to replace the saplogin.ini. (located c:’windows’)
    0015-saplogon-batch-0

  3. Now to backup your original saplogon.ini - just rename it to saplogon.bak.ss

  4. Open saplogon.ini in a notepad. This is how it looks like:
    0015-saplogon-batch-01

  5. Copy paste all the text at the bottom of the screen and paste it into a new notepad. Rename the text file to
    "SAPLOGON-BATCH.BAT"

  6. Open the batch file and replace IP address with your own servers below
    0015-saplogon-batch-03

  7. The above IP address correspond to below system number.
    0015-saplogon-batch-04

  8. Now you can replace your server description accordingly
    0015-saplogon-batch-05

  9. Lastly, replace the system name.
    0015-saplogon-batch-06

  10. Save the "SAPLOGON-BATCH-SAMPL.BAT" on the desktop

  11. Double click the batch file and it will replace your saplogin.ini.

::*********************************************
::* File : Replace existing SAPLOGON.INI
::* Created : 00:43 15/12/2007
::* Version : 1.0
::* Copyright (C) 2007 howtosap.blogspot.com
::*********************************************


@echo Replacing Existing SAPLOGON.INI
@echo 10 precent completed
@echo [Configuration] >= C:’WINDOWS’SAPLOGON.INI
@echo SessManNewKey=4 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [EntryKey] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Router] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo 30 precent completed
@echo [Router2] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [RouterChoice] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=0 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Server] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=172.16.6.6 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=172.16.6.8 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=172.16.6.7 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo 50 precent completed
@echo [Database] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=01 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=03 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=02 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [System] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=3 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=3 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=3 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Description] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=SAP DEVELOPMENT >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=SAP PRODUCTION >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=SAP QUALITY ASSURANCE >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Address] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [MSSysName] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=DEV >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=PRD >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=QAS >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo 70 precent completed
@echo [MSSrvName] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [MSSrvPort] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [SessManKey] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=1 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=3 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=2 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [SncName] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [SncChoice] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo 90 precent completed
@echo [Codepage] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=1100 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=1100 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=1100 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [CodepageIndex] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=-1 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Origin] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=USEREDIT >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=USEREDIT >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=USEREDIT >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [LowSpeedConnection] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=0 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [Utf8Off] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=0 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [EncodingID] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [ShortcutType] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item2=0 >> C:’WINDOWS’SAPLOGON.INI
@echo Item3=0 >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [ShortcutString] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [ShortcutTo] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo [ShortcutBy] >> C:’WINDOWS’SAPLOGON.INI
@echo Item1= >> C:’WINDOWS’SAPLOGON.INI
@echo Item2= >> C:’WINDOWS’SAPLOGON.INI
@echo Item3= >> C:’WINDOWS’SAPLOGON.INI
@echo.>> C:’WINDOWS’SAPLOGON.INI
@echo 100 precent completed!
@echo You may close this window.



Attached Files:

 Continue Reading

Steps by step to query user with certain plants using Business Explorer.

January 03, 2008  

Steps by step to query user with certain plants using Business Explorer.
In organizational level, plant value is actually an object field called "WERKS"


Guide:




  1. Launch Business Explorer
    0010-bussexplorer-001



  2. Select user master data with authorization
    0010-bussexplorer-002



  3. Enter username and execute. Results will be displayed is the excel sheet.
    0010-bussexplorer-003



  4. Right click on a cell > Add Drilldown According to > Field Name
    0010-bussexplorer-004


  5. Now filter again. Right click > Add Drilldown according to > Authoriz. value low
    0010-bussexplorer-005




  6. Keep filtered value
    0010-bussexplorer-006


  7. Congratulation! You have listed only plant company code for the user
    0010-bussexplorer-007
Continue Reading

Find Role inside a Composite role

January 03, 2008  

Step by step to find a role which is used by certain composite role


Guide:



  1. Execute SE16 and enter Table name AGR_AGRS.
    0011-FindRoleinCompositeRol


  2. Enter the role into Child_AGR and execute
    0011-RoleinComposite02

  3. Here, you can see that role "HKTHH1XQNOTA" has a composite role of "HK1THH_KLIENGMU"

    img2
 Continue Reading

Type of processing in SAP - Online and Batch

January 03, 2008  

Type of processing in SAP - Online and Batch



In a SAP R/3 Production environment, business transactions are carried out in the following modes:
-Online Processing
-Batch Processing



Batch Process is a Job, where SAP R/3 reports/Programs are executed in the background as per the scheduled time. Business Process requirements & System Loads are considered for scheduling background Job. A background scheduler is active within the instances of the SAP R/3 System. For Background processing one background work process is assigned to the background Job till the job completes.


Background jobs run in a special type of work process—the background work process—that is different from dialog work processes in two ways:


1. A dialog work process has a run-time limit that prevents users from interactively running especially long reports. By default, the system terminates any dialog work process in a transaction that exceeds 300 seconds. Although the value of the limit can be changed (in the system profile parameter rdisp/max_wprun_time ), that limit is always in effect for dialog work processes. No such limit applies to background work processes.

2. Background work processes allocate memory differently than dialog work processes so that background work processes can become as large as they need to in allocated memory to allow for processing large volumes of data.
Having special work processes for background processing provides an additional dimension for separating background processing and interactive work. Typically, background processing and interactive work on the system is separated by time of day. For example, interactive users have the system during the day; large background jobs have the system by night. But the background work process also lets you separate interactive from background use by server, since background jobs can only run on those servers that offer background work processes.

It is recommended to create one standard user id to run the batch job. Eg: Batch_Adm

 Continue Reading
Subscribe to: Posts (Atom)
Designed By: Blogger Templates | Templatelib