Non cumulative with non-cumulative change
Hi Experts,
I have a Question !, As i know that i can create Non-Cumulative Figure By Means Of two ways:-
1. Non cumulative with non-cumulative change and
2. Non Cumulative with Inflow and Outflow.
the second one is very clear but i am not very clear about 1st option i.e What Non-Cumulative Value changes is? and how it calculates the non-cumulative Value.
If u have an Idea please share your knowledge...
Ragards
Prakash
The 1st option is for key figures like headcount or similar, which you would like to store as a total figure in a cube instead of a DSO in a scenario where you are using a multiprovider on this together with other non-cumulative cubes.
The SAP help below explains this quite well
http://help.sap.com/saphelp_nw04/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
Best,
Ralf
Similar Messages
-
Non cumulative with non cumulative value change
hi,
can any one tell the concept of non cumulative with non cumulative value change with an example with numbers,i am bit confused .
like we have for non *** inflow and outflow- stocks inflow and outflow so non *** is based on inflow and inflow.
in the same way any example for above conceptHi Venkat,
If I under stand your question correctly you wish to have an example of where non cumulative values are used and you have given the value of stock? If so here is an example with figures
So you would do an initial load loading the opening balances of Stock.
Say material number 12345 = 100 units
After that, only movements will be posted so Stock will either increase or decrease depending on what image is posted via the change log.
So there will be a purchase of material 12345 for 50 units so now the balance of material is 150.
But then you could use or sell 70 units of material 12345 so you stock value would be 80 units
I hope this makes sense and this is an example that you are after if not please let me know and I'm happy to help
Regards
Ben
PS assign points if useful -
Cumulative and Non-cumulative KFs
Guys,
so I am confused about cumulative/Non-cumulative keyfigures. I read what it says about them on help.sap.com
Flow/non-cumulative value
You can select the key figure as a cumulative value. Values for this key figure have to be posted in each time unit, for which values for this key figure are to be reported.
Non-cumulative with non-cumulative change
The key figure is a non-cumulative. You have to enter a key figure that represents the non-cumulative change of the non-cumulative value. There do not have to be values for this key figure in every time unit. For the non-cumulative key figure, values are only stored for selected times (markers). The values for the remaining times are calculated from the value in a marker and the intermediary non-cumulative changes.
Non-Cumulative with inflow and outflow
The key figure is a non-cumulative. You have to specify two key figures that represent the inflow and outflow of a non-cumulative value.
For non-cumulatives with non-cumulative change, or inflow and outflow, the two key figures themselves are not allowed to be non-cumulative values, but must represent cumulative values. They must be the same type (for example, amount, and quantity) as the non-cumulative value."
and also checked a few threads on sdn but still a little confused about their purpose.
Can someone tell me when do we use which one?
Thanks,
RG.Hi Ram,
Cummulative & Non Cummulative Key Figures :
Basically the key figures are of two types cumulative and non cumulative.
Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
Now
1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
2)NCum. value with NCUM value change:
In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
In this case you will this option and use the key figure here in the space provided.
3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
you use one key figure for the inflow and one key figure for the outflow.
The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
net value of stocks( inflow- outflow).
Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory. here the aggregation of key figure is based on the another info object
There are two different ways to define non-cumulative key figures:
u2022 Non-cumulative key figure with non-cumulative changes:
Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
u2022 Non-cumulative key figure with inflows and outflows
There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
Features of non-cummulative key figures
A non-aggregating key Figure.
Records are not summarized for Reporting
Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
Examples: Head Count, Account balance, Material stock
consider simple senario
Date Net Stock Quantity Sales Revenue
01.02.2005 40 1000
02.02.2005 50 2000
03.02.2005 25 3000
this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
if stock quantity taken as a cummulative key figure
Date NET STOCK QUANTITY SALES REVENUE
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 100 6000
in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
if stock quantity taken as non-cummulative key figure
Date Net Stock Quantity (LAST) Sales Revenue
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 20 6000
Hope it helps you.
Thanks & Regards,
SD -
Problem with Non-cumulative key figure.
Hi all,
I am facing the problem with the Non-cumulative Key Figure (Quantity). I have created and loaded data to the non-cumulative InfoCube. <b>This cube is defined by me to test the non-cumulative key figure.</b>
<b>In BEx query the non-cumulative key figure and cumulative key figure (Value change) both display same values, i.e. non-cumulative key figure contains the same values which we have loaded for cumulative value change. Non-cumulative key figure is not calculated based on associated cumulative key figure.</b>
I have done the following while defining the non-cumulative InfoCube:
1. Created a non-cumulative key figure which is associated with a cumulative key figure (value change).
2. Loaded data to non-cumulative InfoCube from flat file.
3. Compressed data in non-cumulative InfoCube after the load.
Note:
1. Validity area is determined by the system based on the minimum and maximum date in data.
2. Validity determining characteristic, 0CALDAY is the default characteristic selected by the system.
Is there any other settings to be done?
Please help me in resolving this issue.
Thanks and regards
Pruthvi RBeing a non-cumulative KF, total stock is automatically takes care of that.
Try putting all the restrictions which you have included for total receipts and total issues, for eg, restrict Total Stock with the movement types used in Receipts as well as Issues.
Check and revert.
Regards
Gajendra -
Archive Stock Cube with non-cumulative nature
Hi All,
I have been trying to archive the Inventory (Stock) Infocube as we have more than couple of hundread million records in the cube and it is taking long time to execute query.
I know how to acrive the regular cubes and DSOs, but I couldn't find any helpful documentation where I can know how to archive the Infocube with non-cumulative nature or containing Marker update.
Can anyone pleaes post the link of document?
BTW, we are using BI7.0 SP15
Thanks,
DhavalHi,
There are two ways of archiving data from a non-cumulative InfoCube - time slot archiving and archiving with selection characteristics.
Time slot archiving (recommended)
As an archiving method, you must choose for a non-cumulative InfoCube, time slot archiving for the time reference characteristic. When you recreate an archiving object for a non-cumulative InfoCube, this characteristic is also suggested by the system.
Only archive non-cumulative changes up to a specific point in the past. This reduces the volume of data in the InfoCube. The marker (= end non-cumulative) remains unchanged.
In the variants maintenance screen, in the archive administration, under Non-Cumulatives, choose the Movements Only option.
You are only able to archive the marker if you also archive all of the non-cumulative changes. Subsequently, the contents of the non-cumulative InfoCube are archived completely. In the variants maintenance screen, in the archive administration, under Non-Cumulatives, choose the Movements and End Non-cumulative option.
You must archive the non-cumulative changes (for all times) first, and then archive the marker in a separate archiving run, so that the non-cumulative changes and the marker are stored separately in the archive.
The advantage of time slot archiving is that archiving runs can be carried out periodically using a single variant with a relative time restriction. The alternative archiving method described below does not have this advantage.
Archiving with selection characteristics
In some cases, archiving based only on time slots does not have the required effect of reducing the volume of data in the InfoCube. This is the case, for example, if the non-cumulative bearing objects are subject to high fluctuations, meaning that data is constantly being loaded for new objects and old objects are made obsolete. With time slot archiving, the end non-cumulative remains for all objects until all of the data in the InfoCube is finally archived, even if all the non-cumulative changes for an object have been archived already.
In this case, you want to archive and delete completely any objects that are no longer active in the InfoCube. This means archiving the marker as well. For other objects that are still active, you only need to archive the non-cumulative changes from the past, which means the marker is retained.
When you define the archiving properties for a non-cumulative InfoCube, do not therefore choose the time slot archiving method. Instead, select individually the characteristics that are relevant to restricting archiving runs. The time reference characteristic should also be included in this selection whenever possible.
Using this archiving method, for each archiving run, you need to create selection conditions in a variant. In the variant for the archiving run, in addition to the selection conditions, you can also specify for the selected characteristics whether or not non-cumulative changes and marker data is archived. If you choose to archive marker data, be aware that the time selection contains the maximum value for time.
Please refer to the below link to archive the data for Stock Cube:
http://help.sap.com/saphelp_nw2004s/helpdata/en/3f/c219fe9a46194aa66d55254fdab182/frameset.htm
Hope this helps.
Regards
Tanuj -
Problems with Non-cumulative Cube
Dear All,
I have a cube with non-cumulative key figures. An DSO supply data for that cube.
The query on that cube will gets wrong results sometimes. But after removing all the data from that cube and uploading again from the DSO, the query presents the right result.
Is there anybody knows why and how to fix it?
Thanks.
BolunHi
Non-cumulative Cubes to be defined correctly with Inflow and Outflow because it depends on Which option you choose depends on how you want to evaluate the non-cumulative key figure, and also the Marker Update you are dealing with.
The key figures for non-cumulative value change or for inflows and outflows are normal cumulative key figures that have u2018summationu2019 both as aggregation and exception aggregation. Generally, Non-cumulative key figures always have summation as standard aggregation.
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a6305e07211d2acb80000e829fbfe/frameset.htm
Hope it helps and clear -
Bad performance with non-cumulative key figures
Hi All,
I have a cube with 8 non cumulative key figures based on fiscper.
I am not sure how the performance for reporting with non-cumulatives can be improved.
Thanks
KarenPerformance of non cumulative cubes is dependant on the distance between the marker (date of the last compression) and the execution date.
For actual stock, the more you compress the better it is.
Regards,
Fred -
InfoProvider with non-cumulative key figures
what does infoprovider with non-cumulative key figures...
noncumulative key figures..
looking for replyit's property of the KF... nothing do with Cubes or ODS.
Name itself telling non-Cumulative KF. We can't cumulate this KF. Suppose take the Case Sales Amount and No of Employees. Sales Amount can be cumulated over Time. But No Employees can't be cumulated. Same is the Case with Stock as well.
Nagesh Ganisetti. -
Error when activating Cube with Non-cumulative KF
Hi all,
I'm trying to re-activate an InfoCube but now with non-cumulative KF and I'm getting the error message "Object YYYYY could not be activated".
Please help!
Best regards,
Thiago Modrohi,
have you included the neccessary time characteristics
http://help.sap.com/saphelp_bw32/helpdata/en/80/1a62dee07211d2acb80000e829fbfe/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Ramesh -
BPS: Planning with Non-Cumulative KF
Hi All,
i'm trying to implement Headcount Planning and to do this i'm thinking to use a non-cumulative KF (Headcount) with delta cumulative KF (Hiring and Dismissal).
The user should plan the delta cumulative KF.
I would like to know if this is possible in BPS 'cause i have read that it's "better" not to use non-cumulative KF in BPS.
Thanks in advanceVery Thanks Marc,
so you say me that i cannot plan on the cumulative KF associated to the Non-Cumulative one, example:
1) ZHEADCNC -> Non-Cumulative KF with INFLOW and OUTFLOW:
1a)ZHEADCAS -> Cumulative KF for INFLOW
1b)ZHEADCCS -> Cumulative KF for OUTFLOW
Is it not possible to plan on 1a) and 1b) and get the exact value on the non-cumulative KF?
The question is that the user should plan the headcount variation and not the "headcount stock" on a defined cluster.
I appreciate any hints -
Difference between cumulative and non-cumulative key figures
Hi,
What is the difference between cumulative and non-cumulative key figures and under what conditions they are used. What is snapshort and where it is used.Hi.............
Basically the key figures are of two types cumulative and non cumulative.
Cumulative are the normal one which you use always and they always bring the new values of the key figures in the delta that is if suppose A has value 10 and after change the new value is 20 then you will use cumulative key figures there, and your delta( new value) will bring 20.
but suppose your key figures field only the change in the prior value that is in this case the delta in the key figure value will bring 10 (20-10- change of 10 )as new value in the key figure A then you will have to model it through the non cumulaitve key figures.
Now
1) Cumulative is for the first case that is if the key figure alwyas brings the new values of the key figure and not the change sin the key fiures value.
2)NCum. value with NCUM value change:
In this case ther is only one field which brings the changes for a particualr key figure and you ahve to define that key figure as non cumulative.
Ex: In case of stock only one filed brings both ingoing value and outgoing value so 10 ,-4,100,-34.....
In this case you will this option and use the key figure here in the space provided.
3) In this case you haev two separate key figures one for the inflow of stocks and one for the outflow of the stocks.
you use one key figure for the inflow and one key figure for the outflow.
The main key figure autiomatically takes care of the logic and gives the correct output upon the summation
net value of stocks( inflow- outflow).
Also do remember in this case the key figure for inflow and out flow are the basic key figures that is cumulative key figures.
A non-cumulative is a non-aggregating key figure on the level of one or more objects that is always displayed in relation to time. Examples of non-cumulatives include headcount, account balance and material inventory. here the aggregation of key figure is based on the another info object
There are two different ways to define non-cumulative key figures:
Non-cumulative key figure with non-cumulative changes:
Before you can define the non-cumulative key figure, an additional cumulative key figure containing the non-cumulative change must exist as an InfoObject.
Non-cumulative key figure with inflows and outflows
There has to be two additional cumulative key figures as InfoObjects for non-cumulative key figures - one for inflows and one for outflows. The cumulative key figures have to have the same technical properties as the non-cumulative key figure, and the aggregation and exception aggregation have to be SUM.
Features of non-cummulative key figures
A non-aggregating key Figure.
Records are not summarized for Reporting
Exception Aggregation is being applied on these key figures on the level of one or more info objects usually with time .
Examples: Head Count, Account balance, Material stock
consider simple senario
Date Net Stock Quantity Sales Revenue
01.02.2005 40 1000
02.02.2005 50 2000
03.02.2005 25 3000
this is the query output if stock quantity has treated as cummulative and non-cummulative key figures
if stock quantity taken as a cummulative key figure
Date NET STOCK QUANTITY SALES REVENUE
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 100 6000
in the above result the key figure has aggregated to the total value that wont give sense to the net stock quantity
if stock quantity taken as non-cummulative key figure
Date Net Stock Quantity (LAST) Sales Revenue
01.02.2005 30 1000
02.02.2005 50 2000
03.02.2005 20 3000
RESULT 20 6000
Hope this helps you..............
Regards,
Debjani................
Edited by: Debjani Mukherjee on Sep 15, 2008 7:22 AM -
Non-Cumulative vs. Cumulative KeyFigures for Inventory Cube Implementation?
A non-cumulative is a non-aggregating key figure on the level of one or more objects, which is always displayed in relation to time. Generally speaking, in SAP BI data modeling, there are two options for non-cumulative management. First option is to use non-cumulative management with non-cumulative key figures. Second option is to use non-cumulative management with normal key figures (cumulative key figures). For SAP inventory management, 0IC_C03 is a standard business content cube based upon the option of non-cumulative management with non-Cumulative key figures. Due to specific business requirements (this cube is designed primarily for detailed inventory balance reconciliation, we have to enhance 0IC_C03 to add additional characteristics such as Doc Number, Movement type and so on. The original estimated size of the cube is about 100 million records since we are extracting all history records from ECC (inception to date). We spent a lot of time to debate on if we should use non-cumulative key figures based upon the standard business content of 0IC_C03 cube. We understand that, by using Non-Cumulative key figures, the fact table will be smaller (potentially). But, there are some disadvantages such as following:
(1) We cannot use the InfoCube together with another InfoCube with non-cumulative key figures in a MultiProvider.
(2) The query runtime can be affected by the calculation of the non-cumulative.
(3) The InfoCube cannot logically partition by time characteristics (e.g. fiscal year) which makes it difficult for future archiving.
(4) It is more difficult to maintain non-cumulative InfoCube since we have added more granularity (more characteristics) into the cube.
Thus, we have decided not to use the Cumulative key figures. Instead, we are using cumulative key figures such as Receipt Stock Quantity (0RECTOTSTCK) , Issue Stock Quantity(0ISSTOTSTCK)
, Receipt Valuated Stock Value (0RECVS_VAL) and Issue Valuated Stock Value (0ISSVS_VAL). All of those four key figures are available in the InfoCube and are calculated during the update process. Based upon the study of reporting requirements, those four key figures seems to be sufficient to meet all reporting requirements.
In addition, since we have decided not to use cumulative key figures, we have removed non-cumulative key figures from the 0IC_C03 InfoCube and logically partitioned the cube by fiscal year. Furthermore, those InfoCube are fiscally partitioned by fiscal year/period as well.
To a large extent, we are going away from the standard business content cube, and we have a pretty customized cube here. We'd like to use this opportunity to seek some guidance from SAP BI experts. Specifically, we want to understand what we are losing here by not using non-cumulative key figures as provided by original 0IC_C03 business content cube. Your honest suggestions and comment are greatly appreciated!Hello Marc,
Thanks for the reply.
I work for Dongxin, and would like to add couple of points to the original question...
Based on the requirements, we decided to add Doc Number and Movement type along few other characteristics into the InfoCube (Custom InfoCube - article movements) as once we added these characteristics the Non Cumulative keyfigures even when the marker was properly set were not handling the stock values (balance) and the movements the right way causing data inconsistency issues.
So, we are just using the Cumulative keyfigures and have decided to do the logical partitioning on fiscal year (as posting period is used to derive the time characteristics and compared to MC.1 makes more sense for comparison between ECC and BI.
Also, I have gone through the How to manual for Inventory and in either case the reporting requirement is Inception to date (not just weekly or monthly snapshot).
We would like to confirm if there would be any long term issues doing so.
To optimize the performance we are planning to create aggregates at plant level.
Couple of other points we took into consideration for using cumulative keyfigures are:
1. Parallel processes possible if non-cumulative keyfigures are not used.
2. Aggregates on fixed Plant possible if non-cumulative keyfigures are not used. (This being as all plants are not active and some of them are not reported).
So, since we are not using the stock keyfigures (non cumulative) is it ok not to use 2LIS_03_BX as this is only to bring in the stock opening balance....
We would like to know if there would be any issue only using BF and UM and using the InfoCube as the one to capture article movements along with cumulative keyfigures.
Once again, thanks for your input on this issue.
Thanks
Dharma. -
"initial non-cumulative for non-cumulative values" is not available in DTP (0AFMM_C02)
Hi Experts,
We are working for BI implementation for AFS Industry,
when we are working on AFS specific inventory cube 0AFMM_C02 , we are facing stock mismatch problem
for AFS Stock initialization we are using the data source 2LIS_AF_STOCK_INITALIZATION instead of 2LIS_03_BX, this data source is specificly designed for AFS
when we are extracting the data using 2LIS_AF_STOCK_INITALIZATION for stock initialization and
2LIS_03_BF data source to load the Moments.
we compressed cube with Marker update for 2LIS_AF_STOCK_INITALIZATION data load(by deselecting the No marker update check box)
we compressed cube with No Marker update for 2LIS_03_BF historical data load(by selecting the No marker update check box)
we compressed cube with Marker update for 2LIS_03_BF Delta data load(by deselecting the No marker update check box)
Now we are facing stock mistach problem, we found reason for this
"initial non-cumulative for non-cumulative values" option is not available in DTP only Delta & Full options are available
and infopackage of 2LIS_AF_STOCK_INITALIZATION data source also has "Full update" instead of "Generate Intial Status"
Please let us know how can we get the "initial non-cumulative for non-cumulative values" option in the DTP level.
Regards,
ChandraHi Chandrakumar,
We are facing the same problem, how do you solve it?
Regards, -
Cumulative and non-cumulative for key figure
Hi,
In the aggregation tab, we have the aggregate type SUM, Max or Min.
we also have the comulative/non-cumulative values.
what's the difference between comulative and non-cumulative values? it would be good to have some example for illustration. and does comulative and non-cumulative have any relation with aggregate type?
Many Thanks
JonathanHi,
what's the difference between comulative and non-cumulative values?
Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
Example: sales revenue, weight, etc.
Non-cumulative values are those key figures that are measured in relation to a period in time; that is to say they cannot be meaningfully cumulated over time. Non-cumulative values are summarized over time using so-called exception aggregation.Example:stock quantities/-values, number of employees, account balances, etc.
Does comulative and non-cumulative have any relation with aggregate type?
Different types of non-cumulative keyfigures.....are....
1.Non-cumulativekey figure = cumulative keyfigure with excep.aggregation
2.Non-cumulativekey figure withassociated singledelta (cumulative)
3.Non-cumulativekey figure withassociated in-andoutflow(cumulative)
check these links:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/92c0aa90-0201-0010-17b1-bf5b11c71257
hope it helps...
Regards
chandra sekhar
Edited by: chandra sekhar t on Nov 28, 2008 2:18 PM -
Cumulative and Non Cumulative Keyfigures
Hi,
What are Cumulative and Non Cumulative Keyfigures..? and
what is the lik betwqeen these keyfigures and the option " NO MARKER UPDATE " in the manage tab of infocube?
Can you please tell eloborately?
Regards
Naresh.Hi,
Cumulative values are those key figures that are cumulated using all characteristics, thus also using time.
Non-cumulative values are those key figures that are measured in relation to a period in time; Non-cumulative values are summarized over time using so-called exception aggregation.
In Inventory, When you initialize the stock by using BX Data source. It will bring the current status of the stock by calculating the past transactions happens in all the storage locations.
After loading the Data into Cube you compress the cube with Marker update, then system will take a reference point for the marker. Next when you load BF for the historical data, you compress with "No marker update". This may not be necessary in all the cases. If the client requires reporting on the past data you need to extract this. This time you run the info package with init Delta. If historical data is not required you can run the info pack INIT t without Data transfer.
In the above case you use No marker update, because you have initialized the stock by calculating all the historical data and then you are loading historical data, there would be data mismatch happen to avoid that use no marker so that it will not add to the reference point. Later you can run the delta loads by using BF data source. This time you need to use "Marker update" because all the delta movements are new they should be updated to reference point. Similarly UM also With marker updated for Price revaluations. Why Reference point: When you use Non Cumulative KF in the Cube, During query execution the data will come from Reference point which is set by marker update
Regards,
Maybe you are looking for
-
My back up last month saved everything but the previous one didn't so therefore I lost 2 years of photos. It says there was 3.9 GB saved but half my photos are missing and I only have 316 photos on my camara roll. how do I get this back please help
-
I have my new iPad and I went to the Apple Store to get a couple accessorys and I was facinated by the Smart Cover. So I bought it got home and it worked fine. The Sales person it would fit just as on an iPad 2. So I never owning an iPad 2 thought wo
-
How I upgrade iPad 1software to iOS 6.0
I can not down load Facebook linkeden all ask for iOS 6
-
Cisco Prime Infrastructure 2.1 Upgrade from 1.3.0.20
Hi, We have a full fledged CPI 1.3.0.20 running with about 150-200 buildings worth of wireless data. We need to upgrade it to 2.1 version to make use of the 702W APs WPPs. The upgrade is failing in a boot loop again and again no matter what we do. We
-
What's the coolest photo viewer for a macbook..?
Good Day, Recently I bought a macbook and I was wondering what is the best photo viewer for it, Thanks in advance for you further suggestions,