Integration and Enhancement pro ovia - ProNovia AG

ProNovia SAP PLM PRM DynamicBaseline 

pro ovia 

Product Lifecycle Management 

ProNovia AG, P.O. Box, CH-8180 Bülach 

Integration and Enhancement

ProNovia SAP PLM PRM DynamicBaseline V1.2 

Integration and Enhancement 

Document Information 

Intended for 

■ SAP PLM consultants 

■ SAP Basis administrators 

■ ABAP developers 

Validity 

Version / date of issue A.03 / 24.06.2011 

This version replaces all former versions. 

Valid until Release of a new version. 

General 

ProNovia SAP PLM Product ProNovia SAP PLM PRM DynamicBaseline 

Product-Version V1.2 

Classification 

Document Type ProNovia SAP PLM Products – Documentation 

Document classification No classification 

Creation / Release 

Author of document Christian Gradolf / Frauke Böni 

Release of document Christian Gradolf 

Filing 

Electronically According ProNovia Guideline: ProNovia Documents 

Physically No filing 

Version History Initiator / Reason of Change 

A.00 First English edition for product version V1.0 

A.01 Corrections. 

A.02 Issue for product version V1.1 

A.03 Issue for product version V1.2 

Copyright Remarks 

Copyright ProNovia AG 2009-2011. All rights preserved. Subject to change. 

■ Microsoft is a registered trademark of Microsoft Corporation. 

■ SAP and SAP.com is a registered trademark of SAP AG. 

■ ProNovia is a registered trademark of ProNovia AG. 

ProNovia AG, P.O. Box, CH-8180 Bülach Version A.03 / 24.06.2011 / Page 2/11



Table of Content 

1 Introduction ........................................................................................ 4 

1.1 Document Content ....................................................................................................... 4 

1.2 Additional Documents .................................................................................................. 4 

1.3 Requirements .............................................................................................................. 4 

1.4 Abbreviations / Other ProNovia SAP PLM Products ................................................... 4 

1.5 Document Symbols ...................................................................................................... 4 

2 After the Installation .......................................................................... 5 

3 Authorizations .................................................................................... 6 

3.1 Running PBL Transactions .......................................................................................... 6 

3.2 Configuring PBL Transactions ..................................................................................... 6 

3.3 PBL Layouts ................................................................................................................ 6 

4 PBL Functions .................................................................................... 7 

5 Individual Output processors ........................................................... 8 

6 PDF Output Processor ...................................................................... 9 

6.1 SmartForms ................................................................................................................. 9 

6.2 SAPscript ..................................................................................................................... 9 

7 Enhancements ................................................................................. 10 

7.1 Save / Restore own parameters in layout ..................................................................11 




1 Introduction 

1.1 Document Content 

This document describes the integrated authorization management, the programming interfaces and 

the enhancement of the ProNovia SAP PLM PRM DynamicBaseline with individual output processors 

and BusinessAddIns. 

1.2 Additional Documents 

All relevant and available documents for the ProNovia SAP PLM PRM DynamicBaseline can be found 

on the ProNovia homepage (www.pronovia.com � Quick Links -> Downloads). 

About using ProNovia SAP PLM PRM DynamicBaseline please refer to the User Manual. The 

customizing is described in the Customizing Manual. 

1.3 Requirements 

ProNovia SAP PLM PRM DynamicBaseline has to be installed and set-up correctly on your system. 

To import transport orders into SAP R/3 System, the required authorizations are necessary. 

To run ProNovia SAP PLM PRM DynamicBaseline the user must have the required transaction 

authorizations. 

1.4 Abbreviations / Other ProNovia SAP PLM Products 

In this document the following abbreviations are used for other ProNovia SAP PLM products. Some 

products are optional and may not be installed on your system. 

► PBL ProNovia SAP PLM PRM DynamicBaseline 

► PRM ProNovia SAP PLM ProcessManager (Workbench und Navigator) 

The document ProNovia SAP PLM Solutions and Products gives an overview over all available 

ProNovia products. 

All documents can be downloaded from the ProNovia homepage (www.pronovia.com � Quick Links 

� Downloads). 

1.5 Document Symbols 

In this document the following symbols are being used: 

� 

Important or critical hint, to pay special attention to. 

� Additional information. 

� 

� 

BusinessAddIns (BAdi) are available. 

Function protected by SAP authorization. 




2 After the Installation 

If running ProNovia SAP PLM PRM DynamicBaseline for the first time after installation, a default 

customizing is made by PBL. With this customizing, the default functionality provided by PBL can be 

used. 

Without any setup, only the main transaction /PRONOVIA/PBL can be used. Other PBL transactions 

must be configured, using the function Settings � Setup Transactions within the main transaction. 

See ProNovia SAP PLM PRM DynamicBaseline User Manual for how to configure PBL transactions. 




3 Authorizations 

The descriptions of the authorization objects and their use within ProNovia SAP PLM PRM 

DynamicBaseline are listed below. 

� 

Authorization objects in SAP R/3 cannot be created in the /PRONOVIA/ namespace. Therefore 

the ProNovia authorization objects are in the customer namespace Z*. 

3.1 Running PBL Transactions 

To run the ProNovia SAP PLM PRM DynamicBaseline transactions, a user requires authority to 

execute those transaction codes. The usage of the PBL transaction codes depends on the setup (see 

above 2, After the Installation). 

The PBL transaction codes: 

► /PRONOVIA/PBL PBL main transaction 

► /PRONOVIA/PBL1 



► … 


3.2 Configuring PBL Transactions 

To use the function Settings � Setup Transactions in the main transaction, authorizations are 

required. See ProNovia SAP PLM PRM DynamicBaseline User Manual for how to configure PBL 

transactions. 

The authorization object Z_PRON_PBL controls the authorization for configuring PBL transactions. 

BEGRU ACTVT Description 

TCTR 70 Required to configure PBL transactions. 

3.3 PBL Layouts 

ProNovia SAP PLM PRM DynamicBaseline allows saving layouts. These layouts can either be for 

personal use or for system wide use. Everyone can save or delete personal layouts (no special 

authorization required). 

The authorization object Z_PRON_PBL controls the authorization for saving and maintaining system 

layouts or layouts from other users. 

BEGRU ACTVT Description 

LAY 36 System layouts can be created, but only 

own layouts (personal or system) can be 

overwritten and deleted. 

70 

System layouts can be created and any 

system layout can be overwritten or 

deleted, even if created by other users. 




4 PBL Functions 

ProNovia SAP PLM PRM DynamicBaseline can either be used by its transaction codes or by direct 

integration in customer code using the provided PBL function modules. For information about 

parameters, see description of the function modules. 

Function Module Description 

Main 

/PRONOVIA/PBL_START_MAST Without any parameters, this function runs as the main 

transaction /PRONOVIA/PBL, calling the selection 

screen, reading the data and calling an output 

processor. 

By using the parameters, specific behavior can be 

programmed. 

Selection Screen 

/PRONOVIA/PBL_SELDIALOG_MAST Processes the PBL MAST selection dialog. 

Reading and collecting data 

/PRONOVIA/PBL_SELECT_DATA Reads data according the selection. 

/PRONOVIA/PBL_COLLECT_OBJECT If reading the data is made by an external program or if 

additional data is read using a corresponding PBL 

BusinessAddIn, use this function to collect the data in 

the object table. 

/PRONOVIA/PBL_GET_BOM_DATA Returns the current BOM data, when exploding BOM 

and collecting data. To be used in the BADI’s to read 

own data. 

Output processors 

/PRONOVIA/PBL_OPC_ALV Output processor for ALV Grid output. Supporting 

subscreen or full screen output. 

/PRONOVIA/PBL_OPC_LIS Simple ABAP list output processor. Supporting 


/PRONOVIA/PBL_OPC_PDF PDF output processor using a SAPscript form. Only file 

output supported. 

/PRONOVIA/PBL_OPC_PLOT Output processor to create SEAL plot jobs. Only 

available if the according SEAL software is installed. 

/PRONOVIA/PBL_OPC_TREE Output processor for a tree display. Supporting 


/PRONOVIA/PBL_OPC_TXT Output processor for various text outputs according the 

output processor definition. Only file output supported. 

Service functions 

/PRONOVIA/PBL_BUILD_ALV_FCAT Create default ALV field catalogue, either in the 

SLIS_T_FIELDCAT_ALV or the LVC_T_FCAT format. 

/PRONOVIA/PBL_CALL_OBJECT_DLG Calls the object dialog (on line double click) as defined in 

basic customizing. 

/PRONOVIA/PBL_CTX_MENU_BUILD Build PBL default context menu. 

/PRONOVIA/PBL_CTX_MENU_EXECUTE Executes default context menu commands. 

/PRONOVIA/PBL_OPC_HTML_HEADER Creates default PBL header lines for HTML output (e.g. 

for ALV Grid). 

/PRONOVIA/PBL_OPC_LIST_HEADER Creates default PBL header lines for ABAP list output. 




5 Individual Output processors 

If the provided PBL output processors are not sufficient, own output processors can be implemented. 

Own output processors must be implemented as function modules in the customer name space and 

be registered in the customizing. Best is to copy one of the provided PBL output processors and then 

adapting the code. 

Important data in the control structure PSX_EXE_INFO: 

► OBJ_DATA: all data read for the selection (according OBJ_SEL). 

► FLD_SEL: the selected fields in their requested order for output. 




6 PDF Output Processor 

The PDF output processor requires a SmartForm or a SAPscript form, defining the layout of the PDF 

output. The required parameters depend on the used type of form. If the parameter SMART_FORM is 

present, output will be made using SmartForms else using SAPscript elements. 

See customizing manual for the parameters. 

6.1 SmartForms 

The data for the SmartForm form is provided by following parameters: 

► PS_HEADER Selection and header data, based on structure /PRONOVIA/PBL_IO. 

► PT_OBJ_DATA Table with data for each single object line, based on structure 

/PRONOVIA/PBL_OBJ_DATA. 

6.2 SAPscript 

Table type: /PRONOVIA/PBL_OBJ_DATA_TAB. 

The data for the SAPscript form is provided to the form processer using following structures: 

► GS_PBL_IO Selection and header data, based on structure /PRONOVIA/PBL_IO. 

► GS_OBJ_DATA Data for each single object line, based on structure 

/PRONOVIA/PBL_OBJ_DATA. 




7 Enhancements 

On various points ProNovia SAP PLM PRM DynamicBaseline can be enhanced using 

BusinessAddIns (BAdi’s). 

� 

To implement and activate BAdi’s a user requires development authorizations and must be a 

registered developer. ABAP workbench know how is required. 

BAdi’s must be activated using the BAdi-Builder (transaction SE19). If available use the option Classic 

BAdi (SAP ERP systems). Any implementation name can be used, but must follow the SAP rules for 

client name spaces (see SAP documentation BC – name spaces and name conventions). 

The definition name to use is /PRONOVIA/PBL. 

After implementing, the code can be edited using the Object Navigator (transaction SE80). 

Parameters and exceptions of the method can be shown by clicking on the push button Signature: 

List of available extensions: 

Method / Fcode Usage / Description 

Transaction control 

FILL_TRANSACTION_CONTROL Filling the transaction control data for one transaction. 

LAYOUT_PARA_SAVE Save own screen parameters in layout. For more information see 

below 7.1, Save / Restore own parameters in layout. 

LAYOUT_PARA_RESTORE Restore own parameters in layout. For more information see 

below 7.1, Save / Restore own parameters in layout. 

Selection 

BEFORE_SELECTION_SCREEN Before execution PBL selection screen. Allows to enable 

customer specific tabulators by filling the E_CUST_TAB* 

parameters. 

SELECTION_SCREEN_PBO Process Before Output event in selection screen. 

SELECTION_SCREEN_PAI Process After Input event in selection screen. 

AFTER_SELECTION_SCREEN After PBL selection screen. 

Name in the client name 

space 

Generated name of 

implemented class 




Method / Fcode Usage / Description 

Reading data 

BEFORE_READING_DATA Before reading data. Allows to read data by own code. 

COLLECT_DATA_BEFORE_APPEND Collecting data for one object, just before appending. Allows 

altering or completing data. 

COLLECT_DATA_AFTER_APPEND Collecting data for one object, just after appending. Allows adding 

additional child records for current object. 

AFTER_READING_DATA After reading all data. 

Output processing 

BUILD_ALV_FCAT Building the default ALV field catalog. 

BUILD_HTML_HEADER Building the header for ALV grid. 

BUILD_LIST_HEADER Building the header for list output. 

CTX_MENU_BUILD Building the default PBL context menu. 

CTX_MENU_EXEC Executing a context menu command. 

CALL_OBJECT_DIALOG Calling default dialog for one object (line double clicking). 

SETUP_HEADER_DATA Allows to alternate data or fill append fields in de header structure 

/PRONOVIA/PBL_IO for the output processors ALV, TREE and 

PDF. 

Use I_EXE_INFO-OUTPUT_PROCESSOR-OPCID (or I_EXE- 

_INFO-OUTPUT_PROCESSOR-FUNC_NAME) to check output 

type. 

Constants see attributes in class /PRONOVIA/CL_PBL_DEF. 

7.1 Save / Restore own parameters in layout 

To save own parameters in the layout use the function /PRONOVIA/PBL_LYD_SAVE_SELOPT with 

the pf_paramter for a single parameter or the table pt_sel_option for a selection range. 

To restore own parameter in the layout use the function /PRONOVIA/PBL_LYD_FILL_SELOPT with 

pfx_parameter for a single parameter or the table ptx_sel_option for a selection range. 

All custom parameters must follow the naming convention: Z.

Integration and Enhancement pro ovia - ProNovia AG

Create successful ePaper yourself

Delete template?

Save as template?