probaseline · sap easy access menu no prefix is required. probaseline can also be integrated in a...

User Manual

ProBaseline

2

Imprint

Legal Notice

Issue June 2019 / C.00.0All rights reserved.

Copyright and Usage Rights

This document is copyrighted and may not be modified without the prior written consent of the publisher.Reproduction and distribution is permitted only with the following legal notice:© 2019 ProNovia AGChanges and updates without notice.Microsoft is a registered trademark of Microsoft Corporation.SAP is registered trademark of SAP AG.ProNovia is a registered trademark of ProNovia AG.

Disclaimer

ProNovia AG assumes no responsibility for any typographical, technical, or other inaccuracies, errors, oromissions and their consequences. Liability in respect of the software described herein, please see oursoftware terms.

ProNovia AGP.O. BoxCH-8180 BülachFon +41 44 860 13 06www.pronovia.cominfo [at] pronovia.com

Publisher/Contact

ProNovia A G | P .O . Box | 8180 Bülach | Switzerland | pronovia.com

mailto:

ProNovia AG | P .O . Box | 8180 Bülach | Switzerland | pronovia.com 3

Table of Content

Introduction 41

Other documents1.1 4

Prerequisites1.2 4

Symbols in this document1.3 4

Overview1.4 4

ProBaseline Cockpit 62

Interface2.1 7

Menu Bar2.2 8

Menu Option "Dynamic Baseline"2.2.1 8

Menu Option "Edit"2.2.2 8

Menu Option "Settings"2.2.3 8

Tab "Definition/Selection"2.3 11

Section "Format Basic Selection"2.3.1 11

Section "Entry/Start Object"2.3.2 11

Section "Validity"2.3.3 11

Tab "Object Selelction"2.4 14

Tab "Field Selection"2.5 17

Explanations2.5.1 17

Output Processors 223

Screen Output3.1 22

File Output3.2 23

Integration in a ProFramework application 264

Client Specific Transactions 285

Transactions5.1 28

Output definitions5.2 29

Output processors5.3 30

Introduc tion

ProBaseline

ProNovia AG| P .O . Box | 8180 Bülach | Switzerland | pronovia.com 4

1 Introduction

This document describes the following subjects:

· Operation of ProBaseline.

· ProBaseline user interface.

This document describes ProBaseline as delivered. Client specific enhancements and customizing canchange the appearance and behavior of ProBaseline compared to information/illustrations in this manual.Therefore please consider your client specific definitions.

1.1 Other documents

All relevant and available documents are found in the ProNovia Support Center: http://support.pronovia.ch.

1.2 Prerequisites

Prerequisites for using ProNovia products:

· ProNovia products to be used must be installed and setup correctly on the relevant systems.

· ProNovia products must be properly integrated, activated and configured. Details see documentProBasicLib, Integration and Enhancement Manual.

· To use ProNovia products, valid licenses for each product must be loaded on each system. Details seedocument ProBasicLib, Integration and Enhancement Manual.

· The necessary permissions for the display and maintenance of SAP objects must be present.

· For execution of ProBaseline also ProConfiguration together with a valid licence must be installed (tobe licensed separately).

1.3 Symbols in this document

In this document following symbols may be used:

Important or critical hint, to pay special attention to.

Additional information.

1.4 Overview

ProBaseline can be divided into different sections and applications:

1. ProBaseline cockpit. For details please refer to ProBaseline Cockpit .

2. Output via ProBaseline output processors. For details please refer to Output Processors .

3. Transaction control for client specific ProBaseline transactions. For details please refer to ClientSpecific Transactions .

6

22

28

http://support.pronovia.ch

Introduc tion

ProBaseline


ProBaseline cockpit

· ProBaseline cockpit is a SAP-PLM reporting cockpit, which can generate and output baselinereports.

· The output is based on a "KOFIMA item", generated withProConfiguration andProConfigurationLogistic, if available with a product structure.

· Output data from ProBaseline is created based on the following parameters specified by the user:

o Entry / start object (material / material BOM)

o Validity

o Output definition (Objects & Fields)

For details please refer to ProBaseline Cockpit .

Output Processors

The output processors will generate the desired output based on the determined data. Basicallyfollowing options exist:

· Tree, matrix or GUI list (screen output)

· File (text file or PDF, etc.)

For details please refer to Output Processors .

Client Specific Transactions

The ProBaseline transactions allow assigning definitions for output definition and output processors toclient specific ProBaseline transactions.

For details please refer to Client Specific Transactions .

6

22

28

P roBaseline C ockpit

ProBaseline


2 ProBaseline Cockpit

Start ProBaseline Cockpit with SAP PLM transaction /PCH/CDB (old /PRONOVIA/PBL).

Transactions from a reserved name space must always start with /N in the command field. In theSAP Easy Access Menu no prefix is required.

ProBaseline can also be integrated in a ProFramework application as ProFramework widget, seeProBaseline in a widget of a ProFramework application

SAP command field:

SAP Easy Access Menu:

(Favorites > Insert transaction directly)

26


ProBaseline


2.1 Interface

The ProBaseline user interface is divided in three areas:

Element Description

1 Menu

· Menu functions for ProBaseline.

2 Push buttons

· For general functions.


ProBaseline


Element Description

3 Tabs

· Depending on the selected tab, the following information is shown:

o Definition/Selection > Selection of a output definition, output processor, entry/start

object and validity.

o Object selection > Selection of configuration types and documents which shall be

displayed.

o Field selection > Selection of field to be output for determined objects.

2.2 Menu Bar

The following ProBaseline functions are available for menu option «Dynamic Base Line».

· Dynamic Baseline

· Edit

· Settings

2.2.1 Menu Option "Dynamic Baseline"

Execute

Description

Menu DynamicBaseline Execute

Push button

Function Start output

Explanation Starts output according to entry object, defined options and selected outputprocessor.

Additional Information / Key

Description

Menu DynamicBaseline Additional informatio /key

Push button

Function Indicates additional information.

Explanation Shows additional information for fields and options in the various tabs.


ProBaseline


Exit

Description

Menu DynamicBaseline Terminate

Push button

Function Terminates ProBaseline.

Explanation Exit transaction.

2.2.2 Menu Option "Edit"

Safe output definition

What Description

Menu Edit Save OutputDef

Push button

Function Save current output definition.

Explanation The current output definition will be saved. The following parameters are required:

· Output def.: ID for output definition to be saved.

· Description: Language dependent description for definition to be saved.

· System definition: With this option is set, the definition is saved as systemdefinition and can be used by any user.

· Maintain other languages: Allows further entries for the description in otherlanguages.

A output definition includes all settings for the object and field selection.

Output definitions (and their specific settings) are not included in the SAPtransport system.


ProBaseline


System definitions can only be overwritten, if authorization is available.

Editing or overwriting other user’s definitions is only possible if authorizationis available.

Delete output definition

What Description

Menu Edit Delete OuputDef

Push button Not available.

Function Delete current output definition.

Explanation The currently selected output definition will be deleted.

System definitions can only be deleted, if authorization is available.

Deleting other user’s definitions is only possible if authorization is available.

Cancel

What Description

Menu Edit Cancel

Push button

Function TerminatesProBaseline.

Explanation Terminates transaction.

2.2.3 Menu Option "Settings"

Define

What Description

Menu Settings Define transactions.

Push button Not available.

Function ProBaseline transaction control.

Explanation Please refer to Client Specific Transactions .28


ProBaseline


2.3 Tab "Definition/Selection"

Definition of output definition, output processor, entry object and validity for the output.

A output definition includes all settings for the object and field selection.

The output definition which has been used and defined last will be saved automatically for eachuser and will be available under output definition selection «Last manual selection».

2.3.1 Section "Format Basic Selection"

Selection of output definition and output processor

Field Function

Output def. Selection of output definition. Available are:

· Last manually created definition.

· Saved output definitions (system definitions or personal definitions).

Depending on the customizing settings an additional text will beadded to the system definition and user specific definition name. Thisway the different definition types can be easily distinguished (e.g. thetext “(P)” for a personal definition name).

Output Processor Selection of possible output processors. The output processor is responsiblefor how data will be displayed, according to selection and output definition.For details please refer to Output Processors .

Language Selection of the output language. This selection is only available if supportedby the selected output processor.

2.3.2 Section "Entry/Start Object"

Selection of material and BOM.

22


ProBaseline


Field Function

Material The material number which is the entry object for the BOM explosion anddynamic baseline report.

Plant Plant number for BOM explosion.

Alternative Alternative BOM for BOM explosion.

Explosion level Defines the maximum explosion levels for an explosion of a multi level BOM.The number defines the maximum level to be exploded. Entry material haslevel 0.

Required qty Required quantity sets the reference for the component quantity. If no requiredquantity is defined, the component quantities will be according to the BOMpositions.

This selection option should be used together with the correspondingfields in the field selection (component quantity), see Tab "FieldSelection" .

By BOM usage Sets BOM usage for BOM explosion.

By application Sets BOM application for BOM explosion.

Flat, sorted, reduced list If this option is set, the output of the BOM explosion will be as follows:

· No structure information (level, position number, quantities).

· Sorted by material number.

· Only one output for multiple used components.

2.3.3 Section "Validity"

Selection of validity of material and objects.

Options are analogueProConfiguration validity options. For details please refer toProConfiguration, User Manual (ProNovia Support Center: http://support.pronovia.ch).

17

http://support.pronovia.ch


ProBaseline


The explosion of a material BOM always starts on the defined valid from date. The parametervalid to has no influence on the BOM explosion.

The output of document objects to a certain material respects validity ranges (From .. To). Thevalidity range will be displayed in a separate line, including document objects for this validityrange.Example:


ProBaseline


2.4 Tab "Object Selelction"

Selection of objects (configuration types and documents).

The object selection is part of a output definition.

General Information

· If no parameters are set, all objects will be selected.

· It is possible to select values, e.g. masks with *, > greater than, = equals, etc.

· The entry fields can be combined.

· Multiple entries are possible using push button .

Field Function

Config. types to explode Only for selected ProConfiguration configuration types the BOMs will beexploded and displayed. Exploded configuration types will always be shown.

Config. types to show Only the selected ProConfiguration configuration types will be shown. For allother configuration types the structures will not be exploded and shown in aBOM explosion. See also Section "Entry/Start Object" .

Usages Depending on the selection, the material BOM usages of the material will beshown. The following options are available:

11


ProBaseline


Field Function

· Don’t show usages

o No usages are displayed.

· Mark usages

o If usages exist, they will be indicated in a separate filed. This option is

supported by screen outputs (ALV list / tree ( )).

· Show usage in separate node

o If usages exist, they are shown in a separate node. This option is

recommended for tree output.

· Show usages directly

o If usages exist, they will be shown directly. This option is recommended

for file output.


ProBaseline


Field Function

If usages for the output are selected, the field “Usage” will beactivated automatically. Tab «Field selection», only allows changingthe position of this field. Activating/deactivating is only possible withthe functions described above.

All usages within the validity range and according the organizationalunits are selected (settings "OrgUnit according start object", "Client /Plant", "Sales Organization" and "Distribution Channel" below).

Show sub position If existing, sub positions will be shown on a separate line.

Output documents If ProConfiguration documents exist, they will be output. The options belowallow a more detailed selection.

Other object types When activation this option none document objects within ProConfigurationdata packages will be used for output (e.g. routings, quality info records,suppliers, etc.). The options below allow a more detailed selection.

Output object datapackage

ProConfiguration data packages will be used for output.

OrgUnit according startobject

If activated the settings "Client / Plant", "Sales Organization" and "DistributionChannel" below are ignored and these filters will be set up automaticallyaccording the start object. Following rules apply:

· If the start object is without a plant (group BOM):

o Only data packages, usages and objects which are assigned to the

client view are selected.

o Data packages and objects assigned to a sales view are ignored.

· If the start object is with plant:

o Only data packages, usages and objects which are assigned to this

plant are selected.

o If data packages and objects to sales views should be used in output,

then only such sales views are selected, which have a delivery plantassigned matching the plant from the start object.

Load data package types Document output only for selected ProConfiguration data package types.

Plant / client Output of usages, data packages and objects only to selected plants.

This option is not used for material BOM explosion. For clientspecific objects enter a selection with operand = and value space.

If the option "OrgUnit according start object" is activated, this settingis ignored.


ProBaseline


Field Function

Sales Organization Output of ProConfiguration objects only for selected sales organizations.


Distribution Channel Output of ProConfiguration objects only for selected distribution channels.


Object types in datapackages

Output of documents only for selected ProConfiguration object types.

If activated, the data package objects will only be shown if anmatching object exists in the data package.

Object relevance in DP Output of documents only for selected ProConfiguration objects relevancies.


Documents with Orig.-Appl.

Output of documents only for selected original applications.

Documents withlanguage

Output of documents to ProConfiguration documents only for selectedProConfiguration languages.


Use the value “=” for selection of documents without languageassigned (=none).

2.5 Tab "Field Selection"

In this tab the fields to output and the field order within the output is specified.

Field selection is part of the output definition.

Please note, that the field selection and / or order could be defined or overwritten by the outputprocessor:

· PDF processor:

o The fields and the order is completely defined by the used SAP SmartForms or SAPScript

layout.

· Tree processor:


ProBaseline


o Field order and size can be changed by user using layouts. Such layouts can be saved.

Function Description

Heading Field description

Short Description Short explanation of the field (more see next section).

Output If activated, the field will be shown in the output.

Only with values If activated, the field will only be shown, if object field values have beendetermined (e.g. CAD characteristics).

When using the ProBaseline tree output widget, this option isignored.

Field Name Table field name (more see next section).

The order of the selected fields can be changed with these push buttons.

Obj.Info Format Information about the object. The format can be selected from a Drop-Downlist:


ProBaseline


Function Description

The following formats are available:

· <Type> / <Relevance Des>¦<Type Des>

· <Type> / <Relevance Des>¦<Type Des>

· <Type Des> / <Relevance>¦<Type>

· <Type Des> / <Relevance Des>¦<Type Des>

· <Type> / <Relevance>¦<Type>

· <Type Des> / <Type Des>

· <Relevance Des>¦<Type Des>

For more detailed information about the field description, push the default helpbutton.

Document key startingwith number

The document key will either start with document number or document type.

2.5.1 Explanations

Not all fields are listed. Only ProBaseline specific fields and fields specially treated inProBaseline are listed.

Field Explanation / Example

Altitm

ALPOS

Indicator of an alternative item.

Asm

STLKZ

Indicates that an assembly (BOM) to a material is available.

Description

BEZEI

Object description in login language.

Valid from date

DATUV

Valid from data for object.

Valid to date

DATUB

Valid to date for object.

Inf

OBSTA_ICON

Status icon for object.

Int. Obj.key Internal SAP object key for object, according to object table.


ProBaseline



OBJEK

Int. Obj.Status

OBSTA_INT

Internal object status (language independent).

Relevant for output of language independent document status.

Component Qty.(CUN)

MNGKO

Calculates component quantity:

Based on the component quantity and the input quantity.

E.g.: Component quantity (CU) 0,500 * input quantity 10 = 5'000

Quantity / Unit (UN)

MNGTXT

Calculated component quantity and unit shown in text format.

Example: 5'000 KG

Obj.Information

OBJINFTXT

Show information about the object, see above.

Status

OBSTA_EXT

Object status, if available in external format and in the login language.

Object

OBJEK_EXT

Object key, e.g. material number, document key

Document key will either start with document number or documenttype.

Object name

OBJ_TXT

Object name

E.g.: material / data package / document / validity / sub position etc.

Object type

OBJTY

Object type:

· Object type

· Daten package type

· Configuration type

Org.u.-type

ORGTY

Type of organization unit of BOM.

Org.Key

ORGKY

Key for organization unit.

Originals

HAS_ORIG

Indicates that document info record of originals exists.


ProBaseline



Level

STUFE

Show level of complete structure (all objects) numerically.

E.g.: 0, 1, 2, 3

Level

STUTXT

Level indicated as text (with dots….) within structure (all objects).

Example: 0, ...1, ..2, …3

Level

BOM_STUFE

Show level of exploded BOM items numerically.

E.g.: 0, 1, 2, 3

Level

BOM_STUTXT

Level of BOM items indicated as text (with dots….) within exploded BOM.

Example: 0, ...1, ..2, …3

Table

SAPOB

SAP database table name for object to be shown.

Type

OBJ_IMAGE

Icon / image for object type (material / data package / document / validity /sub position etc.).

Usag.

USAGES

Mark / show further usage of objects.

Counter

LFNUM

Line counter for output.

O utput P rocessors

ProBaseline


3 Output Processors

The output processor defines how data, which is read according to the selection, will be displayed. Thefield selection defines the columns to be shown.

In general two main types are available:

· Output processors, which will display the evaluated data on a screen.

· Output processors, which will export the evaluated data to a file.

Format and processing can be defined as needed for each output processor in the customizing.

3.1 Screen Output

These output processors will display the evaluated data on a screen.

GUI: ALV Processor

The output is created using the SAP ALV (ABAP List Viewer).

GUI: PBL List Processor

The output is created as a default ABAP List.

O utput P rocessors

ProBaseline


GUI: PBL Tree Processor

The output is created with a column tree.

The tree output is possible in a separate window or directly integrated in a ProFrameworkwidget within a ProFramework application. See ProBaseline in a widget of a ProFrameworkapplication

3.2 File Output

These output processors will export the evaluated data into a file. File name and storage location must bedefined.

File: PBL PDF processor

Data output to a PDF file, the layout is defined by the used SmartForm or SAPscript form.

26

O utput P rocessors

ProBaseline


File: PBL Plain Data File

Data output to a text file with fix columns. Separation of columns with symbol "|". The columns willnot be named.

File: PBL Simple Text File Grid

Data output to a text file. Separation of columns and lines with a "text grid". Columns titles arehidden.

File: PBL Simple Text File Group

Data output to a text file. Objects are listed in groups per material. Separation of columns and lineswith a "text grid". Columns names will be indicated.

File: PBL Simple Text File Header

Data output to a text file. Separation of columns with symbol "|". The columns titles are indicated.

O utput P rocessors

ProBaseline


File: PBL Tab Delimited File

Data output to a text file. Separation of columns with with "TAB". The columns titles are indicated.

File: SEAL Plot Order

Creates a SEAL DVSREPRO plot order for all documents/originals which are found in this structure.Details depend on the customizing of the plot order.

Integration in a P roFramework application

ProBaseline


4 Integration in a ProFramework application

In a ProFramework application ProBaseline can run directly integrated. Two widgets are provided:

· The ProBaseline selection widget

· The ProBaseline tree output widget

Depending on the configuration the user can enter the report parameters in the selection widget and thanexecute the report or the report is executed directly when clicking on the tree output widget.

Selection widget

Which fields are displayed and ready for input depends on the widget settings and can bedifferent to the example screen above.

Area / field Description

Format basic selection See description in section Section "Format Basic Selection" .

BOM See description in section Section "Validity" , but note that the validity inthis widget is implemented in a different way, see below.

Validity In the selection widget the validity to use can either be selected directly or thecurrently selected ProConfiguration validity can be used. See table below forthe validity options available.

Ausführen / Using the execute icon in the titlebar of the widget, the baseline report will beexecuted.

11

12

Integration in a P roFramework application

ProBaseline


The validity options:

Option Description

Actual validity

See ProConfiguration user manual, section Selection of Validity in chapterconfiguration display.

All validities

Highest validity

Validities starting fromtoday

Validities starting withtoday's valid revision

Use selected validity With this option the actually within the application set ProConfigurationvalidity will be used. Is this option selected, then right of this drop down apush button to change the actual ProConfiguration selection is available.

Keydate and date range are only available using this option.

Output

Depending on the selected output processor and the application settings the result of the baseline reportcan been shown in a separate window, be written in a file or be shown in a tree output widget. SeeOutput Processors and the following sections for possible output variants.

Tree output widget

The application can be defined, that the result is shown directly in a widget, without selection widget. Inthis case all required information is defined in the widget parameters.

22

C lient Spec ific T ransac tions

ProBaseline


5 Client Specific Transactions

Start Transaction Control

In order to define client specific ProBaseline transactions, the transaction control must be started. Usemenu Settings Define Transactions within a ProBaseline transaction (e.g. /PRONOVIA/PBL).

In general the idea for setting output definitions in a transaction definition is, that either to eachoutput definition a output processor is assigned or that none of the output definitions haveassigned an output processor, but all valid processors are defined in Output processors. Acombination of both methods is possible.

The transaction control settings are not linked with the SAP transport system.

It is not recommended to store definitions for transaction sProBaseline Cockpit(PRONOVIA/PBL) in the transactions control, in order to keep them as unlimited cockpit andtool for the transaction control.

Starting the transaction control requires adequate authorization.

5.1 Transactions

Definition of client specific ProBaseline transactions, which can then be used by the user.

Field Description

Transaction Code Use delivered transactions /PRONOVIA/PBL1 to /PRONOVIA/PBL19.Optional, copies of /PRONOVIA/PBLn transactions to client specifictransactions can be used, too.

TrnCtrlFunc Transaction Controller (according customizing currently always PBL$MAST).

Title Transaction title. Also used by some of the output processors (actual by allscreen processors). Without input the text ProBaseline and the installedproduct version will be shown.


ProBaseline


Field Description

Change of objectselection not allowed.

If activated, no changes on tab „Object selection“ are allowed.

Change of field selectionnot allowed.

If activated, no changes on tab „Field / Selection“ are allowed.

5.2 Output definitions

Assignment of one or more output definitions including output processors to a transaction.

Field Description

Output definition Selectable output definitions for these transactions. Without input all possibledefinitions can be selected.

Output definitions must first be defined and saved before they can beassigned. Only system definitions can be assigned.

Multiple definitions can be assigned.

Output processor If an output processor is entered, only this output processor will be availablefor this output definition. Therefore no selection of an output processor will beavailable for this transaction, and settings under option „output processors“will have no influence.

The output processor assigned must not be in the list of OutputProcessors.

Even if marked as hidden in customizing, a processor can be usedhere.


ProBaseline


5.3 Output processors

Assignment of possible output processors to the transaction.

Field Description

Output proc. Selectable output processors for this transaction. Without input all definedprocessors are available, except hidden processors.

If marked as hidden in customizing, a processor can’t be used.