SAP OSS Note 991429 - Minute Based extraction enhancement for 0FI... http://www.se80.co.uk/sapossnotes/9/9914/991429.

htm

Detials of SAP OSS Note 991429, version 0031. This

inlcudes any symptoms associated with the known
problem and instructions on how to fix it.

Click here for more information about SAP OSS Notes

and how they are downloaded and implemented using
transaction code SNOTE

Contribute (Comments/Questions)
Use the comments section below to add any links,
information or screen shots that you feel are relevant
to this SAP Note. This could include issues you have
found that are associated with this fix as well as any
additional fixes you have found or other relevant SAP
OSS notes. This information can then be found quickly,
simply by searching on the note number 991429
.

Note Details:

When does this problem occur

You would like to implement a 'minute based' extraction logic for the

data sources 0FI_GL_4, 0FI_AR_4 and 0FI_AP_4.

Currently the extraction logic allows only for an extraction once per

day without overlap.

Cause of the problem and Pre-requisites

1. There is huge volume of data to be extracted on a daily basis from FI

to BW and this requires lot of time.

2. You would like to extract the data at a more frequent intervals in a

day like 3-4 times in a day - without extracting all the data

that you have already extracted on that day.

In situations where there is a huge volume of data to be extracted, a

lot of time is taken up when extracting on a daily basis. Minute

based extraction would enable the extraction to be split into

convenient intervals and can be run multiple times during a day. By doi

ng so, the amount of data in each extraction would be reduced and hence

the extraction can be done more effectively. This should also

reduce the risk of extractor failures caused because of huge data in the

1 of 5 system. 8/24/2016 2:16 AM

SAP OSS Note 991429 - Minute Based extraction enhancement for 0FI... http://www.se80.co.uk/sapossnotes/9/9914/991429.htm

reduce the risk of extractor failures caused because of huge data in the

system.

Solution instructions

Implement the relevant source code changes and follow the instructions

in order to enable minute based extraction logic for the extrac

tion of GL data. The applicable data sources are:

0FI_GL_4

0FI_AR_4

0FI_AP_4

All changes below have to be implemented first in a standard test

system. The new extractor logic must be tested very carefully before

it can be used in a production environment. Test cases must include all

relevant processes that would be used/carried in the normal c

ourse of extraction.

Manual changes are to be carried out before the source code changes in

the correction instructions of this note.

1. Manual changes

a) Add the following parameters to the table BWOM_SETTINGS

MANDT OLTPSOURCE PARAM_NAME

PARAM_VALUE

XXX BWFINEXT

XXX BWFINSAF 3600

Note: XXX refers to the specific client(like 300) under

use/test. This can be achieved using using transac

tion 'SE16' for table 'BWOM_SETTINGS'

Menue --> Table Entry --> Create

--> Add the above two parameters one after another

b) To the views BKPF_BSAD, BKPF_BSAK, BKPF_BSID, BKPF_B

SIK

under the view fields add the below field,

View Field Table Field Data Element

DType Length CPUTM BKPF CPUTM

CPUTM TIMS 6
2 of 5 8/24/2016 2:16 AM
SAP OSS Note 991429 - Minute Based extraction enhancement for 0FI... http://www.se80.co.uk/sapossnotes/9/9914/991429.htm

DType Length CPUTM BKPF CPUTM

CPUTM TIMS 6

This can be achieved using transaction 'SE11' for

views BKPF_BSAD, BKPF_BSAK , BKPF_BSID

, BKPF_BSIK (one after another) --> Change

--> View Fields --> Add the above me

ntioned field with exact details c) For the table BWFI_AEDAT index-1

for extractors add the field AETIM (apar

t from the existing MANDT, BUKRS, and AEDAT) and

activate this Non Unique index on all database systems (or at

least on the database under use). This can

achived using transaction 'SE11' for table 'BWFI_AEDAT'

--> Display --> Indexes --> Index-1 For extractors

--> Change -->

Add the field AETIM to the last position (after AEDAT field )

--> Activate the index on database 2. Imple

ment the source code changes as in the note correction instructions. 3.

After implementing the source code changes using SNOTE instru

ction ,add the following parameters to respective function modules and

activate. a) Function Module: BWFIT_GET_TIMESTAMPS

1. Export Parameter

a. Parameter Name : E_TIME_LOW

b. Type Spec : LIKE

c. Associated Type : BKPF-CPUTM

d. Pass Value : Ticked/checked (yes)

2. Export Parameter

a. Parameter Name : E_TIME_HIGH

b. Type Spec : LIKE

c. Associated Type : BKPF-CPUTM

d. Pass Value : Ticked/checked (yes)

b) Function Module: BWFIT_UPDATE_TIMESTAMPS

1. Import Parameter (add after I_DATE_HIGH)

a. Parameter Name : I_TIME_LOW

b. Type Spec : LIKE

c. Associated Type : BKPF-CPUTM

d. Optional : Ticked/checked (yes)

e. Pass Value : Ticked/checked (yes)

3 of 5 8/24/2016 2:16 AM
SAP OSS Note 991429 - Minute Based extraction enhancement for 0FI... http://www.se80.co.uk/sapossnotes/9/9914/991429.htm

e. Pass Value : Ticked/checked (yes)

2. Import Parameter (add after I_TIME_LOW)

a. Parameter Name : I_TIME_HIGH

b. Type Spec : LIKE

c. Associated Type : BKPF-CPUTM

d. Optional : Ticked/checked (yes)

e. Pass Value : Ticked/checked (yes)

4. Working of minute based extraction logic:

The minute based extraction works considering the time to

select the data (apart from date of the document either change

d or new as in the earlier logic).The modification to the code is made

such that it will consider the new flags in the BWOM_SETTINGS t

able ( BWFINEXT and BWFINSAF ) and the code for the earlier extraction

logic will remain as it was without these flags being set as pe

r the instructions for new logic to be used(but are modified to include

new logic). Safety interval will now depend on the flag BWFIN

SAF (in seconds ; default 3600) and has a default value of 3600 (1

hour), which would try to ensure that the documents which are dela

yed in posting due to delay in update modules for any reason. Also there

is a specific coding to post an entry to BWFI_AEDAT with the

details of the document which have failed to post within the safety

limit of 1 hour and hence those would be extracted as a changed do

cuments at least if they were missed to be extracted as new documents.

If the documents which fail to ensure to post within safety lim

it is a huge number then the volume of BWFI_AEDAT would increase

correspondingly. The flag BWFINSAF could be set to particular value

depending on specific requirements (in seconds , but at least 3600 = 1

hour) like 24 hours / 1 day = 24 * 3600 => 86400.With the new

logic switched ON with flag BWFINEXT = X the other flags BWFIOVERLA ,

BWFISAFETY , BWFITIMBOR are ignored and BWFILOWLIM , DELTIMEST

will work as before. As per the instructions above the index-1 for the

extraction in table BWFI_AEDAT would include the field AETIM w

hich would enable the new logic to extract faster as AETIM is also

considered as per the new logic. This could be removed if the stand

ard logic is restored back. With the new extractor logic implemented

you can change back to the standard logic any day by switching o

ff the flag BWFINEXT to ' ' from 'X' and extract as it was before. But

ensure that there is no extraction running (for any of the extr

actors 0FI_*_4 extractors/datasources) while switching. As with the

earlier logic to restore back to the previous timestamp in BWOM2_

4 of 5 8/24/2016 2:16 AM
SAP OSS Note 991429 - Minute Based extraction enhancement for 0FI... http://www.se80.co.uk/sapossnotes/9/9914/991429.htm

actors 0FI_*_4 extractors/datasources) while switching. As with the

earlier logic to restore back to the previous timestamp in BWOM2_

TIMEST table to get the data from previous extraction LAST_TS could be

set to the previous extraction timestamp when there are no curr

ent extractions running for that particular extractor or datasouce.

With the frequency of the extraction increased (say 3 times a day

) the volume of the data being extracted with each extraction would

decrease and hence extractor would take lesser time. You should o

ptimize the interval of time for the extractor runs by testing the best

suitable intervals for optimal performance. We would not be ab

le to give a definite suggestion on this, as it would vary from system

to system and would depend on the data volume in the system, nu

mber of postings done everyday and other variable factors. To turn on

the New Logic BWFINEXT has to be set to 'X' and reset back to '

' when reverting back. This change has to be done only when there no

extractions are running considering all the points above.

With the new minute based extraction logic switched ON,

a) Ensure BWFI_AEDAT index-1 is enhanced with addition of AETIM

and is active on the database. b) Ensure BWFINSAF is atleast 3600 ( 1

hour) in BWOM_SETTINGS c) Optimum value of DELTIMEST is maintai

ned as needed (recommended/default value is 60 ) d) A proper testing

(functional, performance) is performed in standard test system an

d the results are all positive before moving the changes to the

production system with the test system being an identical with the pro

duction system with settings and data.

Description of problem

general ledger 0FI_GL_4 0FI_AP_4 0FI_AR_4 extraction performance

5 of 5 8/24/2016 2:16 AM