19.09.2012 Views

ProNovia SAP PLM DynamicBaseline - ProNovia AG

ProNovia SAP PLM DynamicBaseline - ProNovia AG

ProNovia SAP PLM DynamicBaseline - ProNovia AG

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong><br />

pro ovia<br />

Product Lifecycle Management<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O.Box, CH-8180 Bülach<br />

User Manual


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

Document Information<br />

Intended for?<br />

→ <strong>SAP</strong> <strong>PLM</strong> user<br />

→ <strong>SAP</strong> <strong>PLM</strong> consultants<br />

Validity<br />

Version / date of issue A.02 / 24.06.2011<br />

This version replaces all former versions.<br />

Valid until Release of a new version<br />

General<br />

<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> Product <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong><br />

Product-Version V1.2<br />

Classification<br />

Document Type <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> Products Documentation<br />

Document classification No classification<br />

Creation / Release<br />

Author of document Marcel Schifferle / Frauke Böni / Christian Gradolf<br />

Release of document Christian Gradolf<br />

Filing<br />

Electronically According <strong>ProNovia</strong> Guideline: <strong>ProNovia</strong> Documents<br />

Physically No filing<br />

Version History Initiator / Reason of Change<br />

A.00 First English edition for product version V1.0<br />

A.01 Corrections.<br />

A.02 Issue for product version V1.1<br />

A.03 Issue for product version V1.2<br />

Copyright Remarks<br />

Copyright <strong>ProNovia</strong> <strong>AG</strong> 2009-2011. All rights preserved. Subject to change.<br />

→ Microsoft is a registered trademark of Microsoft Corporation.<br />

→ <strong>SAP</strong> and <strong>SAP</strong>.com is a registered trademark of <strong>SAP</strong> <strong>AG</strong>.<br />

→ <strong>ProNovia</strong> is a registered trademark of <strong>ProNovia</strong> <strong>AG</strong>.<br />

<strong>ProNovia</strong> <strong>AG</strong>, Postfach, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 2/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

Table of Content<br />

1 Introduction ........................................................................................ 4<br />

1.1 Document Content ....................................................................................................... 4<br />

1.2 Additional Documents .................................................................................................. 4<br />

1.3 Requirements .............................................................................................................. 4<br />

1.4 Abbreviations ............................................................................................................... 4<br />

1.5 Document Symbols ...................................................................................................... 5<br />

2 Overview ............................................................................................. 6<br />

2.1 <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> Cockpit ........................................................... 6<br />

2.2 Output Processors ....................................................................................................... 6<br />

2.3 Client Specific Transactions ........................................................................................ 6<br />

3 <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> Cockpit ................................ 7<br />

3.1 Start ............................................................................................................................. 7<br />

3.2 Interface ....................................................................................................................... 8<br />

3.3 Interface Functions ...................................................................................................... 9<br />

3.3.1 Title Bar ........................................................................................................................ 9<br />

3.3.1.1<br />

3.3.1.2<br />

3.3.1.3<br />

Menu Option „<strong>DynamicBaseline</strong>“ ................................................................................. 9<br />

Menu Option „Edit“ .....................................................................................................10<br />

Menu Option „Settings“ ..............................................................................................12<br />

3.4 Tab “Layout/Selection” ...............................................................................................13<br />

3.4.1 Layout Area: „Format Basic Selection“ ......................................................................14<br />

3.4.2 Layout Area „Entry / Start Object“ .............................................................................14<br />

3.4.3 Layout area „Validity“ .................................................................................................14<br />

3.5 Tab „Object Selection“ ...............................................................................................15<br />

3.6 Tab „Field Selection“ ..................................................................................................18<br />

3.6.1 Explanations of Fields ................................................................................................19<br />

4 Output Processors ........................................................................... 21<br />

4.1 Output Processors for Screen Output .......................................................................21<br />

4.1.1 General Functions .....................................................................................................22<br />

4.1.2 Context Menu Functions for Data ..............................................................................22<br />

4.2 Output Processors for File Output .............................................................................23<br />

4.2.1 General Functions .....................................................................................................25<br />

5 Client Specific <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong><br />

Transactions ..................................................................................... 26<br />

5.1 Start Transaction Control ...........................................................................................26<br />

5.1.1 Transactions ..............................................................................................................26<br />

5.1.2 Layouts ......................................................................................................................27<br />

5.1.3 Output Processor .......................................................................................................28<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 3/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

1 Introduction<br />

1.1 Document Content<br />

This document describes the following subjects:<br />

► Operation of <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong>.<br />

► <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> user interface.<br />

This document describes the <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> as delivered. Client specific<br />

enhancements and customizing can change the appearance and behavior of <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong><br />

<strong>DynamicBaseline</strong>. Therefore please consider your client specific definitions.<br />

1.2 Additional Documents<br />

All relevant and available documents for the <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> can be found on<br />

the <strong>ProNovia</strong> homepage (www.pronovia.com � Quick Links -> Downloads).<br />

1.3 Requirements<br />

► <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> has to be installed and setup correctly on your system. To<br />

import transport orders into <strong>SAP</strong> R/3 System, the required authorizations are necessary.<br />

► <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> ProcessManager has to be installed and setup correctly on your system.<br />

► To run <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> the user must have the required authorizations.<br />

► To run <strong>SAP</strong> <strong>PLM</strong> transactions and programs, triggered by <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong>,<br />

the required user authorizations are necessary.<br />

► To run <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> a valid <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> license<br />

must be installed.<br />

► To run <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> a valid <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> ProcessManager license,<br />

must be installed.<br />

1.4 Abbreviations<br />

In this document the following abbreviations are used for other <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> products:<br />

► PBL <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong><br />

► PLG <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> GUI<br />

► PRM <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> ProcessManager (Workbench und Navigator)<br />

The document <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> Solutions and Products gives an overview about all available<br />

<strong>ProNovia</strong> products.<br />

All documents can be downloaded from the <strong>ProNovia</strong> homepage (www.pronovia.ch � Quick Links �<br />

Downloads).<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 4/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

1.5 Document Symbols<br />

In this document the following symbols are being used:<br />

�<br />

�<br />

�<br />

�<br />

Important or critical hint, to pay special attention to.<br />

Additional information.<br />

BusinessAddIns are available (See also document <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong>,<br />

Integration & Enhancement).<br />

Function protected by <strong>SAP</strong> authorization. For authorizations please refer to document <strong>ProNovia</strong><br />

<strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> Integration & Enhancement.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 5/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

2 Overview<br />

<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> can be divided into different sections and applications:<br />

► <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> Cockpit. For details please refer to 3, <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong><br />

<strong>DynamicBaseline</strong> Cockpit.<br />

► Output via <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> Output Processors. For details please refer to<br />

4, Output Processors.<br />

► Transaction control for client specific <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> transactions. For<br />

details please refer to 5, Client Specific <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> Transactions.<br />

2.1 <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> Cockpit<br />

► <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> Cockpit is a <strong>SAP</strong>-<strong>PLM</strong> reporting cockpit, which can generate<br />

and output a baseline report.<br />

► The output is based on a KOFIMA item, generated with <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> ProcessManager and<br />

<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> ProcessManager – Logistic Extension, if available with a product structure.<br />

► All output data will be defined by the user with <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong>, setting the<br />

following parameters:<br />

→ Entry / start object (material / material BOM)<br />

→ Validity<br />

→ Layout (Objects & Fields)<br />

2.2 Output Processors<br />

The output processors will generate the desired output based on the determined data. Basically<br />

following options exist:<br />

► Tree, matrix or GUI list (screen output)<br />

► File (text file or PDF, etc.)<br />

2.3 Client Specific Transactions<br />

► The <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> transaction control allows assigning definitions for<br />

layouts and output processors to client specific <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> transactions.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 6/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

3 <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong><br />

Cockpit<br />

3.1 Start<br />

Start <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> Cockpit with <strong>SAP</strong> <strong>PLM</strong> transaction /PRONOVIA/PBL.<br />

�<br />

Transactions from a reserved namespace must always start with /N in the command field. In<br />

the <strong>SAP</strong> Easy Access Menu no prefix is required.<br />

<strong>SAP</strong> command field<br />

AP Easy Access<br />

Menu<br />

�<br />

Favorites � Insert transaction directly<br />

In future versions, <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> will be available directly in the <strong>SAP</strong><br />

<strong>PLM</strong> GUI.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 7/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

3.2 Interface<br />

The <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> user interface is divided in three layout areas:<br />

Element Description<br />

1 Menu<br />

► Menu functions for <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong>.<br />

2 Push buttons<br />

► For general functions.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 8/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

Element Description<br />

3 Tab<br />

► According to the tab selection, the following information is shown:<br />

→ Layout/Selection: Selection of a layout, output processor, entry/start object and<br />

validity.<br />

→ Object selection: selection of configuration types and documents which shall be<br />

displayed.<br />

→ Field selection: Selection of field to be output for determined objects.<br />

3.3 Interface Functions<br />

<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> functions can be initiated by various options:<br />

► Function call via menu options in the title bar<br />

► Function call via push button<br />

3.3.1 Title Bar<br />

3.3.1.1<br />

Menu Option „<strong>DynamicBaseline</strong>“<br />

The following <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> functions are available for menu option „Dynamic<br />

Base Line“.<br />

3.3.1.1.1 Execute<br />

Description<br />

Menu <strong>DynamicBaseline</strong> � Execute<br />

Push button<br />

Function Start output.<br />

Explanation Starts output according to entry object, defined options and selected output<br />

processor.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 9/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

3.3.1.1.2 Additional Information / Key<br />

Was Description<br />

Menu <strong>DynamicBaseline</strong> � Additional information / key<br />

Push button<br />

Function Indicates additional information.<br />

Explanation Shows additional information for fields and options in the various tabs.<br />

3.3.1.1.3 Exit<br />

Description<br />

Menu <strong>DynamicBaseline</strong> � Terminate<br />

Push button<br />

Function Terminates <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong>.<br />

Explanation Exit transaction.<br />

3.3.1.2<br />

Menu Option „Edit“<br />

The following <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> functions are available for menu option „Edit“.<br />

3.3.1.2.1 Safe Layout<br />

Description<br />

Menu Edit � Save layout.<br />

Push button<br />

Function Save current layout.<br />

Explanation The current layout will be saved. The following parameters must be entered in the<br />

dialog:<br />

► Layout<br />

→ ID for layout to be saved.<br />

► Description<br />

→ Language dependent description for layout to be saved.<br />

► System layout<br />

→ Layout will be saved user specific, except this option is set.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 10/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

► Maintain other languages<br />

→ Allows further entrees for the description in other languages.<br />

�<br />

�<br />

3.3.1.2.2 Delete Layout<br />

Description<br />

Menu Edit � Delete layout.<br />

Push button Not available.<br />

Function Delete current layout.<br />

A layout includes all settings for the object and field selection.<br />

Layouts (and their specific settings) are not included in the <strong>SAP</strong><br />

transport system.<br />

System layouts can only be overwritten, if authorization is available.<br />

Editing or overwriting other user’s layouts is only possible if<br />

authorization is available.<br />

Explanation The currently selected layout will be deleted.<br />

System layouts can only be deleted, if authorization is available.<br />

�<br />

3.3.1.2.3 Cancel<br />

Description<br />

Menu Edit � Cancel.<br />

Push button<br />

Deleting other user’s layouts is only possible if authorization is available.<br />

Function Terminates <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong>.<br />

Explanation Terminates transaction.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 11/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

3.3.1.3<br />

Menu Option „Settings“<br />

The following <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> functions are available for menu option „Settings“.<br />

3.3.1.3.1 Terminate Transaction<br />

Description<br />

Menu Settings � Define transactions.<br />

Push button Not available.<br />

Function <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> transaction control.<br />

Explanation Please refer to chapter 5, Client Specific <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong><br />

Transactions.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 12/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

3.4 Tab “Layout/Selection”<br />

Definition of layout, output processor, entry object and validity for the output.<br />

�<br />

A layout includes all settings for the object and field selection.<br />

The layout which has been used and defined last will be saved automatically for each user and<br />

will be available under layout selection „Last manual selection“.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 13/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

3.4.1 Layout Area: „Format Basic Selection“<br />

Field Function<br />

Layout Selection of layout. Available are:<br />

► Last manually created selection.<br />

► Saved layouts (system layouts or personal layouts).<br />

�<br />

Depending on the customizing settings an additional text will be<br />

added to the system layout and user specific layout name. This<br />

way the different layout types can be easily distinguished (e.g. the<br />

text “(P)” for a personal layout name).<br />

Output Processor Selection of possible output processors. The output processor is responsible<br />

for how data will be displayed, according to selection ad layout definition.<br />

For details about output processors refer to 4, Output Processors.<br />

Language Selection of the output language. This selection is only available if supported<br />

by the selected output processer.<br />

3.4.2 Layout Area „Entry / Start Object“<br />

Field Function<br />

Material The material number which is the entry object for the BOM explosion and<br />

dynamic baseline report.<br />

Plant Plant number for BOM explosion.<br />

Alternative Alternative BOM for BOM explosion.<br />

Explosion level Defines the maximum explosion levels for an explosion of a multi level BOM.<br />

The number defines the maximum level to be exploded. Entry material has<br />

level 0.<br />

Required qty Required quantity sets the reference for the component quantity. If no<br />

required quantity is defined, the component quantities will be according to<br />

the BOM positions.<br />

�<br />

By BOM usage Sets BOM usage for BOM explosion.<br />

This selection option should be used together with the<br />

corresponding fields in the field selection (component quantity),<br />

see 3.6, Tab „Field Selection“.<br />

By application Sets BOM application for BOM explosion.<br />

Flat, sorted, reduced<br />

list<br />

3.4.3 Layout area „Validity“<br />

Set validity for output of material and objects.<br />

�<br />

�<br />

If this option is set, the output of the BOM explosion will be as follows:<br />

► No structure information (level, position number, quantities).<br />

► Sorted by material number.<br />

► Only one output for multiple used components.<br />

Options are analogue <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> ProcessManager validity options. For details please<br />

refer to <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> ProcessManager User Manual (www.pronovia.com � Quick Links<br />

� Downloads).<br />

The explosion of a material BOM always starts on the defined valid from date. The parameter<br />

valid to has no influence on the BOM explosion.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 14/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

The output of document objects to a certain material respects validity ranges (From � To). The<br />

validity range will be displayed in a separate line, including document objects for this validity<br />

range.<br />

Example:<br />

3.5 Tab „Object Selection“<br />

Definition of object determination (configuration types and documents).<br />

� The object selection is part of a layout.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 15/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

General Information<br />

► If no parameters are set, all objects will be selected.<br />

► It is possible to select values, e.g. masks with *, > greater than, = equals, etc.<br />

► The entry fields can be combined.<br />

► Multiple entries are possible using push button .<br />

Field Function<br />

Config. types to<br />

explode<br />

Only for selected PRM configuration types the BOMs will be exploded and<br />

displayed. Exploded configuration types will always be shown.<br />

Config. types to show Only the selected PRM configuration types will be shown. For all other<br />

configuration types the structures will not be exploded and shown in a BOM<br />

explosion. See also 3.4.2, Layout Area „Entry / Start Object“.<br />

Usages Depending on the selection, the material BOM usages of the material will be<br />

shown. The following options are available:<br />

► Don’t show usages.<br />

► Mark usages (run time!).<br />

→ If usages exist, they can be indicated in a separate filed, using push<br />

button, or context function „usages". This option is recommended<br />

for screen output list processor.<br />

► Show usage in separate node (run time!).<br />

→ If usages exist, they are shown in a separate node. This option is<br />

recommended for tree output.<br />

► Show usages directly.<br />

→ If usages exist, they will be shown directly. This option is<br />

recommended for file output.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 16/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

Field Function<br />

�<br />

If usages for the output are selected, the field “Usage” will be<br />

activated automatically. Tab „Field selection“, only allows changing<br />

the position of this field. Activating / deactivating is only possible<br />

with the functions described above.<br />

All material usages within the validity range are considered,<br />

independent of the entry object definition (plant and usage).<br />

Show sub position If existing, sub positions will be shown on a separate line.<br />

Output documents If PRM documents exist, they will be output with the material. The<br />

documents can be selected more detailed with the described options<br />

following.<br />

Output object data<br />

package<br />

Load data package<br />

types<br />

PRM data packages which are handled as documents will be output.<br />

Document output only for selected PRM data package types.<br />

Plant / client Output of PRM documents only to selected plants.<br />

� This option is not used for material BOM explosion.<br />

For client specific documents enter the value „=“ (plant empty �<br />

client).<br />

If the selection “Plant / Client” should be made according to the<br />

BOM selection, enter “=S” as selection value.<br />

This option is also valid for data package objects.<br />

Sales Organization Output of PRM documents only for selected sales organizations.<br />

� This option is also valid for data package objects.<br />

Distribution Channel Output of PRM documents only for selected distribution channels.<br />

� This option is also valid for data package objects.<br />

Object types in data<br />

packages<br />

Output of documents only selected PRM object types.<br />

�<br />

If activated, the data package objects will only be shown if an<br />

adequate object exists in the data package.<br />

Object relevance in DP Output of documents only for selected PRM objects relevancies.<br />

Documents with Orig.-<br />

Appl.<br />

�<br />

If activated, the data package objects will only be shown if an<br />

adequate object exists in the data package.<br />

Output of documents only for selected original applications.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 17/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

Field Function<br />

Documents with<br />

language<br />

Output of documents to PRM documents only for selected PRM languages.<br />

�<br />

3.6 Tab „Field Selection“<br />

Definition of output fields and order for determined objects.<br />

� Field selection is part of the layout.<br />

If activated, the data package objects will only be shown if an<br />

adequate object exists in the data package.<br />

Use the value “=” for selection of documents without language<br />

assigned (language empty � none).<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 18/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

Function Description<br />

Heading Field description<br />

Short Description Short explanation of the field (more details below).<br />

Output If activated, the field will be shown in the output.<br />

Only with values If activated, the field will only be shown, if object field values have been<br />

determined (e.g. CAD characteristics).<br />

Field Name Table field name (more details below).<br />

The order of the selected fields can be changed with these push buttons.<br />

Obj.Info Format Information about the object. The format can be selected from a Drop-Down<br />

list:<br />

Document key starting<br />

with number<br />

The following formats are available:<br />

► / ¦<br />

► / ¦<br />

► / ¦<br />

► / ¦<br />

► / ¦<br />

► / <br />

► ¦<br />

3.6.1 Explanations of Fields<br />

�<br />

For more detailed information about the field description, push the -button<br />

of the default help.<br />

The document key will either start with document number or document type.<br />

Not all fields are listed. Only PBL specific fields and fields threated specially in PBL are listet.<br />

Field Explanation / Example<br />

Altitm<br />

ALPOS<br />

Asm<br />

STLKZ<br />

Description<br />

BEZEI<br />

Valid from date<br />

DATUV<br />

Valid to date<br />

DATUB<br />

Inf<br />

OBSTA_ICON<br />

Int. Obj.key<br />

OBJEK<br />

Indicator of an alternative item.<br />

Indicates that an assembly (BOM) to a material is available.<br />

Object description in logon language.<br />

Valid from data for object.<br />

Valid to date for object.<br />

Status icon for object.<br />

Internal <strong>SAP</strong> object key for object, according to object table.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 19/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

Int. Obj.Status<br />

OBSTA_INT<br />

Component Qty.(CUN)<br />

MNGKO<br />

Quantity / Unit (UN)<br />

MNGTXT<br />

Obj.Information<br />

OBJINFTXT<br />

Status<br />

OBSTA_EXT<br />

Object<br />

OBJEK_EXT<br />

Object name<br />

OBJ_TXT<br />

Object type<br />

OBJTY<br />

Org.u.-type<br />

ORGTY<br />

Org.Key.<br />

ORGKY<br />

Originals.<br />

HAS_ORIG<br />

Level<br />

STUFE<br />

Level<br />

STUTXT<br />

Level<br />

BOM_STUFE<br />

Level<br />

BOM_STUTXT<br />

Table<br />

<strong>SAP</strong>OB<br />

Type<br />

OBJ_IM<strong>AG</strong>E<br />

Usag.<br />

US<strong>AG</strong>ES<br />

Counter<br />

LFNUM<br />

Internal object status (language independent).<br />

Relevant for output of language independent document status.<br />

�<br />

Calculates component quantity:<br />

Based on the component quantity and the input quantity.<br />

E.g.: Component quantity (CU) 0,500 * input quantity 10 = 5,000<br />

Calculated component quantity and unit shown in text format.<br />

Example: 5,000 KG<br />

Show information about the object, see above.<br />

Object status, if available in external format and in the logon language.<br />

Object key, e.g. material number, document key<br />

�<br />

Document key will either start with document number or document<br />

type.<br />

Object name<br />

E.g.: material / data package / document / validity / sub position, etc.<br />

Object type:<br />

► Object type<br />

► Daten package type<br />

► Configuration type<br />

Type of organization unit of BOM.<br />

Key for organization unit.<br />

Indicates that document info record of originals exists.<br />

Show level of complete structure (all objects) numerically.<br />

E.g.: 0, 1, 2, 3<br />

Level indicated as text (with dots….) within structure (all objects).<br />

Example: 0, ...1, ..2, …3<br />

Show level of exploded BOM items numerically.<br />

E.g.: 0, 1, 2, 3<br />

Level of BOM items indicated as text (with dots….) within exploded BOM.<br />

Example: 0, ...1, ..2, …3<br />

<strong>SAP</strong> database table name for object to be shown.<br />

Icon / image for object type (material / data package / document / validity /<br />

sub position, etc.).<br />

Mark / show further usage of objects.<br />

Line counter for output.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 20/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

4 Output Processors<br />

The output processor defines how the data, which is read according to the selection, will be displayed.<br />

The field selection defines the columns to be shown.<br />

4.1 Output Processors for Screen Output<br />

The determined data will be shown on the screen. Various functions are available.<br />

Processor / Description<br />

► GUI: PBL ALV Processor<br />

Output will be generated with <strong>SAP</strong> List Viewer (ALV).<br />

Example:<br />

► GUI: PBL List Processor<br />

Output with <strong>SAP</strong> List Display.<br />

Example:<br />

► GUI: PBL Tree Processor<br />

Output in <strong>SAP</strong> Tree Display.<br />

Example:<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 21/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

4.1.1 General Functions<br />

�<br />

Outputs are implemented via <strong>SAP</strong> standard functions. Therefore the standard functions can be<br />

used. Details are provided in the standard help, which can be called up by using the -push<br />

button. (Only available for PBL List Processor und PBL ALV Processor).<br />

In this section only specific functions and fields of <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> are<br />

described.<br />

► A double-click on the object line calls-up <strong>SAP</strong> <strong>PLM</strong> display actions according to the PBL basic<br />

settings. The standard setting calls-up the <strong>SAP</strong> <strong>PLM</strong> object display transaction.<br />

► Using interactive display modes, e.g. tree display, the nodes can be expanded or closed using the<br />

expand and collapse icons ( / ).<br />

4.1.2 Context Menu Functions for Data<br />

Depending on the object type (material, document, etc) general functions are available.<br />

Function Possible<br />

on object<br />

Display Material<br />

Documen<br />

t<br />

Data<br />

package<br />

Change Material<br />

Show<br />

Original<br />

PRM<br />

Workbenc<br />

h<br />

Documen<br />

t<br />

Documen<br />

t<br />

Status log Material<br />

Description<br />

Calls up <strong>SAP</strong> <strong>PLM</strong> display transaction as customized.<br />

Calls up <strong>SAP</strong> <strong>PLM</strong> change transaction as customized for the object.<br />

If existing, document originals will be shown. If more than one document<br />

exists, the required one must be selected from a selection list.<br />

Material Calls up PRM-Workbench for the object.<br />

Documen<br />

t<br />

Data<br />

package<br />

Shows status log for the object.<br />

BOM Material Calls-up <strong>SAP</strong> <strong>PLM</strong> transaction to show BOM.<br />

Change of<br />

cross plant<br />

status<br />

Change of<br />

plant<br />

status<br />

�<br />

BOM display is made with the validity according Valid from Date<br />

on tab Layout / Selection.<br />

Material Enables cross plant material status change. Possible settings according<br />

customizing are listed.<br />

Material Enables plant specific material status change. Possible settings according<br />

customizing are listed.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 22/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

Function Possible<br />

on object<br />

Description<br />

Usages Material A separate dialog will show the materials where used list.<br />

�<br />

Only available if “Usages” was activated on tab “Object Selection”<br />

(see 3.5).<br />

4.2 Output Processors for File Output<br />

The selected data will be written in a file.<br />

�<br />

Format and presentation of data can be configured in detail for each output processor during<br />

customizing.<br />

Processor / Description<br />

► File: PBL PDF Processor<br />

Output results in a PDF File.<br />

Example:<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 23/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

► File: PBL Plain Data File<br />

Output results in a text file with fixed columns. Separation of columns with symbol „|“. No output of the<br />

column title.<br />

Example:<br />

► File: PBL Simple Text File Grid<br />

Output results in a text file. Columns and lines are separated with „text grid“. Columns titles are shown.<br />

Example:<br />

► File: PBL Simple Text File Group<br />

Output results in a text file. Objects are grouped per material. Columns and groups are separated with<br />

the „text grid“. Column titles are shown.<br />

Example:<br />

► File: PBL Simple Text File Header<br />

Output results in a text file. Columns are separated with symbol „|“. Column titles are shown.<br />

Example:<br />

► File: PBL Tab Delimited File<br />

Output results in a text file. Columns are separated with the tabulator character. Column titles are<br />

shown.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 24/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

► File: SEAL Plot Order<br />

Creates a SEAL DVSREPRO Plot Order containing all documents / original files found in the structure.<br />

Details are depending from plot order type used.<br />

4.2.1 General Functions<br />

► After starting the output processor execution the file name and storage location must be entered.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 25/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

5 Client Specific <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong><br />

<strong>DynamicBaseline</strong> Transactions<br />

5.1 Start Transaction Control<br />

In order to define client specific <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> transactions, the transaction<br />

control must be started. Use menu Settings � Define transactions within a <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong><br />

<strong>DynamicBaseline</strong> transaction (e.g. /PRONOVIA/PBL).<br />

In general the idea for setting layouts in a transaction definition is, that either to each layout a<br />

output processor is assigned or that none of the layouts have assigned an output processor,<br />

� but all valid processors are defined in Output processors. A combination of both methods is<br />

possible.<br />

� The transaction control settings are not linked with the <strong>SAP</strong> transport system.<br />

It is not recommended to store definitions for transactions <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong><br />

� <strong>DynamicBaseline</strong> Cockpit (PRONOVIA/PBL) in the transactions control, in order to keep them<br />

as unlimited cockpit and tool for the transaction control.<br />

� Starting the transaction control requires adequate authorization.<br />

5.1.1 Transactions<br />

Definition of client specific <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> transactions, which can then be used<br />

by the user.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 26/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

Field Description<br />

Transaction Code Use delivered transactions /PRONOVIA/PBL1 to /PRONOVIA/PBL19.<br />

Optional, copies of /PRONOVIA/PBLn transactions to client specific<br />

transactions can be used, too.<br />

TrnCtrlFunc Transaction Controller (according customizing currently always<br />

PBL$MAST).<br />

Title Transaction title. Also used by some of the output processors (actual by<br />

all screen processors). Without input the text <strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong><br />

<strong>DynamicBaseline</strong> and the installed product version will be shown.<br />

Change of object<br />

selection not allowed.<br />

Change of field selection<br />

not allowed.<br />

5.1.2 Layouts<br />

If activated, no changes on tab „Object selection“ are allowed.<br />

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

Assignment of one or more layouts including output processors to a transaction.<br />

Field Description<br />

Layout Selectable layouts for these transactions. Without input all possible<br />

layouts can be selected.<br />

�<br />

Layouts must first be generated before they can be assigned.<br />

Only system layouts can be assigned.<br />

Multiple layouts can be assigned.<br />

Output processor If an output processor is entered, only this output processor will be<br />

available for this layout. Therefore no selection of an output processor<br />

will be available for this transaction, and settings under option „output<br />

processors“ will have no influence.<br />

�<br />

The output processor assigned must not be in the list of Output<br />

Processors.<br />

Even if marked as hidden in customizing, a processor can be<br />

used here.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 27/28


<strong>ProNovia</strong> <strong>SAP</strong> <strong>PLM</strong> <strong>DynamicBaseline</strong> V1.1<br />

User Manual<br />

5.1.3 Output Processor<br />

Assignment of possible output processors to the transaction.<br />

Field Description<br />

Output proc. Selectable output processors for this transaction. Without input all<br />

defined processors are available, except hidden processors.<br />

�<br />

If marked as hidden in customizing, a processor can’t be used<br />

here.<br />

<strong>ProNovia</strong> <strong>AG</strong>, P.O. Box, CH-8180 Bülach Version A.032 / 24.06.201110 / Page 28/28

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!