Ansicht
Dokumentation

/EHR/SOL71_ORGPUB - OrgPublisher for SAP solutions

/EHR/SOL71_ORGPUB - OrgPublisher for SAP solutions

General Data in Customer Master   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

OrgPublisher(TM) for SAP® solutions - OrgPublisher(TM) is a trademark of TimeVision, Inc. in the United States and other countries. SAP® is a registered trademark of SAP AG. The trademarks, logos, and service marks not owned by TimeVision, Inc. and that are displayed in this document are the registered and unregistered marks of their respective owners.

Purpose

The report extracts the objects along an defined evaluation path. It converts the extracted data into a CSV- or XML file that TimeVision´s OrgPublisher can read.

The relevant data objects has to be defined in the customizing tables. A corresponding configuraion is described with the parameter output format (customizing tables).

The download file can be saved on a local workstation or down on a SAP application server or temporarily into TemSe.

Within the tab "Options" you can define to start the OrgPublisher application directly after download (automatically). Prerequisites are saving the file on the local workstation and maintaining the field that refers to the location of the OrgPublisher application.

Data that has been stored can also be (before reaching the expiry date) transfered to the local workstation or application server without starting the extraction again by using "Read from TemSe"

Parameters

Objects

With Plan version, Object type and Object ID you determine the root object for the evaluation path. This object ist the top of the hierarchy of objects, which is given to the OrgPublisher for Charting. Only one object can be entered here.

The root object can be searched via the field search term.

The evalution path is defined in the output format and can't be changed here.

Output

The output format is defined in the own customizing tables for the OrgPublisher for SAP solutions. It defines which objects are read and how the data are extracted (infotypes, fields, special functions).

As output a text or XML format are possible. Textformats are better suitable for calling the OrgPublisher directly.

The data for the OrgPublisher can be written to:

  • the local workstation (not possible if the programs runs in background)
  • to the filesystem of the SAP application server
  • into the TemSe ( = temporary sequential objects)

Input

Nomally the data are read via evalution path from objects and infotypes (Analyse OM object data). Here the maximum numbers of hierarchies can be limited.

Or the stored data in the TemSe can be read.

Options

The OrgPublisher program can be called with the extracted data as input.

With "Show custom fields for all position types" the fields are displayed in the OrgPublisher Chart, if the field was defined with "Display" in the output format. This is valid for custom fields, e.g. fields with column number > 19.

For storing data into TemSe you need the number of days, how long the object in the TemSe should not be reorganized.

Text data can be searched for all languages like defined in SAP standard table T778L or only for one language.






General Data in Customer Master   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 3510 Date: 20240427 Time: 003715     sap01-206 ( 63 ms )