Hierarchy

⤷

⤷

Basic Data
Data Element | RSDS_DELTAMETHOD |
Short Description | DataSource: Delta Process |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RSDS_DELTAMETHOD | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
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 | Delta Pro. |
Medium | 15 | Delta Process |
Long | 20 | Delta Process |
Heading | 30 | Delta Process |
Documentation
Definition
This field indicates which delta procedure is used by the DataSource.
The delta procedure is characterized by the following properties:
- Record typeof extracted records:
The record type describes the type of data records transferred from the DataSource to the BI in a delta procedure:
DataSource returns Full (complete data set of source)
DataSource returns Before Images (status of records before the change)
DataSource returns Before Images (status of records before the change)
DataSource returns Delta Images for values that cannot be totaled (After Images for values that cannot be totaled)
DataSource returns Deletion records (only key values)
DataSource returns complete deletion records (Reverse Images)
DataSource returns New images (new records) - Delta type (type of request and transfer in SAP source system):
This property is only relevant for SAP source syetems. The delta type describes how new and changed data records are added to the delta queue in the SAP source system.
Delta using delta queue: The application (or extraction using function module) delivers the delta to the generic delta queue, where the delta is retrieved from the DataSource by means of a request from the BI.
Delta using extractor: The DataSource extractor returns the delta (requested from the BI) and stores it in the delta queue, in case an error occurs and the transfer needs to be repeated.
Delta using ALE change pointer for master data - Serialization request:
This property indicates whether changes made to document data have to be in the same order as in the source system.
Serialization not required
Serialization of request required
Serialization of data packages required
Use
For DataSources from SAP source systems, the system displays the delta procedure specified in the source system.
Delta Procedure Description Record type Delta type Serialization Purpose Example/Explanation
- Full upload (Delta only by using InfoPackage selections) F - by request: InfoCube, DataStore Object, InfoObject
A ALE change pointer (master data) A ALE by package: only master data
ABR Complete delta with deletion flag using delta queue N,B,A,R Queue by package: InfoCube-capable
ABR1 Like 'ABR' procedure but serialization is only by request N,B,A,R Queue by request: InfoCube-capable
ADD Additive extraction using extraktor D Extractor: by request: InfoCube-capable LIS infostructures
ADDD Like 'ADD' but using delta queue D Queue by request: InfoCube-capable
AIE After images using extractor A Extractor by package: only DataStore object FI-GL, AP, AR
AIED After images with deletion flag using extractor A,L Extractor by package: only DataStore object FI-GL, AP, AR
AIM After images using delta queue A Queue by package: only DataStore object FI-AP, AR
AIMD After images with deletion flag using delta queue A,L Queue by package: only DataStore object
CUBE InfoCube extraction D Extractor No serialization InfoCube Export-DataSource of InfoCube
D Unspecific delta using delta queue - Queue by package: only InfoCube
E Unspecific delta using extractor - Extractor by package: only InfoCube
NEWD Only new records (inserts) over delta queue N Queue No serialization InfoCube-capable
NEWE Only new records (inserts) over extractor N Extractor No serialization InfoCube-capable
ODS DataStore object extraction N,B,A,R Extractor by package: DataStore object, InfoObject-capable Export-DataSource of DataStore object
For file, UD connect, DB connect, and Web service DataSources you can select the following delta procedures:
Delta procedure Description Record type Delta type Serialization Purpose Example/Explanation
- Full upload (Delta only by using InfoPackage selections) F - by request: InfoCube, DataStore Object, InfoObject You can make selections by using the date, for example.
FIL0 Delta data (after images) A - by package: DataStore object Each record to be loaded provides the new status for all key figures and characteristics.
FIL1 Delta data (delta images) D - by package: DataStore object, InfoCube The record to be loaded for additive key figures provides only the modification to the key figure.
Dependencies
Examples
AIM (After images using delta queue):
This delta procedure used for DataSources from SAP source systems only sends After images. Therefore delta requests can only be used to update to a DataStore object. It cannot be directly updated to an InfoCube. The same key can be transferred multiple times within a request. Therefore it is necessary to serialize the data package by package. The delta records are written directly to the delta queue, where the records are retrieved from the BI by request. This procedure is used in FI-AP / AR to transfer the line items.
FIL0 (After Images):
This delta procedure only sends After images. Therefore delta requests can only be used to update to a DataStore object. It cannot be directly updated to an InfoCube. The same key can be transferred multiple times within a request. Therefore it is necessary to serialize the data package by package. This delta procedure is used by all source system types apart from SAP source systems. Therefore delta queues are not implemented: Delta data records are transferred directly from the source system to the DataSource in the BI.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 700 |