No records in delta extractor after change

We have a generic delta extractor that is based on ztable filled by a scheduled load program.
Last week I changed some records and then ran the transaction to fill the table and the program correctly filled the table and the extractor had the delta data.
I then extracted a delta init to an ODS in BW where I had to manually change the QM status of the load from yellow to green and got the status messages that the timestamp had changed from 0 to xxxxxx
Now after this init delta load, I went into R/3 again and changed the records.
Ran the transaction to fill the ztable but no records come up in there.
Also the extractor has no delta records.
In VBAP I see the changed items but in 2lis_11_vaitm, no delta records.
Any thoughts?
Edited by: CC on Jul 1, 2008 12:33 AM

Hi,
We have a generic delta extractor that is based on ztable filled by a scheduled load program.
Now after this init delta load, I went into R/3 again and changed the records.
Ran the transaction to fill the ztable but no records come up in there.
Also the extractor has no delta records.
If I understand correctly, the load program did not add any records to 'ztable'.
If that is the case the extractor running off 'ztable' would not deliver any delta records as there is nothing to deliver.
If my understanding is right you should revisit the load program of 'ztable' to see why it is not filling 'ztable' table as you expect.
BR/
Mathew.

Similar Messages

Problems Delta Extractor after Homogeneous Source System Copy

Hi,
We have R/3 system landscape HUD, HUQ, HUP. And we have BW system landscape BWD and BWP.
We connect BWD to HUQ and BWP to HUP.
We made a homogeneous system copy from HUP to HUQ.
We haven´t made any homogeneous system copy from BWP to BWD.
We have applied the next OSS note after source system copy:
325525 Copying and renaming systems in a BW environment
184322 Procedure after DB copy of BW source system
184754 Procedure after BW database copy.
But we have problems in our BW Development (BWD), and we have the next Dump "MESSAGE_TYPE_X" when we can change any delta infopacket, the next text are from Dump:
"MESSAGE_TYPE_X" C
"SAPLRSS1 " or "LRSS1F11 "
"RSM1_CHECK_FOR_DELTAUPD"
I think that the problem is about inconsistencies between RSSDLINIT/SEL tables in BW side and ROOSPRMSC/F tables in R/3 side.
Please could you tell how can i solve this Dump, because i can restrart and initial and delta packet for different Datasource and i can´t do anything.
Thanks in advanced,

Hi,
We are upgrading our R/3 system from 4.7 to Ecc 6.
While copying database tables we are using Clinet Carrier tool which is considering only clinet dependent tables. Hence we are loosing our BW delta queue entries in RSA7 of ugraded system.
We found ROOSPRMSC and ROOSPRMSF tables and copying these 2 tables may resolve the issue and We copied and delta went fine.But we are not sure of only these are the tables to be considered.
Please let us know what are the relevent tables to be considered to make the Delta to work while copying Data base tables from one system to another.
Thanks in Advance
Regards,
R@ngzz

Delta Extractor Is not picking changed values

Hi All,
When the values or texts in a PO are changed the delta extractor is picking up the changed values as deltas (provided the changes where done in PO Header or Item Overview) but when a PO values or text that are changed in the Item Details the delta mechanism is not picking up the changed values (the fields whose values are changed were initially not in the LO Cockpit Extractor they where added and the values to these fields are populated using an ABAP Program)
Is there a reason that Delta mechanism doesn't work for fields that are not delivered by the SAP Extractor or do we need to modify the code in order to collect these changed values by Delta Mechanism (Direct Delta as the Update Mode).
Please let me know if anybody came across the same problem .
Thank you all in advance.
Regards,
Dhanam

Hi,
this is another story.....
You'll have to
- enhance the PO items table (EKPO) with your fields
- activate the right customer exit for purchase orders (search in SMOD; or in this forum..) and populate your fields during this exit. if the field needs to be maintainable by the R3 user, you'll have find a SAP exit (again SMOD) in order customize one of the screen and populate your fields in R3.
- use another exit to populate the new fields to LO delta queue
- enhance your BW extract structure (done)
- and so on...
As you can imagine, the above get quite more complicated (an expert in MM shall support you) and it needs to be approved by the PM since you'll modify R3.
But that's basically it!
hope this helps...
Olivier.

Trigger workflow after change of control record(pa03)

Hi Experts,
Is it possible to trigger a workflow after change of the control record - transaction pa03?
Thanks,
Agata
Edited by: Agata Nowak on Sep 14, 2009 12:43 PM

Hi,
Thanks for replay but:
1. just so the event or action in PA03 , on which you want to trriger WF ,Before that with TCOde swels switch ON , then afer the action in SWEL , you wil find if any BO and event is there for that action . if so , then using this you can trriger you WF. if not
I've already tried this and no event is triggered ;(.
then
2. you can go for user exit , badi or enhancement spots (verson ECC.6.0 above). in that using SWE_EVENT_CREATE creat the event to start yr WF.
I've been already searching for BADI or user exit but I really can not find any user exit nor badi for this transaction (in fact it is SAPMP52X Program) ;-((
Thanks,
Agata

Changes In Business Content and Extractors after r/3 upgrade

Hi All,
We are in the process of upgrading from R/3 4.0b to ECC 6.0.
with the BW system bein upgraded to BI 7.0
Question.
What changes would occur for the business content and extractors after the R/3 upgrade.
Thanks in advace.
Regards,
Nikhil.S

Hi Nikhil
The datasources remain same, U can migrate them in BI side from 3.5 to 7.0 using RSDS -tcode.
All extractors remains same, Well it again depends on the service packs u r using.
Now the latest for BI is service pack 17 and for Business content patch is Patch 10.
U can find new datasources like 0FI_GL_14 and 0FI_GL_40 and many other queries.
In BI side
1.If you have update rules you will have to create transformations and there is no shortcut here ..if there are routines you will have to write them as well and change the syntax as some of the old syntax of 3.x is no more valid in BI 7.
2.Data loading concept changes as you can bypass the Infosource(but in few places you will need it actually like when you are directly loading from datasource to target and you want to read master data).
3.DTPs will be required..changes in the Process chains for the same.
4.Datasources need migration(first emulate them and test whether the Bi 7 loaidng is working or not otherwise if you migrate you will loose your transfer rule.
Reward if helped
thanks

Problem with 0FI_GL_4 Delta extractor

hi everyone,
I have encountered a problem when using 0FI_GL_4 delta extractor.
As I had changed the settings in table BWOM_SETTINGS according to note 485958, the datasource should be able to extract FI lines up to the day I run the extractor.
Here is the problem:
At 1st March, 01:18 am, I ran the extractor and get some records.
I found that FI lines with createdon date later than 29th Feb 16:00 were not extracted to BW. According to that note, shouldn't I get all FI lines created on 29th Feb?
After 30 minutes, I ran the extractor again. These records came to BW this time. That's strange.
My settings in table BWOM_SETTINGS:
     EXTLOG
     ORGSYSONLY
     NOTSSELECT
     OBJSELSIZE     X
     FLAG_AL
     OBJCURTYPE     10
     BWFILOWLIM     19910101
     BWFISAFETY     1
     BUFFERREF
     OBJSELSICO     X
     BWFITIMBOR     020000
     BWFIOVERLA     X
     DELTIMEST     60
     PRICECOMP     X
Thanks for your help!

Hi,
I agree with Murali as your are extracting data before 02.00 AM the data till yesterday will be extracted.
Check the below link for more information,
[http://help.sap.com/saphelp_bw33/helpdata/en/af/16533bbb15b762e10000000a114084/content.htm]
but as per your another post the second extraction happened before 0200, just cross check one thing that the time noted was not from local machine but was from app server.
Rgards,
Durgesh.

2LIS_02_ITM delta missing after good receipts

Hi everybody:
We are using 2LIS_02_ITM for extracting purchase order, in some cases, delta changes are not uploading to BW, it seems, when good receipt is posted.
We have found the note
Note 485650 - BW: Missing entries in delta queue after goods receipt.
But this note is for SAP_APPL 4.6 and our version is SAP_APPL 4.7 patcht level 14.
We have no be able to find a note for our release but we think that the poblem should be similar than described in that note, but any other clue is good received.
Thank you.

LBWE -- maintain Lo **** pit
Step by step
Go to RSA6 and check the availability of the data source
if data source is not available then go to RSA5 (all business content object available here) make a copy of the required DS.
RSA6 - check the DS is available or not..
lbwe - lo customising **** pit...
select required fields - hide - inversion...
do statistical setup run
login to bi
replicate DS..
go to info package
do initalization delta (Delta Q will be generated only after a successfull delta initializtion done. when you do the same system will load historical data from setup table after loading from set up table (init delta) delta Q will be get posted with records for all changes/creation which is happening in R/3 (related to MM) through events. )
i suggest you should go for unserialized v3 (store and transffer on demand )
1. V3 Unserealized ---unsort records
Unserialized V3 -> Update Q> (V3 Coll. Run)---> Delta Q
[When a transaction happends those delta will be get posted in Update Q, in order to transfer those record from update Q to Delta Q you should do V3 collective Run, (the process of loading data from update Q to delta Q is known as V3 Collective Run) ]
2. Qued Delta [SAP recommended]--
It will not sort record or stop record while transferring to to delta q but will continue until the whole record finish. it will have the track of failure record
3. Direct Delta --->Delta Q
it will directly post records to delta Q when transaction happends
hope it will help you
binu v. rajan

Support Package and Delta/Extractor functionality

Hello Experts,
We have been testing the New GL Totals Delta and Extractor functionalities. Previously when Support Packege 13 was installed, the Delta was bringing incorrect results.
Now we are using Support Pack 15. Now if i post documents in ecc and upload to bi, the Delta is working properly and values match in ecc and bi.
Could you please suggest if there have been any changes or upgradations in the New GL Totals Delta/Extractor functionality between Support Packages 13 and 15.
Thanks and Regards,
Labanya.

Hi,
Its always better to drain the delta queues before an upgrade.
As a standard practice we drain the delta queues by running the IP/ chain multiple times.
As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
See SAP Notes 506694 and 658992 for more details.
Page 17
Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
The SAP BW Service SAPI, which is used for internal and BW to BW data mart extraction, is
upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
upgrade to avoid any possibility of data loss.
upgrade preparation and postupgrade checklist
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895 [original link is broken]
OSS notes 328181 and 762951 as a prerequisites.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
/thread/804820 [original link is broken]
thanks,
JituK

Generic delta extractors without timestamp!

Hi,
For a certain requirement, I have to develop generic extractors which should be delta capable. But unfortunately the source tables donu2019t have a timestamp; hence I canu2019t create delta enabled generic extractors using timestamp. Moreover most of the tables are standard SAP tables, which are used across different modules so it is not possible to introduce timestamp in these tables.
I am working on extractors for Business Partners in SAP Transaction Banking.
I have got couple of options:
1) To use the change pointers by activating CNS service in source system. It is possible to activate the service and set up the segments for standard and custom tables, from where I need to extract the data.
2) To develop the function module and create the generic extractors using delta queue functionality.
Issues: In the first approach, I have created an extractor and it is possible to recognize the changed records. But the issue is I need some kind of flag which tracks the information regarding last successful delta extraction for an extractor based on change pointers and standard SAP table. I am not sure how does standard extractors maintains this status and picks up new/changed records in delta functionality. Not sure how to achieve this.
In second approach I am not sure if it is possible to create generic extractors using delta queue and what are the complexities involved.
If someone has already worked on these areas, any inputs are most welcome.
Thanks and Regards,
Amit

Hi Amit,
I haven't worked on SAP Transaction Banking but I hope you can get most of Business Partner data in standard extractors. Try to look for some.
If you have to go for Generic extractor. there are 2 options:
1. Use BTE
[How To Create GDS which uses Delta Queue|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b68b99-022e-2a10-999d-c4dc9ec24a59]
2.Use FM based GDS
[How to Create Generic Delta|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
[Generic Delta Using Funtion Module |Re: Generic Delta Using Funtion Module]
You can also look for some numeric pointer from RSO2.
Hope it will help you...
Regards,
Ashish

Custom delta extractor: All data deleted in source table in R/3

Hi everyone,
I have made a custom delta extractor from R/3 to a BW system. The setup is the following:
The source table in R/3 holds a timestamp, which is used for the delta. The data is afterwards loaded to a DSO in the BW system. The extractor works as expected with delta capability. Furthermore if I delete a record in the source table, this is not transmitted to the DSO, which is also as expected.
The issue is this however: If we delete all data in the source table, then on the next load there is a request showing 1 record transfered to the DSO. This request does, however, not show up in the PSA, and afterwards all data fields in the DSO is set to initial.
Does anyone know why this happens?
Thank you in advance.
Philip R. Jarnhus

Hi Philip,
As you have used generic extractor I am not sure how the ROCANCEL will work but you can check the below link for more information,
[0RECORDMODE;
Regards,
Durgesh.

Transformationsde-activating after changing write optimized to standard dso

Hi experts,
i changed write optimized dso to standard dso because of some changes, but after changes done i activated the changed transformations standard dso(previously write optimized), but it is not activating , after gone through the issue its happened
because of 0 record mode, i deleted the 0 recordmode rule and activated.
Now the real issue:-
when i transport this changed dso and transformations from dev to acceptance test am facing this issue below are the details.
Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode)
Transformation 0MX1MHVGBT0A0PTA526YRW3O48Q77GOC deleted in version M of DDIC
Transformation 0RKZY5AKAWMJ2ZRKJMSZO791UP6X1F2N deleted in version M of DDIC
Activation of Objects with Type Transformation
Checking Objects with Type Transformation
Checking Transformation 0MX1MHVGBT0A0PTA526YRW3O48Q77GOC
Rule 10 (target: 0RECORDMODE group: 02 Technical Group ): Constant is initial
Checking Transformation 0RKZY5AKAWMJ2ZRKJMSZO791UP6X1F2N
Rule 10 (target: 0RECORDMODE group: 02 Technical Group ): Constant is initial
Saving Objects with Type Transformation
Internal Activation (Transformation )
Preprocessing / Creation of DDIC Objects for Transformation 0MX1MHVGBT0A0PTA526YRW3O48Q77GOC
Preprocessing / Creation of DDIC Objects for Transformation 0RKZY5AKAWMJ2ZRKJMSZO791UP6X1F2N
Please help me in this by rectificying in dev system how could i manage to send this transport to acceptance test.
One more thing even after deletin the 0recordmode in transformation , i can able to see that in techinical group.
cheers
vas
Post Processing/Checking the Activation for Transformation 0MX1MHVGBT0A0PTA526YRW3O48Q77GOC
Transformation 0MX1MHVGBT0A0PTA526YRW3O48Q77GOC was activated

Hi
You can change write optimised to satndard DSO.
You are supposed to add 0recordmode field in datsource check below links for clear information:
error while activating transformations
Re: Transformation error.
Ravi

Inbund IDOC error: Status records with status 51 after status 53

Hi all,
I'm looking to resolve an issue related to posting an inbound IDOC. when I process inbound IDOC created from report prg I'm getting a status message: "Status records with status 51 after 53" .
Functionality: I'm creating an IDOC from flat file and processing it to post Customer master data into SAP. During this process creation of IDOC is successful but when I'm changing the existing data record (customer master data) IDOC is throwing this error.
Changing data: For changing existing data I'm passing KUNNR field and overwriting the remaining data. Even though the idoc status is 51 the changed data is getting posted in to SAP. Here my concern is to see IDOC status as 53.
Regards,
Ganesh.
Edited by: Ganesh Sunkara on Aug 1, 2009 3:45 AM

Hi all,
I solved this issue by myself. There is an error in the user exit code.
regards,
Ganesh.

BIA Master Data Index Not Updated After Change Run

In BIA it shows master data 0VERSION table /BI0/SVERSION has 360 records which matches with the number of entries in SE16 /BI0/SVERSION. One record was added to 0VERSION so now SE16 /BI0/SVERSION shows 361 records. I did a change run for this infoobject 0VERSION but the BIA index for /BI0/SVERSION still only show 360 records. I expect it to show 361 records after the change run. Is this a bug? Thanks.

Hi Thao,
I see one of 3 possible scenarios:
1) You load 0VERSION as a part of master data load (from flat file or another system). You see your 11th record in version "M" after load and then you run change run that makes "A" version of the record. ---> BIA index should be automatically updated. If not - open OSS message to SAP.
2) You load transactional data in an InfoCube, and it has new value for characteristic 0VERSION. ---> In this case you need to run roll-up of this new load request in the InfoCube to let BIA index be in-sync.
3) You are modifying 0VERSION manually (e.g. SQL INSERT statement), so system is not aware of new record at all. ---> You need to run the mentioned single-table-index program to update BIA index.
Is it any of these 3 scenarios, or you have the 4th one?
Regards,
-Vitaliy
Edited by: Vitaliy on Aug 19, 2008 1:59 PM

How a new output message will be created automatically after changing a PO?

Dear friends,
How to generate a new output message automatically after changing a PO and saving it?
Thx & Regds
Amitava

Hi,
System only takes automatically the Output message in PO in creation mode in ME21N ( Only if you have maintained the condition record MN04)
If you have not maintained Condition record in creation of PO also you need to maintain manually.
But once you changed the PO system will not automatically pick up the new Output message, you have to manuallly input the Output messages in change mode of PO - ME22N.
You can also use ME9F for this.
rgds
gsc

How to find "menge" in "me21n" after change?

How to find "menge" in "me21n" after change?
The user create new order in me21n,
He insert new quantity ( for example 105 ) ,
And after it ( he change to ) 106 ,
i want to see those 106 parts in user exit MM06E005 (exit 6 , 7 , 8 )
But i see the old input of 105 parts and not the last input 106 parts ,
The structures of the exit not supplies this data ,
so , in which parameter/structure/memory I can find it ( in the exits ) ?

i am talking about creating order , new one ,
i insert the data and expect to see the data ,there is no order number or line and no database record .
the tables in the exit just keep the change befor
the last one .
for example , i put in the quantity 109 and now 110
i see the 109 , where i can see the last input ( 110 ) ?
thanks any way .

No records in delta extractor after change

Similar Messages

Maybe you are looking for