Force Element
Definition
The enhancement of the object type
organizational unit
in the
Organizational Management
component. It enables
organizational elements of armed forces, police, and aid organizations to be mapped, together with their specific properties and relationships.
The force element enhances the object type
organizational unit
in particular with properties and usage options in the
Logistics
area, thereby enabling organizational structures to be integrated for planning and controlling administrative, HR, and logistics processes.
Use
Use this object to:
Map organizational elements (divisions, units, and so on), together with their properties, such as:
Mission (assignment of tasks and/or documents)
Names, classifications, and descriptions
Functional responsibilities such as for supplying or providing specific services for other organizational elements
Addresses, geolocations, and geocoordinates
Inclusion in logistics structures (assignment to plant, MRP areas, and so on)
Inclusion in Accounting and Funds Management (assignment to cost centers, WBS elements, real estate contracts, and so on)
Assignments to technical objects and logistics/responsible work centers
Map and plan the equipment of your organization in terms of personnel, material, and infrastructure at the level of the organizational elements
Map the organizational structures of your organization, that is, the hierarchical or functional relationships between the organizational elements
Force elements used in this way enable you to control in the SAP system processes in different business areas (organization, personnel, material, maintenance, and so on) on the basis of the properties, tasks, and equipment of organizational elements, or across organizational structures.
Structure
Organizational unit
The technical basis of a force element is an object of the type
organizational unit
. The enhancement of an organizational unit for a force element is stored in
table /ISDFPS/FORCE.
Field |
Meaning |
Use |
|---|---|---|
FORCE_ID |
Internal key of the force element |
Identification of the force element |
FORCE_CNT |
Internal version counter |
|
PLVAR |
Plan version (organizational unit) |
Assignment of the force element to an organizational unit |
OTYPE |
Object type (organizational unit) |
|
OBJID |
Object ID (organizational unit) |
When a force element is created and edited in the
Structures Workbench
, the system automatically creates an organizational unit or edits the underlying organizational unit. Relationships between a force element and other objects are created on the basis of the organizational unit that underlies the force element in question.
Force elements are always created in the active plan version.
Status and Validity
Force elements have their own status and a validity period. A force element can have the following
statuses from status management in
Organizational Management
:
Planned
,
Requested
,
Approved
,
Active
,
Obsolete
, and
Rejected
. See also
Status Networks
.
Properties and relationships
The properties and relationships of force elements are displayed and edited in the
structural displays and on the
tab pages in the
Structures Workbench
. For an overview of all of the tab pages available, see the following documentation.
The following properties and assignments of the force element are stored in table /ISDFPS/FORCE:
Field |
Meaning |
Tab Page |
|---|---|---|
WERKS_S |
Plant (Stock) |
|
BERID_S |
MRP Area (Stock) |
|
ACNTABLE_S |
Accountable (Stock) |
|
LGORTACNT |
Storage Location (Stock) |
|
WERKS_P |
Plant (Provisions) |
|
BERID_P |
MRP Area (Provisions) |
|
ACNTABLE_P |
Stockpiling (Provisions) |
|
WERKS_RE |
Plant (Infrastructure) |
|
BERID_RE |
MRP Area (Infrastructure) |
|
ACNTABLE_RE |
Accountable (Infrastructure) |
|
LGORT_RE |
Storage Location (Infrastructure) |
|
PSPNR |
WBS Element |
|
READINESS_MAT |
Level of Readiness (Material) |
|
READINESS_PERS |
Level of Readiness (Personnel) |
|
READINESS_TRAI |
Level of Readiness (Training) |
|
EKORG |
Purchasing Organization |
|
EKGRP |
Purchasing Group |
|
LOGLEV |
Logistical Level |
|
PRIO |
Organizational Priority |
|
MATSTAT |
Initial Supply Status |
Furthermore, the table contains administrative data about the force element (date of creation, last changed by, and so on).
You can define your own fields for this table without any need for extra modifications. To do so, use the include CI_FORCE.
The following properties and assignments are stored by means of infotypes:
The properties and relationships of a force element that can be covered by the object type
organizational unit
and that are not specific to armed forces, police, and aid organizations are stored in the force element’s standard
infotypes in Organizational Management. These include:
Infotype 1000 (Object)
Infotype 1001 (Relationships)
Infotype 1002 (Description)
Infotype 1008 (Acct. Assignment Features)
Infotype 1018 (Cost Distribution)
Infotype 1019 (Quota Planning)
Force-element-specific object properties and relationships are mainly stored in component-specific infotypes for the force element:
Infotype 1950 (Properties)
Infotype 1951 (Classification)
Infotype 1952 (Stationing)
Infotype 1953 (Service Offer)
Infotype 1954 (Service Provider)
Infotype 1955 (Cmd and Control Relatshps)
Infotype 1956 (Operation/Exercise)
Infotype 1980 (Relocation)
Infotype 1981 (Assgmt Relocation - Matl)
Infotype 1982 (Assgmt Relocation – Pers.)
Infotype 1984 (Logical System)
Infotype 1985 (Op./Ex. Relationships)
Infotype 1986 (Structure Information)
Infotype 1988 (Operational Weighting)
A logical system is assigned to a force element at a point in time as an operational system .
Assignments of objects that are not stored by means of infotypes are stored in the FORCER framework tables.
Some properties (assigned information) are stored in special management systems. These include:
Business Address Services (BAS)
Document Management
For information about editing force elements, see Editing Force Elements .
Integration
In addition to integration with objects of the type
organizational unit
, assignments can exist for the following objects:
Force elements can be:
Linked to one another for organizational structures
Linked to the following objects for resource planning purposes:
Positions for mapping the authorized personnel
Material planning objects or material containers for mapping the authorized materials
Equipment packages for mapping required material combinations
Provisions packages for mapping the logistical requirements
Infrastructure planning objects for mapping the authorized infrastructure
Included in logistics structures (plant, MRP areas, storage locations, and so on); see also Stock/Provisions and Logistics Data
Linked to maintenance objects (master equipment and responsible work centers); see also Technical Objects and Assignments to Maintenance Objects
Linked to objects from
Flexible Real Estate Management
(
Real Estate Contracts
,
Business Entities
).
Linked with jobs , tasks , account assignment objects , and documents
Described by reference force elements
Assigned to relocations