Install Process Runner GLSU

There are four main steps that must be completed for GLSU to run on your productive SAP system, and in addition, an optional fifth step.

1. Step 1: Install and import the GLSU transport into SAP.
2. Step 2 : Set up logical file names for your system
3. Step 3 : Set up user authorizations .
4. Step 4 : Transport to other systems.
5. Step 5 : OPTIONAL – Set profile parameters

Each of the steps are detailed below.

Note: If you are upgrading from a prior version, you probably have already set up the logical file names and authorization. Those steps can be skipped for upgrades.

Step 1: Install and import the GLSU transport

Copy the all the files from the CD root directory (or .ZIP file) into \usr\sap\trans (or its equivalent) on your SAP machine.

1. Run the included ZOPUNSAR.BAT file (if you are on a Windows NT operating system). This will expand the compressed file ZOPGLSU60.SAR. If you are not on Windows NT, run the sapcar commands manually, e.g., "sapcar –xvf ZOPGLSU61a.SAR".

   Note: This version is Unicode compliant. Even if your SAP system is not Unicode, you should still install this version. The code is Unicode compatible and it will save you an upgrade step if you should ever convert your SAP system to Unicode.

   Example:

   e:\usr\sap\trans>zopunsar

   sapcar -xvf ZOPGLSU60.SAR

   x cofiles/K900077.ZD2

   x cofiles/K900077.ZD2

   Note: Actual transport numbers may vary from GLSU version to GLSU version.

   The transport for this release is as follows:

   ZD2K900077 – GLSU MAIN PROGRAM

2. Add the transport to the correct import queue. Use transaction STMS. Press the "Truck" icon or Overview > Imports.

   Double-click the queue for the system into which you want to import the transport (usually your development box).

   When the Import Queue is displayed, select Extras > Other Requests > Add and enter the transport number (for example, ZD2K900077). Confirm that you wish to add it to the queue.

3. Import the transport using Request > Import.

   If errors occur, try re-importing the file using more override flags. Some errors in importing are unavoidable.

   If something fails to generate, try importing it again, and then try manually generating the object.

Step 2 : Set up logical file names

Note: If you are upgrading from a prior version, you probably already have the logical file names set up – those have not changed in the upgrade.

If you are in a technical environment that has more than one application server, please read the "Supported Technical Environment Notes" section below before starting this step for important information.

1. Determine what path you would like to use to store the GLSU temporary posting files.

   These files are usually less than 2-3 megabytes in size, but for some heavy users, they can approach 15 megabytes. The files are deleted as soon as the process completes, so the normal state of this directory is to be empty. During rare circumstances, files can get hung; it is good practice to occasionally purge any files over 30 days old.

   You will need to set up a logical file names and logical file paths for each SAP system ID where GLSU will be run. The logical file names are in the format "ZOPTION_GLSU_POST_xxx" where "xxx" is replaced by the system ID. "ZOPTION_GLSU_POST_ZD1" is provided in the transport only as an example.

2. Use transaction FILE to create the logical file paths.

   Acknowledge the client-independent warning. Scroll to the bottom of the list of logical paths. Select ZOPTION_GLSU_POST_ZD1 and press the Copy As... button or use menu option Edit > Copy As... This will allow you to create a new entry and shows you the current ZOPTION_GLSU_POST_ZD1 as the default name. Erase the "ZD1" and put in your system ID. When you have it correct, press Enter, and when asked if you want to copy dependent entries, select Copy All.

   You now need to set the path for this new logical file path definition. Select the new ZOPTION_GLSU_POST_xxx entry and press the second file folder icon up at the top. This allows you to enter the physical file name for Windows NT. If you are not using Windows NT, please use the New Entries button and enter your correct operating system in the Syntax Group field, along with the correct physical path for this system ID.

   If you want to set up more than one system ID, go back to the main "Change View Logical File Paths Overview" screen and press the top file folder icon. Do the Copy As... and repeat the instructions in step 2.

   When you are finished creating the logical file paths, press the SAVE button, or choose menu option Table View > Save. It will ask for a transport number - create a new one so you can easily track the logical file names.

3. Use transaction FILE to create logical file names.

   Now that all the logical file paths have been defined and their physical paths defined, we need to assign logical file names that use those paths. While still in transaction FILE, click on the 3rd file folder icon. Scroll to the bottom of the list, and again, we will select the entry called ZOPTION_GLSU_POST_ZD1 and press the Copy As... button or use the menu option Edit > Copy As... This will pop up a screen requesting the logical file information. The only thing that needs to be changed is the logical file and logical path, replacing "ZD1" with your desired system id in both fields.

   If you want to also change the physical file name, you may edit the "Physical file" field. The text "<PARAM_1>" is replaced by the system with Username+Timestamp, so for John Smith, whose USERID is JSMITH, running the program at 8:38 in the morning would have a filename like ZOP_GLSU_JSMITH083079 in the path you defined in step 2.

   Repeat step 3 as necessary for all your system IDs.

   When you have finished creating the logical file names, press the SAVE button, or choose the menu item Table View > Save.

   As an alternative configuration method, you can choose to create one logical filename definition as ZOPTION_GLSU_POST and transport it throughout your landscape. It is important to note you must use extreme care when utilizing this method. Use appropriate variables as this path will be used in all systems including production unless you choose to maintain the entries separately in each system. In the case of a mixed logical filename configuration (one that contains both a ZOPTION_GLSU_POST_SID entry and a ZOPTION_GLSU_POST entry), the "SID" entry will be used if one is available and then the entry without a SID.

4. Record the transport number.

   This package will have to be transported to all systems where GLSU will be run.

Step 3 : Set up user authorizations

Note: If you are upgrading from a prior version, most of the prior authorizations will still work – the only addition is RFC access if you want your users to be able to post their documents directly from the Excel spreadsheet via RFC connection.

1. The following is a list of authority objects which are needed to use the GLSU solution.

   Authorization Object	Field :: Values
   S_TCODE	Transaction code  :: "FB01" for document posting "SM35" for document processing/log viewing "ZGLSU" for the main GLSU program "FBS1" for Accrual "FBV1", "FBV0", and "FBVB" for Park Document "FBB1" for Post Foreign Currency Adjustment "FV50L" for Park to Ledger Group
   S_BTCH_JOB	JobAction :: RELE JobGroup :: *
   S_BDC_MONI	Batch input monitoring activity :: DELE Session name :: FI-GLSU*
   S_RFC	Activity :: 16 Name of RFC to be protected :: /ZOPTION/GLSU, /ZOPTION/COMMON, RFC1, SRFC, SUSO, SYST, RFCH, BDS_BAPI (for attaching documents), 0002 (for document drillback), SDIFRUNTIME (for meta- data retrieval) Type of RFC object to be protected :: FUGR
   S_PATH	Full Authorization
   S_DATASET	Activity: Full Authorization (Delete authority is needed to cleanup temporary intermediate files) Filename: Path as configured in Section 2 Program: "/ZOPTION/*", "RFBIBL0*"
   F_BKPF_BUK	Company Code: All required Activity: "01" for Posting and Accrual "03" to download master data in the .INI or real-time pick lists and description functionality. This is also the activity which was added to adhere to SOX requirements for data access "77" for Park Document
   S_GUI	For uploading/downloading files: "60" and "61" for ACTVT (Activity)
   S_SCR	Authorization for SAP GUI scripting: "16" for ACTVT (Activity)
   S_BDS_DS	For attaching documents to the BDS: "BKPF" and "ACCTGDOCMT" for ClassName "BO" (Bravo, Oscar) for ClassType "01" - "05", and "30" for ACTVT (Activity) Additional activities as required.
   S_BDS_D	For attaching documents to the BDS: "01" - "05", and "30" for ACTVT (Activity) Additional activities as required. "BDS*" for LOIO_CLASS (or as configured)

Step 4 : Transport to other systems

1. Transport all of the above to any systems where GLSU will be run.

Step 5 : OPTIONAL – Set profile parameters

1. If users require document drill-back functionality from Excel, set system profile parameter "sapgui/user_scripting" equal to "TRUE".

Supported Technical Environment Notes:

When configuring logical file paths, it is important that the file paths specified are either Network File System or Windows Shares, common and writable across all application servers (if the environment has more than one application server). Since GLSU jobs are load- balanced, it is possible that jobs will be started on application servers other than the one the user has logged onto.

BDC Log files stored at the application server OS level must be configured to be read by all application servers. The default path suggested by SAP is \usr\sap\<SID>\SYS\global. If this directory is not common to all application servers, the financial document number may not be retrievable by the GLSU application since the document number is retrieved from these files.

SAP Upgrade Notes:

If you are upgrading your SAP system from any 4.0x, 4.5x, 4.6x, or 4.7x version to any of these versions, you do not need a separate transport. Although there are significant differences in the SAP repository components for these SAP versions, ALL of the objects necessary to run in each of these environments are delivered with the one code base. Therefore, an upgrade of the Z Option software is not necessary unless you desire new functionality in a later release of GLSU.

Transport object list for GLSU:

Object Directory    LIMU    ADIR    R3TRSOTR/ZOPTION/GLSU

Table Definition        LIMU    TABD    /ZOPTION/GLSU_TEMPLATE_DATA

Table Definition        LIMU    TABD    /ZOPTION/GLSU_TEMPLATE_LIST

Class (ABAP Objects) R3TR    CLAS    /ZOPTION/CL_IM_GLSU_PRKLDG

Domain    R3TR    DOMA /ZOPTION/CHAR260

Domain    R3TR    DOMA /ZOPTION/CHAR8000

Data Element R3TR    DTEL    /ZOPTION/MAXROWS

Data Element R3TR    DTEL    /ZOPTION/ROWNUMBER

Data Element R3TR    DTEL    /ZOPTION/SHEETNUMBER

Data Element R3TR    DTEL    /ZOPTION/SPLITNUMBER

Data Element R3TR DTEL /ZOPTION/VAL260

Data Element R3TR DTEL /ZOPTION/VALKEY

Data Element R3TR DTEL /ZOPTION/VALLINE

Data Element R3TR  DTEL  /ZOPTION/VALMSG

Data Element R3TR DTEL /ZOPTION/DB_FILTER_NAME

Data Element R3TR  DTEL  /ZOPTION/DB_FILTER_VALUE

Enhancement Implementation R3TR ENHO /ZOPTION/GLSU_PRKLDG_EXT

Enhancement Implementation R3TR ENHO /ZOPTION/GLSU_PRKLDG_IMP

Function Group    R3TR  FUGR  /ZOPTION/COMMON Contains:

/ZOPTION/PING

/ZOPTION/GET_PREMIUM_USERS

/ZOPTION/USER

Function Group    R3TR    FUGR  /ZOPTION/GLSU Contains:

/ZOPTION/GLSU_POST

/ZOPTION/GLSU_GET_VALIDATION

/ZOPTION/GLSU_LIVE_PICK_GET

/ZOPTION/GLSU_LIVE_VAL_GET

/ZOPTION/GLSU_LIVE_AUTH

/ZOPTION/GLSU_LIVE_DESCR_GET

/ZOPTION/GLSU_LIVE_CUSTVAL

/ZOPTION/GLSU_GET_AUFNR

/ZOPTION/GLSU_INSTALL_CHECK

/ZOPTION/GLSU_LIVE_SUBST

/ZOPTION/GLSU_LIVE_SETTING_GET

/ZOPTION/GLSU_LIVE_COBL_CHECK

/ZOPTION/GLSU_LIVE_CUSTEXTRACT

/ZOPTION/GLSU_LIVE_CUSTPICK

/ZOPTION/GLSU_LIVE_DOCEXTRACT

/ZOPTION/GLSU_PARK_LDGRP

/ZOPTION/GLSU_RWBAPI_COBL

/ZOPTION/GLSU_GET_TEMPLATE_LST

/ZOPTION/GLSU_GET_TEMPLATE_DAT

/ZOPTION/GLSU_LINK_ATTACHMENT

/ZOPTION/GLSU_LIVE_FB00_GET

/ZOPTION/GLSU_VALIDATE_BALACCT

/ZOPTION/GLSU_GET_DASHBRD_DATA

Message Class R3TR    MSAG /ZOPTION/GLSU

Program    R3TR    PROG  /ZOPTION/GLSU

Program    R3TR    PROG /ZOPTION/GLSU_PRINT_HISTORY

Program    R3TR    PROG /ZOPTION/GLSU_SEND_CONFIG

Program    R3TR    PROG /ZOPTION/GLSU_SEND_CONFIG_OFFL

Program    R3TR    PROG /ZOPTION/GLSU_TOP_CONSTANTS

Program    R3TR    PROG /ZOPTION/GLSU_TOP_TABLES

Program    R3TR    PROG /ZOPTION/HIDDEN

Business Add-Ins - Implementations    R3TR    SXCI    /ZOPTION/GLSU_PRKLDG

View Maintenance: Data    R3TR    VDAT V_FILENACI

View Maintenance: Data    R3TR    VDATV_FILEPATH

View Maintenance: Data    R3TR    VDAT V_PATH

Package    R3TR    DEVC /ZOPTION/COMMON

Package    R3TR    DEVC /ZOPTION/GLSU

Package    R3TR    DEVC  ZGL1