Hierarchy

⤷

⤷

Basic Data
Data Element | RERAOPISVALIDCOACC |
Short Description | Posting Activity Valid for COA Company Code |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RECABOOL | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
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 | COA CoCd |
Medium | 15 | COA CoCd |
Long | 30 | COA Company Code |
Heading | 10 | COA CoCd |
Documentation
Use
- Indicator is set (
'X'
)The posting activity can be started from a mandate company code (COA mandate) (see company code type).
- Indicator is not set (
' '
)It is not possible to start the posting activity from a mandate company code (COA mandate).
If you use COA management, then you normally define a few special posting activities for COA management. You should set this indicator for these posting activities so that they can be started from the mandate company code.
Usually postings that are made in the COA company code, and therefore have to be entered in parallel in the related manager company code or the condominium owner company code, are also started from the COA company code.
Use
Dependencies
Example
For postings related to COA management, you could define posting activities for each service charge key. The system can then in most cases derive the given settlement unit from the posting activity and the company code.
History
Last changed by/on | SAP | 20050219 |
SAP Release Created in | 600 |