SC Complete Status Report

Hi All;
We are using SRM7 classic scenario where PO is created in ERP. Confirmation takes place in SRM.
Is there a transaction or report which will show the compelet status of the SC as follows:
SC No.
SC date:
SC created by:
SC approved by:
PO No.:
PO created by:
PO approved by:
Cofirmation (GR) made by:
Confirmation Approved by:
If no such report exists, would you please tell me in whic tables i can found these information?
Thanks

Hi
SRM has limited reports .
try
BBP_BW_SC1
BBP_BW_SC2
BBP_BW_SC3
BBP_BW_SC4
transactions
You can explore more BI reporsts if you were connected to BW system..

Similar Messages

LMS Completion Status Reporting Incorrectly

We currently use Learn.com as our LMS solution. When we publish our Captivate projects to the LMS, users course completion status is marked as
'Completed' after they have opened the course and viewed the first slide. I've set our reporting settings from the Preferences>Quiz>Reporting to Complete/Incomplete and Slide Views only to 100%. I don't understand why it's reporting completed when users have only viewed one slide.

Hi,
Which version of Captivate are you using?
What are the Quiz Reporting Settings? Have you published to SCORM or AICC?
Please let us know.
Thanks,.
Sushma

Set the workflow about PPR process as completed status with a report.

Hi Gurus,
I need to complete a workflow and all regarding task from UWL.
To do this, I implemented 2 functions module: the first to execute the dialog step and the second to set the dialog step as completed status.
When I run the report the both function module doesn't work. Sy-subrc return me different result as 0.
If I execute the SWIA T-code, I see all the task and there I execute the "dialog step" WORK ITEM to set it from ready status to started status and after I use "complete manualy" for the same task then the workflow created a new "dialog step" WORK ITEM I do the same with it and the workflow is completed.
So I would like to do the same in a report with SAP_WAPI_SET_WORKITEM_STATUS and SAP_WAPI_DECISION_COMPLETE functon module ... please see my code below:
loop at lit_wi_stat where wi_type = 'W' and wi_stat = 'READY'.
*to set dialog step WORK ITEM as started status.
      call function 'SAP_WAPI_SET_WORKITEM_STATUS'
        exporting
          workitem_id          = lit_wi_stat-wi_id
          status               = 'STARTED'
          user                 = sy-uname
          language             = sy-langu
          do_commit            = 'X'
        importing
          new_status           = lit_wi_status
          return_code          = lv_subrc
      TABLES
        MESSAGE_LINES        =
        MESSAGE_STRUCT       =
*to set dialog step WORK ITEM as completed status
      call function 'SAP_WAPI_DECISION_COMPLETE'
        exporting
          workitem_id          = lit_wi_stat-wi_id
          language             = sy-langu
          user                 = sy-uname
          decision_key         = '0001'
          do_commit            = 'X'
      IMPORTING
        RETURN_CODE          =
        NEW_STATUS           =
      TABLES
        MESSAGE_LINES        =
        MESSAGE_STRUCT       =
    endloop.
But it doesn't work correctly.
Maybe you have a better idea to reproduce the complete process in a report.
Thanks in advance for your reply..
Best regards.
Julien.

Hi Chandni
I would presume that you are calling some activity step to perform some operation ...when this fails, you are passing some flag to the workflow to send the email and the "planned" error!
It's pretty simple then:
1) Analyze the flag using a condition step
2) Use mail step to send the email
3) Call a custom method to raise a workflow exception - workflow will go in error.
More on Workflow Exceptions:
BO Based Exception:
http://help.sap.com/saphelp_nw73EhP1/helpdata/en/4f/372e0cf5d95541e10000000a421937/content.htm?frameset=/en/4f/3457d50a7b5542e10000000a421937/frameset.htm
How you can define custom BO:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0f157e8-456b-2910-8ea5-c57d9267c913?overridelayout=true
Or you can also trigger Class based Exceptions if you are using ABAP OO for workflow (custom functionality via Class using IF_WORKFLOW Interface). Just make sure you make your Custom Exception Class as a child of CX_BO_TEMPORARY or CX_BO_APPLICATION
Regards,
Modak

Error while generating the Document... Bursting Status Report

Hey all,
I am getting some errors in a production environment when trying to burst out some invoice data.
This process has been pretty robust and out of 1000+ invoices a day, I can only find 4 that are failing regularily.
Why am I mentioning?, just to show that I am thinking this is a data issue, but just cannot see anything that stands out.
I can take the xml output and run it through my development suite on my local machine and all runs fine.
Just when it is running live through the db is when it fails.
Here is the Bursting output that shows the error....
<?xml version="1.0" encoding="UTF-8"?>
<BURS_REPORT>
<REQUESTID>27044820</REQUESTID>
<PARENT_REQUESTID>27044726</PARENT_REQUESTID>
<REPORT_DESC>Invoice Print Selected Invoices</REPORT_DESC>
<OUTPUT_FILE>[$OUT_DIR]/o27044820.zip</OUTPUT_FILE>
<DOCUMENT_STATUS>
<KEY></KEY>
<OUTPUT_TYPE>pdf</OUTPUT_TYPE>
<DELIVERY></DELIVERY>
<OUTPUT></OUTPUT>
<STATUS>fail</STATUS>
<LOG>Error while generating the Document...</LOG>
</DOCUMENT_STATUS>
</BURS_REPORT>
The problem is that this output doesn't necessarily help, nor can I find any hints in the OPP logs.
So... the question becomes...
Any ideas on where I can look to resolve this issue?+
Or where I can find any clues at, that would possible point at the issue?+
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
BI Publisher 5.6.3
Thanks
Hayden,

Tim,
Thanks for the suggestion, always seems to slip my mind that the Bursting Report has debug on it.
As far as what is generating the XML, it is oracle's standard, only slightly modified ... ;), invoice generating report, RAXINV_SEL.
Well RAXINV_SEL, or RAXINV_NEW, doesn't matter, same code, that is the executable.
I have turned on the debug, for both the source xml and the burst request, and unfortunately, still nothing stands out to me.
I was really expecting to see something in the burst log, pasted at the bottom...
but, it yet avoids me.
If I had to guess, I would bet the user went, in our terminology, "slashwit crazy", or example "model /w options", in some description.
But can't seem to find which field it is blowing up on, since we are catching these special characters in several places already, and slashwit is littered throughout the output.
I was also looking in the bursting control file for the special xml tags identified there, as those would require no slashes. But those are all clean.
Hayden,
XML Publisher: Version : 11.5.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XDOBURSTREP module: XML Publisher Report Bursting Program
Current system time is 21-SEP-2009 10:43:12
XML/BI Publisher Version : 5.6.3
Request ID: 27048106
All Parameters: ReportRequestID=27044726:DebugFlag=Y
Report Req ID: 27044726
Debug Flag: Y
Updating request description
Updated description
Retrieving XML request information
Node Name:{node}
Preparing parameters
null output =/u007/app/applmgr/{instance}/out/{instance}/o27048106.out
inputfilename =/u007/app/applmgr/{instance}/out/{instance}/o27044726.out
Data XML File:/u007/app/applmgr/{instance}/out/{instance}/o27044726.out
Set Bursting parameters..
Temp. Directory:/u007/app/applmgr/{instance}/temp
[092109_104315337][][STATEMENT] Oracle XML Parser version ::: Oracle XDK Java 9.0.4.0.0 Production
[092109_104315340][][STATEMENT] setOAProperties called..
Bursting propertes.....
{burstng-source=EBS, font.Free 3 of 9.normal.normal=truetype./usr/java/jre/lib/fonts/FREE3OF9.TTF, font.Times New Roman.normal.normal=truetype./usr/java/jre/lib/fonts/TIMES.TTF, system-temp-dir=/u007/app/applmgr/{instance}/temp, font.Arial.italic.normal=truetype./usr/java/jre/lib/fonts/ARIALI.TTF, user-variable:cp:parent_request_id=27044726, user-variable:cp:application_short_name=XDO, font.Courier New.normal.bold=truetype./usr/java/jre/lib/fonts/COURBD.TTF, font.Times New Roman.normal.bold=truetype./usr/java/jre/lib/fonts/TIMESBD.TTF, user-variable:cp:request_id=27048106, font.Arial.normal.normal=truetype./usr/java/jre/lib/fonts/ARIAL.TTF, font.Courier New.normal.normal=truetype./usr/java/jre/lib/fonts/COUR.TTF, user-variable.OA_MEDIA=http://diierp.corio.com:8002/OA_MEDIA, font.Courier New.italic.bold=truetype./usr/java/jre/lib/fonts/COURBI.TTF, user-variable:cp:org_id=83, user-variable:cp:DebugFlag=Y, font.Times New Roman.italic.bold=truetype./usr/java/jre/lib/fonts/TIMESBI.TTF, user-variable:cp:responsibility=51270, font.Arial.italic.bold=truetype./usr/java/jre/lib/fonts/ARIALBI.TTF, font.Courier New.italic.normal=truetype./usr/java/jre/lib/fonts/COURI.TTF, user-variable:cp:user=HAYDEN, user-variable:cp:reportdescription=Invoice Print Selected Invoices, user-variable:cp:language=en, font.Times New Roman.italic.normal=truetype./usr/java/jre/lib/fonts/TIMESI.TTF, user-variable:cp:ReportRequestID=27044726, user-variable:cp:locale=en-US, user-variable:cp:territory=US, font.Arial.normal.bold=truetype./usr/java/jre/lib/fonts/ARIALBD.TTF}
Start bursting process..
Bursting process complete..
Generating Bursting Status Report..
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
------------- 1) PUBLISH -------------
Beginning post-processing of request 27048106 on node {node} at 21-SEP-2009 10:43:19.
Post-processing of request 27048106 completed at 21-SEP-2009 10:43:20.
Finished executing request completion options.
Concurrent request completed
Current system time is 21-SEP-2009 10:43:20
---------------------------------------------------------------------------

'Project Status Report' activation in cProjects

Hi,
I was trying to configure the Status Reports in cProjects. I have completed creation of the form (chose DPR_PROJECT), activated the templates for the relevant Project type and also implemented the Badi with the correct form name. I am still unable to see any template dropdown in the application (cProjects). The DPR_Project template should appear in the same for me to create the Status Report. Please advice.
Thanks,
Sachin

Hi Sachin ,
I think, it may be a ADS installation issue.
The configuration of ADS server is somehow not very easy, as I saw so many installations problems with status report in cProj. 4.0.
Would you please check the following notes:
900310 & 992492 .
And the following reports may be helpful to check the setting:
FP_PDF_TEST_00 (returns version number of ADS)
FP_TEST_00 (creates a test PDF)
FP_EXAMPLE_01 (creates a test PDF using SFLIGHT data)
FP_TEST_IA_01 (creates an interactive PDF that can be signed via certificate)
FP_PDF_TEST_12 (returns signatures of a signed PDF  requires secure (SSL) ADS connection  ADS_HTTPS)
Kind regards,
Zhenbo

Few CRs are coimng under "Not Completed" status in CRM_DNO_MONITOR transact

Hi All,
Few (only 3) change requests are coming in "Not Completed" status in CRM_DNO_MONITOR transaction. Ideally all closed change requests should not come under "Not Completed" staus when reporting is done.
Kindly help.

Hi,
Please try to implement this note
1459839 CRM_SOCM_SERVICE_REPORT: no update on CRMD_ORDER wo
if after this still issue persists, then please run
CRM_INDEX_REBUILD to correct the CR's status
Hope this helps.
Cheers
SH

What are the settings under SCORM 2004 to indicate the completion status on LMS

Hi everyone,
I have a captivate file which i have published as scorm 2004 compliant and checked that file on the scorm cloud. It worked well.
SCORM Pacakage does note report partial completion. When a person stops training, we have the progress bar to indicate that they are at 0, 25, 50, 75 or 100%.
Problem: I dont know exactly, what are the settings to enable to indicate the completion status. I tried but it didn't worked.
Please help & suggest the right way to do this..
Regards
Vikas Sharma

anybody there.... pls help

Completion Status Sent Two Times

I am having a problem with my completion status being sent
twice to an LMS. I have 5 questions that are multiple choice (I
give users two attempts at answering each question). Prior to the
Results page, the results are sent to the LMS and the record is
sent twice, not once, like I would like it to be. I have turned off
"reporting interactions", I've turned off the message when an
answer is "correct"...I am not sure what I am doing wrong. Is there
some way to control the submit button or control how the data is
sent to the LMS? Please help...thanks!

chuckguytoronto,
This message seems quite similiar to someone else posting
with the same
issue. Is this AICC or SCORM? What problem is occuring with
the status
being sent more than once?
Regards,
Andrew

How to Use Solution Manager to collect Status Reports from Consultants

Hi,
I am planning to use Solution Manager for collecting the weekly status reports from my consultants and maintain it as a repository . Please let me know the best way of doing this in SOLMAN. There should be mailing options too.
BR,
Raj

Hi Rajasan,
to be able to meet this requirement, you need to set up plan working load in admin tab for your resource, they need to update actual data based on the work completion, you will get status of work,
if you require email, you need to set-up scot, then develop a program with execution scheduling
please check and revert
Anil

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)

Feature requests: Quotas & status reports

I just sent the following feedback to Apple:
"Beside the highly missed backup to AirDisks I would appreciate two additional features in TimeMachine: (1.) I'd like to set a quota for the backup set as I don't want it to fill up the device completely (2.) It would be great to have a daily status report (e. g. by mail) about the performed backups, their size, the oldest backup and available diskspace. I've got three Macs in my family using TM and I'd like to control the backup without logging into every machine."
Anyone to second this?
Mattes

Ricktoronto wrote:
If you have a say 500GB drive and you want to limit say 300 GB to TM, you make a 300GB partition on that drive and tell TM that partition is its drive.
Thanks for this advice, I was aware of this possibility, but with three Macs backing up to the same USB device, I do not want to hold a partition for every client. Another tweak is to limit the size of the sparse images with "hdiutil", but why not implement this option in the product itself ... ?
Mattes

SABA LMS Completion Status is always "Successful" -- even if quiz skipped

For a course I'm creating, the SABA LMS Completion Status is always “Successful” even if just 1 slide of the Scorm 1.2 compliant Adobe Presenter course is viewed – doesn’t even need to get into quiz.
A failing grade is also always "Successful". How to get an "Unsuccessful" for skipping the quiz and/or failing the quiz?
Settings:
Reporting - Quiz Manager:
Enable reporting for this project -- checked
Learning Managemenet System (LMS) -- Scorm
Choose Report Data -- Report Quiz results only
Report Pass or Fail -- Report Pass/Fail (should this be Report staus as defined by report data?)
Report Score to LMS as: Percent
Reporting Level -- Report interactions and the score

I have Presenter courses working properly in Saba. Sometimes the issue is your Offering or Content settings in Saba. Could be a combo of having Is Scoring checked and having a Mastery Score set on Course or Offering level.
When you dig down into the Activity History for that transcript completion, what status is listed on the module level? Saba will roll up to a status of Successful/Unsuccessful/Not Evaluated depending on how you have it setup. What Status is your content actually passing back: Completed, Incomplete, Passed, Failed?
Good Luck!

How to set completion status

Hello,
I have a course built in Captivate 3 that automatically moves to completed within our LMS when users open it. How can I set the status to not change until users have gone through the entire course? Any ideas?
Thanks!

Hi Shannon,
In our LMS this occurs if I add the SWF as a Flash file when I upload to the LMS. However, if I enable reporting on the Quiz Preferences pages in the Captivate file before publishing and then import it as a SCORM package in the LMS it uses the LMS customization settings on the Quiz Preferences page to track and set a completion status.

SOCO completion status. How I can see that status in a SC repport

Hello,
I have completed a shopping cart (SC) in the sourcing cockpit.
How can I see the completed status in the shopping cart or in a shopping cart repport.
I can do not see it in
BBP_BW_SC4 - Shopping Carts per Cost Center
BBP_BW_SC3 - Shopping Carts per Product
Nor in SC Check status
Cheers,
Marta

Hi Marta,
You can see the status only if you have SAP_EC_BBP_EMPLOYEE role with Check status transaction attached to it.I feel that you are using some Z role where check status transaction is not maintained.
You can check your roles in SU01 transaction role tab.
for
BBP_BW_SC4 - Shopping Carts per Cost Center
BBP_BW_SC3 - Shopping Carts per Product
You need to have buyer role SAP_EC_BBP_OP_PURCHASER to see these reports.
Regards,Nishant

Sales order delivery status report

Hi,
i have to give a report on sales order delivery status report which displays the sales order information and delivery status details. and also please let me know the tables.
thanking you in advance.

Hi,
For the document header and document items, VBAK and VBAP, you can find the delivery status in the table VBUK and VBUP respectively.
The fields are VBUK-LFSTK
In VBUP, the field is VBUP-LFSTA which can take values, null, A, B, C for not relevant, Not yet processed,Partially processed and Completely processed
Based on this, you can write your report.
Hope this helps. You can reward if this helps.

SC Complete Status Report

Similar Messages

Maybe you are looking for