SAP ABAP Data Element REBDVACFORCEACC (Generate Follow-Up Postings for Retroactive Changes?)
Hierarchy
☛
EA-FIN (Software Component) EA-FIN
⤷ RE-FX-BD (Application Component) Basic Data
⤷ RE_BD_OC (Package) RE: Occupancy (Occupancy History and Vacancy Reason)
⤷ RE-FX-BD (Application Component) Basic Data
⤷ RE_BD_OC (Package) RE: Occupancy (Occupancy History and Vacancy Reason)
Basic Data
Data Element | REBDVACFORCEACC |
Short Description | Generate Follow-Up Postings for Retroactive Changes? |
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 | FollPost. |
Medium | 15 | FollPost.f.Chg |
Long | 20 | FollPost. at Change |
Heading | 10 | FollPost. |
Documentation
Definition
When changes are made to a rental object or contract and these changes affect time periods for which postings already exist, then follow-up postings can be created. However, follow-up postings are only possible when the account assignment changes. Changing the account determination does not lead to follow-up postings. See the settings in the Vacancy Account Assignment field.
Use
Decide if you want postings to be changed retroactively.
- Indicator is set (
'X'
)The posting term can be changed retroactively.
- Indicator is not set (
' '
)The posting term is not changed retroactively.
Dependencies
Example
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in | 500 |