RH_STRUCTURE_FOR_ORGPUBLISHER to build the datastructure with which an organizational structure can be displayed andpublished using OrgPublisher from TimeVision.Further information
Function module RH_STRUC_GET is used for structure evaluations.
Description
Return structure of BAPI in case of error.
Description
Technical depth of structure.
The number specifies the number of levels of a structure for which anevaluation is to be carried out. If you enter a 3 in this field, forexample, the systerm edites three structure levels from the root objectwhich you selected previously.
Default
You can leave the parameter out. In this case, the evaluation depth isgiven the value 3.
Description
Contains a key which stands for an evaluation path. An evaluation pathenables you to evaluate objects that are part of particularrelationship chains. For example: You want to evaluate objects that arepart of the relationship chain organizational unit > position > person.
If this parameter is transferred, but at the same time, a defaultevaluation path is defined in table T77Scen_AW, the evaluation pathdefined in the parameter is used.
Value range
Evaluation paths are defined in table T77AW.
Default
You can leave this parameter out. In this case, the evaluation pathwhich has been transferred or the default scenario is used.
Description
Key date for evaluation. The results of the BAPI represent a "snapshot"of the organizational plan based on time changes.
Default
You may leave the parameter out. If you do, the current date will beused as the evaluation ley date.
Description
Identification (8-digit number) of the root object for evaluation. Theroot object is defined clearly along with the object type.
Default
This parameter must be transferred for evaluation.
Description
Type of root object transferred for evaluation, 2-character field.
Value range
Possible values: 'O ' for an organizational unit, 'S ' for a position,'C ' for a job. 'P ' for a person, 'US' for a user.
Default
The parameter can be left blank. In this case, the root object isassumed to be an organizational unit ('O ').
Description
Contains a one or two-digit alphanumeric key. Plan version keysdifferentiate between organizational plans.
(PD allows you to maintain several plans in one system in parallel).
Default
The field may be left blank. In this case, the active plan version isused.
Description
Scenarion for retrieving data from an organizational plan, a four-character field.
Value range
Possible entries are specified in table T77Scen_AW.
Default
The above table defines a default evaluation path for each scenario.This evaluation path is used for structure evaluation, as long as noevaluation path has been transferred to the BAPI using the pathIDparameter.
The parameter can be left blank. In this case, the BAPI uses thepredefined scenarion "MDT1", which supports the link betweenOrgPublisher and Manager's Desktop.
Description
Table with agents for workflow tasks.
If the evaluation of the BAPI leads to workflow tasks, this tablecontains their agents.
Value range
The ACTORID field includes a 12-character identification (user name).
Default
This output parameter may be left out.
Description
The evaluation module can provide additional data on objects whichappear in the evaluation by executing Queries. The query that isexecuted for each object type is determined by entries in tableT77ScenQy. In this table, a query is specified for each scenarioand each object type.
The FieldCatalogue table contains the formal description of the datafields that are returned in the FieldData table.Description
The evaluation module can retrieve additional data for all objects thatappear in the evaluation by executing queries. The query that isto be used for each object type is determined by entries in the DBtable T77ScenQy. In this table, a query is specified for eachscenarion and object type.
The FieldData table contains additional data on each object retrievedusing the query.
- The object is identified by the fields PlVar, OType and ObjID.
- SeqNr represents a sequential number for the same object.
- Desc_Index refers to the field description in the FieldCatalog,
- the 255-character VALUE field contains the additional data.
Description
Object data for structure evaluation. Data is written in this table forall objects that appear in this table. The structure contains thefollowing fields:
- PlVar (2-digit charcter field): plan version
- OType (2-digit character field): object type
- ObjID (8-digit numeric character field): Object ID. If the object is an
external object from Organizational Management, which does nothave an 8-digit numeric key (cost center or user, for example), theREALO field is used rather than the ObjID field.
- BegDa: (8-digit date field): start date of object
- EndDa: (8-digit date field): end date of object
- IStat: (character): planning status
- Histo: (character): historical record indicator from database
- Short: (12-character character field): short description
- SText: (40-character character field): object long text
- REALO: (45-character character field): object ID for objects that are
not identified by an 8-digit numeric key (according to OBJID, seeabove).Description
Result of a structure evaluation. The complete structure informationcan be taken from this table according to the evaluation path used.
As this structure is evaluated in the same way as a tree, theinformation comes in the form of "parent-child" nodes. The followingfields exist:
- SeqNo (whole number) pointers PUP, PDOWN, PPREV, and PNEXT refer to
this field.
- Level: (whole number) depth of elements in structure, corresponds to
the "evaluation depth".
- OType (2-character field) type of object in this entry
- ObjID(45-character field) ("enhanced") ID of object in this entry.
- PDown (whole number) SeqNo. of entry, found in the tree underneath the
entry.
- VCount (whole number) number of directly related objects
- Pup (whole number) SeqNo of entry, "parent" of the current entry. Root
of tree is empty.
- PPrev (whole number) SeqNo of the same-level node on the left
- VRSign (character) Specification of relationship of "parent" of current
object to current object ('A' or 'B')
- VRelat (3-character field): Relationship of "parent" to current entry
- VPriox (2-character field): priority of relationship
- VIStat (character): planning status
- VBegDa (8-character field): relationship start date
- VEndDa (8-character field): relationship end date
- VProzt (decimal field with 2 decimal places): relationship weighting
percentage
- SubRC (whole number): return code which is returned when reading the
relationship.
- RFlag (character): indicates recursiveness check
- SBegD (8-character date field): start date
- SEndD (8-character date field): end date
- VSign (character): planning status
- VSeqNr (3-digit character field): number of infotype record, if more
than one date is transferred with the same key.