Invalid vales of characteristic and units of measure
Hello,
During the data load the system generated the following messages :
1. No SID found for value 'CBM' of characteristic 0VOLUMEUNIT
2. Value "X%X'''" (like that) of characteristic contents invalid letters
What do you reccomend to do?
hi,
check table t006a if CBM is there.
if you load from r/3, you may need to transfer from r/3, by rsa1 > source system > right click 'transfer global setting'.
you can maintain the unit use transaction CUNI.
Similar Messages
-
Partner profile LI and unit of measure
Hi gurus,
I am experiencing a weird situation and probably you have any clue about it.
I have configured an output to send the Purchase order information via EDI. I have used the standard function and programs to create the output. I have created the condition record for that particular vendor and output.
Then i have created the LI partner profile in we20 with the vendor number and the message types ORDERS and ORDCHG and I have also included my output with the ME10 and the ME11 in each of the messages.
When i create the PO and the output is sent I have the PO number but then i have the standard error message " Update was terminated" with the error "There is no conversion factor for material and unit of measure !" I have reviewed the PO and i have used a UoM PC that i have as an ISO code.
the point is if I use a different LI partner profile with exactly the same information then the idoc is sent without any problem. I have deleted the partner LI that I orinally created and i created it again as a copy of the one that is working but without sucess.
I have reviewed the vendor master data...but all is exactly the same.
I think or there is some config missing or that I have created the partner profile incorrectly. But it is rare that the partner profile has any link to the UoM.
Do you have any idea what it can be?
thanks so muchI understand from your mail, you have maintained the ISO equivalence to your UOM. When you change your vendor in WE20, did you change that information in MN04? This is the place where the right output type is triggered.
Other than that make sure you configured all the necessary items in WE20 -> Outbound Parameters -> process code and all otehr necessary settings.
Let me know, how it works?
Regards, -
Supplement Units of Measurement and Units of Measure
Hi All,
The company i work for, the WM system fabrics are stored in the Roll based form and in the QM module i have to create inspection lot for it. I found in the customizing "Supplement Units of Measurement and Units of Measure" which i think will help me in my process. Please explain the procedure for the "Supplement Units of Measurement and Units of Measure" in customizing.
Regards,
DTDhttp://help.sap.com/erp2005_ehp_04/helpdata/EN/c6/f83bb94afa11d182b90000e829fbfe/frameset.htm
-
Oracle and EPSG and Units Of Measure tabel.
I believe there is a wrong value in the Oracle 11g Enterprise database on Windows 64 bit.
We installed this a couple of months ago and found out that the Units Of Measure table is different from a Oracle 10g.
Here is what I think is wrong.
Oracle 10g Express Edition
9101 radian Radian angle 9101 1 1 ISO 1000:1992 EPSG FALSE
9102 degree Decimal Degree angle 9101 3.14159265358979 180 EPSG FALSE
9103 arc-minute angle 9101 3.14159265358979 10800 EPSG FALSE
9104 arc-second angle 9101 3.14159265358979 648000 EPSG FALSE
9105 grad angle 9101 3.14159265358979 200 EPSG FALSE
9106 gon angle 9101 3.14159265358979 200 EPSG FALSE
9107 degree minute second angle 9102 EPSG EPSG FALSE
9108 degree minute second hemisphere angle 9102 EPSG EPSG FALSE
9109 microradian angle 9101 1 1000000 ISO 1000. EPSG FALSE
9110 sexagesimal DMS angle 9102 EPSG EPSG FALSE Oracle 11g Enterprise
9101 radian Radian angle 9101 1 1 ISO 1000:1992 EPSG FALSE
9102 degree Decimal Degree angle 9101 3,14159265358979 180 EPSG FALSE
9103 arc-minute angle 9101 3,14159265358979 10800 EPSG FALSE
9104 arc-second angle 9101 3,14159265358979 648000 EPSG FALSE
9105 grad angle 9101 3,14159265358979 200 EPSG FALSE
9106 gon angle 9101 3,14159265358979 200 EPSG FALSE
9107 degree minute second angle 9101 EPSG EPSG FALSE
9108 degree minute second hemisphere angle 9101 EPSG EPSG FALSE
9109 microradian angle 9101 1 1000000 ISO 1000. EPSG FALSE
9110 sexagesimal DMS angle 9101 EPSG EPSG FALSE It is all about the conversion from 9110 to 9101.
11g tells me do nothing.
While 10g tells me to go via 9102, which in the end does pi/180.0.
I've checked EPSG v6.17 (Access database) which is similar as 10g.
Is it a know bug in Oracle 11g (why change it in the first place? it was correct).I filed this as a bug (9534127), and it's fixed.
The following is the workaround (as mentioned in the bug description):
begin
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9107; -- degree minute second, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9108; -- degree minute second hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9110; -- sexagesimal DMS, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9111; -- sexagesimal DM, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9203; -- coefficient, based on 9201
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9115; -- degree minute, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9116; -- degree hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9117; -- hemisphere degree, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9118; -- degree minute hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9119; -- hemisphere degree minute, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9120; -- hemisphere degree minute second, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9121; -- sexagesimal DMS.s, based on 9102
end;
begin
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9107; -- degree minute second,
based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9108; -- degree minute second
hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9110; -- sexagesimal DMS, based on
9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9111; -- sexagesimal DM, based on
9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9115; -- degree minute, based on
9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9116; -- degree hemisphere, based
on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9117; -- hemisphere degree, based
on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9118; -- degree minute hemisphere,
based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9119; -- hemisphere degree minute,
based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9120; -- hemisphere degree minute
second, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9121; -- sexagesimal DMS.s, based
on 9102
end;
begin
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
target_uom_id = 9001 where uom_id = 10031; -- Meter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
target_uom_id = 9001 where uom_id = 10032; -- Meter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1000, factor_c = 1,
target_uom_id = 9001 where uom_id = 10033; -- Kilometer, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1000, factor_c = 1,
target_uom_id = 9001 where uom_id = 10034; -- Kilometer, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .01, factor_c = 1,
target_uom_id = 9001 where uom_id = 10035; -- Centimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .01, factor_c = 1,
target_uom_id = 9001 where uom_id = 10036; -- Centimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .001, factor_c = 1,
target_uom_id = 9001 where uom_id = 10037; -- Millimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .001, factor_c = 1,
target_uom_id = 9001 where uom_id = 10038; -- Millimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1609.344, factor_c = 1,
target_uom_id = 9001 where uom_id = 10039; -- Mile, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1852, factor_c = 1,
target_uom_id = 9001 where uom_id = 10040; -- Nautical Mile, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .3048006096012, factor_c =
1, target_uom_id = 9001 where uom_id = 10041; -- U.S. Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .3048, factor_c = 1,
target_uom_id = 9001 where uom_id = 10042; -- Foot (International), based on
10032
update mdsys.sdo_units_of_measure set factor_b = .0254, factor_c = 1,
target_uom_id = 9001 where uom_id = 10043; -- Inch, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .9144, factor_c = 1,
target_uom_id = 9001 where uom_id = 10044; -- Yard, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 20.1168, factor_c = 1,
target_uom_id = 9001 where uom_id = 10045; -- Chain, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 5.0292, factor_c = 1,
target_uom_id = 9001 where uom_id = 10046; -- Rod, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.20116619497596571965479068149417, factor_c = 1, target_uom_id = 9001 where
uom_id = 10047; -- Link, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.30481225298450596901193802387605, factor_c = 1, target_uom_id = 9001 where
uom_id = 10048; -- Modified American Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.30479726511509957523453133559723, factor_c = 1, target_uom_id = 9001 where
uom_id = 10049; -- Clarke's Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.30479951799004225054718498468167, factor_c = 1, target_uom_id = 9001 where
uom_id = 10050; -- Indian Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.20116782494375873394114972441151, factor_c = 1, target_uom_id = 9001 where
uom_id = 10051; -- Link (Benoit), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.20116765121552632252046201402296, factor_c = 1, target_uom_id = 9001 where
uom_id = 10052; -- Link (Sears), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
20.116782494375873394114972441151, factor_c = 1, target_uom_id = 9001 where
uom_id = 10053; -- Chain (Benoit), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
20.116765121552632252046201402296, factor_c = 1, target_uom_id = 9001 where
uom_id = 10054; -- Chain (Sears), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.914398553970126751641554954045, factor_c = 1, target_uom_id = 9001 where
uom_id = 10055; -- Yard (Indian), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.91439841461602873872937279101345, factor_c = 1, target_uom_id = 9001 where
uom_id = 10056; -- Yard (Sears), based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1.8288, factor_c = 1,
target_uom_id = 9001 where uom_id = 10057; -- Fathom, based on 10032
end;
begin
update mdsys.sdo_units_of_measure set factor_b =
.017453292519943295769236907684886, factor_c = 1, target_uom_id = 9101 where
uom_id = 10001; -- Decimal Degree, based on 10002
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
target_uom_id = 9101 where uom_id = 10002; -- Radian, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.0000048481368110953599358991410235795, factor_c = 1, target_uom_id = 9101
where uom_id = 10003; -- Decimal Second, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.00029088820866572159615394846141477, factor_c = 1, target_uom_id = 9101
where uom_id = 10004; -- Decimal Minute, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.015707963267948966192313216916398, factor_c = 1, target_uom_id = 9101 where
uom_id = 10005; -- Gon, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.015707963267948966192313216916398, factor_c = 1, target_uom_id = 9101 where
uom_id = 10006; -- Grad, based on 10002
end;
/ -
Change Material Number and unit of measure
Can we change material code and / or its Unit of measure . Please help
http://sap-img.com/materials/change-base-unit-of-measure.htm
Re: change material code
Change of unit of measure -
Material Master IDOC MATMAS05 and unit of measure
Hi
We are using SAP standard material master IDOC type MATMAS05 to trigger IDOC. Our material master is having base unit of measure as "G". We are not using ISO unit of measurement. But Material master IDOC, segment E1MARM is populating base unit of meaurement (MEINS) as "GRM".
Any idea why IDOC is picking ISO unit of measurement instead of material master base unit of measurement.
Any idea how to send base unit of measurememt as "G" instead of "GRM" in DOC segment.
Thanks
NileshThats the way it works. In any interfacie to or from external sys. , it uses the ISO code from CUNI instead of the UOM .
-
Valuation of characteristics for unit of measure "" causes rounding diff
Dear gurus,
I am facing a problem on Goods Issue and Transfer Posting. My Material is maintained with Batch Specific Unit of Measure.
Base Unit = Kg ,and Batch specific unit of Measure = BAL(Bales).
My unit of Issue = BAL. For every bale at the the time of GR, i m storing the wieght of the Bales in the system. Now at the time of Issue and transfer posting, system is giving the following error message:
"Valuation of characteristic for unit of measure BAL causes rounding diff"
In unit = KG, Decimal places = 7, Decimal places rounding = 7
In Unit = BAL, decimal places = 3, Decimal places rounding = 3.
Kindly help me guys...
ThanksDear Johi,
See SAP NOTE 147489 - Error XU033 in goods movement with active ingredient. If you doesn't need to check rounding errors:
"For this use the following path: Logistics -> General -> Batch Management -> Define System Message Attributes (Transaction OCHS)."
Edit the system message XU03 to no errors.
Regards -
Unit of Measures missing in Crystal XI
Crystal Reports XI fixpack 3.2.
I'm designing a crystal report that contains a distance field with a measurement and unit of measure. In bex the value displays correctly,eg. 104,000 KM. In crystal I have three options for my key figure: Value, formattted value and Unit.
The value field contains 104,000, the formatted value contains 104,000 KM and the Unit field should contain "KM" but it's empty.
I don't get anything from unit field for any of my data rows (about 100 rows returned).
Do I need to make some setting adjustment or something? Any and all suggestions are welcome.
Thanx,
erUpon further review I noticed that the Unit dimension is being correctly populated when the value is a monetary amount. For example $100 CAD, the CAD is populated in the Unit dimension for this key figure. The distance measurements (all KM) don't have anything.
The UOM is present in both key figures in the bex query when run in Bex Analyzer. -
I have my base unit of measure set as EA and in the additional unit of measure I'm trying to put a conversation to state that 1 EA = 165838 KG
The system wouldn't allow that since the this field in the table only accepts 5 characters and 0 dec. (it also saves the digits in x,xxx format which means I can only give 4 digits).
Is there anything to do to fix this? I can't store in Ton because it won't be accurate.
Thank youIdeally your base unit should be the smallest unit or a small unit. In this case KG should have been the base unit.
However, if you still wish to continue...
try using 500 EA = 82919 TON (This is exact if 1 TON = 1000 KG)
If it is not allowing 5 digits, and you are willing to have a minor approximation, you can use
50 EA = 8292 TON. At 1 TON = 1000 KG, this works out to 1 EA = 165840 KG (A difference of 2 KG from actual figure).
Hope this helps,
Lakshman
P.S. Dear Srao, changing the number of decimals in currencies and Units of measures is not recommended. -
Issue: Proportion/produciton unit of measure NO is invalid for item 900001.
Hi All,
Issue: Proportion/produciton unit of measure NO is invalid for item 900001.
Here we have MTO Scenario: In outbound delivery when we do batch split & batch determination we are getting the above error.
Consider the following settings: at MM01 - Prodution/Proportion unit data is maintained with a characterstic specific to batch. Means Batch specific unit of measurement. In Work scheduling view produciton unit, unit of issue are maintained as 'NO'. All these settings are same for all material codes.
Please suggest us why we are getting the issue for perticular material coce.
Info: We resolve the issue by adding one more line item in the sales order & do the transfer posting the stock from line item to line item. But this is not the permanent solution.
Regards
ChowdaryI believe the error message no is VL 382 (Proportion/product unit of measure & invalid for item &)
You need to double click on the error message flashing on the status bar to get the error number.
I believe long text for the error message is self explainatary. Refer it and make necessary changes to resolve the issue.
Diagnosis
You want to use a proportion / product unit for an item.
You are not allowed to change the unit of measure into a proportion / product unit if:
- The following exist for a sales document item:
Preceding documents
Subsequent documents
- You are processing a scheduling agreement for the component supply industry
- You change the target unit of measure in a scheduling agreement item (and the sales unit is not a proportion / product unit)
- You are processing a customer requirements plan
- The following exist for a delivery item:
Preceding documents
Subsequent documents
Batch split items
- You are processing a batch split item
Procedure
Use a different unit of measure.
If you want to change the target unit of measure into a proportion / product unit in a scheduling agreement item, you need to change the sales unit accordingly. The system then sets the target unit of measure to the same as the sales unit.
Further, if you are working on older version, refer SAP Note 364206 - VLSP:indic.for proportion/product quantities deletd.
Regards
JP -
Create Characteristic with multiple units of measure
Hello Friends,
I want to create characteristic (CT04) which has multiple units of measure. At present a Characteristic is created with a single unit of Measure. I have to create characeristic and assign it in MIC. MIC specifications are customer dependent. Customer may give specifications in different unit of measure. While creating sales order, I am entering the specifications for characteristics, as material is created with varient.
I am creating Single Characteristic multiple times for different Unit of Measure and assigning it to the class.
Therefore according to the Customer requirment and his specifed Unit of Measure, that Characteristic is choosen having same UoM as of Customer.
Insead of doing this, Is it possible to assign multiple units of measure to single characteristic?
Waitng for reply!
Regards,
KiranHi,
With Multiple Unit Of measures, I don't think its possible.
You can Use CHAR for characteristics, to Use.
Instead for Fixed Units. Let Marketing/sales Enter the req.
But you shall make it Multiple Selection, Since you can use them in Selection Condition.
Hope this is Useful.
Regards
Raghu -
$CL - Create Characteristic with multiple Unit of Measure
Hello Friends,
I want to create characteristic (CT04) which has multiple units of measure. At present a Characteristic is created with a single unit of Measure. I have to create characeristic and assign it in MIC. MIC specifications are customer dependent. Customer may give specifications in different unit of measure. While creating sales order, I am entering the specifications for characteristics, as material is created with varient.
I am creating Single Characteristic multiple times for different Unit of Measure and assigning it to the class.
Therefore according to the Customer requirment and his specifed Unit of Measure, that Characteristic is choosen having same UoM as of Customer.
Insead of doing this, Is it possible to assign multiple units of measure to single characteristic?
Waitng for reply!
Regards,
KiranWhat UOM's are we talking about?
Are you talking about ppm vs. %? Or ppm vs. ppb?
SAP can make some of these conversion automatically. I encourage clients to standardize what their lab people report on in inspection lots. I.e. they should always record ppm or always record % in the inspection lots.
In the certificates you can use the certificate profile to change the UOM actually reported on the COA to the customer. So you can record by ppm in the lab, but in the cert for the characteristic, you indicate that it should be reported in %. The system will automatically make this conversion for you.
If you are talking somethign like screens, I recommend doing all in the lab as either thru or on and doing calculated characterisitcs to calculate the opposite for those customers that want thru instead of on, or vice versa.
FF -
Display alternate unit of measure as a characteristic
Hello,
I have successfully implemented the 'How to ... Report Data in Alternate Units of Measure' using the business content infocube 0IC_C03, Material Stocks/Movements.
The infocube currently contains only base unit of measure.
In the queries I am displaying key figures in base unit and alternate unit of measure.
My requirement is to subtotal by alternate unit of measure. Is this possible? If I add 0BASE_UOM to the query this has no affect on the alternate unit of measure.
Can I add an alternate unit of measure characteristic to the infocube and populate it during query run time? Where would this configuration take place?
SAP_BW 3.1, content 3.3.
Thanks for any suggestions,
MarkHI,
Go to Inforecord of that material with that vender on that plant.
Change Inforecord(me12)...here in general data...change the order unit.
system will give the conversion factor as u defined in material master.
Hope Help U !
Regards,
Pardeep Malik -
Report on material code, description and all unit of measure conversions
report on material code, description and all unit of measure conversions ?
any ideas?Material Number MATNR
with this key and SPRAS (the desired Language key)
from MAKT you can get the descriptions..
and with MATNR from MARM you can get alternative UOM and the conversion rates.
If you need help on MARM how to get the conversions please notify.
Hope it helped
Please reward if found useful
Best Regards -
Unit of measurement for materials received and withdrawn
Hi Experts,
Base unit of material is KG whereas sales unit is M2 and conversion is maintained between both. Now I am using sale unit (M2) while entering material componenets. Then I am raising PR, PO, GR in project and withdraw the material in sale unit M2. But system updates the report in KG (under purchasing data tab of component). When I get material report, system shows reqmt qty in M2 but received and withdrawn qty in KG. Its confusing and doesn' serve the reporting purpose. Can we do something so that received and withdrawn qty will appear in M2 (sale unit) rather than KG (base unit)?
Thanks and Regards
Dinesh ChauhanHi,
To resolve this issue, you need to maintain the conversion factors. In material master, additional tab, unit of measure tab you need to maintain the conversion factors. Say example I Kg = How much M2. If you maintain this the system will convert automatically all the Kg in to M2, or vice versa you can do. Otherwise you can maintain the conversion factors in the Info Record also for externally procured materials.
Regards,
V. Suresh
Edited by: V.SURESH on Jan 5, 2009 12:19 PM
Maybe you are looking for
-
Access violation error with 1.4.0
Our client/server application (RMI) ran fine in 1.3.1. When we compiled and deployed with 1.4.0, an error of "access violation" were thrown by Windows NT or Windown 2000 at run time. Stack trace posted as below. Anyone has any ideas on the cause of i
-
Very slow PDF generation when conditional text is hidden in FM 9.0
I am working on 96-page chapter of a larger book. A 7-page section of the chapter needs to be hidden until the next release, so I hid it with conditional text. After doing this, the "Save as PDF" printing process goes from taking 6-7 seconds to takin
-
Preventing my 7 year old from seeing (on his Ipad) what I see on my Iphone
So, I am surfing for Christmas gifts.... maybe some other adult type gifts. I signed my sons I pad up to my Itunes account. He is getting access to all my apps, Icloud whatever. How do I stop it? I have no problem creating his own apple ID and email
-
i have tried several times to get my 80g ipod classic into disc mode and it just won't go. I get the apple logo but when i hold menu+play nothing happens. Am i doing something wrong?
-
SYSLOGD gone wild - where are the files?
Hey all, Yesterday I had 15GB of free HD yesterday, it told me today that I was down to 100MB. Confused - because I haven't added any files, I check the activity monitor and found that SYSLOGD was running, and using an absurd amount of processor and