Installation of Printer Drivers & Printer Configuration

Installation of Printer Drivers and addition of printer in SAP

 

Download Drivers

 

Download printer drivers for SAP from vendor site. Drivers will be in .PRI format and save it to local PC.

 

Uploading Drivers to SAP

 

You need to upload drivers into SAP. To do this go to TCode SPAD > Utilities > For Device Types > Export  (OR) Run report RSTXSCRP from SE38

 

 

In next screen click on radio button Device Type and provide object name usually this would be .PRI file name. Execute report .

 

 

Assign this object to a package and give person responsible name

 

 

This will generate a transport request. Once TR is created browse to driver path.

 

 

Create Printer for new device Type

 

SPAD > Output Devices > Display > Go to change mode and click on create button

 

 

Select device type from available devices from drop down menu under Device Attributes

 

 

 

Input all required field entries and Save Settings. You can transport this printer through request by clicking on truck button.

 

 

 

Read more...

Performing Effective SAP License Audit

In this blog I will describe process of performing sap license audit. For this SAP has standard tools for performing license consolidation. The measurement program contains counting modules that

​​

automatically calculate software engine use

​​

 

Useful Information

 

1.       To be able to measure all users in your SAP installation clearly and precisely, your systems, clients, and users must be classified according to current use and the price list they are based on prior to each system measurement. This classification reflects the terms of your contract.

2.       If you convert from a software components contract to a mySAP contract, users that are already classified must be reclassified according to the newly licensed user types.

3.       Disable multiple login in all system with parameter logon/disable_multi_gui_login=1 in default profile.

4.       Maintain same user id for a user across the whole landscape and maintain user master data properly for all fields. This makes easy while consolidating users at final step.

5.       Cleanup un used installations in service market place and maintain correct system type like ABAP,JAVA. You can delete un used installation numbers and systems by creating a support message to SAP under XX-SER-LIKEY

6.       License measurement need to be carried out for all systems including central system(Like Solution Manager).

 

Steps:

 

1.       Maintain price lists

 

Maintain price list according to your license agreement with SAP from tcode USMM.

 

 

2.       Download LAW file

 

a.       Classify the users of all systems according to their activity in the system

b.      Start transaction USMM > Start system measurement (F8). This will schedule background job and after completion of job you can see report under measurement statistics.

c.       Download the measurement results: System measurement à Export to LAW File

 

 

d.      Save the measurement data according to the proposed file name. Do not change file name here and proposed file name will be LicenseSID.

e.      Repeat above steps for all systems in your landscape.

 

3.       Uploading Results

 

a.       Execute transaction SLAW in a central system which can connect to SAP. Generally this system is production system or solution manager system.

 

 

b.      Import data of a system which was downloaded from all systems.

c.       Combine the different user records of one person. You can select condition on which thing you would like to combine users. i.e By User Name, First Name, E-Mail Address

d.      Consolidate to a resulting user type

e.      Send the consolidated data to SAP. Make sure RFC SAPOSS and SDCC_OSS are working properly so that data can be transferred immediately.

 

4.       Find the results

 

log for the LAW data transferred via menu path  Measurement Data à Send Results à Results Log à Create Results Log

 

The LAW results are structured in

·         List of installations and systems consolidated

·         Consolidated measurement results for engines

·         Consolidated measurement results by user type

·         LAW Customizing data Measurement log for each system

 

References

 

Note 142724 - Prevention of multiple SAPGUI logons

 

Read more...

Could not retrieve a password for credential: ReaderRights(200,101)

Error:

Could not retrieve a password for credential: Reader Rights(200,101)  while accessing adobe interactive form.

You have got error while testing interactive form report FP_TEST_IA_01

Resolution:

This error usually comes when there is mismatch between adobe credentials certificate or there are no certificates are installed in your system.

Installing and Configuring Credentials

Requesting Adobe Credentials :

Open an SAP customer message under the component BC-SRV-FP-ICF. In the message text, write that you require a credential for the Adobe Interactive Forms scenarios. In the message, include an e-mail address to which the credentials can be sent. The persons responsible will then contact you directly.

Note that only one credential can be assigned for each customer number. The credentila is valid for all Adobe Document Services installations for this customer number. The credential you will receive is a PKCS #12 (.pfx) file that you need to install and a .txt file which contains password.

Installing a PKCS #12 Credential

Once you receive your PKCS #12 credential file, you must install the file in the appropriate location on your file system.  Upload  the credential file (<filename>.pfx) to the /usr/sap/<SAPSID>/SYS/global/AdobeDocumentServices/TrustManagerService/trust/credentials directory.

Configuring Credential Attributes used by ADS

From Visual Adminstrator tool Navigate to Cluster > Server 0 > Services > Document Services Configuration and add credentials as follows. Use Alias as "ReaderRights". Browse the file from /usr/sap/<SAPSID>/SYS/global/AdobeDocumentServices/TrustManagerService/trust/credentials and select .pfx whilch you have receive.

Maintain Same Alias and password under tab Passwords and click on Add.

This is optional. If not you will be ended with error

Credential login error while applying rights to pdf

Restart Services -  Document Services Trust Manager Service and Pdf Manipulation Moule .

Restart Java Instance from Tcode SMICM > Administration > J2ee Cluster Global > With Restart.

After java stack is restarted execute report FP_TEST_IA_01 with ADS connection.

Once the connection is successful you will get pdf file opened in SAP GUI.

References:

SAP Notes

Note 944221 - Troubleshooting if problems occur in forms processing

Note 736902 - Adobe Credentials

Note 894009 – ADS: Configuration Guide (NW 7.0)

Note 685571 – Printing pdf based forms

SCN Documents

http://scn.sap.com/docs/DOC-26143

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30a9630b-4f89-2a10-6fab-e311b3ffd9a6?overridelayout=true

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f03414f8-d4ce-2a10-d4b6-ab201b329d98?QuickLink=index&overridelayout=true&26160645819923

http://help.sap.com/saphelp_em70/helpdata/en/db/aafb211ead420faeeaa24e99eb5f41/frameset.htm

Request temporary key at following url

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70aa75cc-6ac3-2910-c78c-ade192ec861e

Read more...

Business Objects Business Intelligence SP level Update SP04 to SP06

Business Objects Business Intelligence SP level Update SP04 to SP06

 

Current Environment:

Operating System           :               Windows 2008 Enterprise SP1

BOBI Package Level       :               BOBI 4.0 SP04 FP03

Product Version              :               14.0.3

Processor Architecture

​   ​

:

​           ​

AMD64 – X86

 

Target Environment:

BOBI Package Level        :               BOBI 4.0 SP06

Product Version               :               

 

Download Components

https://service.sap.com/swdc > Support Packages and Patches  > Browse our Download Catalog > Analytics Solutions > SBOP BUSINESS INTELLIGENCE PLATFORM (SBOP ENTERPRISE) > SBOP BI PLATFORM 4.0 > Comprised Software Component Versions > SBOP BI PLATFORM SERVERS 4.0 > Windows on x64 64bit > Download relevant package

 

CD Numbers Required

ENTERPRISE06_0-20007504.EXE                 SBOP BI Platform Servers 4.0 SP06 

 

 

After extraction of patch it will do pre requisite check and will provide you if any missing pre requisites are missing

 

 

Proceed with next and it will guide you with the help of wizard

 

 

 

Kindly check the port of CMS. This you can get it from url http://hostname:port/BOE/CMC and pass the credentials of CMS Admin User

 

 

It will deploy all required components

 

 

Once installation of patch is completed you will prompted success screen.

 

 

Checking Component Release

 

You can check target component release by loggin into CMC http://hostname:port/BOE/CMC  > Settings >

 

 

 

You can get SP level of product version from

 

SAP Note 1602088 - Which version number corresponds to which patch / SP / FP for SAP Business Objects BI 4.0 ?

Read more...

Access SAP Webgui and Portal Through Internet Using Web dispatcher

Summary

                This document describes installation and configuration to be performed to access webgui and other java stack urls to be accessed from internet without exposing your system directly to internet and making use of web dispatcher.

Applies To:

Software Provisioning Manager 1.0 SP03

SAP Netweaver 7.0 and above

Windows Server 2008

 

Introduction

The SAP Web dispatcher lies between the Internet and your SAP system. It is the entry point for HTTP(s) requests into your system, which consists of one or more NetWeaver application servers. As a "software web switch", the SAP Web dispatcher can reject or accept connections. When it accepts a connection, it balances the load to ensure an even distribution across the servers. The SAP Web Dispatcher therefore contributes to security and also balances the load in your SAP system.

You can use the SAP Web dispatcher in in pure ABAP systems as well as in combined ABAP/Java systems ("dual-stack" systems), and in pure Java systems.

 

Preparation

It is advisable to install SAP web dispatcher on a machine which is different from SAP landscape. This setups your DMZ zone which required for dispatcher configuration and make sure both networks are reachable to each other.

Your web dispatcher should have public ip or it should have natted public ip address so that it can be accessible from internet and open ports required.

Maintain host entries of sap ecc system in web dispatcher system host file.

Installation

On windows systems perform installation with sapinst and required services will be created by sapinst only.

Download software provision manager from http://service.sap.com/sltoolset  and corresponding kernel from service market place.

Launch Sapinst.exe and navigate to SAP Netweaver 7.3 > Oracle > SAP Systems > Standalone Engines > Web dispatcher.

Select parameter mode as prompted. If you would like to install in advanced mode select Custom. Input your web dispatcher SID and installation drive.

Give Inputs as prompted by sap installation master and proceed further. This completes installation of web dispatcher. 

 

 After completion of installation new instance will be created in sap management console.

Webgui Administration

Administration console can be accessed from following url

http://<webdisphost>:81<webdisp inst number>/sap/admin

Default user name will be webadm and same can be found from usr\sap\SID\SYS\global\security\data\ icmauth in encrypted format.

Configuration

Initially your requests from internet will come to web dispatcher host and from here they will be redirected to your webgui. For this open the ports which you want to access from outside.

Maintain following parameters in instance profile

 

icm/server_port_0 = PROT=HTTP,PORT=6666,TIMEOUT=60,PROCTIMEOUT=600

icm/server_port_1 = PROT=HTTP,PORT=7777,TIMEOUT=60,PROCTIMEOUT=600

                         

This mean your requests for first server will be received on port 6666 and for second server requests will be received on port 7777. All these requests need to be transferred to your target url. For this add following parameters to instance profile. i.e. Requests received on port 6666 will be directed to your first server on port 8100.

 

wdisp/system_0 = SID=DEV, MSHOST=dev.yourdomain.com,MSPORT=8100,SRCSRV=*:6666

wdisp/system_1 = SID=PRD, MSHOST= prd.yourdomain.com,MSPORT=8100,SRCSRV=*:7777

 

SID - SID of ABAP system

MSHOST - Host name ABAP system

MSPORT  - Port number of message server. This can be obtained from dev_ms of abap server.

 

You can access webgui from internet using following urls. To be access these url with domain name maintain host entry webdispatcher and public IP or resolve it DNS server.

 

http://webdispatcherhostname.abcd.com:6666/sap/webgui

http://webdispatcherhostname.abcd.com:6666/irj/portal

 

Resources

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/8fe37933114e6fe10000000a421937/content.htm?frameset=/en/48/8fe37933114e6fe10000000a421937/frameset.htm

SAP Note 552286 - Troubleshooting for the SAP Web Dispatcher

​​

SAP Note 538405 - Composite SAP Note: SAP Web Dispatcher

 

Read more...

552 4.3.1 Message size exceeds fixed maximum message

Error

 

While sending mails from SAP with big attachments in size error comes "52 4.3.1 Message size exceeds fixed maximum message"

 

 

Environment

 

ECC 6.0,  Windows SMTP relay server

 

Resolution

 

This error persists because it has reached maximum mail size can be transmitted through SMTP relay server. To resolve this we need to increase maximum mail size limit in relay server.

 

Login into SMTP relay server > Launch IIS Manager ( Run > inetmgr6 ) > right click on SMTP note > Properties and navigate to message tab > Increase file size in 'Limit message size'

 

 

 

Read more...