Missing PO's from delta loads.

Hi All,
I am facing a peculiar problem as following:
Datasource : 2lis_02_scl
r/3 field :elikz(final delivery indicator)
Update mode is 'delta' to one ODS.
Loads are correctly running as expected but recently noticed that BW field 'final delivery' is not getting updated for many PO's.In R/3 PO's having recent values for the field 'elikz' ,which ideally should have come as part of deltas in BW but unfortunately this is not happening.
Since I am not sure about the exact number of PO's missing in BW ( not sync with R/3) , so I cannot pull these pariticulars PO's with 'full repair request'.
If anyone encountered this kind of issue or have some clue about the reason, please revert.
Awaiting your responses.
Thanks,
Shiv

Hi,
Did you solve this issue? I have a simialr issue even a full repair request of certain POs did not solve the issue. The field ELIKZ is filled wrong in BI.
Regards
Selin

Similar Messages

Records are Missing when we run Delta Load( FIGL-ACCOUNT ITEMS)

Hi,
Some records are missing when we run Delta load.
We have one generic data source on FAGLFLEXA table.
We select Field nm TIMESTAMP
TIME STAMP IS LOCAL.
upper limit is Blank
Lower limit is 1000.
we run this process chain every day.
we select delta settings is New status for changed records.
Please give me any idea why records are missing when we run deltas.
Thanks
Naik

Hi Anju,
Please ensure that you are following the below steps while Initilizing the application 13:
1. All the users in source system, must be locked.
2. Ensure that SMQ1 and RSA7 are having no data for application 13. Delete the application 13 datasource entries from RSA7.
3. Delete and refill the setup tables for application 13.
4. Run a INIT with data transfer load for the required datasources of application 13.
5. The Deltas can follow from the next day.
This will ensure that your deltas are fetching correct data. Note that, delta will pick up the same conditions on which the INIT load was run.
Please let me know if you need any more information.
Regards,
Pankaj

Missing Data in 0FI_GL_4 delta loads.

Hello All,
We successfully loaded the 0FI_GL_4 related ODS upto 02/06. We turned on delta loads for the same from 03/06. The data validation team has discoved that there is missing data in 03 and 04. I plan on resetting the delta queue in R3 and reinitialize a full load until april. Here are my questions
1) Are there any specific steps i would need to follow?
2) Are their any other better alternatives then reinitializing with the full load.
Thanks in advance.
Kiran

Initialization Concept :
I will explain this with an example.
You have 5 company codes (CCs) (1000, 2000, 3000, 4000, 5000) in your R/3 source system.
But your client wants reporting in BW only for 3 Company codes (CCs) (1000, 2000, 3000).
In that case, there is no point in bringing the data for other 2 CCs.
So during Initialization, you give the inputs as,
CC = 1000, 2000, 3000 and do a Initialization (With or Without Data transfer)
So henceforth, when Delta is pulled, any changes corresponding to CCs 1000, 2000, 3000 only will be captured.
Eventhough there are changes in 4000 & 5000, they will not be captured in the Delta.
Hope I answered your Question.
Regards,
Balaji V

Data Recovery from delta loads

Hi Everybody,
We pull GL Item data from R/3 to BW on a nightly basis using the 0FI_GL_4 extractor using delta updates with a process chain.
The process normally starts around 01:00 CST. At around 01:37, there was a problem with the database for R/3 and our extraction job was cancelled. No data was transferred to BW. No PSA entries were created in BW.
Later on, we executed the same process chain again. This time, the process chain completed successfully. However, the system said there were no new delta records. Since it is in the middle of the week and
there are only a few days until month end financial close, we should have many GL records.
We need to find out if we lost any GL data, and if so, how is the best way to recover.
Thanks in advance
Varun

Hello Srini,
Goto Delta Queue, RSA7 -> Display Data enteries -> there you select Delta Repetition option for update mode and then execute. Now you should be able to see some records for the extractor. Then pull it into BW.
GSM.

Records missed from DELTA for which changes made only in enhanced fields

Dear Friends,
I have enhanced a feild in standard extractor 0UCINSTALLAH_ATTR_2 by adding a z-field in append structure and writing corresponding code in customer exit. In RSA3 also I'm able to see the data getting reflected for enhanced z-fields but when I'm pulling delta those records are not getting extracted for which changes have been made only in Z-FIELDS in R/3 side.
i.e. if I do not make any changes in std fields of the std. extractor and only change z-fields this record is missed from delta data pulled. Please help urgently.
Regards,
Amit Srivastava

Hi ,
Some times it happens that the system is not able to capture the delta based on the changes made to the Z - fields :
You can think of the following options :
1. You can write a code in the user exit for this thing so that the changes are captured(Not sure how it is done, however had read that it is possible. You may have to explore the same)
2. Try to change any of the standard fields used for delta along with the custom fields so that the changes get captured.
3. Extract a full load instead of a delta load. This may depend on various parameters
I hope you have already checked the extraction.
Hope the above points help.
Regards,
Adarsh Mhatre

Delta load of customer from R/3 (ECC5.0) to CRM5.0

We have done an initial load of customers from ECC to CRM (R3AS). A change is done on a customer in ECC. I expect the changes to be reflected in CRM as a delta load. I do not see the changes. What am I missing?
All responses are appreciated and will be rewarded.

Hi Mani,
Here are some clues on how to proceed with processing of incomplete or failed BP deltas:
First of all you have to note that during the initial download, no delta download can occur. In particular, no delta download of customers occurs if the initial download of materials occurs at the same time. This is because the material download depends on the customer download.
During the delta download, the CRM system uses the inbound queues R3AD_CUSTOME<nnnnnnnnnn> where <nnnnnnnnnn> corresponds to the customer number in the R/3 system. If an error occurs during the download, the inbound queue for this customer is stopped. You can see the error messages in the flow trace. For the delta download, you have the option to use Transaction CRMM_BUPA_MAP for the error analysis. If you enter the customer and press Enter here, you can display the business partner number for a customer and all open BDocs (that is, those which contain errors or are being processed). To do this, you only have to click the 'Queues and BDocs during download' pushbutton. The system issues an overview of the queue and the open BDocs for this customer and in particular, you can 'look into' the BDoc. As a result, you return to the flow trace and you can display the error messages which occured as described above. During the delta download, you have the option to send the same BDoc again. This is useful if you can simply solve the problem by correcting Customizing in the CRM system. To do this, you simply click the corresponding icon in the flow trace (currently, this is the second icon from the left).
If you have to correct the error in the R/3 system, you have to delete the existing BDoc since it cannot be processed further. As a result, the inbound queue in the CRM system is released again. In this case, you are recommended to delete all existing open BDocs and to make the changes in the R/3 system.
If inconsistencies occur between the R/3 system and the CRM system, you can start a request for the customer. To do this, click the 'Get customer from the R/3 system' pushbutton. This starts a request which uses the inbound queue R3AR_CUSTOMER. Process possible errors as during an initial download.
If you still have problems and don't know how to fix, please post more specific information from the BDoc queue, such as what error message you are getting. It helps us better identify the problem.
Regards,
Rahul
PS. Please award points if it helps!
PPS. For future reference: this info was found in note 362621: Error drng data exchange customer<->business partner

Delta Load failure from ODS to Cube

Experts,
After CRM upgrade, I had to reinitilized the delta process. In this, I reloaded ODS with first init delta without data and then delta load with new data created in CRM. This worked good so far. After this when I tried to load cube with init. delta without data, no issues. But delta load from ODS to Cube doesn't work. Does anybody have any suggestions, please?
Thanks,
Nimesh
Following error observed in Status for delta load from ODS to Cube.
Error when transferring data; communication error when analyzing
Diagnosis
Data Packets or Info Packets are missing in BW, but there were - as far as can be seen - no processing errors in the source system. It is
therefore probable that an error arose in the data transfer.
With the analysis an attempt was made to read the ALE outbox of the source system, which lead to error .
It is possible that no connection exists to the source system.
Procedure
Check the TRFC overview in the source system.
Check the connection of the source system for errors and check the
authorizations and profiles of the remote user in both the BW and
source systems.
Check th ALE outbox of the source system for IDocs that have not been

Hi,
As far as i understood, you have successful deltas' loading to the ODS and you want to update entire ODS data to the Cube followed by daily delta's.
If this is the case,
Make sure that you have active update rules exist between ODS and Cube.
First goto your ODS and right click and select option 'Update ODS data in data target'.
Select Init update > IT will take you to the init info package where you select init <b>with data transfer</b> (Init with data transfer will bring all the records from ODS to Cube)
Once init is completed ,you can schedule to load delta's regularly form ODS to Cube by following the same steps.
Hope this helps
Praveen
Message was edited by:
Praveen Vujjini

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

Error in delta load of 'Customer Group' from R/3 to CRM

Hi Experts,
I added new 'Customer Groups' in R/3. But this is not being updated in CRM. Do I have to trigger initial load again through R3AS or should I create new Customer Groups in CRM?
The BP delta load BDocs are stuck in SMW01 due to this change. Also, if I need to do the Initial load of Customer Group, which object do I need to do the load for? Is it dnl_cust_sales?
Please help as it is a Production issue.
-- Pat

Hi Pat,
Use object 'DNL_CUST_SALES' to download Customer Group from R/3 to CRM.
Use R3AS4 transaction to execute the same.
Best Regards,
Pratik Patel
<b>Reward with Points!</b>

Delta Load from SAP R/3 to XI

Hi Experts,
Please let me know your how can I send the following data using IDoc from R/3 to XI :
DELTA LOAD
1.New or changed WBS Elements/Networks (T Code: CJ02, perhaps others)
2.New or changed Orders (T Code: KO02 (internal), IW32 (PM))
3.Transaction Data for capital objects (Not thru XI)
4.New or changed Cost Elements (T Code: KA02, perhaps others)
5.New or changed Cost Centers (T Code: KS02, perhaps others)
Thanks,
Anirban.
Moderator message: please do some research before asking.
Edited by: Thomas Zloch on Mar 21, 2011 10:11 AM

You must see this in WE05 or BD87. Just release the idoc and have a look at we05 or bd87 and limit down the time where to search. in sm58 you can only see the idoc ith the system can not log on to the remote system. Did you check sm58 in the target system? did you check bd87 in the target system?

Repair request for Delta load? Orders missing in Billing line Items

Hi
I am using BW 3.5; Some Orders are missing in BW for Billing line item reports (2LIS_13_VDITM) according to the users.
The report is based on Cube directly, ODS is not used. I planned to do a repair full request for this month's data so as to get the missing orders.
Could you please advice me on correct procedure to do that? Delta loads runs every day and todays delta is completed.
Thanks and BR
P.B

While it's usually recommended to execute setups during "quiet time", it's not required. Especially in this case. Since you're going to be restricting the setup to only extract a range of Billing Documents that are representative of the dates of data missing (or purely the identified missing documents), there is no need to wait for "quiet time" because you'll pick up the data either in your Full Repair extract or in the delta extract. Depending on how the target InfoProvider for this data is setup (cumulative v. non-cumulative), you may have to look out for duplicate data.
My recommendation would be to run your setup for only those documents that have been identified as missing. That way, you're limiting the amount of data that's required to be extracted to the setup table and then into BW, but also will remove any risk of duplicate data in your target InfoProviders.

Issue with delta load from R/3 to BW

Hi frnds,
There is a standarded D.S 2LIS_05_ITEM in R/3. Evereday We extraceted data from R/3 to BW based on this standard Data Source with delta load.There are two fields ZX and ZY in BW ,some times the data haven't extracted for this 2 fields in BW with the delta update.But some times this 2 fields properly extracted in to BW with the same delta update.
Why is it happen like this ? Please give some inputs on this.
Regards,
Satya.

Hello,
if its a standard field then its getting populated in correct way.
if its custom field then you need to analyze the records for which its getting populated and for one which its not.
Quite possible that some cutomization in CMOD results in this behaviour.
Also,check underlying tables to see the correct values.
Regards
Ajeet

Middleware - Delta load is not working from CRM to R/3

Hi Experts,
Our client is using SAP-R/3 4.7 and CRM 5.0
Connectivity was established via Middleware and initial load of Customizing objects and Master data( Customer and Material) was finished successfully.
Now if i create any Customer or Product in R/3 they were replicating to CRM(Delta load), but this delta load is not working in CRM to R/3 direction.
In CRM Administration console( Transaction code - SMOEAC) R/3 site was maintained and subscribed for Publications - All Business Partners, All Business Transactions and All Business partner Relationships.
Can anybody help me out that why Delta load is not happening from CRM to R/3 Direction.
Thanks in advance
Nadh.

Hi Nadh,
for BPs check PIDE settings once agiain, i hope u ve already downloaded all mandatory obects for BP, because u already told that replication from r/3 to crm is ok, so check once again PIDE settings (CRM to R/3),
for Products u ve to manual upload only
for Products
This may be necessary because the data is required in the OLTP System for a number of logistical processes such as procurement, inventory management, billing, financial accounting, controlling.
cheers
Ranga

I have a iPod clsic load it with the music I like. I want to sync all my iPod music with the iTunes library (new) without missing any music from my iPod. How I do that?

I have a iPod clsic load it with the music I like. I want to sync all my iPod music with the iTunes library (new) without missing any music from my iPod. How I do that?

you have to pay to get a program like CopyTrans here is the link: http://www.copytrans.net/download.php

Delta load from r3 to bw ?

i have one question on the mechanism of data transfer from r3 to bi 7.0. the followings is my concerns:
scenario:
The total numer of data is 1000 rows and these rows are seperated into 10 data package , each package contains 100 rows.
Now bw is trying to recieve these 10 packages from r3 in sequence.
When 5 data packages have been transfer to bi psa. the network is broken and the tranfer is canceled at the 6th data package.
What i want to know is when the network is reconnected ,Does the transfer start from the 6th data package?
How to find out whether its a delta load or a full load if a transfer is scheduled from r3 to bw ? For both CUBE & ODS.
How to find out how many records have been transfered from r3 to bw while the transfer has ended in
the middle ? I mean how to check how many records have been successfully transfered from r3 to cube/ods .Please tell me for ods as well as cube.
Is the continuation of transfer process is same for both ODS & INFOCUBE, if it ends in the middle ?
What is the procedure for full load & Delta load in case of CUBE & ODS ? I mean how to reschedule the transfer.
And if the whole scenario is is in the support, SO I will be handling these issues on the live production server. Am I right ? So in this case my user id should have access to all the production r3 and production bw to do these change status to red and delete the request and reload the request etc., So I should be logging on to the production server and do all the manipulation, Am I right ?
Last doubt, what is repair request and so if the transfer stops in the middle we change the status to red and reload the request again , Is it called repair request ?
What is the difference between repeat delta & repair request & repair delta ? When do we choose these options, In which scenarios ?
How do we schedule a daily load job from r3 to bw without the use of process chains ? I mean daily it should fetch the records from r3 to bw from the SD datasources at 10.00 PM ,how do we do that ?
Please I am having all these doubts and I want you SAP experts to answer them please so that I can clear my doubts in production support . I really appreciate if someone explain me the scenarios here. It will be a really great help if someonce clears these doubts.

Hi......
What i want to know is when the network is reconnected ,Does the transfer start from the 6th data package?
If your connection is broken in between......inspite your load is through PSA...........you have to delete the request from the target(after making the QM status red)............then you have to reload it again............But before repeating the load check the connection is ok or not in SM59........
How to find out whether its a delta load or a full load if a transfer is scheduled from r3 to bw ? For both CUBE & ODS
This you can check in IP scheduler in the Update tab...........whether it is delta or full load.......
or you can also check in IP monitor(You can go here through RSMO..........IP monitor screen will open directly here............or you can also go through RSA1>> Find your IP >> Double click on it >> Click on the monitor icon in the top >> From the you will go to the IP monitor>> the under the Header Tab you can see whether it is a delta or Full update...........
Or you can check the datasource also..........
If it is a generic datasource go to RSO2..........and check...........If it is a standard datasource check it in RSA5...........
How to find out how many records have been transfered from r3 to bw while the transfer has ended in the middle ? I mean how to check how many records have been successfully transfered from r3 to cube/ods .Please tell me for ods as well as cube
Your load cannot be ebded in the middle.........it can failed.............if it fails then you have to delete the request from the target..........and then repeat the load.......
Is the continuation of transfer process is same for both ODS & INFOCUBE, if it ends in the middle
Yes.........
What is the procedure for full load & Delta load in case of CUBE & ODS ? I mean how to reschedule the transfer
If a full or delta load fails after extraction got completed due lock issue or SID issue.....etc..........and if you load is through PSA.............then just delete the request from the target without making the QM status red.......and reconstruct the request.........no need to repeat the whole load again........
But if you r load is not through PSA..........then make the QM status red........delete the request from the target........and repeat the load...........
And if the whole scenario is is in the support, SO I will be handling these issues on the live production server. Am I right ? So in this case my user id should have access to all the production r3 and production bw to do these change status to red and delete the request and reload the request etc., So I should be logging on to the production server and do all the manipulation, Am I right ?
Yes.......
What is repair request and so if the transfer stops in the middle we change the status to red and reload the request again , Is it called repair request or reload request?
Suppose you delta load has failed ............and you have deleted the request from the target without making the QM status red............In this case your data will be lost and your delta mechanism will get corrupted............In this situation.............
1) Delete the init flag........
2) You have to do Full repair..........(After filling the set up table)
3) Init without data transfer to set back the init flag
4) Then Delta upload.............
In case of an ODS............you cannot load Full update and delta upload parrallely..............Your ODS activation will fail...........suppose you want full upload in the ODS..............then you have to go for Full repair............
What is the difference between repeat delta & repair request & repair delta ? When do we choose these options, In which scenarios ?
I think Full repair concept is now clear............
Suppose your delta load fails...........After that you delete the request after making the QM status red............Then system will ask for a repeat delta when you will try to repeat the load...........which means it will pick the same delta records of the failed load..........
How do we schedule a daily load job from r3 to bw without the use of process chains ? I mean daily it should fetch the records from r3 to bw from the SD datasources at 10.00 PM ,how do we do that ?
This you can do via infopackage or infopackage group...........schedule it at the specific time.....
Check these links :
http://help.sap.com/saphelp_nw04/helpdata/en/20/ad673844a7114be10000009b38f842/frameset.htm
Re: Schedule Infopackage for last day of a fiscal period
Hope this helps you.........
Regards,
Debjani...........

Missing PO's from delta loads.

Similar Messages

Maybe you are looking for