Hierarchy
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SALE2 (Package) Application Link Enabling/ Basis Tools
Basic Data
Data Element | BDCP2_ACT |
Short Description | Information on Whether Change Pointers are Written to BDCP2 |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BDCP2_ACT | |
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 | BDCP2_ACTIVE | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | CP Target |
Medium | 20 | Change Pointer Targt |
Long | 35 | Change Pointer Storage Location |
Heading | 40 | Storage Location for Change Pointers |
Documentation
Definition
ALE change pointers are stored in the database tables BDCP/BDCPS and BDCP2. If message types support the use of BDCP2, you should make use of this option, since it considerably improves the speed at which change pointers are accessed both in read and write mode. The message types are characterized by the indicator BDCP2_SUP = 'X' in table TBDME.
If you already have change pointers stored in BDCP/BDCPS for a message type that you want to use with new change pointers, you must migrate the change pointers. Proceed as follows to do this:
During the migration process, change pointers of the message types to migrated must not be processed. From an organizational point of view, ensure that they cannot be processed, and then proceed as follows for migration:
- Process the open change pointers, if possible.
- Delete processed and old change pointers.
- Set the change pointer destination for the message types to be migrated to 'M', i.e. migration from BDCP/BDCPS to BDCP2.
- Migrate the stored change pointers using report RBDCPMIG.
- Set the change pointer destination for the message types to be migrated to 'X', i.e. BDCP2.
In productive operation, do not switch from BDCP2 storage back to BDCP/BDCPS storage. Back-migration is not supported. The change pointers in table BDCP2 are then not visible for the application, and data may be inconsistent as a result.
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in | 50A |