SAP ABAP Data Element RERAHASPARTNERBLOCK (Locking Partner Data in Posting Term Possible)
Hierarchy
☛
EA-FIN (Software Component) EA-FIN
⤷ RE-FX-RA (Application Component) Rental Accounting
⤷ RE_RA_CA (Package) RE: Cross Application Rental Accounting
⤷ RE-FX-RA (Application Component) Rental Accounting
⤷ RE_RA_CA (Package) RE: Cross Application Rental Accounting
Basic Data
Data Element | RERAHASPARTNERBLOCK |
Short Description | Locking Partner Data in Posting Term Possible |
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 | HASPARTNERBLOCK | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Prtnr Lock |
Medium | 15 | Partner Lock |
Long | 20 | Partner Lock |
Heading | 10 | Prtnr Lock |
Documentation
Definition
Controls, at company code level, if it is possible to lock the partner and the partner-relevant data in a posting term. This is necessary, for instance, for a tenant changeover, where a new main contractual partner takes over the contract and all rights and duties of the old main contractual partner.
Use
- Indicator is set (
'X'
)
When you create a new time slot for a posting term that contains a new partner, you can lock all prior time slots for the old partner. If this lock is set, then the locked partner is no longer used in postings. This also applies for retroactive follow-up postings in time periods in which the old partner is entered in the posting term.
- Indicator is not set (
' '
)
It is not possible to set a lock. The standard logic applies. This means that the system continues to use the old partner (for instance, for follow-up postings).
Dependencies
Example
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 604 |