SAP NW Newbie

This post discusses various known issues and solutions to deal with the following error when running Software Upgrade Manager (SUM): Could not detect AS Java release. Return code condition success evaluated to false for process /usr/sap/<SID>/<INST>/j2ee/cluster/bootstrap/scripts/version.sh for action ACTION_VERSION. Using DEFAULT configuration fro web methods protection Edit DEFAULT.PLF file from /usr/sap/(SID)/SYS/profile and set configuration:  service/protectedwebmethods = DEFAULT Restart all the SAP instances (including sapstartsrv) and retry the failed step. Replace the scripts Download the latest SERVERCORE.SCA patch file from service market place. Extract sap.com~bootstrap.sda.sda from SERVERCORE.SCA/DEPLOYARCHIVES with an archiver. Extract the following files from sap.com~bootstrap.sda.sda/script launcher.bat launcher.csh launcher.sh version.bat version.csh version.sh version.jstart Go to /usr/sap/[SID]/[INSTANCE]/j2ee/j2ee/cluster/boots

When you first launch SUM tool, it requests you to set an admin password for the tool itself. If for some reason you forgot the password (feeding incorrect password will throw the error: " The password you have entered for role Administrator is wrong "), here is how you can change it Stop the SUM tool Go to the folder <SUM Directory>/SUM/sdt/data Rename or move the files .sdt_storage and .sdt_keystore Start the SUM tool again and it will prompt you to set the new passwords Changing passwords will not reset the upgrade phases, you can continue from the point where SUM stopped.

As soon as you enter the credentials on ESR/Integration Repository/Integration Directory/Integration Builder, if you see the  error " com.sap.aii.ib.core.ejbutil.rb_all.SERVER_MS_NOT_AVAILABLE ", it means that the message server could not connect to  the P4 port of the PI system Call the following URL and check if P4 port is listed: http://<msg_server_host>:<msg_server_port>/msgserver/text/logon Try msg_server_port as the port 81NN, when NN is the instance number of ASCS or SCS or Central Instance (where ABAP message server and enqueue servers are running) Depending on which message server lists the P4 port, maintain the message_server_port (81NN) in the following exchange profile parameters com.sap.aii.connect.directory.mshttpport com.sap.aii.connect.repository.mshttpport If the error includes java.net.MalformedURLException, then the above profile parmaters are not maintained at all and must be maintained along with com.sap.aii.connect.repository.m

Before you begin the refresh activity, note down the current value of trkorr in the table E070L. This table has only one row and the field TRKORR contains the current transport number. After refresh, the transport request numbering will be changed creating a conflict with the already exported transports that are present in the file system. This is because the production system would have fewer released transport requests compared to QA. To avoid this conflict, you can note down the current request sequence held in E070L table and update it after the refresh. If you did not note the current request number, you may be able to find that out from the /usr/sap/trans/log/ALOG* file.

When you want to archive CO tables (COEP, COEJ, COSP, COSS, COST), there are several possible archive objects: CO_ALLO_ST CO_CCTR_PL CO_COSTCTR CO_ITEM CO_KSTRG CO_ORDER CO_PROCESS COPA2_* PM_ORDER PP_ORDER PR_ORDER PS_PROJECT RE_RNTL_AG SD_VBAK In order to choose the best archive object suitable to archive the data in your system, SAP has delivered the following programs: RARCCOA1 : Creates data extract for analysis of CO tables for archiving objects: CO_ITEM, CO_PROCESS, CO_KSTRG, RE_RNTL_AG, CO_COSTCTR, PS_PROJECT, CO_ORDER, PP_ORDER, PM_ORDER, PR_ORDER, SD_VBAK, COPA2_* RARCCOA2 : Evaluates the data extract from the report RARCCOA1 RARCCOAA : For analysis of CO tables for archiving object CO_ALLO_ST. RARCCOAP : For analysis of CO tables for archiving object CO_CCTR_PL. RARCCOA1 and RARCCOA2 Program RARCCOA1 counts the entries of required CO tables, assigns them explicitly to an archiving object and creates a data extract with the required information.

The output of the bdf command is not formatted in a reader friendly fashion. For example the output of bdf sometimes writes the disk usage details in two lines Filesystem          kbytes    used   avail %used Mounted on /dev/sapsidvg/lvsapmnt                    8388608 3450677 4670062   42% /sapmnt To format the output properly, use the following awk trick:  bdf | awk '{if (NF==1) {line=$0;getline;sub(" *"," ");print line$0} else {print}}' The output know will look like this: Filesystem              kbytes    used   avail %used Mounted on /dev/sapsidvg/lvsapmnt 8388608 3450680 4670058   42% /sapmnt

SAP R/2 was the first highly stable solution released by SAP. "R" stood for real-time data processing and "2" stood for the two layers: presentation + integrated application & database. This was in late 70's, when companies were running their business applications on mainframes, and R/2 was apt with the existing technology. SAP R/2 marked the first generation of SAP's business solution. Then came SAP R/3 in the 90's, capitalizing on client-server architecture. "3" signified the three layer architecture (database, application and presentation). The separation of application layer from database layer reduced the load off database and helped improve the overall performance of the solution. This was immensely popular (second) generation of SAP's business solutions. One can attribute the success to Y2K and SAP R/3 fitting the business needs of most organizations looking to dodge Y2K paranoia. SAP was riding the wave of Y2K-led-success