Sr

Information

Link

Size

1

Displays the menu tree of the tool (Analysis Generator)

Basics of analysis on baan table (including authorizations, search criteria ,document properties , specific values etc)

2 MB

Shows the user authorization of analyses based on table companywise. With this tool , it's possible to authorize each analysis for particular user and company

Shows the available aggregate functions (total,min,max etc) for data type of  query field

Shows the variable/ field type (Row/column/data) in query fields

Displays Selection criteria for enum and date type of fields. Any kind of enum field and date field can be entered with same ease with which data can be entered in entire Baan

Selection criteria for specific values in an analysis are shown . User can specify specific values of any field type up to 127 .

Selection criteria for specific companies to be used. Users can combine various companies with ._compnr field.

Shows formulae among query fields can be constructed with proper validations. Invalid formulae are rejected. Formulae allows user to manipulate data values at the Extract level (not at Load level)

Excel sheet attributes to manipulate Excel output ,totals for row output ,graphs etc are demonstrated

Calculated fiels for output results (running % , calculation on results etc) are shown. It's very much required that data manipulation is possible at Load level and not just at Extract level.

Excel output and graphs are described

Excel Criteria giving information from Selection criteria used in Baan. This helps user to determine what this file mean at a later date.

Document properties of the excel output which help user trace the origins of the document are displayed

2

In query field tdjwx020.ddat as 'column' type field. This makes variable column results available to users. As the tdjwx020.ddat is date type of  field , it  can be converted to meaningful periods (months in this case)

Colorful chartiing and exception norms for baan table

1.1 Mb

In exception norms form of query data  , deviant data has to be shown in different color (red) considering left to right increasing trend. This can be specified only for 'data' type field.

In selection criteria , for from to date 1-Jul to 31-Dec , meaningful job offsets available for periodic repeating analyses. Only meaningful job offsets (as per from to selections) will be available to user for selection.

In excel attributes , different graphs selected for each row/col separately and for aggregates results also. Users can selects graphs at each row / each column level and at aggregate row /col level also.

Excel output with results along with aggregates specified and all range of graphs are also shown.

3

This avi shows the folder organization on client PC

Information regarding folder organization and file saving on client PC

5.1 Mb

C:\analysis is where analysis results are stored

Users can have analyses results stored for each user , company , analyses , date ,time etc by having folders in any order. In this case, folders are arranged in 3 levels viz analysis  code , company number and date

Further users can save analyses results files also with different names based on analysis code , data, time , user and company. Here the analysis codes are saved on the basis of time it's created.

When the user opts for getting the analysis results in htm format also in Baan then , client program also creates the htm output . This htm output can not be modified by users and can be placed in a network location for viewing by authorized user.

4

This again is an excel summary.

Different treatment for negative enum values

8.7 Mb

The transaction date is converted to quarters in query fields

The field tiitm001.reli is obtained from tiitm001 based on tdinv700.item. Extra filter condition will eliminate records in tdinv700 which do not match that criteria.

Further the quantity in tdinv700 is always positive. However for getting the net change in inventory levels it's mandatory the quantity field is treated negatively if tdinv700.kost value is production issue and sales delivery. This also is demonstrated.

Further noteworthy is that item code is 16 characters long. But due to coding convention only item codes with 6 characters are required for analysis . This is possible by specifying number of characters in selection criteria.

Further custom graphs of MS Excel are selected for output and the result is demonstrated.

5

In any data warehousing , success clearly depends on creating data marts useful to users. ERPJewels to allows data marts in Baan.

Anlysis history user wise

8.5 Mb

This data marts are created only for analyses of type other than 'Save as XLS' and only if the after analysis action is 'Save'

Data marts can be useful for backward integration and even using other tool to load the analyses results arrived at in Baan after 'Extract and Transform' in Baan using ODBC/JDBC connection to Baan.

All details like user , company , creation time ,date etc are available for each analysis run (called History or saved analysis number)

User can run the analysis afresh by clicking run button here. In this case a new history will be created with all ETL overhead on system. This is the case when user wants to get the current analysis results with current selection values.

User may also see what values were used for running the analyses using 'History' button.

User can also regenerate the old analyses results by clicking button 'Re-run'. In this case 'Extract and transform' overhead on system will be eliminated. Only load action will be done.

Transaction date converted to Quarterend then figures are calculated.

6

This is demonstration how periodic repeating analysis can be started and run automatically using Baan Job management.

Push intelligence and meaningful job offsets

11.9 Mb

First selection criteria are shown. Only if the from-to dates are meaningful then job offsets are available . If for example from-to date is beginning and end of a year quarter then available job offsets are Quarter,Month,Fortnight,Daily.

Always system date and job offset type is used for determining the from to period range. As system date can not be changed (for the purpose of this testing) , job offset value derived from system date , job offset type and from to dates at the time of creating jobs is modified through backend (e.g. 2 to 1 ). This effectively means whenever the analysis are run in job mode , systems should determine from to period dates for 1 Quarter before the current quarter.

Further analyses results are to be sorted on the results (top analyses ) and an Excel Diagram has to be prepared for data in certain column.

When the analyses are  run in job mode , Excel results are saved and closed and not open. Further the errors if any also are written to log files instead of showing it on the screen . If the user opts for creating and sending mail , then in job mode it will just be created and sent.

7

This will demonstrate how non IT user can create analysis out of a report with little knowledge about nitty gritties of Baan report

Easy analysis creator wizard for baan report

13.2 Mb

For example  a user needs report on inventory valuation report for item groups. The file shows the report without analyses attached to it .

Keeping the session open , User needs to get into easy analysis creator session. User can see the entry for session along with description. User can also add session therein manually.

Double clicking the session , program brings the user to screen whereby all reports attached to the session are displayed with the report description. Reports printed using brp functions in Baan may not come here if  pragma used statement is not written in the program script. In that case , user needs to add the report here.

User can view the layout fields for that report by double clicking the report.

Records marked with * are the ones on which analyses can be created. User can see report input fields (with description) and layout fields for particular layout even before creating analyses.

If the user wish to create analyses he/she needs to write analysis code and go to 2nd form. Fill in all basic details in the  screen and then create analysis. For save as XLS , all output  fields are added to the query fields. Thus the analyses is  created without user having to know report codes , VRC structure and output field codes.

Original Baan report and Analysis results in Excel . There is no device to be created in Baan . Original report retained as it is.

8

This file shows analysis definition for Report on inventory movement. Inventory unit (tiitm001.cuni) for items is brought from item master (tiitm001) custom grouping.

Job scheduling for baan report and activating the same.

15.5 Mb

Analyses defined on Baan report can be included with action 'Include analysis ' in screen tudll9160m000. The plain output without analysis and with analyses are compared . The results are also compared with results in MS Excel.  Criteria values show for which selection the analysis results are derived.

Excel can clearly extract the summary in Baan report and display the reports. The same graphs and  charts can also be attached to analyses based on report.

User need not create any device in Baan and original Baan report remains as it is.

The report was printed for May 2003 .In the job. A job is created on this session using Baan job management . 1 number is skipped while creating job on tdinv7410m000 (in order to accommodate parameter changing session to have priority before this session). Once job is defined on tdinv74100m000 , Job offset for this session is defined on this report (in tudll9166m000) . Zoom choices are available which brings all the related values from Baan Job management. All date fields in the session are brought by default. User can define the job offset type as monthly.

As the system date can not be changed for this testing, job offset of 2 created in the backend is changed to 1  so that report runs for June 2003 instead of May 2003

Job could be activated singly if job status is free and next execution time and date has elapsed.

When in job , the output is stored in appropriate directory and not shown  on the screen.

9

Analyses created on reports in a VRC other than report PVRC , user can execute the 'copy to current VRC' button . This saves user the time for creating analyses again. In the example the analyses was copied from B40cc4live to B40cc4cust .

Analyses scheduling for reports called from user options

22.7 Mb

Report has certain fields which user can categorize based on the coding of that particular variable. The example illustrates one such example.

The stone quality report is printed through user choices in tdjwx0233m000 with brp* functions. Baan Job management executes only run.job section or cont.process section it the absence of run.job section. To execute  user choices in job , user has to write the user choice in job correctly and in run.job section of the program script , a dll function has to be called. This makes sure that right report is printed in the job.

In Job offset the from to variable and job offset type have to be defined . Job offset value is changed in the backend as system date can not be varied.

Further when there are many analyses on the same report, user may optionally exclude certain analyses when run in job in 'Link analysis'.

10

This avi demonstrate the non-date numeric indicator time used in Baan . Baan job management can not consider this for automatically varying selections. When the job offset type is as on date/period and period type is numeric (i.e. non date) , user can also specify a year offset to indicate the year variable in the report.  As the system period can not be modified, job offset defined in the setup is modified in the backend. It can be seen that the financial period is picked up automatically when in Job.

Analyses scheduling for baan report based on non-date numeric time indicators like week , fiscal period etc

17.3 Mb

11

ERPJewels is easy to setup and use. Installation consists of 2 parts 1. Server part and 2. Client part .

EJ Setup on client

2.7 Mb

Server part involves 1. Import data dictionary, convert data dictionary , create runtime data dictionary and creating tables .This are normal baan admin procedures . These are not demonstrated in the file.

Client setup is also demonstrated.

12

This example illustrates the use of hierachies in Baan and its imapact Pivot Table.

Hierarchies in Baan

10.9 Mb