Showing posts with label Enterprise tools. Show all posts
Showing posts with label Enterprise tools. Show all posts

Unix commands used in BAAN ERP


UNIX Commands
Note:  UNIX is case sensitive.  Be sure to type the commands as they are listed.  UNIX considers the capital and lower case versions of the same letter to be totally different.  Be careful.

cd Changes the current working directory to the directory you indicate.   
To move back to your home directory, type cd.
To move to a directory that is not a subdirectory off the current  working directory, you can use a full pathname – one that begins with a slash.  For example, to look around in the /usr directory (where all home directory are stored), you can type
cd /usr


Example:
You log in and do some work in your home directory.  Next, you want to move into your budget directory to see which file are there you type:


cd  budget


clear Clears the screen.  This command doesn’t’ affect files or jobs – it just clears the clutter from your screen.


clear


Example:
You just tried to use the cat command to lock a word-processing document and your screen is full of gibberish.  Type clear.


cp Copies one or more files.
If you know DOS, you may think that omitting the second filename tells cp to copy a file into the current working directory.  This technique doesn’t work in UNIX – instead, use a period (.) to copy a file into the current directory.


NOTE! What happens if you copy a file to a new name and a file already has that name?  Assuming that you have permission to write (change) the existing file, UNIX blow it away and replaces it with the copied file.  Always use the ls command to check that your filename isn’t already in use.  And use the –I to tell cp to ask before overwriting a file.


cp [-I] oldfiles newfiles
or
cp [-I] [-r] oldfiles directory [/newfiles]
-I    Ask before you replace an existing file with a copied file
ksh fix.it.up
mkdir Creates a new directory.
mkdir directory 
directory – Specifies the name of the new directory.  If the name doesn’t begin with a slash, the new directory is created as a subdirectory of the current working directory.  If the name begins with a slash, the name defines the path from the root directory to a new directory.


You must have permission to write in a directory to create a subdirectory to it.  For the most part, you should create directories in your own home directories or subdirectories of it.


mkdir temp


more Display information one screen at a time so that you can read it easily.
ls |more
You receive a file (new.fil).  To display it on your screen type.


more new.fil
mv renames a file or moves it from directory to another.
mv [-I] oldname newname


ps Display information about your processes (jobs).


You wonder weather the process you ran in the background is still running.  Type:
ps
to see a list of all your processes.  To see more information about them type
ps –l
pwd Display the name of the current working directory.
rm Deletes (removes) a file permanently.

Audit Management in BAAN ERP

Audit Management, which is used in relation with Databases to record the changes that were made in the data. 



Using Audit Management
Audit management is used to track the changes to an existing application or company table.  The audit data is stored in the files of a database independent format and can be printed per date and time, per session, or per user.  The audit files are created and maintained by a UNIX process that communicates with the bshell.  This process is called the audit server.
For parameter tables within BAAN Software, Audit Management is mandatory to use. For other tables it is optional. It is supposed to be for critical data. 

  • Keep track of all commands which affects the table data (Insert / Update / Delete)
  • Mandatory for Parameter Tables
  • Optional for other Tables
The Implementation of Audit Management


The procedure begins with defining, for each table field, whether or not an audit trail is allowed.  Next, the audit trail field of the database definition is set to yes and the location of the audit files is defined.  Then, the default audit file parameters are specified in the ${BSE}/lib/audit_spec file and various security levels are assigned to all users.  If desired, the parameters of the audit files of particular tables can be changed afterwards.
As a result of this procedure, the changes made to several BAAN IV tables can be tracked.  It is also possible to print the audit data.


Print Range of Audit Files
The purpose of the Print Range of Audit Files session is used to get information from the Audit files.


Related Posts:

Database Management in BAAN ERP

Introduction
BAAN applications store data in tables. This data is modified, processed, and printed using several different sessions. BAAN Tools offers tremendous flexibility regarding data storage.


Database Management Procedure


Database Management Overview


BAAN is database and hardware independent. In other words, you can store your data in BAAN Base, Oracle, Informix, and other formats. Moreover, this data can be stored on the machine where BAAN is started or on one or more remote machines on your network. The format and location of data is totally transparent to your application.

Database Management within a Package Combination

Files in the directory structure that give information about the databases are listed:
  • tabledef6.1 What kind of database is used
  • isamdef.1 Where are the Isam tables
  • auditdef6.1 Where are the audit files
  • compnr6.1 A list of shared tables
  • ddOPER The database independent model for this Package Combination
Related Posts

Different Method Using VRC Management


The procedure begins with the creation of a new package combination and new package VRCs.  The developers and their company number are linked to the new package combination.  Runtime help information for the new VRCs are created, and the developer data is modified.  Next, the normal users are linked to the former development package combination.  Their company numbers are also linked to this new package combination.  Finally, the changes in user data are converted to runtime.
The result of this procedure is a new development package combination, which is used by the developers.  The former development package combination has become the new live package combination, which is used by the normal users.




Software components can be exported from one VRC and imported into another.  In this procedure, software components of a certain development VRC are released by exporting them to sequential files.  These files can be imported into a different VRC.  Next, the copied software components are compiled, dumped, or converted to runtime.  Finally, the runtime help of the copied components must be dumped.

Customized software components are normally created in a development environment.  Normal users cannot use these software components, because these users are linked to a package combination, which contains other package VRCs than the development environment.  After testing, the customized components are released for use by normal users.

Package VRC

A Package VRC is a package, which is indicated by a VRC. Within each PVRC, various components can be created and/or modified. The advantages of using PVRCs are:

  • standard software cannot be overwritten
  • new software components can be developed and tested in a protected environment before releasing them to production
  • a PVRC does not contain all software components, only new or changed components
  • development authorizations can be set by PVRC

The software components that can be created and/or modified within PVRCs are:

  • Labels
  • Forms
  • Menus
  • Reports
  • Sessions
  • Functions (Include Files)
  • Program Scripts
  • Messages
  • Questions
  • Domains
  • Table Definitions
  • Dynamic Link Libraries
  • Charts

Package Combination
A Package Combination is a combination of individual PVRCs, but only one VRC from each package.
A working environment is determined by:
  • package combination code
  • various PVRCs
  • company number(s)
  • users
Assigning a Package combination to a user in a company:
Example
This slide depicts two environments: a Production environment (OPER) and a Design Environment (DSGN). The Design Environment is based on the Production Environment because of the derived from structure of the Package VRCs. Everything that is created in the Design Environment will not affect the production environment unless it is released. 


Users are linked to a Package Combination in order to find the software components at runtime. 
Developers will create/modify software components. To be able to run the software components, the developer is linked to a package combination like the user. But in order to create new software components, the developer needs a Current Package VRC.  If authorized, the developer can switch between Package VRCs.


Related Posts:



Version Release Customization(VRC) in BAAN ERP

Introduction
Unlike conventional products, such as cars or furniture, computer software is dynamic in nature. Rapid technological advancement, changing customer requirements, bug fixes, etc., make it imperative for software houses to regularly introduce newer versions of their software. Failure to do so would be disastrous for customers as well as the software house.
However, managing these different versions, their corresponding releases, and all the different customizations performed on them becomes a nightmarish task.


Different kinds of Software

BAAN software is divided into packages. There can be:

  • Standard Software
  • Localizations
  • Line of Business
  • Customizations
  • Own 

The bshell usually searches for a software component from the outside to the inside (see Figure ) .  First, the bshell searches for any own customization for that component.  If there is no own customization, the bshell searches for a customer-specific customization, and so on.  The search path, however, is not the same for all users depending on the package combination to which the user is linked.

Components of a Package VRC

V (Version) - indicates a major change in the software
R (Release) - indicates a minor change or new enhancement
C (Customization) - indicates a customer extension, which uses the customer’s initials

Types of Software:
VRC management can be used to distinguish between various types of software. Baan delivers standard and localization packages. The customer has the option to customize the software to meet their specific needs.
A VRC should be coded using the following legend:
  • L:  Localization
  • B:  Line of business specific
  • C: Customization developed by a third party
  • O:  In-house customization
Rules: When creating a new package VRC that is derived from a standard or localization VRC, you must include one of the letters from the previous legend.
For example:
Existing VRC = tiB40a
New VRC = tiB40Ca cus

Package VRC Deviation Structure

Related Posts:

Device Management in BAAN ERP

Introduction
Generating output is one of the most important tasks of an information system.  Raw data is fed into the system and processed.  The processed data must then be sent to a suitable output device such as a printer, a terminal screen, or a file to be of further use.


Figure Representing Device Management:


Device Types:

Within BAAN Software the following Device Types can be defined:
  • Printer (Physical Printer)
  • Direct (also a physical printer but not handled by the print deamon)
  • Logical Printer (set of physical printers)
  • Append to File
  • Rewrite File
  • Screen
  • Aux. Port
1) Screen Device

2) File Devices

There are two different File Devices:

  • Append
  • Rewrite

If required, you can make use of a converting program to convert the output into other formats, for example, ASCII format. 
The user may assign a name and directory path to the output file.

3) Printer Devices
There are three kinds of Printer Devices:

  • Printer
  • Logical Printer
  • Direct

4) The Printer Device Types
A Printer Device is handled by the BAAN shell script lp6.1. This shell script contains the UNIX commands for different kinds of hardware platforms. To define a Printer Device, you have to specify the UNIX Spooler name of that printer, for example pr1001. 
The Logical Printer is group of physical Printers.
The Direct Printer is handled directly by UNIX. You have to specify the whole UNIX command like: /bin/lp -c -dpr1005 -n%d -s %s. See the paragraph on Maintaining Device Data for an explanation of this command. 

5) Device Queue and Printer Daemon
The Device Queue is the Tools Table ttaad320, which contains all the Print Requests. This table is used by the Printer Daemon to register the Requests and to handle them. 

User Management in BAAN ERP

Introduction
One of the most important tasks in an information system environment is effectively managing and monitoring system usage.  Special user requirements and restrictions may have to be implemented.  BAAN provides comprehensive facilities to handle user and security management.


Login Procedure

Users can login and work with the BAAN software if their user accounts are defined at two different levels:

  • UNIX
  • BAAN

With all the User Interfaces, the password file is checked for the right login code and password. With BA and BX, settings like the BSE-variable are set in the “profile” files. BW has these kinds of settings in its configuration screen.
When a user logs in, the Bshell accesses the user file in ${BSE}/lib/user directory.  The information in this file is used to tell the system what authorizations the user has and what system settings will be


UNIX vs. BAAN Profile
Normally, a UNIX user has one BAAN Profile. However, you can base two or more BAAN Profiles on the same UNIX Profile. This can be beneficial for Users who need to work in Production, Test, or Design environments. They just have to remember one UNIX password. 
Switching between your User Profiles means setting your $USER variable. 
Example:
From your BW configuration enter 
-- -set USER=jan
in the box labeled command:. Running this configuration will switch you from user jp to jan as shown in above figure.

Overview User Management 
User Management in relation with DEM
This slide depicts some overlapping features within User Management in Tools and the Dynamic Enterprise Modeler. With DEM you can create a User account and generate Session Authorizations. Then if you need some additional authorizations or you need to make some changes you can use Tools.  The entire user management process can be done through Tools; however, DEM is a quick start creating users.

User Types and Authorizations 

There are two different user types: 
  • Super 
  • Normal
Depending on the User Type and on what kind of permissions a user needs, you can set the following authorizations:
  • Session
  • Database
  • Company
  • Text
  • Developer
  • Terminal ( only if terminal is connected to a fixed tty port)
Steps in Creating BAAN Users
Figure outlines the steps necessary to create a user.  The first step is creating a UNIX id for the user.  Once we have the UNIX id we can then create a BAAN id for the user.  To activate the id you must do a convert to runtime.  The steps on the right are additional steps to add the appropriate authorizations.

Application Dictionary(APDD) vs Runtime Dictionary(RTDD)

APDD are the Tools Tables of Company 000. With the Tools application, you will maintain the BAAN Software creating entries in Company 000. These changes need to be moved to the directory structure by:

  • Compilation:  Reports, Program Scripts and Dynamic Link Libraries
  • Generate Dump:  Forms and Menus
  • Conversion:  User Data, Database Information, etc.
  • Direct Available:  Means that those tables are used at runtime as well
It is important to note that those items requiring a conversion will require the user to log off and login again.  This needs to be done because critical data has been changed at the Operating System level. Logging in / Starting the application again means that the bshell is able to read the changes.
Another important table is the runtime table (ttadv999). This table can be considered as a kind of shopping list for the Bshell. If the Bshell needs to run a session, it uses the information stored in the runtime table (ttadv999) to locate any objects, forms, reports, etc. which are linked to that session.
  • Object
  • Form
  • Report
Related Questions:

  • what is the need of converting software components to runtime data dictionary after any change in software component.?
  • Why this is recommended that after any change in software component  we should log off Baan and login again? 

${BSE} directory

In the ${BSE} directory there are many subdirectories with software, settings and log information.

Software:

  • application: In the application directory runtime dumps of software components, like forms, menus, and report objects are stored.  Each Package VRC has its own separate directory. 
  • bin: This directory contains UNIX programs used by BAAN IV.  The Bshell (Logic Server), Database drivers and many more programs are stored there.  A few examples of these programs are:
ba6.1; ASCII display server
bx6.1; X-window display server
shmmanager6.1; shared memory manager
  • include6.1: This directory contains several files for standard functions and definitions used by the bshell during the compilation of program and report scripts.
  • tools: The Tools software and its table and domain definitions are stored separately in the ${BSE}/tools directory.
Logging:
  • tmp : BAAN IV provides the capability to repeat print requests by storing temporary files for print requests in the ${BSE}/tmp directory.  The files in this directory all start with tmp.  
  •  log:  If an error occurs while the application is used, an error message is displayed on the screen.  These error messages, as well as information, is stored in a log file in the log directory.   Some examples: log.bshell, log.audit, log.repgen6.1, log.bdbpost. 
Settings:
  • etc :This directory contains a number of shell scripts used by BAAN IV.  Scripts for start up, shut down, and job management can be found in this directory.
  •  lib :The ${BSE}/lib directory contains the settings and driver information files. 
.
The ${BSE}/lib directory
The ${BSE}/lib directory contains definition files for:
  • Users
  • Software
  • Data
  • Devices (printers)
Users
In the ${BSE}/lib/user directory, you will find the user files. These files contain information about users, such as:
  • Start Menu
  • Default Company (Set of Data)
  • Package Combination (whether the user is in the Production Environment or in the Design Environment or elsewhere)
An example of a User File:

{BSE}/lib/tabledef6.1
 
Data
  • tabledef6.1: WHAT kind of Database Management System is being used for the BAAN IV tables.  If tables are installed on a remote system, the name of that system is also displayed in the file.
  • isamdef6.1: WHERE to find the tables for B-base databases.  The file contains the addresses of the ISAM tables on the system.
  • compnr6.1 :  Used in the case of “SHARED TABLES” 

The ${BSE}/application directory

Software components are stored in the $BSE/application directory by Package VRC. Here is an example with the directory tdB40_b (Distribution BAAN IV b). The module sls is Sales .
  • ftdsls2 Forms, English Language (Lang. 2)
  • mtdsls2 Menus, English Language (Lang. 2)
  • otdsls2 Report Objects English Language (Lang. 2)
  • otdsls Objects
  • ptdsls Program Scripts (if any)
  • itdsls Include Files
  • rtdsls Report Scripts
Note: Program Scripts do not automatically come with the system.
Terminology:
  • Language Dependent
  • Language Independent

Tables Directory (Bbase)
If a B-base database is used, the data of the BAAN IV application is stored in ISAM tables in the tables directory.
In this Figure , the tables directory contains sub-directories for the different company numbers which are used within BAAN IV.  A directory of a certain company number consists of several sub-directories for the different modules of the BAAN IV packages.  In these directories, the data is stored in ISAM tables.
An ISAM table consists of two UNIX files.  For example, tsls040200.bid and tsls040200.bdt.
The file with the .bdt extension contains the table data.  The file with the .bid extension contains the table index information.
In other Database Management Systems, parameters will be set to point to those tables in that database.


${BSE}/dict directory
The place of the dict directory can differ from installation to installation. It can be set up in, for example, /usr1/dict or /usr1/bse/dict. This figure depicts:
  • Tools tables by modules
  • Database Independent Model (table and domain definitions) 
In regards to Tools, it is important to note:
  • The Tools Tables are company 000 representing the APDD (Application Data Dictionary).
  • Tools can be divided into several modules
Some of the Tools modules are:
  • aad Application Administration
  • adv Application Development
  • txt Text
  • iex Import / Export
The Database Independent Model consists of files with domains (characteristics) and table definitions (the layout of the tables).




Directory Structure



The Bshell acts as the logic server gathering information from the directory structure at the Operating System level. This information can be system settings or software components.  System directory paths and users definitions are examples of the type of informational settings that can be set.  Software components are objects, forms, menus, reports, etc. 
These settings and software components are created with the use of the Tools software. The Tools software writes the information in the Tools Tables (company 000).
This information must be converted into a runtime object that is made available at the operating system level.  These runtime objects are created by doing a Convert to Runtime Data Dictionary, a compile, or using generate dump.  The Bshell can now use the converted object.


DIRECTORY STRUCTURE



This figure depicts the relationship between Users, Software, and Data. Users use the software to provide an interface between them and their data.  This data can consist of system parameters or user data.
The ${BSE}/lib directory contains the setting and driver information files.
BSE is the name of a variable, which stands for BAAN Software Environment.  The location of the software environment is defined by this UNIX environment variable.  Each BAAN IV user must have a correct BSE variable set up for them.
Different user interfaces are available within BAAN. The type of equipment being used determines which user interface the user will execute.
If the user is running BA (ASCII), the environment variable is set in UNIX files like /etc/profile and a personal .profile in the home directory of the user. If you are using BW, it is set in the BW Configuration screen. 

BSE ENVIRONMENT
Short description of directories:
bse         BAAN Software Environment, it contains the software environment.
dict The dict directory contains sub-directories for the table and domain definitions                
                (data dictionary)  of each package combination as well as the BAAN IV Tools
                 package(company 000).
tables      If a B-Base database is used, the data of the BAAN IV application is stored in ISAM       
                 tables in the tables directory.
test           If a B-base database is used the test tables are stored here


Related Posts:

WHERE Conditions and Functions



Within the WHERE clause, the operand1 can be one of the following:
  • Numeric constant
  • String constant
  • Table Field
  • Numeric Expression
  • String Expression
  • Special Field (enum, date)
  • Combined Field
Operator Syntex Figure


The operator is used to compare or set conditions between operand1 and operand2.

Operand Syntax:


Overall syntax for WHERE statement:


Arithmetical Operators for WHERE Conditions:

  • [+] [-]: Positive, Negative (value indicators)
Example: Show negative stocks.
SELECT dmoes001.item,
dmoes001.dscr,
dmoes001.stck
FROM dmoes001
WHERE dmoes001.stck=-10
  • [+] [-]: Adds, Subtracts (binary)
Example:
SELECT dmoes001.item,
dmoes001.dscr,
dmoes001.stck, 
dmoes001.ostk
FROM dmoes001
WHERE (dmoes001.stck-dmoes001.ostk)>50
  • [*]: Multiplies
  • [/]: Divides
Example: Check 30% profit or more.
SELECT dmoes001.item,
dmoes001.dscr,
dmoes001.ppri,
dmoes001.spri
FROM dmoes001
WHERE dmoes001.spri>dmoes001.ppri*.3

Relational Operators for WHERE Conditions:
  • [=]: Equality test
        Example:
SELECT dmoes001.item,
  dmoes001.dscr,
dmoes001.stck
FROM dmoes001
WHERE dmoes001.item = 10
  • [!=] [^=] [<>]: Inequality test.
   Example:
SELECT dmoes001.item,
dmoes001.dscr,
dmoes001.stck,
dmoes001.ostk
FROM dmoes001
WHERE dmoes001.ostk <> 10
  • [>]: Greater than
  • [<]: Less than
Example:
SELECT dmoes001.item,
dmoes001.dscr,
dmoes001.stck,
dmoes001.ostk
FROM dmoes001
WHERE dmoes001.ostk < 10
  • [>=]: Greater than or equal to.
  • [<=]: Less than or equal to.
Example:
SELECT dmoes001.item,
dmoes001.dscr,
dmoes001.stck,
dmoes001.ostk
FROM dmoes001
WHERE dmoes001.ostk <= 10

Logical Operators for WHERE Statements:
  • AND:
Returns TRUE if both component conditions are TRUE; otherwise returns FALSE.
Example:
SELECT dmoes001.item,
dmoes001.dscr,
dmoes001.stck,
dmoes001.ostk
FROM dmoes001
WHERE dmoes001.ostk > 10 and
dmoes001.stck > 10
  • OR:
Returns TRUE if either component conditions are either TRUE or unknown; otherwise     returns FALSE.
Example:
SELECT dmoes001.item,
dmoes001.dscr,
dmoes001.stck,
dmoes001.ostk
FROM dmoes001
WHERE dmoes001.ostk > 10 or
dmoes001.stck > 10
Example: OR clause using parentheses
SELECT dmoes001.item,
dmoes001.dscr,
dmoes001.stck,
dmoes001.ostk
FROM dmoes001
WHERE (dmoes001.igpc = “010” and dmoes001.spri > 50) or
(dmoes001.igpc = “020” and dmoes001.spri > 100)
  • NOT:
Returns TRUE if the following condition is FALSE; otherwise returns FALSE.
  The NOT condition is used with these conditions:
Between
In
Like
The NOT is placed in front of these conditions.

Select Internal Functions in SQL


Key Words

  • min
  • max
  • avg
  • sum
  • count
Select Statement Optional Functions

In the SELECT statement you can use the following built-in functions:

  • COUNT number of records

Example:
SELECT COUNT(dmoes001.item)
FROM dmoes001

  • AVG average value in column

Example:
SELECT AVG(dmoes001.spri)
FROM dmoes001

  • SUM sum of the values in column

Example:
SELECT SUM(dmoes001.spri)
FROM dmoes001

  • MAX maximum value in a column

Example:
SELECT MAX(dmoes001.spri)
FROM dmoes001

  • MIN minimum value in a column

Example:
SELECT MIN(dmoes001.item)
FROM dmoes001



Share

Twitter Delicious Facebook Digg Stumbleupon Favorites More