Technical data

ManualsBrandsSimplicity ManualsDo-It-Yourself tools4564

271

272

273

274

275

276

277

278

279

280

Converting BAM 8.8 Models to Analytic Models Chapter 16

BAM 8.8 Part Name Attribute Attribute Change Upon Conversion

Non alphanumeric characters Non alphanumeric characters are rem oved from the part name. For

example: Cost$ of delivery converts t o COST_OF_DELIVERY.

Part names with m ore than 27 characters Characters exceeding the 27 character limit are truncated. For

example: Moving STD by Country and Group converts to

MOVING_STD_BY_COUNTRY_AND_G

Duplicate part names Numeric values are appended to duplicate part names. For example,

if the BAM 8.8 model co ntains the Actual Sales and Actual_Sales

part names, PTAEA CECONV creates two n ew part names:

ACTUAL_SALES and ACTUAL_SALES1.

Note. Converted names of expression modifiers include the prefix EXP_.

Additionally, for each part that is converted, the original part name is converted into the new part’s description.

Note. Filter user functions that are r eferenced by dimensions that exist in table views are converted to user

functions. The user function names include the prefix DR_ plus the converted dimension name.

Code in Data Cube Rules, User Func tions, and Expression Modifiers

PTAEACECONV uses the following order of execution when converting code in data cube rules, user

functions, and expression modifiers:

1. Replace all references to part names with resolved part names.

During conversion, PTAEACECONV searches through the code in data cube rules, user functions, and

expression modifiers for all part names and replaces these part names with new, converted part names.

For example, the EmployeeNetMonthlyIncome user function contains the following code:

Monthly Salary - Monthly Deductions

PTAEACECONV changes the user function’s code to:

MONTHLY_SALARY - MONTHLY_DEDUCTION

2. Replace all references to option lists with a literal string.

Because analytic models do not support option lists, PTAEACECONV converts references to option

lists within the code of data cube rules, user functions, and expression modifiers. For example, the

RevenueMethod option list exists in the following user function code:

&RevenueMethod := GetRevenueMethod( );

CASE(

&RevenueMethod = \Revenue Method\Data Entry\ :

Do_Something;

&RevenueMethod = \Revenue Method\Repeat Value\ :

Do_Something_ELSE;

)

The PTAEACECONV Application Engine program converts the user function’s code to:

&RevenueMethod := GetRevenueMethod( );