FI-CO Delta Safety Interval Summary
Safety interval is mandatory to FI-CO extractors, the underlying reason is FI-CO extraction rely on timestamp. System must add buffer to timestamp because of the document saving time consuming.
But it is not easy to find out how the buffer are given and what is the value, this blog post will help you to understand and get necessary information.
Types of Safety interval
There are two types of safety interval (refer to notes 2116914):
- Safety interval by generic delta
⑴. Generic datasource (created by customer using transaction code RSO2),
⑵. A few application datasources(mainly in FI/CO area) : for example, 0FI_GL_10, 0FI_GL_14
- Safety interval by application
⑶ 0FI_GL_4 (0FI_AR_4 and 0FI_AP_4 as well)
⑷ Some CO datasources:e.g. 0CO_OM_CCA_9, 0CO_OM_WBS_6, 0CO_OM_OPA_6, 0CO_OM_NWA_2, 0CO_OM_NAE_2, 0CO_OM_NTW_2, 0CO_OM_CCA_40, 0CO_OM_OPA_40.
Safety interval by generic delta
The datasource which using ‘Safety interval by generic delta can be found in table ROOSOURCE by field GENDELTAFD <> NULL :
The safety interval is defined in table ROOSOURCE
The delta time stamp is in table ROOSGENDLM
Safety interval by application
①0FI_GL_4 (0FI_AR_4 and 0FI_AP_4 as well):
The safety interval logic is implemented in function BWFIT_GET_TIMESTAMPS.
The safety interval is defined in table BWOM_SETTINGS
The delta time stamp is stored in table BWOM2_TIMEST
②Some CO datasources (*not all), e.g. 0CO_OM_CCA_9, 0CO_OM_WBS_6, 0CO_OM_OPA_6, 0CO_OM_NWA_2, 0CO_OM_NAE_2, 0CO_OM_NTW_2, 0CO_OM_CCA_40, 0CO_OM_OPA_40.
The safety interval logic is implemented in function BWOMT_GET_TIMESTAMPS.
The delta time stamp is in table BWOM2_TIMEST
The safety interval is default 120 minutes and defined in programs
Here is an example of interval defined in program.
Important settings/tables determining timestamp
|BWOM_SETTINGS||this table maintains the settings for delta extraction, the entries made in this table are common for all the data source extractors|
|BWFI_AEDAT||Contains List of changed documents(cleared or changed) with date|
|BWFI_AEDA2||log table for changed(cleared or changed) transactional figures|
|BWFI_AEDA3||Table for changed(cleared or changed) credit management data|
Important parameters of table BWOM_SETTINGS:
This field is used to calculate the upper limit of date for the extraction.
It makes formula = Current Date – BWFISAFETY.
Default value for this field is 1.
Blank- switch on BWFISAFETY
X-switch off BWFISAFETY
|DELTIMEST||60||Days of log kept in table BWFI_AEDAT, BWFI_AEDA2 and BWFI_AEDA3|
|BWFITIMBOR||020000||Value in this field indicates the time after which delta extraction will take the latest delta records. By default the value is maintained as 2.00 AM. That is after 2.00 AM delta run will bring the latest records from the past day. If the delta is run before 2.00 AM. It goes back by one more day.|
|BWFINEXT||This field is set for activating the minute based extraction. That is if the value for this field is set to ‘X’, minute based delta extraction is enabled. By default the value = ‘SPACE’.|
Following the introduction, tables and program I listed, you can check various issues on FI-CO delta extraction, such as delay,duplication and data lost.
Please also be awared that, usually the data/time is stored as timestamp format, then you need use function module ‘RKE_TIMESTAMP_CONVERT_OUTPUT’ to convert it .
You can find more detail informaton from there SAP notes: 1012874 / 2116914 / 2132869 / 553561.