No purchasing date in delta extraction (2LIS_02_ITM, 2LIS_02_SCL)

Hi.
We have been experiencing some issues with delta extraction of purchasing data, using 2LIS_02_ITM and 2LIS_02_ITM.
In particular, the posting date's field (BUDAT) is not always filled: for example, I noticed that when users set the final delivery flag even if the purchase delivered quantity does not correspond to the whole order's quantity or the flag has been set later than the change of the delivery date, the field (BUDAT) in the delta queue is not filled.
By this way, the field may be overwritten: however, we need to keep the posting date value.
I am wondering whether I am correct and, in this case, it is possible to keep that value: however, it seems that the only way is to use a full extraction of data.
Thanks a lot

Roberto Negro,
While filling setup table by using T-code OLI3BW (Purchasing) it is taking very long time.
Please let me is there any way to rerduce this time.
We are at BW 7.3 version.
Regards,

Similar Messages

Data with delta extraction.

Hi Gurus
I want a small clarification regarding data with delta extraction.
If today the data is extracted from r/3 system with delta to ODS object and the data is activated and datamarted to another ODS and Cube.
Now if tomorrow the same records had changes how will the old data will be changed i.e in cube if we compress the old data what is the scnerio.
Can anyone explain in detail starting from Delta queue to change taking place at cube.
Regards
Raju

Raju,
Don't worry about compression of Cube... Even if you do delta after compression, nothing to worry about Data. Next time you compress it, it will Make 1 record.
Assume...
Initially... in ODS Document 45000001 Item 0001 qty 10 Amount 20
in Cube Document 45000001 Item 0001 qty 10 Amount 20 (After compression)
Qty changed to 5...
In ODS Document 45000001 Item 0001 qty 5 Amount 10. This record will create 2 delta records to Cube.
that is looks like this...
Document 45000001 Item 0001 qty -10 Amount -20 Record mode ' X' (Before Image)
in ODS Document 45000001 Item 0001 qty 5 Amount 10 Recordmode ' " (After Image)
Finally cube contains...
Document 45000001 Item 0001 qty 10 Amount 20
Document 45000001 Item 0001 qty 10 Amount -20
ODS Document 45000001 Item 0001 qty 5 Amount 10
If you compress cube... you will endup with last record.
all the best.
Nagesh Ganisetti.

LO Extraction - Help required to load missing Purchasing data

Hi,
We are using 2 Data Sources: 2LIS_02_ITM & 2LIS_02_SCL to load the Purchasing data in to Info Cube: ZPUR_C01. While comparing the Invoice Amount for the periods 11.2007 & 12.2007, we found the variation between BW and SAP R/3 data.
In this scenario, do we need to delete the set up tables and fill the set up tables in R/3 side and perform RE-INIT of InfoCube in BW side?
OR
There is possibility to load the data in set up tables in period wise in R/3 side? If it is possible, i can delete the data from InfoCubes for the periods 11.2007 & 12.2007 using Selective deletion and load the data in to InfoCube for the same periods. Please let me know.
Thanks & Best Regards,
Venkata

Hi Venkat,
First you need to know how ur period is derived, is it based on (EKKO-AEDAT) or (EKPO-AEDAT). If period is derived from EKKO-AEDAT you can delete data from cubes period by period and have to fill setup tables based on Doc. date for those periods. And you have to do full repair loads. Make sure that during that time no one creates/changes/GR/IR for those period PO's. Otherwise they again comes in delta load and values will be summed up.
hope this will help.
Thanks, Vamsee

Error while doing DELTA Extraction (generic data source)

Hi BW Experts,
In my R/3, I have a generic data source ZBUT_VW.
It receives data from a View which is created based on couple tables.
When I do full load to the corresponding ODS, it is successful.
But after that I delete the ODS and created CUBE with DELTA
I have Initialized delta.
When I do DELTA extraction, it fails.
The error The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
and/or
the maximum wait time for this request has not yet run out
and/or
the batch job in the source system has not yet ended.
I delete the initialization load and trying to do DELTA extraction again and it Fails.
With the same error
Please let me know how can I resolve this problem.
URGENT
gaurav

I dont think it is possible to have to additive delta with creation date.
Try a full load to cube to check if the extractor is working.

Delta extraction for FI (AR & AP) data sources

I tried extracting the data from 2 standard SAP data sources under FI module for Accounts Receivable.
0FI_AR_10(Customer payment history via delta extraction)
0FI_AR_5 (customer payment history)
The data to be extracted into 0FIAR_C05(payment history) info cube.I assigned the 2 data sources to an info source and pumped the data into the cube via an ODS.Now the problem is with delta extraction.No records are picked in the delta extraction.So I checked in extractor checker RSA3 with delta update mode.I got the following error.
"Could not determine BW release of logical system"
Could some one resolve the issue?Thanks in advance.
Thanks & Regards
Vinay

Hi ,
Please go through 493422 note once . see if suits to your requirement follow it accordingly .
Thanks ,
Anil

Extraction, Flat File, Generic Data Source, Delta Initialization

Extraction, Flat File, Generic Data Source, Delta Initialization
I have couple of questions regarding data extraction.
1.     If you have Data Source a Flat File e.g. Excel file I know that you have to create Data Source at BW side. How do you upload updates, by selecting Delta Update when executing next Data Load? Do you ever u201Cconvertu201D this Excel file into Application Tables to become SAP Source 
2.     Can you please give me example of situation where you had to create Generic Data Source? What is difference between Time Stamp, Calend. Day and Numeric Pointer. Which one is most common to select?
3.     I read somewhere that Generic Data Source does not have Setup Table. I thought that you have to have Setup Table in order to load transaction Data otherwise you will lock the Application Tables. Where am I going wrong im my thinking please?
4.     What are steps in terms of IP before, under and after Delta Initialization. I belive that you can do two ways:
Full Update - Initialize Delta Process (without Data Transfer) u2013 Delta Update or
Initialize Delta Process (with Data Transfer) u2013 Delta Update
Am I right? What is most common method and why?
5.     If you want to add a filed in Data Source after 6 month using it, you want to do it without re-init Delta Queue. You add field in RSA6, then provide info for ABAP to populate new filed (info u2013 name of Data Source, Extract Structure, field added, name of Application Table which contains the field). How does it work now as there is no SetUp table it has been deleted after Initialisation? How does Delta Queue know that it is going to receive data which has been expanded by one field or it may does not need to know at all?
THANKSSSSSSSSSs

Hi,
1. If you have Data Source a Flat File e.g. Excel file I know that you have to create Data Source at BW side. How do you upload updates, by selecting Delta Update when executing next Data Load? Do you ever u201Cconvertu201D this Excel file into Application Tables to become SAP Source
Once you create Datasource for A flat file extraction then it is file source system specific hence you cont change to Application table source Data source
In info package you can change the source as application server instead of desktop no need to change the DS
2. Can you please give me example of situation where you had to create Generic Data Source? What is difference between Time Stamp, Calend. Day and Numeric Pointer. Which one is most common to select?
When we don't find any standard extractor then we can go for Generic(if i want information sales along with finance information in a data source then generally we dont get standard one hence we can go for generic DS)
Check the below link for More about generic DS .
http://wiki.sdn.sap.com/wiki/display/BI/Generic+Extraction
for Delta capturing you can use
Timestamp(if the table has time stamp filed so it can stamp the last changed record in that table hence it is easy to get delta based on the time stamp)
Calday- (If the table doesn't have the Timestamp filed then search for Calday where you can stamp the delta based on the date when documents are changed )
Numericpointer : If the table doesn't above both then we go for this option where you can the numeric value change stamp )
3. I read somewhere that Generic Data Source does not have Setup Table. I thought that you have to have Setup Table in order to load transaction Data otherwise you will lock the Application Tables. Where am I going wrong im my thinking please?
Generic datasource nothing but we extracting data directly from the database table without any interface between the application/systems
4. What are steps in terms of IP before, under and after Delta Initialization. I belive that you can do two ways:
Full Update - Initialize Delta Process (without Data Transfer) u2013 Delta Update or
Initialize Delta Process (with Data Transfer) u2013 Delta Update
Am I right? What is most common method and why?
Correct
5. If you want to add a filed in Data Source after 6 month using it, you want to do it without re-init Delta Queue. You add field in RSA6, then provide info for ABAP to populate new filed (info u2013 name of Data Source, Extract Structure, field added, name of Application Table which contains the field). How does it work now as there is no SetUp table it has been deleted after Initialisation? How does Delta Queue know that it is going to receive data which has been expanded by one field or it may does not need to know at all?
Once you add the new field to structure(DS) you will get the data as on date onwards not historical data hence what is the concept of setup table ( delta records come from the Delta Que not from the setup table )
If you want histaric data to new field then you need to setp table deletion ...etc...
Hope it is clear..
Regards,
Satya

Purchasing Data - 2LIS_02_SCL

Hi Experts,
We are loading the purchasing data from SAP R/3 data soiurce 2LIS_02_SCL. The PO raised in the local currency(JPY), then while PO generation it converted to order currency(USD). In the extractor filed BWGEOO posting the confirmation value which is calculted by current exchange rate table WKURS. But i do not want chk this PO values with the exchange rate.
So can i use the field BWEFFWR(Effective Purchase Order Value) for goods receipts values. Please provide your suggestion. because i am receiving this filed in the BW end and value looks fine(i mean, not using any exchange rate)
calcultion:
BWGEOO u2013 Purchase Value in Order Currency
bwgeoo = eket-menge * ekpo-effwr / ekpo-menge.
bwgeoo = Schedule Line Quantity * Effective Price / Item Quantity
For goods receipts, the following applies:
bwgeoo = bwgeo converted using WKURS
Advance Thanks.
RR.

Hi Gopal,
You can refer the below SAP Link for the 2LIS_02_SCL.
http://help.sap.com/saphelp_nw04/helpdata/en/8d/bc383fe58d5900e10000000a114084/content.htm
Currently we are using the BWGEOO u2013 Purchase Value in Order Currency in goods receipt amount.
The PO raised in the local currency(JPY), then while PO generation it converted to order currency(USD). In the extractor filed BWGEOO posting the goods receipt amount which is calculated by current exchange rate table WKURS. But i do not want calculate the goods receipt amount with the exchange rate.
In the same extractor field called BWEFFWR(Effective Purchase Order Value) which also post the goods receipts amount.
So can i use the field BWEFFWR(Effective Purchase Order Value) for goods receipts amount instead of BWGEOO field.
Please provide your suggestion. because i am receiving this filed in the BW end and value looks fine(i mean, not using any exchange rate). Now the problem related to the goods receipts amount. Please refer the above link for filed BWGEOO & BWEFFWR calculations.
Advance Thanks.
RR.

Generic Data Source delta is not extracted

Hi,
There is a problem in extracting the delta records using Generic Data Source. Delta records ( New / Modified records ) are not posted in the RSA7.
I'll Explain you the Scenario I have done. Created a generic data source in R/3 using view. In the view there is a field Sales Order No. I have enabled the delta update for this field. In the generic delta i have chosen delta type as Numeric pointer.
Extracted the entire record using full update and after initializing the Delta, it extracts the delta record well ie. it only extracts the sequence of Sale Order No. First I extracted nine records(i.e 10001 to 10009) using full update. again I entered a record in underlying table with sale order no as 10011-10013. It extracts those records into BW system. Then again I made an entry in the table with sales order no 10010. But the record is not extracted. Even though I tried of specifying safety lower limit as -3. Still it not extracting the record(10010).
And what if I posted a value of sale order 10014 with the same. what should I do?? Help on this plz.
--Durai.S

Hi SVS,
Thanks for your reply.
I followed this in my scenario. But I don't understand why it is not extracting? even I specified the safety limit of upper and lower values in the generic delta.
Here the below explanation shows that the delta record can be extracted even if the pointer value is greater than the posted value.
Numeric pointer (last extracted value 10011; Data in underlying table (Max value = 10025) )
Data would be extracted from a min-value of 10010 (lower limit adjusts the last counter 10011 by specified value u2013 1)
max-value of 10020 (after adjustment for upper safety limit u2013 by 5). The current pointer would now indicate 10020 in
RSA7.
--Durai.S

Problems with Delta Extraction for 0CRM_OPPT_H (no data found)

Hi,
I've some problems with the Delta Extraction of the Infosource 0crm_oppt_h (CRM Opportunities Header). After initialization I get no delta data from the CRM system.
What I already did:
Activated 0crm_oppt_h Data Source (checked functionality with rsa3)
Started Info Package (Init) on BW side (worked fine)
Checked the status of the Data Source on the CRM system using BWA7 ("initial upload" is unmarked; "delta active" is marked and what makes me worry is that the column "Queue exists" in <i>unmarked</i>...)
If I change anything (like Phase, Expected Sales Vol.) in the opportunity, the Delta Extraction get no changes.
Could You help me out, please?
Best regards,
Markus Svec

hi Markus,
try to check oss note 788172
Release Status Released for Customer
Released on 23.03.2005
Priority Correction with high priority
Category Program error
Symptom
No data exists in delta extraction from the CRM server to the BW system for business transactions, if parallel processing is applied as per note 639072. But Data is extracted if parallel processing is switched off.ie. when BWA_NUMBER_OFF_PROCESSES is set to 1,there is data during delta. This applies to the following DataSources:
0BBP_TD_CONTR_1
0CRM_COMPLAINTS_I
0CRM_LEAD_ATTR
0CRM_LEAD_H
0CRM_LEAD_I
0CRM_OPPT_ATTR
0CRM_OPPT_H
0CRM_OPP T_I
0CRM_QUOTATION_I
0CRM_QUOTA_ORDER_I
0CRM_SALES_ACT_1
0CRM_SALES_CONTR_I
0CRM_SALES_ORDER_I
0CRM_SRV_CODES
0 CRM_SRV_CONFIRM_H
0CRM_SRV_CONFIRM_I
0CRM_SRV_CONTRACT_H
0CRM_SRV_PROCESS_H
0CRM_SRV_PROCESS_I
Other terms
DataSources, BWA, initial extraction, delta init, parallel processing, no data in delta.
Reason and Prerequisites
There is an update on the generated delta table which causes data corruption in running delta initializations as the changed delta sets will be deleted with every further update on documents. An open cursor statement is there without fetch data in SMOX3_GET_DATA.
Solution
The problem is solved with the attached corrections.After applying the corrections a new initialization of the affected datasources is necessary.

Delta extraction of modified data in already closed periods

Hi everyone,
we're currently facing a scenario where data in BI does not seem to match R/3. We're using the business content extractors 0ec_pca_3 & 0ec_pca_4 to get data for a balance sheet report, but some of the figures don't match. The client currently uses periods 001 - 013, in other words they have one special period. After much investigation and discussions with the users, we found out that the client sometimes goes back and makes changes to periods that have already been closed. For instance, period 013.2007 is closed in R/3 (and loaded to BI), at some point in 2008 the client "reopens" the period and modifies the data. This data does not seem to be picked up by the BI delta extractor. So our theory is that the two systems don't balance because of this late period modification. My questions are:
Is it part of standard SAP FI process to re-open an already closed period and add/change/delete data?
If so, would this changes be picked up by the standard delta extraction? If not why and is there anything we can do to achieve this?
If not part of standard process, what would the solution be? We've suggested to potentially create a separate period, say period 014, for these changes? Would this be a recommended way forward?
Thanks for your time.
Cheers,
Dion

0EC_PCA_4 does not support delta right?
Have you already checked contraints mentioned in these links?
http://help.sap.com/saphelp_nw70/helpdata/EN/5d/ac7d8082a27b438b026495593821b1/frameset.htm
Can a full load for the missing records be tried?
Also look at Note 577644

ALE delta extract for HR master data

We want to create some R/3 delta extracts based on the HR PA* tables using the ALE delta extract function of generic extractor. Has anyone done this before? Are there any OSS notes or documents that I should look at? Thanks!

Hi Bill Faison,
This is very old message. I think your problem must be solved. If it is not then: yes we can extract Data from R/3 with ALE Delta .
You have to perform below steps.
1.     In your Table you need to activate ALE change   pointer.
2.     Create change documents for required table.
3.     Created Generic Extractor with ALE Delta.
Hope this will help.
Let me know if you have any concern or issue in this regards
Best Regards
Sharad Verma

Master Data Delta Extraction

Hi,
I have a BI 2004's.
I tried to do a delat extraction but it does not work, apparently we have to active the change pointers and config an ALE. Do you know some How To or Best pactrice to configure the Delta extraction for master data.
Thanks a lot.
Eric

Hi Mauricio,
maybe it depends by the number of records in delta quque. If you have a daily lot of changes in a Master Data the system is no more able to extract the data in tables for change pointers. Also maybe that you have to cancel entries on the tables of changed data.
Check the quantity of delta records for every day, and then check also if it is possible to update this master data frequently.
Ciao.
Riccardo.

Generic Delta Extraction (Bill Plan Data)

Hi BW Gurus,
We need to cerate data source from Bill plan extractor.
Please note that there is no SAP standard extractor for the bill plan data. So that is the reason we are using generic extractor (RSO2). We were using sales order delta extract program to find out the changes in bill plan data and there was routine in that extract which updated the custom table. But, soon they have to get rid of this design, because they observed that all the changes being done to bill plan were not being captured in the sales order delta extract. So, they have to go ahead with a full extract instead of the delta extract for bill plan data. Now we need to create design so we can do a delta extract on the billing plan data.
Please advice me ASAP.
In Advance Many thanks for your help.
Regards
SAP Team

You could use the date field instead , you could have a lower safety interval and then when you do the delta again the records included in the lower safety interval are included. As for delta with timestamp , I have a question what is the timestamp used for delta - is it UTC Timestamp or the date and time concatenated together. UTC Timestamp did not seem to work for me and I did not have the luxury of having a concatenated timestamp.
When I checked the base tables for delta maintenance , I found both timestamps and am confused as to what timestamps to use.
Arun
P.S I have a current delta with changed date and a lower safety interval of 1 day and it is working fine so far.

Purcahsign data tables for the extractors 2lis_02_scl and 2lis_02_itm

Hi,
Can any one tell in which tables the purchasing data is stored in R/3
Thanks in Advance
Dru

Hi........
EKKO >> Purchase document
EKPO >> Purchase document (item level)
EKPV >> Shipping-Specific Data on Stock Tfr. for Purch. Doc. Item
EINA >>Purchase info record (main data)
EINE >> Purchase info record (organizational data)
EBAN >> Purchase requisition
EBKN >> Purchase Requisition Account Assignment
T024 >> Purchasing Groups
EKET >> Scheduled lines
EKES >> Vendor confirmed lines
Regards,
Debjani......

3FI_SL_C1_TT - Procedure of extracting data with delta

Dear experts,
I try to load FI-SL data with delta.
We use extractor 3FI_SL_C1_TT and have implemented the start routine from note 577644 to create 0balance within the transformation.
Delta is only available for actuals so we select data only for valuetype 10 as recommended.
I read that I have to do a full update of the closed periods.
To load the carryforward from 2014 I have to select 000.2015 and load it with a full load.
Till now every thing is clear.
But what are the next steps?
What do I have to select within the infopackage for the init load of the open periods (current year)?
After executing the init load: how do I have to define the delta load?
Thanks for your help.
Best regards
Mirjam

Hi Leszek,
we use cube for each year.
So when the periods of the previous year (2014) is not closed, too, I have to work with them
the same as with cube for current year and do at first an init for the whole year and after that a Delta for whole year.
For current year cube I try do init/Delta with 001.2015 - 016.9999. But what do I do with the carryforward -
I can´t do only once a full, case with every new data record for 2014 it will Change.
What is the best practise with carryforward in this case?
Regards,
Mirjam

No purchasing date in delta extraction (2LIS_02_ITM, 2LIS_02_SCL)

Similar Messages

Maybe you are looking for