Delta not reflecting in Queue (RSA7)

For testing purpose we posted some FI documents in R/3(Devlopment) side using tcode F-02
after that we used tcode RSA3
DataSource: 0FI_GL_4
Update mode: D
Target System: BIWXYZ
after extraction we could view the posted enteries...
after 1 day(As FI data gets available in queue after 24hrs) we tried to view the same in delta queue using tcode RSA7 but its not being reflected over there
any clue???

Hello Alok,
RSA3 picks the record from the delta queue which in turn for the FI data source shows the records which are part of delta.
FI data source do not use the delta queue and store records into that like LO data source
There are delta is triggered by the API's....that is at the time when the infopackage is scheduled in BW the delta entries are pulled based on timestamp and before that they are not stored anywhere separately.
So the entry in delta queue for FI data sources tells that init is done for the data source and delta can be scheduled...but there is no such mechnisam or periodic jobs to push the records from the FI tables to extractors as in the case of LO data sources and where we see the records in RSA7...therefor wwe dont see records in delta queue for the FI data sources and this is how FI data sources are designed.
once the delta is scheduled then the records are kept for the purpose of repeat delta and this most probably you can see if you use the delta repetition in RSA7 display...but i think its not possible even there..
Thanks
Ajeet

Similar Messages

Delta not reflecting in ODS

Dear All,
I am pulling data from Ztable (R/3) using generic extraction. The data is on planned production. The fields are YEAR,MONTH,WEEK, UPLOAD-DATE , MATERIAL,QUANTITY. The R/3 user uploads a flat file every month into this Ztable. During the month if changes in data are to be done.He deletes the recent upload and makes changes in required fields and re-uploads the file into Ztable. The only changes he does are in the QUANTITY Field. In R/3 the generic datasource I create , I use Generic Delta with "new status for changes records". I am confused which field I should use, UPLOAD-DATE or QUANTITY for "Delta-specific field". Whichever field I choose and test, I take this Delta into ODS. In ODS although when I take "INIT DELTA PROCESS" for a particular YEAR, I pull the all records pertaining to that year. But when the user changes info in ZTABLE hence-forth ,those changes are not pulled when I take further "DELTA UPDATE" into my ODS. Why is that?
Regards,
Ratish
[email protected]

Hi Ratish,
What is approximate data volume in Ztable ?? If its not significant then opt for full updload .
Second option is, if possible insert time stamp field in the Ztable and populate it with the timestamp of record change. Create generic extractor delta on the timestamp field.
Hope that helps.
Regards
Mr Kapadia
Removed

2LIS_04_P_ARBPL Delta not captured from extraction queue

I am using datasource 2LIS_04_P_ARBPL to load 0PP_C03 cube. I have setup init selections as follows
0PRODORDER     AUFNR     Order Number     6000000000     6999999999
0COORD_TYPE     AUART     Order Type     ZCP1
0PLANT     WERKS     Plant     1010
In short I have the selections for entire range of production orders for a given plant and order type.
I have populated setup tables, did init load with data transfer, activated the update in LBWE, scheduled V3 job, no issues here.
When we create new production orders they are available in extraction queue MCEX04, when V3 job runs it makes it to delta queue, available in RSA7, loads into BW when delta load is done.
Ths issue is when we TECO a production order (status marked complete) to same production order which we just loaded as delta, it does makes it to extraction queue MCEX04, but when V3 job runs it is not available in delta queue, RSA7. May I please know if this is standard behavior of this extractor or I am missing something? Why the same production order is now getting filtered by V3 job?
Any help will be appreciated.

Hello
I am also facing same issue.
but in my case, I not mapped 0recordedmode with rocancel in transformation.
My scenario : DS(2LIS_04_P_ARBPL) ---->DSO(Stranded DSO) ---> Info Cube. DSO and Cube is Z object.
In cube I am having 2 records: 1 is Correct and 2nd is bad(Minus or 0 values) record.
That bad records fetch in report with Minus or 0 values not correct one.
Please let me know if have any concern on this.
Thanks is advance.

Data source was activated and replicated but not showing up in RSA7.

Hello,
Data source was activated and replicated but not showing up in RSA7. At what point does the data source appear in the Delta Queue?
Thanks

Hi,
for LO,LIS,generic,FI data sources, delta records come from delta queue.
if u run the INIT in BW whether it may be success or not delta queue will be maintained in RSA7. and u can check the records in RSA7 or smq2.
when the init request goes to R/3 then it will maintains delta queue in RSA7.
assign points if it helps,
thanks,
pavan.

Deltas not picking up..

Hi experts,
In lbwe in job control i have scheduled a job for SD Sales. But when i checked the job in sm37 it was cancelled and the error message is:
Structures have changed (sy-subrc = 2).
In development for the datasource 2lis_11_vaitm we have enhanced the datasource and added 4 fields.
Now the problem is occuring in production.The datasource is active and when checked in rsa3 it is picking up values for the newly added fileds also.
How to solve this and schedule the datasource for picking up deltas ?
Thanks in advance..
Bhadri M.

Hi Bhadri,
1] Ask the respective team to stop the posting in R3 for the S&D area.. and u need to set the time frame for this activity as generally the down time shud be as minimum as possible. Before doing this one u need to analyze the data which has got blocked in SMQ1 or LBWQ.. this is depends on the way that ur V3.. if u are using the Queued then it will be there in LBWQ.. and if u are using the unserialized then it will with the SMQ1.. and if u are using the direct then it will be direct from the base tables to the Delta queue.
U shud not change the V3 mode without the proper knowledge.. .. so u need to make sure that u use the exising settings of the V3.. if u change the V3 type to some other .. then the posting will be moved from base tables to LBWQ or SMQ1 based on the type of V3 that u are going to select.
So make sure that u have the information about the data which is has got blocked.. for this u can check the base tables and in that u can check the documents from the date this issue has arised.. preferably u can take 1 days before the transport which has happend to till date.(both based on created on and changedon).. this clears both question 1 and 2.
3] For filling up the setup tables u need to delete the existing Setup tables data for this application(11).. and then u need to fill the setup tables for the missing document range or for the period range. once this is done in R3.. then u can take the repair full load to BW with the same selections(same as Setup selections).
4] once u have done the repair full.. then u can ask remove the down time... .. before this.. make sure that u have the proper V3 update for ur application.
5] after the down time u will get the data in LBWQ or in SMQ1 based on the V3 type... and u need to schedule the V3 job.. so that the data will move from here to the Delta queue RSA7.
and then u can schedule the delta loads normally.
If the existing data in BW is small for this application then u can look at filling the whole set up tables and then reload the content again..
As u have introduced new objects in ur DS and I hope u might have enhanced ur targets as well with those fields.. For getting the history to the new fields u need to take this setup tables filling anyway..
So plan the activities accordinly and then proceed further..
Make sure that u will take proper down time and also drain the queue before introducting the changes in the extractor level..
Thanks
Assigning points if the way to say thanks

CRM user status in delta not extracted

Hi,
In the delta load of datasource 0CRM_SRV_CONTRACT_H the custom added user status fields are not filled.
For extracting CRM (5.0) user statusses of Service Contract Business Transactions to BW (3.5) I did required CRM customizing in SBIW and appended extraction structure with fields and did Bdoc mapping in BWA5 (customizing CRM_BWA_MBDOC BAdI not required according SAP user status logic). The custom user status fields are defined as BWSTONE<i>xyz</i>.
Full load works fine, but in delta load the user status is not filled. It appears that the delta messages in the delta queue (RSA7) do not contain the user status, even when the delta is triggered by a user status change only.
Has anyone an idea what the problem can be? Or better: how to solve?
Thanks in advantage!
Kind regards,
Marinus

Note 793986 may help (at least in my case, even parallel processing is not used!).

Significance of delta update and repetition in RSA7

Hi all,
Can anyone explain me the significance of delta update and repetition in RSA7. Can anyone explain me with examples?
Thanks
Pooja

Pooja,
Repeated delta is to repeate last failed delta. In RSA7 last delta records available for repetition. But repeate can be done using infopackage only.
For more info related to RSA7 check: [Note 380078 - FAQ: BW delta queue (RSA7): Questions and answers |http://sapbwneelam.blogspot.com/2007/09/note-380078-faq-bw-delta-queue-rsa7.html]
Srini

2LIS_02_ITM deleted line items are not reflected in BW

Hi,
Our current Data flow 2LIS_02_ITM-->DSO-->CUBE.
I am analyzing a Invoice, When it is created 01.04.2014 it has got 10 Line Items and all the data is load to BW,Invoice with 10 Line items.
In ECC I can now see the same Invoice only got 5 line items and from change log I can see 5 line items are deleted on 15.04.2014.These changes are not reflected in BW.In BW invoice data still shows 10 line items.
If I perform setup table job and ECC RSA3 for that invoice I am getting only 5.
I believe it’s something to do with 0RECORDMODE,Can you please let me know how to fix this in BW.
Thanks

Yes this is a known behavior in case of deltas.
For Deleted line items Rocancel field will have an entry with R.
To handle this you need to map ROCANCEL field in Technical group of transformation (Between Datasource to DSO) with 0Recordmode.
Once you will do that then after activating the data in DSO it will nullify the records and deleted order or item will not appear.
Regards,
AL

LPA changes are not reflected fully in 2LIS_02_SCL

The changes done to scheduling agreement, schedule lines are not reflecting in 2LIS_02_SCL, and there by resulting errors in delta update in BI system.
For example
     LPA     RM     SCL     Quantity                                    (2LIS_02_SCL)
ODS(A)      3001             15          800
ODS(C)     3001     X     15          300
     3001          15          800
PSA      3001     X     15          400
        3001             15          900
As we are using the Update type Addition,
From PSA, it is clear that the change is 500; this change got reflected in ODS properly.
But when I compare ODS data with EKET data,
LPA     SCL     ODS(Active)          EKET
3001     15     800               900
As you can see wrong validation results between BI & R3
I am missing the below changes happened to SCL in the extractor
     3001     X     15          300
     3001          15          400
The missing above entry is resulting errors.
Does anybody know how the EKET line changes can be tracked?
How to check the V3 Update, we checked the program: RMBWV302
Does anybody have idea where to track this error.
Note: the above case is happening to only a for few documents
Regards,
NK.A
Message was edited by:
        nandakumar a

Hi Renjith,
Thanks for the reply. Can you please let me know few more answers to the below points.
As the datasource 2LIS_02_SCL does not takes this event into account (only MA, MB, MC and MD), this field is not passed to BW (you can see the events per datasource in transaction LBWE)
You are referring to posting of the Material Ledger posting right ? Can you please give some more information about MA MB MC MD as I have verified in LBWE and could not find anything about it except that its picking that GLMNG value from MCEKET table.
Renjith, Please update your views on the below query. I am not able to get any answers from anyone on this query. I appreciate your reply.
In my opinion you would be able to fill it in the customer-exit of LIS (EXIT_SAPLEINS_001) or BW (EXIT_SAPLRSAP_001)
If I add a zfield to the SCL DS and then populate that field with the code in the include ZXRSAU01 , EXIT_SAPLRSAP_001 in that going to help.
Do I have to verify the events MA MB MC and MD while populating this zfield or I can just do a direct lookup on EKET
select single * from EKET
where EBELN = l_MC02M_0SCL-EBELN
and EBELP = l_MC02M_0SCL-EBELP
and ETENR = l_MC02M_0SCL-ETENR will do ?
So when ever the ds fields are getting populated in the org DS ...it will find this zfield in the same structure and will fill this field. Is that going to fix it ? I have also found couple of SAP Notes on the same issue and do you think implementing those notes will fix the problem without the zfield or code.
Could you please check out these notes 100690 and 431145. Please suggest.
Thanks,
Daniel

R/3 numbers are not reflected in APO

HI
i transfered planned order from PPDS to R/3. it successfully CIFed as production order but R/3 production orders are not reflecting in APO. all integration models are in active status. what will be the reason

Hi Thennarasu,
One or more of the input products(components) have special procurement key set in R/3 material master for withdrawal from another plant.
Planned orders are changed in SAP APO and then the conversion indicator is set to initiate conversion into a manufacturing order.
But the queue from SAP APO to SAP R/3 hangs with an error message that indicates that the material in question is not maintained in the certain storage location of a specified plant.
As a result, the planned order is not converted.
Check to maintain the storage locations in customising - Enterprise Structure->Definition->Materials Management->Maintain Storage locations. Here maintain the storage locations of the Plant from which you are procuring the components under the Plant which requires them.
Please confirm
Regards
R. Senthil Mareeswaran.

Changes are not reflecting in the Quality

Hi,
These are standard SAP Components. I have imported the ESS and MSS Packages.
Actually 3 Development Components are using in my application (Tra,TraTri and TraTre).Tra is the root DC.
I have made changes to those objects and sucecessfully build without errors.
After check-in all activities those activities are working fine in Development system.
But those changes not refclecting in Quality system. So i was founded build log error in Consolidation.
I was fixed the error in the Development system and build the components without build error.
still now changes are not reflecting in the quality system.
But out of 3 DCs(Tra,TraTri,TraTre) Tra and TraTre are working fine in Quality(changes are reflecting) only problem in TraTri DC (changes are not reflecting in the Quality)..
Please help me as soon as possible....Its very help full for me
Regards
Sudhakar Reddy A

Hi Slava,
very very thanks to you for the fast reply. but one thing in my side.
When i release the activities after successful build, i export those changes and place them in the import queue of the consolidation system in the CMS.
The export in the SAP NetWeaver Developer Studio packs all selected activities into a change request, and then places them in the import queue of the consolidation system.
When the my system administrator imports this request into the consolidation system, the released changes are integrated into the DTR workspace of the consolidation system; the build server compiles the modified components.
my system administrator findout build error in consolidation system:
[wdgen] [Error]   .PersonnelNumberCheck: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   com.sap.xss.tra.tri.vc.changepersno.VcTriChangePersNo --> ContextModelNode PersonnelNumberCheck [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)
     [wdgen] [Error]   .PersonnelNumberCheck.I_Employeenumber: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   com.sap.xss.tra.tri.vc.changepersno.VcTriChangePersNo --> ContextModelNode PersonnelNumberCheck_Output [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)
     [wdgen] [Info]    com.sap.xss.tra.tri.vc.changepersno.VcTriChangePersNo --> ContextModelNode PersonnelNumberCheck_Output [supplyingRelationRole]: Supply function or supplying relation role missing (Hint: A child node which is not mapped must have either a supplying relation role or a supply function or one of its parent nodes must have a supply function.)
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.E_Name: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   com.sap.xss.tra.tri.vc.changepersno.VcTriChangePersNo --> ContextModelNode PersonnelNumberCheck_Et_Return [modelClass]: The context model node has not been bound to a model class (Hint: A Context model node has to be bound to a model class or mapped to a model node of another controller.)
     [wdgen] [Info]    com.sap.xss.tra.tri.vc.changepersno.VcTriChangePersNo --> ContextModelNode PersonnelNumberCheck_Et_Return [supplyingRelationRole]: Supply function or supplying relation role missing (Hint: A child node which is not mapped must have either a supplying relation role or a supply function or one of its parent nodes must have a supply function.)
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Type: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Message: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Log_No: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Field: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.System: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Message_V1: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Message_V3: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Message_V2: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Log_Msg_No: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Number: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Message_V4: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Parameter: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Id: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   .PersonnelNumberCheck.PersonnelNumberCheck_Output.PersonnelNumberCheck_Et_Return.Row: The mapping definition is inconsistent, the mapped context element does not exist.
     [wdgen] [Error]   com.sap.xss.tra.tri.vc.changepersno.VcTriChangePersNo --> ContextValueAttribute EmployeeName [readOnly]: The context attribute has to be read-only. (Hint: As the mapped context attribute is read-only this attribute has to be read-only, too.)
I was fix error in my development system with out any build errors. still now not working ...pls give me any suggestion.i dont have access to consolidation system.
Regards,
Sudhakar

Station Globals modified externally are not reflected

Hi,
I am having an UI developed in CVI(EXE1) which runs a teststand sequence. The flow of sequence is controlled by Station Globals.
The Station Globals i am trying to control from another user interface so that the flow in EXE1 will be exrcised. But some reason the updated station globals are not reflected in EXE1.
In the sequence i have used Engine.ReloadGloabls() but some reason the values are not reflected.
Anyone can help me out on this.

Hey ramjeev,
Are you certain that the globals are being saved from the location you edited them before you call the Engine.ReloadGlobals()? Also, as mentioned in the function help here, you should clear or destroy your existing references to the globals before calling the ReloadGlobals() method. This is because any existing references will retain their values rather than being updated with the method call.
However, I'm not sure if this is the best approach for your application. Typically, Station Globals are used for configuration settings, particularly those that need to persist between executions. Since you're wanting to control this test sequence from another user interface, I wonder if UIMessages or a synchronization object such as a queue or notifier would be better for this purpose. Have you explored any of these options?
Daniel E.
TestStand Product Support Engineer
National Instruments

Changes made in ECC not reflected to CRM

Just encountered a problem. As follows:
1. When a line item in a sales order in ECC is rejected with a reason, the changes are reflected back to CRM. Likewise, when the PO number field in the sales order is changed, the changes are reflected back to CRM. This is ok.
2. But when I make a change in the address fields (i.e. change the street) in the ship-to partner (on the header level) in the sales order in ECC, the changes are not reflected back to CRM.
Has anyone encountered this issue before and if so, what was the solution?
Will reward points...

Hello,
Check the inbound queue in CRM and outbound in R/3.
Prase

Changes in MM02 not reflecting in COPA lin item report

Hi,
In my project during data conversion material was grouped wrongly. We realised it later once we started designing COPA reports. The material is used by seven company codes. The basic material group defined in basic data is used by all company codes while Material group 1,2,3 4 and 5 are used by company specific defined in sales orgs 2 View in MM master(MM01).
I am designing report for three companies by using material group 1,2,3,4 and 5.
We tried changing the material group 1,2,3,4 and 5 for wrongly grouped materials in MM02. But in COPA report these changes are not reflecting. The grouping in report is still as per the data conversion grouping.
Please suggest on how should we rectify our material grouping to reflect in COPA report.
Regds

Hi,
in COPA reports characteristics are read from the COPA tables, they are not dynamically derived at the time of executing the report. In the COPA tables oyu will find the characteristic as derived at the moment of posting the line item.
If the characeristic that you want to rectify is in the definition of your your COPA segments - which you can check through TC KEQ3 - then there is possibility to carry changed master data over to past COPA data.
TC KEND allows you change the existing COPA segments according to current master data. However, it will not make changes to table CE1XXXX, where COPA line items are stored, but changes happen on the segment level (CE4XXXX).
This means that you always see the changes in COPA reports that read from segments, but not in line item based reports.
To change your output from line item based reports I see no other possibilty but to make correcting entries in CE1XXXX using KE21N or KEFC.
If you should consider using KEND please read the documentation for "realignment". It can create problems, for example if you have a SAP BW that is delta-updated from CE11XXX. Also your summarization levels for COPA have to be rebuilt after KEND.

Material regrouping in MM02 not reflecting in COPA report

Hi,
In my project during data conversion material was grouped wrongly. We realised it later once we started designing COPA reports. The material is used by seven company codes. The basic material group defined in basic data is used by all company codes while Material group 1,2,3 4 and 5 are used by company specific defined in sales orgs 2 View in MM master(MM01).
I am designing report for three companies by using material group 1,2,3,4 and 5.
We tried changing the material group 1,2,3,4 and 5 for wrongly grouped materials in MM02. But in COPA report these changes are not reflecting. The grouping in report is still as per the data conversion grouping.
Please suggest on how should we rectify our material grouping to reflect in COPA report.
Regds

Hi,
in COPA reports characteristics are read from the COPA tables, they are not dynamically derived at the time of executing the report. In the COPA tables oyu will find the characteristic as derived at the moment of posting the line item.
If the characeristic that you want to rectify is in the definition of your your COPA segments - which you can check through TC KEQ3 - then there is possibility to carry changed master data over to past COPA data.
TC KEND allows you change the existing COPA segments according to current master data. However, it will not make changes to table CE1XXXX, where COPA line items are stored, but changes happen on the segment level (CE4XXXX).
This means that you always see the changes in COPA reports that read from segments, but not in line item based reports.
To change your output from line item based reports I see no other possibilty but to make correcting entries in CE1XXXX using KE21N or KEFC.
If you should consider using KEND please read the documentation for "realignment". It can create problems, for example if you have a SAP BW that is delta-updated from CE11XXX. Also your summarization levels for COPA have to be rebuilt after KEND.

Delta not reflecting in Queue (RSA7)

Similar Messages

Maybe you are looking for