SAP ABAP Data Element CIFALECUS (Transfer of Data Changes to Cutomer via ALE Change Pointer)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
SCM-BAS (Application Component) SCM Basis
⤷
CIF (Package) Core Interface
SAP_APPL (Software Component) Logistics and Accounting⤷
SCM-BAS (Application Component) SCM Basis⤷
CIF (Package) Core Interface
Basic Data
| Data Element | CIFALECUS |
| Short Description | Transfer of Data Changes to Cutomer via ALE Change Pointer |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FLAG | |
| 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 | ALEPointer |
| Medium | 19 | ALE Change Pointer |
| Long | 37 | Customer Master Changes, Change Pntr |
| Heading | 45 | Customer Master Changes via ALE Change Pntr |
Documentation
Definition
If you choose this option, ALE change pointers that can be analysed via transaction CFP1 are written when changes are made to customer master records in the ERP system. The actual transfer of the changed customer data to SAP APO takes place only with transaction CFP1. You should schedule the change transfer per ALE indicator periodically via a batch job.
Note
Please note that the ALE pointers are not deleted, but rather are marked as 'processed' after the transfer of changes. You should archive the ALE change pointers regularly (transaction BD22) so as not to impair the system's performance.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in |
