Additional Functions 

Use

The MIME Repository provides a number of additional functions for editing MIME objects.

Features

Moving Subdirectories and MIME Objects

In the MIME Repository, choose one or several subdirectories or MIME objects and move them to another directory using Drag and Drop. If the subdirectories contain MIME objects, these objects are also moved.

This function is useful if you want to move MIME objects from an application-specific directory to the public directory.

Previewing MIME Objects

●      To preview an object in the MIME Repository, double-click it. Depending on the MIME category, the object is either displayed directly at the bottom of the browser, or the system prompts you to choose a suitable editor.

Choose  with the quick info text Preview to open or close the preview area.

●      To process a MIME object in an external editor, double-click the object in the object list. All changes you have made in the external application are adopted in the SAP system.

Displaying All Versions of MIME Objects

To display all MIME objects that have more than one language version, choose  with the quick info text Display All Versions. All MIME objects for which there is more than one language version are displayed as a subtree.

This scenario is possible only if additional language versions for those MIME objects have been created in the translation system and these versions have been transported to the development system.

Changing the Package Assignment of MIME Objects

In the MIME Repository, choose the object you want to edit and in the context menu, choose Change Package Assignment.

This function is helpful if you save MIME objects initially as local objects ($TMP) and then want to assign them to a package for transport.

Assigning a Transport Request to MIME Objects

In the MIME Repository, select the required directory, subdirectory, or individual MIME object and in the context menu, choose Write Transport Request.

To transport an application directory with all its subdirectories and all the MIME objects in it, select all the nodes of the application directory and all the objects in these nodes and assign them to a transport request.

Setting Expiry Time in Client Cache

Using the expiry time in the client cache, you can control how long a MIME object stays in the cache of the HTTP client - typically a Web browser. Objects that are subject to frequent change should not stay in the client cache long because the client cannot register any change to the object during this time and thus displays the old version. Objects that are seldom or never changed should have a longer expiry time in order to reduce the grid load and increase performance.

You can define the expiry time of a MIME object in the MIME Repository. In the context menu of a node, choose Additional Functions ® Expiry Time Client Cache.

You can specify the expiry time for a folder and then copy it to all the subnodes (folders and MIME objects). To assign an expiry time that is different from the time in the higher-level folder, you can set the indicator for the "individual expiry time". For such nodes (and their subnodes), the expiry time is not influenced by setting the indicator for a higher-level folder.

If the indicator "Expiry Time" is not active, then implicit expiry applies - that is, the client queries (if settings are made accordingly) the server at each access whether the object is still current.

The Overview Subtree pushbutton displays the expiry time of the subtree below the selected node. If you increase the expiry time, you need to take care of the subnodes with individual expiry time.

When folders or MIME objects with individual expiry time are transported, the expiry time is copied into the target system. In the case of folders, it is copied to the subnodes in the target system. For nodes without an individual expiry time, the expiry time of the higher-level folders is copied into the target system upon import into that system.