Baan-IV-Crystal-Sales-By-Sales-Person-By-Customer
11 Saturday Aug 2012
Posted Baan-IV-Cognos
in11 Saturday Aug 2012
Posted Baan-IV-Cognos
in11 Saturday Aug 2012
Posted Baan-IV-Cognos
inBusiness concept RE_RANKING for Baan IVc (202631)
INTRODUCTION:
Business Concept solutions can comprehend the following components:
Example:
– Extraction model RE_RANKING.bem
– Decision Stream component RE_RANKING_2_0_10.pkg
– SQL Script RE_RANKING_2_0_10.sql
Considerations with respect to business concept solutions:
– A business concept is infrastructure independent:
It is compatible with the infrastructure version in which it has been developed.
However, when fixes have been applied to the Infrastructure BaanComponents for generic use it is important that these solutions are being applied too, to prevent problems.
– A business concept might be dependent of another business concept.
Therefore, check the compatibility matrix of the Enterprise Analytic the business concept is used in.
– A business concept has a relation with the Business Intelligence Layer.
When fixes have been applied to the Business Intelligence Layer it is important that these solutions are being applied too, to prevent problems.
– The components of a business concept (Extraction dll Baan, extraction model, Decision Stream component, SQL script) should always be compatible with each other, else severe problems might occur.
– A business concept should be upgraded to the latest released solution for the business concept, whenever possible. This means for instance for getting from version 2.0.4 to version 2.0.7, the installation of the solutions for version 2.0.5 and version 2.0.6 in logical order (the solutions are incremental).
However there are situations in which this is not possible (yet):
re-exporting and re-loading the data warehouse are often mandatory actions to perform, when the model has been changed; these actions can require a lot of time, during which the data warehouse data cannot be accessed.
This ‘One Solution per Business Concept’ document has been developed:
– To organize all the individual Scopus solutions that have been released since the GA and/or maintenance release of the Business Concept.
– To find and retrieve solutions for a Business Concept, for any situation that is applicable.
It provides:
– An overview of the Enterprise Analytics the Business Concept is used in.
– An overview of Scopus solutions that have been released so far for the Business Concept, including a reference to the fixed component(s) of the Business Concept.
– An overview with the compatibility of the released solutions and their components.
– General installation procedures for the different components of the template.
– Solution specific installation procedures, in case the general installation procedures do not match.
BUSINESS CONCEPT:
RE_RANKING for Baan IVc
COMPATIBILITY:
CPM Infrastructure 3.0
Business Intelligence Layer 2.1
ENTERPRISEANALYTICS:
SSA EA Inventory V2.5 for Baan IVc
Overview of the Scopus solutions that have been released.
Business Concept version |
Solution number |
Solution summary |
Extraction model |
Decision Stream comp. |
SQL Script |
1.0.9 GA |
|
|
|
|
|
2.1.14 |
205141 |
For Quantity now it used 15 digits before and 4 digits after decimal. Also for amount it uses 28 digits before and 4 digits after decimal
You have to install Stock Overview Components of solution 205141 when you want to use this solution for RE-RANKING |
|
|
SQL_RE_RANKING_2.1.14_205141.ZIP |
|
|
|
|
|
|
|
|
|
|
|
|
Overview of the compatibility of this business concept in relation to other available components.
Business Concept version |
Solution number |
Infrastructure 3.0 |
Business Intelligence 2.1 |
Business Concepts/ Enterprise Analytics |
1.0.9 GA |
|
|
|
SSA EA Inventory V2.5 for Baan IVc GA |
|
|
|
|
|
INSTALLATION INSTRUCTIONS GENERAL:
Extraction model *)
– Put the RE_RANKING.bem and RE_RANKING_BaanTables.xml files in the directory where the RE_RANKING.bem is installed (i.e. C:Program FilesSSA Baan Extraction Manager 1.1TemplatesModels )
– Import the new RE_RANKING.bem model.
– Generate the model information (Exchange scheme and/or library Baan SQL queries) and the SQLTXT definition file.
Decision Stream component *)
In SQL Server back up the data warehouse and the catalog database.
In Decision Stream back up the catalog.
Put the downloaded and unzipped package in a temporary folder.
Update the catalog with the new package:
– Open the Decision Stream catalog
– Select File Menu
– Select Import package
– Select and open RE_RANKING_<version>.pkg from the temporary folder
– On the Import Package wizard screen, highlight in ‘Components in package’ window the components as indicated in the solution
– Click Add button
– De-select all the dependent components – they already exist in the catalog
– Click OK
– ‘Components to import’ panel will contain the highlighted components
– Click next
– Click Finish
SQL Script
Put thedownloaded and unzipped SQL scripts in a temporary directory.
This directory will have two folders: one for the SQL Server scripts and one for the Oracle scripts. Dependent of the kind of data warehouse database only one sets of scripts has to be executed.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script to be executed RE_RANKING_<version>.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script to be executed RE_RANKING_<version>.sql
– Select Worksheet / Execute
*) Each solution contains an additional SQL script to update the table c_exejobs. This table contains the version number of the Business Concept. The name of the script is UPDATE_VERSION_FOR_RE_RANKING.sql. Dependent of the kind of data warehouse database the script has to be executed on SQL Server or Oracle.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_RE_RANKING.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_RE_RANKING.sql
– Select Worksheet / Execute
11 Saturday Aug 2012
Posted Baan-IV-Cognos
inBusiness concept PHYSICAL_INVENTORY for Baan IVc (202623)
INTRODUCTION:
Business Concept solutions can comprehend the following components:
Example:
– Extraction dll Baan BI_B40_INPI_21
– Extraction model PHYSICAL_INVENTORY.bem
– Decision Stream component PHYSICAL_INVENTORY_2_0_10.pkg
– SQL Script PHYSICAL_INVENTORY_2_0_10.sql
Considerations with respect to business concept solutions:
– A business concept is infrastructure independent:
It is compatible with the infrastructure version in which it has been developed.
However, when fixes have been applied to the Infrastructure BaanComponents for generic use it is important that these solutions are being applied too, to prevent problems.
– A business concept might be dependent of another business concept.
Therefore, check the compatibility matrix of the Enterprise Analytic the business concept is used in.
– A business concept has a relation with the Business Intelligence Layer.
When fixes have been applied to the Business Intelligence Layer it is important that these solutions are being applied too, to prevent problems.
– The components of a business concept (Extraction dll Baan, extraction model, Decision Stream component, SQL script) should always be compatible with each other, else severe problems might occur.
– A business concept should be upgraded to the latest released solution for the business concept, whenever possible. This means for instance for getting from version 2.0.4 to version 2.0.7, the installation of the solutions for version 2.0.5 and version 2.0.6 in logical order (the solutions are incremental).
However there are situations in which this is not possible (yet):
re-exporting and re-loading the data warehouse are often mandatory actions to perform, when the model has been changed; these actions can require a lot of time, during which the data warehouse data cannot be accessed.
This ‘One Solution per Business Concept’ document has been developed:
– To organize all the individual Scopus solutions that have been released since the GA and/or maintenance release of the Business Concept.
– To find and retrieve solutions for a Business Concept, for any situation that is applicable.
It provides:
– An overview of the Enterprise Analytics the Business Concept is used in.
– An overview of Scopus solutions that have been released so far for the Business Concept, including a reference to the fixed component(s) of the Business Concept.
– An overview with the compatibility of the released solutions and their components.
– General installation procedures for the different components of the template.
– Solution specific installation procedures, in case the general installation procedures do not match.
BUSINESS CONCEPT:
PHYSICAL_INVENTORY for Baan IVc
COMPATIBILITY:
CPM Infrastructure 3.0
Business Intelligence Layer 2.1
ENTERPRISEANALYTICS:
SSA EA Inventory V2.5 for Baan IVc
Overview of the Scopus solutions that have been released.
Business Concept version |
Solution number |
Solution summary |
Extraction dll Baan |
Extraction model |
Decision Stream comp. |
SQL Script |
1.0.22 GA |
|
|
|
|
|
|
2.1.23 |
204059
204237
|
Primary Key of Physical Inventory table now has Posting Date ,Baan Source ID,Logical Company .Extraction of Manually Inserted inventory Transactions is eliminated
Oracle Update script of solution 204059 is not Proper.This is adjusted now.This solution is applicable only for Oracle Datawarehouse and only if solution 204059 is installed. |
Bidmcdll4263 |
|
PHYSICAL_INVENTORY_B_01
PHYSICAL_INVENTORY_B_02
PHYSICAL_INVENTORY_OLD_DATA_L |
PHYSICAL_INVENTORY.SQL
PHYSICAL_INVENTORY_2.1.27_205141.SQL
|
2.1.27 |
205141 |
The Quantity is set to 15 digits before and 4 digits after Decimal. For Amounts it is set to 28 digits before and 4 digits after decimal.
Wrong Updation of Count Date when the Data is extracted again.
To make Datawarehouse Consistent with Baan5.0c , 2 New columns are introduced in table |
|
PHYSICAL_INVENTORY.bem |
PHYSICAL_INVENTORY_B_02
Tables PHYSICAL_INVENTORY_FEX, PHYSICAL_INVENTORY
|
PHYSICAL_INVENTORY.SQL
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Overview of the compatibility of this business concept in relation to other available components.
Business Concept version |
Solution number |
Infrastructure 3.0 |
Business Intelligence 2.1 |
Business Concepts/ Enterprise Analytics |
1.0.22 GA |
|
|
|
SSA EA Inventory V2.5 for Baan IVc GA |
|
|
|
|
|
INSTALLATION INSTRUCTIONS GENERAL:
Extraction dll Baan *)
– Unzip the PMC dump
– Transfer the dump to the Baan server in binary mode
– Install the solution using PMC
Extraction model *)
– Put the PHYSICAL_INVENTORY.bem in the directory where the PHYSICAL_INVENTORY.bem is installed (i.e. C:Program FilesSSA Baan Extraction Manager 1.1TemplatesModels )
– Import the new PHYSICAL_INVENTORY.bem model.
– Generate the model information (Exchange scheme and/or library Baan SQL queries) and the SQLTXT definition file.
Decision Stream component *)
In SQL Server back up the data warehouse and the catalog database.
In Decision Stream back up the catalog.
Put the downloaded and unzipped package in a temporary folder.
Update the catalog with the new package:
– Open the Decision Stream catalog
– Select File Menu
– Select Import package
– Select and open PHYSICAL_INVENTORY_<version>.pkg from the temporary folder
– On the Import Package wizard screen, highlight in ‘Components in package’ window the components as indicated in the solution
– Click Add button
– De-select all the dependent components – they already exist in the catalog
– Click OK
– ‘Components to import’ panel will contain the highlighted components
– Click next
– Click Finish
SQL Script
Put thedownloaded and unzipped SQL scripts in a temporary directory.
This directory will have two folders: one for the SQL Server scripts and one for the Oracle scripts. Dependent of the kind of data warehouse database only one sets of scripts has to be executed.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script to be executed PHYSICAL_INVENTORY_<version>.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script to be executed PHYSICAL_INVENTORY_<version>.sql
– Select Worksheet / Execute
*) Each solution contains an additional SQL script to update the table c_exejobs. This table contains the version number of the Business Concept. The name of the script is UPDATE_VERSION_FOR_PHYSICAL_INVENTORY.sql. Dependent of the kind of data warehouse database the script has to be executed on SQL Server or Oracle.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_PHYSICAL_INVENTORY.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_PHYSICAL_INVENTORY.sql
– Select Worksheet / Execute
11 Saturday Aug 2012
Posted Baan-IV-Cognos
inINTRODUCTION:
An Enterprise Analytic consists of several Business Concepts. Solutions are delivered on business concept level.
This ‘One Solution per Enterprise Analytic’ document has been developed to list all the appropriate individual Scopus solutions that have been released since the GA and/or maintenance release of the Enterprise Analytic.
An Enterprise Analytic is infrastructure and Business Intelligence layer dependent. Therefore it is important that solutions for these components will be applied too, to prevent problems. The components should always be compatible with each other, else severe problems might occur.
It is recommended always to upgrade to the latest versions of all business concepts and the other mentioned related components. However there are situations in which this in not possible (yet):
Re-exporting and re-loading the data warehouse are often mandatory actions to perform, when the model has been changed; these actions can require a lot of time, during which the data warehouse data cannot be accessed.
ENTERPRISEANALYTIC:
SSA EA Procurement V2.5 for Baan IVc
COMPATIBILITY:
CPM Infrastructure 3.0
Business Intelligence Layer 2.0
BUSINESS CONCEPTS:
ALL_TIME
BUSINESS_DIMENSIONS
BUSINESS_UNIT
CONTRACT_ACTIVITY
EMPLOYEE
FINANCIAL_CURRENCY
MATERIAL
OPERATIONAL_FRAMEWORK
PROCUREMENT_ACTIVITY_SUMMARY
PROCUREMENT_DOCUMENT_CLASS
PROCUREMENT_STATUS
PURCHASE_ACTIVITY
QUOTATION_ACTIVITY
UNIT_OF_MEASURE
Overview of the latest available versions of related components since the GA deliverance of the analytic. No maintenance releases have been delivered yet.
Component Name |
Latest available Version |
Business Concepts |
|
ALL_TIME |
2.0.23 |
BUSINESS_DIMENSIONS |
2.0.6 |
BUSINESS_UNIT |
2.0.7 |
CONTRACT_ACTIVITY |
1.0.70 (GA) |
EMPLOYEE |
2.0.7 |
FINANCIAL_CURRENCY |
2.0.6 |
MATERIAL |
2.0.6 |
OPERATIONAL_FRAMEWORK |
2.0.25 |
PROCUREMENT_ACTIVITY_SUMMARY |
1.0.45 (GA) |
PROCUREMENT_DOCUMENT_CLASS |
1.0.28 (GA) |
PROCUREMENT_STATUS |
1.0.24 (GA) |
PURCHASE_ACTIVITY |
1.0.70 (GA) |
QUOTATION_ACTIVITY |
1.0.64 (GA) |
UNIT_OF_MEASURE |
2.0.5 |
Other |
|
CPM Infrastructure |
3.0 (GA) |
Business Intelligence Layer |
2.1.1 |
11 Saturday Aug 2012
Posted Baan-IV-Cognos
inINTRODUCTION:
An Enterprise Analytic consists of several Business Concepts. Solutions are delivered on business concept level.
This ‘One Solution per Enterprise Analytic‘ document has been developed to list all the appropriate individual Scopus solutions that have been released since the GA and/or maintenance release of the Enterprise Analytic.
An Enterprise Analytic is infrastructure and Business Intelligence layer dependent. Therefore it is important that solutions for these components will be applied too, to prevent problems. The components should always be compatible with each other, else severe problems might occur.
It is recommended always to upgrade to the latest versions of all business concepts and the other mentioned related components. However there are situations in which this in not possible (yet):
Re-exporting and re-loading the data warehouse are often mandatory actions to perform, when the model has been changed; these actions can require a lot of time, during which the data warehouse data cannot be accessed.
ENTERPRISEANALYTIC:
SSA EA Sales V2.5.1 for Baan IVc
COMPATIBILITY:
CPM Infrastructure 3.0
Business Intelligence Layer 2.1.1/2.2
BUSINESS CONCEPTS:
ALL_TIME
CUSTOMER
EMPLOYEE
FINANCIAL_CURRENCY
MATERIAL
OPERATIONAL_FRAMEWORK
ORGANIZATION
SALES_BILLING
SALES_DISTRIBUTION
SALES_DOCUMENT_CLASS
SALES_HISTORY
SALES_ORDER
SALES_STATUS
SHIPPING_POINT
SHIPPING_TO_POINT
UNIT_OF_MEASURE
Overview of the latest available versions of related components since the GA deliverance of the analytic. No maintenance releases have been delivered yet.
Component Name |
2.5.2 |
2.5.1 |
|
Business Concepts |
|
|
|
ALL_TIME |
|
|
2.0.23 |
CUSTOMER |
|
|
2.0.13 |
EMPLOYEE |
|
|
2.0.7 |
FINANCIAL_CURRENCY |
|
|
2.0.6 |
MATERIAL |
|
|
2.0.6 |
OPERATIONAL_FRAMEWORK |
|
|
2.0.25 |
ORGANIZATION |
|
|
2.0.10 |
SALES_BILLING |
|
|
2.0.10 |
SALES_DISTRIBUTION |
|
|
2.0.20 |
SALES_DOCUMENT_CLASS |
|
|
2.0.2 (GA) |
SALES_HISTORY |
|
|
2.0.1 |
SALES_ORDER |
|
|
2.0.15 |
SALES_STATUS |
|
|
2.0.1 (GA) |
SHIPPING_POINT |
|
|
2.0.2 (GA) |
SHIPPING_TO_POINT |
|
|
2.0.7 (GA) |
UNIT_OF_MEASURE |
|
|
2.0.5 |
Other |
|
|
|
CPM Infrastructure |
|
|
3.0 (GA) |
Business Intelligence Layer |
|
|
2.1.1 |
11 Saturday Aug 2012
Posted Baan-IV-Cognos
inBusiness concept ORGANIZATION for Baan IVc (202415)
INTRODUCTION:
Business Concept solutions can comprehend the following components:
Example:
– Extraction model ORGANIZATION.bem
– Decision Stream component ORGANIZATION _2_0_10.pkg
– SQL Script ORGANIZATION _2_0_10.sql
Considerations with respect to business concept solutions:
– A business concept is infrastructure independent:
It is compatible with the infrastructure version in which it has been developed.
However, when fixes have been applied to the Infrastructure BaanComponents for generic use it is important that these solutions are being applied too, to prevent problems.
– A business concept might be dependent of another business concept.
Therefore, check the compatibility matrix of the Enterprise Analytic the business concept is used in.
– A business concept has a relation with the Business Intelligence Layer.
When fixes have been applied to the Business Intelligence Layer it is important that these solutions are being applied too, to prevent problems.
– The components of a business concept (Extraction dll Baan, extraction model, Decision Stream component, SQL script) should always be compatible with each other, else severe problems might occur.
– A business concept should be upgraded to the latest released solution for the business concept, whenever possible. This means for instance for getting from version 2.0.4 to version 2.0.7, the installation of the solutions for version 2.0.5 and version 2.0.6 in logical order (the solutions are incremental).
However there are situations in which this is not possible (yet):
re-exporting and re-loading the data warehouse are often mandatory actions to perform, when the model has been changed; these actions can require a lot of time, during which the data warehouse data cannot be accessed.
This ‘One Solution per Business Concept’ document has been developed:
– To organize all the individual Scopus solutions that have been released since the GA and/or maintenance release of the Business Concept.
– To find and retrieve solutions for a Business Concept, for any situation that is applicable.
It provides:
– An overview of the Enterprise Analytics the Business Concept is used in.
– An overview of Scopus solutions that have been released so far for the Business Concept, including a reference to the fixed component(s) of the Business Concept.
– An overview with the compatibility of the released solutions and their components.
– General installation procedures for the different components of the template.
– Solution specific installation procedures, in case the general installation procedures do not match.
BUSINESS CONCEPT:
ORGANIZATION for Baan IVc
COMPATIBILITY:
CPM Infrastructure 3.0
Business Intelligence Layer 2.0
Business Intelligence Layer 2.1
ENTERPRISEANALYTICS:
SSA EA Sales V2.5 for Baan IVc
SSA EA Sales V2.5.1 for Baan IVc
SSA EA Accounts Receivable V2.5 for Baan IVc
SSA EA Accounts Receivable V2.5.1 for Baan IVc
SSA EA Accounts Payable V2.5 for Baan IVc
Overview of the Scopus solutions that have been released.
Business Concept version |
Solution number |
Solution summary |
Extraction model |
Decision Stream comp. |
SQL Script |
2.0.7 GA |
|
|
|
|
|
2.0.8 GA |
203805 |
Modified business concepts in maintenance release are not available in other analytics |
|
ORGANIZATION_B_01 ORGANIZATION_B_02 |
ORGANIZATION_2.0.8_203805.sql |
2.0.10 GA |
204117 |
Indexes set for AR to improve performance. |
|
|
ORGANIZATION.SQL |
Overview of the compatibility of this business concept in relation to other available components.
Business Concept version |
Solution number |
Infrastructure 3.0 |
Business Intelligence 2.0/2.1 |
Business Concepts/ Enterprise Analytics |
2.0.7 GA |
|
|
2.0 2.0
2.1 |
SSA EA Accounts Payable V2.5 for Baan IVcGA |
2.0.8 GA |
|
|
2.0 |
SSA EA Sales V2.5.1 for Baan IVc GA |
2.0.10 GA |
|
|
2.1 |
SSA EA Accounts Receivable V2.5.1 for Baan IVc GA |
INSTALLATION INSTRUCTIONS GENERAL:
Extraction model *)
Model:
– Put the ORGANIZATION.bem and ORGANIZATION _BaanTables.xml files in the directory where the ORGANIZATION.bem is installed (i.e. C:Program FilesSSA Baan Extraction Manager 1.1TemplatesModels )
– Import the new ORGANIZATION.bem model.
– Generate the model information (Exchange scheme and/or library Baan SQL queries) and the SQLTXT definition file.
Decision Stream component *)
In SQL Server back up the data warehouse and the catalog database.
In Decision Stream back up the catalog.
Put the downloaded and unzipped package in a temporary folder.
Update the catalog with the new package:
– Open the Decision Stream catalog
– Select File Menu
– Select Import package
– Select and open ORGANIZATION _<version>.pkg from the temporary folder
– On the Import Package wizard screen, highlight in ‘Components in package’ window the components as indicated in the solution
– Click Add button
– De-select all the dependent components – they already exist in the catalog
– Click OK
– ‘Components to import’ panel will contain the highlighted components
– Click next
– Click Finish
SQL Script
Put thedownloaded and unzipped SQL scripts in a temporary directory.
This directory will have two folders: one for the SQL Server scripts and one for the Oracle scripts. Dependent of the kind of data warehouse database only one sets of scripts has to be executed.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script to be executed ORGANIZATION _<version>.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script to be executed ORGANIZATION _<version>.sql
– Select Worksheet / Execute
*) Each solution contains an additional SQL script to update the table c_exejobs. This table contains the version number of the Business Concept. The name of the script is UPDATE_VERSION_FOR_ ORGANIZATION.sql. Dependent of the kind of data warehouse database the script has to be executed on SQL Server or Oracle.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_ ORGANIZATION.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_ ORGANIZATION.sql
– Select Worksheet / Execute
11 Saturday Aug 2012
Posted Baan-IV-Cognos
inBusiness Concept SALES_BILLING for Baan IVc (202416)
INTRODUCTION:
Business Concept solutions can comprehend the following components:
Example:
– Decision Stream component SALES_BILLING_2_0_10.pkg
– SQL Script SALES_BILLING_2_0_10.sql
Considerations with respect to business concept solutions:
– A business concept is infrastructure independent:
It is compatible with the infrastructure version in which it has been developed.
However, when fixes have been applied to the Infrastructure BaanComponents for generic use it is important that these solutions are being applied too, to prevent problems.
– A business concept might be dependent of another business concept.
Therefore, check the compatibility matrix of the Enterprise Analytic the business concept is used in.
– A business concept has a relation with the Business Intelligence Layer.
When fixes have been applied to the Business Intelligence Layer it is important that these solutions are being applied too, to prevent problems.
– The components of a business concept (Extraction dll Baan, extraction model, Decision Stream component, SQL script) should always be compatible with each other, else severe problems might occur.
– A business concept should be upgraded to the latest released solution for the business concept, whenever possible. This means for instance for getting from version 2.0.4 to version 2.0.7, the installation of the solutions for version 2.0.5 and version 2.0.6 in logical order (the solutions are incremental).
However there are situations in which this is not possible (yet):
re-exporting and re-loading the data warehouse are often mandatory actions to perform, when the model has been changed; these actions can require a lot of time, during which the data warehouse data cannot be accessed.
This ‘One Solution per Business Concept’ document has been developed:
– To organize all the individual Scopus solutions that have been released since the GA and/or maintenance release of the Business Concept.
– To find and retrieve solutions for a Business Concept, for any situation that is applicable.
It provides:
– An overview of the Enterprise Analytics the Business Concept is used in.
– An overview of Scopus solutions that have been released so far for the Business Concept, including a reference to the fixed component(s) of the Business Concept.
– An overview with the compatibility of the released solutions and their components.
– General installation procedures for the different components of the template.
– Solution specific installation procedures, in case the general installation procedures do not match.
BUSINESS CONCEPT:
SALES_BILLING for Baan IVc
COMPATIBILITY:
CPM Infrastructure 3.0
Business Intelligence Layer 2.0
Business Intelligence Layer 2.1
ENTERPRISEANALYTICS:
SSA EA Sales V2.5 for Baan IVc
SSA EA Sales V2.5.1 for Baan IVc
Overview of the Scopus solutions that have been released.
Business Concept version |
Solution number |
Solution summary |
Decision Stream comp. |
SQL Script |
2.0.7 GA |
|
|
|
|
2.0.8 |
202715 |
Index missing on table BILLING. |
– |
x |
2.0.10 |
203656 |
Standard items on a project are rejected. |
SALES_BILLING_B_01 |
– |
2.0.11 |
205879 |
Altered the precision and scale values |
|
SALES_BILLING.SQL |
Overview of the compatibility of this business concept in relation to other available components.
Business Concept version |
Solution number |
Infrastructure 3.0 |
Business Intelligence 2.0/2.1 |
Business Concepts/ Enterprise Analytics |
2.0.7 GA |
|
|
2.0 2.0 |
SSA EA Sales V2.5.1 for Baan IVc GA |
|
|
|
|
|
INSTALLATION INSTRUCTIONS GENERAL:
Decision Stream component *)
In SQL Server back up the data warehouse and the catalog database.
In Decision Stream back up the catalog.
Put the downloaded and unzipped package in a temporary folder.
Update the catalog with the new package:
– Open the Decision Stream catalog
– Select File Menu
– Select Import package
– Select and open SALES_BILLING_<version>.pkg from the temporary folder
– On the Import Package wizard screen, highlight in ‘Components in package’ window the components as indicated in the solution
– Click Add button
– De-select all the dependent components – they already exist in the catalog
– Click OK
– ‘Components to import’ panel will contain the highlighted components
– Click next
– Click Finish
SQL Script
Put thedownloaded and unzipped SQL scripts in a temporary directory.
This directory will have two folders: one for the SQL Server scripts and one for the Oracle scripts. Dependent of the kind of data warehouse database only one sets of scripts has to be executed.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script to be executed SALES_BILLING_<version>.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script to be executed SALES_BILLING_<version>.sql
– Select Worksheet / Execute
*) Each solution contains an additional SQL script to update the table c_exejobs. This table contains the version number of the Business Concept. The name of the script is UPDATE_VERSION_FOR_SALES_BILLING.sql. Dependent of the kind of data warehouse database the script has to be executed on SQL Server or Oracle.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_SALES_BILLING.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_SALES_BILLING.sql
– Select Worksheet / Execute
11 Saturday Aug 2012
Posted Baan-IV-Cognos
inBusiness concept OPERATIONAL_FRAMEWORK for Baan IVc (202414)
INTRODUCTION:
Business Concept solutions can comprehend the following components:
Example:
– Decision Stream component OPERATIONAL_FRAMEWORK_2_0_10.pkg
– SQL Script OPERATIONAL_FRAMEWORK_2_0_10.sql
Considerations with respect to business concept solutions:
– A business concept is infrastructure independent:
It is compatible with the infrastructure version in which it has been developed.
However, when fixes have been applied to the Infrastructure BaanComponents for generic use it is important that these solutions are being applied too, to prevent problems.
– A business concept might be dependent of another business concept.
Therefore, check the compatibility matrix of the Enterprise Analytic the business concept is used in.
– A business concept has a relation with the Business Intelligence Layer.
When fixes have been applied to the Business Intelligence Layer it is important that these solutions are being applied too, to prevent problems.
– The components of a business concept (Extraction dll Baan, extraction model, Decision Stream component, SQL script) should always be compatible with each other, else severe problems might occur.
– A business concept should be upgraded to the latest released solution for the business concept, whenever possible. This means for instance for getting from version 2.0.4 to version 2.0.7, the installation of the solutions for version 2.0.5 and version 2.0.6 in logical order (the solutions are incremental).
However there are situations in which this is not possible (yet):
re-exporting and re-loading the data warehouse are often mandatory actions to perform, when the model has been changed; these actions can require a lot of time, during which the data warehouse data cannot be accessed.
This ‘One Solution per Business Concept’ document has been developed:
– To organize all the individual Scopus solutions that have been released since the GA and/or maintenance release of the Business Concept.
– To find and retrieve solutions for a Business Concept, for any situation that is applicable.
It provides:
– An overview of the Enterprise Analytics the Business Concept is used in.
– An overview of Scopus solutions that have been released so far for the Business Concept, including a reference to the fixed component(s) of the Business Concept.
– An overview with the compatibility of the released solutions and their components.
– General installation procedures for the different components of the template.
– Solution specific installation procedures, in case the general installation procedures do not match.
BUSINESS CONCEPT:
OPERATIONAL_FRAMEWORK for Baan IVc
COMPATIBILITY:
CPM Infrastructure 3.0
Business Intelligence Layer 2.0
Business Intelligence Layer 2.1
ENTERPRISEANALYTICS:
SSA EA Sales V2.5 for Baan IVc
SSA EA Sales V2.5.1 for Baan IVc
SSA EA General Ledger V2.5 for Baan IVc
SSA EA General Ledger V2.5.1 for Baan IVc
SSA EA Accounts Receivable V2.5 for Baan IVc
SSA EA Procurement V2.5 for Baan IVc
SSA EA Inventory V2.5 for Baan IVc
SSA EA Accounts Payable V2.5 for Baan IVc
Overview of the Scopus solutions that have been released.
Business Concept version |
Solution number |
Solution summary |
Decision Stream comp. |
SQL Script |
2.0.21 GA |
|
|
|
|
2.0.23 GA |
|
|
|
|
2.0.24 GA |
203805 |
Modified business concepts in maintenance release are not available in other analytics |
|
OPERATIONAL_FRAMEWORK_2.0.24_203805.sql |
2.0.25 |
206058 |
Jobs with extraction mode ‘E’ check unnecessarily for dependencies. |
SYS_CHECK_JOB_DEPENDENCIES_F SYS_CHECK_JOB_RUN_STATUS_F |
|
2.0.34 |
224379 |
Enabling SFTP for copying extracted txt files from Baan server to ETL server (SSH2 connection). When using the SFTP functionality, an updated version of the Operational Framework in the Decisionstream catalog must be installed. |
SYS_BAAN_COPY_FILES_F |
|
Overview of the compatibility of this business concept in relation to other available components.
Business Concept version |
Solution number |
Infrastructure 3.0 |
Business Intelligence 2.0/2.1 |
Business Concepts/ Enterprise Analytics |
2.0.21 GA |
|
|
2.0 2.0 |
|
2.0.23 GA |
|
|
2.0 |
SSA EA Accounts Receivable V2.5 for Baan IVc GA |
2.0.24 GA |
|
|
2.1
2.1
2.1
2.0 2.0 |
SSA EA Procurement V2.5 for Baan IVc GA SSA EA Inventory V2.5 for Baan IVc GA SSA EA Accounts Payable V2.5 for Baan IVc GA SSA EA Sales V2.5.1 for Baan IVc GA SSA EA General Ledger V2.5.1 for Baan IVc GA |
|
|
|
|
|
INSTALLATION INSTRUCTIONS GENERAL:
Decision Stream component *)
In SQL Server back up the data warehouse and the catalog database.
In Decision Stream back up the catalog.
Put the downloaded and unzipped package in a temporary folder.
Update the catalog with the new package:
– Open the Decision Stream catalog
– Select File Menu
– Select Import package
– Select and open OPERATIONAL_FRAMEWORK_<version>.pkg from the temporary folder
– On the Import Package wizard screen, highlight in ‘Components in package’ window the components as indicated in the solution
– Click Add button
– De-select all the dependent components – they already exist in the catalog
– Click OK
– ‘Components to import’ panel will contain the highlighted components
– Click next
– Click Finish
SQL Script
Put thedownloaded and unzipped SQL scripts in a temporary directory.
This directory will have two folders: one for the SQL Server scripts and one for the Oracle scripts. Dependent of the kind of data warehouse database only one sets of scripts has to be executed.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script to be executed OPERATIONAL_FRAMEWORK_<version>.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script to be executed OPERATIONAL_FRAMEWORK_<version>.sql
– Select Worksheet / Execute
*) Each solution contains an additional SQL script to update the table c_exejobs. This table contains the version number of the Business Concept. The name of the script is UPDATE_VERSION_FOR_OPERATIONAL_FRAMEWORK.sql. Dependent of the kind of data warehouse database the script has to be executed on SQL Server or Oracle.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_OPERATIONAL_FRAMEWORK.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_OPERATIONAL_FRAMEWORK.sql
– Select Worksheet / Execute
11 Saturday Aug 2012
Posted Baan-IV-Cognos
inBusiness concept SALES_DISTRIBUTIONfor Baan IVc (202419)
INTRODUCTION:
Business Concept solutions can comprehend the following components:
Example:
– Decision Stream component SALES_DISTRIBUTION_2_0_10.pkg
– SQL Script SALES_DISTRIBUTION_2_0_10.sql
Considerations with respect to business concept solutions:
– A business concept is infrastructure independent:
It is compatible with the infrastructure version in which it has been developed.
However, when fixes have been applied to the Infrastructure BaanComponents for generic use it is important that these solutions are being applied too, to prevent problems.
– A business concept might be dependent of another business concept.
Therefore, check the compatibility matrix of the Enterprise Analytic the business concept is used in.
– A business concept has a relation with the Business Intelligence Layer.
When fixes have been applied to the Business Intelligence Layer it is important that these solutions are being applied too, to prevent problems.
– The components of a business concept (Extraction dll Baan, extraction model, Decision Stream component, SQL script) should always be compatible with each other, else severe problems might occur.
– A business concept should be upgraded to the latest released solution for the business concept, whenever possible. This means for instance for getting from version 2.0.4 to version 2.0.7, the installation of the solutions for version 2.0.5 and version 2.0.6 in logical order (the solutions are incremental).
However there are situations in which this is not possible (yet):
re-exporting and re-loading the data warehouse are often mandatory actions to perform, when the model has been changed; these actions can require a lot of time, during which the data warehouse data cannot be accessed.
This ‘One Solution per Business Concept’ document has been developed:
– To organize all the individual Scopus solutions that have been released since the GA and/or maintenance release of the Business Concept.
– To find and retrieve solutions for a Business Concept, for any situation that is applicable.
It provides:
– An overview of the Enterprise Analytics the Business Concept is used in.
– An overview of Scopus solutions that have been released so far for the Business Concept, including a reference to the fixed component(s) of the Business Concept.
– An overview with the compatibility of the released solutions and their components.
– General installation procedures for the different components of the template.
– Solution specific installation procedures, in case the general installation procedures do not match.
BUSINESS CONCEPT:
SALES_DISTRIBUTION for Baan IVc
COMPATIBILITY:
CPM Infrastructure 3.0
Business Intelligence Layer 2.0
Business Intelligence Layer 2.1
ENTERPRISEANALYTICS:
SSA EA Sales V2.5 for Baan IVc
SSA EA Sales V2.5.1 for Baan IVc
Overview of the Scopus solutions that have been released.
Business Concept version |
Solution number |
Solution summary |
Decision Stream comp. |
SQL Script |
2.0.16 GA |
|
|
|
|
2.0.17 GA |
|
|
|
|
2.0.18 |
202753 |
Index missing on table SALES_DISTRIBUTION |
– |
X |
2.0.20 |
203656 |
Standard items on a project are rejected. |
SALES_DISTRIBUTION_B_05 |
– |
2.0.21 |
205879 |
Altered the precision and scale values |
|
SALES_DISTRIBUTION.SQL |
Overview of the compatibility of this business concept in relation to other available components.
Business Concept version |
Solution number |
Infrastructure 3.0 |
Business Intelligence 2.0/2.1 |
Business Concepts/ Enterprise Analytics |
2.0.16 GA |
|
|
2.0 |
|
2.0.17 GA |
|
|
2.0 |
SSA EA Sales V2.5.1 for Baan IVc GA |
INSTALLATION INSTRUCTIONS GENERAL:
Decision Stream component *)
In SQL Server back up the data warehouse and the catalog database.
In Decision Stream back up the catalog.
Put the downloaded and unzipped package in a temporary folder.
Update the catalog with the new package:
– Open the Decision Stream catalog
– Select File Menu
– Select Import package
– Select and open SALES_DISTRIBUTION_<version>.pkg from the temporary folder
– On the Import Package wizard screen, highlight in ‘Components in package’ window the components as indicated in the solution
– Click Add button
– De-select all the dependent components – they already exist in the catalog
– Click OK
– ‘Components to import’ panel will contain the highlighted components
– Click next
– Click Finish
SQL Script
Put thedownloaded and unzipped SQL scripts in a temporary directory.
This directory will have two folders: one for the SQL Server scripts and one for the Oracle scripts. Dependent of the kind of data warehouse database only one sets of scripts has to be executed.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script to be executed SALES_DISTRIBUTION_<version>.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script to be executed SALES_DISTRIBUTION_<version>.sql
– Select Worksheet / Execute
*) Each solution contains an additional SQL script to update the table c_exejobs. This table contains the version number of the Business Concept. The name of the script is UPDATE_VERSION_FOR_ SALES_DISTRIBUTION.sql. Dependent of the kind of data warehouse database the script has to be executed on SQL Server or Oracle.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_ SALES_DISTRIBUTION.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_ SALES_DISTRIBUTION.sql
– Select Worksheet / Execute
11 Saturday Aug 2012
Posted Baan-IV-Cognos
inBusiness concept MATERIAL_STORAGE for Baan IVc (202621)
INTRODUCTION:
Business Concept solutions can comprehend the following components:
Example:
– Extraction model MATERIAL_STORAGE.bem
– Decision Stream component MATERIAL_STORAGE_2_0_10.pkg
– SQL Script MATERIAL_STORAGE_2_0_10.sql
Considerations with respect to business concept solutions:
– A business concept is infrastructure independent:
It is compatible with the infrastructure version in which it has been developed.
However, when fixes have been applied to the Infrastructure BaanComponents for generic use it is important that these solutions are being applied too, to prevent problems.
– A business concept might be dependent of another business concept.
Therefore, check the compatibility matrix of the Enterprise Analytic the business concept is used in.
– A business concept has a relation with the Business Intelligence Layer.
When fixes have been applied to the Business Intelligence Layer it is important that these solutions are being applied too, to prevent problems.
– The components of a business concept (Extraction dll Baan, extraction model, Decision Stream component, SQL script) should always be compatible with each other, else severe problems might occur.
– A business concept should be upgraded to the latest released solution for the business concept, whenever possible. This means for instance for getting from version 2.0.4 to version 2.0.7, the installation of the solutions for version 2.0.5 and version 2.0.6 in logical order (the solutions are incremental).
However there are situations in which this is not possible (yet):
re-exporting and re-loading the data warehouse are often mandatory actions to perform, when the model has been changed; these actions can require a lot of time, during which the data warehouse data cannot be accessed.
This ‘One Solution per Business Concept’ document has been developed:
– To organize all the individual Scopus solutions that have been released since the GA and/or maintenance release of the Business Concept.
– To find and retrieve solutions for a Business Concept, for any situation that is applicable.
It provides:
– An overview of the Enterprise Analytics the Business Concept is used in.
– An overview of Scopus solutions that have been released so far for the Business Concept, including a reference to the fixed component(s) of the Business Concept.
– An overview with the compatibility of the released solutions and their components.
– General installation procedures for the different components of the template.
– Solution specific installation procedures, in case the general installation procedures do not match.
BUSINESS CONCEPT:
MATERIAL_STORAGE for Baan IVc
COMPATIBILITY:
CPM Infrastructure 3.0
Business Intelligence Layer 2.1
ENTERPRISEANALYTICS:
SSA EA Inventory V2.5 for Baan IVc
Overview of the Scopus solutions that have been released.
Business Concept version |
Solution number |
Solution summary |
Extraction model |
Decision Stream comp. |
SQL Script |
1.0.17 GA |
|
|
|
|
|
2.1.18 |
205141 |
Data Type of Replenishment Lead time is changed to Numeric(10,2) |
|
|
MATERIAL_STORAGE_2.1.18_205141.sql |
|
|
|
|
|
|
Overview of the compatibility of this business concept in relation to other available components.
Business Concept version |
Solution number |
Infrastructure 3.0 |
Business Intelligence 2.1 |
Business Concepts/ Enterprise Analytics |
1.0.17 GA |
|
|
|
SSA EA Inventory V2.5 for Baan IVc GA |
|
|
|
|
|
INSTALLATION INSTRUCTIONS GENERAL:
Extraction model *)
– Put the MATERIAL_STORAGE.bem and MATERIAL_STORAGE_BaanTables.xml files in the directory where the MATERIAL_STORAGE.bem is installed (i.e. C:Program FilesSSA Baan Extraction Manager 1.1TemplatesModels )
– Import the new MATERIAL_STORAGE.bem model.
– Generate the model information (Exchange scheme and/or library Baan SQL queries) and the SQLTXT definition file.
Decision Stream component *)
In SQL Server back up the data warehouse and the catalog database.
In Decision Stream back up the catalog.
Put the downloaded and unzipped package in a temporary folder.
Update the catalog with the new package:
– Open the Decision Stream catalog
– Select File Menu
– Select Import package
– Select and open MATERIAL_STORAGE_<version>.pkg from the temporary folder
– On the Import Package wizard screen, highlight in ‘Components in package’ window the components as indicated in the solution
– Click Add button
– De-select all the dependent components – they already exist in the catalog
– Click OK
– ‘Components to import’ panel will contain the highlighted components
– Click next
– Click Finish
SQL Script
Put thedownloaded and unzipped SQL scripts in a temporary directory.
This directory will have two folders: one for the SQL Server scripts and one for the Oracle scripts. Dependent of the kind of data warehouse database only one sets of scripts has to be executed.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script to be executed MATERIAL_STORAGE_<version>.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script to be executed MATERIAL_STORAGE_<version>.sql
– Select Worksheet / Execute
*) Each solution contains an additional SQL script to update the table c_exejobs. This table contains the version number of the Business Concept. The name of the script is UPDATE_VERSION_FOR_MATERIAL_STORAGE.sql. Dependent of the kind of data warehouse database the script has to be executed on SQL Server or Oracle.
On SQL Server:
– Execute SQL Query Analyzer (tool of Microsoft SQL Server)
– Connect to the data warehouse server
– Select the data warehouse database
– Select File / Open and browse to the Mssql subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_MATERIAL_STORAGE.sql
– Select Query / Execute
On Oracle:
– Execute SQLPlus Worksheet (tool of Oracle)
– Connect to the data warehouse database
– Select File / Open and browse to the Oracle subfolder in the temporary folder
– Select the SQL script UPDATE_VERSION_FOR_MATERIAL_STORAGE.sql
– Select Worksheet / Execute