Beas access parameters

Installation Instructions > Beas startup options > beas standalone options > beas Access parameters

Top  Previous  Next
Expand/Collapse Toggles

Beas can be directly integrated from SAP Business One via an Add-on or through "Accessing external programs".

Each Beas – function can be started using parameters. Separator for parameters is a blank character. If the parameter contains a space, please replace by AltGr-3 ( = ³ ).

Beas may only be started in home directory "%programfiles(x86)%\beas software\beas". Change directory before calling.

Beas can also be started via Windows-task planner. See tasks

 

See youtube Start Beas in different ways

The following parameters are available:

mrp=x

Calculates the MRP x
Example: Calculating the MRP2

beas.exe db=yyy server=zzz user=aaa pw=bbb mrp=2

The line can be entered as follows in the Beas –server:

tools=beasrun=mrp=2

batchcalc=x

Performs the corresponding batch calculation

beas.exe db=yyy server=zzz user=aaa pw=bbb batchcalc=2

The line can be entered as follows in the Beas –server:

tools=beasrun=batchcalc=2

Terminal

The application "terminal" is started.
Note: it has to be set up first in Program group Administration

 

1.Create a link on the desktop to C:\program files\beas software\beas\beas.exe
2.Beas start using the link and register once to ensure that the credentials are stored correctly.
3.End Beas.
4.Edit link (right-click)
5.Enter in target box: "C:\Program files\beas software\beas\beas.exe" terminal db=trainingdb"
(the appropriate directory name and the correct database name need to be specified)

 

A logon with username "terminal" is executed. This user may not be registered as SAP Business One- or Beas-user, because he has special authorizations (license and program).

SAP Business One-transactions are executed for the user who is entered in Configuration wizard > System > DI-API.

On the terminal SAP Business One this is not required, only in the SAP Business One-DI-API.

 

Note:

Logon is executed with the user name "terminal". This user may not be created as a  SAP Business One- or Beas-User, as he has special authorizations.

SAP Business One-Transactions are executed with the user set up in Configuration wizard > System > DI-API. On the PC-Terminal no SAP Business One needs to be installed. But the SAP Business One-DI-API is required. One SAP Business One - Indirect – License is required per work station.

See Licenses.

 

Note:

The parameter "USER" may not be used. If this is used, the actual user needs to have a Beas  – Basic-License.

 

 

Note:

One DI-API-user per terminal needs to be defined and called up:

(x86)\beas software\beas\beas.exe" terminal user=TERM1  pw=XXXXXX server = SAP9-2016 db=SBO_XXXXXXX_PROD

 

Please consider SAP licensing conditions!

 

see Program group Administration

see also Authorization control DI-API User

terminalanw

Attendance Login/Logoff terminal

/shortdebug

Allows to analyze the program at start

 

a) Beas directly opens the debug window

b) Beas creates a debug log in the file  %temp%\beas\beas.log e

 

An error message is displayed at the program start because the debug window has no access to the database. The first error message.

 

/debug

Generate a debug file on assembly level. You can use this for deep analysis.

The debug file beas.dbg is located in the same folder as the program itself.

It only works if you start Beas with Admin Rights.

task=x

Executes a script which is stored in planned activities. Executed in server mode., Once finished, the Beas instance is closed.

see

planned activities

Tasks

form=<formname.psr>

Opens a form (PSR File) directly. If started with SingleMode (/ms), the program will close when closing the form.

server=<servername>

Name of server. Replace spaces with letter "³"

If no servername is defined, beas uses the last used server.

db=<database>

Database index (n-th entry in database list) or database description or client description. Replace space by _

user=<User-Id>

Enter the SAP-User-Id which the program uses for logging on. If a user is entered, the Parameter "pw" is required.

 

Terminal-Mode: The entered user needs the respective Beas – License and Authorizations. The terminal license is not applied here.

pw=<User-Pwd>

The associated user password

dw=<PSR-File>

Opens corresponding window at program start

befehl=<Command>

Submit command to a window. Several command parameters can be specified

/ms

The master window is not opened. Program works in "Single window mode"

/pn

No pop-up window at program start

/f

No footer window

/tb

Do not display toolbar

/ws

Do not load user window settings

/st

Do not load language table

/sw

Single window. If the window specified at start is closed, the whole application is closed.

/sm

"Small menu". Only the menu items "Edit", "Window" and "Help" are available

s_parm1=<value>

Set variable s_parm1 (…4)

c_parm1=<value>

Set variable c_parm1 (…4)

script=<file>

Executes the Beas script. If this contains <cr_lf> , it is executed as a batch routine. Blank spaces must be replaced with ³

 

Important:

If only one function (Object) is called, the program needs to be closed afterwards with "app=close"

 

Examples:

beas.exe db=yyy server=zzz user=aaa pw=bbb script=messagebox=hello³world

 

Alternatively, the Beas script can be stored in a file

beas.exe db=yyy server=zzz user=aaa pw=bbb script=$c:documents³and³settings\user\myscript.src<cr_lf>app=close

 

(Note: the character ³ is accessible via ALT+3)

 

To call an object directly, put in quotation marks, otherwise it would be incorrectly interpreted.

 

Example: Post-calculation

beas.exe db=yyy server=zzz /inservermode script="<cr_lf>setstr=c_parm3=3<cr_lf>object=ue_fert_naka=batchnaka=3<cr_lf>app=close<cr_lf>"

 

Alternatively a task can be created and the stored script can be executed with "task=x" see Tasks

/language=<language>

defines the user language (only if the standard behavior has been disabled under Extra/Options/General)

servermodus

Beas starts as "server" Alternative to the server service in local mode

/inservermode

Beas starts in server mode. This means that all messages are blocked. Use this to execute scripts.

/debug2file

Activates the debug to file mode at Beas  startup.

See topic System Information > Settings > "Debug to file".

Available from 2020.05.

 

Examples of Beas call up

 

Examples: Enter correct values for user, password and database.

 

Terminal on "Demo" database,

beas.exe db=demo terminal /pn

 

Report currently present

beas.exe user=manager pwd=manager db=mustermann dw=bde_anwesenheit_aktuell.psr /sw /pn /ms s_parm1=onlypresent

 

Report on client "Mustermann", prevent popup

beas.exe db=mustermann report projekt\mustermann\reports\meinReport.rpt /pn

 

Report item_description.rpt for item 100.344

beas.exe report artikel_edit_beschreibung /pn /dv=Artikelnummer:=100.344

 

Open item processing for 100.344 with User Manager, end program, when window is closed, use small menu and no popup

beas.exe db=mustermann dw=artikel_edit s_parm1=100.344 user=manager pw=manager /pn /sw /sm

 

Call only order time receipt, close the program immediately afterwards

beas.exe dw=fert_arbzeit_erfassen.psr user=manager pw=manager db=trainingdb /sw /ns /ms

 

Note: .rpt or .psr NO longer need to be specified.

 

Calling up several instances in parallel, (eg. multiple terminal users) the name of the currently logged on user can be displayed in program title.

Insert "app=title=beas: <currentuser>"

 

Concept: call up via windows task planner

See: tasks


Help URL: https://help.beascloud.com/beas202102/index.html?beas-aufrufparameter.htm