SAP support SMTP from WebAs 6.20 and higher.

As of SAP Web Application Server 6.20, faxes and text messages (pager/SMS) can also be exchanged via SMTP. For this purpose, the faxes and messages are packed into e-mails. For sending, the mail server refers to the domain of their recipients' addresses and forwards the e-mails either to an internal fax/text message server.

Adobe Document Services (ADS) comes installed by default with NetWeaver AS Java and is SAP’s standard way of creating PDFs by SAP applications. These PDFs can be normal PDFs or interactive (called Adobe Interactive Forms). The SAP system using ADS can be any NetWeaver ABAP or Java system. This makes the setup process a little bit more complex: it depends on your use case which steps have to be executed. You can have the ADS system that is a NW Java system, a NW ABAP system and another NW Java system that use ADS. And many times the calling NW Java system is the same system ADS is running on.

Tip

When you start configuring ADS, write down each system and its role. If not, it`s pretty likely you`ll have later some problems in identifying which connection and user you are configuring.

For this document I`ll consider the scenario of an ABAP system calling ADS to generate a PDF. In this scenario, the components involved are ADS, NW ABAP and NW Java. These are also the main areas to consider when setting up ADS.

Things are more complicated because the communication between the ADS and the calling system is bi-directional. For instance, the ABAP system calls ADS and sends the data to be converted and after ADS finished the conversion, ADS calls the ABAP system. After all, you want to use PDF in your ABAP system. Simplified, the information looks is like:

What does this mean now when you have to configure ADS together with ABAP?

1. Check that there is an ADS user with the right UME actions on NW Java
2. Check that there is an ABAP user with the right profile on NW ABAP
3. There needs to be a connection from ABAP to ADS (destination type web service)
4. There needs to be a connection from ADS to ABAP (as a destination: NW Java, as a SICF service: NW ABAP)

Configuration: ADS

As ADS is a JEE application it makes use of the security and authorization concept of JEE. This means that you

1. a) need an ADS user and
2. b) assign the right permissions to this user

to be capable of executing the application. As ADS is a NW Java application, to gain access the right assignment of UME action to the user executing / calling the application is needed (therefore, you can use any username). By default, the user ADSuser is created and the UME actions are made available in the NW Java system when ADS is installed. If they are missing, something is wrong with the ADS installation.

Short: on the Java side the ADS configuration is actually nothing more than assigning permissions.

Parameters to remember

While the SAP documentation talks about assigning a role, what counts are the UME actions assigned to that role. Looking up the UME actions for default user ADSuser.

ADSuser:

Role

UME actions

As soon as the user ADSuser is assigned to the role SAP_ADSCALLER the necessary permissions are available and this user can access and use ADS.

Remember

ADSuser is the user used by the ABAP system to call ADS. The ABAP system will use this user to log on to NW Java and to execute the ADS web services. This is not a service user used in the background by ADS.

Configuration: ABAP

In the ABAP system, configuration involves main tasks:

1. Set up a HTTP connection so the ABAP system can call ADS
2. Maintain user used by ADS to call the ABAP system
3. Set up the destination called by ADS to transfer the PDF

Let us go through each one of these three steps, starting with the user administration.

1. HTTP Connection

This configuration is needed so that the ABAP system can actually call ADS.

Transaction: SM59

Information flow: ABAP -> ADS

By default, the name of the destination is ADS and of type G (which means HTTP. After all, ADS is exposed as a web service).

The technical settings point to the NetWeaver Java server where ADS is running.

Logon tab

Here the logon information send by ABAP to Java to authenticate as an ADS user are given. The user entered here MUST have the right UME permissions assigned. The user information entered must match what was used in Configuration: ADS (see above).

2. User SAP Help

To send back the PDF, ADS invokes a ICF service on the ABAP server. To do so, it must authenticate on the ABAP server. Therefore, a user must be made available on the ABAP system that has the This is the user used by ADS to send back the generated PDF to the ABAP system.

Information flow: ADS -> ABAP.

Transaction: SU01

3. ICF service. SAP Help

This configuration is used by ADS to actually send back the generated PDF. ADS is not using a RFC / BAPI connection but a web URL. As in ABAP a URL is backed by a ABAP application, a valid ABAP user with the right permissions to execute the ABAP application is needed. This user was provisioned in the previous step. This implies also that the PDFs are not simply stored as pdf files in a file repository but processed by a SAP application.

Transaction: SICF

Information flow: ADS -> ABAP

Enter fp in the service name field and execute the report. The service will be shown. Ensure that the service is active.

Configuration: ADS to ABAP

Configure a connection between ADS and ABAP so that ADS can call the ABAP system and send back the generated PDF. This is done in NW Java using a destination. SAP Help

Open NWA and navigate to SOA -> Destinations

Create a new destination. The name of the destination needs to follow a certain naming convention: FP_ICF_DATA_<SID>

In case the <SID> of your ABAP system is SID, the correct name to enter here is FP_ICF_DATA_SID. (If your ABAP SID is AB1, it would be FP_ICF_DATA_AB1).

Next, enter the connection settings. These are needed by ADS to call the ABAP server using HTTP and for the logon information. In case the HTTP server of the ABAP server is listening on port 8000 on SID and client 100 with logon language English, the information to be entered looks like this:

The last step in the destination configuration wizard is to provide the logon information. Remember, this is how ADS will authenticate itself against the ABAP system. Therefore, a user with the right permissions on the ABAP system must be entered here. For basic authentication, (NetWeaver Java will transmit username and password) using the default user ADS_AGENT the information to be entered is:

Conclusion

After going through the basic setup, there are a few things to note.

1. On the Java ADS side, you can have more than one ADS user. They only have to be assigned to the correct UME actions. If you want, you can have N users: ADS1, ADS2, …, ADSN
2. For each ABAP system you`ll have to create a destination on the ADS NW system.
3. Each destination can have its own user, these do not have to be the same or even share the same password
4. Both the destination ADS uses as well as the URI of the ABAP service are fixed. While ADS uses the destination to resolve the host name (and user/password), the path on the ICF service cannot be configured through the destination and is fixed.

If you need to mass lock printers in split second, here is a quick way to do so.

Steps

1. Go to txn SPAD -> Utilities -> For output device->Export devices and export the printers to a text file:

2. Click Generate button to start the export. You will get a Save As popup window to save the exported file and this is result screen once you save the file.

3. Edit your exported file in any text editor e.g. Notepad and change PADISABLED="" to PADISABLED="X" (this is the setting to disable the printers)

4. Re-import the printers. Go to txn SPAD -> Utilities -> For output device->Import devices. Select your modified file, select the values as shown and click Generate to import the printers.

5. All Printers are now locked now.

1. Pre - Requisites :

• No of Drives should be same in both Source Server & Target Server. (Not Mandatory)
• Drive Names should be same in both Source Server & Target Server. (Not Mandatory)
• Installation of Database & SAP should be same in both Source Server & Target Server.

1. STOP SAP & Oracle SERVICES AND EMPTY FOLLOWING  DIRECTORIES :

Go to Target Server & Stop all services (oracle & SAP both).

Now Delete the All files inside the following Directories.

SAPDATA_HOME\sapdata1\sysaux

SAPDATA_HOME\sapdata1\system

SAPDATA_HOME\sapdata1\temp

SAPDATA_HOME\sapdata1\undo

SAPDATA_HOME\sapdata1\cntrl

SAPDATA_HOME\sapdata2\ sr3_1 ………sr3_n

SAPDATA_HOME\sapdata3\ sr3702_1 ……… sr3702_n

SAPDATA_HOME\sapdata4\sr3usr_1

SAPDATA_HOME\origlogA\cntrl

SAPDATA_HOME\origlogB\cntrl

SAPDATA_HOME\sapdata1\cntrl

1. PLACE BACKUP FILE IN SAPBACKUP DIRECTORY

Place the xxxxxxxx.and File In Sap backup Folder

SAPDATA_HOME \sapbackup

The File Name Will Be Like This belerzpm.and

1. Open Cmd Prompt And Run This Command

BRRESTORE –m full –b xxxxxxxx.and –d disk –c

Now The Restoration Process Has Started

1. Again Delete Oracle Control Files under these directories that comes after restoration  

SAPDATA_HOME \origlogA\cntrl

SAPDATA_HOME \origlogB\cntrl

SAPDATA_HOME \sapdata1\cntrl

1. Create trace file in source server using this command:

SQL>Alter database backup controlfile to trace;

Copy this trace file to target server and rename to control.sql.

Now modify this control.sql

Delete all before “startup mount” & after “CHARACTER SET UTF8;” in control.sql

Change

• <source SID> to <target SID> 
• REUSE –> SET
• NORESETLOGS --> RESETLOGS

            Now, Put this Control.sql to C drive on <TARGET SID>   SYSTEM.        

              Start Oracle Services

             SQL> @C:\CONTROL.SQL;   

1. Copy all archive logs to SAPDATA_HOME\oraarch & Run these commands

SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;     

SQL>ALTER DATABASE OPEN RESETLOGS;

1. Create Users as per note 50088.

1. Start SAP Services.

A little background to this document.  In our environment the Central Services (ASCS and SCS) are currently housed on the same server as our Database.  This database server is in a secluded (via firewall) network zone.  For certain upgrade activity we have found it necessary to move the ASCS and the SCS on to the same server as our Central/Primary Instance.  We were not able to find any documentation online on how to accomplish this.  Through trial/error we developed our our procedure, which I would now like to share with the community.  Our environment is a UNIX one.  Adjust accordingly for Windows/other.

These instructions have been used/tested on NetWeaver 7.0, 7.02, and 7.3.

Definitions

Primary or Central Instance - In this document I will often be referring to the Primary or Central Instance.  This is meant to refer to the instance DVEBMGS*.  For the purposes of my document, these terms should be considered synonymous.

Central Service - ASCS and SCS.  Generally enqueue and message services.

1. On the Central Instance application server make a backup of the entire /sapmnt/<SID>/profile directory (cp –R /sapmnt/<SID>/profile /sapmnt/<SID>/profile.bak).
2. Move the ASCS and SCS profiles to the Central/Primary Instance Server.
3. Using tar/zip, move /usr/sap/<SID>/(ASCS##|SCS##) from the source server to the target server.
4. In our environment the ASCS and the DVEBMGS instances have the same number (They are on different servers).  If this is the same in your environment, make sure to rename the /sapmnt/<SID>/profile file(s) to a new (unused) number.  The ASCS/SCS folder(s) in /usr/sap/<SID> will also have been be renamed with the same corresponding number.
5. In /sapmnt/<SID>/profile, edit the DEFAULT.PFL.  You will need to change any value that relates to the Enqueue/Message service.  If you changed the instance number of the ASCS/SCS, you will also have to reflect these changes in the appropriate entries in DEFAULT.PFL.  Pay special attention to Port numbers and host names/IP addresses.  If you are a bit lost on the port numbers, this SAP Document on TCP port numbers may come in handy.
6. In /sapmnt/<SID>/profile, change values in <SID>_DVEBMGS##_<Server> as required to reflect the location of your new cental services.  In our environment, no changes were needed here as this is entirely defined in our DEFAULT.PFL.
7. In /sapmnt/<SID>/profile, change values in <SID>_ASCS##_<Server> and <SID>_SCS##_<Server>, similar as you did in Step #5.
8. In /sapmnt/<SID>/profile, change values in START_SCS##_<Server> and START_ASCS##_<Server>, similar as you did in Step #5.
9. Rename <SID>_SCS##_<SourceServer> and <SID>_ASCS##_<SourceServer> to <SID>_SCS##_<TargerServer> and <SID>_ASCS##_<TargerServer>, respectively.  Be sure to pay attention to CaSe SeNsiTivItY.  On UNIX environments, the "hostname" command will provide you with the expected host name and case.  Change the ## as appropriate, if required.
10. Rename START_SCS##_<SourceServer> and START_ASCS##_<SourceServer> to START_SCS##_<TargerServer> and START_ASCS##_<TargerServer>, respectively, similar to step #9.
11. In systems that have a java stack, open ConfigTools.
    1. Under Global Server Configuration and Global Dispatcher Configuration open up manager/cluster manager and in the fields ms.host and ms.port change to desired values. Also change “Managers/Locking Manager” enqu.host and enqueue.port
       
    2. After you complete the changes on the first screen, proceed to the File|configuration editor and scroll down through cluster-data|Propertysheet instance.properties and look for the instance.properties option. Click the pencil to enter edit mode.  Change the following to new, appropriate values:

       1. Instance.en.host

       2. Instance.en.port
       3. Instance.ms.host
       4. Instance.ms.port
    3. Save your changes and exit Config Tools.
12. In systems that have a java stack, you need to tell the SDM of the new central service location.  If you fail to do this, the java instance will not start up.
    1. cd /usr/sap/<SID>/DVEBMGS##/SDM/program
    2. ./sdm.sh jstartup mode=standalone (SAP System may need to be down?)
    3. ./sdm.sh registerjstartup sdmhome=/usr/sap/<SID>/<Instance>/SDM/program/ jstartupdir=/usr/sap/<SID>/<Instance>/exe/ mshost=<TargetServer hostname> msport=<Port Of Message Server>
    4. ./sdm.sh jstartup mode=integrated
13. Start SAP System.  Check /usr/sap/<SID>/<Instance>/work/dev_server0 to ensure the java stack comes to "Running".

To move the Central Services back, simply restore the backup you made in step #1 above and undo the changes you made in Steps 11/12.

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on November 2013.

BC-CCM-MON*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

RZ20 for CPU_Virtualization_Power

- the CPU_Virtualization_Power subtree is in responsibility of the agent

- all other CPU_Virtualization_* nodes are in responsibility of saposcol

This means:

1) agent creates CPU_Virtualization_Power and is responsible for the content
2) fortunately - the data presented in the subnode are gained from saposcol and are reachable in other CPU_Virtualization_*   subtrees
3) agent does some kind of renaming in the nodes, e.g.  "Entitlement" could be found as "Guaranteed Capacity" in CPU_Virtualization_Virtual_System subtree

Summary - the values present in CPU_Virtualization_Power are collected by agent from other CPU_Virtualization_* subtrees, which are maintained by saposcol. It's kind of duplicity. The saposcol is always the originator of the data. There are no additional data in the _Power node which are not present in other virtualization subtrees.

At first in the beginning the EWA report only reported the standard CPU data for the physical server and the data for this is directly collected
by SAPOSCOL in a 24 hour buffer in which for each hour 4 times 60 measurements are stored because SAPOSCOL collects the data every 15
seconds by default.

This means that you can say that in the old EWA reports the OS CPU operating statistics are based on 4x60 is 240 measurements each hour.

After this SAP decided to create new monitor structures for the OS virtualization but the monitoring data for the CPU_Virtualization_Power
is not stored in the 24 hour SAPOSCOL buffer anymore. Actually the data is still collected by SAPOSCOL but only as a snapshot and we do need

the CCMS monitoring segment to store the data for a longer period. This can be done by using an ABAP report which reads the SAPOSCOL

snapshot data and stores the data in the CCMS monitor segment but this report only can be started each 5 minutes or this can be done by using a

SAPCCM4X agent and the agent can read the SAPOSCOL snapshot data every 60 seconds and sometimes even a little bit faster than this.

Installation and Configuration of SAPOSCOL:
http://help.sap.com/saphelp_nw70ehp1/helpdata/de/c4/3a6bff505211d189550000e829fbbd/content.htm

Operating System Collector SAPOSCOL:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/c4/3a6bff505211d189550000e829fbbd/frameset.htmk

1. sapcontrol -nr 00 -function GetVersionInfo

2. sapcontrol -nr 00 -function GetProcessList

3. sapcontrol -nr 00 -function J2EEGetProcessList

4. sapcontrol -nr 00 -function GetSystemInstanceList

5. sapcontrol -nr 00 -function ParameterValue SAPLOCALHOST

6. sapcontrol -nr 00 -function ParameterValue SAPPROFILE

After configuring the ADS service (as detailed in this document) it can happen that the service is not working. In that case, you can consult SAP Note 944221 - Troubleshooting if problems occur in forms processing. It contains several tips on how to solve possible issues. This note treats issues caused by a faulty configuration of ADS and not issues caused by ADS because of bugs or others that are solved by patching ADS.

Considering that ABAP related problems are handled by another person and that we actually want to verify a ADS problem, the section about Web Dynpro for Java scenario is more than enough to test ADS and verify its correct behavior. In that case, only the correctness of ADS installation is checked and not the whole setup, like sending the PDF back to the ABAP system.

The section that allows to only verify ADS is II Web Dynpro for Java. This specific section lists 5 areas to check:

1. Testing the user and password
2. Check the Web service destination ConfigPort_Document.
3. Check whether the credential is installed and configured.
4. Generated PDF with additional information
5. Activating ADS trace on the J2EE Engine

Its sufficient to verify ADS configuration by going through points 1 to 3. For the walkthrough I only consider NetWeaver systems higher than 7.11.

Step 1

Check the user and password of ADS.

• Go the the web services navigator: http://server:port/wsnavigator.
• Select Provider System and search for AdobeDocumentServicesVi

This should return the service interface AdobeDocumentServicesVi

Select the operation rpData

Leave the parameters as they are.

Click on execute and an authentication popup should appear. Enter the ADS credentials. Why the ADS credentials? The ABAP system is calling the ADS web service with these. If the ADS user and password are incorrect, the ABAP system cannot call the web service. WIthout this, no PDFs are generated. With this you also test if the ADS user is active. Sometimes it can happen the user ID and password are correct, but the user is disabled. In that case, the test of course also won't work.

Afterwards the web service should be executed and the result view shows some data.

What is of interest is the RpString VersionInfo. When it shows the version number of the ADS, it worked.

Result in above example => Worked. ADS credentials are correct.

Step 2

Check the Web service destination ConfigPort_Document.

This step depends on SAP Note1443819: Web Service Destination ConfigPort_Document does not exist. To see if the config port document and inspecition.wsil are set up correctly, the note suggests to use wsnavigator.

From there on, the same steps as in step 1. are executed.

Now, what the note does not mention is that the destination can point to a server not accessible by your browser. What does this mean? When you select the service interface from the logical destination.

If you get this error:

It is not allowed to access URL "http://server:port/AdobeDocumentServices/Config?wsdl&mode=ws_policy&style=document". Host "server" is not in the white list of Web Services Navigator and cannot be requested. In order to add it, go to http://server:port/nwa/middleware-settings and select tab WSNavigator or contact your system administrator.

What happens? The URL wsnavigator tries to call contains the name of the underlying web service server and that one is not available to you. The error message contains a hint on how to solve this problem: adding the server to the white list using the application found under /nwa/middleware-settings.

Add the server name to the while list:

Save the change and go back to wsnavigator. Now it should work.

Explanation

Why is this configuration actually necessary? Especially as the same web service works in step 2 but fails when the destination template is used? Isn’t the destination template also hosted on the local server? Well, there you have your answer. The destination template is a logical name that points to a WSIL file. Taking a look at the configuration of the destination template shows how this is done:

The URL parameter points to the actual server name where the inspection.wsil file is hosted. If this for instance is the internal server name of the NetWeaver Java system that is not available to your client, you`ll get an error during service invocation from wsnavigator. This also mains that you may put here a server name that is accessible to both the server and the clients.

Step 3

Check whether the credential is configured

“If you want to create interactive forms, you need a Reader Rights Credential (usage rights credential)”

• Only needed for Adobe Interactive Forms.

The other steps outlined in the note for the Java scenario help you to gather more information, but not directly on how to solve the problem.Step

Step 4 & 5

Not part of this document.

Here are the steps for BO 4.0 SP6 Installation on Windows. BO 4.1 is the latest version available at Marketplace.

Download media from Service Market Place

Extract file and run setup.exe

Choose a language for the setup program to use during the installation process. The language setting is used by the installation program to display information to you in the language of your choice.

The installation program checks for required components. Review the results and decide whether to continue with the installation, or abort and correct any unmet requirements.

If a dependency prerequisite condition is critical, the installation program will not allow the installation to proceed. If a missing or unsupported component is optional, you have the option to either continue with the installation or stop and correct the condition. The installation program will provide information on how to correct the condition.

Accept the License Agreement.

Enter Temporary Product Key. This can be found on SAP Service Market Place.

Permanent key can be provided later.

To install support for a language, select it from the list.

The Choose Install Type screen is used to select the installation component options.

We choose ‘Custom’.

Enter the path into which the installation program will install SAP BusinessObjects Business Intelligence platform. If the folder does not exist, the installation program creates it.

As a result of having chosen the ‘Custom Installation’ option we can now view the functionalities that have been installed and the ones that haven’t.

As per requirement, you can add the ones that do not get installed by default.

Disk Cost can be checked

Start a new installation

Enter a name and port number for the System Intelligence Agent (SIA) node.

Port 6410 is a standard TCP/IP port number reserved for use with a the BI platform SIA.

The name must consist of English alphanumeric characters (A-Z, a-z, and 0-9) and contain no spaces or other punctuation. The SIA name cannot start with a number.

This is the name that you will see in the Central Configuration Manager (CCM). Many CMS servers can be managed by a single SIA.

The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately.

Review the default value for the Central Management Server (CMS) port number. This is the port on which the CMS listens for incoming connections from the web application server, web server (if applicable), other CMS nodes (if applicable) and servers. The CMS must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately.

Port 6400 is a standard TCP/IP port number reserved for use with the BI platform CMS.

Enter the CMS Administrator password and CMS cluster key for the existing CMS host.

Communication between some CMS components is encrypted to provide a higher level of security. The cluster key must match the key entered on the existing CMS host, to which you are attempting to connect.

Provide passwords for SQL Server administrator and BOEUSER accounts

Kept the default ports for Tomcat

Kept the default port for WACS

If you chose to install the bundled Subversion version control system for use with Lifecycle Manager, confirm the port number and enter and confirm a password for the BI platform to use when accessing the Subversion repository.

The BI platform can integrate with your organization's deployment of SAP Solution Manager Diagnostics (SMD).

If required can be done later.

The BI platform can integrate with your organization's deployment of CA Wily Introscope Enterprise Manager. If required can be done later.

The Start Installation screen appears. Click Next to install.

Central Configuration Manager

Central Management Console Login

Provide credentials

Post-install diagnostic checks

You can run the Monitoring Tool at any time to run a diagnostics check and look for problems.

To access the Monitoring Tool in order to run diagnostic tests, log on to the Central Management Console (CMC), select the Monitoring screen, and click the Probes tab.

Now imagine the following situation. You are the administrator of a production system, and you encounter in the Process Overview (transaction sm50) a batch process, which already has been running several days and has been selecting data from a database table. This process is blocking other background jobs and you have to find out what this process is actually doing:

You can find this out very easily with the ABAP Runtime Analysis. You can use the ABAP Runtime Analysis (SE30) to trace programs which are running in a parallel session.

1. Ensure that you run SE30 on the same server as the running process!

2. You must create or adjust a trace variant for tracing the parallel process. Set aggregation to "None" again to get the Call Hierarchy.

3. Press the "Switch On/Off" button to trace processes running in a parallel session. The Runtime Analysis displays a list of the running processes similar to the Process Overview (transaction sm50).

4. Use the "Start measurement/End measurement" buttons to activate and deactivate trace.

Caution: Deactivate the trace again after short tracing time so that you do not reach the trace file quota! Before deactivating the trace, refresh the work process display. The dialog step that was active in the work process with the activated trace may have changed, and that deactivates the trace automatically.

5.  "Evaluate" button to analyze trace results.

identify the job that is long running and identify details like job class, workprocess that is executing the job

How to identify long running background jobs

2) Click on the job to view the display job screen. In the screen, click on job log to understand what is being performed by the job currently. This may give details like job is currently extracting some data packages or processing data packages etc

3) Identify the executing server and process id of the job from the step 1 and goto transaction SM50 of the respective executing server to view more details about the background job running.

Figure out the status of the job like On Hold or running from the process overview. If the job is On Hold, find out the reason for On Hold by examing the "Reason" column of SM50 transaction. Reason for On Hold could be due to CPIC/RFC/DEBUG/ENQ/PRIV/UPD etc.

Double click on the reason column for detailed information on the same and troubleshoot accordingly. If reason is RFC, check out which RFC it is referring to and cross check whether destination system is up or not and any other problems with that system.

• If it is ENQ, check out any lock issues like lock overflow etc
• If it is PRIV, check out for memory bottlenecks
• If it is UPD, check out whether any update issues
• If it is CPIC, check out for any network , gateway, message server and other communication problems

4) After performing step3, if you figure out job is not on Hold and it is in running state, then examine report column to identify what report/program is being executed by the job. Once you got the report/program details, figure whether it sap program or custom program and take actions accordingly.

5) Also examine Action and table columns in SM50 transaction of respective executing server to identify what is the action( roll in/roll out /Sequential read/Physical read/insert/update/delete etc)  being carried out by the job currently and what is the table on which action is being carried out.

If it is sequential read, figure out the cost of that sequential etc and consider for indexing etc. If it is physical read, check out whether there are too many swaps and consider resizing buffers accordingly. If you observed delay is due to high roll in/roll out, identify reasons for the same and tune buffer/memory parameters accordingly.

6) Once you get the table details on which action is being carried out, figure out        

•     How many records are existing in the table ?
•     Is this taking long time due to volume of records ?
•     Are there proper indexes on the table ?(If no proper index, consider index creation  by taking help of DBA )
•     Is the table having upto date statistics ? (If statistics are out of date,

              consider updating statistics of that table)

7) Consider debugging the process in SM50 ( Program/Session -> Program ->   Debugging ) to figureout the issue

8) Using ST05 or ST12, a trace can be taken for background job to figure out where exactly time is being consumed and to identify various cpu/memory bottlenecks or any buffer issues.

9) STAT/STAD transcation can be used to figure out what is the reason for high response time and actions can be taken accordingly

10) By taking help of ABAP er, even ABAP run time analysis can be done using SE30 transaction

By following the above steps, you can pin point the issue and take actions accordingly to minimize runtime of long running background jobs.

The SAP Passport is a single sign-on (SSO) Internet certificate.

It saves you time (you do not have to remember and type in your password) and it is a requirement to gain access to certain areas of the SAP portals (e.g. MMPor the PEC) or carry out certain functions (e.g. software download). This is why this is the first step you should take once you get your new S-User ID. 

However, passport is valid for 12 months only for security reasons so you will need to remove any expired certificates from your PC and install a new one after the 12 month period to continue to avail of this SSO certificate on our portals.

To Uninstall an SAP Passport

1.Open an internet browser window

2.Go to Tools and Internet Options

3.Click on the Content tab

4.Click on Certificates

5.Select the SAP Passport and click Remove

To Install an SAP Passport

1.Navigate to the SAP PartnerEdge Portal

2.Select Login Help (Top right hand side of the screen)

3.Under the header SAP Passport, Select Install

A pop-up window will appear, as shown in the image below. Please ensure
that you have allowed the browser to open the application in a new indow.

4. Enter your password for your S-ID number and click on “Apply for SAP
Passport”

Saposcol communicates with the "outer world" using the shared memory and reader-writer mechanism. To avoid situations when part of the data

red from the shared memory is from one collection interval and second one from another, there is exclusive lock for writing and for reading.

If there are a lot of readers, it may time-to-time happen that saposcol is not able to lock memory for writing.
  This message alone does not mean that you have some problems, this is just a problem that may happen in this case of communication and data exchange within one shared memory segment. But if you for example would have problems with failing calls to retireve data from ST06N transaction
#1692551 - Wrong log entry classification

Known:Warnings and error messages of dev_coll and possible problems with SAPOSCOL
http://scn.sap.com/community/netweaver-administrator/blog/2013/10/08/contain-of-devcoll-and-possible-problems-with-saposcol

SAPOSCOL Log Files
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c4/3a6c67505211d189550000e829fbbd/content.htm

Hello All;

This document describes how to schedule a backup in SAP ERP 6.0 System and how to send it to your backup server.

It also shows you how to prepare, and setup your backup server in order to make it ready to accept, and save the backups which are sent by your SAP System.

The systems that are used:

1- SAP ERP 6.0 EHP 5 running on Windows Server 2008 R2

2- Oracle 11.g

3- Backup Server is a Windows Server 2008 R2 with 1 TB space with 4GB of RAM

Step 1:

DB13 - Schedule of Backups

Go to your SAP System, and run the transaction code "DB13"

In this transaction you schedule the start time for your backup, and the type of the backup.

The following backup types are offered based on the need:

1) Whole database offline + redo log backup (best option - it includes everything)

2) Whole database online backup

3) Whole database offline backup

4) Whole database online + redo log backup

5) Full database offline + redo log backup

6) Full database online backup

7) Full database offline backup

8) Full database online + redo log backup

9) Incremental offline + redo log backup

10) Incremental database offline backup

11) Incremental database online backup

12) Incremental online + redo log backup

13) Partial database offline backup

14) Partial database online backup

In our case we will schedule one Whole database offline + redo log backup every Saturday at 9:00 PM, and one Whole database online + redo log backup every day at 9:00 PM.

To schedule a backup do the following steps:

1) Go to DB13

2) Double click on the day you want to start a backup in

3) In the next screen double click on the database type which you want to start

4) In the next screen specify the exact time when to start the backup

5) No click on the tab recurrences

6) Now make it to be every Day at 9:00 PM except for Saturday. This is for our cas, but in your case you can choose your own scenario which you want to follow.

7) The schedule must look like the following:

Step2:

Background Configurations

The main work will be on the file "initSID.sap"

The location of this file is under D:\app\Administrator\product\11.2.0\dbhome_1\database

In our case it is located under the D drive.

There are three parameters which need to be changes in this file, and they are:

• Backup_dev_type = disk

#This is the storage type of the backup

• Backup_root_dir  =  \\Backup server IP \File name which will hold your backup

# This is the location of the torage for the backups

• Compress = brtools

Make sure that you have enough space on your backup server. For example if your backup size is 150GB make sure that your backup server has more than 150GB disk space on the drive that you are sending your backup to.

Also make sure that your backup server is able to see your SAP server. To double check this point ping your SAP server from your backup server, and then ping your backup server from your SAP server.

Step3:

Mapping the drive of your backup server to your SAP server

In your SAP Server right click on your computer icon --> Map Network Drive

In the next step you will be asked to provide the IP of your backup server then the drive where you want to send the backup to, then click finish.

Step 4:

Check if your backup was finished successfully

To check if your backup was finished successfully go to your SAP system and run DB12. Here you will know the status of your backup.

This concludes the document. Hope it was helpful

Best Regards

~Amal Aloun

Saposcol communicates with the "outer world" using the shared memory and reader-writer mechanism. To avoid situations when part of the data

red from the shared memory is from one collection interval and second one from another, there is exclusive lock for writing and for reading.

If there are a lot of readers, it may time-to-time happen that saposcol is not able to lock memory for writing.
  This message alone does not mean that you have some problems, this is just a problem that may happen in this case of communication and data exchange within one shared memory segment. But if you for example would have problems with failing calls to retireve data from ST06N transaction
#1692551 - Wrong log entry classification

This warninig in dev_coll  was detected only under HPUX.

If this warnings appear approximately only once per hour, then according to the note 1692551 these warnings can be ignored.

There are several improvements in shared memory locking, shared memory communication mechanisms and time-consuming data

generation. It should in some cases improve the situation where several tools are attaching to same shared memory segment, where

saposcol acts as a writer and every CCMS agent (standalone sapccm4x/sapccmsr as well as integrated in sapstartsrv) as reader has

exclusive access.

The line "Collection Interval" should contain 60s value. If there is less, then please add the following line in the host_profile with which saposcol is running:

  hostexec/oscol/arguments = -w60

The message in log could be useful for the support to analyze data unavailability problems.

Hello Friends,

   Fallowing steps describes about SAP Kernel up-gradation from version 701 to 720 in Cluster High Availability environment.

Environment : Cluster - NODE-A and NODE-B, One Additional Instance.

Prerequisites:

1. Perform offline backup.

2. Create a SAPADM user with admin rights.

3. Download latest SAPCAR file

4. Download SAPHOSTAGENT

    SAPHOSTAGENT.SAR

5. Download SAP Kernel version 720 files from SMP.

    a. Database independent patch latest  - SAPEXE.SAR

    b. Database dependent patch latest - SAPEXEDB.SAR

    c. Br*Tool 7.20 patch 29 - DBATL720.SAR

    d. Oracle instant client - OCL10264.sar

    e. IGS - igsexe.sar

    f. IGShelper - igshelper.sar

    g.  SAPCRYPTOLIB - SAPCRYPTOLIB.SAR

    h. Classic RFC SDK - Classic RFC SDK 7.20

    i.  Microsoft C-runtime - vcredist_x64.exe

6. Download Cluster files from SMP.

    NTCLUSTER - ntclust.sar

Procedure(login as SIDADM):

    1. STOP all SAP and Oracle services in NODE-A, NODE-B and Additional Instance

    2. Stop the Windows Cluster Service in NODE-A, NODE-B

    3. Stop sapstartsrv service and deactivate in NODE-A, NODE-B and Additional Instance

         (Startup Type = Disabled) the servicesSAP<SID>_<INSTANCE no.>.

        SAPSID_00 -     NODE-A, NODE-B

        SAPSID_01 -     Additional Instance

    4. Stop and Delete SAPOSCOL in NODE-A, NODE-B and Additional Instance

    Execute below command at command prompt

        net stop saposcol

        sc delete saposcol

    5. Install SAPHOSTAGENT in NODE-A, NODE-B and Additional Instance

        a. Uncar SAPHOSTAGENT.SAR

        b. cd hostagent

        c. hostagent> saphostexec.exe -install (provide the SAPADM password while requesting).

    6. Backup old kernel files

        1. E:\usr\sap\SID\SYS\exe\uc\NTAMD64 and rename NTAMD64 as NTAMD64.save

        2. E:\usr\sap\SID\DVEBMGS00\exe

        3. E:\usr\sap\SID\D01\exe (Additional Instance)

    7. Create a kernel (NTAMD64) folder

    8. Restore below files form backup Kernel directory (NTAMD64.save)

        rfcexec.exe, rfcexec.sec, icu*30.dll or icu*34.dll

    9. Uncar below SAP kernel file in NTADM64 

        a. Database independent patch latest - SAPEXE.SAR

        b. Database dependent patch latest - SAPEXEDB.SAR

        c. Br*Tool 7.20 patch 29  - DBATL720.SAR

        d. Oracle instant client - OCL10264.sar

        e. IGS - igsexe.sar

        f. IGShelper - igshelper.sar

        g. SAPCRYPTOLIB - SAPCRYPTOLIB.SAR

    10. Uncar ntcluster and copy ntcluster /'Sap*.dll' files(3 files) in windows\system32(in NODE-A and NODE-B)

    11. Update Windows\SAPCLUSTER(in NODE-A and NODE-B) directory with the corresponding files in the central kernel staging directory(i.e., NTAMD64).

    12. Copy ntcluster/ disablewp.exe & enablewp.exe files in Kernel directory (NTAMD64)

    13. Uncar Classic RFC SDK 7.20 and copy rfcsdk\bin\librfc32.lib to in c:\windows\SysWOW64 and c:\windows\system32(in NODE-A, NODE-B and Additional Instance)

    14. Delete the files under  E:\usr\sap\SID\DVEBMGS00\exe and E:\usr\sap\SID\D01\exe (Additional Instance)

    15. Install vcredist_x64.exe in NODE-A, NODE-B and Additional Instance

    16. Run SAPCPE(SAPCPE will not be there in \work directory. Hence copy it from NTADM64 kernel directory.

        In Central Instance

    cd E:\usr\sap\SID\DVEBMGS00\work sapcpe pf=E:\usr\sap\SID\SYS\profile\SID_DVEBMGS00_dbSID

        In Additional Instance

    cd E:\usr\sap\SID\D01\work sapcpe pf=\\dbSID\sapmnt\SID\SYS\profile\SID_D01_Additional Instance

    17. Activate (Startup Type = Automatic) and start the Windows Services SAP<SID>_<INSTANCE no.>

        SAPSID_00 -     NODE-A, NODE-B

        SAPSID_01 -     Additional Instance

    18. Start SAP and database services.

    19. Run SGEN

    20. Done.

Regards,

Farkath C

Step 1:Login TO Solman System Hit SE38 TCode

STEP 2:  Run The  /TMWFLOW/RMOBASKETAPPROVAL Program

STEP 3: Select Desired File and Click Confirm Download.

After that go to the service market place and download the Approved file from Download basket.

Details Description of  SPAU & SPDD

1970888 - HowTo: SPDD/SPAU handling during the Update/Upgrade

Usually the Basis Admin do not carry out the SPAU/SPDD activities, they just send SPAU/SPDD text file to Developers.  But, in some organizations, Basis admin have to perform the SPAU/SPDD activities.  If you ever have to perform these activities, follow the instructions in this document.   I am covering most of the activities that I performed during Support Pack upgrade and  these steps would be more or less same with the system upgrade (EHP) as well.

Why SPAU/SPDD:

During an upgrade or the import of a Support Package, existing objects of the SAP standard are overwritten with the new objects.  To help the customer retain the changes to SAP objects done in a previous release, SAP provides the list of all modified objects which are redelivered (in an upgrade or Support Package). 

Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade. Using SPDD, we can
adjust Domains, Data elements, Tables, Structures.

Transaction SPAU allows you to adjust notes, programs, function modules, screens, interfaces, documentation, and text elements after
an upgrade. Notes should be adjusted before adjusting the rest of the modification to avoid errors in Note implementation due to modifications.

SPDD/SPAU activities will be carried out during the upgrade phase when it prompts for, otherwise whatever customizations
that we have done will be lost. Complete all modification adjustments before continuing with the import.

Perform SPDD Adjustments
Before performing these steps, open the system, go to SE06 and open the system for modification  Go to SCC4 and open client 000 with the  options: Automatic recording of changes Changes to Repository and cross-client Customizing allowed

SPDD STEPS:
Click Call SPDD when you get that option during SP/Upgrade
Go to the Adjustment Filter tab, and uncheck Adjusted, Click Execute
Expand the Entire Modifications and Enhancements tree
Save the <SID>_SPDD_ALL.txt file,  Select System, List,  Save, Local File, Choose unconverted, Generate the file

Adjust Dictionary Objects
Objects with Yellow Triangle
Click Yellow Triangle in Without Modification Assistant
For those with Green Dot and Current Version same as Proposed Version,
Continue, Accept Proposal, Reset to Original   ,  Yes
Create new transport and make a note of the transport

If you cannot reset the other objects, select the tree and click on Reset to Original icon

Click on refresh and all reset objects should be disappeared.

Leave the Deleted objects as is

Click on Assign Transport and provide the above transport number: This step only perform on Development systemGreen arrow back,       Confirm SPDD Adjustments,        Hit the truck icon to continue the Support Pack Upgrade

Monitor the job OCS_QUEUE_IMPORT jobs.  in SM37 or monitor your process in SM50. Another way to monitor your progress is to tail the most recent logs in /usr/sap/trans/SID/tmp tail -f <filename>

SPAU STEPS

Click Call SPAU when you get that option during SP/Upgrade
Go to the Adjustment Filter tab, and uncheck Adjusted, Click Execute
Expand the Entire Modifications and Enhancements tree
Select System , List , Save , Local File, Choose unconverted and click green check, <SID>_SPAU_ALL.TXT, Click Generate

Notes with Green Question Marks
Open another session, and go to transaction SNOTE
Just download all the note(s) with the green question marks again, do no try to implement.
On the SPAU session, select the menu option Goto , Determine Adjustment Modes
Click Execute
Click green check through all of the Format of correction instructions…. Screens
Click green arrow back to the SPAU screen
Click Refresh

Note: You should see all the notes with green question marks go to either gray or yellow dots.

Reset Notes With Gray Dots

Click on one of the gray dots to the left of the note, Click Reset
If you get the Format of correction instructions… screen, then this note might not reset to original, and that is okay
If you are prompted to download the note again, click green check and do the following
Once you get back to the SPAU screen, click on one of the gray dots again.  It will either get reset to original, or you it won’t and that is okay.

Reset Notes With Yellow Dots
Note: Before resetting these notes, evaluate if the note needs to be reapplied.  Read the note from SAP Service Marketplace and determine if the note was included in a support package that has been applied.  If that is the case then the note does not need to be reapplied.  If the note is coming in a future support package, then the note should be reapplied.  Do one of the following actions per note.

• If the note is to be reapplied, do these steps
Click on the yellow dot beside the note.  This will take you into SNOTE.
If the status is green, and the Message Text is Changes can be copied, then it will automatically apply.  If these conditions are true, then check the Copy Changes column, and click green check.  On the next panel, select all objects and click green check to activate, If status is not green, or the Message Text is not Changes can be copied, then further analysis has to be done.  Documenting that analysis is too complex.

• If the note is not to be reapplied, do these steps
Click on the yellow dot beside the note.  This will take you into SNOTE.

Note: On some occasions, you might not get to SNOTE, and the note will be labeled as cannot be implemented in SNOTE.  When that happens move on to the next note in SPAU.  You will set the status of all notes in SNOTE later.

Uncheck the Copy Changes column, and click green check
Answer Yes to the Are you confirming the correct implementation of the SAP Note?

Set the Note Status to Completed, Go to transaction SNOTE, Expand the In Processing section
For every note (from above) that has a green check, single click the note, and click the Set Processing Status icon.  Choose the Completed option, and click green check. 

For every note (from above) that has a gray diamond, single click the note, and click the Set Processing Status icon.  Choose the Not Relevant option, and click green check

Note: This is the list of objects that need to be evaluated to see if the Organization specific modifications need to be reapplied.

Select System , List , Save , Local File, Choose unconverted and click green check, <SID>_SPAU.TXT,Click Generate

Reset Remaining Objects to Original.

Note: If the object has a red dot, then you can ignore resetting it to original.  Do the following to reset the objects to original
Single click on the <Object Name>, Choose F9, Once all of the objects have been selected, click Reset to Original
Click green check to Do you want to reset the selected objects?
For each window titled Set Processor/Status that pops up, check the Completed check box for each line and click Copy

Click on Assign Transport and provide the above transport number: This step only perform on Development

Note: These are the steps to make the transport a modification adjustment transport to be used in subsequent systems.

Note: In QUA and PRD, provide the above transport when it prompts for  “Do you want to add Modification Adjustment Transports to the queue?  Click on yes, and provide the transport number.  You should see little or no objects show up in the SPAU/SPDD of QUA and PRD systems because of the modification adjustment transport was included in the modification queue.

Save the <SID>_SPDD_ALL.txt file

Support pack Modification Adjust Transport  warning "Transport does not fit.

I would like to share my recent experience with SPAM Modification Transport on the DEV system.  When we were going thru SPAM steps (display define queue, Target Package Selection), in the target package selection, some of the component did not appear.  This is obvious because we need to use SAINT in order to perform the delta upgrade and the new release level support packages. 

So after completing the SPAM including SPAU/SPDD transport, we performed the SAINT steps,  in the Support Package Selection screen, one of my colleagues forgot to select the latest Support Package Selection from the drop down and continue. So, when SAINT finished, it did not upgrade that particular component to the latest release level because of wrong selection in the Support Package Selection screen.

Since SAINT can only be used for Add-on, delta upgrade, and the new release level.  We had to perform SPAM steps again to upgrade that particular component to the latest release level that was missed in SAINT.  Finally we finished the SPAM and that component updated to the new release level.  Also, in this second step of SPAM, it did not prompt to create Modification adjust transport, because SPAU/SPDD was cleaned up in the first SAPM steps.

Mistake made:

So after performing the SPAM, SAINT and SPAM, we released the Modification Adjustment Transport and here we made mistake.  The released transport took the snapshot of the source release level, so in the subsequent system, you get warning “Transport does not fit”  when you try add Modification Adjustment Transport in QAS, PRD.  We continued SPAM with that warning and when it prompts to Call SPAU/SPDD,  click on call SPAU/SPDD and confirm SPAU/SPDD without making any changes and finally when SPAM finished, confirmed the SPAM Queue.  After confirming the SPAM queue, we manually imported the Modification Adjust transport, when you import click on options tab and tick all check boxes for  Ignore then proceed with the import process.  Go back to SPAU/SPDD and you should see everything clean and looks similar to DEV system.

So what we learned with the above experience is to immediately release the SPAM Modification Adjustment transport after confirming the SPAM queue and before starting SAINT.