First installation

For first transport and installation (import of the ProBasicLib (UTI)) into SAP,

please refer to the section Transport and Installation.

Further installations

Further installations of ProBasicLib as well the installation of other ProNovia products can afterwards be made using ProNovia's central product management as described in

Importing ProNovia products after first UTI installation.

Integration into standard SAP

The integration into standard SAP is done by the SAPINT layer of ProBasicLib.

See section Integration into Standard SAP.

Setup ProNovia Transactions for SAP GUI for HTML

The ProNovia can be rendered in the SAP HTML GUI.

Transactions based on ProNovia ProFramework (AFW, this includes most ProPLMClient, ProMaterialData, ProProcess, ProDocument and ProConfiguration transactions) must be setup before they can be used in SAP GUI HTML. Please refer to Preparations for SAP GUI HTML.

See Restrictions for SAP GUI for HTML" Known SAP GUI Errors and their Impact on ProNovia Products.

Fiori Components Setup

If ProNovia Fiori componets are used, there are various steps required to activate them.

See section Fiori Components Configuration.

ProNovia Transaction in Fiori Launchpad

The ProNovia S/4HANA product transactions can be integrated into and launched from the Fiori Launchpad.

The options depend on the SAP releases used. Consult the current SAP documentation for your system environment.

As an example, consider the following SAP documentation:

• Direct Integration via Semantic Objects:
  https://www.sap.com/documents/2017/11/780cf362-df7c-0010-82c7-eda71af511fa.html

• Integration via SAP Easy Access Menu in FLP:
  https://www.sap.com/documents/2017/11/e4fbe262-df7c-0010-82c7-eda71af511fa.html

Customer-specific title for tiles

As an example, consider to use the SAP Launchpad Designer, see documentation above.

https://<server>>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html

With the SAP Launchpad Designer, SAP transactions, ProNovia AFW transactions and customer transactions such as MM01, /PCH/BPF1 , ZPLC1 etc. can be defined with customer-specific tile names via catalogues.

Example:
Transaction ZPLC6 , transaction name “ProPLMClient”, tile name in the launchpad ‘ProPLMClient - with cloning”