Here’s how it goes.

Trying to access the table

When trying to maintain a certain table, the user will receive the following warning:

Sending a system message using a standard SAP function module

Once you’ve identified the user, access SE37 – assuming you have permission! In SE37 call SAP standard function module TH_POPUP.

Fill in the following input parameters:

- CLIENT: the system client on which you’re working on. If you don’t know this, take a look at the lower right status bar;
- USER: the user for which you want the message to be delivered;
- MESSAGE: the text message you want to deliver to the user;
- MESSAGE_LEN: allows you to define a message length. Leave it empty;
- CUT_BLANKS: allows you to specify if you want to trim existing spaces. Leave it empty.

To submit the message just hit “Execute (F8)”

What the user receives

When you click on “Execute (F8)”, the destination user receives the following message as a pop-up:

This is just a simple system tool that can help you in a day to day basis, working with SAP.

First of all, and for the beginners’ sake, I want to start by defining what is a SAP Support Package. In the same context, it is also important to understand what is a SAP Online Support System (OSS) Note. On a normal day, in the more than 140.000 SAP system installations worldwide, errors occur within these systems. Normally business critical situations happen less frequently but since SAP is composed by several pieces of software designed by humans, divided into Application Areas or Modules, there are quite a few bugs, errors and misconceptions which go through to clients’ live systems.

So SAP provides a support portal on which clients can report these situations, categorizing them accordingly and assigning them with a different priority (most frequent are medium and high). The way these tickets are dealt with is also according to the type of agreement the company has with SAP – the bigger SAP clients usually have little response time. But they pay for it.

The so called Online Support System – OSS – is the system SAP uses to manage these tickets and interaction flow with the Clients.

SAP Notes

When an identified issue is considered by SAP as a software defect, it will be solved by change of code, table configuration, etc, and it’s correction will be issued by SAP in the form of a SAP Note. SAP notes are an excellent way to keep our systems up to date with SAP so it’s a common task for a SAP Basis administrator to make sure the systems he works on are aligned with the most current versions implemented. Typically, large companies have predefined dates on which they apply what we’ll cover on the next point – the Support Packages.

SAP Support Packages

SAP Support Packages are bundles or collections of SAP notes (typical volume of grouped notes is 200). They’re also referred to as “Support Pack (SP)”. Support Packages are compiled periodically and are a set of SAP applications or specific components which are made available in the SAP Support Portal. SPs can be implemented using basis transaction codes like SPAM (Support Package Manager) or SAINT (SAP Add-On Installation Tool). For the JAVA stack of WAS a tool called Java Support Package Manager (JSPM) is used for SP deployment. So it is already clear that as a Basis Administrator, you will have to deal with the ABAP Stack (for the backend) and the JAVA Stack (for the front-end).

Before starting with the Support Package Stack (SPS) upgrade, please make sure to cover the following points:

1. Ensure that a full back of the system up has been performed.
2. Read thoroughly the related SAP documentation. I recommend that start by reading the standard SAP documentation available in the SAP Support.
3. Lock all SAP users except the ones used for the upgrade during the entire process.
4. Ensure that the front-end server is in the correct version of the JAVA runtime environment.
5. Ensure that you have the correct patching on the Oracle database.
6. You should also have a complete check-list of whatever cut-over activities you’ll need to perform after the SP upgrade. A Z developments inventory is also a good idea.

Preparation and organization play a critical part in this process!

On my next post I’ll describe the Support Package Upgrade process step by step, covering the SPAM execution, the ABAP Stack, the JAVA Stack and the Kernel Upgrade.

Please comment and visit SAPLAB.org for the rest of the series. Thanks!

Example: The product version SAP NetWeaver 7.0 is structured into the instances ‘Application Server ABAP’, ‘Application Server Java’, ‘Enterprise Portal‘, ‘Frontend’ etc. The ‘Application Server ABAP’ itself consists mainly of the software component versions SAP BW 7.00, SAP ABA 7.00, SAP BASIS 7.00 and SAP Kernel 7.00 32-BIT (or a newer downward compatible one).

Please note that you will need a valid SAP OSS user in order to access SAP’s Product Availability Matrix (PAM) website.

In case you don’t have a company issued SAP user, here’s your opportunity to get the SAP NetWeaver 7.0 Product Availability Matrix (PAM) document, just click on the download link below.

For anyone who doesn’t know this fact, from version 7.5, SAP DB is distributed under a new name which is MaxDB.

If your scenario is a fresh installation of Netweaver Developer Workplace but the MaxDB version doesn’t suit your needs, please take a look at the steps below, it will help you to learn how to install or drop a MaxDB instance.

1. How to install a MaxDB Instance

Start by creating a new database instance and specify the First Database Manager Operator:

dbmcli db_create <database_name> <DBM_user>,<DBM_password>

At this stage, you will have several different options to consider, depending on your needs and objective:

If you have more than one version of the database software installed, you must specify the version to be used, indicating the option:

-R <dependent_path>

To install a new database instance remotely, use the following option, to specify the remote computer and identify yourself towards the operating system of this computer:

-n <server_node>
dbmcli -n <server_node> db_create <database_name> <DBM_user>
,<DBM_password> <OS_userid>,<OS_password>

In case you use a Unix operating system, it doesn’t distinguish between remote and local communication. Therefore, you always must identify yourself towards the operating system. If you create a new database locally, you can avoid the identification using the option -s:

dbmcli -s db_create <database_instance> <DBM_user>,<DBM_password>

Use a Database Manager CLI script to complete the installation.

dbmcli -d <database_name> -u <DBM_user>,<DBM_password> -i <script_file>

Sample script:

param_startsession
param_init
param_put MAXUSERTASKS 5
param_checkall
param_commitsession
param_addvolume 1 LOG LOG_001 F 2000
param_addvolume 1 DATA DAT_001 F 10000
db_admin
util_connect
util_execute INIT CONFIG
util_activate <SYSDBA_userid>,<SYSDBA_password>
util_release
load_systab -ud <DOMAIN_password>

Of course you should change the parameters to suit your own needs. User SYSDBA is the first Database User, which is able to create additional users for the new database instance.

2. How to drop a MaxDB Instance

Start by stopping the database instance

dbmcli -d <database_instance> -u <DBM_userid>,<DBM_password> db_stop

Delete the database instance on the database server

dbmcli -d <database_instance> -u <DBM_userid>,<DBM_password> db_drop

The result is the deletion of the database instance.

SU01 – User Maintenance
SU01D – User Display
SU02 – Maintain Authorization Profiles
SU03 – Maintain Authorizations
SU05 – Maintain Internet users
SU10 – User Mass Maintenance
SMLG – Maintain Logon Group
SUPC – Profiles for activity groups
SUIM – Info system Authorizations
PFCG – Profile Generator
PFUD – User Master Data Reconciliation

Client Administration:

SCC3 – Checking Client Copy Log
SCC4 – Client Administration
SCC5 – Client Delete
SCC7 – Client Import Post-Processing
SCC8 – Client Export
SCCL – Local Client Copy
SCC9 – Remote client copy

Database Administration:

DB01 – Analyze exclusive lock waits
DB02 – Analyze tables and indexes
DB12 – DB Backup Monitor
DB13 – DBA Planning Calendar
DB15 – Data Archiving: Database Tables

Transport Management System:

STMS – Transport Management System
SE01 – Transport and Correction System
SE06 – Set Up Workbench Organizer
SE07 – CTS Status Display
SE09 – Workbench Organizer
SE10 – Customizing Organizer
SE11 – ABAP/4 Dictionary Maintenance
SE16 – Data Browser
SE80 – Repository Browser
SM30 – Call View Maintenance
SM31 – Table Maintenance

Background Jobs Administration:

SM36 – Define Background Job
SM37 – Background Job Overview
SM39 – Job Analysis
SM49 – Execute External OS commands
SM62 – Maintain Events
SM64 – Release of an Event
SM65 – Background Processing Analysis Tool
SM69 – Maintain External OS Commands
Spool Administration:

SP01 Output Controller
SP11 TemSe directory
SP12 TemSe Administration
SPAD Spool Administration

Other Administration Tcodes:

AL11 – Display SAP Directories
BD54 – Maintain Logical Systems
OSS1 – Logon to Online Service System
SALE – IMG Application Link Enabling
SARA – Archive Management
SICK – Installation Check
SM14 – Update Program Administration
SM35 – Batch Input Monitoring
SM56 – Number Range Buffer
SM58 – Asynchronous RFC Error Log
SM59 – RFC Destinations (Display/Maintain)
SAINT – SAP Add-on Installation Tool
SPAM – SAP Patch Manager (SPAM)
SPAU – Display modified DE objects
SPDD – Display modified DDIC objects
ST11 – Display Developer Traces

Daily monitoring TCodes:

AL08 – Current Active Users
SM12 – Display and Delete Locks
SM13 – Display Update Records
SM21 – System Log
SM50 – Work Process Overview
SM51 – List of SAP Servers
SM66 – System Wide Work Process Overview
ST22 – ABAP/4 Runtime Error Analysis
ST01 – System Trace
ST02 – Setups/Tune Buffers
ST04 – Select DB activities
ST05 – Performance trace
ST06 – Operating System Monitor
ST10 – Table call statistics
ST03 – Performance, SAP Statistics, Workload
SU56 – Analyze User Buffer

Other Monitoring Tcodes:

OS01 – LAN check with ping
RZ01 – Job Scheduling Monitor
RZ03 – Presentation, Control SAP Instances
ST07 – Application monitor
STAT – Local transaction statistics

Other Useful Transactions Codes:

AL22 – Dependent objects display
BAOV – Add-On Version Information
SA38 – ABAP reporting
SE38 – ABAP Editor
HIER – Internal Application Component Hierarchy Maintenance
ICON – Display Icons
WEDI – IDoc and EDI Basis
WE02 – IDoc display
WE07 – IDoc statistics
WE20 – Partner profiles
WE21 – Port definition
WE46 – IDoc administration
WE47 – Status Maintenance
$TAB – Refreshes the table buffers
$SYNC – Refreshes all buffers, except the program buffer

The author excluded ABAP generated by special frameworks, like Report writer, SAP Query, Web Dynpro, LSMW,  and so on. He opted to do the filtering by Source System, Owner and Package. The release covered by this tool is ECC 6.0 an the following are also out of scope of this tool:

• BSP’s
• Adobe Forms, Smartforms and SAPScript
• XSLT/Web Services

This utility was named ZSDN_simple_ABAP_SLOC_COUNT, and aims to be an an indicator. The author didn’t want to give it too much relevance, the idea is solely to be an useful tool and help us estimate the upgrade effort or to evaluate the amount of work allocated for each of our packages.

As a curiosity, the post also includes the following information, related to lines of code in known software systems:

• Windows XP:      45 million lines of code
• Windows Vista:  50 million lines of code
• Mac OS:              86 million lines of code
• SAP (ABAP):      238 million lines of ABAP

Copy the code from the textearea below and paste it in a new report in transaction code SE38.

*&---------------------------------------------------------------------*
*& Report  ZSDN_SIMPLE_ABAP_SLOC_COUNT
*& Author: Andrea Olivieri, Sergio Ferrari
*&         Techedge SpA
*& Version: 1.0  - 2009/01/20
*& Title   How many lines of custom ABAP code are inside your system?
*&---------------------------------------------------------------------*
REPORT  zsdn_simple_abap_sloc_count_n LINE-SIZE 255.

* Global Data Type [ GDT   ]
TYPES: BEGIN OF ty_repository,
         devclass  TYPE tadir-devclass,
         name      TYPE trdir-name,
         object    TYPE tadir-object,
         srcsystem TYPE tadir-srcsystem,
         author    TYPE tadir-author,
         subc      TYPE trdir-subc,
         sloc      TYPE i,
       END OF ty_repository.
DATA: l_repository TYPE ty_repository.
DATA: t_repository TYPE STANDARD TABLE OF ty_repository.

* defining the selection-screen
TABLES: tadir.
SELECT-OPTIONS: xpack   FOR tadir-devclass,
                xobject FOR tadir-object,
                xauthor FOR tadir-obj_name.

INITIALIZATION.
  PERFORM init_select_options.

START-OF-SELECTION.
  PERFORM get_obj_set.
  PERFORM upd_obj_set_count_class_sloc.
  PERFORM count_prog_sloc.

END-OF-SELECTION.
  PERFORM alv.

*&---------------------------------------------------------------------*
*&      Form  init_select_options
*&---------------------------------------------------------------------*
*       INCLUDE OBJECTS:  PROG, FUGR and CLAS
*       EXCLUDE PACKAGES: $TMP and from A to W
*       EXCLUDE USERS:    SAP, SAP*, DDIC
*----------------------------------------------------------------------*
FORM init_select_options.

* Include objects: PROG, FUGR and CLAS
  IF xobject[] IS INITIAL.
    xobject-sign   = 'I'. xobject-option = 'EQ'. xobject-low = 'PROG'.
APPEND xobject.
    xobject-sign   = 'I'. xobject-option = 'EQ'. xobject-low = 'FUGR'.
APPEND xobject.
    xobject-sign   = 'I'. xobject-option = 'EQ'. xobject-low = 'CLAS'.
APPEND xobject.
  ENDIF.

* Exclude packages: $TMP and from A to W
  IF xpack[] IS INITIAL.
    xpack-sign   = 'E'. xpack-option = 'BT'. xpack-low = 'A'. xpack-high
= 'WZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'. APPEND xpack.
    xpack-sign   = 'E'. xpack-option = 'EQ'. xpack-low = '$TMP'. APPEND
xpack.
  ENDIF.

* Exclude objects belonging to users: SAP* and DDIC
  IF xauthor[] IS INITIAL.
    xauthor-sign   = 'E'. xauthor-option = 'EQ'.     xauthor-low =
'SAP'.  APPEND xauthor.
    xauthor-sign   = 'E'. xauthor-option = 'EQ'.     xauthor-low =
'SAP*'. APPEND xauthor.
    xauthor-sign   = 'E'. xauthor-option = 'EQ'.     xauthor-low =
'DDIC'. APPEND xauthor.
  ENDIF.
ENDFORM.                    "init_select_options

*&---------------------------------------------------------------------*
*&      Form  get_obj_set
*&---------------------------------------------------------------------*
*       Get from TADIR
*----------------------------------------------------------------------*
FORM get_obj_set.
  DATA: l_tadir TYPE tadir.

  SELECT * FROM tadir INTO l_tadir
           WHERE pgmid      EQ 'R3TR'
           AND   obj_name   IN xauthor
           AND   object     IN xobject
           AND   devclass   IN xpack
            AND srcsystem   NE 'SAP'
           AND   author     IN xauthor.               "#EC CI_SGLSELECT
    IF NOT l_tadir-obj_name CP '_______________________________*'.
      MOVE-CORRESPONDING l_tadir TO l_repository.
      l_repository-name     = l_tadir-obj_name.
      l_repository-devclass = l_tadir-devclass.
      APPEND l_repository TO t_repository.
    ENDIF.
  ENDSELECT.
*
  SORT t_repository BY devclass name.

ENDFORM.                    "get_obj_set

*&---------------------------------------------------------------------*
*&      Form  upd_obj_set_count_class_sloc
*&---------------------------------------------------------------------*
*       ...and Compute SLOC for CLAS
*----------------------------------------------------------------------*
FORM upd_obj_set_count_class_sloc.
  TYPE-POOLS: sedi.
  TYPES: BEGIN OF ty_irdir,
          name LIKE trdir-name,
          devc    LIKE tadir-devclass,
        END OF ty_irdir,
        BEGIN OF ty_itab,
          repname LIKE sy-repid,
          devc    LIKE tadir-devclass,
        END OF ty_itab,
        BEGIN OF ty_crdir,
          name LIKE trdir-name,
          subc LIKE trdir-subc,
          devc    LIKE tadir-devclass,
        END OF ty_crdir.

  DATA: save_tabix      TYPE sy-tabix,
        l_class         TYPE sobj_name,
        l_pgmid         TYPE pgmid,
        l_object        TYPE trobjtype,
        class_name      TYPE programm,
        class_pool_name TYPE programm,
        lclskey         TYPE seoclskey.
  DATA: sourceline      TYPE string.
  DATA: l_1st_char      TYPE c.

  DATA: l_irdir         TYPE ty_irdir,
        l_itab          TYPE ty_itab,
        l_itab1         TYPE ty_itab,
        l_crdir         TYPE ty_crdir.
  DATA: t_irdir TYPE STANDARD TABLE OF ty_irdir,
        t_itab  TYPE STANDARD TABLE OF ty_itab,
        t_itab1 TYPE STANDARD TABLE OF ty_itab,
        t_crdir TYPE STANDARD TABLE OF ty_crdir.

  DATA: l_sloc          TYPE i.

  LOOP AT t_repository INTO l_repository.
    save_tabix = sy-tabix.
    CASE l_repository-object.
      WHEN 'PROG'.
        SELECT SINGLE subc FROM trdir INTO l_repository-subc WHERE  name
= l_repository-name.
        IF sy-subrc = 0.
          MODIFY t_repository FROM l_repository INDEX save_tabix
TRANSPORTING subc .
        ENDIF.
      WHEN 'FUGR'.
        CONCATENATE 'SAPL' l_repository-name INTO l_irdir-name.
        l_irdir-devc = l_repository-devclass.
        APPEND l_irdir TO t_irdir.
        l_repository-name   = l_irdir-name.
        l_repository-object = 'PROG'.
        SELECT SINGLE subc FROM trdir INTO l_repository-subc WHERE  name
= l_repository-name.
        IF sy-subrc = 0.
          MODIFY t_repository FROM l_repository INDEX save_tabix
TRANSPORTING name object subc.
        ENDIF.
        CLEAR l_irdir.
      WHEN 'CLAS'.
        DATA source_new TYPE sedi_source.
        DATA l_inctype(5).

        class_name = l_repository-name.
        l_pgmid = 'R3TR'.
        l_object = l_repository-object.
        l_class = class_name.
        CALL FUNCTION 'SEO_CLASS_GET_CP_NAME'
          EXPORTING
            pgmid                 = l_pgmid
            object                = l_object
            obj_name              = l_class
          IMPORTING
            progname              = class_pool_name
          EXCEPTIONS
            no_class_or_interface = 1.

        IF sy-subrc = 0.
          SELECT SINGLE subc FROM trdir INTO l_repository-subc WHERE name
= class_pool_name.
        ENDIF.

        lclskey-clsname = cl_oo_classname_service=>get_clsname_by_include(
class_name ).

        CLEAR l_class.
        CONCATENATE l_repository-name '%' INTO l_class.

        SELECT name FROM  trdir INTO TABLE t_crdir WHERE  name  LIKE
l_class.
        IF NOT t_crdir[] IS INITIAL.
          LOOP AT t_crdir INTO l_crdir.
            l_inctype = l_crdir-name+30(5) .
            REFRESH source_new.
            CALL FUNCTION 'SEO_CLASS_GET_INCLUDE_SOURCE'
              EXPORTING
                clskey                       = lclskey
                inctype                      = l_inctype
              IMPORTING
                source_expanded              = source_new
              EXCEPTIONS
                _internal_class_not_existing = 1
                not_existing                 = 2
                OTHERS                       = 3.
            CHECK sy-subrc = 0.

*           Compute SLOC !
            LOOP AT source_new INTO sourceline.
              l_1st_char = sourceline.
              IF    sourceline IS INITIAL
                 OR l_1st_char = '*'.
                DELETE source_new INDEX sy-tabix.
              ENDIF.
            ENDLOOP.
            l_sloc = LINES( source_new ).
            ADD l_sloc TO l_repository-sloc.
          ENDLOOP.
          MODIFY t_repository FROM l_repository INDEX save_tabix
TRANSPORTING sloc subc.
        ENDIF.
      WHEN OTHERS. CONTINUE.
    ENDCASE.

  ENDLOOP.

  IF t_irdir[] IS NOT INITIAL.
    LOOP AT t_irdir INTO l_irdir.
      REFRESH t_itab1.
      CALL FUNCTION 'GET_INCLUDES'
        EXPORTING
          progname = l_irdir-name
        TABLES
          incltab  = t_itab1.

*     append lines of t_itab1 to itab.
      LOOP AT t_itab1 INTO l_itab1.
        l_itab-repname = l_itab1-repname.
        l_itab-devc    = l_irdir-devc.    "Sometimes it's false
        APPEND l_itab TO t_itab.
        CLEAR l_itab.
      ENDLOOP.
    ENDLOOP.
  ENDIF.

  DATA: l_trdir TYPE trdir.

  LOOP AT t_itab INTO l_itab.
    SELECT SINGLE * FROM  trdir INTO l_trdir
           WHERE  name  = l_itab-repname
            AND    cnam  NOT LIKE 'SAP%'
            AND    cnam  <> 'DDIC'.
    CHECK sy-subrc = 0.

    MOVE-CORRESPONDING l_trdir TO l_repository.
    l_repository-devclass = l_itab-devc.
    l_repository-object   = 'PROG'.
    APPEND l_repository TO t_repository.

  ENDLOOP.

  SORT t_repository BY name object devclass.
  DELETE ADJACENT DUPLICATES FROM t_repository COMPARING name object
devclass.

ENDFORM.                    "upd_obj_set_count_class_sloc
*&---------------------------------------------------------------------*
*&      Form  count_prog_sloc
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
FORM count_prog_sloc.
  DATA: l_prog     TYPE c LENGTH 30.
  DATA: isource    TYPE TABLE OF string.
  DATA: l_1st_char TYPE c.

  LOOP AT t_repository INTO l_repository WHERE object = 'PROG'.
*   Compute SLOC !
    l_prog = l_repository-name.
    READ REPORT l_prog INTO isource.
    DATA: l_source_line TYPE string.
    LOOP AT isource INTO l_source_line.
      l_1st_char = l_source_line.
      IF    l_source_line IS INITIAL     "Empty
         OR l_1st_char = '*'.            "Comment
        DELETE isource INDEX sy-tabix.
      ENDIF.
    ENDLOOP.
    l_repository-sloc = LINES( isource ).

*   Update SLOC into t_repository
    READ TABLE t_repository WITH TABLE KEY name     = l_repository-name
                                       devclass = l_repository-devclass
                                       object   = l_repository-object
                                       srcsystem = l_repository-srcsystem
                                       author    = l_repository-author
                                       subc      = l_repository-subc
                        TRANSPORTING NO FIELDS.
    IF sy-subrc = 0.
      MODIFY t_repository FROM l_repository INDEX sy-tabix TRANSPORTING
sloc.
    ENDIF.
  ENDLOOP.
ENDFORM.                    "count_prog_sloc

*&---------------------------------------------------------------------*
*&      Form  alv
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
FORM alv.
  DATA: gr_table     TYPE REF TO cl_salv_table,
        gr_display   TYPE REF TO cl_salv_display_settings,
        gr_functions TYPE REF TO cl_salv_functions,
        gr_sorts     TYPE REF TO cl_salv_sorts,
        gr_agg       TYPE REF TO cl_salv_aggregations.
  TRY.
*     Create ALV table
      cl_salv_table=>factory( IMPORTING r_salv_table = gr_table CHANGING
t_table = t_repository ).
*     Set zebra layout
      gr_display = gr_table->get_display_settings( ).
      gr_display->set_striped_pattern( cl_salv_display_settings=>true ).
*     Display all standard function
      gr_functions = gr_table->get_functions( ).
      gr_functions->set_all( abap_true ).
*     Sort
      gr_sorts = gr_table->get_sorts( ).
      gr_sorts->add_sort( columnname = 'DEVCLASS' subtotal = abap_true ).
      gr_sorts->add_sort( columnname = 'NAME'     subtotal = abap_false ).
*     Totals
      gr_agg = gr_table->get_aggregations( ).
      gr_agg->add_aggregation( 'SLOC' ).
*     Display table
      gr_table->display( ).
    CATCH cx_salv_msg.
      WRITE: / 'Exception CX_SALV_MSG'.
    CATCH cx_salv_not_found.
      WRITE: / 'Exception CX_SALV_NOT_FOUND'.
    CATCH cx_salv_data_error.
      WRITE: / 'Exception CX_SALV_DATA_ERROR'.
    CATCH cx_salv_existing.
      WRITE: / 'Exception CX_SALV_EXISTING'.
  ENDTRY.
ENDFORM.                    "alv

Additional links and resources:

• Source lines of code (wikipedia)

1. Enter transaction code ST01.

2. Click on “Analysis” to access the options for the Trace Analysis program.

3. Configure the necessary parameters. In the example below, the trace records selected to be captured where “Kernel Functions” and “RFC Calls”. Tip: this procedure is also useful to perform Authorization Checks. In this case, we should only select “Authorization Check” from the Trace Records option list.

4. Go to the front-end and browse to the immediate point before you need to start capturing the trace records. This is important because as soon as you activate the trace, all actions will be stored in the log record. In the example, user would click in the standard Manager Self-Service Universal Worklist application

5. As soon as you have your browsing aligned in the front-end side, go back to ST01 and click on execute. Return to the Portal and click on the Universal Worklist link.

6. In ST01, click on “Analysis” to view the results. The result list will show something like the screenshot below. Notice that I’ve highlighted the standard function modules that were executed (SWN_UWL_GET_WORK and SYSTEM_RESET_RFC):

7. By double-clicking the Function Modules, you’ll be able to dig deeper and view more detailed information:

7. When you finish your analysis, don’t forget to switch off the trace analysis program. This is important because when the trace is active it will be gathering information at all times, which is a resource consuming operation:

A session records transactions and data in a special format that can be interpreted by the R/3 System. When the System reads a session, it uses the data in the session to simulate on-line entry of transactions and data. The System can call transactions and enter data using most of the facilities that are available to interactive users.

For example, the data that a session enters into transaction screens is subject to the same consistency checking as in normal interactive operation. Further, batch input sessions are subject to the user-based authorization checking that is performed by the system.

There are three batch input methods:

1. In the Direct Input Method, the programs are provided by the SAP system. These programs are available for Standard Applications. Under this method, the data base is updated using a Function Module, which is responsible for executing the appropriate consistency checks.
2. In the Call Transaction Method, the ABAP Program reads the external data which is present on the Application or Presentation Server, and uses the ABAP Statement CALL TRANSACTION USING to run a SAP statement.
3. In the Session Method the program reads the data and the SAP system stores the data in a “Batch Input Session”. The session records the actions that are required to transfer data into the system using normal SAP transactions.

Figure – Batch Input Session

Copyright (c) 2009 – saplab.org.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free documentation License, Version 1.2 or any later version published by the Free Software Foundation, with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. Source: wikipedia.

What SAP referes to as SAP Passports are nothing more that Digital Certificates, which guarantees a secure access between your computer and any SAP Portal using the digital certificate which is generated and installed.

Please follow the steps below to enable Single Sign-On for SAP websites with your OSS user.

1. Access http://service.sap.com

2. Click on “Benefit from Single Sign-On”

3. On the next screen, you will see some relevant information. Take your time and learn more about Single Sign-On with SAP OSS users by reading the “Read documentation first” and “More on SAP Passports”

4. Click on “Apply for a SAP Passport”

5. You should now enter your account information, SAP user and password

6. After authenticating, you will access the “Applying for an SAP Passport” page. You should now confirm your information and re-enter your password before proceeding.

7. Enter your password and click on “Apply for SAP Passport”

8. The following message will appear:

9. Click “Yes”

10. The following message will appear:

11. Click “Yes”

12. The following message will appear:

13. Click “Yes”

14. You should receive a confirmation that the SAP Passport was successfully installed and you can now make use of it. For that, you will need to restart all your browser sessions.

15. After restarting the browser, access the SAP Marketplace again – http://service.sap.com

16. The following screen will appear:

17. Note that the “Name” field will correspond to your SAP OSS user (hidden in the examples for obvious reasons).

18. If you click on “View Certificate”, you will be able to check some useful information, like the validity and the status:

19.  Go back and click on “Ok”. You will access the SAP Marketplace without having to enter your username and password again.

You are now ready to use Single Sign-On on the SAP Service Marketplace. You will be able to access many of the portals within the SAP Service Marketplace without having to enter your user-ID and password.

No related posts found

1 – Execute transaction SCOT;

2 – Goto menu View -> Node

3 – Goto SMTP node. Double click on the required node which is * in this case:

4 – Click on the Maintain Node button:

5 -Enter the Mail Host & Mail Port for outgoing mails (mail host example below). Click on Set for “Internet” option to set:

6 – Enter the Address Area as * for the receipt addresses. Also set the Output formats for the SAP Documents as shown in the image below. In the specified format the output will be sent as attachment in the email:

7 – Confirm these settings;

8 – Similarly Pager/Fax settings can be done. For Pager(SMS), the prerequisite is that in transaction SA14, the paging services should be defined. Once this is done, in the SCOT transaction, click on Set adjacent to Pager (SMS);

9 – Mention as * in the Address area for the receipt number and Domain name in the Domain input:

10 – Confirm the entries. The SMS will be of the format SMS=+ReciptNumber@Domain.