SAP ABAP Data Element OPAREA (Operational area)
Hierarchy
☛
IS-UT (Software Component) SAP Utilities/Telecommunication
⤷ IS-U-IDE (Application Component) Intercompany Data Exchange
⤷ EECC_EDI (Package) IS-U: Deregulation
⤷ IS-U-IDE (Application Component) Intercompany Data Exchange
⤷ EECC_EDI (Package) IS-U: Deregulation
Basic Data
Data Element | OPAREA |
Short Description | Operational area |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | OPAREA | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table | EOPAREA |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Op. area |
Medium | 15 | Op. area |
Long | 20 | Operational area |
Heading | 5 | OA |
Documentation
Definition
An operational area runs according to uniform rules and standards for communication. Generally, an operational area has one distributor.
Execptions occur when different communication rules are used in the same operational area. For example, if a distribution company operates in different geographical areas (as is the case in different US states) a number of different regulations may apply in the distribution grid.
There may also be different communication standards for residential and nonresidential customers in the same distribution grid. In this case, you must create more than one operational area.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 462 |