Show TOC

 Managing of Documents for Layout Definitions Locate this document in the navigation structure

Use

To use your own layout for browser-based PI sheets and process manufacturing cockpits , you must create and manage a number of different files in the SAP system. For the system to be able to access the right XSL style sheet and other files while creating the PI sheet or cockpit, these files must be stored centrally in the SAP system.

In the same way, all generated XML documents are stored in the SAP system until the corresponding process orders or cockpits from Customizing are deleted.

You can store your documents for document management purposes as follows in the SAP system:

In the Business Document Service (BDS)

If you are using the SAP Release 4.6C, you should manage your documents in BDS if you define your own stylesheets.

In the Web Repository

The Web Repository should be used in the following situations:

Release 4.6C as of SP45

Release 4.6C and lower Support Package than SP45 but with Note 481463 in the system and Internet Explorer 6.0

Releases higher than 4.6C (especially if they work with Unicode).

Features

Business Document Service (BDS)

Initial Screen

You can find the initial screen for the Business Document Navigator in the SAP Menu by choosing ToolsBusiness DocumentsMiscellaneousBusiness Documents . On the Business Document Navigator selection screen, you must enter a class name and class type to get to the detail screen containing the documents.

Structure

The BDS is structured hierarchically. The first level contains classes and the second level contains object keys (or object IDs ). You can use the object keys to create your own directories with any names you like in the BDS.

The files for PI sheets and cockpits are stored in the classes POC_TEMPLATE and POC_PIDOC. They are assigned to class type OT. The object key SAP is below the class POC_TEMPLATE. Here, you can find the templates for style sheets. Below the object key, you can find the documents.

Class POC_TEMPLATE

Store all documents that serve as master data (such as your own XSL files, CSS files, GIF files, and so on) in this class.Versions can be created for these documents and they can have different language variants. You can also find the following templates under the object key "SAP":

Standard XSL style sheets

- For manufacturing cockpits: "PMC_STY_C_DEFAULTX.XSL" - For PI sheets: "PMC_STY_DEFAULTX.XSL" - For the archiving of PI sheets: "PMC_STY_A_DEFAULTX.XSL"

Standard CSS style sheets

For PI sheets and process manufacturing cockpits and for the archiving of PI sheets Screen layout: "PMC_STY_DEFAULTS.CSS" Print layout: "PMC_STY_DEFAULTP.CSS"

Standard JavaScript files

For PI sheets and process manufacturing cockpits "PMC_STY_DEFAULTFC.JS"

This graphic is explained in the accompanying text.

Changes you make to the above-mentioned files do not have any effects since they only serve as templates to define your own XSL style sheets. The original files are loaded from the Web Repository.

Class POC_PIDOC

All documents that serve as transactional data (such as XML files that are automatically created for a PI sheet or cockpit) are stored here.

Class SAP_ICONS

This class contains icons that are used in the standard SAP system. You can copy them and use them for your style sheets. The icons used in the standard style sheets, are stored in the Web Repository only (see below).

URL convention

You must adhere to the following URL convention when naming references to documents that are stored in the BDS:

SAPR3-BDS-<class name>-<class type>-<object ID>-<file name>-<version number>-<variant number>  ( ) SAPR3-BDS-POC_TEMPLATE-OT-MYDOC-MYTEST.DOC SAPR3-BDS-POC_TEMPLATE-OT-MYDOC-MYTEST2.HTML-31-3 (version 31, variant 3) Version number and variant number are optional. If you do not specify a version number, the system automatically uses the latest version.

 ( ) Note that files names are case-sensitive.

Transferring standard files from the SAP Reference Client

Since the BDS is client-specific, the standard files mentioned above are usually only available in the SAP Reference Client. To copy the files from the SAP Reference Client to your logon client, you must run the report RCOPOC_SAP_LAYOUT_CLIENT_COPY (see Note 312275).

Web Repository

Initial Screen

You can find the initial screen for the Web Repository in the SAP Menu under Tools -> Web DevelopmentWeb Repository . On the initial screen, you must select the Web object type. The Object selection screen appears. You must specify a development class.

Structure

The Web Repository is structured according to development classes. All original files that are accessed when the standard layouts for PI sheets and cockpits are used are stored as follows in the Web Repository:

Web object: binary data for WebRFC applications

Development class: CMX_POC (as of Release Enterprise 4.70 Extension 1.10) and

Development class: CMX_BFW (as of Release Enterprise 4.70 Extension 1.10)

The GIF files to which the standard style sheets refer only exist in the Web Repository.

You can use the original files stored here as copying templates.

URL convention

You must adhere to the following URL convention when naming references to documents that are stored in the Web Repository:

SAPR3-WR-<file name>  ( ) SAPR3-WR-MYTEST.GIF

This graphic is explained in the accompanying text.

You can use standard files from both the Web Repository and the Business Document Service as templates. Just make sure that the paths for the references in your style sheets are always adjusted to the appropriate location where your document is stored.

For a list of all files that you can use for PI sheets and cockpits and how they are related to each other hierarchically, see Standard Files as Templates for Styelsheet Definitions .