SAP ABAP Data Element ECGPVKDELAY (Interval period for changes to BP and CA in move-in/out)
Hierarchy
☛
IS-UT (Software Component) SAP Utilities/Telecommunication
⤷ IS-U-CS-BT-IO (Application Component) Move-In/Out
⤷ EE06 (Package) IS-U: Move-In/Out
⤷ IS-U-CS-BT-IO (Application Component) Move-In/Out
⤷ EE06 (Package) IS-U: Move-In/Out
Basic Data
Data Element | ECGPVKDELAY |
Short Description | Interval period for changes to BP and CA in move-in/out |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUM2 | |
Data Type | NUMC | Character string with only digits |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | ChgIPBPCA |
Medium | 15 | Chg IP: BP/CA |
Long | 40 | Chg int perd BP & CA |
Heading | 3 | BC |
Documentation
Definition
Determines how many days before the move-in date/move-out date the changes made to the business partner and contract account data should come into effect.
The changes come into effect on the the move-in/move-out date minus the number of days in the interval period. At the earliest, the system can activate them on the date of entry.
If you set the interval period to 99 then the system deactivates the planned changes function, and applies the changes immediately.
Notes
To activate the planned changes, you must carry out the report BUSPCDACT for the application objects BUPA (business partner) and FICA (contract account) regularly (daily, if possible).
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |