Simplify SAP R/3 development with Excel VBA/VB RFC  
Home> Bapi>OrgUnitExtended




The business object Organizational plan unit is an
organizational unit that represents a division of the enterprise that
is defined according to its responsibility for fulfilling specific work related tasks at the enterprise.


Organizational plan units are structurally integrated within an
assignment hierarchy and interlinked through a reporting hierarchy. In
this way, a department, for example, can belong to a central department but still report to the executive board.

The manner in which organizational plan units are defined and linked determines the form of the organizational plan, such as a line
organizational structure or matrix organization.


An organizational plan unit contains several positions and is managed by a position.

An organizational plan unit can be assigned a company code to which the
values of the organizational plan unit that are relevant to financial
accounting are allocated. An organizational plan unit can also be assigned a business area if financial accounting is performed for
business areas.
It is also possible to determine the portions of the personnel costs of
the organizational plan unit that are allocated to a cost center, and the cost centers to which they are allocated.

An organizational plan unit can be assigned a personnel subarea and an
employee subgroup. In this case, the human resource provisions specified for this subarea/subgroup are valid for the organizational
plan unit.



Available Methods

  • DataGet : Extract data on organizational structure [ BAPI_ORGUNITEXT_DATA_GET ]
  • GetDetailedList : Object List With Detailed Information [ BAPI_PDOTYPES_GETDETAILEDLIST ]




Using this BAPI, you can execute structure evaluations and dataretrieval for organizational units and related objects. Starting from aroot object, with plan version PlVar, object type OType and root objectID ObjID, an evaluation is executed for key date KeyDate. The evaluation path used is determined either directly using the EvalPath
parameter or - if this is empty - the "Scenario" scenario and acorresponding entry in the data base table T77Scen_AW. The evaluationdepth (that is, how many levels of the tree starting from the root object are to be evaluated) is determined using the EvalDepth

If there is no evaluation path for the scenario in customer tableT77Scen_AW, a search of the entries in the SAP table T77Scen_AW_Syst takes place.

For more information on the output parameters, see the documentation.

You can specify various ABAP Queries which read and return additional
data from the R/3 data set, for all hit objects for an evaluation perscenario. These are determined per object type and scenario in table T77ScenQy.

If no entry for the object and scenario is found in customer tableT77ScenQy, a serch of the entries in SAP table T77ScenQy_Syst takes
place. If NO query is to be carried out for the object, eventhoughthere is a corresponding entry in SAP table T77ScenQy_Syst, an empty entry (or no entry) is to be made in T77ScenQy.

The function module that this BAPI is based on is also used by the function module RH_STRUCTURE_FOR_ORGPUBLISHER
to build the data structure 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.




This function module is used as the basis for the BAPI-method

This method reads the parameter that you have given to an object typeand delivers an object list which accords to the input parameters.

If you have not defined a parameter for the method, the object list
will be created according to the following criteria:

Plan version -> Active plan version
Start date -> 01.01.1990
End date -> 31.12.9999
Planning status -> 1 = active
Language -> Logon language


If you want to save all active objects which will exist in the year
2000, select the following parameter:

Start date -> 01.01.2000
End date -> 31.12.2000


You need structural authorizatoin for the HR object type.

The 'OBJECTTYPE' parameter will be determined by the BOR objects which
are called up.

Notification will be given in the 'RETURN' parameter. You will find

the return values and their meanings in this parameter documentation.