EasyInput User's Manual - SAP & Excel integration · PDF fileEasyInput User’s manual ... Product configuration ... users SAP system or can be used as a tutorial how one can create

EasyInput User’s manual

EasyInput – Easy Communication Excel - SAP Version: 2.5X, 2015-12-16

EasyInput - Page 1/34

Table of contents

1. EasyInput product information ........................................................................................................ 2

2. Product installation on user’s computer ........................................................................................ 5 EasyInput global settings .................................................................................................................... 6

3. Working with EasyInput .................................................................................................................... 8 EI_Logon – EasyInput connection worksheet ..................................................................................... 8 EI_Data – EasyInput data worksheet (this is the default name that can be changed while configuring the script) ......................................................................................................................... 9 Ribbon menu – EasyInput ribbon menu ........................................................................................... 11

4. Product configuration ..................................................................................................................... 14 EI_ScriptName – Script ID/ name/ type and optional script information ......................................... 14 EI_Script_TR – Transaction script details definition ......................................................................... 16 EI_Script_FM – BAPI/ Function script details definition ................................................................... 16 EI_Config – Other configuration and license settings ....................................................................... 20

5. Recording scripts with the SHDB transaction (for transaction scripts) .................................... 26

6. Selecting function module with BAPI repository (for function scripts) .................................... 30

7. Tips & Tricks .................................................................................................................................... 31

8. Authorizations in the SAP system ................................................................................................. 33

EasyInput – User’s Manual

http:/ www.bccgroup.eu EasyInput - Page 2/34

1. EasyInput product information

EasyInput facilitates exchanging data between MS Excel workbook and an SAP system. It connects functionalities of MS Excel and various SAP system types - ERP/ CRM/ BW/ etc.). With one button click, one can create thousands of master data records, postings or for example purchase requisition documents. EasyInput has also the functionality to read data from an SAP transaction or BAPI interface. Thanks to its user friendly interface (only Excel, no SAP GUI), possibility to test transactions before actual run, clear message communication, support of the F4 search help for possible entry values, and many other functions Easy Input can replace the standard SAP migration framework (LSMW) and sometimes replace the SAP GUI itself. Example screen of an EasyInput workbook

To use the EasyInput one has to prepare a script (or use one of the delivered as an example). EasyInput 2.X can handle two different kinds of scripts:

Script type Description

Transaction Script (TR) Scripts based on transaction recording. These scripts use batch input technique and can be used for most transactions in the SAP system.

BAPI/ Function module Scripts (FM)

Scripts based on Business Application Interface (BAPI) created by SAP for easy external integration with an SAP system. These scripts implement either BAPI methods predefined by SAP or RFC-enabled function modules.

See EasyInput forum at https://easyinput.net to get more information on EasyInput.

https://easyinput.net/



How does EasyInput work ? EasyInput product consist of several elements. The application logic is contained in EasyInput Excel Add-in. The script definition (configuration) is contained in MS Excel workbooks. These workbooks (called EasyInput workbooks) can be based either on the empty EasyInput workbook template or on one of EasyInput example workbooks. EasyInput – Solution elements

EasyInput installation files contain:

EasyInput MS Excel Add-in

EasyInput MS Excel Template (that will be put during installation to personal templates directory, so that the user could access it later when creating new EasyInput workbook)

EasyInput Example Workbooks (that can be either used directly or after adjustments to the user’s SAP system or can be used as a tutorial how one can create EasyInput workbooks)

EasyInput SAP system transport (optional, for full version only; facilitates connection between SAP and Excel)

Additionally during installation an EasyInput shortcut is created on the desktop. It facilitates starting EasyInput (although one can start EasyInput just by starting MS Excel and use of the EasyInput ribbon menu).



Using EasyInput means using EasyInput workbooks. Such special workbooks are created either on the base of empty EasyInput workbook template or on the base of one of EasyInput example workbooks. EasyInput workbook creation

The EasyInput workbook can be created either by IT people or by business users themselves. As creation of scripts for a selected transaction is based on recording of this transaction, it is quite straightforward. A self-training using tutorials published on EasyInput forum (https://easyinput.net) should be enough to start own script creation. After an EasyInput workbook is prepared and tested it can be reused many times with different data. EasyInput workbook creation participants and EasyInput workbook use

To start working with EasyInput the user starts MS Excel and open any EasyInput workbook (e.g. empty EasyInput workbook template or one of the example workbooks). When Excel recognizes EasyInput workbook then additional EasyInput ribbon menu changes. EasyInput application is ready to be used.




2. Product installation on user’s computer

Prerequisites: Excel 2007/2010/2013/2016 (32bit), SAP GUI 7.30 (SP7 or higher)/7.40, Microsoft operating system Vista or later. Prerequisites for the trial version: Internet connection in order to request the temporary license key. EasyInput installation on user’s workstation is quite easy:

a) Unpack the installation package if provided as compressed (zip) file Important: If automatic product update is envisaged, then the user should put the installation files into a shared folder. Then after the users install the product from that shared folder, EasyInput will check for updates in this path once a week. Putting the new version of EasyInput installation files to the shared folder (exactly the same path) will automatically allow companywide product update (Microsoft ClickOnce technology).

b) Form the subfolder User run setup.exe * One need administrator rights to fully install the program on a workstation.

Select install if the system asks you to confirm installation from a publisher that cannot be verified. Important: Computer reboot may be required, if additional Microsoft components (e.g. Microsoft Visual Studio Tools for Office Runtime) are needed to be installed. After successful installation, the user should be presented with the window confirming the success:

Important: When re-installing (running setup on a computer with EasyInput already installed), the old example files may be overwritten with new versions. Important: To use EasyInput the user needs authorizations in the SAP system, which are described at the end of this manual in the chapter “Authorizations in the SAP system”. After the installation the user can:

a) Build new EasyInput workbooks based on the empty template (use New EasyInput workbook ribbon menu button)

b) Try the examples provided with the tool and stored in personal template folder in EasyInput_ExampleFiles subfolder . Important: Most of the financial examples will work without much adjustment. The logistics examples are usually too dependent on the system configuration to be executed successfully on another system, that the one they were created on. The functional scripts (FM) are less prone to system changes than transactional scripts (TR).

The easiest way to access the examples is to start EasyInput via desktop shortcut and select Open EI Template button from EasyInput ribbon menu. To uninstall EasyInput use standard Control Panel > Programs & Features tool.



EasyInput global settings

After installation it is recommended to set the EasyInput global settings that will be used for every EasyInput workbook. This global settings can be accessed via EasyInput ribbon menu > EasyInput Info > Settings Here the default regional settings as well as license management and other settings can be done. Regional settings

One should set the data and number formats as they are on the SAP system side. License management

Here the license can be viewed, imported from Internet, uploaded to a license file or downloaded from a license file. Other settings

Here, if the administrators imported the EasyInput transport request to the SAP system (full version only), the user can switch globally to use EasyInput (BCC) own function modules instead of those SAP standard ones. This allows better security management and helps being independent from SAP changes. Also the maximum empty lines number allowed between separate transactions data can be given here.



Auto reconnection time is the maximum idle time, after which no password has to be given (automatic reconnection). The two buttons at the bottom allow checking for updates and resetting global settings to their defaults. Checking for updates manually works differently form automatic update option. With manual update check, the companies that bought the maintenance option can check if there are upgrades accessible for them. Normally, if there are updates, they should be downloaded and unzipped, by the product administrator and then put to the shared installation folder, so that the automatic update could be done companywide.



3. Working with EasyInput

To use EasyInput one has to open one of the existing EasyInput workbooks or create a new MS Excel workbook based on empty EasyInput template (Ribbon menu New EI workbook). When creating new EasyInput workbook one needs to configure the script (see the next chapter). When the script configuration is done, one can enter connection data on EI_Logon worksheet and then enter the information on the data worksheet (by default EI_Data). The additional EasyInput ribbon allows to perform script execution and data upload or download actions.

EI_Logon – EasyInput connection worksheet

To get access to an SAP system one has to fill the technical connection information on the EI_Logon worksheet (they can usually be found in the SAP Logon Pad application).

The information entered on this screen are divided into 4 sections:

Section Description

1. General logon data Rows 7-11

The most important (required) fields in this section are: - SAP user ID

- Logon language

The other data is optional.

2. Connection data – SAP SNC

(Secure Network Communications)

Similar to SSO but for external systems.

SNC is a software layer in the SAP system architecture that

provides an interface to an external security product.

3. Connection data – SAP system

using a specific application server

If the connection is to be done with a specific application

server this section should be filled in. In such a case the

section 4 should remain empty.

4. Connection data – SAP System

using load balancing

If the connection is to be done with load balancing this section

should be filled in. In such a case the section 3 should remain empty.

Usually one has to provide USER in the first section and fill the data in one of the sections 2, 3 or 4.



EI_Data – EasyInput data worksheet (this is the default name that can be changed while configuring the

script)

EasyInput data worksheet elements (by default EI_Data)

Rows 1-4 of the data worksheet are reserved for steering data. Steering data are used for example by the F4 search help functionality. Steering row Description

1 – Table-field info Table-Field string describing table and table field. The 1st row is crucial for the F4 help to work for a column. Usually the

value in this row is copied from the script. Some transactions

however, have their screen field meaning set only in runtime. For such transaction it can be necessary to fill the data

manually based on the F1 help in SAP GUI and technical info. Important: In difficult cases, when no table-field pair gives the

F4 functionality, one can put Table-Field-SearchKey where

searchkey is the ID of the searchkey with required F4 functionality.

2 – Data Type-Length info Describes data type and length of the field. This data is

informational.

3 – Length String String containing so many characters (digits) as the length of

the field assigned to the column. Thanks to this string the user can simply adjust column with to the length of the data

(especially important for the descriptions strings)

4 – Optional fixed value string An optional string containing list (separated by comma) of values that should be allowed in the column. E.g.

“1000,2000,3000,/”. When the user introduces such a string

and then calls the function Create references in data sheet columns (text) from the script sheet in the ribbon, the

standard Excel value help for the column will be created.

Rows 6 and 9 from AA column upwards can be edited manually, so that the data column descriptions were comprehensible for the user. The texts in the 9th row (as well as the steering data in rows 1-3) can be generated automatically based on the script (with the use of Create References in Data Sheet columns function accessible via the EasyInput ribbon – see the Script creation) . The columns A-G of the data worksheet are reserved columns for the transaction processing messages. The columns B,C,D describe the test run results. The columns E,F,G describe the actual run results. This area can be cleared manually by selecting it and choosing Clear contents form the context menu.



The Y column of the data worksheet is reserved for data level. For simple transaction this field can be left empty. For transaction consisting of data at various levels (e.g. header level=0 and line item level=1), one should enter data level in this field starting with 0. This allows the programs to distinguish between header lines and line item lines (that can be more than one for a transaction). Important! Levels allow a loop over a script section. If within a script there are lines describing only one line item in the document, and when they are assigned level 1, and there are more than one data lines on data sheet assigned to level 1 as well, then the script part will be repeated for each data line. If a transaction has different data on the same level (e.g. line item level and delivery item level), than they can be distinguished by a string in the Z column (order). Filling this order field is optional. Order can be any string distinguishing data on the same level (e.g. A and B). Important! If data on a sublevel/ order is optional one can put string “_O” at the end of order string (e.g. “A_O” or just “_O”). Alternatively one can set the default on the configuration worksheet. Important! If data on a sublevel/ order is required one can put string “_R” at the end of order string (e.g. “A_R” or just “_R”). Alternatively one can set the default on the configuration worksheet. From the 10th row and from the column AA start transaction data, that can be entered by the user. When the cursor is in this area pressing F4 should call SAP search help window (if in 1st row the technical table-field info is maintained).



Product EasyInput uses ribbon menu. This ribbon is used to perform the product tasks and the most frequently changed settings. Important! EasyInput ribbon menu is worksheet-relevant. When the script worksheet is selected by the user, then the script relevant buttons will be presented. Important! EasyInput ribbon may not show correctly when opened while Excel cell is in “edit mode” (“Edit mode” prevents macros from executing). If such a problem appears, the user should press ESC on the keyboard (to exit from the “edit mode”) and press the “EasyInput Info” BCC Icon. After the information popup is closed the ribbon menu should be OK again.

Ribbon menu – EasyInput ribbon menu

EasyInput File ribbon menu (shows when no EasyInput workbook is open)

Standard EasyInput ribbon menu

EasyInput ribbon menu for Data worksheet (default EI_Data)

EasyInput ribbon menu for Transactional script (EI_Script_TR worksheet)

EasyInput ribbon menu for BAPI/Function Module script (EI_Script_FM worksheet)

EasyInput ribbon object Object function

Buttons of File ribbon menu (show when no EasyInput workbook is open)

File – New EI workbook Opens new empty EasyInput workbook.

File – Open EI template Opens EasyInput templates stored in personal templates

folder – e.g. EasyInput examples.

File – Open EI workbook Opens any EasyInput workbook.



Buttons of the standard EasyInput ribbon menu

Button “Process EasyInput script” Starts the SAP transaction for the chosen script.

Dropbox “Script” Choosing the script that will be run when „ Process EasyInput script” button is pressed. In a workbook there can be more

than one script defined (e.g. one to create and one to change master data).

Scripts that can be chosen are defined on EI_ScriptName worksheet.

Dropbox “Run type” Allows to choose between test and actual runs. Additionally

one can choose to process only records, that had errors before, or only the new records (without any results).

This combo box can be hidden via relevant setting on

EI_Config screen.

Button “Show/ hide configuration” Switches on/off the visibility of the configuration worksheets:

- script names sheet EI_ScriptName - script definition sheet EI_Script_TR

- configuration sheet EI_Config

If configuration is finished these worksheets can be hidden.

Button “EasyInput Info” Shows the product information window and buttons to open

license terms and user’s manual.

Transactional Script sheet buttons (appear when EI_Script_TR worksheet is selected)

Button “Import script file” Optional button, that appears only when worksheet

EI_Script_TR is chosen. Allows importing a recorded BDC

script from a text file.

Button “Create descriptions” Optional button, that appears only when worksheet

EI_Script_TR is chosen. Pressing that button fills the

description column on the EI_Script worksheet. That simplifies recognition of the meaning of the technical field names.

Button “Create references in data sheet columns”

Optional button, that appears only when worksheet EI_Script_TR or EI_Script_FM is chosen. Pressing that button

copies the technical data from the EI_Script worksheet to the

Data worksheet (rows 1-3) and creates description for data sheet columns.

BAPI/Function Module Script sheet buttons (appear when EI_Script_FM worksheet is selected)

Button “Add an RFC-enabled function module”

Optional button, that appears only when worksheet EI_Script_FM is chosen. Allows creating EasyInput FM script

for the given by the user function module.

Button “Create references in data sheet columns”

Optional button, that appears only when worksheet EI_Script_TR or EI_Script_FM is chosen. Pressing that button

copies the technical data from the EI_Script worksheet to the Data worksheet (rows 1-3) and creates description for data

sheet columns.

Correctness check buttons (appear when EI_Script_XX worksheet is selected or data sheet)

Button “Script pre-check” Optional button, that appears only when worksheet EI_Script_TR or EI_Script_FM is chosen. Pressing that button

starts script correctness check.

Button “Data pre-check” Optional button, that appears only when data worksheet is

chosen. Pressing that button starts script correctness check

and data correctness check. Important! “Data pre-check” checks only data type (alphanumerical or numerical) and data

length.

Data columns maintenance buttons (appear when EI_Script_XX worksheet is selected or data sheet)

Button “Insert column” Optional button, that appears only when the script or data

worksheet is chosen. Allows inserting empty column on the data sheet and reorganizes references to columns in script

sheets. Warning! When using more than one script in the

workbook all the scripts will be adjusted.



Button “Delete column” Optional button, that appears only when the script or data

worksheet is chosen. Allows removing the selected column on the data sheet and reorganizes references to columns in script

sheets. Warning! When using more than one script in the workbook all the scripts will be adjusted.

Button “Swap columns” Optional button, that appears only when the script or data

worksheet is chosen. Allows swapping places of two columns on the data sheet and reorganizes references to columns in

script sheets. Warning! When using more than one script in the workbook all the scripts will be adjusted.

Data tools (appear when data sheet e.g. EI_Data is selected)

Button “Delete result messages” Optional button, that appears only when

MessagesDeleteButton is not empty on the configuration worksheet. Allows clearing messages of last EI run.

Button “Delete data area” Optional button, that appears only when DataAreaDeleteButton is not empty on the configuration

worksheet. Allows clearing contents of data sheet.



4. Product configuration

EasyInput configuration is done by filling appropriate data on following worksheets (dependent on script type either EI_Script_TR or EI_Script_FM will be used):

Worksheet name Worksheet description

EI_Logon User & connection details

EI_ScriptName Script ID/ name / and script mode

EI_Script_TR Transaction script details

EI_Script_FM BAPI/Function script details

EI_Config Definition of other configuration settings

Important: Remember to enter the SAP system connection data and user name on the EI_Logon worksheet before configuring the script.

EI_ScriptName – Script ID/ name/ type and optional script information

The worksheet EI_ScriptName contains script names, script ID, script type and optional information about the script mode. There can be one or more scripts in one EasyInput workbook.

Column Field Field description

A Script name Script description that the user will be able to choose on the ribbon

B Script ID Short technical script ID. The script ID should not

C Script type Currently following script types are implemented: TR-Transaction script FM-Function script

D Mode (optional) Optional field (not used for fucntion scripts; used optionally for transaction scripts). If empty the default run mode for transaction scripts is chosen from the EI_Config worksheet Empty = > default B-Standard = Batch Input C-Extended = No batch Input, Read capability D-Extended = Batch Input, old CATT, Read capability, not

recommended E VBA macro executed

before the script (optional)

Optional field used to integrate EasyInput script with user’s VBA macros. See tips and tricks section.

F VBA macro executed after the script (optional)

Optional field used to integrate EasyInput script with user’s VBA macros. See tips and tricks section.

G DataSheet (optional) Optional. Provides the name of the data worksheet valid for the specified script. If not specified here, the default value from EI_Config worksheet is used.

H ReadValueFromMessage string (oprtional)

Optional. Provides string allowing teking back results (e.g. documents number) from messages for the specified script. If not specified here, the default value from EI_Config worksheet is used.





EI_Script_TR – Transaction script details definition

The EI_Script_TR worksheet contains transaction script details. The tranaction script uses the SAP Batch Input technology. Apart from batch input data (columns F-J) the worksheet EI_Script_TR contains additional data steering how the script will be executed.

EI_Script_FM – BAPI/ Function script details definition

The EI_Script_FM worksheet contains BAPI/ function script details. The function script calls one or more remote SAP function modules (usually BAPI object methods). Apart from data describing the function module (columns F-J) the worksheet EI_Script_FM contains additional data steering how the script will be executed.

Column Field Field description

A Script ID Assigns script row to a given script ID

B Run type Defines whether the script row is used for: A – actual run T – test run C – both test and actual run



Most of the script rows usually is the same for actual and test run, so that they are signed with C. The rows, that are different for actual and test runs will be assigned A or T letter. Info! Usually the last screen action (field value), that for the actual run is (BDC_OKCODE =BU) for the test run is (BDC_OKCODE /ECNC). For the test run new screen appears (confirmation of the cancellation): SAPLSPO1 0200 X BDC_OKCODE =YES

C Level Optional. Described in part Working with EasyInput. Level allows copying of a given part of the script for a given data line (e.g. document line item). For simple scripts (without sublevels) the level value may stay empty. For more complicated scripts this should be filled with values starting from 0. The first transaction data line should always have 0 value (may be left empty for simple scripts).

D Order Optional. Described in part Working with EasyInput. Order allows diferentiation between data on the same level.

E Inactive Optional. Can be left empty or filled with „X” value. When set to value „X”, then the relevant script row is omitted.

F-J for Transaction Script

Program, Screen, Start ID, Field name, Field value

Standard transaction script recorded in the SAP system. The script can be recorded with the SHDB transaction, and than either copied manually (Ctrl+Y > Ctrl + C > Ctrl + V) or saved as file and uploaded from file. The recording is usually extended by specifying the transfer fields (see description below for columns L/M) In the column “Field value” either constant or Excel formula can be put instead of transfer defined by columns L/M.

F-J for BAPI/ Function Script

Program, Screen, Start ID, Field name, Field value

Standard script data generated automatically by EasyInput, after the user inputs the SAP function module ID (after pressing the button Add an RFC-enabled function module) The recording is usually extended by specifying the transfer fields (see description below for columns L/M) In the column “Field value” either constant or Excel formula can be put instead of transfer defined by columns L/M. One can remove some not used lines from the script.

K Field description Informational field. Filled when Create description button pressed. Simplifies recognition of technical field names.

L Transfer Type Optional. Can be left empty or filled with values WriteData or ReadData. Functions when value is provided: WriteData –copying data from Data Sheet to the script ReadData –reading data from SAP screen and copying to Data Sheet Examples with ACGL_HEAD-BLDAT field: ACGL_HEAD-BLDAT/empty/WriteData/F BDC_CURSOR/ACGL_HEAD-BLDAT/ReadData/F



Important! Reading possible only when extended mode is selected in script or configuration (full version only).

M Read/ write column Optional. The Data Sheet column from which/ to which data will be copied in runtime. Can be filled with Data Sheet column letter only when Transfer type set to WriteData or ReadData.

N Screen omitting Optional. Can be left empty or filled with „X” value. Value X can be set only in the row when Start ID (column H) has olso value X (screen row). Value X means, that the screen can be missing in the system, and the program should check it, and if the screen is really missing then try with the script without the screen. Example of use: In FB50 transaction at the beginning the screen with the Company Code input may or may not appear depending on the customization.

P-S Formula reference column 1-4

Optional. Used only in scripts, where a formula is used to check in runtime whether a script line should be used or not. The fields contain references to Data Sheet (column letters). When the script is generated during runtime, data from given data sheet columns will be copied to the relevant script sheet columns (U-X). This allows script formula in column T and script value in column J to be calculated during runtime (e.g. differently for each data line). When string ROW is put in these columns, then during runtime in respective script sheet columns (U-X) are filled with row number of the line currently processed on the data sheet. Example of values: AA AB .. AZ ROW

T False/True formula Optional. Can be empty or filled with value True or False. In case of it’s value is False the relevant script row will be excluded from the script. Usually not set as fixed value, but as formula referencing data from relevant or preceding script rows, from columns U-Z. On the contrary to column E, the T column is calculated during runtime. Example of such a formula: =$T$96<>$U$96.

U-X Value 1 -4 Values filled by the EasyInput during script generation, if columns P-S are defined. The values from these fields are used to calculate formula in the T column.

Y Read value If in the read/write column, the line is customized as ReadData row, then the value that is read in the script line apart from being put to the data sheet, is copied into this column. It can be than used in the formula in the T column (=$Y$255=”A”).

Z Loop index In this column, the consecutive transaction number (for level 0) and loop index (for level > 0) is copied during script execution. This allows to make formulas in column T to have different values e.g. for the first line item in a transaction (=$Z$255=1).



Transaction script preparation Transaction scripts are usually prepared by recording a chosen transaction in the SHDB recorder

transaction in the SAP system. The process of transaction script preparation is described in a later

section of this manual. After the script is recorded it can be imported and processed further with the use of special script buttons that appear when EI_Script_TR worksheet is selected.

EI_Script_TR – Button Import script file The easiest way to copy the script generated in SAP into EasyInput is to do it manually with the use of key shortcuts Crtl+Y, Ctrl+C, Ctrl+V (Copy and Paste). For longer scripts this metod can be to tedious, and therefore a second automatic option to import such a script is implemented. A recorded in SHDB transaction script can be saved to a text file. This text file can be later uploaded to EasyInput. To load such a script file click the button “ Import script file” on the ribbon. The button is only accessible when worksheet EI_Script_TR is selected

EI_Script_TR – Button Create descriptions Fills the description column on the EI_Script worksheet (“K”). That simplifies recognition of the meaning of the technical field names.

EI_Script_TR – Button Create references in data sheet columns After creating the script itself on the EI_Script_TR or EI_Script_FM worksheet, the references to data sheet should be created for each row where column “L” has a value. This is an automatic task, that performs 3 activities:

Optional: To the data sheet row the technical information about data fields is copied. This allows later use of F4 search help on data sheet.

Optional: In the row 7 of the data sheet description of the transferred field is generated and in the rows 2-3 the data type and length info is stored.

Optional: For the data sheet columns, that are referenced in the script with a field that has fixed domain values (e.g fixed H/S values for Debit/Credit) standard Excel value help can be created. It facilitates data input.

To create references one shoud click the „Create references in data sheet columns” button on the ribbon. The button is only accessible when worksheet EI_Script_TR or EI_Script_FM is selected. BAPI/ Function script preparation Function script preparation starts with the selection of the relevant SAP function module with the use

of the BAPI repository transaction (BAPI). The process of function module selection is described in a later section of this manual. After the function module is selected it can be processed further with the

use of special script buttons that appear when EI_Script_FM worksheet is selected.

EI_Script_FM – Button Add an RFC-enabled function module The function module chosen in the BAPI transaction in the SAP system can be added to the function script with this button. After the user inputs the function module ID EasyInput generates the script entries. EI_Script_FM – Button Create references in data sheet columns The same meaning as in the transaction script



EI_Config – Other configuration and license settings

The worksheet EI_Config contains other configuration setting described in the table below:

Row/ ID Configuration setting Description

License

13/14/15/16/17 License key to a SAP system 1/2/3/4/5

Obsolete. Not used from version 2.50 and above.

18 License key to a computer Obsolete. Not used from version 2.50 and above.

General settings EI_C_LANG Language Enables choosing the product language. As

standard three languages are defined English, German and Polish. On the hidden worksheet EI_Texts the user can add definitions and translations to other two languages.

EI_C_NAME EasyInputName The name displayed in all EasyInput worksheets in the fifth row. Usually the name is connected somehow to the script/ scripts name.

EI_C_DS_ID DataSheet The reference to the data sheet. The data sheet must exist and have the required structure.

EI_C_DS_START DataStartRow The first row, from which data starts on the data sheet. Usually it stays 10, but can be given a larger value.

EI_C_DS_END DataEndRow Optional. Usually left empty (then the last row will be searched automatically).



Separate transactions can be separated by up to 4 empty rows.

EI_C_PREV_DOUBLE PreventDoublePosting Optional. Can be left empty or have X value. When set to X then it is impossible to run actual mode for all records (the user still cen use actual run for new records and for errors).

EI_C_BACKUP_BEFORE MakeDataBackupBefore Opitional. Can be left ampty, filled with O or A values. When filled with O/A values than data sheet will be copied after EasyInput run. For A (all) it will be done allways. For O (only for actual) it will be done only for actual runs.

EI_C_BACKUP_AFTER MakeDataBackupAfter Opitional. Can be left ampty, filled with O or A values. When filled with O/A values than data sheet will be copied after EasyInput run. For A (all) it will be done allways. For O (only for actual) it will be done only for actual runs.

EI_C_DEBUG_DET_MESG DebugMode DetailedMessages

Optional: Can be left empty or filled with X value. When set to X, messages contain more echnical information. Used mostly, when debugging scripts. Should normally be left empty.

EI_C_SKIP_IND SkipFieldIndicator Sign, that designates data not to be transfered. Can be left empty or have value that rarely shows in the script ,e.g. „/”. When configuration setting “Delta” is set, than if the data contains the value defined by SkipFieldIndicator, than the corresponding script line is not transferred to SAP.

EI_C_SKIP_DELTA Delta – do not pass SkipField values

Optional. Default value = X. When set to X, the data fields containing SkipFieldIndicator will be omitted in the script. When empty, EasyInput will not check data fields values and transfer them all to the script (apart form completely empty rows).

EI_C_WAIT_TIME WaitTime AfterTransaction When one script contains several transactions, that should be called one after another, and when the transactions data is relates, the user may force EasyInput to wait after each transaction for the system have time to post it correctly, before the start of the next transaction. The delay is stated in milliseconds. Setting anything greather than 0 will have negative influence on EasyInput performance.

EI_C_SUBLEVEL_REQUIRED SublevelRequired Sets the default for the sublevel data. If set to X, than the system assumes, that the



sublevel data (e.g. line items) are required. If not set, than sublevel data is treated as optional (may or may not be present in the data sheet). The default setting on the configuration worksheet can be overriden by the order ending: _O – optional _R – required

EI_C_SAP_GUI_USE UseSAPGUI Forces use of SAP GUI to process script data. Some moder transactions will not work without this setting.

EI_C_LOOP_BACK LoopBackwards If set, the sublevel data is processed from the last data row to the beginning. This is usefull, when transactions are recorded that way, that the data is always added in the first row, and allows the posted data to keep the order given in data sheet.

EI_C_AUTO_LEVEL_ORDER Automatic LevelOrder InDataSheet

If set the system tries to establis level/order on data sheet automatically based on the data entered by user. This can only work If the script does not contains overlapping data (various level/order assigned to one data column). For most of the scripts this requirement will be fulfilled.

EI_C_MESSAGE_TYPES_PRESENTED MessageTypesPresented Allows filtering the message types presented with the filtering string. String examples: * - all messages E – only error messages (type E) ES – error and informational messages (E and S) EWISA – error messages of types EWISA

EI_C_MESSAGE_VALUE_READ_STRING ReadValueFromMessage (ID-Nr-Param-Column [-Start-Length])

Allows copying one of the four message paramters of a chosen message (V1, V2, V3 or V4) to the selected data sheet column. This option is sometimes used to read back the document number given in a message. Example of a correct parameter: F5-312-V1-AH or F5-312-V1-AH-1-10 (first 10 characters)

EI_C_TEST_MODE_PRESENT TestModePresent If set to “X” than the test run is excluded from the dropdown list in the menu combo box. Useful when only actual run is to be performed (some function modules always commit changes and test mode cannot be easily implemented)

EI_C_RESULT_CHECK_STRING ResultCheckingString The result of the script call is set as follows: - If the called function module raises

an exception, than the result is set to error



- If the called function module/ transaction does not raise an error and return messages then these messages are analyzed according to ResultCheckingString.

The most popular setting is: E-E, where, the first E depicts that by default there will be success unless an error is found out. The second E depicts the fact that if there is a message of type E, than it is treated as an error. The full syntax of ResultCheckingString is: E|S-Type[-Id][-Nr], where message ID and message Nr are optional.

EI_C_MESS_DEL_BUTTON MessagesDeleteButton Allows switching on additional EI ribbon button, when on data worksheet. This button serves clearing last EI run results. Example values: X =AA10:AQ1000 (additional area to be cleared)

EI_C_DATA_DEL_BUTTON DataAreaDeleteButton Allows switching on additional EI ribbon button, when on data worksheet. This button serves clearing all data entered on the data worksheet. Both messages and data are cleared when the button is pressed. Example values: X =AA10:AQ1000 (other area to be cleared than default one)

EI_C_SHOW_PROGRESS ShowProgressWindow Allows displaying the progress window. Possible values: Empty – no progres window X – progress window always S – progress window above 200 data lines Number e.g. 300 – progress window above given number of data lines

EI_C_DATASHEET_AUTO_SWITCH AutoSwitchToDataSheet Allows automatic switching to another data sheet if two or more scripts are defined, that use different data worksheets. Possible values are: Empty – no switching X – switching, when script changed H – switching plus old data worksheet hiding when script changed

EI_C_HIDE_RIBBON HideEasyInputRibbonMenu Switches off the EasyInput Ribbon menu. Can be set (“X” value) when VBA macros are used to start EasyInput functions.



EI_C_HIDE_RUN_TYPE HideRunTypeSelection Hides the EasyInput menu part – combo box “Run type”. Usefull for scripts with only one run type e.g. for scripts reading data.

EI_C_CONFIG_PASS ConfigurationPassword Allows locking configuration (when hidden, that entering password will be required to show configuratiion from the menu). Warning! There is always the possibility to unnhide the EI_Config worksheet manually and check the password there.

TR settings (transactional script settings) EI_C_TR_SFM StandardRunFunctionModule Decides whether the standard SAP module

is used, or the module provided by BCC. If the transport request furnished with the full version of the program is not implementerd in the SAP system only the SAP function module can be used.

EI_C_TR_EFM ExtendedRunFunctionModule Decides whether the standard SAP module is used, or the module provided by BCC. If the transport request furnished with the full version of the program is not implementerd in the SAP system only the SAP function module can be used. Warning! Extended SAP module requres E-CATT swich active on the client level and additional user authorizations.

EI_C_TR_DEBUG DebugModeScriptTesting Opitional. Can be left empty, filled with A or E values. Used when debugging scripts. When A/E is set only the first data pack (usually one transaction) is performed with the option to show SAP GUI screen (A= all screens, E= only screens with errors). Additionally the script generated for the first data package is saved as a text file EI_Debug_*.txt. Such a file can be imported in SHDB transaction an tested in SAP GUI. The text file is saved to My Documents folder. When this option is switched on (E/A) then the status (Error/OK) of manually analyzed transaction is not set by the system in the data sheet. This option should be used carefully, when script debugging and only in SAP test systems.

EI_C_TR_MODE Mode Distinguishes between EasyInput operation modes: B-Standard – batch input set to X, only write C-Extended – batch input cleared, write and read allowed When only writing data to SAP the standard mode can be used. Important!



The extended mode can be used only in the full version of the product and requires the SAP system administrator to upload transports requests provided with the full version installation files. Important! The scripts for the standard (batch input = ‘X’ and extended batch input = ‘ ‘ modes can be different for some transactions). One should take it into consideration when recording script with SHDB transaction.

FM settings (BAPI/ functional script settings) EI_C_FM_CFM GenericConversion

FunctionModule Decides whether the standard SAP module is used for the not handled internally conversions, or the module provided by BCC. If the transport request furnished with the full version of the program is not implementerd in the SAP system, only the SAP function module can be used.

EI_C_FM_RET_TRIM TrimReturnedStrings Decides, that the strings returned will not have leading/trailing spaces.

EI_C_FM_RET_FIRST_ROW FirstReturnLineInTheSameRow Decides that if table is returned from function module, than the first row will be put into the last row of calling parameter (used when only one row expected)

EI_C_FM_RET_HEIGHT ReturnedRowHeight Decides of the hight of rows for table type returned data. If set to 0 then the height is taken from the row above the inserted row.

EI_C_FM_DEBUG DebugModeScriptTesting Opitional. Can be left empty or filled with X value. Used when debugging scripts. When X is set only the first data pack (usually one transaction) is performed with the option to show passed fo FM data on EI_Debug worksheet. Additionally the script generated for the first data package is saved as a text file EI_Debug_*.txt. The text file is saved to My Documents folder. When this option is switched on (X) then the status (Error/OK) of analyzed transaction is not set by the system in the data sheet. This option should be used carefully, when script debugging and only in SAP test systems.

EI_C_FM_COMMIT BAPI commit after actual function call

Decides whether after each actual function module call the commit with the BAPI_TRANSACTION_COMMIT should be executed (needed for newer BAPI methodes)



5. Recording scripts with the SHDB transaction (for transaction scripts)

SHDB = Transaction recorder, allows automatic transaction script recording for EasyInput. The Transaction recorder records user actions in a given transaction in the form of a script. Such a recorded script may be than copied to the EasyInput EI_Script_TR worksheet. Recording script with SHDB The easiest way to start the SHDB transaction is to enter SHDB into the command field in SAP GUI and then press Enter

On the main SHDB transaction screen the option to start new recording should be chosen

on the right data should be put in the popup windows that appears afterwards:

The most important data to be set here are:

- Recorded transaction ID (in the case above FB50) - The name under which the script will be saved (ANY_REC_NAME).

Important! When the recording is prepared for the standard mode (Batch Input) the Recording parameters should be left with their default values (as on the picture above). If the recording is done for the Extended mode then three Recording parameters should be changed:

- CATT mode should be set to A – CATT with individual screen control - Cont. after commit – should be checked - Not a Batch Input Session – should be checked

The next step is to start recording. The screen of the chosen to be recorded transaction should appear. From this moment on all user actions will be recorded. Usually one has to repeat script recording several Times to get a script without unnecessary user actions and without errors. Several rules of script recording: - to make script universal one has to think carefully how the recorded transaction work (in FB50 transaction where there are line items, it is worth to enter the data always to the first row, and add a new row above the preceding to always perform the same pattern for the data line. This will allow



to exceed the limit of ten line items visible on screen, and to treat the script for the first line as the script for all data lines) - During recording it is advisory to enter a value to all fields to which later EasyInput will provide a value (even if the value as default is already given). This will save us time on manually editing recorded script. - When EasyInput will be to read a value from a field it is advisory during recording to press Enter on the screen and to set the cursor on that field (click it with the mouse. This will add a new screen in the script(Enter) and record cursor focus line, where the user will later add read reference. After end of the recorded transaction the SAP system will show the script window.

Script contains script rows grouped for screens. Such a script if correct can be saved and copied to EasyInput Workbook. It can be done either manually or via a text file. Manual script copying Use the key sequence Ctrl + Y = switches SAP to mark area mode Than the user should mark the area from the first program field to the last field value field visible on the screen. Ctrl + C = copying the marked selection to the clipboard After switching to MS Excel, the clipboard can be pasted into the script (EI_Script_TR) columns F-J with the use of Ctrl + V or via ribbon menu. When copying manually, the copying should be repeated several times, because only data visible on a screen can be copied at once. Automatic script copying

First save the script to file by clicking Export icon (Shift + F8) on script change screen in SAP GUI. Then, on the EasyInput workbook, on the EI_Script_TR worksheet press the EasyInput ribbon menu button Import script file.



Script row meaning Although a recorded script contains many rows, and may seem quite complex at the beginning, but the rows can be easily assigned to only a few of row types. The table below makes the script structure more comprehensible

Script row Meaning

//T/Transaction/ Example: //T/FB50/

Informs that the script is recorded for a given transaction. Is placed always at the beginning of a recorded script. One EasyInput script can contain several recorded scripts one after another.

Program/Screen/X// Example: SAPMF05A/1001/X//

Informs about start of a new screen in the script. Until another screen row (or till the end of the script) all the script rows below are recorded for this screen.

///BDC_OKCODE/Code Example: ///BDC_OKCODE/=0005

Defines which key/button/ icon was pressed to go to the next screen (the next screen can be the same screen e.g. after pressing enter). The most common codes =OK or /00 for the Enter key.

///BDC_SUBSCR/subscreen Defines subscreens within the main script screen. Usually left without a change in the script.

///BDC_CURSOR /field Example: ///BDC_CURSOR/ ACGL_HEAD-BLDAT

Designates setting cursor to a screen field (e.g. clicking with mouse on a field). Used for example to read the data from the script. Reading data can be done only for such a line (requires filling reference information in columns K=ReadData & L)

///field /value Example: /// ACGL_HEAD-BLDAT / 31.12.2013

Designates entering a value to a screen field. Used to enter fixed values or values from the data sheet to a field (writing from Data sheet requires filling reference information in columns K=WriteData i L)

Manual script adjustments Sometimes the recorded screen can be used without any changes, but such a situation is rare. Usually the recorded script requires some manual adjustment. The most common script adjustments:

a) The script lines, that are not needed in our script can be removed or inactivated via entering „X” in the „E” column of the script worksheet (EI_Script_TR)

b) For script rows of type (///field / value), for which one want to enter data from the data sheet adding references in columns K & L is needed. Such lines if not recorded can be introduced to the script manually. To get a screen field name click on it, press F1 and then press the technical information icon. On the bottom of the technical information screen, the Screen Field can be found.

c) For script rows of type (///BDC_CURSOR / field), from which we want to copy data to data sheet adding references in columns K & L is needed. The field id can be checked the same way as described above.

d) Removing from the recorded script unnecessary information about repeatable parts e.g. the part referring the second line of the document (usually for such lines the script should contain a part only for one line, that will be repeated as many times as many data rows for the line there are in the data sheet. Remember about pressing inserting a new line to clear the first row in the recorded script to make place for the second row).

e) Adding additional script version with cancelling transaction before the save, for testing purposes. To be able to test transaction data it is recommended to prepare two script versions – for testing and actual run. Usually the versions can be identical up to last script screen. The most common change consist of setting on the last screen two action variants: Example of change in the last screen action:



Run type Program Screen Start ID Field name Field value A - Actual run BDC_OKCODE =BU

T - Test run BDC_OKCODE /ECNC

Adding at the end of the script the lines confirming the exit in the test run: Run type Program Screen Start ID Field name Field value T - Test run SAPLSPO1 0200 X

T - Test run BDC_OKCODE =YES

Important! For many transactions one can do the change manually basing on the example above. It is however always advisory to record transaction twice, once with a break before saving and then compare the scripts to detect the changes needed.

Important! When recording a transaction containing several line items it is recommended to: - Always insert new line before the first row (for each script line item) - Always enter the data into the first row - Record only the first line item (if while recording more were recorded, they should be

removed from the script) If these rules are followed the script will be ready to be repeated for any number of line item rows in the data sheet (the repeated script rows should be assigned Level value > 0 - see the description of the Level column of the script)



6. Selecting function module with BAPI repository (for function scripts)

In order to select the ID of a function module to be used in the BAPI/ function script, one uses the SAP system. In the SAP system, one calls the transaction BAPI (Business API Explorer). BAPI explorer shows Business Objects and their methods prepared for the interfacing with the SAP system.

When After double clicking on a method of an BAPI object, on the Details tab, one can see the function module implementing the method ID. This ID should be given to create the function script. In the BAPI Explorer one can read BAPI methods parameter description (it is recommended to log in to an SAP system with the English language, as most of the description are given only in English).



7. Tips & Tricks

It is recommended to analyze the scripts in the example workbooks (these workbooks may not work in the client SAP system as each system can be differently customized). Reading data from any SAP table with the use of function module RFC_READ_TABLE. Easy input can read data from any SAP table/ database view. This can be achieved using function script based on RFC_READ_TABLE function module. When no DELIMITER is set, EasyInput will cut the retrieved data and put separate fields into separate columns of the data sheet. See the example EI_FM_Ex_READ_ANY_SAP_TABLE. Using EasyInput in your own Visual Basic for Applications programs (VBA macros) For external use the following macros (API) are prepared. One can write VBA macros in the EasyInput sheets calling this predefined application Interface:

Macro Description Sub API_BCC_EI_SetScript(ByRef pWorkbook As Workbook, pScript As String)

Chooses the EasyInput script

pScript - Script ID or Script name to be

set

Function API_BCC_EI_GetScriptName(ByRef pWorkbook As Workbook, Optional ByVal pError As Boolean = True) As String

Returns the selected script name

Function API_BCC_EI_GetScriptID(ByRef pWorkbook As Workbook, Optional ByVal pError As Boolean = True) As String

Returns the selected script ID

Sub API_BCC_EI_SetRunType(ByRef pWorkbook As Workbook, pRT As String)

Sets the run mode

pRT - Run mode- possible values:

TR

TE

TN

AR

AE

AN

Function API_BCC_EI_GetRunType(ByRef pWorkbook As Workbook) As String

Returns the selected run mode

(TR,TE,TN,AR,AE,AN)

Sub API_BCC_EI_SetDataSheet(ByRef pWorkbook As Workbook, pDataSheet As String)

Sets the data sheet

pDataSheet - Name of the data sheet on the

EI_Config worksheet

Function API_BCC_EI_GetDataSheet(ByRef pWorkbook As Workbook) As String

Returns the name of the data sheet

Function API_BCC_EI_RunScript(ByRef pWorkbook As Workbook) As Boolean

Runs the set EasyInput script

Sub API_BCC_EI_ClearLevelOrder(ByRef pWorkbook As Workbook)

Clears the data sheet level/order columns

Sub API_BCC_EI_ClearResultMessages(ByRef pWorkbook As Workbook)

Clears the data sheet result messages

Sub API_BCC_EI_ClearDataArea(ByRef pWorkbook As Workbook) Clears the data sheet data area

Sub API_BCC_EI_SetConfig(ByRef pWorkbook As Workbook, ByVal pParam As String, ByVal pValue As String)

Sets the chosen configuration setting.

WARNING: This procedure does not check the

passed value in any way! The programmer

must ensure, that the passed value is

correct.

pParam – depicts the configuration

parameter to be set

pValue is the passed parameter value

Function API_BCC_EI_GetConfig(ByRef pWorkbook As Workbook, ByVal pParam As String) As String

Gets the chosen configuration setting.

pParam – depicts the configuration

parameter to be set

Sub API_BCC_EI_SetALO(ByRef pWorkbook As Workbook) Fills level/order columns on the data

worksheet.

Function API_BCC_EI_getLastDataSheetRow(ByRef pWorkbook As Workbook) As Long

Returns last row on the data sheet

GetConfig/SetConfig pParam most important values (for full list see EI_Config worksheet,

column A):

DS_START - data sheet start row (number >=10)

DS_END - data sheet end row (optional, number >=11)

PREV_DOUBLE - prevent double posting (X)

BACKUP_BEFORE - save backup data sheet before script start (X)

BACKUP_AFTER - save backup data sheet after script end (X)

DEBUG_DET_MESG - debug mode detailed messages (X)



SKIP_IND - character used as skip indicator (skipped if put on data sheet, can be left

empty)

SKIP_DELTA - setting telling that the skip indicator will be used, or all values will be

transfered (X)

WAIT_TIME - wait time between consecutive transaction call (used sometimes to slow down the

EI) (number in ms)

SUBLEVEL_REQUIRED - setting telling whether the sublevel (level more than 0) is required e.g.

for FI documents (X)

SAP_GUI_USE - setting telling whether SAP_GUI should be used for the script (needed for some

transactions) (X)

LOOP_BACK - setting telling that loops over sublevels should be done backwards (useful for

some transaction scripts) (X)

AUTO_LEVEL_ORDER - auto recognition of data lines (about setting of level/order) (X)

MESSAGE_TYPES_PRESENTED - message types that should be presented on data sheet (*=ALL, string

e.g. AESIW)

MESSAGE_VALUE_READ_STRING - string to get value from the message back (ID-Nr-Param-Column)

RESULT_CHECK_STRING - setting telling how result checking is verified (E|S-Type[-Id][-Nr])

CONFIG_PASS - string for config pass (can be left emty)

Important! If the data sheet is visible (Visible = True), then when running macro run script the sheet will be activated (shown). If it is hidden (Visible = False), this activation will not be performed. Important! To call any of the EI API macros the automation object should be constructed and its method should be used (see the example below). An example of own VBA macro using EasyInput API: Public MyEIMacro

Dim addIn As COMAddIn

Dim automationObject As Object

Dim pWorkbook As Workbook

Set addIn = Application.COMAddIns("EasyInput")

Set automationObject = addIn.Object

Set pWorkbook = ActiveWorkbook

' prepare and run the first script

Sheets("EI_Data").Range("Y12:AS5000").ClearContents

automationObject.API_BCC_EI_SetConfig pWorkbook, "DS_START", "10"

automationObject.API_BCC_EI_ClearResultMessages pWorkbook

automationObject.API_BCC_EI_ClearLevelOrder pWorkbook

automationObject.API_BCC_EI_SetScript pWorkbook, "CI"

If automationObject.API_BCC_EI_RunScript(pWorkbook) = True Then

' only run second macro if connection successfull

automationObject.API_BCC_EI_ClearLevelOrder pWorkbook

automationObject.API_BCC_EI_SetConfig pWorkbook, "DS_START", "12"

automationObject.API_BCC_EI_SetScript pWorkbook, "CB"

automationObject.API_BCC_EI_RunScript pWorkbook

End If

' read data from EI_Data worksheet and write result to EI_Example worksheet

CalculateReport

End Sub

Important! On the EI_ScriptName worksheet one can define user’s macros, that will be called before and/or after the EI Script run. This allows connecting own development and extending EasyInput functionalities. See EasyInput forum at https://easyinput.net to get more information on EasyInput.




8. Authorizations in the SAP system

8.1. EasyInput required authorizations The user needs following SAP authorizations objects to run the script: OBJECT: ‘S_RFC’

ACTVT: ‘16’ (=execute)

RFC_NAME:

SRFC

RFC1

STTF

BATG

BACV

MRFC

SDTB

SDDO

SUF4

SYST

SCTM

SBDC

/BCC/Z_EASYINPUT

RFC_TYPE: ‘FUGR’

8.2. Function script: When using BAPI/ Function script each function module used will require additional authorizations:

OBJECT: ‘S_RFC’


RFC_NAME:

ID_OF_THE_FUNCTION_MODULE

RFC_TYPE: ‘FUNC’

In older systems (SAP_BASIS application component < 702), the granularity of the authorizations has to be larger (function group). If this is the case use: OBJECT: ‘S_RFC’


RFC_NAME:

ID_OF_THE_FUNCTION_GROUP_OF_THE_MODULE

RFC_TYPE: ‘FUGR’

Important: When using function script with the SAP conversion module (in the full version one can use the module provided by BCC - /BCC/Z_EASYINPUT_RCONV, that does not require additional authorizations) following additional authorizations may be needed: OBJECT: ‘S_TABU_RFC’

ACTVT: ‘03’ (=display)

The user needs following SAP authorizations objects to use the BAPI transaction to choose the function modules (only the script developer needs these authorizations): OBJECT: ‘S_TCODE’



TCD: BAPI

OBJECT: ‘S_DEVELOP’

ACTVT: ‘03’ (=display)

8.3. Transaction script: Important: When using extended mode in the transaction script with the SAP function module (in the full version one can use the module provided by BCC - /BCC/Z_EASYINPUT_SIMPLE, that does not require additional authorizations) following additional authorizations will be needed:


OBJTYPE: ‘SCAT’

OBJNAME: ‘*’



OBJTYPE: ‘ECSC’

OBJNAME: ‘*’


Important: Using Extended Mode: When not using the BCC function modules for transaction script (parameter ExtendedRunFunctionModule on EI_Config worksheet, that can be set in full version if the BCC transport is imported in the system), than E-CATT should be allowed on the mandant level (SCC4 transaction) before being able to use the Extended mode.

The user needs following SAP authorizations objects to use the SHDB transaction to record the transaction scripts (only the script developer needs these authorizations):

OBJECT: ‘S_TCODE’

TCD: SHDB The user needs following SAP authorizations objects to debug a transaction within EasyInput:

OBJECT: ‘S_TCODE’

TCD: SHD0