Estimation Catalog

Transaction /DBME/WMA_MENU_USER

All new Catalogs should be maintained in the new Estimation Catalog. 

Create and Maintain Job Catalog

The new Job Catalog has been created and added to the main 'VSS master data' folder: 

Estimation

 The layout of Estimation catalog node:

Estimation catalog node

Usage

Maintain your job- / estimation catalogue. With the transaction “Maintain Catalogs” the new estimation catalogs are maintained. To migrate the job catalog from release 18.1 to the estimation catalog release 18.2 see the RENO (Release notes) document.

The first screen will be the following calling the transaction “Maintain Catalogs”:

Create Estimation Catalog

In the description a text must be maintained.

In the filed Usage the following usage should be used: /DBME/WMA_ESTITM (SRS Estimation Item Value).

• Create a hierarchy node in the catalog

With the right mouse click a new hierarchy node can be maintained. The following data should be maintained:

• The Hierarchy ID (can be defined as the customer wants)
• Description (Char 40)
• The Hierarchy group SCHM defines in the OAS or Customer Portal that only one code in this hierarchy can be selected (e.g. used for inspection). This Group can be defined in the Customizing.

Create Hierarchy in the Catalog

To each hierarchy a code can be defined. After creating the code the estimated time can be maintained as following:

Maintain the estimated times

With the function “Calculation” the finding of the values can be checked. See the following example

While setup Estimation Catalog for OAS or Customer Portal , Lean Condition usage can be defined in a way, that one of the condition table defines Estimation Value independent of user role (field USROLE is not included as criteria) while second table defines Estimation Value for the same criteria but with USROLE included as a condition.

Example of the access sequence:

Example for Lean Condition table to determine the catalog

Estimation Value defined using table with access seq. 20 will be independent of User Role, so values will be visible for each user. Values defined by table with access seq. 30 will be visible only for users with specified User Role.

Example:

As result, when displaying Catalog OAS_CAT_TOY without any criteria, codes MCE1, MCE2, MCE3, SC5 and SC6 are displayed without any value:

After entering User Role ADMIN as criteria for calculation, these codes display values:

Result after doing the calculation with user role

All estimation codes are defined with flag ‘Allow empty value’ not set. This causes, that if no value is calculated for the code, this code is not included in the result at all.

Flag: "Allow empty value" for a code

It is possible to restrict usage of a code to vehicles meeting certain mileage and/or age criteria. If the fields "Mileage from - to" and/or "Months from - to"  are set, then the Customer Portal will automatically filter out irrelevant codes.

Codes will be deemed irrelevant if both, mileage and vehicle age do not fit. If vehicle age is not specified then age restriction will be ignored. If vehicle mileage is not specified then mileage restriction will be ignored.

Mileage and age criteria

Calling OAS or Customer Portal for standard, or anonymous user, only codes with values corresponding to current user role are determined and displayed. This means, that user in OAS or Customer Portal sees only services with user role-independent values:

 Display of estimation Catalog in the OAS (1)

When calling OAS or Customer Portal for internal user (with role ADMIN assigned), service catalog includes all codes: user role independent and those defined for role ADMIN as well:

The URL of an image to be displayed should be a link to an image in following formats: JPEG, GIF, PNG, BMP, TIFF or SVG (ICO should also work).You can use absolute or relative URLs. Absolute means that URL contains hostname, i.e. http://downloadicons.net/sites/default/files/tire-icon-46884.png A relative URL doesn't include hostname and it's relative to the domain, i.e. /sap/bc/bsp/sap/public/zDBME_oas/audi.ico, which means that the image is hosted on the same server as application.

Example could be the following:

And the result is following:

In the module VSS Packages can be maintained with the transaction /DBE/PACKAGE. These packages can be assigned to the Estimation Catalogues.

VSS Transaction /DBE/PACKAGE to maintain packages