Administration > System initialization > Configuration wizard > System - robinfeng/beashelp GitHub Wiki

Administration Financials Business Partners Sales Master Data Production Quality Control Materials Management Calculation Attendance Business Performance System

The options of the the "System" section in the configuration wizard are described here.

Field Description beas check for messages activate hmtoggle_plus1 Determines, if beas checks for new messages regularly If enabled, (default) beas checks regularly (at the same time as SAP checks) for new messages in beas - messages system. This option may only be activated, if you do not use the beas message system. Disabling the option, you will get no notes if a message arrives. the message system itself is not disabled. See Messages, Activities beas9.0-004-033-000 Variable beasmessagedisable, Default J

Extended error message beas can automatically create activities for the current user if certain errors occur. Further measures are described in this activity. If the current user is a terminal or pure beas user, they will be unable to receive these messages. In this case the recipient is specified here. Field Description Extended error message Determines if and how the extended error messages should be activated Default = beas activity. This setting as recommended as this is the only way to have access to the full functionality.

beas activity: a beas activity is generated and displayed in the beas message window. SAP Business One activity: a SAP Business One activity is generated. a business partner must be specified on which this activity is set. If no business partner is stored, a beas activity is generated automatically. NO: no activity is generated. Recipient activity Determines who receives this activity if it is created by a terminal or pure beas user without a SAP Business One account. Activity business partner Needed if working with SAP Business One activity. For activities, a business partner must be specified. Ideally your own company should be created as a customer and this entered here.

DI API If you log in to beas without SAP as a pure beas user or as a terminal user, beas requires an access account to DI API. Special Authorizations are required for this user. Configuration also possible in beas logon (without SAP) in the logon screen under Options. Field Description B1 API User hmtoggle_plus1 Administration User - System user beas requires administrative access to SAP Business One for database check, and check of transactions, which are executed via different interfaces,WEB-server,beas-server and the terminal. The SBO user entered there, does not require a SAP Business One Professional-User-license. The user requires special authorizations See required SAP Business One - rights (See Terminal) SBO API Set Password Click on the "Set Password" button , to set the password for the API user. SBO API Test Test the connection between the entered user and the DI API by clicking on the "Start Test" button.

Further Setup Browse: Max. number of lines to be displayed hmtoggle_plus1 Maximum number of rows In all lists and selection windows (not analyses, however), only a certain number of lines is shown to facilitate the presentation of the result on the screen. The maximum number of result lines can be set here. The higher the number, the longer it takes for the display to show, and the higher the load on the network or the server. Default : 200 If a list contains more rows than set up here, on the bottom right corner binoculars are displayed. Clicking on it, all rows are displayed. Drop down with full text search hmtoggle_plus1 Drop down full text search Relates to beas window with selection columns (drop down) During selection, you can limit the selection in the drop down area by entering the search term. If the option is activated, the entry must be a part of the selection. If the option is deactivated, the selection must begin with the entry.

Example Selection: Hans Harald Input: Harald

The term will be found if full text search is enabled. If search is deactivated it will only be found if "Hans" is entered. Directory for customer-specific extensions hmtoggle_plus1 Project folder - Main folder Determines the local directory where customized extensions are stored. If you leave the field empty, the directory is determined automatically. Only one directory for Client and Server.

Below the defined directory the following structure is created:

[chosen folder] |_ AddOn |_ [one folder per AddOn] |_ project |_ standard (default folder for customizing scripts] |_ [customer-name] (Folder for customer specification)

Example: In AddOn-Administration - Customer-Specification - Directory was set up:"beas" In configuration wizard \myserver\project
Customized extensions will be saved under: \myserver\project\project\beas

Important: The directory needs to be accessible from all clients

Advantage: for a central directory: no distribution on clients needed

Disadvantage: network can be overloaded

Note If beas is started in service mode, there is no access to the local directory. In this case a central directory is mandatory.

Without definition If the directory is not defined, by default there is a local directory and one on the server. At program start the server directory is checked for a newer version. If yes, this version is copied to the local directory.

Directory on server: [b1_shr]\beas\project[customer name] Local directory: [%programdata%]\beas\project[customer name]

see also: customizations

返回 主页