Old PR release strategy - release completed status change

Dear Gurus,
We have impletemented Item level release strategy for PR.
There was old strategy exisitng only one level release, then we have implemented new release strategy which is multiple level release.
Now the question, there are some PR are released completed for old strategy,. if we change the old PR with old strategy - which was release completed, the system triggeres new release strategy, which over writes the old strategy even though it was release completed status.
Please advice
Regards
RS

Hi,
Check with T.Code OMGS (Define Release Strategy for Purchasing documents) , then go to release indicator --> then
Check the value of Changeability of purchasing document during/after release  ( 1 - 6).
Choose the appropriate value based on your req.
Regards,
Udayasankar Rajagopalan
Edited by: Udayasankar.rajagopalan on Dec 9, 2009 1:07 PM

Similar Messages

  • PR number is same , release date getting change

    Hi experts
    Here my query is , Auto generated PR's are there (20 PR's ). For autogenerated PR's there is no release strategy appilicable.
    In above case, For 20 dyas once PR's Release date getting changed.
    How come for same PR's numbers , only the release date is getting changing ....
    Can anybody giv some inputs to trouble shoot.
    Thanks
    Sap-MM

    Hi,
    The Release date in PR has nothing to do with release strategy of PR.
    It is :
    Specifies the date on which the purchase order should be initiated on the basis of the purchase requisition.
    The release date is based on:
    The purchasing department processing time defined for the plant
    The planned delivery time from the material master record or purchasing info record
    The delivery date
    The goods receipt processing time from the material master record
    Open any PR (ME53N)          goto Qantities/Dates tab           Click on Release date              Press F1 key    you will get the complete information.
    Cheers,
    Satish

  • How to release user status for sales documents automatically

    Hi All,
    We have configured status profile for third party sales document type. This will stop creating PR from sales order. After chaning the status from STP to GO, system will create PR. But the problem here is user is going and changing the object status manully.
    The business wants to release at a time many records automatically. Do we have any transaction code which we can use for changing the user status automatically for many orders?
    We have tried V.26, but this is just report we can not change the status automatically,
    Thanks in advance!
    Regards
    Lakshmikanth

    Hi,
    No standard program exists for it, as statuses are always customized.
    create a BDC program for status change and run in backgram as batch job.

  • Re_detemination of release staretgy after changes to cost center

    We have a problem in redetermining release stratergy
    AA -> released
    AB -> released
    AC -> not released
    AD -> not released
    When we change a item cost center, there release stratergy is not redetermined (cancelling all previous releases ).
    When there is a value (price)change, the release stratergy is  redetermined, but not for cost center.
    Both CC and total value are mainatained in class char.
    Any suggestions.
    Thanks.
    Edited by: MIKE JO on Sep 1, 2010 5:20 PM

    Hi,
    The release strategy does not get reset because there is no change in any of the values in CEKKO straucture. Please note that while creating po release strategy in all the char CEKKO structure will be reffered. For change in cost center u will hav to use user exit.
    Regards
    Naveen

  • Quotation in Release Rejected Status, how does the purchaser can review it?

    Hi Gurus,
    Once the approval rejected the quotation. Now the status become release rejected. When purchaser try to open the quotation it show an error message "you cannot open rfx response 9000000001 with release rejected status". The approval is assign with SAP_ALL and SAP_NEW. Beside, i not able to find this error msg in SE91.
    Regards,
    Wind

    Hello Wind,
    As per the standard functionality delivered with SRM 701, purchaser user should be allowed to view the details for the Rejected RFx response  and he also he will be provided with the Undo Reject option to re-submit the response for approval to the purchasing manager.
    Also you have mentioned about the roles assigned to your user id , i could see that you have given both SRM 70 and SRM 701 roles at the same point of time.
    Kindly assign the SRM  701 roles only , else the system will not behave properly.
    Try with the below roles in ABAP system with the proper authorization.
    /SAPSRM/OP_PURCHASER_EHP1
    /SAPSRM/ST_PURCHASER_EHP1
    /SAP_CFX_USER
    ZSRM_TEAM
    In portal kindly give the corresponding Strategic purchaser Ehp1 role.
    After making these changes kindly check the scenario once again, it should work fine.
    Best Regards,
    Rahul

  • Status change from 'Completed' to 'In Process' not allowed

    When configuring Appraisals in R/3 we want to change the  Status of 'Completed' when pressing the 'Reject' button so that it moves to the Target Status of 'In Process'
    However, we are getting an error message:
    Status change from 'Completed' to 'In Process' not allowed
    The SAP help states the following:
    In Process (only if final appraisal or part appraisal is defined)
    This has been defined at Template Level.
    So I don't understand why we are getting the message.
    Does any one else know of a way to configure the Appraisal template so that after it has been 'Rejected' it moves back into 'In Process'
    Thanks
    MN
    Points Rewards!

    Hello Andreas,
    Ah, sorry, there was so much talk about user decisions that I assumed you were using a standard decision task.
    Still, I would be extra careful of changing the way workflow usually works because you have an unknown target audience that are based on the standard.
    The standard SAP philosophy is quite simple: cancel/F3 or do nothing and it stays reserved. If you do not want it reserved, you need to perform an action. This is based on a majority of processes: in most cases when you execute a work item you will also be the one who is going to completed it. Replacing it is the lesser used of the two alternatives, therefore it is the only one that requires an action on the part of the user.
    Again, this is intended as constructive input. Strange quirks and unusual behaviour tend to add a black mark to software if they do not make things easier to use. In many environments users are not even aware of the reserve/replace business, so there you would be adding an additional layer of complexity.
    Personally I would find an exit popup annoying as a regular workflow user - regular decisions can be approved with one click, or I can back out with a single click if I need to make a phone call or look up some info before approving - but with this new-fangled thing I've got an extra button to click and an extra thing to think about. This is especially the case in a payment approval scenario where you may have users in some departments who may approve hundreds of payments each week.
    My suggestion would be to leave it like that. By all means put an option into the user decision to put it back or to 'un-reserve' it (and loop round if the user chooses it). That way you are adding value and not clicks.
    Cheers,
    Mike

  • Process completed successfully but status changes  to red

    hi in my process chain all the processes of the master data load local chain completed succesfully but the status changes to red and the chain is not processding further.  wh t may be the reason for this.
    do any one have idea about this

    Hi,
    RED means the whole status of the chain or any particualr step in the process chain..?
    If the total status is RED even all the steps finished successfully once come out of the session and again refresh and chk status...
    Now if any step in the chain fails the total chain status remains RED only...
    If u still needs to process further then u can use FM: RSPC_PROCESS_FINISH in SE37
    U hav to copy the detals from the table RSPCPROCESSLOG.........
    Check this blog:
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    rgds,

  • Sales order as complete and change the delivery status.

    Hello All,
    We  produces an order but then the customer calls and does not want the material so we in turn will scrap the material against the production order using transaction MB1A mvmt type 951 E. 
    Since the material were scrapped and no material were shipped against the sales order, the sales order u201Coverall statusu201D remains open and the delivery status is u201Cnot deliveredu201D.
    To close the order  we u201CRejected line itemu201D and moved on.
    I would like to know if there is another way we can set the sales order as complete and change the delivery status. 
    Regards
    Amit

    Hello,
    you can use the status profile for the same. but a better way would still be to use the rejection reasons . the rejectionr reasons are very well integrated with the document flow as well as transfer of requreiemnts to Production
    so a best practise would be to use rejection reason
    hope this helps
    Thanks
    akasha

  • Batch status change with UD

    Hi Everybody,
    I have a question about batch status change while taking UD. I understand that stock posting and batch status for each UD code is decided by the value in 'Posting proposal UD' field in Selected Set settings. I understand that I can customize the movement types for the values (eg VMENGE01, VMENGE02 etc) in config. But that is only for stock posting. From what setting is the Batch status decided eg. If we approve, the batch is unrestricted and if we reject it is restricted.
    Can I customize those values which are available in the drop down in the 'Posting proposal UD' ? Can I create a value of my own ?
    Regards,
    Manish Saraswat

    Manish,
    execute tcode QS51
    you will be able to see 'Posting Proposal UD' in "Selected Set ". Now select that line (Posting Proposal UD line). Status for Posting Proposal UD should be "Released"
    After selecting that line on left hand side there is " Dialog Structure " in that there is " Selected Set Code " Click on that.
    Complete list of code will come you can add and modify those codes.
    Hope now its clear to you.
    Edited by: tejasg on Mar 24, 2010 4:21 PM

  • User Status change problem in Process Order

    Hi,
    We are in process of upgrading our system from 4.6C to ECC 6.0. I have a problem with User status change for process Orders.
    In 4.6C we are using the profile x with settings:
    10     ZNEW     Created process order     10     90     1     1     ZSTA
    20     ZLCK     Locked process order     20     90     1     1     ZREV
    30     ZOPN     Reopened process order     20     90     1     1     ZOPN
    40     ZMST     MES order started     20     90     1     1     ZMST
    50     ZMCL     MES order closed     20     90     1     1     ZMCL
    90     ZTEC     Technically completed      20     90     1     1     ZTEC
    In ECC 6.0 we also use the same profile settings as above.
    The problem is in ECC 6.0 when I do a goods receipt the User status changes to ZTEC . The process followed is ..Create process order, Release Order, Goods issue, Phase partuial confirmations, Goods receipt and then Finla confirmations of phases. Now in 4.6C if i do the above process the User status remains at ZMST and it only changes to ZTEC when i technically complete the order but in ECC 6.0 when I do a goods recipt from above steps the User status changes to ZTEC. THis should not happen.
    Any pointers will be very helpful.

    Hi,
    The log for production order preliminiary costing is not saved. Therefore, once the order is saved, there is no log available anymore (this is by the way a question of PP; none of the logs is saved).
    Hope that helps...
    Regards,
    Declan

  • Restore completed  status 4014 iphone 5s

    i try to restore my iphone 5s form 3 PC and change 2 Cabels
    every time give me a 4014 and the finall time give me
    and this is  a log for it status:2005
    2014-04-14 06:40:05.147 [15724:4538]: restore library built Feb 12 2014 at 16:27:17
    2014-04-14 06:40:05.147 [15724:4538]: iTunes: iTunes 11.1.5.5
    2014-04-14 06:40:05.148 [15724:4538]: iTunes: Software payload version: 11D167
    2014-04-14 06:40:05.148 [15724:4538]: iTunes: Using MobileRestore state machine
    [04:40:49.0144] Changing state from 'Idle' to 'Restoring'
    [04:40:49.0147] AppleDevice::GetDeviceID: failed for iBoot
    [04:40:49.0148] AppleDevice::GetDeviceID: failed for iBoot
    [04:40:49.0151] requested restore behavior: Erase
    [04:40:49.0153] requested variant: Erase
    [04:40:49.0186] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [04:40:49.0680] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
    [04:40:49.0684] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreLogo" Digest = "<CFData 123A06E8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0686] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreDeviceTree" Digest = "<CFData 123A5D88 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0688] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 1239F068 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0692] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 123A3160 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0693] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 1239F410 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0695] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 1239FC80 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0697] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 123A18E8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0699] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
    [04:40:49.0701] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
    [04:40:49.0702] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
    [04:40:49.0704] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
    [04:40:49.0705] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
    [04:40:49.0706] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
    [04:40:49.0709] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow1" Digest = "<CFData 123A0418 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0712] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow0" Digest = "<CFData 123A60E8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0714] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 123A02B0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0715] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBoot" Digest = "<CFData 123A0B68 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0717] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "DeviceTree" Digest = "<CFData 123A06A0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0719] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "SEP" Digest = "<CFData 123A26F8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0721] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging1" Digest = "<CFData 1239F6E0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0723] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreSEP" Digest = "<CFData 123A4630 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0724] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "AppleLogo" Digest = "<CFData 123A4F30 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0726] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryPlugin" Digest = "<CFData 123A0B20 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0728] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryFull" Digest = "<CFData 123A35E0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0730] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging0" Digest = "<CFData 123A26B0 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0731] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RecoveryMode" Digest = "<CFData 123A2308 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [04:40:49.0733] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 11F7B4D8 [6F1B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
    [04:40:49.0735] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
    [04:40:49.0736] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per4976.tmp/amai/debug/ts s-request.plist
    [04:40:50.0792] amai: tss_submit_job: HttpQueryInfo returned 200
    [04:40:51.0005] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
    [04:40:51.0007] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per4976.tmp/amai/debug/ts s-response.plist
    [04:40:51.0541] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
    [04:40:51.0542] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "CFELoader"
    [04:40:51.0544] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "RBM"
    [04:40:51.0546] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PHLEET"
    [04:40:51.0547] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PERTOS"
    [04:40:51.0548] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PEHammer"
    [04:40:51.0919] <DFU Device 05FDA3F0>: production fused device
    [04:40:51.0920] requested restore behavior: Erase
    [04:40:51.0924] AppleDevice::GetDeviceID: failed for iBoot
    [04:40:51.0925] AppleDevice::GetDeviceID: failed for iBoot
    [04:40:51.0936] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#64c33543
    [04:40:51.0937] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#64c33543
    [04:40:51.0939] <DFU Device 05FDA3F0>: operation 0 progress 1
    [04:40:51.0940] <DFU Device 05FDA3F0>: operation 0 progress 2
    [04:40:51.0942] <DFU Device 05FDA3F0>: operation 0 progress 4
    [04:40:51.0944] <DFU Device 05FDA3F0>: operation 0 progress 5
    [04:40:51.0946] <DFU Device 05FDA3F0>: operation 0 progress 7
    [04:40:51.0948] <DFU Device 05FDA3F0>: operation 0 progress 8
    [04:40:51.0950] <DFU Device 05FDA3F0>: operation 0 progress 9
    [04:40:51.0952] <DFU Device 05FDA3F0>: operation 0 progress 11
    [04:40:51.0954] <DFU Device 05FDA3F0>: operation 0 progress 12
    [04:40:51.0956] <DFU Device 05FDA3F0>: operation 0 progress 14
    [04:40:51.0958] <DFU Device 05FDA3F0>: operation 0 progress 15
    [04:40:51.0960] <DFU Device 05FDA3F0>: operation 0 progress 17
    [04:40:51.0962] <DFU Device 05FDA3F0>: operation 0 progress 18
    [04:40:51.0964] <DFU Device 05FDA3F0>: operation 0 progress 19
    [04:40:51.0966] <DFU Device 05FDA3F0>: operation 0 progress 21
    [04:40:51.0968] <DFU Device 05FDA3F0>: operation 0 progress 22
    [04:40:51.0970] <DFU Device 05FDA3F0>: operation 0 progress 24
    [04:40:51.0972] <DFU Device 05FDA3F0>: operation 0 progress 25
    [04:40:51.0974] <DFU Device 05FDA3F0>: operation 0 progress 26
    [04:40:51.0976] <DFU Device 05FDA3F0>: operation 0 progress 28
    [04:40:51.0978] <DFU Device 05FDA3F0>: operation 0 progress 29
    [04:40:51.0980] <DFU Device 05FDA3F0>: operation 0 progress 31
    [04:40:51.0983] <DFU Device 05FDA3F0>: operation 0 progress 32
    [04:40:51.0986] <DFU Device 05FDA3F0>: operation 0 progress 34
    [04:40:51.0989] <DFU Device 05FDA3F0>: operation 0 progress 35
    [04:40:51.0991] <DFU Device 05FDA3F0>: operation 0 progress 36
    [04:40:51.0993] <DFU Device 05FDA3F0>: operation 0 progress 38
    [04:40:51.0995] <DFU Device 05FDA3F0>: operation 0 progress 39
    [04:40:51.0997] <DFU Device 05FDA3F0>: operation 0 progress 41
    [04:40:51.0999] <DFU Device 05FDA3F0>: operation 0 progress 42
    [04:40:52.0001] <DFU Device 05FDA3F0>: operation 0 progress 43
    [04:40:52.0003] <DFU Device 05FDA3F0>: operation 0 progress 45
    [04:40:52.0005] <DFU Device 05FDA3F0>: operation 0 progress 46
    [04:40:52.0007] <DFU Device 05FDA3F0>: operation 0 progress 48
    [04:40:52.0009] <DFU Device 05FDA3F0>: operation 0 progress 49
    [04:40:52.0011] <DFU Device 05FDA3F0>: operation 0 progress 51
    [04:40:52.0013] <DFU Device 05FDA3F0>: operation 0 progress 52
    [04:40:52.0015] <DFU Device 05FDA3F0>: operation 0 progress 53
    [04:40:52.0017] <DFU Device 05FDA3F0>: operation 0 progress 55
    [04:40:52.0019] <DFU Device 05FDA3F0>: operation 0 progress 56
    [04:40:52.0021] <DFU Device 05FDA3F0>: operation 0 progress 58
    [04:40:52.0023] <DFU Device 05FDA3F0>: operation 0 progress 59
    [04:40:52.0025] <DFU Device 05FDA3F0>: operation 0 progress 60
    [04:40:52.0027] <DFU Device 05FDA3F0>: operation 0 progress 62
    [04:40:52.0029] <DFU Device 05FDA3F0>: operation 0 progress 63
    [04:40:52.0031] <DFU Device 05FDA3F0>: operation 0 progress 65
    [04:40:52.0033] <DFU Device 05FDA3F0>: operation 0 progress 66
    [04:40:52.0035] <DFU Device 05FDA3F0>: operation 0 progress 68
    [04:40:52.0037] <DFU Device 05FDA3F0>: operation 0 progress 69
    [04:40:52.0039] <DFU Device 05FDA3F0>: operation 0 progress 70
    [04:40:52.0041] <DFU Device 05FDA3F0>: operation 0 progress 72
    [04:40:52.0043] <DFU Device 05FDA3F0>: operation 0 progress 73
    [04:40:52.0045] <DFU Device 05FDA3F0>: operation 0 progress 75
    [04:40:52.0047] <DFU Device 05FDA3F0>: operation 0 progress 76
    [04:40:52.0049] <DFU Device 05FDA3F0>: operation 0 progress 77
    [04:40:52.0051] <DFU Device 05FDA3F0>: operation 0 progress 79
    [04:40:52.0053] <DFU Device 05FDA3F0>: operation 0 progress 80
    [04:40:52.0055] <DFU Device 05FDA3F0>: operation 0 progress 82
    [04:40:52.0057] <DFU Device 05FDA3F0>: operation 0 progress 83
    [04:40:52.0059] <DFU Device 05FDA3F0>: operation 0 progress 85
    [04:40:52.0061] <DFU Device 05FDA3F0>: operation 0 progress 86
    [04:40:52.0063] <DFU Device 05FDA3F0>: operation 0 progress 87
    [04:40:52.0065] <DFU Device 05FDA3F0>: operation 0 progress 89
    [04:40:52.0067] <DFU Device 05FDA3F0>: operation 0 progress 90
    [04:40:52.0069] <DFU Device 05FDA3F0>: operation 0 progress 92
    [04:40:52.0071] <DFU Device 05FDA3F0>: operation 0 progress 93
    [04:40:52.0073] <DFU Device 05FDA3F0>: operation 0 progress 95
    [04:40:52.0075] <DFU Device 05FDA3F0>: operation 0 progress 96
    [04:40:52.0077] <DFU Device 05FDA3F0>: operation 0 progress 97
    [04:40:52.0079] <DFU Device 05FDA3F0>: operation 0 progress 99
    [04:40:52.0079] WinDFU::UploadData: EOF, cbRead: 1084
    [04:40:52.0081] <DFU Device 05FDA3F0>: operation 0 progress 100
    [04:40:52.0082] WinDFU::UploadData: ZLP
    [04:40:52.0082] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
    [04:40:52.0083] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
    [04:40:52.0084] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
    [04:40:52.0085] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
    [04:40:55.0081] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
    [04:40:55.0082] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
    [04:40:55.0082] WinDFU::ResetDevice: resetting...
    [04:40:55.0234] WinDFU::FinalizeDfuUpdate: success
    [04:40:55.0237] <DFU Device 05FDA3F0>: DFU succeeded
    [04:40:55.0239] Finished DFU Restore Phase: Successful
    [04:40:55.0279] DFU mode device disconnected
    [04:40:55.0281] Device removed when in state Restoring, moving device to transition state
    [04:40:55.0282] Changing state from 'Restoring' to 'Transitioning'
    [04:40:55.0283] Creating timer to monitor transition
    [04:41:25.0846] DFU mode device connected
    [04:41:25.0846] Transitioning device returned, continuing restore.
    [04:41:25.0847] Canceling timer
    [04:41:25.0848] Changing state from 'Transitioning' to 'Restoring'
    [04:41:25.0849] AppleDevice::GetDeviceID: failed for iBoot
    [04:41:25.0850] AppleDevice::GetDeviceID: failed for iBoot
    [04:41:25.0850] requested restore behavior: Erase
    [04:41:25.0851] requested variant: Erase
    [04:41:25.0860] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [04:41:26.0594] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
    [04:41:26.0595] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
    [04:41:26.0597] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
    [04:41:26.0598] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
    [04:41:26.0600] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
    [04:41:26.0601] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
    [04:41:26.0602] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBSS"
    [04:41:26.0604] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
    [04:41:26.0605] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
    [04:41:26.0607] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
    [04:41:26.0608] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
    [04:41:26.0609] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
    [04:41:26.0610] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
    [04:41:26.0612] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
    [04:41:26.0613] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
    [04:41:26.0613] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
    [04:41:26.0614] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "LLB"
    [04:41:26.0615] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
    [04:41:26.0616] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
    [04:41:26.0617] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "SEP"
    [04:41:26.0618] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
    [04:41:26.0619] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreSEP"
    [04:41:26.0619] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
    [04:41:26.0620] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
    [04:41:26.0621] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
    [04:41:26.0622] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
    [04:41:26.0623] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
    [04:41:26.0624] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
    [04:41:26.0625] <DFU Device 121B7E30>: production fused device
    [04:41:26.0625] requested restore behavior: Erase
    [04:41:26.0626] AppleDevice::GetDeviceID: failed for iBoot
    [04:41:26.0627] AppleDevice::GetDeviceID: failed for iBoot
    [04:41:26.0628] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ec6fe4df
    [04:41:26.0629] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ec6fe4df
    [04:41:26.0630] <DFU Device 121B7E30>: operation 0 progress 0
    [04:41:26.0631] <DFU Device 121B7E30>: operation 0 progress 1
    [04:41:26.0632] <DFU Device 121B7E30>: operation 0 progress 2
    [04:41:26.0633] <DFU Device 121B7E30>: operation 0 progress 3
    [04:41:26.0634] <DFU Device 121B7E30>: operation 0 progress 4
    [04:41:26.0635] <DFU Device 121B7E30>: operation 0 progress 5
    [04:41:26.0639] <DFU Device 121B7E30>: operation 0 progress 6
    [04:41:26.0643] <DFU Device 121B7E30>: operation 0 progress 7
    [04:41:26.0647] <DFU Device 121B7E30>: operation 0 progress 8
    [04:41:26.0653] <DFU Device 121B7E30>: operation 0 progress 9
    [04:41:26.0657] <DFU Device 121B7E30>: operation 0 progress 10
    [04:41:26.0661] <DFU Device 121B7E30>: operation 0 progress 11
    [04:41:26.0665] <DFU Device 121B7E30>: operation 0 progress 12
    [04:41:26.0669] <DFU Device 121B7E30>: operation 0 progress 13
    [04:41:26.0675] <DFU Device 121B7E30>: operation 0 progress 14
    [04:41:26.0679] <DFU Device 121B7E30>: operation 0 progress 15
    [04:41:26.0683] <DFU Device 121B7E30>: operation 0 progress 16
    [04:41:26.0687] <DFU Device 121B7E30>: operation 0 progress 17
    [04:41:26.0694] <DFU Device 121B7E30>: operation 0 progress 18
    [04:41:26.0698] <DFU Device 121B7E30>: operation 0 progress 19
    [04:41:26.0702] <DFU Device 121B7E30>: operation 0 progress 20
    [04:41:26.0706] <DFU Device 121B7E30>: operation 0 progress 21
    [04:41:26.0711] <DFU Device 121B7E30>: operation 0 progress 22
    [04:41:26.0717] <DFU Device 121B7E30>: operation 0 progress 23
    [04:41:26.0721] <DFU Device 121B7E30>: operation 0 progress 24
    [04:41:26.0725] <DFU Device 121B7E30>: operation 0 progress 25
    [04:41:26.0729] <DFU Device 121B7E30>: operation 0 progress 26
    [04:41:26.0735] <DFU Device 121B7E30>: operation 0 progress 27
    [04:41:26.0739] <DFU Device 121B7E30>: operation 0 progress 28
    [04:41:26.0743] <DFU Device 121B7E30>: operation 0 progress 29
    [04:41:26.0747] <DFU Device 121B7E30>: operation 0 progress 30
    [04:41:26.0751] <DFU Device 121B7E30>: operation 0 progress 31
    [04:41:26.0757] <DFU Device 121B7E30>: operation 0 progress 32
    [04:41:26.0761] <DFU Device 121B7E30>: operation 0 progress 33
    [04:41:26.0765] <DFU Device 121B7E30>: operation 0 progress 34
    [04:41:26.0769] <DFU Device 121B7E30>: operation 0 progress 35
    [04:41:26.0775] <DFU Device 121B7E30>: operation 0 progress 36
    [04:41:26.0779] <DFU Device 121B7E30>: operation 0 progress 37
    [04:41:26.0783] <DFU Device 121B7E30>: operation 0 progress 38
    [04:41:26.0787] <DFU Device 121B7E30>: operation 0 progress 39
    [04:41:26.0793] <DFU Device 121B7E30>: operation 0 progress 40
    [04:41:26.0797] <DFU Device 121B7E30>: operation 0 progress 41
    [04:41:26.0801] <DFU Device 121B7E30>: operation 0 progress 42
    [04:41:26.0805] <DFU Device 121B7E30>: operation 0 progress 43
    [04:41:26.0809] <DFU Device 121B7E30>: operation 0 progress 44
    [04:41:26.0815] <DFU Device 121B7E30>: operation 0 progress 45
    [04:41:26.0819] <DFU Device 121B7E30>: operation 0 progress 46
    [04:41:26.0823] <DFU Device 121B7E30>: operation 0 progress 47
    [04:41:26.0827] <DFU Device 121B7E30>: operation 0 progress 48
    [04:41:26.0833] <DFU Device 121B7E30>: operation 0 progress 49
    [04:41:26.0837] <DFU Device 121B7E30>: operation 0 progress 50
    [04:41:26.0841] <DFU Device 121B7E30>: operation 0 progress 51
    [04:41:26.0845] <DFU Device 121B7E30>: operation 0 progress 52
    [04:41:26.0849] <DFU Device 121B7E30>: operation 0 progress 53
    [04:41:26.0855] <DFU Device 121B7E30>: operation 0 progress 54
    [04:41:26.0859] <DFU Device 121B7E30>: operation 0 progress 55
    [04:41:26.0863] <DFU Device 121B7E30>: operation 0 progress 56
    [04:41:26.0867] <DFU Device 121B7E30>: operation 0 progress 57
    [04:41:26.0873] <DFU Device 121B7E30>: operation 0 progress 58
    [04:41:26.0877] <DFU Device 121B7E30>: operation 0 progress 59
    [04:41:26.0881] <DFU Device 121B7E30>: operation 0 progress 60
    [04:41:26.0885] <DFU Device 121B7E30>: operation 0 progress 61
    [04:41:26.0889] <DFU Device 121B7E30>: operation 0 progress 62
    [04:41:26.0895] <DFU Device 121B7E30>: operation 0 progress 63
    [04:41:26.0899] <DFU Device 121B7E30>: operation 0 progress 64
    [04:41:26.0903] <DFU Device 121B7E30>: operation 0 progress 65
    [04:41:26.0907] <DFU Device 121B7E30>: operation 0 progress 66
    [04:41:26.0913] <DFU Device 121B7E30>: operation 0 progress 67
    [04:41:26.0918] <DFU Device 121B7E30>: operation 0 progress 68
    [04:41:26.0922] <DFU Device 121B7E30>: operation 0 progress 69
    [04:41:26.0926] <DFU Device 121B7E30>: operation 0 progress 70
    [04:41:26.0930] <DFU Device 121B7E30>: operation 0 progress 71
    [04:41:26.0936] <DFU Device 121B7E30>: operation 0 progress 72
    [04:41:26.0940] <DFU Device 121B7E30>: operation 0 progress 73
    [04:41:26.0944] <DFU Device 121B7E30>: operation 0 progress 74
    [04:41:26.0948] <DFU Device 121B7E30>: operation 0 progress 75
    [04:41:26.0954] <DFU Device 121B7E30>: operation 0 progress 76
    [04:41:26.0958] <DFU Device 121B7E30>: operation 0 progress 77
    [04:41:26.0962] <DFU Device 121B7E30>: operation 0 progress 78
    [04:41:26.0966] <DFU Device 121B7E30>: operation 0 progress 79
    [04:41:26.0972] <DFU Device 121B7E30>: operation 0 progress 80
    [04:41:26.0976] <DFU Device 121B7E30>: operation 0 progress 81
    [04:41:26.0980] <DFU Device 121B7E30>: operation 0 progress 82
    [04:41:26.0984] <DFU Device 121B7E30>: operation 0 progress 83
    [04:41:26.0988] <DFU Device 121B7E30>: operation 0 progress 84
    [04:41:26.0994] <DFU Device 121B7E30>: operation 0 progress 85
    [04:41:26.0998] <DFU Device 121B7E30>: operation 0 progress 86
    [04:41:27.0002] <DFU Device 121B7E30>: operation 0 progress 87
    [04:41:27.0006] <DFU Device 121B7E30>: operation 0 progress 88
    [04:41:27.0012] <DFU Device 121B7E30>: operation 0 progress 89
    [04:41:27.0016] <DFU Device 121B7E30>: operation 0 progress 90
    [04:41:27.0020] <DFU Device 121B7E30>: operation 0 progress 91
    [04:41:27.0024] <DFU Device 121B7E30>: operation 0 progress 92
    [04:41:27.0028] <DFU Device 121B7E30>: operation 0 progress 93
    [04:41:27.0034] <DFU Device 121B7E30>: operation 0 progress 94
    [04:41:27.0038] <DFU Device 121B7E30>: operation 0 progress 95
    [04:41:27.0042] <DFU Device 121B7E30>: operation 0 progress 96
    [04:41:27.0046] <DFU Device 121B7E30>: operation 0 progress 97
    [04:41:27.0052] <DFU Device 121B7E30>: operation 0 progress 98
    [04:41:27.0057] <DFU Device 121B7E30>: operation 0 progress 99
    [04:41:27.0059] WinDFU::UploadData: EOF, cbRead: 1084
    [04:41:27.0060] <DFU Device 121B7E30>: operation 0 progress 100
    [04:41:27.0061] WinDFU::UploadData: ZLP
    [04:41:27.0062] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
    [04:41:27.0062] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
    [04:41:27.0063] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
    [04:41:27.0064] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
    [04:41:30.0061] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
    [04:41:30.0062] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
    [04:41:30.0063] WinDFU::ResetDevice: resetting...
    [04:41:30.0127] WinDFU::FinalizeDfuUpdate: success
    [04:41:30.0128] <DFU Device 121B7E30>: DFU succeeded
    [04:41:30.0130] Finished DFU Restore Phase: Successful
    [04:41:30.0174] DFU mode device disconnected
    [04:41:30.0175] Device removed when in state Restoring, moving device to transition state
    [04:41:30.0176] Changing state from 'Restoring' to 'Transitioning'
    [04:41:30.0178] Creating timer to monitor transition
    [04:41:41.0291] Recovery mode device connected
    [04:41:41.0292] Transitioning device returned, continuing restore.
    [04:41:41.0293] Canceling timer
    [04:41:41.0293] Changing state from 'Transitioning' to 'Restoring'
    [04:41:41.0294] requested restore behavior: Erase
    [04:41:41.0295] requested variant: Erase
    [04:41:41.0311] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [04:41:41.0927] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
    [04:41:41.0929] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
    [04:41:41.0930] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
    [04:41:41.0932] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
    [04:41:41.0933] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
    [04:41:41.0934] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
    [04:41:41.0936] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBSS"
    [04:41:41.0937] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
    [04:41:41.0938] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
    [04:41:41.0940] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
    [04:41:41.0941] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
    [04:41:41.0943] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
    [04:41:41.0944] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
    [04:41:41.0946] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
    [04:41:41.0947] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
    [04:41:41.0948] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
    [04:41:41.0950] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "LLB"
    [04:41:41.0951] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
    [04:41:41.0953] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
    [04:41:41.0954] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "SEP"
    [04:41:41.0955] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
    [04:41:41.0957] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreSEP"
    [04:41:41.0958] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
    [04:41:41.0960] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
    [04:41:41.0961] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
    [04:41:41.0962] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
    [04:41:41.0964] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
    [04:41:41.0966] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
    [04:41:41.0967] iBoot build-version = iBoot-1940.10.58
    [04:41:41.0968] iBoot build-style = RELEASE
    [04:41:41.0969] requested restore behavior: Erase
    [04:41:41.0971] requested restore behavior: Erase
    [04:41:41.0972] unable to open device_map.txt: No such file or directory
    [04:41:41.0974] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
    [04:41:41.0975] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [04:41:41.0976] AMDeviceIoControl: GetOverlappedResult failed
    [04:41:41.0979] AMDeviceIoControl: pipe stall
    [04:41:41.0980] USBControlTransfer: error 31, usbd status c0000004
    [04:41:41.0981] command device request for 'getenv radio-error' failed: 2008
    [04:41:41.0983] radio-error not set
    [04:41:41.0984] unable to open device_map.txt: No such file or directory
    [04:41:41.0985] <Recovery Mode Device 12703958>: production fused device
    [04:41:41.0987] requested restore behavior: Erase
    [04:41:41.0989] requested restore behavior: Erase
    [04:41:41.0990] interface has 1 endpoints, file pipe = 1
    [04:41:41.0990]
    [04:41:41.0991] <Recovery Mode Device 12703958>: operation 4 progress -1
    [04:41:41.0992] unable to open device_map.txt: No such file or directory
    [04:41:41.0992] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
    [04:41:41.0993] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [04:41:41.0994] requested restore behavior: Erase
    [04:41:41.0995] requested restore behavior: Erase
    [04:41:41.0996] <Recovery Mode Device 12703958>: operation 42 progress -1
    [04:41:41.0996] requested restore behavior: Erase
    [04:41:43.0024] <Recovery Mode Device 12703958>: operation 5 progress -1
    [04:41:43.0367] unable to open device_map.txt: No such file or directory
    [04:41:43.0369] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
    [04:41:43.0370] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [04:41:43.0370] AMDeviceIoControl: GetOverlappedResult failed
    [04:41:43.0371] AMDeviceIoControl: pipe stall
    [04:41:43.0372] USBControlTransfer: error 31, usbd status c0000004
    [04:41:43.0373] command device request for 'getenv ramdisk-delay' failed: 2008
    [04:41:44.0483] <Recovery Mode Device 12703958>: operation 6 progress -1
    [04:41:45.0512] <Recovery Mode Device 12703958>: operation 7 progress -1
    [04:41:45.0832] <Recovery Mode Device 12703958>: operation 8 progress -1
    [04:41:45.0833] unable to open device_map.txt: No such file or directory
    [04:41:45.0833] found device map entry for 0x00008960 0x00000000. boardConfig=n51ap platform=s5l8960x
    [04:41:45.0834] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [04:41:45.0835] <Recovery Mode Device 12703958>: operation 9 progress -1
    [04:41:45.0836] <Recovery Mode Device 12703958>: Recovery mode succeeded
    [04:41:45.0836] Finished Recovery Restore Phase: Successful
    [04:41:46.0607] Recovery mode device disconnected
    [04:41:46.0609] Device removed when in state Restoring, moving device to transition state
    [04:41:46.0611] Changing state from 'Restoring' to 'Transitioning'
    [04:41:46.0612] Creating timer to monitor transition
    [04:41:49.0792] Restore completed, status:4014
    [04:41:49.0792] Failure Description:
    [04:41:49.0792] Depth:0 Error:Unexpected device state 'DFU' expected 'RestoreOS'[
    and After one time give me
    2014-04-13 14:22:48.639 [3380:18a4]: restore library built Feb 12 2014 at 16:27:17
    2014-04-13 14:22:48.639 [3380:18a4]: iTunes: iTunes 11.1.5.5
    2014-04-13 14:22:48.639 [3380:18a4]: iTunes: Software payload version: 11D167 (option key)
    2014-04-13 14:22:48.639 [3380:18a4]: iTunes: Using MobileRestore state machine
    [12:24:20.0679] Changing state from 'Idle' to 'Restoring'
    [12:24:20.0713] AppleDevice::GetDeviceID: failed for iBoot
    [12:24:20.0714] AppleDevice::GetDeviceID: failed for iBoot
    [12:24:20.0719] requested restore behavior: Erase
    [12:24:20.0728] requested variant: Erase
    [12:24:20.0803] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [12:24:21.0345] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
    [12:24:21.0345] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreLogo" Digest = "<CFData 12C393C0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0346] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreDeviceTree" Digest = "<CFData 12C38EB0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0347] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 12C39408 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0348] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 12C38E68 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0349] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 12C388C8 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0350] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 12C38A30 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0351] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 12C37EA8 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0352] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "Diags" not part of manifest, skipping
    [12:24:21.0352] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "CFELoader" not part of manifest, skipping
    [12:24:21.0353] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RBM" not part of manifest, skipping
    [12:24:21.0354] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PHLEET" not part of manifest, skipping
    [12:24:21.0354] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PERTOS" not part of manifest, skipping
    [12:24:21.0355] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "PEHammer" not part of manifest, skipping
    [12:24:21.0356] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow1" Digest = "<CFData 12C38F40 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0357] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow0" Digest = "<CFData 12C394E0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0358] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 12C389A0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0358] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBoot" Digest = "<CFData 12C38AC0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0359] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "DeviceTree" Digest = "<CFData 12C385B0 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0360] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "SEP" Digest = "<CFData 12C37D40 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0361] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging1" Digest = "<CFData 12C39768 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0362] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreSEP" Digest = "<CFData 12C38958 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0363] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "AppleLogo" Digest = "<CFData 12C391C8 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0364] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryPlugin" Digest = "<CFData 12C39888 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0365] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryFull" Digest = "<CFData 12C39600 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0366] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging0" Digest = "<CFData 12C39450 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0367] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RecoveryMode" Digest = "<CFData 12C39840 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [12:24:21.0368] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 12BDD478 [720B907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
    [12:24:21.0369] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
    [12:24:21.0369] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per9561.tmp/amai/debug/ts s-request.plist
    [12:24:23.0320] amai: tss_submit_job: HttpQueryInfo returned 200
    [12:24:23.0326] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.0.0)
    [12:24:23.0328] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/ADMINI~1/AppData/Local/Temp/Per9561.tmp/amai/debug/ts s-response.plist
    [12:24:23.0408] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
    [12:24:23.0410] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "CFELoader"
    [12:24:23.0412] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "RBM"
    [12:24:23.0414] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PHLEET"
    [12:24:23.0415] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PERTOS"
    [12:24:23.0417] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "PEHammer"
    [12:24:23.0443] <DFU Device 07B89C58>: production fused device
    [12:24:23.0444] requested restore behavior: Erase
    [12:24:23.0446] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [12:24:23.0447] AppleDevice::GetDeviceID: failed for iBoot
    [12:24:23.0447] AppleDevice::GetDeviceID: failed for iBoot
    [12:24:23.0454] amai: AMAuthInstallPlatformCreateDataFromFileURL: can't resolve file
    [12:24:23.0455] failed to read dfu file C:\Users\ADMINI~1\AppData\Local\Temp\Per9561.tmp\Firmware\dfu\iBSS.n51ap.RELEAS E.im4p
    [12:24:23.0455] WinDFUUpload: dfuData is NULL!
    [12:24:23.0456] AMRAuthInstallDeletePersonalizedBundle
    [12:24:23.0765] Restore completed, status:2005
    [12:24:23.0765] Failure Description:
    [12:24:23.0765] Depth:0 Error:Failed to restore device in DFU mode.
    i hope some one help me

    Put the iPhone in DFU mode. Connect in iTunes. Hit Restore.
    (Don't use Shift or Option)

  • Unable to commit the project status change

    Dear Experts,
    I am developing a utility program to change the status of multiple projects at once.
    I am changing the status of Phase, task, check list,check list item and Project status from
    Create to Release, release to Complete and to Work Effor Complete.With respective status change BAPIS.
    when ever the projects is not able to change the status success fully due to validations
    such as person respondsble not mainted or any other basic data is missing,
    We are not committing the changes if every thing goes fine we are commiting with BAPI: BAPI_CPROJECTS_COMMIT_WORK
    but when we commit with this it still retaining the previous project status in LUW and trying to commit previous project too.
    and commit is getting failed.
    I am not able to roll back or free the project with BAPI:BAPI_CPROJECTS_ROLLBACK_WORK and BAPI_BUS2172_FREE
    BAPI_CPROJECTS_ROLLBACK_WORK: when iam trying to use this BAPI it is going to short dump
    BAPI_BUS2172_FREE:  It is returing error saying unable to free the project.
    Could you please tell how to roll back the changes to the project or how to commit only success full projects (Project with out any errors in status change.)
    Kindly do the needful
    Thanking you.
    -ravi

    Program flow
    Loop at It_Project
    *Status Change for Check List
    CALL FUNCTION 'BAPI_BUS2176_SET_STATUS'
        EXPORTING
          checklist_guid                = p_guid
      IV_STATUS_PROFILE             =
         is_business_transaction       = lv_bus_trans
         TABLES
             return                    =  t_return.
    *Status Change for task
      CALL FUNCTION 'BAPI_BUS2175_SET_STATUS'
        EXPORTING
          task_guid               = p_guid
          is_business_transaction = lv_bus_trans
        TABLES
          return                  = t_return.
    *Status Change for project
    CALL FUNCTION 'BAPI_BUS2172_SET_STATUS'
          EXPORTING
            project_definition_guid = p_guid
            is_business_transaction = lv_bus_trans
          TABLES
            return                  = t_return.
    If there is a sucess in changing the status.
    CALL FUNCTION 'BAPI_CPROJECTS_COMMIT_WORK'
        TABLES
          return = t_creturn.
    Else.
        CALL FUNCTION 'BAPI_CPROJECTS_ROLLBACK_WORK'
          TABLES
            return = t_rreturn.
    Endif.
    Endloop.
    In the above code when we are executing  BAPI_CPROJECTS_ROLLBACK_WORK is going for dump.
    If we simply commit with  BAPI_CPROJECTS_COMMIT_WORK for all the projects then if any project
    commits with error same error is re produced for all the following projectsid (unable to destroy the LUW).
    and in CRM we can't use 'BAPI_TRANSACTION_ROLLBACK'.

  • ERecruiting - Triggering of mail when candidate status changes

    Hi All,
    Is an email generated from the system, when a candidate status is changed?
    Say for example if the Activity of an candidate is changed to "Status Change - Rejected", will an email will be generated?

    Hello,
    some general thoughts at the beginning:
    Candidates do not have a rejected state. Candidate states are profile locked and profile released. Only applications and candidacies have a rejected state. It is very important for a technical view to have the obect types in e-recruiting very clear or you will get into big trouble sooner or later.
    SAP delivered workflows are examples. They do not fit a production environment. Also the sap delivered activity and process customizing is an example (and no good one) you will have to design this according to the business needs in the project.
    For the workflow question. It is possible to trigger a workflow by activity creation and activity completion. For status chage activities ths is the same as they are completed directly and never have status planned. The BOR object ERC_ACTIV contains both events, activtycreated is triggered directly, activitycompleted needs a note to run properly.
    It is also possible to trigger a workflow by a status change of an object. The super BOR object ERC_OBJECT contains a statuschanged event, which is raised for all status changes of NA, NB, NC, ND and NE objects.
    For rejection there are basically 2 scenarions.
    Scenario 1
    When rejecting a candidacy by creating a rejection activity you trigger a workflow based on the activity to create the corresponces activity automatically. You can either send it directly or just create it to allow the user to have an individual text. (I do not go into details of this workflow according to the chosen application-candidacy-relation, that would go to far at this point).
    Scenario 2
    When rejecting a candidacy directly in minimum data entry you do not have a status change activity as the status is set directly. In this case you have a workflow which is triggered directly by the status chang which again creates (and sends) the correspondence activity.
    Of course you need checks to ensure the two workflows are not mixed.
    Kind regards
    Roman

  • ERecruitment (EHP4) distributed scenario  - Questions status changes

    I am creating questions in draft mode and then changing back the status to released after it is complete.
    I then want to create the questionnaires and use them in the process template.
    Issue:
    Even though I can change the status of the questions from "Draft" to "Released", when I close the "Create Questions screen and come back, the status automatically reverts back to "Draft".
    Periodic Services are running every 5 minutes.
    Due to the issue with the status change, I cannot create a questionnaire and release them to be used elsewhere.
    Any thoughts on where else to look?
    Thanks, Sunil

    Hello sunil,
    I could reproduce this error in one of the sandboxes I can access.
    The reason for this system behavouir seems to be an inconsistency in configuration of SES search. When you save the questionaire in status released the UI shows a success message but you should find an error message in TCode SLG1 like:
    - Exit WRITE_CPOINTER_SES of exit area AT does not exist or
    - Enhancement'Write Change Pointer for SES Search (in COM_SE_CPO' (area 'Follow-Up Processing (Background)') is not assigned to category 'Evaluable Information'
    The error is not shown in the UI as someone put the following code in there:
    METHOD save_quesnr_status.
      TRY.
          CALL METHOD cl_hrrcf_qa_bl=>change_template_status
            EXPORTING
              p_template_id = is_quesnr_object-objid
              p_new_status  = iv_status_new.
        CATCH cx_root.
      ENDTRY.
    ENDMETHOD.
    On a system wehre I did the SES config myself questionaires can be released correctly. Please apply the sap note 1098046 step by step (esp. number 2 and 3 are important for this special issue, including the note mentioned there). After doing this on the sandbox releasing questionaires works fine.
    Best regards
    Roman

  • Event triggering through status change

    Hi,
    Currently I am learning workflow. I came to know that events could be triggered even with a status change. Could anyone let me what does "status change" mean? It would be better if anyone give me a high-level view of an example related to this?
    Thank you,
    Raja

    Hi Raja,
    Take an example of Service notification.
    It can have differnt technical status like <i>Created, Inprocess, Technically complete</i> or <i>Released</i>.
    Based on the particular status, say when notification is <b>Technically complete</b>, you want to inform somebody, you can do it with workflow and status management.
    Hope it clarifies idea of status changes/ management.
    For more help refer:
    http://help.sap.com/saphelp_47x200/helpdata/en/c5/e4aee2453d11d189430000e829fbbd/content.htm
    Regds,
    Akshay

Maybe you are looking for

  • To use a Sap Exit variable in a diferent infoobject of the same type

    Hi gurus,   I have the Sap Exit standard variable 0P_KEYDT in the infoobject Posting Date (0PSTG_DATE), and i need use this variable with the Document Date (0DOC_DATE), but i don´t have it in the infoobject. Both infoobjects are referenced by 0DATE.

  • Wiped macbook pro will not boot from install DVD

    I recently purchased an older MacBook Pro that came with the OS system wiped but it did have the original Install DVDs.  The computer will not boot from the DVD.  I have booted holding down the C key and nothing happens.  I have booted holding down t

  • I have a question. my ipod won't mount

    I have 3rd generation ipod 40gb. The ipod plays fine (whats on it) but when i plug it in the bells go off and the ipod reads "do not disconnect" but itunes won't open and if i open it myself it still dosen't see the ipod. I was going to retore it but

  • Can I rock an "else if" in advanced actions.

    Hey all, Is there a way to add an "else if" statement to conditional actions in the captivate advanced actions dialogue? The if>then>else is obvious but I want if>then>else if>then>else.  And I don't want to have to build a widget or write JS if I ca

  • Car holder for E-51?

    In the latest (Feb!) issue of PcPro, there's a query from a reader about a car holder with charger for the E-51. mark Squires, Nokia UK's head of comms is reported as saying that the CR-82 will work with the E-51. This isn't confirmed on the Nokia we