SAPTechArena

Unicode : Multi language support

Non Unicode : single language support 

Unicode supports all multiple languages like english, chainaa, german,..etc.
Nonunicode :only supports  two languages i.e english and german.

After NetWeaver and ECC 5.0 and etc. supports unicode kernel.
Unicode provides a unique number for every character, no matter what the platform, no matter what the program, no matter what the language.
 
OLD Code pages have the following disadvantages!

• They cover only a subset of all characters. 
• Different codepages have incompatibilities between each other. 
• Data  exchange is restricted between code pages. there are simply to many code pages.
•  Unicode has the cabaility to support all the languages in the world in one code page! 
• it support 65,000 characters and has room to support an additional 1 million characters.  

Note *

* Unicode is mandatory for SAP systems deploying JAVA applications.
* Many companies are adopting service oriented architecture standards providing
   web services to enable global interoperability. these standards  require Unicode.

What is saproot.sh?

saproot.sh is used to configure the ownership and permissions of some kernel files (BRTOOLS), including the SAPOSCOL. We have to execute the saproot.sh script after we have performed the kernel upgrade. The script need to be execute under root user and can be find under below location.

/usr/sapmnt/SID/exe

How to use

To execute the saproot.sh, just put the SAP system name (SID) and enter.

./saprootsh SID

Starting the SAP System

Stopping the SAP System

Pre Export Process In Application level :- 

• Check the Java JRE version (Min 1.4.1).
• Check the QCM table entries of SAP.
• Check for cancelled and update task
• Delete table entries from TATGPC, TATGPCA
• Check the incremental table conversion
• Cancel all released jobs
• Check for the operation modes
• Delete unnecessary spool data
• De-schedule all SAP jobs
• Delete all the batch jobs
• Release all repairs and correction and transports
• delete background input logs
• Delete job logs
• Delete the tRFC
• Check for the code pages installed
• Check the DDIC password for 000 client

Pre Export Process In OS level :-

• Deschedule all OS DB backups
• Shutdown all external interface
• The source should have minimum SP3

Pre Export Process In DB level :-

• Update DB statistics
• Change the DB to no archive log mode

Steps to Start the DB export

• Enter the system as adm
• Create to directory in the source system eg, Export, Install
• Check for the PSAPTEMP, the size should be 2 times the largest index 
• Start the R3setup.bat program from the kernel CD (use the 45B_EXT kernel cd for the migration as the target system is AIX 5.3, always check the PAM before using the kernel cd.)
• Edit the DBEXPORT.R3S file and skip the update of statistics as it is already done and update statistics of R3SETUP is high time consuming. It can even run for days for a DB size more than 1 TB
• Edit the DBEXPORT.R3S to stop for splitter
• Start the export
• The export stops at the given breakpoint for the splitter
• Split the STR files generated
• Repeat the export process

Import process

• Check the Java version ( Minimum JRE version 1.4.1 )
• Check all necessary drives and filesystems. ( #mkdir /oracle/client/92x_64, # cd /oracle/stage, #mkdir 920_64 )
• Create to directory eg, Install, Import
• From install directory run instool.sh of Ext. kernel cd for AIX.
• set environment.
• #csh
• #setenv LIBPATH /sapmnt//exe:/oracle//920_64/lib.
• Install the central instances. R3SETUP –f CENTRAL.R3S
• In the next installation process choose “Exit”
• Install Oracle software as per WAS640 guide with ora user.
• After the oracle installation is done repeat the installation of the R3SETUP
• The R3SETUP stops for Migration key check phase
• Create the tablespaces of the required sizes
• Restart the database in no archive log mode
• Start the import process
•  Complete the post installation steps from the migration guide of 45 B

Some of the problems faced with the above mentioned source and target system

• During the export phase after the STR files are created the export stops with an error saying 

“Cannot connect to DB”

Solution: Delete the following R3load, R3szchk, R3ldctl from the Instal directory.

•  Use update of DB statistics by sapdba or brtools. Avoid using the update of statistics by the export

Process

Solution: Edit the DBEXPORT.R3S file and delete the lines DBCOMPUTESTAT4MIG_XT*,
DBCOMPUTESTAT4MIG*, BRCONNECTEXPSTAT*

•  Export takes a huge time

Solution: Use the java based package splitter to split the STR files for the export.

•  Export fails complaining the PSAPTEMP size is small.

Solution: Check the size of the PSAPTEMP before export. It should be atleast 2 times the size of the largest index for R/3.

• During the import process check the aio settings in the OS level.

Solution: We have used the mix server of 512 and max server of 1024 during the import process

• 6. The import process fails due to lack of space to extend the extent at PSAPROLL

Solution: Try using the PSAPUNDO in place of PSAPROLL

• 7. The total system downtime could be reduced if MIGMON was used. The firewall rule prevented 

from the use of migmon between the source and the target.


Post Installation jobs for BASIS area

•  Replace the disp+work of the kernel.
•  Delete the table entries as mentioned in the Heterogeneous system copy guide of 45B
• Edit the RFC destination address of other connected system.    
•  Change the printer definition of the target. Test all the printers are working or we need to make changes in the settings.
•  Set up the TMS
• Check for the ALE and IDOCS flow after the new system is up
•  Schedule all the basic BASIS background jobs.
•  Take a full offline backup

Reason for moving to Oracle 9.2.0.7

9.2.0.4 being the first stable release of R/3 had many bugs which are listed in the SAP and Oracle sites were later removed in later subsequent releases.

This oracle will be upgraded to Oracle 10.2.0.2 and for the upgrade the source should be at oracle 9.2.0.7 before it can be upgraded to 10g. 

As we go higher up in the in the Optimizer gets improved hence the execution plans are improved and this results is transactions executing faster

Using of the Package splitter

The java based package splitter can be used to split the STR files

•  Open new terminal preparation for splitter tool.
•  Edit packet_splitter_end.properties file 
•  Use splitter guide for clarification.
•  setenv JAVA_HOME /usr/opt/java141.
•  using adm user, start split process.

This web site is not affiliated with,sap,microsoft, All the contents are based on author’s day to day work administration and troubleshooting activities.

Use the following command to determine the Sybase database version installed.

Select @@ version
go

Or use below command

sp_version
go 

• Sorting of records
• Filtering of records
• Totals and Sub-totals
• Download the report output to Excel/HTML
• Changing the order of the columns in the report
• Hide the unwanted columns  from the report

FUNCTION MODULE	DESCRIPTION
REUSE_ALV_LIST_DISPLAY	Display an ALV list
REUSE_ALV_GRID_DISPLAY	Display an ALV grid
REUSE_ALV_COMMENTARY_WRITE	Output List header information
REUSE_ALV_VARIANT_F4	Display variant selection dialog box
REUSE_ALV_VARIANT_EXISTENCE	Checks whether a variant exists
REUSE_ALV_FIELDCATALOG_MERGE	Create field catalog from dictionary structure or internal table

DATA: it_spfli TYPE TABLE OF spfli.

SELECT * FROM spfli INTO TABLE it_spfli.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
  EXPORTING
    i_structure_name = 'SPFLI'
  TABLES
    t_outtab         = it_spfli.

You might want to install SAP ECC 5 or SAP ECC 6 and been asking SolmanKey. What if you don't have Solman Server ? Then how would you generate solman key ? There are 2 ways (if you don't have Solman Server to generate solman key) :

1. Ask your friend which have Solman Server to generate it. OR

2. Use this simple script (VB Script) to generate it.



'   Solution Manager Key Generator   '
Open Notepad and copy this Script and save it .vbs
'Save to SolManKeyGen.vbs and execute'

msg="System ID (3 chr.)"

SIDs=InputBox(msg,"Solution Manager Key Generator")

msg="System Number (2 dig.)"

SNs=InputBox(msg,"Solution Manager Key Generator")

msg="Server Name (max. 15 chr.)"

SERVs=InputBox(msg,"Solution Manager Key Generator")

KEYs=SolManKeyGen(SIDs, SNs, SERVs)

msg="Solution Manager Key"

ENDs=InputBox(msg,"Solution Manager Key Generator",KEYs)

'-------------------------------------------------------

Function SolManKeyGen(SIDst, SNst, SERVst)

 Dim SIDSNhex(5)

 Dim SERVhex(15)

 Dim reshex(5)

 SIDSNstr = UCase(SIDst) + UCase(SNst)

 SERVstr  = UCase(SERVst)

 For arrcnt = 1 To 5

  SIDSNhex(arrcnt) = Asc(Mid(SIDSNstr, arrcnt, 1))

 Next

 For arrcnt = 1 To Len(SERVstr)

  SERVhex(arrcnt) = Asc(Mid(SERVstr, arrcnt, 1))

 Next

 For arrcnt = Len(SERVstr) + 1 To 15

  SERVhex(arrcnt) = 0

 Next

 If (Len(SERVstr) > 0) Then

  If (Len(SERVstr) < 5) Then

   For arrcnt = Len(SERVstr) + 1 To 5

    SERVhex(arrcnt) = Asc(" ")

   Next

  End If

 End If

 If (Len(SERVstr) > 5) Then

  If (Len(SERVstr) < 10) Then

   For arrcnt = Len(SERVstr) + 1 To 10

    SERVhex(arrcnt) = Asc(" ")

   Next

  End If

 End If

 If (Len(SERVstr) > 10) Then

  If (Len(SERVstr) < 15) Then

   For arrcnt = Len(SERVstr) + 1 To 15

    SERVhex(arrcnt) = Asc(" ")

   Next

  End If

 End If

 For arrcnt = 1 To 5

  reshex(arrcnt) = ((((0 Xor SIDSNhex(arrcnt)) Xor SERVhex(arrcnt)) Xor SERVhex(arrcnt + 5)) Xor SERVhex(arrcnt + 10))

 Next

 reshex(1) = reshex(1) Xor 84  Xor 0

 reshex(2) = reshex(2) Xor 131 Xor 11

 reshex(3) = reshex(3) Xor 194 Xor 46

 reshex(4) = reshex(4) Xor 52  Xor 105

 reshex(5) = reshex(5) Xor 119 Xor 188

 hexstr = "0123456789ABCDEF"

 resstr = ""

 For arrcnt = 1 To 5

  hihex = reshex(arrcnt) \ 16

  lohex = reshex(arrcnt) Mod 16

  resstr = resstr + Mid(hexstr, hihex + 1, 1) + Mid(hexstr, lohex + 1, 1)

 Next

 SolManKeyGen = resstr

End Function

You need to change an instance profile parameter on the R/3 system. 
Goto :TCODE RZ10,

login/system_client
The default value is 000.

Which Client you want change client value like 300,800,000,.

Goto transaction code RZ11, enter the parameter name – rdisp/max_wprun_time and press enter. Once you get the below screen, click on Change Value and enter the desired time. Please not to set the value to 0 as it will make the running time unlimited.

No restart required as the parameter is dynamically switchable. For permanent change, please do it on transaction code RZ10. You can refer to SAP Note 25528.

You want to change the transport number range on the SAP System.

1. Basis Administrator shall login to www.service.sap.com with OSS & password and download the latest Kernel files.

• Downloads---->SAP Support Packages---->Support packages & Patches-Entry By application group---->SAP application Components---->SAP ERP---->SAP ERP 6.0---->  Entry By Component---->SAP ECC Server----> SAP KERNEL 7.20 EXT 64-BIT UC---->Windows Server on X64 64BIT---->MaxDB “SAPEXEDB_402-20006745.SAR”    (Kernel Part II)

• Downloads---->SAP Support Package---->Support packages & Patches-Entry By application group---->SAP application Components---->SAP ERP---->SAP ERP 6.0---->Entry By Component---->SAP ECC Server---->SAP SAP KERNEL 7.20 EXT 64-BIT UC---->Windows Server on X64 64BIT---->#Database  Independent “SAPEXE_402-20006748.SAR” (Kernel Part I).                                                                                                         

• Drive:\usr\sap\SID\SYS\exe

• SAPSID_00
• SAPSID_01
• SAPHostControl
• SAPHostExec

• Go to command prompt
• Go to as above path & Extract the files