If requirement comes to you that business needs a beep sound in RF console when it scans a bar code this is what you should do.

Step 1: Stop laughing
Step 2: Follow note 371838

Suppose we have a standard SAP function module issuing an error message because of invalid input data. Now if we are calling this function module from any custom conversion program and such an error message is issued by the function module, the entire processing would stop and program would terminate displaying this error message. In case of a background job, it would also show an error and abruptly stop.

In order to handle such scenarios, we can provide an additional parameter in the function module exception called 'ERROR_MESSAGE' and give a sy-subrc value to it. This should be before the normal OTHERS parameter.

Now when the error is issued in the function module, the program doesn't terminate immediately. But the SAP function module returns with the SY-SUBRC value corresponding to the ERROR_MESSAGE exception.

Also the error message details can be found in the standard system message fields (SYST structure) and can be used by the custom program to populate any processing log / report.

For Purchasing transaction exits, you may use table entries like T160 or T180 to find the nature of transaction.
Field - TRTYP (Transaction type)

4) Enter the system name as “CLNT “E.g.: TP6CLNT800

*to get WAS Host name, WAS Path and WAS protocol settings using the function Module RSBB_URL_PREFIX_GET (Transaction SE37)

* The property BI Master System means that the BI system is the central Persistence storage for the portal. The BI Master system is used to read and execute Web templates. The Running BI Web Runtime requires exactly one BI Master System within the portal.

* Information about the R3 ABAP system can be obtained through transaction smms

* Select “Permissions” for the newly created system and ADD “Everyone: group and set “Read” access to the Administrator and select: End User” checkbox.
8) Create 2 System Alias: PW3CLNT800 and SAP_BW and choose the former one as the default.




Export BI certificate from the BI system.
1) Goto Transaction “strtustsso2” in BW system and double click on Own certificate



2) Click on the Export Certificate button as shown.


3) Give the name to the certificate as “certificate.crt” and save the certificate.Choose the file format as Binary



Import the portal Certificate to the BI system.

1) In the portal navigate to System administration-> System configuration-> KeyStore Administration.


2) Save the certificate at the desired location.Choose the format as Binary



3) To include the certificate in the SSO Access Control list (ACL)Click on “Add to Certificate List”



4) Click on “Add to ACL”


5) Now the Certificate gets included in BI system.



Create RFC Destination in the BW system.

The BI system uses the RFC destination to communicate with the portal.
1) Start Transaction SM59
2) Type: T for TCP/IP connection.





Create RFC Destination in J2EE Engine.

1) Open the Visual administrator in portal system. Go to Server -> services ->JCo RFC Provider->select the existing connection and edit the properties as below.

** Program Id should be the same as the program Id specified in the RFC destination.



2) Select Security Provider-> Evaluate Assertion Ticket -> Click on Edit ->Click on Modify-> Enter the properties as shown below.



Import the BW certificate into the J2EE Engine
1) Start the Visual Administrator Tool.
2) Select the /Server<#>/services / key Storage -> TicketKeyStore->SAP Logon Ticket -> Load -> select the certificate to be exported from the BW system.



Create the JCO connection in portal system.

1) Logon to the portal.
2) Navigate to Content Management ->Web Dynpro -> Maintain JCo Destinations-> Create JCo destination for BI-METADATA, BI_MODELDATA, and WD_ALV_MEATADATA_DEST AND WD_ALV_MODERDATA_DEST
3)Click on create.
4)Enter the Name: BI_METADATA
Client: 800


5) Select “Use Local J2EE engine “JEE on XXX\j2e””. Click Next.



6) Select Data Type: Dictionary Meta Data



7) Maintain the details of the Message Server: TP6 XXXX
Logon Group : Public



8) Specify the ABAP user id and Password


Adding permissions to the IViews.
1) Go to Content Administration->Portal Content->Content provided by SAP-> platform Add ons-> Business Intelligence -> Iviews -> select each of the IViews and add “Everyone “ group to all the iviews.


Connected Portal Details

Use transaction “SM30”; enter the Table name “RSPOR_T_PORTAL”.
Click display. Select the RFC Destination created Earlier . click on New Entries.



Configure User Management in the portal.

1) Go to System Administration->System Configuration->UME configuration
Make the following Entries:
Under Data Sources tab.



Under ABAP system tab.



Under User Mapping Tab.



Set up Repository Manager for BI Documents and BI Metadata.

In this activity you can set up the BI document and BI Metadata Repository manager.
Execute the following steps to set up a Repository manager for BI in the portal.

1) Logon to the portal
2) Start iview System administration -> System Configuration ->Knowledge management –>Content Management .
3) Choose Content Management->Repository managers.
4) Under Classes, choose BI document Repository.
5) Create a new instance of the BI Document Repository.
6) Enter the following entries.
Name: unique name of Repository Manager.
Alias of BW system:
Prefix: < BI_DOCUMENTS_PREFIX>(eg: /bi_documents)
Active: X
Security Manager: BWDocumentSecurityManager.

8)Choose OK to save the settings.


Repeat the last 4 steps for BI Metadata Repository.

Maintain User assignment in the portal:
In this activity you assign a user in the BI System to a user in the portal.
Execute the following steps to maintain user mapping in the portal.
1) Logon to the portal
2) Start the iview User Management -> User mapping.
3) Choose User from the dropdown box.
4) Search the user (Administrator)
5) Choose modify
6) Choose the tab User Mapping for system Access.
7) From The system dropdown select the BI system Created.
8) Under the Mapping Data enter the userid (ABAP user) and its Password.
9) Save the entries.



Possible Problems that might arise and its solution:

1) If connection to BI system could not be established because the message server port was not known on the system.
To make this port known, there must be an entry in the file C:\WINDOWS\system32\drivers\etc\services.

2) Any Changes that you make in the config tool should be made under the Global Configuration Settings and not under Instance specific settings.

3) After Unistallation of SAP System, check the registries, as some of the entries might not have been removed by the uninstaller.
So during reinstallation, the installation process may fail due to this.

4) In case of JMSSecurityException, refer to the following note: 971249.

Prerequisites


For the comunication of your Solution Manager with SAP ,ensure that the following prerequisites are fullfilled

Transaction: OSS1



If you have problems with the connection test of SAPOSS you can check and maintain settings for the connection in transaction OSS1. The RCF SAPOSS will be adapted automaticlly after change of configuration in OSS1.



For transaction OSS1 and RFC connection SAPOSS in SAP Note 17285

S-user Authorizations

URL: http://service.sap.com/user-admin

You can check the authorization objects of your Solution Manager S-user with the „Authorization reports“. Please ensure that your S-user has at least the marked authorization objects.

Check of Prerequisites Support Package LevelsPlease ensure that all support package levels for the managed systems (satellite systems) are up to date according to SAP Note 1274287.
Please also check if the mentioned SAP Notes are applied in the managed systems.

Check of Prerequisites Client Copy

SAP delivers standard Solution Manager configuration in clients 000 and 001.
but it always recommended is to create a productive client and keep the master client original. It is also recommend to create an additional client for the BI Content because it is more secure to work only with communication users on BI data and it’s easier for root cause analysis in case of problems.

Therefore please create a new productive client (and also consider creating a separate BI Client) and perform the client copy using profile SAP_ALL with 000 as the source client and 001 as the source client for users

Check of Prerequisites Client Copy – Convert UME
After you created a new productive client you need to convert the Java user store to the new productive ABAP client. Please ensure that you entered 001 as “Source Client User Masters” for your Client Copy. Without the standard java users from 001 the Java engine will not start after converting UME!

You can find a detailed description in the IMG (Implementation Guide - transaction SPRO) in the tree Basic Settings -->General Settings -->Convert UME



Basic Settings - Initial Configuration

Here we do following steps :-

User Administration
Create an Solution Manager administration user
Create an Business Partner for this user

Technical Configuration
Initial technical configuration

SLD Configuration
Start the automatic SLD Configuration
Read System Data into Solution Manager SLD

Basic settings – General Configuration SAP Solution Manager IMG



t-code :- SPRO

The IMG tree contains all Basic Setting and Scenario- Specific Settings for your Solution Manager.
Always up to date implementation guideline
Automated configuration wizards can be used



The Central Correction Note is used to bundle all notes that are necessary for the scenarios set up by the basic configuration of SAP Solution Manager. It can be implemented at 1 with transaction SNOTE or as part of the automated procedure at tab Information:- Guided Procedure for Automated Basic Configuration.

Basic Settings - Initial Configuration New Guided Setup Wizard for Basic Configuration


New guided setup wizzard for Basic Configuration
Transaction: SOLMAN_SETUP



If you start the SOLMAN_SETUP for the first time, you will be asked to activate Web Dynpro Services to display the wizard in your browser screen.

Transaction: SOLMAN_SETUP


Start the activity “Initial Configuration – User Administration“
User Administration

Solution Manager Administration user will be created


User SOLMAN_ADMIN is created with the authorization profile ZSAP_SOLMAN_ADMIN

When the option Add Authorization for Note Implementation is selected,
it gives the specified user the authorization S_DEVLOP

If an administrator user already exists we can use that user and
adjust its authorizations using Only Update Authorizations
A Business Partner will be created for the user
The two roles Business Partner (Gen) and Employee will be assigned to
the user SOLMAN_ADMIN

Business Partners will be used for Solution Manager Scenarios like Service Desk
And Change Request Management



Ensure that SAP Note 1236420 is implemented and profile generation is filled
(transaction SU25 --> Initial Fill of Customer Tables).
Fill out the User data and click on “Execute”.
If a user already exists you can give the username and just click “Update Authorizations Only”
When CUA, is active you might get an error while creating/maintaining users.
In this case you can manually create a administrator user and assign the
role ZSAP_SOLMAN_ADMIN and skip this step



Transaction: SOLMAN_SETUP



Start the activity “Initial Configuration – Technical Configuration“

Technical Configuration

Some initial technical configuration will be done, for example modeling
the Solution Manager system in the system landscape or activating the
Service Data Control Center (SDCCN).



Just click on the button “Configure” to start the automatic Technical Configuration.

Check the Log area for warnings or errors.
Transaction: SOLMAN_SETUP


Start the activity “Initial Configuration – SLD Configuration“

To work with the tools of the Solution Manager we need technical information about the connected systems in the Solution Manager System landscape (SMSY)

To avoid manual maintenance, the Solution Manager uses its local SLD to read systems information like servers, databases, system component levels, application servers, support pack levels etc

You can connect the local Solution Manager SLD to a central SLD, which is the central information source for the system landscape. But the Solution Manager should be independent of the central SLD, to be available in the absence of SLD.

Configure Local System Landscape Directory
The Solution Manager uses its local SLD to read technical system information

Read data from SLD
Once the local SLD is configured you can read the data from the local SLD and update the system definitions in SMSY




Read SLD:
This step will reads data from the local SLD by running a background job RSGET_SMSY and updates the systems information in SMSY. Please remember that you have to ensure that the data is available in Solution Manager SLD before you can read the data for SMSY.





1. Provide ABAP and J2EE Administrator Users and Passwords

2. This step will create technical users for SLD

3. Deselect the option Generate Passwords and specify a password for
the technical SLD users.

4. Click Next to complete the SLD Configuration.

When you provide SOLMAN_ADMIN username/password make sure that you
logon as SOLMAN_ADMIN though SAP GUI and change the initial password.

After configuring the local Solution Manager SLD and before reading the SLD data for Solution Manager System Landscape (transaction SMSY) you have to think about how to get data in the Solman SLD.
That means at first you have to check if your system data is already available in a central SLD
(e.g. in an PI system) or if you like to use your Solution Manager SLD as central SLD.



Managed System Configuration for a ABAP system ---continued on next blog..