Production posting

Hi friends
I need to make the single step production posting to two steps .
eg ., currently i am doing production posting using movement type 311
I need to make it in two steps ie 313 and 315
Can anyone tell me the steps in detail..
Is this need to be done in customization or what should be done?
Thanks in advance for ur replies.

Hi,
311 movement type is for Transfer posting storage location to storage location in one step.In this
the quantity is transferred from unrestricted-use stock of the issuing storage location to unrestricted use in the receiving storage location.
In two step 313 movement type for quantity is transferred from unrestricted-use stock of the issuing storage location to stock in transfer in the receiving storage location.
Then in 315,the quantity is transferred from the
stock in transfer to the unrestricted-use stock in the receiving storage location.
Regards
ritesh

Similar Messages

Re:Query for no.of days delayed using Receipt from production posting date.

Dear SAP Experts,
I need a query to calculate no of days delayed by using Receipt from production posting date and prod.order due date..i have already done the query but there is no link for joining the tables.Is there any link to join the tables..
Plz Suggest a good query for this issue..
With Regards,
Revathy

Dear Revathy,
I think there is no need to link table if you just need calculate no of days delayed by using Receipt from production posting date and prod.order due date.
You may check this query with the above:
SELECT T0.ItemCode,T0.DueDate,
T0.DocNum, T0.CloseDate,
Datediff(dd,t0.DueDate,T0.CloseDate) Diff
FROM dbo.OWOR T0
WHERE Datediff(dd,t0.DueDate,T0.CloseDate) > 0
Thanks,
Gordon

Extended Production Posting in Localization for Chile

We are implementing SAP B1 Version 9.0 PL5 for a company in Peru and the used localization is the one for Chile.
According to the this power point
you activate the Extended Production Posting functionality this way:
But I don't see this options in our system...
Any hints?

OK.
Here is the link:
http://scn.sap.com/thread/3539773

Reciept from production posting date

Hi Everybody,
I m facing a problem in reciept from production document. I am adding Issue for production for a Production order in july date, now when I add recipt from production for that Production order in march, sap B 1 allowing me.
I want to stop this, Pls tell me the solution.
if SP is must for this , Pls provide me.
Thanks a lot in advance
Deepak Tyagi

Hi Deepak,
Check the thread
Re: Production order - post date - cannot change
*Close the thread if issue solved.
Regards
Jambulingam.P

Is there a PDF of the Adobe CS6 product poster available?

I need to hang one up in our classroom and the Adobe customer service reps I've chatted with (4 of them!) could not even understand the question. I need a 2 foot by 3 foot poster celebrating the master collection. I know that SOMEONE in Adobe has created one for trade shows and the like. I don't want to buy one. I just need a PDF that I will print out myself. Many thanks to anyone who can end my frustration.

Hi, HelpMe123456,
It's terrific that you'd like to have a poster of Creative Suite 6 in your classroom! Adobe doesn't typically release these PDFs, but I'll check with our marketing team.
May I ask if your classroom is in a school, college, university or training center?
Thanks,
Kirsti

Daily Automatic delivery creation for Finished Products

Dear All,
As per my client requirement, they need automatic delivery creation when ever the finished products posted(Reached) in to the Finished Products Storage location with out time specification.
Scenario is like this.
1.Scheduling agreement will be created for one month or one year for the specific customer with specific products.
2.After producing the material, from the production line finished products will taken in to the Finished product Storage location with some acknowledgement.
3.When ever the acknowledgement happen(stock get added) automatic delivery need to be created for that acknowledged quantity with reference the scheduling agreement.
4.There is no time specification When ever the finished products stock acknowledgement happen automatic delivery need to be created.
5.There is no quantity specification also what is the quantity at finished products Storage location acknowledged for that quantity automatic delivery need to be created .
6.If there is no production-->There is finished products -->No delivery should trigger.
This will be applicable to specific customer and specific material only.
Please give your valuable inputs as early as possible.
Regards,
Murali.

Dear Rohit,
1) Who creates the acknowledgement..
-->Finished Products Storage location people will run this entry when they recieve the finished product from the production line.
2) How frequently is this acknowledgement created..
-->When ever receives the finished products from the production line,
3) Is this acknowledgement a print out or a documetn type.
-->It is not a print or document type, it is just an Transfer posting entry to add the Finished products qty to the existing stock at that particular storage location.
4) If it is document type does it appear in document flow.
-->No it will not come in the document flow.
I hope it will clear for you,
Regards,
Murali.

Error in posting to Accounting

We hv created a new wagetype 1TLF-Telephone Exps. Reimbursement.We are posting the same to Accounting thru T.Code-PC00_ M99_CIPE.
System is giving an Error Msg.No.3G103;Posting balance is not cleared (Preriod 03/2007A)
Can anyone help in resolving the problem.
With Rgds.,
Rakesh Kumar
[email protected]

Hi Jigar,
I found very helpful SAP NOTE 179655 which should solve your issue.
The details of the note are below.
Reward if its helpful.
Thanks
Murtuza
A posting balance which is not cleared may occur due to three reasons which occur with different frequencies:
Customizing of posting is incorrect
The payroll is incorrect
Program errors occur during the evaluation
In almost all cases, if an employee is rejected because the posting balance is not cleared, Customizing of posting is incorrect (case A);in a smaller number of cases, this rejection reveals errors in the payroll (case B);only rarely, program errors exist in the programs for the evaluation created by SAP which lead to a rejection of the employee (case C).
Examples for case A
A deduction wage type (for example, 'Taxes payable') is not posted.
A wage part is not posted (for example 'Public holiday supplement')
A wage type is posted with the incorrect +/- sign (for example, an expense wage type which is stored with a + sign, the system incorrectly posts with reverse +/- sign that is, positive amounts are posted to credit and negative amounts to debit).
A cumulation wage type is posted, in addition, an individual wage type which is included in this cumulation wage type is also posted.
Unusual secondary wage types occur which are not coded at all or coded incorrectly with respect to posting (for example, wage tye /565 'Carry over for next month')
Examples for case B
Correctly, a wage type which is an imputed income is not posted, however it is incorrectly included in the total gross amount.
A wage element is incorrectly not included in the total gross amount, however, it is set up correctly as an 'expense' with regard to posting.
A wage type is included in the total gross amount, it is coded correctly as an expense and is not stored in the payroll results.
A deduction wage type is created correctly but not deducted from the net amount.
Example for case C
(Currently, no examples are known)
Solution
Case A
In most cases you can correct the error by correcting the Customizing of the wage type; you should then be able to perform a posting run again without rejection. (If the employees evaluated correctly should also be evaluated again, you must delete any productive posting run that was possibly created with incorrect Customizing before the re-evaluation can be performed.)
Case B
You can correct the original settings in a test system and then go on with testing.
If you detect such an error before the end of the payroll, in general it is sufficient to correct the original incorrect settings and settle the affected employees again. SAP therefore usually recommends that you perform a test or simulation posting run before the end of the payroll.
If you only detect such an error after the payroll, then the correction of the problem becomes more complex; if the error is caused by SAP, refer to the component responsible for the error.If you caused the error through a mistake, contact your consultant.
Case C
If case C occurs, contact SAP so that the error is analyzed and corrected as soon as possible.In this case you should supply detailed information on the underlying payroll (the list of for- and in-periods in RPCLSTRx, the list of wage types from table RT), the underlying Customizing and the completely expanded log of report RPCIPE00.As a topic area you should select PY-<COUNTRY>, PA-XX or PY-XX-DT.
General tips and tricks
After an upgrade or after applying a Legal Change Package, compare changed schemas and calculation rules with the new schemas and calculation rules delivered by SAP and check whether changes to the SAP objects affect your payroll accounting.
SAP recommends that after an upgrade or after you apply a Legal Change Patch or major changes to Customizing, you simulate the last posting run again - it must have the same result as the last one.In addition, before the end of the payroll, you should execute a test or simulation run.
Often, the employee's balance provides information on the wage type which was not posted at all/posted incorrectly/posted in the incorrect way.
You should determine the way posting should look like as an example for one employee and then check whether this posting balances to zero and whether the corresponding wage types are printed with the correct amounts in the log of posting.
When you analyse the log, ensure that the payroll result is still fully evaluated and logged and the posting within the payroll result does not have a balance of zero; all further accounting results are then no longer evaluated.
When a retroactive change is performed on the posting characteristics of a wage type, the wage type is cancelled during retroactive accounting in the same way it was originally posted.

Material Valuation for Finished Product in Production Scenario

Dear SAP Gurus,
Kindly recommend appropriate Material Valuation Control for Finished Product in manufacturing scenario. SAP recommends pricing control 'S' (Standard), but my client's buying nature is not periodic(varies), they buy material on requirement basis (On actual material consumption ) which is very frequent. Pricing for each buy also changes due to the market conditions. You are requested to suggest me appropriate Material Valuation Control (either S / V) for Finished Product along with reasons, advantages & disadvantages for the same.
Thanks,
Shantanu

Hi Alll
Well one disavantage in material with 2/V for production consumption is in case of incorrect goods receipt, incorrect price for example, all your consumption will be wrong.
For correction you would have to reverse all production posting, correct the goods receipt and repost the production confirmation.
If you were using 3/S configuration, all consumption would be done in standard price and at month end material ledger would calculate the actual price for price revaluation. People from MM would have time to correct the entries during the month.
Regards.

My iTunes Store Isn't Showing Newest Items Posted

My iTunes store is not showing the latest products posted. My roommate went onto her iTunes and all the new stuff was showing on hers. Anyone know why my iTunes is not showing updated posts? I have the current version of iTunes. Any help would be great.

That's odd. Have you tried clicking on something on the iTunes Store, and then clicking on the home icon, to refresh the iTunes Store home page?

Macally drops support for Post-Op/iMedia FCP Keyboard on Intels

Though I doubt you can buy one anymore, and Post-Op the company I paid $180.00 to, no longer sells them, I thought I would post this info for those using it now, or finding an old one on e-bay.
PRODUCT: Post-Op EZ keyboard is just a repackaged Macally iMedia Key keyboard. You used the Macally iMedia software to program the custom button along the top, and you could program an eject button, which the new Mac Pros need, (though F12 would work for one optical bay). While the keys still work for input, without updated software you can't program the buttons now on Intel Tiger or Intel Leopard. I wrote them and this was the Christmas cheer message I received.
Dear Customer,
Thank you for contacting us.
I am sorry that we'll not have Intel Mac driver support for this keyboard.
For Eject, you may press and hold the F12 key for 1 second to open/close the CD tray.
If you have any question, please let me know. Wish you a Merry Christmas and Happy New Year,
Tom - Tech Support
Macally Peripherals
4601 E. Airport Dr.
Ontario, CA 91761 USA
Phone: 909-230-6778 EXT. 151
FAX: 909-230-6889
www.macally.com
Learned an expensive lesson on buying "custom" keyboards, think twice.

Error compiling form in 6i

Moving this thread from "PL/SQL" to "Forms"
purple
Posts: 3
Registered: 02/23/11
PL/SQL Version 8.0.6.0.0 (Production)
Posted: Feb 23, 2011 8:55 AM
oracle , builder , 6i , pl , sql , forms           Reply
I'm a total newbie here. We have someone using Oracle Form Builder [32-Bit]. Oracle 6i database. Her information is as follows:
Forms [32 Bit] Version 6.0.8.21.3 (Production)
Oracle Toolkit Version 6.0.8.21.0 (Production)
PL/SQL Version 8.0.6.0.0 (Production)
Oracle Procedure Builder V6.0.8.17.0 Build #863 - Production
PL/SQL Editor (c) WinMain Software (www.winmain.com), v1.0 (Production)
Oracle Query Builder 6.0.7.1.0 - Production
Oracle Virtual Graphics System Version 6.0.5.38.0 (Production)
Oracle Tools GUI Utilities Version 6.0.8.20.1 (Production)
Oracle Multimedia Version 6.0.8.20.0 (Production)
Oracle Tools Integration Version 6.0.8.18.0 (Production)
Oracle Tools Common Area Version 6.0.8.18.0
Oracle CORE Version 4.0.6.0.0 - Production
She's having trouble compiling a form. In comparing her PC with another (working) PC, the only difference is in the third line.
Her's is: PL/SQL Version 8.0.6.0.0 (Production)
The working PC is: PL/SQL Version 8.0.6.3.0 (Production)
How do I "upgrade" this?
BluShadow
Posts: 16,328
Registered: 09/21/05
Re: PL/SQL Version 8.0.6.0.0 (Production)
Posted: Feb 23, 2011 9:08 AM in response to: purple Helpful
Reply
Well, that database is very much out of date, and I don't even think you'd be able to easily get the patches from Oracle any more as they haven't supported that version for many years now. If you have a support contract with Oracle you could try asking for the relevant patch.
Other than that, you're looking at upgrading the database to something more recent and supported.
purple
Posts: 3
Registered: 02/23/11
Re: PL/SQL Version 8.0.6.0.0 (Production)
Posted: Feb 23, 2011 9:29 AM    in response to: BluShadow           Reply
Thank you for the quick response. Yes, it's true it is an old database, but that's what we're using here. I used Patch12 which I thought was the most recent patch.
SomeoneElse
Posts: 11,472
Registered: 10/15/98
Re: PL/SQL Version 8.0.6.0.0 (Production)
Posted: Feb 23, 2011 9:57 AM in response to: purple Helpful
Reply
She's having trouble compiling a form.
Aside from the ancient software you have, you never told us what the trouble is.
An error message? A syntax error? Something else?
purple
Posts: 3
Registered: 02/23/11
Re: PL/SQL Version 8.0.6.0.0 (Production)
Posted: Feb 23, 2011 10:45 AM    in response to: SomeoneElse           Reply
She's tried several different scenarios and still is not able to compile a "XXFPQLTR" form.
It still appears to be something with the xxfps_price_pkg package in the get_rates procedure. If she comments out the line below it won't blow her out of forms.
If it's in there, it tells her it's encountered an error, and closes forms with a non-descript error message.
She attempted to hit 'debug' instead of 'close' when she got the forms error, and it did not provide herwith any further information .... it just blew up.
Forms is only blowing up when she tries to compile a form that accesses pl/sql tables . If we take out the procedure that has the pl/sql she can compile the form.
Billy Verreynne
Posts: 12,472
Registered: 05/27/99
Re: PL/SQL Version 8.0.6.0.0 (Production)
Posted: Feb 23, 2011 9:47 PM in response to: purple Reply
Forms is not PL/SQL and PL/SQL is not forms. Yes, somewhat common language. No, very different as one runs on the client (Forms) and the other runs on the server (PL/SQL).
And this is a PL/SQL forums - not Forms. So answers will tend to be about PL/SQL and not Forms. Make sure you do not mistake these as answers for Forms.
In your sho3s.. I would dump Forms in favour of using Oracle 11gr2 with Apex.

I've applied Patch12 to no avail
So, what is your PL/SQL Version now that you've applied Patch 12?
Patch12 is not the latest patch but but Patch17 is
True, but you always want your development environments to match your production environment. If Prod is currently at Patch 12, then Patch 12 should be installed on ALL developer workstations.
It is entirely possible that the problem is truly isolated to this one workstation. Have you tried performing a complete Unistall/Install of the Developer Suite (DS) 6i? With version 6i, I also found running Microsoft's RegClean tool often cleared up issues with the DS 6i. Microsoft no longer supports RegClean, but you can find it on the internet.
you can put the code in a database procedure instead of a Forms procedureIf things still don't work after all this, I agree with InoL, perhaps the best option would be to move your logic to a database procedure and call the DB procedure from your Form.
Out of curiosity, what is your Workstation operating system?
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.
Edited by: CraigB on Feb 24, 2011 11:01 AM

Round off problem in unit of measurement

Dear Experts
We are in SAP 4.7 , we are having more than 12 plants using same client.
One of our plant requirement we were changed the UOM 'Nos' with 3 decimels allowed.So where ever we not useing decimel places we have to use UOM as 'EA' (each).This is dont have any decimel places.
Now we are in implementation project for our one more new plant in same client. But for them we are going to introduced Batch specific unit of measurement. Base unit of measurement is KG and Batch specific UOM is EA.
All sale material have both unit of measurement , inward or production posting in KG and we will create batch number. We will enter the coversion value of how many quantity per kg for each batch.This will be in 'EA'
While i'm doing transfer posting or consumption or sales for the material in UOM 'EA' , it is coming with 3 decimel places.
If the same UOM 'EA' in normal condition (without batch specific UOM) it is working correctly.It is getting roundoff correctly.
Please help me out on this.I need the consumption should not be decimel places for UOM 'EA'.
Suresh

Hi Senthilkumar SD,
You have not read the thread before posting.
It quite clearly states that the UOM EA already has NO DECIMAL PLACES.
Quote "<b>we have to use UOM as 'EA' (each).This is dont have any decimel places."</b>
It is good to see lots of people trying to help and so I am pleased to see you trying, but it really doesn't help if you haven't read the question before posting the answer.
Steve B

HP Color Laserjet 3600n printer displays Install Supplies when supplies are installed

Printer displayed message that supplies were out for all toners except magenta.
We put new black, cyan and yellow toners in the printer but it still displays INSTALL SUPPLIES with questions marks for those three toners on the display screen.
We set the printer to DISABLE CARTRIDGE CHECK mode and requested it print an event log, so the data light turned on steady without blinking and the display says it's printing the event log, but nothing happens for hours.
Took out the three toners (black, cyan and yellow) and kept the printer in DISABLE CARTRIDGE CHECK mode, then was able to print anything requested but prints only have magenta toner on them.
Put a black in the magenta toner slot, still in DISABLE CARTRIDGE CHECK mode, and print only in black where the magenta should be.
Cartridge locks are in good condition. Have cleaned all contacts in the toner slots.
Have checked all connections from DC controller and re-seated the formatter and all appear to be secure and sound.
Any advice as to whether this could be the formatter, DC controller, or something I've not guessed?

Hope you a having a great day,
I am reaching out to probe if you still experience this issue and to make a suggestion. If you are, Perhaps since this is a commercial product, posting in the forum for HP Business Support will provide a better chance at finding a prompt solution.
You may find the commercial Laserjet board here.
http://h30499.www3.hp.com/t5/Printers-LaserJet/bd-p/bsc-413
If you are not experiencing this issue any longer you may disregard this post, although I will appreciate if you can take I little bit of your time and let me know.
Best of luck;
RobertoR
You can say THANKS by clicking the KUDOS STAR. If my suggestion resolves your issue Mark as a "SOLUTION" this way others can benefit Thanks in Advance!

Time machine sick to death of it!

I am absolutely sick and tired of trying to create a back up. I have been endevouring to do this all year.. and still I am no further forward. I have a Mybooklive attached to my Netgear. I have wiped it clean and started again. .. and STILL I dont seem to have a successful back up on there. It is driving me to distraction. I get the following errors...
this back up started on March 9 - it seems to stop and restart each time the amount to be backed up reduces... until it gets to say 2gb..
Copied 398.9 MB of 51.7 GB, 818 of 188991 items
Copied 664.8 MB of 51.7 GB, 1652 of 188991 items
Copied 919.4 MB of 51.7 GB, 2741 of 188991 items
Copied 1.2 GB of 51.7 GB, 2797 of 188991 items
Copied 1.6 GB of 51.7 GB, 2831 of 188991 items
Copied 2.1 GB of 51.7 GB, 2922 of 188991 items
Copied 2.5 GB of 51.7 GB, 3023 of 188991 items
Copied 2.9 GB of 51.7 GB, 3149 of 188991 items
Copied 3.0 GB of 51.7 GB, 3154 of 188991 items
Copied 3.5 GB of 51.7 GB, 3252 of 188991 items
Copied 3.9 GB of 51.7 GB, 3343 of 188991 items
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Error: (-36) SrcErr:NO Copying /Users/alex/Laura's Backup/College A2 WORK/Media/Production/Poster 3 to /Volumes/Time Machine Backups/Backups.backupdb/Alex/2012-02-28-193411.inProgress/9378BF43-2E24-442E-A 311-0AF326DC41BA/Macintosh HD/Users/alex/Laura's Backup/College A2 WORK/Media/Production
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Error: (-36) SrcErr:NO Copying /Users/alex/Laura's Backup/College A2 WORK/Media/Production/Soundtrack CD Cover to /Volumes/Time Machine Backups/Backups.backupdb/Alex/2012-02-28-193411.inProgress/9378BF43-2E24-442E-A 311-0AF326DC41BA/Macintosh HD/Users/alex/Laura's Backup/College A2 WORK/Media/Production
Stopping backup.
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Error: (-8062) SrcErr:NO Copying /Users/alex/Laura's Backup/College A2 WORK/Media/Production/Soundtrack CD Cover/back.psd to (null)
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Copied 3364 files (4.4 GB) from volume Macintosh HD.
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Copy stage failed with error:11
Stopping backupd to allow ejection of backup destination disk!
then it started again...
Starting standard backup
Attempting to mount network destination using URL: afp://;AUTH=No%20User%[email protected]/TimeMachine
Mounted network destination using URL: afp://;AUTH=No%20User%[email protected]/TimeMachine
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/TimeMachine/Alex.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Detected system migration from: /Volumes/Macintosh HD 1
No pre-backup thinning needed: 56.66 GB requested (including padding), 462.55 GB available
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Copied 832.8 MB of 47.2 GB, 384 of 188991 items
Copied 1.5 GB of 47.2 GB, 384 of 188991 items
Copied 2.7 GB of 47.2 GB, 384 of 188991 items
Copied 4.3 GB of 47.2 GB, 384 of 188991 items
Copied 5.0 GB of 47.2 GB, 384 of 188991 items
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Error: (-36) SrcErr:NO Copying /Users/alex/Laura's Backup/iPhoto Library Croyde/Modified/2011/Steph Hannay Shoot/IMG_0426.JPG to /Volumes/Time Machine Backups/Backups.backupdb/Alex/2012-02-28-193411.inProgress/36DEB5FD-4562-47BA-9 FF1-45EA1EAF0095/Macintosh HD/Users/alex/Laura's Backup/iPhoto Library Croyde/Modified/2011/Steph Hannay Shoot
Stopping backup.
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Error: (-8062) SrcErr:NO Copying /Users/alex/Laura's Backup/iPhoto Library Croyde/Modified/2011/Steph Hannay Shoot/IMG_0426.JPG to /Volumes/Time Machine Backups/Backups.backupdb/Alex/2012-02-28-193411.inProgress/36DEB5FD-4562-47BA-9 FF1-45EA1EAF0095/Macintosh HD/Users/alex/Laura's Backup/iPhoto Library Croyde/Modified/2011/Steph Hannay Shoot
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Stopping backupd to allow ejection of backup destination disk!
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Copied 384 files (5.0 GB) from volume Macintosh HD.
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Copy stage failed with error:11
then this one... different files it didn't like
starting standard backup
Attempting to mount network destination using URL: afp://;AUTH=No%20User%[email protected]/TimeMachine
Mounted network destination using URL: afp://;AUTH=No%20User%[email protected]/TimeMachine
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/TimeMachine/Alex.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Detected system migration from: /Volumes/Macintosh HD 1
No pre-backup thinning needed: 48.25 GB requested (including padding), 455.44 GB available
Waiting for index to be ready (101)
Copied 1.8 GB of 40.2 GB, 26 of 188991 items
Copied 2.9 GB of 40.2 GB, 26 of 188991 items
Copied 4.9 GB of 40.2 GB, 26 of 188991 items
Copied 6.9 GB of 40.2 GB, 26 of 188991 items
Copied 8.4 GB of 40.2 GB, 26 of 188991 items
Copied 10.8 GB of 40.2 GB, 26 of 188991 items
Copied 13.2 GB of 40.2 GB, 26 of 188991 items
Copied 16.1 GB of 40.2 GB, 26 of 188991 items
Copied 17.6 GB of 40.2 GB, 26 of 188991 items
Copied 18.6 GB of 40.2 GB, 26 of 188991 items
Copied 19.6 GB of 40.2 GB, 26 of 188991 items
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Error: (-36) SrcErr:NO Copying /Users/alex/Laura's Backup/iPhoto Library Croyde/Originals/2011/Germany!/IMG_1773.JPG to /Volumes/Time Machine Backups/Backups.backupdb/Alex/2012-02-28-193411.inProgress/DC60CF4F-8C13-4B6B-9 205-D73D777F8E57/Macintosh HD/Users/alex/Laura's Backup/iPhoto Library Croyde/Originals/2011/Germany!
Stopping backup.
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Error: (-8062) SrcErr:NO Copying /Users/alex/Laura's Backup/iPhoto Library Croyde/Originals/2011/Germany!/IMG_1773.JPG to /Volumes/Time Machine Backups/Backups.backupdb/Alex/2012-02-28-193411.inProgress/DC60CF4F-8C13-4B6B-9 205-D73D777F8E57/Macintosh HD/Users/alex/Laura's Backup/iPhoto Library Croyde/Originals/2011/Germany!
Stopping backupd to allow ejection of backup destination disk!
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Copied 26 files (19.6 GB) from volume Macintosh HD.
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Copy stage failed with error:11
& so it goes on and on all week failing with an error 11.
until tonight...
Starting standard backup
Attempting to mount network destination using URL: afp://;AUTH=No%20User%[email protected]/TimeMachine
Mounted network destination using URL: afp://;AUTH=No%20User%[email protected]/TimeMachine
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/TimeMachine/Alex.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Detected system migration from: /Volumes/Macintosh HD 1
No pre-backup thinning needed: 3.63 GB requested (including padding), 412.67 GB available
Copied 1.2 GB of 2.1 GB, 29 of 188991 items
Copied 3.6 GB of 3.6 GB, 29 of 188991 items
Copied 4.2 GB of 4.2 GB, 29 of 188991 items
Stopping backupd to allow ejection of backup destination disk!
Stopping backup.
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Error: (-34) SrcErr:NO Copying /Users/alex/Laura's Backup/Iphoto2/iPhoto2/iPhoto Library Alex/Modified/2011/Cornwall, Easter/IMG_2657.JPG to /Volumes/Time Machine Backups/Backups.backupdb/Alex/2012-02-28-193411.inProgress/7A89729E-7A3B-4E28-B EA8-1FF28BEC62B7/Macintosh HD/Users/alex/Laura's Backup/Iphoto2/iPhoto2/iPhoto Library Alex/Modified/2011/Cornwall, Easter
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Copied 29 files (4.2 GB) from volume Macintosh HD.
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Device not configured
Copy stage failed with error:28
I tried at one stage to go in and edit as per another post on here using terminal.. got stuck at a particular stage and gave up as noone responded how to help.
I just want a back up. Western Digital have offered to replace my hard drive - but it will be a reconditioned one and not a new one..
I just hate it.

That's a different problem. It's getting a negative value for the estimate of what's changed and needs to be backed-up!
Start by Verifying your internal HD to be sure it's not a directory problem. See #6 inUsing Disk Utility if you're not sure how to do that.
Then check your exclusions in Time Machine Prefs > Options. Make sure there isn't any overlap (such as excluding both a folder and a file or sub-folder inside it, separately).
Then do a "full reset" of Time Machine, per #A4 in Time Machine - Troubleshooting, to be sure the file where the exclusions are kept isn't corrupted.
If none of that helps, your installation of OSX may be damaged. Try installing the "combo" update, per Installing the ''combo'' update and/or Reinstalling OSX.
If still no help, install a fresh copy of OSX (that won't disturb anything else), per the same article.
Thanks Pondini -verifying Tick. Nothing in exclusions -tick. Full reset tick. Haven't installed Lion as it really isn't happy with a Western Digital so I've been told so kept to snow leopard for now. This is what is going on now....
Starting standard backup
Attempting to mount network destination using URL: afp://;AUTH=No%20User%[email protected]/TimeMachine
Mounted network destination using URL: afp://;AUTH=No%20User%[email protected]/TimeMachine
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/TimeMachine/Alex.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Detected system migration from: /Volumes/Macintosh HD 1
Warning: Bytes to copy estimate was negative (-33828)
No pre-backup thinning needed: 100.0 MB requested (including padding), 373.56 GB available
Waiting for index to be ready (100)
Copied 3.8 GB of 3.8 GB, 8061 of 188991 items
Copied 6.2 GB of 6.2 GB, 8066 of 188991 items
Copied 6.9 GB of 6.9 GB, 8069 of 188991 items
Copied 8.2 GB of 8.2 GB, 9436 of 188991 items
Copied 9.1 GB of 9.1 GB, 11524 of 188991 items
Copied 11.2 GB of 11.2 GB, 12449 of 188991 items
Copied 12.3 GB of 12.3 GB, 37345 of 188991 items
Copied 13.6 GB of 13.6 GB, 38934 of 188991 items
still got a negative. ARHHHH!

Lightroom 3 - The worst program Adobe has ever put out...

If anyone cares to read this, I will be the first to say DO NOT UPGRADE!!
I am spreading the word - facebook, word of mouth, every professional photographer in LA I know, blogs, etc.
You gotta raise hell to get changes.
Lets see if Adobe will do anything about these issues...
I thought that Adobe created "beta" for a reason - to smooth out all the kinks before they put the disk out. Nope.
I have been waiting for them to put out updates on many issues since I purchased the disk a month ago.... Still waiting Adobe!!!
It is excruciating to watch my photos take literally 4-5 minutes to open. Even worse, is the time it takes to save from Photoshop CS5 back to Lightroom - I timed 14min. FOR A PHOTO!
I feel like the old days when I rendered video - went out to get a coffee, and came back to find the spinning of wheel of death still spinning.
Oh, and I got to talk to India today too! for 3.5 hours - with no resolution to my problems.
Susheel accessed my computer remotely - saw my catalog - sees 73,000 images, and asks "are you a photographer?" REALLY?! DId you REALLY just ask me that Susheel??
Why I HATE Lightroom 3 - let me count the ways:
1. Adobe closed their tech support in Portland (whom I have spoken to many times, and ALWAYS got my problems resolved. They always went above & beyond the protocol - and we sit here and wonder why the US economy is crashing), now you get a no-name person in India or in the philippines (who have no extension, no email, not even a direct line so when you sit on a call for 3.5 hours and need to call back you are starting all over again.. Dear Adobe - do we live in 1980?? You are suppose to be a LEADER in technology.
I am morally against outsourcing, my artwork is all about the death of american industrial capitalism. In a time when the US is in crisis, Adobe works on moving things out of the US. I'm outraged - You can't get someone in the US EVEN IF YOU TRIED! The best I could do was talk to someone in sales about this - wow. What does that say - American's "look good and sound good to sell our product, but when it comes to something advanced in technology like using the product and trouble shooting, we prefer to use someone with no extension in another country"
2. They don't offer support for anyone who is running off a network (they expect professionals to be working off their local "c" drive or Mac internal hard drive. HA!!
3. They continued to blame my network - even though my network is running smoothly, has no limitations on access, will open directly into photoshop just fine (and quick!), worked absolutely perfectly in Lightroom 2.... Yeah, it's the network, riiight.
4. Lightroom 3 is corrupting files when opening into Photoshop CS5 - if I'm lucky enough to open them
5. When I do get a photograph open, it loses it's filters once saved back into Lightroom (I rate my photos to help me navigate through the masses) - this really is hurting my workflow. When I shoot 800 images in the studio in one day - I DO NOT want to go back and fish around to find the edited version that lost its flag...
6. I have been promised to get a phone call "sometime next week" since there is no extension I can call back on to move forward. I'll keep you updated - let you know if Susheel keeps his word. He couldn't tell me who was going to call me, or when, but he "assures" me it will happen.
I wont hold my breath

function(){return A.apply(null,[this].concat($A(arguments)))}
Keith_Reeder wrote:
ambienttroutmask wrote:
So the worst programme Adobe ever put out, yet even though you can have a 30 day trial you still went out and brought it...
Yep, everything is always someone else's fault. It's never because they've made a stupid decision to buy before making absolutely sure that the software will work for them.
Seems like nobody is prepared to take responsibility for their own actions these days.
So, by that logic Adobe does not have to take ANY responsibility for pushing this kludge out the door? Given they had a RC ready almost INSTANTLY after release should be sufficient to show they KNEW they were pushing garbage out the door. Adobe is indeed responsible for their offering a know buggy product, bugs which CROSS PLATFORMS so it has to be the core code design not the user hardware or anything a given user has done. Sure some systems might have setups which help make these issues more apparent, but that is on Adobe to deal with as they should publish limitations and known configurations which can potentially induce greater problems...but these entail an admission and accepting responsibility for the original buggy release...btw, release notes used to be where one would find quirks info and how to work around them post system requirements being carved in stone and set to entice the lowest common denomonator user.
One more thing...LR is marketed not as a PRO TOOL, it is sold as a tool for the average to hobby level photographer. That is also has huge appeal to the pro market is a happy accidentally-on-purpose thing...but to berate people who don't feel it's their job to troubleshoot a commercial app is completely unreasonable...but anymore the US consumer is the largest beta tester group on the planet...I wonder how our EU counterparts are fairing as ironically, they have stronger consumer protection laws...try pushing a crap product out in the German market...heh-heh, yeah good luck with that.
Actually I would say this is not the worst software Adobe has ever pushed out the door but perhaps the worst photography software they ever sent as RTM. Many, many PDF related apps and utils have actually been worse and we won't get into what they have done to Flash and Dreamweaver after that acquisition. The closest analog I can see if that of what happened to Norton products post Norton being purchased by Symmantec.
However, I am willing to give Adobe time to address this because they did have the RC ready almost right away. Should they have done this? No way, but perhaps the marketing wonks put the company in the position where it had to meet the release date even if issues were discovered and fixes in the pipeline already and it was gonna be a 3-9 week delay before the issues were mostly fixed. But they did and well, even those who ran the beta, ran the 30-day trial did not find the issues because they simply did not use that part of the program enough for the bugs to manifest their effects to the degree when you the user, realize something odd is happening.
I too am pissed, beyond belief as I depend on LR for my business, I can, however work around it for a while but I don't make money as a photographer I use photography for my business so the issues, while causing huge levels of frustration, are not fatal....yet...all I know is I don't want to revert to LR2.7 because I have done so much work onLR3/ LR3.2RC already and the tools themselves are indeed superior in LR3.x....when they work and that is the rub. So many here are telling those with these bugs affecting their income/workflow bought into this to save time and leverage the bestter NR/sharpening and I say much improved adjustment tools. I don't use the lense profiles at all really so nothing special for me there.
I would ask a question...I am sure this has been asked and answered but, eh, why not one more time because search is sooooo "haaaard"
but does this issue affect all file types? I am shooting DNG but can switch to PEF if needed and convert on import but would rather just shoot DNG. I am not willing to switch to JPG because if I have to do this I give up too much control on my images, for that I would switch back to LR2.7.
Also, what versions of Camera RAW were used in the beta and what versions are being used with LR3. I know I did upgrade to ACR6.2(?) or whatever the most current version. I understand there are a ton of factors at play in these bugs but I do doubt it's ACR as my old antique PS CS3 version of Photoshop does not have any problems, of course it's using the old version of ACR 4.6(?) again sorry I forget what version exactly but it's trivial and can be determined.
I like LR because I don't need the advanced features of PS all that often, still PS is a fun tool to have as a backup for the complicated shots though I don't have time to really spend in it as I would like to...
But in general I guess I am trying to say, Adobe had to know in advance of the RTM original LR3 because they had the RC ready almost instantly. Of course past releases of LR also had the same experience just the bugs were, well, not as impactful I suppose. I have been happy with LR since 1.x versions but this version is painful to support...and I as I previously posted I won't screw with Adobe's refund people, likely off-shored staff who get bonuses for talking customers OUT of getting a refund, I will simply file a chargeback with Mastercard...that is why I use it, so I don't have to let companies waste my time wading through their red-tape. And btw, Adobe knows the customer will WIN any chargeback because this evidence of a known to be defective product was sold to the consumer and the customer even allowed the mfg to remediate the issue only they failed to deliver in a timely fashion. So, if one is not happy just "go to the mattresses"...use the chargeback hammer. The bonus is every chargeback granted to the consumer costs the retailer, Adobe in my case, $35 when they lose...

Production posting

Similar Messages

Maybe you are looking for