Delta Missing for Billing Cube

Data goes missing only for 25th dec 08 in Billing cube , rest is available in the cube
Data modeling:
DataSource: 2LIS_13_VDITM & 2LIS_13_VDHDR
Load type : Delta
Target : Infocube
System: BW3.1
Possible solution is to delete the deltas since 25th dec 08 till today and perform repair full request for the concerned period (since target is cube so we have to delete the previous loads to avoid duplicate records)
then,
delete the init
initilize w/o data transfer
schedule the load back to delta
Before going for this method,do we have to delete/fillup setup table in R/3 ??? I dont think so as we are performing full repair load in BW for the given range of date/period...
Guys, lets me know whether i m right or not,,,will it be okay to delete delta loads since 25th till today??
Do u have any better method to get the missing billing data for 25th??

Alok,
1. Delete data in BW for the period from 25th Dec. one doubt is there whether we have to delete all the requests since 25th till date or just to delete 25th data?
2. Dont touch the exisiting init as ait adds unnecessary work
3. Delete the setup table in R3 fisrt (in case thr is some old data)
4. Fill the setup table fro Appl 13 for the date range you have deleted. it will be filled up for missing documents
5. Do a repair full request for this selection. (P.S : Stop the billing delta until you complete this correction) i think we have to borrow help from functional consultant to stop the posting
6. Restart the billing delta
--> Alok, if delta queue getting updated and same time setup also performing while postings happening till current date, chances of same record available in setup table and delta queue.
As you are loading into a cube(addition), after setup tables data loding through repair full, same record may come again via delta(due to new postings). It creates a redundancy of data.
So, as you have problem with one day data on 25th Dec, its better to delete data for that day or for that week and reload by selectively. As you are loding historic data, no postings happens to those records, no need to worry for delta queue. Or
Find out missing records, setup and load. Bit tidious job.... but 100% safe...
P.S: Deleting entire data from 25th onwards and reloading is not a wise decision, as you are loding into a cube.
Hope its Clear
Srini

Similar Messages

Delta update for Info cube, How it will be works, what are mode to select.

Hi all,
              How delta update works for info cube, Generic data source delta update options are
              1) time stamp
              2) Calday
              3) Nemeric pointer
Please explain briefly delta update for infocube and delta init and delta update.
Thanks,
Gowda

Hi,
How delta update works for info cube
When you are updateing the data to cube from ods then data would extracted from change log their delta pointer get setup in the source request (in Source you can check the option beside the reqest says updated to target object.... it means the records are updated to target hence we would not update the same request )
Incase of PSA to cube Also in the PSA request get stamped as last updated .
Regarding Generic Datasource
When we don't find any standard extractor then we can go for Generic(if i want information sales along with finance information in a data source then generally we dont get standard one hence we can go for generic DS)
Check the below link for More about generic DS .
http://wiki.sdn.sap.com/wiki/display/BI/Generic+Extraction
for Delta capturing you can use
Timestamp(if the table has time stamp filed so it can stamp the last changed record in that table hence it is easy to get delta based on the time stamp)Calday- (If the table doesn't have the Timestamp filed then search for Calday where you can stamp the delta based on the date when documents are changed )
Numericpointer : If the table doesn't above both then we go for this option where you can the numeric value change stamp )
Re: Extraction, Flat File, Generic Data Source, Delta Initialization
Regards,
Satya

Condition missing for Billing Type

Hello Gurus
I have a Billing Type ( Say Z123) for which a condition ( say VPRS) is missing. How can I update this ?
Regards
Rajesh

Hi Rajesh,
You will have to do a Pricing analysis and then will have to follow corrective measures accordingly.
Some common errors are:
1) If the requirement is not met. in this case you will have to readt the requirement code and debug to see which check in the code is failing.
2) If the condition record is missing, you will have to check wether the record exista and pricing date is within the validity dates. If its not created create a new recrord.
3) Lot of times, one data point is missing in the sales order for right determination of pricing records. You will have to check this analysis, if one data point is missing then it will carry an exclamation mark.
4) It record has been found and not set, then change the pricing date to the date after pricing record validity date.
Hope this helps.
Abhishek

Delta update for Cube : 0CRM_PRI - Service Orders and Confirmations: Item

Dear experts,
For Cube : 0CRM_PRI - Service Orders and Confirmations: Item
Source data is from Two ODS
1. Confirmations (Item Data) : 0CRM_CNFI and
2. Service Orders: Item Data : 0CRM_PROI
I have done Init upload to this cube from both this ODS.
I am not getting delta option to this.
When I am trying update Delta after init from ODS message is No new deltas in DataStore object 0CRM_PROI for update. No delta option available . It is showing Initial and Full Update option only.
How i can initiate delta option for this Cube ? Please update us.
Thanks in advance.
Regards,

Hi,
you can use DTP's to laod data from ODS to cube .. it will take deltas ..
With a data transfer process, you can transfer data either in full extraction mode or in delta mode. In full mode, the entire dataset of the source is transferred to the target; in delta mode, only the data that was posted to the source since the last data transfer is transferred. The data transfer process controls delta handling and therefore allows you to fill several targets with different deltas from one source. With a data transfer process, you do not need to explicitly initialize the delta method as you do when copying data with an InfoPackage.
or you can create a sepeate Ip for delta apart form full and init .. that will laod delat data in cube ..
Regards,
shikha

The delta update for the InfoCube ZCUBE is invalidated

Hi BI Experts,
I am working on BW 3.5.
For the datasource 2LIS_13_VDITM there were some requests(deltas) missing for 3 days. So I got all the documents there were missing or not updated in BW. I deleted the setup tables and filled them with the new document numbers.
I did a full repair request from the Infopackage level and the data got updated in ODS.
But the DM Status is missing for all the requests in the ODS.
And the data for the full repair request didnt get updated in the Cube and I got the following error:-
The delta update for the InfoCube ZCUBE is invalidated. The can be due to one of the following:
1. A request, which was already retrieved from the target system, was deleted from the InfoCube.
2. A request, which was not yet retrieved from the target system, was compressed in the InfoCube.
And the following delta was also not successfull.. How can I clear up this mess and ensure smooth flow of deltas. How can I set the DM status.
Thanks
Kumar

Thanks for your reply.
When I did a Full Repair Request on the ODS the data is in the New table and the DM status got reset(vanished). And the following day delta got failed( data for that request did not get updated in ODS and Cube)
How can we bring back the DM Status and make the deltas successfull.
Thanks
Kumar

Billing Cube

Hi
Can anybody send me the BI content link for Billing Cube.
Bye

Hi J B,
Sales Overview cube we use for billing aswell.
http://help.sap.com/saphelp_nw04/helpdata/en/71/1769372b2b7d20e10000009b38f842/content.htm
For CRM link
http://help.sap.com/saphelp_nw04/helpdata/en/04/47a46e4e81ab4281bfb3bbd14825ca/frameset.htm
Assign points if it helps...
Regards,
ARK

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.

Master Data is missing for Specified Matierials at cube level !!

Hello Experts,
Good Day..!!
I have been facing an issue in my project, Master Data is missing for a KF and values are not displayed in a report for the specified matierial Nos. Where as other matierial nos KF values are displaying.
Intially, i checked from Cube End and found the issue is in Cube level only.
For that in the data flow, i already checked whether the data has been loaded perfectly or not.
Tried to reran the DTP once again and checked the values for the KF in the report and unfortunately KF values are not displaying for specified matierials only.
Kindly advice how can i move further..
Thanks,
SN.

Hi,
Check if SIDs are generated for the infoobject, if not try to do the change run attribute and then load the data to Cube.
Hope this helps...
Rgs,
Ravikanth.

Manual Billing is missing for service period 06/19/2009 u2013 7/21/2009

HI
Can anybody help me to fix the below issue?
Issue: The Manual Billing is missing for service period 06/19/2009 u2013 7/21/2009 for contract 9018967003.
After completing the Billing and invoicing using EASIBI t-code and looking at the refreshed ES32, i found that Manula billing is missing for service period 06/19/2009 to 07/21/2009.
thx
DGR

Hi,
It seems you have processed normal billing and invoicing process.
If the individual invoicing process is successful, the invoicing document should get created and posted unless outsorted.
In your case, if the invoicing document is outsorted, you would be able to see the billing document. (in refreshed ES32 view as mentioned) .
For the billing document, you can check the invoicing document as well, when you display the billing document ... check the print document tab on the same.
If the invoicing document is visible and is not posted, it would be out sorted. Either check the EMMA tcode processing for the same as it seems, an EMMA case might have generated as you are unable to view the same in EA05.
Hope this helps!!
Regards,
Rajesh Popat

Cubes for Billing, BAcklog and Sales forecast

HI
I want to know the cubes for the following. Billing, BAcklog and Sales forecast
Regards
sam

Hi,
You can use 0SD_C03 cube for billing and all related to sales or using 2lis_13_vditm and 2lis_13_vdhdr youcan create your own ODS for billing.
http://help.sap.com/saphelp_nw70/helpdata/EN/38/0c853c01c89d7ce10000000a11405a/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/71/1769372b2b7d20e10000009b38f842/frameset.htm
Regards.

Billing Request Editor - "Customizing missing for Characteristics"

Our Production system is getting the following error when users are trying to access the Billing Request Editor;
This same error doesn't exist in our lower landscapes and I've validated that the Characteristics for Billing Request Editor are in sync with one another. Is there more configuration that I am missing? Any assistance is appreciated.

We ended up removing the table entries and recreating them from another lower landscape environment. That seemed to work for now.

Delta Upload for Flat File

Hello Everyone
i am srikanth. i would like to know wheather do we have a facility for Delta Upload for flat file. If yes can u please give me the steps.
thanks in advance
srikanth

Hi Sabrina...thank you for ur help...i did load the data from cube to ods
steps.
1. i generated export data source on the cube
2. i found the name of the cube with prefix 8<infocube name> in the infosource under DM application component.
3. there are already communication structure and transfer rules activated but when i am creating update rules for the ods..i am getting the message 0recordmode missing in the infosource.
4. so i went to infosource and added 0recordmode in communication structure and activated but the transfer rules in yellow colour..there was no object assigned to 0recordmode but still i activated.
5.again i went to ods and created update rules and activated (tis time i didnt get any message about 0recordmode).
6.i created infopackage and loaded.
a)Now my question is without green signal in the transfer rule how data populated into the ods and in your answer you mentioned to create communication structure and transfer rules where in i didnt do anything.
b) will i b facing any problem if i keep loading the data into the ods from cube (in yellow signal) ..is it a correct procedure..plz correct me..thanks in advance

When we drilldown at document level it displays one record for each cube

Dear Experts .
The users want to see the report by status for the order detail report at document level it displays one record for each cube .
They want to see the single line for the order quantity , Amount, Billing quantity delivery and amount along with the Sales order number , billing document number billing date , delvert date ..et in signgle line. ( Sale order DeliveryBilling)
When we are doing on Multiprovider recording displaying from each cube.
We have tried with Constant selections and it is not giving the required results m since these want to see by status. Due to huge data performance reasons we re unable to use it .
Please provide your valuable inputs.
Thanks,
Mahesh.

Mahesh,
If you want to get detail data with respect to Sales order - delivery - Billing, on top of Multiprovider you can come up with Constant selection.
But I am not clear that why constant selection is not working properly, can I have some light on that.
Probably, you are struggling with multiple records .
I suggest you to go with end routine and map all fields to one IC and do reporting on that single IC, then your requirement will fulfill.
But here we need to take care of performance issues and process chain scheduling wile loading deltas.
If Multiprovider is not working properly , then try with Infoset(If you have more than 2 ICs it not possible).
Regards,
rvc

DELTA AND INIT TO CUBE Simple

Please help me with this, I have a bad red delta request coming from billing ods in bmw cube so i deleted the request, but bmw cube has other green request coming from order and delivery which is fine green and success.
now to resolve this i deleted the red delta request of billing and also deleted every thing from ods and i redo the set up table and did init to billing ods but now when init goes to bmw cube it fails please tell me the exact step to resolve this please tell me how can i set up the delta again so that init from billing ods goes to cube
help me with navigation step.i do not want to delete the entire data from cube to resolve this
thanks
soniya
soniya

Let me try to get it.
Your ODS has delta coming in for a specific fiscal period? Is there no overlap (meaning one billing document coming in as new into the ODS and cube is not changed in the next period)?
If not, there may be a problem.
Consider the case where you had a document which came in earlier (successful) request, and is there in the cube (say with a original qty of 25). Now, say your last delta had a change to it (of qty increased by 5, say), and this delta failed to go to the cube. Now you are doing a full load with repair for this period.
Since you are doing a full load, it will bring a qty of 30; however your cube has the earlier record (with a value 25), so instead of total 30 (correct) you will end up with a value of 55(incorrect).
The difference here is that your delta which failed had a qty of 5 (incremental amount) for this doc, but now you are bringing the qty of 30 with a full load.
This is a theortical scenario which can cause inconsistency to your data. If there is no case where an earlier existing record was being changed in the last delta (ie last delta had all new records) then you should be ok.

Delta with reversal into cube from LO extractors

Hi SDN,
In our LO extraction design we have write-optimized DSO used as EDW as the first layer in BI. Then data is sent to Business Content infocubes, such as 0PUR_C01 though we are using their copies and instead of Update Rules/Transfer Rules, we are using PSA, Transformation, Write Optimized DSO, another transformation and onto the cube. DS and all other objects in the data flow are BI 7.
What we are not clear about is the role or ROCANCEL when passed to both STORNO and RECORDMODE and its impact on the cube after the write-optimized DSO. Some key figures are reversed for 'R' but others are not.
We had thought that 2LIS_02_ITM via a Write Optimized DSO will pass on STORNO and RECORDMODE to the cube which should have reversed all key figures in the cube if the value is 'R'. But it is not happening. Whatever key figures were reversed in the source system, they remained reversed, others are still there and adding another row in the cube with some positive values.
Can anyone shed light on this or provide reference to documentation regarding delta processing in the cube, especially from LO extractors like 2LIS_02_ITM, etc.?
Thanks
SM

Friends,
Thanks for the reply.
My question is more fundamental.
In 3.5 There was expected to be no DSO between Source system and the cube. How were the Update, add and delete handled then?
As I see it, write-optimized DSO is no hindrance because essentially the data is coming into the cube as if there was no DSO in the middle. I do not see SAP suggesting a DSO anywhere between the source and business content cubes, especially in our case dealting with 2LIS_02_ITM, SCL, etc. to handle delta.
Are you saying that no delta management is possible without inserting a DSO before the cube? Please realize that WO DSO only brings data request by request without any summation and overwrite confusion.
What I puzzled at is the lack of comprehensive unfied and detail information either in documentation or a blog.
Please advise.
SM

Delta Missing for Billing Cube

Similar Messages

Maybe you are looking for