BWOM_SETTINGS

Hi All,
We are using controlling extarctor CCA_9 and recently we are facing a issue with it's performance.
We checked the indexes 1 and 4 and they say active and existes in database system.
Can anybody throw me some light?
When I went to table BWOM_SETTINGS table I see some entries for CCA_9. I am not sure if these values are correct
CCA _9                         NOBLOCKING X
CCA_9                         MOSTRECENT
CCA_9                        LOCKING
Are these entries correct???????
Let me know.

Hi Ram ,
I am not sure regarding the setting but in my project this setting is like :
0CO_OM_CCA_9 MOSTRECENT Blank
0CO_OM_CCA_9 NOBLOCKING Blank
For more info regarding the extraction see this link :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a
Hope it helps,
Supriya

Similar Messages

FI- Line Item Extraction- BWOM_SETTINGS- Control Table Entries

Gurus,
I am working on FI- Line item extraction in the sand box. I have all my DS's in Nodes not connected. I transfereed the application component hierarchy in SBIW. Now I went to check on the basic settings before activating the DS's for FI line item- in the control table, BWOM_SETTINGS, I could not find any parameters- lowlimit, safety, there are only 2 parameters-OBJSELSICO-'X', and OBLIGODELT- ' '.
We can enter the param values manually and transfer global settings to BI. Could we do the same for fields too. Could we enter them manually?
Why does my control table doesn't have the fields for std line item extraction- lowlim, safety, timbor, overla. My plug- ins are good. I have all the plug ins. I can see them in dev box but not sand box. Why?

Hi Ram,
I think Time stamp will set in this table when we run first delta or init in BI system.
So activate the data source and replicate the same BI system. develop data model for this data source and run the init for this data source.
then you will be able to find time stamp for this data source.
FI-Line item data-Delta.
0FI_GL_4 delta functionality?????
Regards,
Venkatesh

Entries in table BWOM_SETTINGS for PARAM_NAME = 'OBJSELSIZE '

Hello All,
The entries in table BWOM_SETTINGS for PARAM_NAME = 'OBJSELSIZE ' in our ECC system were as follows originally:
OLTPSOURCE = ''
PARAM_NAME = 'OBJSELSIZE '
PARAM_VALUE = 'X'
At that point we started using delta extarctor 0PM_OM_OPA_2 and it had a very poor performance.
SAP asked us to implement note 1040072.
As a result of applying that note, the BWOM_SETTINGS table has 2 entries for PARAM_NAME = OBJSELSIZE.
1. OLTPSOURCE = ''
PARAM_NAME = 'OBJSELSIZE '
PARAM_VALUE = 'X'
2. OLTPSOURCE = '0PM_OM_OPA_2'
PARAM_NAME = 'OBJSELSIZE '
PARAM_VALUE = 'X'
Things were fine until we added more init selections to another CO extractor, 0CO_OM_OPA_6.
0CO_OM_OPA_6 deltas were taking around 2 hours for original init selections:
Fiscal year / period 2007001 2007012
Fiscal year / period 2008001 2020012
Controlling Area 3000
Recently we added more init selections and now selections are :
Fiscal year / period 2007001 2007012
Fiscal year / period 2007001 2020012
Fiscal year / period 2008001 2020012
Controlling Area 3000
Controlling Area 4000
Controlling Area 5000
The extraction is now taking unacceptably long time, about 15 hours.
I am not sure if it is because adding more inits.
I have a feeling the entries in BWOM_SETTINGS for OBJSELSIZE are incorrect.
According to note 836740 should they be as below?
OLTPSOURCE = '0CO_OM_OPA_6'
PARAM_NAME = 'OBJSELSIZE '
PARAM_VALUE = 'X'
OLTPSOURCE = '0PM_OM_OPA_2'
PARAM_NAME = 'OBJSELSIZE'
PARAM_VALUE= 'X'"
One more question. If we change the BWOM_SETTINGS entries to as above, will that affect other CO extractors?
For instance, we use 0CO_OM_CCA_9 very widely and it runs very fast currently. I just want to make sure we dont mess up its performance by modifying the entries in BWOM_SETTINGS. May be add one more entry in BWOM_SETTINGS for 0CO_OM_CCA_9 too?
Sorry about the lengthy post.
Any help is greatly appreciated.
Thank you.

As stated in [OSS Note 836740 - Delta extractors CO: OBJSELSIZE DataSource specific|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=836740], there should be parameter OBJSELSIZE entries, with a value of X for the following CO DataSources:
0CO_OM_CCA_9
0CO_OM_OPA_6
0CO_OM_ABC_7
0CO_OM_WBS_6
0CO_OM_NAE_2
0CO_OM_NTW_2
0OC_OM_NWA_2
The independent entry, where the DataSource is blank, should also be prsent for the OBJSELSIZE parameter with a value of X. [OSS Note 1040072 - 0PM_OM_OPA_2: Poor performance|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1040072] shows that it's also needed for the 0PM_OM_OPA_2 DataSource.
Your entries for 0CO_OM_OPA6 and 0PM_OM_OPA_2 are correct. You should add 0CO_OM_CCA_9 and any other DataSource in the list above. If they're not listed, they are supposed to be taken care of by the independent entry (DataSource is blank).

Settings to BWOM_SETTINGS table in R/3 for deltas

Hi my requirment is to change a Parameter value in BWOM_SETTINGS table in R/3 for deltas..
I made the change in ore R/3 customizing client...but the setting is not updated in other clients
Please update me how to proceed
Thanks

Hi
Its not allowing me to change in the extraction client
Is this a client dependent table and do i need to ask basis to open the system for changes
Thanks

Settings of the Tabel BWOM_SETTINGS

Hello experts,
We're having some issues regarding to the 0FI_GL_4 extractor.
We're only able to update record to the previous day.
Is there any way to update the records in BW to the time that the extractor is running?
Based on your experience, can you tell us what are the main problems with the extraction of the most current data?
The settings of our Tabel BWOM_SETTINGS are:
DataSource                           PARAM_NAME           Char
                                              BWFIGLLOG
                                              BWFILOWLIM           19910101
                                              BWFINEXT
                                              BWFINSAF             3600
                                              BWFIOVERLA
                                              BWFISAFETY
                                              BWFITIMBOR           020000
                                              DELTIMEST           60
                                              OBJSELSICO           X
                                              OBLIGODELT
                                              ORGSYSONLY
0COORDER_ATTR_TEXT      ORGSYSONLY
0FI_GL_4                              BWFIOVERLA           X
0FI_GL_4                              BWFISAFETY
0FI_GL_4                              DELTIMEST           60
Thanks in advance.
Best regards,
Rui Romba

Hi Rui,
1. This is a time stamp table which is used in Delta extraction.It serves as loading history of items. It also provides defined restart points following incorrect data requests.
2. The data we extract via 0FI_GL_4 is transaction data .In case the postings are getting created in R/3 side and at the same time you are extracting that data too then you may miss some of the critical transaction data .
3. It is suggested that their should be at least 30 min safe interval between postings in R/3 and extraction in BW .In case you miss some of the postings you will not be able to do correct reporting and the data that will be lost cannot be recovered without resetting time stamp and repeating delta loads again for that duration .
4. You can change the time stamp setting by BWOM2_TIMEST report program .
Regards,
Jaya Tiwari

BWOM_TIMEST, BWOM_SETTINGS somebody please help

Hi Gurus,
Can somebody explain me and confirm my understanding on Delta in FI.
1. Delta in FI is done through Timestamp method but not through Delta Queue.
2. Before starting the init we need to setup an entry in table TPS31 so as to enable the recording of the change documents.
3. BWOM_TIMEST table will have the loading history like when we did the init and delta
Fields Explaination
LAST_TS:- Check mark in this field shows the time intervals of the last delta load.
if for exampel we have done three loads say form
jan1 to jan31
feb1 to feb28
mar1 to mar21 (this is the last load done through delta) we will be having the check mark in field LAST_TS for mar1 to mar21 saying this was the last load.
And if we have some problem in the deltas already loaded we can change this check mark in the field to the desired data and we can get all the data from the check mark again....Am i right.
DATE_LOW: This is the start date of the selection data for a load.
DATE_HIGH: This is the end date of the selection of data for a load.
Say for example if we have done init on jan31 extracting data from
Jan1 to Jan31
then the Jan1 will be the DATA_LOW and Jan31 will be the DATE_HIGH. PLZ KINDLY CORRECT ME IF I AM WRONG.
4. Table BWFI_AEDAT will be having the record of the changed documents. and when we do delta system will get the details form here and extract the data.
5. Table BWOM_SETTINGS is the table which will be controlling the delta in FI related applications. It will be controlling the selection of data in init as well as the delta saftey intervals.
BWFILOWLIM: It will be having the time limit from where the data will be selected for an initialization of the delta. For Eg:
if we have data in our system from 01-01-1991 to 01-02-2006.
and we have an entry in our field BWFILOWLIM as 01-01-1994 then when we do our initialization then we will only get the data from 01-01-1994 so our init will only set the delta parameters for the data from 01-01-1994 only.
BWFISAFETY:- this field will determine the saftey interval of the delta for example if we have 1 in that field that means we will get deltas till previous day.
am i right in my understanding the fields till now.
can somebody explain me the fields and their logic.
BWFIOVERLA
BWFITIMBOR
thanks
Neel

It's all in the SAP net documentation - but for clarity
1. yes
2. Should be enabled as default
3. TIMESTAMP not date stamp
Datelow is the date high from the previous load - if it is the first load - it will be set to a aribtary date BWFILOWLIM - it has nothing to do with your init selections
Date high is set in normal operation by 0FI_GL_4 and is dpenedant on the BWFIOVERLAP paramter
4. True
5. Doesn;t control data in an init (apart from the arbitary date for date low - note 1991 is the CPU date - there will be no R3 transactions posted back then - R3 wasn;t released onto the market until July 1992 ) - but everything else is true
BWFISAFETY - true - but if you have BWFIOVERLA set - it ignore this
BWFIOVERLA - set to X will mean timsetamp high will be 23:59 of the day you run it (it well past the time your an - so you can get up to date documents and not wait for the safety)
BWFITIMBOR - safety time - if you run an infopackage after this time it does day -1 - if you run it before this time it does day -2 - if you BWFIOVERLA set - it ignores this

BWOM_SETTINGS Issue

Hi Experts,
I have BWOM_SETTINGS table in Development and Quality.
Now I am Transporting Entries from Development to Quality.I have imported the request from the import query in Quality, however the table contents are not getting updated. The fields of the table BWOM_SETTINGS are different in Development and Quality.
But, why why am i not getting the table entries in Quality for BWOM_SETTINGS after transporting the request from Development.
Plz help.
Thanks in advance.

Hi,
Have you tried this :
go to se09, create a new transport of copies type request, then into request objects, 'R3TR' for program id, 'tadir' for object type and 'BWOM_SETTINGS' for object name.
Then, during transportation of this request, in options, selecting 'overwrite originals'

Delta Extraction of CO_OM_CCA_9 after change in BWOM_Settings

Hi Sap Gurus,
We have implemented the SAP OSS note 553561 to modify the safety limit in BWOM_settings for most updated Delta Extraction for CO DataSource 0CO_OM_CCA_9, But when i schedule the delta it brings only the CO documents that have created in the month of September 2011 only and we do have a lot of documents resides in R/3 side. Last Delta run a year ago in Sandbox.
Any idea why its not fetching the complete delta?
All kind of help will be appreciated.

Hi
check how much data you have in RSA7, delta will pick the data in RSA7.
check you have any selections in IP on 0CALMONTH, then remove the selections and run the IP to get all the data.
Before you start delete the previous request to overcome duplicate records.
Regards,
Venkatesh

Keeping no of days less than 15 in field DELTIMESTof BWOM_SETTINGS table

Hello Experts,
Is it possible to keep no of days less than 15 in field DELTIMEST of BWOM_SETTINGS table so as to keep data in BWFI_AEDAT only for 2 days.
Also I tried but its not working,it still keeping data of last 15 days.
Regards,
Ankush Sharma

Hi Ankush,
DELTIMEST is the minimum retention period of time stamp tables.
As per SAP logic, the minimum retention period for entries in the time stamp table is 15 days. So if you decrease the parameter value less than 15, SAP will automatically take the minimum value as 15 and ignore the settings. That is why you are not able to delete the entries less than 15 days.
Ideally, when entries are deleted from table BWOM2_TIMEST, the corresponding entries for the changed line items are deleted simultaneously from log table BWFI_AEDAT, BWFI_AEDA2 and BWFI_AEDA3.
BWFI_AEDAT table contains list of changed documents with the change date and the document number which helps in the delta extraction. SAP has recommended DELTIMEST value to be >= 60.
Refer the below SAP note: (check BWOM_SETTINGS part in solution)
1012874 - FAQ extractors 0FI_AP_* 0FI_AR_* 0FI_GL_*(except 10)
Let me know if there are any questions.
Thanks
Amit

Performance issues with 0CO_OM_WBS_1

We use BW3.5 & R/3 4.7 and encounter huge performance issues with 0CO_OM_WBS_1? Always having to do a full load involving approx 15M records even though there are on the average 100k new records since previous load. This takes a longtime.
Is there a way to delta-enable this datasource?

Hi,
This DS is not delta enabled and you can only do a full load. For a delta enabled one, you need to use 0CO_OM_WBS_6. This works as other Financials extractors, as it has a safety delta (configurable, default 2 hours, in table BWOM_SETTINGS).
What you should do is maybe, use the WBS_6 as a delta and only extract full loads for WBS_1 for shorter durations.
As you must have an ODS for WBS_1 at the first stage, I would suggest do a full load only for posting periods that are open. This will reduce the data load.
You may also look at creating your own generic data source with delta; if you are clear on the tables and logic used.
cheers...

BW Extractor for FS10N Repot

Hello all,
I have seen few threads on BW extractors for FS10N report.
I would like to know which is the best BW extractor to use for FS10N report.
Is it 0FI_GL_4 or 0FI_GL_10 or 0FI_GL_1? Could anyone please suggest.
Thanks,
Praveen Tati

Thank you Murali.
The table FAGL_ACTIVEC has no entries in ECC. I assume it is not active.
I will use 0FI_GL_4 extractor and enhance as per the requirement.
Could you please tell me what setting I need to do to get latest delta's when I run data load from BW?
I understand that I need to do some settings in tables BWOM_SETTINGS, BWOM2_TIMEST.
Thank you very much.
Praveen
Edited by: Praveen Tati on Jun 17, 2011 11:12 PM

The 0co_om_opa_6 ip in the process chains takes long time to run

Hi experts,
The 0co_om_opa_6 ip in the process chains takes long time to run around 5 hours in production
I have checked the note 382329,
-> where the indexes 1 and 4 are active
-> index 4 was not "Index does not exist in database system ORACLE"- i have assgined to " Indexes on all database systems and ran the delta load in development system, but guess there are not much data in dev it took 2-1/2 hrs to run as it was taking earlier. so didnt find much differnce in performance.
As per the note Note 549552 - CO line item extractors: performance, i have checked in the table BWOM_SETTINGS these are the settings that are there in the ECC system.
-> OLTPSOURCE - is blank
   PARAM_NAME - OBJSELSIZE
   PARAM_VALUE- is blank
-> OLTPSOURCE - is blank
   PARAM_NAME - NOTSSELECT
   PARAM_VALUE- is blank
-> OLTPSOURCE- 0CO_OM_OPA_6
   PARAM_NAME - NOBLOCKING
   PARAM_VALUE- is blank.
Could you please check if any other settings needs to be done .
Also for the IP there is selction criteris for FISCALYEAR/PERIOD from 2004-2099, also an inti is done for the same period as a result it becoming difficult for me to load for a single year.
Please suggest.

The problem was the index 4 was not active in the database level..it was recommended by the SAP team to activate it in se14..however while doing so we face few issues se14 is a very sensitive transaction should be handled carefully ... it should be activate not created.
The OBJSELSIZE in the table BWOM_SETTINGS has to be Marked 'X' to improve the quality as well as the indexe 4 should be activate at the abap level i.e in the table COEP -> INDEXES-> INDEX 4 -> Select the u201Cindex on all database systemu201D in place of u201CNo database indexu201D, once it is activated in the table abap level you can activate the same indexes in the database level.
Be very carefull while you execute it in se14 best is to use db02 to do the same , basis tend to make less mistake there.
Thanks Hope this helps ..

In Which R/3 Table, the Extraction Date should be RESET to Limit DELTA ???

Hi all,
We have a daily delta extraction setup for DataSource 0FI_GL_4 from R/3 into ODS. I think there is a table on R/3 side where we could RESET the extraction date (?) to limit the delta reload incase something goes wrong with delta process. Without this reset, it may take 2-3 WEEKS for us.
Is any one has any idea about this table , PLEASE....
Thanks.

hi Venkat,
check oss note 485958-BW-BCT-FI: Repeating delta extractions
Symptom
This note provides the option of repeating delta extractions under certain conditions.
The note is valid for the DataSources listed below:
0FI_AP_4 - Accounts Payable: Line Items
0FI_AR_4 - Accounts Receivable: Line Items
0FI_GL_4 - General Ledger: Line Items
0FI_TX_4 Taxes: Line Items
0FI_AP_6 Accounts Payable: Transaction Figures Using Delta Extraction
0FI_AR_6 Accounts Receivable: Transaction Figures Using Delta Extraction
0FI_GL_6 - General Ledger: Transaction Figures Using Delta Extraction
0FI_AP_7 - Accounts Payable: Special G/L Transaction Figures Using Delta Extraction
0FI_AR_7 - Accounts Receivable: Special G/L Transaction Figures Using Delta Extraction
0FI_GL_7 - General Ledger: Cost of Sales Accounting Ledger Using Delta Extraction
0FI_AR_8 - Accounts Receivable: Credit Management: Central Data Using Delta Extraction
0FI_AR_9 - Accounts Receivable: Credit Management: Control Area Data Using Delta Extraction
0FI_AR_10 - Accounts Receivable: Payment History Using Delta Extraction
Other terms
BWOM2_TIMEST, TIMESTAMP, BWOM_SETTINGS, LAST_TS, delta, init
Reason and Prerequisites
For test or correction purposes you require a function to repeat delta extractions.
In the standard system, you can repeat the delta extractions for the last sixty days.
The number of days is defined by the 'DELTIMEST' parameter in the BWOM_SETTINGS table.
For all DataSources mentioned above you can repeat the delta extraction without problems because all DataSources use an ODS object. The system automatically filters out data that is selected several times.
Solution
The solution consists of resetting the time stamps used for the delta extraction in the BWOM2_TIMEST table to a certain date.
To do this, you must reset the 'X' marker in the 'LAST_TS' column for the last successful delta extraction.
The next delta extraction then loads all data created or changed as of this date to the BW system.
To reset the 'X' marker in the 'LAST_TS' column, use the 'BWOM2_TIMEST' report. If the report is not yet available in you system, you can install it as described in Note 836288.
Caution - important note
If you repeat several delta extractions in a run using this note, the number of the extracted records will in most cases be smaller than the total of the individual delta extractions.
This can happen in the following cases:
If documents are contained in several individual delta extractions due to document changes. The system selects these documents only once.
If you have set parameter BWFIOVERLA = X in the BWOM_SETTINGS table. (See Note 485958)
In this case, the upper limit of the period for the data selection is not, as usual, 23:59:59 of the previous day. The system also extracts all existing documents of the current day. These documents are also contained in the following delta extraction.
1. If you can load the expected data volume in one delta extraction, proceed as follows:
Execute the 'BWOM2_TIMEST' report for the relevant DataSource.
Remove the marker in the entry of the last delta extraction.
In the columns for the date of the time stamp and the time of the time stamp, you can see up to when the individual data extractions have extracted data.
Select the entry up to which the data in your BW system is still correct.
Save the changes.
Do not make any further changes in the BWOM2_TIMEST table.
              The next delta extraction uses the date + 1 of the selected entry as a lower limit for the data selection and the current date - 1 for the upper limit.
2. If you must load the expected data volume in several parts, proceed as follows:
Caution: There are the following two cases:.
a) The 'BWFIOVERLA' parameter in the BWOM_SETTINGS table is not set.
           Execute the 'BWOM2_TIMEST' report for the relevant DataSource.
           Remove the marker in the entry of the last delta extraction.
           In the columns for the date of the time stamp and the time of the time stamp, you can see up to when the individual data extractions have extracted data.
Select the entry up to which the data in your BW system is still correct.
           Save the changes.
Do not make any further changes in the BWOM2_TIMEST table.
               The next delta extraction uses the date + 1 of the selected entry as a lower limit for the data selection.
You can control the upper limit for the data selection by changing the ' BWFISAFETY' parameter in the BWOM_SETTINGS table. The upper limit is determined using the current date minus the value of the 'BWFISAFETY' parameter (default = 1).
If you want to extract the data of the last twenty days in four parts, for example, set the parameter as follows in Transaction SE16:
before the 1. delta extraction > > BWFISAFETY = 15
before the 2. delta extraction > > BWFISAFETY = 10
before the 3. delta extraction > > BWFISAFETY = 5
before the 4. delta extraction > > BWFISAFETY = 1 (= default)
b) The 'BWFIOVERLA' parameter in the BWOM_SETTINGS table is set (=X).
           First, deactivate the 'BWFIOVERLA' parameter in the BWOM_SETTINGS table. This is necessary because if you do not do this, the system ignores the settings of the 'BWFISAFETY' parameter.
           Execute the 'BWOM2_TIMEST' report for the relevant DataSource.
           Remove the marker in the entry of the last delta extraction.
           In the columns for the date of the time stamp and the time of the time stamp you can see up to when the individual data extractions have extracted data.
Do NOT select the entry up to which the data in your BW system is still correct, rather select the entry before that.
           Save the changes.
Do not make any further changes in the BWOM2_TIMEST table.
               The next delta extraction uses the date + 1 of the selected entry as a lower limit for the data selection.
You can control the upper limit for the data selection by changing the ' BWFISAFETY' parameter in the BWOM_SETTINGS table. The upper limit is determined using the current date minus the value of the 'BWFISAFETY' parameter (default = 1).
If for example you want to extract the data of the last twenty days in four parts, set the parameter in Transaction SE16 as follows:
before the 1. delta extraction > > BWFISAFETY = 15
before the 2. delta extraction > > BWFISAFETY = 10
before the 3. delta extraction > > BWFISAFETY = 5
before the 4. delta extraction > > BWFISAFETY = 1 (= default)
                and parameter BWFIOVERLA = X to return to the originaldelta mode.

FI Line Item Data

Hi,
I have report against FIAR line items data(0FIAR_O03).The purpose is to report at Customer level for aged trail balance amounts(only for charge back amounts).I have the report ready and restricted document type only with CB- charge back.But the problem is,on the R/3 side for some CB accounts,there is a reference amounts like Credit memos or Customer Payments(document type DZ and DG).How can get these refrences into my report when i restrict the report only with CB.So under charge back ammount,the user should be able to see the associated Credit memos and Customer Payments as in R/3.Thanks for the help.
Ravi.

Hi Revathi,
Kindly find the answers below :
1.How the table BWOM2_TIMEST will work for delta & what is the selection will happen at BKPF-CPUDT
Basically, BWOM2_TIMEST will show you the Last Time stamp for both Init and Delta..
Whenever you will do an Init load.....automatically an entry will take place in this table.....and you will see a "X" sign in the field "LAst TS"....
Also for Delta...there may be N number of entries with Update mode D....but only for the latest delta you will see a "X" sign in the field "LAst TS"....
With Financial Accounting line items that have been posted in the SAP R/3 system since the last data request, the extractors identify the following delta dataset using the time stamp in the document header (BKPF-CPUDT).
2.How the tbale will wok BWOM_SETTINGS for delta
With these settings your delta extraction uses CPU date of recording records in table in R/3 to define your security interval with at least 1 day
This means that your data is loaded until the actual day - 1.
You can check the SAP note : 485958
Regards,
Debjani..

Fi Extraction and BWFIOVERLA

Hi All,
I have a question regarding FI Extraction.
The issue was that we have the FI extraction in our system which brings in data once a day, while we wanted to increase the frequency of this load.I checked SAP note 485958. It suggested some enhancements in BWOM_SETTINGS.
But I could not understand where exactly the change needs to be done and how??
Pl help me with the steps.
Also, I believe if BWFIOVERLA is set to 'X' then you can get the delta until the previous day(that is until yesterday) but if it is left blank then you can get delta until day before the previous day that is until day before yesterday.
In our system we have this as blank. What will be the consequences if I set it as X? For example, if I check BWFIOVERLA as X, then how will it affect my tomorrow morning's loading??
Thanks and Best regards,
Sharmishtha Biswas

Hi,
Hope the value of Parameter BWFIOVERLA is actually depended on parameter BWFITIMBOR in table BW0M_SETTINGS.
The default Parameter value of the parameter BWFITIMBOR is 2:00 AM.
Case 1:
If the data extraction started before 2:00 am of particular day (10.04.2007) the data selected will be upto day before the last extraction run. If last extraction completed by 09.04.2007, 00:50 am. Then the data extracted will be upto 08.04.2007, 24:00 Hrs. Because of parameter BWFISAFETY (value = 1 Day).
Case 2:
If the extraction is started after 2:00 am, then the data extracted will be upto 09.04.2007, 24:00 Hrs.
To overcome the case 1, we maintain the parameter BWFIOVERLA (value x). So that if you extract the data before 2:00 am of 10.04.2007 also, you can extract the data upto 09.04.2007, 24 Hrs.
Regards,
Vishwanath.
Message was edited by:
Vishwanath H.E

BWOM_SETTINGS

Similar Messages

Maybe you are looking for