Delta load green but incomplete..

Hi friends!
Last week, we have a request "100" with QM status and Monitor status GREEN.
After, others delta were loaded ok from my DSO to the Cube.
When I check the request 100 in the monitor detail tab, I can see that the most of the package (with 50000 records each one) were transfered and loaded to the cube except one. This package show 'waiting messages from update rules', and this only package is in YELLOW.
How can I force to update / transfer this data to the cube?
Thanks in advance!

Hi SSap,
Usually DTP generates lot of Background jobs.Goto monitor of bad request-->click on Job Overview >Then you will get the jobs list>check any job is in active state.
If yes,then check the job log you will get some useful information.If all the jobs are finished,this may be the display issue i think so.
Have you got the reporting symbol for all the request in CUBE...?
If you got reporting symbol and DTP jobs are finished,you can leave this.
Hope this helps,correct me if i am wrong
Regards,
Venkatesh

Similar Messages

InfoPackage delta load error, but repeat successfully

Hi,
we are facing a strange behavior when executing a infopackage.
The datasource is created via RSO2 using delta = AIMD. We use a programm to select the data and insert it in the deltaqueue.
So the data is already in the queue when we start the infopackage. We only using a dummy function module to trigger the transfer of the data.
So the problem is:
When we start a delta load, it brings up an error (RSM340 - Error in Sourcesystem), but when we make a repair or execute the infopackage again, (immediately or a few minutes later) the load works.
We have checked everything, joblogs, idocs, trfc, authorizations and everything is ok. All jobs are being executed in the sourcesystem correctly and the idoc´s are sent back to the BW.
We are on a SAP BW 7.31 SP7 system.
Does anyone has an idea, where to look or whats could go wrong?
Kindly regards
Maximilian Müller

Hi,
Have you checked your info pack job log details at ecc side, SM37.
if check there you may know more details about your issue.
From failed info pack monitor--> menu Environment-->job overview--> job in the source system, enter ecc user id and password, you will get your ecc job, select job and click on log details, see and share here if you see nay abnormal messages.
Thanks

Init. Delta load in BI 7.0?

Hi, Experts:
I just changed to a new BI application team. We have a delta load from ECC into an ODS then into a cube. I thought that there must be an initial delta load before the daily delta load. But I don't see init delta load request when right click the ODS/cube then select "Manage". The application started to load from January 2008. I have put the request display date to sometime 2007 then click the refresh button. But still could not see init delta load. From the very 1st load till date, I only see all are delta loads. Is this some thing new in BI7.0 that init delta is not needed any more? Or something is wrong?
Thanks,
Jenny

Hi,
that's right, there is no special request for Delta/Init.
The DTP can do it itself at the first time.
If you want to check which DTP is the Initialization, you can go on the DTP log, and in the header you will see "Extraction Mode" -> Delta.
If the corresponding DTP request is the init, the flag "Delta Init" is ticked.
Hope it helps !
Mickael

Data load from infoprovider : status is green, but no data is loaded.

Hi,
I have created a new application copying the planning application (which was again a copy from the apshell application set). I modified the dimensions, after which I wanted to load data from a BW infoprovider using the datamanager.
The first thing I noticed in the datamanager, was that the packages were not the same as in the original planning application. In fact I had chosen to copy all objects to the new application. For example, the package 'load data from infoprovider' that was contained in the data management map of the planning application, was not visible anymore in my new application. Instead, there is a package 'Loadinfoprovider' located in the system administrative map. As these packages are exactly the same, the package 'Loadinfoprovider' does not seem to work properly. When you run the package, it says that is has submitted records to your application, but when you run a report on it, or go look to the bpc infocube in BW, no data is visible.
Does anyone know what may cause this problem ?
Edited by: Wouter Vanhoutte on Dec 1, 2009 3:46 PM

Hi Wouter,
Did you check your transformation file?
I had the same problem once, my mistake was that I didn't add a line for my key figure amount (AMOUNT=ZAMOUNT). So the status is green but no data transferred because no key figure to transform.
I hope this will help you
Mathieu

Request status is Green,But no data is loaded into infocube.

Hi,
I have loaded the data from Flat File to Infocube. The status of the request is Green. But no records are added into infocube.
The data is available in PSA.

Hi Jen,
I had created DTP and scheduled it. There shows a request in infocube with status green but no records added.
I have checked in PSA , the data is present in PSA.
I am wondering why data is not uploaded from PSA to Infocube.

Full load works, but delta fails - "Error in the Extractor"

Good morning,
We are using datasource 3FI_SL_ZZ_SI (Special Ledger line items) to load a cube, and are having trouble with the delta loads. If I run a full load, everything runs fine. If I run a delta load, it will initially fail with an error that simply states "Error in the Extractor" (no long text). If I repeat the delta load, it completes successfully with 0 records returned. If I then rerun the delta, I get the error again.
I've run extractions using RSA3, but they work fine - as I would expect since the full loads work. Unfortunately, I have not been able to find why the deltas aren't working. After searching the Forums, I've tried replicating the datasource, checked the job log in R/3 (nothing), and run the program RS_TRANSTRU_ACTIVATE_ALL, all to no avail.
Any ideas?
Thanks
We're running BW 3.5, R/3 4.71

And it's just that easy....
Yes, it appears this is what the problem was. I'd been running the delta init without data transfer, and it was failing during the first true delta run. Once I changed the delta init so that it transferred data, the deltas worked fine. This was in our development system. I took a look in our production system where deltas have been running for quite some time, and it turns out the delta initialization there was done with data transfer.
Thank you very much!

Error in delta loading from a planning cube

hi all,
I am using a delta load from one planning cube to another.When the changed records are of a magnitude of 100 then it is successful but when the records are of magnitude of 100000 then it stays yellow with no data records sent and eventually fails.the packet size is 20000.
any help is appreciated.

Hello Ajay,
Have you checked that your Request is closed in the planning cube? FM RSAPO_CLOSE_TRANS_REQUEST will do it
It is a customizing issue to tell the infopackage to end "green" when it has no data.
Transaction Spro ==> SAP Netweaver ==> SAP Business Information Warehouse ==> Automated Processes ==> Monitor Settings ==> Set Traffic Light Color. There you have to set the Traffic light on green if no data is available in the system.
Hope that helps
best regards
Yannick

No initial load of Customers, Material and delta load of Sales Orders.

Hi Experts,
I am facing a very troublesome issue. I am not able to setup the Middleware portion for initial and delta loads. I read a lot of documents and corrected a lot of things. finally, the connectivity is done with R/3 and CRM. Initial load of all objects is successful (as per Best PRactices guide). Customizing load is successful.
But after now I have these open issues for which I am unable to find any answers (am really exhausted!!):
- Customer_main load, it was succesful, but no BP's of R/3 are available.
- Material, it failed in SMW01, SMQ2, the errors are:
Mat. for Initial Download: Function table not supported
EAN xxxxxxxxxxxxxxxxxx does not correspond to the GTIN format and cannot be transferred
EAN yyyyyyyyyyyyyyyyyy does not correspond to the GTIN format and cannot be transferred
Plant xx is not assigned to a business partner
- Sales order, it shows green bdoc, but error segments says "No upload to R/3" and the order does not flow to R/3.
We had our system setup 3 years back for data transfer and Middleware. But few things changed and connectivity stopped. I did all that again now, but am not yet successful. Any inputs will be greatly appreciated.
Thanks,
-Pat

Hi Ashvin,
The error messages in SMW01 for MAterial initial load is :
     Mat. for Initial Download: Function table not supported
     EAN 123456789000562 does not correspond to the GTIN format and cannot be transferred
     EAN 900033056531434 does not correspond to the GTIN format and cannot be transferred
     Plant 21 is not assigned to a business partner
I have done the DNL_PLANT load successfully. Why then the plant error?
Some of the messages for BP:
Messages for business partner 1331:
No classification is assigned to business partner 1331
For another,
     Partner 00001872(469206A60E5F61C6E10000009F70045E): the following errors occurred
     City Atlanta does not exist in country US
     Time zone EST_NA does not exist
     You are not allowed to enter a tax jurisdiction code for country US
     Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
Now, the time zone EST is assigned by default in R/3. Where do I change that? I do not want to change time zones as this may have other impacts. Maybe CRM I cna change this, not for sure in R/3. City check has been deactivated in R/3 and CRM, still the error.
Till these 2 are not solved, I cannot go into the Sales order loads.
Any ideas will be greatly appreciated.
Thanks,
-Pat

Converting Full Load - Delta load

Hi Experts,
I am trying to convert ODS from Full Load to Delta Load.
The problem is already there are full req so its not allowing me to activate delta.
I have tried running the program "RSSM_SET_REPAIR_FULL_FLAG" which would convert full req into repair req and then I should be able to load Init/Delta.( see OSS Note 689964)
Problem is even after running the program succesfully I m getting same message and not able to activate Init.
I again tried running running the prog but now progr does nt show any req which could be converted to Repair req.
So how to proceed from here and Full load ODS -> Delta...???
All help would be appreciated and awarded by points...
Thanks in advance!!!
Sorabh

Hi Ajai,
I checked RSREQDONE; in tht Qm status of req is Green...I dont know what I shud check in this table..
Also as per my understandings loading thru reqs in PSA is another way (if the request still exist in PSA)apart from the program given.
Program shud work in any condition whether req is there in PSA or not.
Correct me if I am wrong..
but again struck ..on same issue...:)..
Thanks,
Sorabh

Urgent: Problems in Delta load

Hi BW Gurus/Experts,
I am new to BW and My requirement is to load deltas from CRM to BW,I have initialized deltas and after some days(appx. around 3days) there was changes in the records so I have created infopackage and tried to load deltas but i cannot do that i donot know what might be the reason when i check in monitor the status of the request is yellow with 0 from 0 records eventhough there are records which i check in RSA7. I have seen some previous posts according to some gurus suggestion I have activated the transfer structure and replicated datasources and loaded deltas again but it didnot helped me.I even tried by init load without data transfer and than i have created another infopackage for delta load that too it didnot helped me. Would anyone please suggest me some of the steps and brief explaination on them I need to follow for the following queries:
1) If I need to load deltas after 4 to 5 days of Init load.
2) If I need to load deltas again after 5 to 6 days of deltas load.
When I load deltas after init or delta load after some days by init load without data transfer and loaded deltas than the status of the request is green in monitor but with 0 from 0 records. would anyone put some light on it. I appreciate it in advance.
Thanks a lot
Regards
Reddy

Hi AK,
1) As mentioned that you have activiated the transfer structure and replicated data source..I guess it should be other way ..first you have replicate the datasource and activate the transfer structure but though TS gets activate by normal ..Its good if you activate TS through the program RS_TRANSTRU_ACTIVATE_ALL ..give TS name and activate then try to load the data.
2) There are some possible reasons when IDOC get hangs such as missing free dialog process in the target system
a)IDOC hang in status 64 for tRFC with immediate( Check note:555229)
b)Request hang because IDOCS are not processed (Check note: 561880)
c)RFC resource check returns incorrect result (Check note:311930)
3)Check entries in delta queue (RSA7) see also note 380078.
4)Its also better to use Diagnosis tools delta queue monitor qRFC t.code :SMQ1 in source system see also note 444261.
I hope the above information will help you.
Thanks n Regards
Sreedhar

Delta load - request status is partially activated

Hi to All,
From one Info package data is loading to 1 CUBE, 1 ODS simaltaneously through PSA, but data is not updated to PSA. Then I have activated the ODS and then I changed the ODS request status to GREEN but here transfered records are 2000 but added records are 0, after few minuets data packets came into PSA then I am trying to CHANGE THE REQUEST ODS STATUS TO RED, IT IS SAYING "REQUEST IS PARTIALLY ACTIVATED".
In both ODS and CUBE manual updation terminating.
LOAD IS : DELTA
Pls can anyody give suggestions/inputs to come out from the problem.
Thanks In Adv,
MSM.

Hi Akash,
Here ODS request status is changed to(from RED ->GREEN) GREEN forcebly b'z red request is not activating the ODS, after ODS activation when I am trying to change the request status to RED, its saying " REQUEST IS PARTIALLY ACTIVATED NOT POSSIBLE TO CHANGE THE QM STATUS"
If we want to delete the request the REQUEST SHOULD BE IN RED, its allowing to change to RED
pls help me on this what can we do now
Thanks in Adv
MSM.

Duplcate records in the delta load

BW experts,
I am getting the following errors when doing a delta load from 2LIS_02_ITM
into OBBP_CON, 0BBP_INV, 0BBP_PO, 0SRCT_DS1, 0SR_VEGUID.
The delta loads show a green light for all the targets except 0SR_VEGUID and
the error message is
3 Duplicate record found. 2295 records used in /BIO/XSR_VEGUID
3 Duplicate record found. 2295 records used in /BIO/PSR_VEGUID
I tried to check the contents of the both /BIO/XSR_VEGUID and
/BIO/PSR_VEGUID but i get a message saying the tables are not active in the
dictionary.
However, i can view the data in the Info object OSR_VEGUID.
How can i resolve this issue ?
Any help will be appreciated.
Many Thanks

Kiran,
Welcome to SDN,
P and X tables are created only if you have 1. Time dependent Navigational Attributes ( X Table)
2. Time Independent Master Data Attributes.. ( P table)
Otherwise the tables will not be created.
Arun
What table do you see in the header when you see the data for the infoobject ? on the creen - do you see something like
/bi0/XX0SR_VEGUID where XX xould be some characters ... Ideally P table should be viewable...

Difference: Full load, Delta Load & INIT load in BW

Hi Experts,
I am new to SAP BW Data warehousing.
What is the difference between Full load, Delta Load & INIT load in BW.
Regards
Praveen

Hi Pravin,
Hope the below helps you...
Full update:
A full update requests all the data that corresponds with the selection criteria you have determined in the scheduler.
You can indicate that a request with full update mode is a full repair request using the scheduler menu. This request can be posted to every data target, even if the data target already contains data from an initialization run or delta for this DataSource/source system combination, and has overlapping selection conditions.
If you use the full repair request to reload the data into the DataStore object after you have selectively deleted data from the DataStore object, note that this can lead to inconsistencies in the data target. If the selections for the repair request do not correspond with the selections you made when selectively deleting data from the DataStore object, posting this request can lead to duplicated data records in the data target.
Initialization of the delta process
Initializing the delta process is a precondition for requesting the delta.
More than one initialization selection is possible for different, non-overlapping selection conditions to initialize the delta process when scheduling InfoPackages for data from an SAP system. This gives you the option of loading the data
relevant for the delta process to the Business Information Warehouse in steps.
For example, you could load the data for cost center 1000 to BI in one step and the data for cost center 2000 in another.
The delta requested after several initializations contains the upper amount of all the successful init selections as the selection criterion. After this, the selection condition for the delta can no longer be changed. In the example, data for cost
centers 1000 and 2000 were loaded to BI during a delta.
Delta update
A delta update requests only the data that has appeared since the last delta. Before you can request a delta update you first have to initialize the delta process. A delta update is only possible for loading from SAP source systems. If a delta update fails (status red in the monitor), or the overall status of the delta request was set to red manually, the next data request is carried out in repeat mode. With a repeat request, the data that was loaded incorrectly or incompletely in the failed delta request is extracted along with the data that has accrued from this point on. A repeat can only be requested in the dialog screen. If the data from the failed delta request has already been updated to data targets, delete the data from the data targets in question. If you do not delete the data from the data targets, this could lead to duplicated data records after the repeat request.
Repeat delta update
If the loading process fails, the delta for the DataSource is requested again.
Early delta initialization : This is a advanced concept, but just for your information ...
With early delta initialization you can already write the data to the delta queue or to the delta tables in the application while the initialization is requested in the source system. This enables you to initialize the delta process, in other
words, the init request, without having to stop posting the data in the source system. You can only carry out early delta initialization if this is supported by the extractor for the DataSource that is called in the source system with this data
request. Extractors that support early delta initialization were first supplied with.

0BPARTNER delta load problem

Hi All,
For 0BPARTNETR master data , its a delta load and infopackage is showing red but request inside the Data Target is green with 0 added records. But some times it picks the delta figures and sometimes it will show 0 added records . Please assist me regarding this .
Regards,
Aditya

When there are no changes in the master records in R/3 then 0 records will come in delta..
if only records are created or modified then only it will pull delta..records.
Now when request is red you can make its status red manually i.e status not okay and then run repeat delta and check if load is happening...
in infopackage settings..we sometimes put the status preference green or yellow if its stuck for long time...you can check this out ...go to infopackage menu bar and left top corner you can see those options..
Regards
RK

Delta loading methodology

Hi gurus
In BI7 we have a load process like
Infopackage >>>PSA/DS>>>>TRANSFORMATION>>>>>DTP>>>>>DATATARGET
in this kind of flow is the delta work only till PSA like in a delta load we will get the data till psa from source system and we will get green (the sourcesystem will get the message as the load is succesful) and if becoz of some reason the load from PSA to Datatarget fails through DTP then
1. Do we need to do a repeat delta ( because before for repeat delta we used see the request status in Datatarget which should be green and make it to red) what about now do we still use the same functionality.
How exactly DTP will bring the requests from PSA...
will it read the request in PSA in according to Datatarget updated request and will bring only the request which are not read when we set delta in DTP. what if we want to load all the data from PSA again if for some reason.
2. Is the delta initialization done and the status updated to PSA or to Datatarget.
thanks and regards
Sreedhar
Message was edited by:
Sreedhar M

Hi
Thanks for the info.
i have a scenario here
i have loaded an init from an infopackage>>>>>i got 2500 records into psa
and then i have loaded it into Datatarget using DTP using Delta as option
i have seen that total records which it is pulling is 5000 and adding 1000 (WHICH COULD BE THE TRANSFORMATIONS BUT till transforamtion why is it picking 5000 records.)
So i have delted that request form Datatarget and then when into DTP checked the option GET DATA BY REQUEST and then loaded data this time it only picked 2500 records till transformation and added 1000 so the added records do not change but why is it picking different number of records when we select and deselect Get data by request
thanks and regards

Delta load green but incomplete..

Similar Messages

Maybe you are looking for