Status updates history period default

Hi
Is there any way to change the default status updates history date range from 3 months please? Currently as the status approver for a major change program I'm getting several hundred tasks to approve every day across multiple project plans; the problem
is that when I go in to clear down to run my weekly reports it lists every task submission for the last 3 months. The thing is, IE can take several minutes before it displays the page in full as it chews through all of the data which is annoying
to say the least.
I'd quite like it to show only the last 3 weeks, not the last 3 months.
Does anyone have any suggestions please?
Thanks.

Hi,
As far as I tested, changing the default 3 months range from the date range feature will unfortunaltely not be kept in your IE cache next time you'll navigate to the status update history page. Thus you'll have to set it again every time you access
the page.
I guess this 3 months default value might be changed programmabily but I can't help on this.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Similar Messages

Report on "Status updates history"

Hi,
i need to check if resource are updating task from "My Task". Is it possible to estract a report on "Status updates history"?
I mean this type of data:
Approval Date
Action
Status
Info
Task Name
Project
Type
Start
Finish
Actual Work
Remaining Work
% Complete
Assigned To
Approved By
Thanks
Daniele

Hi Daniel,
You will probably have to create a join with the MSP_ASSIGNMENT_TRANSACTIONS Table.
See reference here:
http://blogs.msdn.com/b/project_programmability/archive/2008/01/03/statusing-transactions-partial-documentation.aspx
Hope this helps.
Guillaume Rouyre - MBA, MCP, MCTS

Windows 2008 R2 Server not showing update history and not detecting new updates

Hi Sirs,
We have a Windows 2008 R2 server which is showing an empty windows update history, and is not detecting new updates from the WSUS server. It says that the windows is up to date, no error when trying to detect new updates, but I doubt it because when I checked
the installed updates menu, it shows that that the most recent update date installed was last 2013, it just stop detecting and installing updates. I've already tried the ff workarounds but to no avail:
1. restart wuauserv and bits service
2. rename/delete the software distribution folder
3. reinstalled the update agent/restarted the server
4. deleted the susclientid on the registry
Thanks in advanced for your help.
here's the windowsupdate.log:
2014-07-22   00:57:06:728   928   a34   AU   #############
2014-07-22   00:57:06:728   928   a34   AU   Successfully wrote event for AU health state:0
2014-07-22   00:57:06:728   928   a34   AU   Featured notifications is disabled.
2014-07-22   00:57:06:728   928   a34   AU   AU setting next detection timeout to 2014-07-21 20:50:56
2014-07-22   00:57:06:728   928   a34   AU   Successfully wrote event for AU health state:0
2014-07-22   00:57:06:728   928   a34   AU   Successfully wrote event for AU health state:0
2014-07-22   00:57:11:727   928   abc   Report   REPORT EVENT: {AF0753F1-F6F9-4583-87B0-A0B0AEA0C6A7}   2014-07-22 00:57:06:728+0800   1
147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows
Update Client successfully detected 0 updates.
2014-07-22   00:57:11:727   928   abc   Report   REPORT EVENT: {188957AA-577F-4DC5-9CDB-2D8CFEE96670}   2014-07-22 00:57:06:728+0800   1
156   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Pre-Deployment Check   Reporting
client status.
2014-07-22   00:57:11:727   928   abc   Report   CWERReporter finishing event handling. (00000000)
2014-07-22   01:11:10:931   928   abc   Report   Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22   01:11:10:947   928   abc   Report   Reporter successfully uploaded 2 events.
2014-07-22   04:50:56:736   928   1130   AU   #############
2014-07-22   04:50:56:736   928   1130   AU   ## START ## AU: Search for updates
2014-07-22   04:50:56:736   928   1130   AU   #########
2014-07-22   04:50:56:736   928   1130   AU   <<## SUBMITTED ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
2014-07-22   04:50:56:736   928   d08   Agent   *************
2014-07-22   04:50:56:736   928   d08   Agent   ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   04:50:56:736   928   d08   Agent   *********
2014-07-22   04:50:56:736   928   d08   Agent      * Online = Yes; Ignore download priority = No
2014-07-22   04:50:56:736   928   d08   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22   04:50:56:736   928   d08   Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22   04:50:56:736   928   d08   Agent      * Search Scope = {Machine}
2014-07-22   04:50:57:017   928   d08   Setup   Checking for agent SelfUpdate
2014-07-22   04:50:57:017   928   d08   Setup   Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22   04:50:57:017   928   d08   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   04:50:57:017   928   d08   Misc   Microsoft signed: Yes
2014-07-22   04:50:59:611   928   d08   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   04:50:59:611   928   d08   Misc   Microsoft signed: Yes
2014-07-22   04:50:59:611   928   d08   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   04:50:59:611   928   d08   Misc   Microsoft signed: Yes
2014-07-22   04:50:59:626   928   d08   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   04:50:59:626   928   d08   Misc   Microsoft signed: Yes
2014-07-22   04:50:59:626   928   d08   Setup   Determining whether a new setup handler needs to be downloaded
2014-07-22   04:50:59:626   928   d08   Setup   SelfUpdate handler is not found. It will be downloaded
2014-07-22   04:50:59:626   928   d08   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   04:51:01:095   928   d08   Setup   Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   04:51:01:095   928   d08   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   04:51:01:110   928   d08   Setup   Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   04:51:01:110   928   d08   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   04:51:01:142   928   d08   Setup   Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   04:51:01:142   928   d08   Setup   SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22   04:51:01:860   928   d08   PT   +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22   04:51:01:860   928   d08   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   04:51:01:891   928   d08   PT   WARNING: Cached cookie has expired or new PID is available
2014-07-22   04:51:01:891   928   d08   PT   Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22   04:51:01:891   928   d08   PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22   04:51:04:485   928   d08   PT   +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22   04:51:04:485   928   d08   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   04:51:04:875   928   d08   Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22   04:51:04:875   928   d08   Agent   *********
2014-07-22   04:51:04:875   928   d08   Agent   ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   04:51:04:875   928   d08   Agent   *************
2014-07-22   04:51:04:875   928   1278   AU   >>## RESUMED ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
2014-07-22   04:51:04:875   928   1278   AU      # 0 updates detected
2014-07-22   04:51:04:875   928   1278   AU   #########
2014-07-22   04:51:04:875   928   1278   AU   ## END ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
2014-07-22   04:51:04:875   928   1278   AU   #############
2014-07-22   04:51:04:875   928   1278   AU   Successfully wrote event for AU health state:0
2014-07-22   04:51:04:875   928   1278   AU   Featured notifications is disabled.
2014-07-22   04:51:04:875   928   1278   AU   AU setting next detection timeout to 2014-07-22 00:38:28
2014-07-22   04:51:04:875   928   1278   AU   Successfully wrote event for AU health state:0
2014-07-22   04:51:04:875   928   1278   AU   Successfully wrote event for AU health state:0
2014-07-22   04:51:09:874   928   d08   Report   REPORT EVENT: {FE398C01-75A1-4AD8-8C43-0894FCFCE13F}   2014-07-22 04:51:04:875+0800   1
147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows
Update Client successfully detected 0 updates.
2014-07-22   04:51:09:874   928   d08   Report   REPORT EVENT: {CDA386AD-6392-4C34-859E-35307BCB5EA0}   2014-07-22 04:51:04:875+0800   1
156   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Pre-Deployment Check   Reporting
client status.
2014-07-22   04:51:09:874   928   d08   Report   CWERReporter finishing event handling. (00000000)
2014-07-22   05:05:09:109   928   d08   Report   Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22   05:05:09:109   928   d08   Report   Reporter successfully uploaded 2 events.
2014-07-22   08:38:28:883   928   1130   AU   #############
2014-07-22   08:38:28:883   928   1130   AU   ## START ## AU: Search for updates
2014-07-22   08:38:28:883   928   1130   AU   #########
2014-07-22   08:38:28:883   928   1130   AU   <<## SUBMITTED ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
2014-07-22   08:38:28:883   928   53c   Agent   *************
2014-07-22   08:38:28:883   928   53c   Agent   ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   08:38:28:883   928   53c   Agent   *********
2014-07-22   08:38:28:883   928   53c   Agent      * Online = Yes; Ignore download priority = No
2014-07-22   08:38:28:883   928   53c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22   08:38:28:883   928   53c   Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22   08:38:28:883   928   53c   Agent      * Search Scope = {Machine}
2014-07-22   08:38:29:195   928   53c   Setup   Checking for agent SelfUpdate
2014-07-22   08:38:29:195   928   53c   Setup   Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22   08:38:29:195   928   53c   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   08:38:29:195   928   53c   Misc   Microsoft signed: Yes
2014-07-22   08:38:31:804   928   53c   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   08:38:31:804   928   53c   Misc   Microsoft signed: Yes
2014-07-22   08:38:31:804   928   53c   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   08:38:31:820   928   53c   Misc   Microsoft signed: Yes
2014-07-22   08:38:31:820   928   53c   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   08:38:31:820   928   53c   Misc   Microsoft signed: Yes
2014-07-22   08:38:31:835   928   53c   Setup   Determining whether a new setup handler needs to be downloaded
2014-07-22   08:38:31:835   928   53c   Setup   SelfUpdate handler is not found. It will be downloaded
2014-07-22   08:38:31:835   928   53c   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   08:38:33:241   928   53c   Setup   Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   08:38:33:241   928   53c   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   08:38:33:272   928   53c   Setup   Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   08:38:33:272   928   53c   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   08:38:33:288   928   53c   Setup   Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   08:38:33:288   928   53c   Setup   SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22   08:38:33:991   928   53c   PT   +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22   08:38:33:991   928   53c   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   08:38:34:038   928   53c   PT   WARNING: Cached cookie has expired or new PID is available
2014-07-22   08:38:34:038   928   53c   PT   Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22   08:38:34:038   928   53c   PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22   08:38:36:616   928   53c   PT   +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22   08:38:36:616   928   53c   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   08:38:37:022   928   53c   Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22   08:38:37:022   928   53c   Agent   *********
2014-07-22   08:38:37:022   928   53c   Agent   ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   08:38:37:022   928   53c   Agent   *************
2014-07-22   08:38:37:022   928   aa8   AU   >>## RESUMED ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
2014-07-22   08:38:37:022   928   aa8   AU      # 0 updates detected
2014-07-22   08:38:37:022   928   aa8   AU   #########
2014-07-22   08:38:37:022   928   aa8   AU   ## END ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
2014-07-22   08:38:37:022   928   aa8   AU   #############
2014-07-22   08:38:37:022   928   aa8   AU   Successfully wrote event for AU health state:0
2014-07-22   08:38:37:022   928   aa8   AU   Featured notifications is disabled.
2014-07-22   08:38:37:022   928   aa8   AU   AU setting next detection timeout to 2014-07-22 04:15:53
2014-07-22   08:38:37:022   928   aa8   AU   Successfully wrote event for AU health state:0
2014-07-22   08:38:37:022   928   aa8   AU   Successfully wrote event for AU health state:0
2014-07-22   08:38:42:021   928   53c   Report   REPORT EVENT: {45B5AD35-C612-4C43-8FE0-DFC63B114FC9}   2014-07-22 08:38:37:022+0800   1
147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows
Update Client successfully detected 0 updates.
2014-07-22   08:38:42:021   928   53c   Report   REPORT EVENT: {BA606714-0153-41BA-ADC8-78520F678D97}   2014-07-22 08:38:37:022+0800   1
156   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Pre-Deployment Check   Reporting
client status.
2014-07-22   08:38:42:021   928   53c   Report   CWERReporter finishing event handling. (00000000)
2014-07-22   08:52:41:224   928   53c   Report   Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22   08:52:41:240   928   53c   Report   Reporter successfully uploaded 2 events.
2014-07-22   12:15:53:027   928   1130   AU   #############
2014-07-22   12:15:53:027   928   1130   AU   ## START ## AU: Search for updates
2014-07-22   12:15:53:027   928   1130   AU   #########
2014-07-22   12:15:53:027   928   1130   AU   <<## SUBMITTED ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
2014-07-22   12:15:53:043   928   a58   Agent   *************
2014-07-22   12:15:53:043   928   a58   Agent   ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   12:15:53:043   928   a58   Agent   *********
2014-07-22   12:15:53:043   928   a58   Agent      * Online = Yes; Ignore download priority = No
2014-07-22   12:15:53:043   928   a58   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22   12:15:53:043   928   a58   Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22   12:15:53:043   928   a58   Agent      * Search Scope = {Machine}
2014-07-22   12:15:53:308   928   a58   Setup   Checking for agent SelfUpdate
2014-07-22   12:15:53:308   928   a58   Setup   Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22   12:15:53:308   928   a58   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   12:15:53:324   928   a58   Misc   Microsoft signed: Yes
2014-07-22   12:15:55:901   928   a58   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   12:15:55:901   928   a58   Misc   Microsoft signed: Yes
2014-07-22   12:15:55:901   928   a58   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   12:15:55:917   928   a58   Misc   Microsoft signed: Yes
2014-07-22   12:15:55:917   928   a58   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   12:15:55:917   928   a58   Misc   Microsoft signed: Yes
2014-07-22   12:15:55:933   928   a58   Setup   Determining whether a new setup handler needs to be downloaded
2014-07-22   12:15:55:933   928   a58   Setup   SelfUpdate handler is not found. It will be downloaded
2014-07-22   12:15:55:933   928   a58   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   12:15:57:167   928   a58   Setup   Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   12:15:57:167   928   a58   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   12:15:57:167   928   a58   Setup   Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   12:15:57:167   928   a58   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   12:15:57:198   928   a58   Setup   Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   12:15:57:198   928   a58   Setup   SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22   12:15:57:917   928   a58   PT   +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22   12:15:57:917   928   a58   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   12:15:57:963   928   a58   PT   WARNING: Cached cookie has expired or new PID is available
2014-07-22   12:15:57:963   928   a58   PT   Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22   12:15:57:963   928   a58   PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22   12:16:00:572   928   a58   PT   +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22   12:16:00:572   928   a58   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   12:16:00:932   928   a58   Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22   12:16:00:932   928   a58   Agent   *********
2014-07-22   12:16:00:932   928   a58   Agent   ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   12:16:00:932   928   a58   Agent   *************
2014-07-22   12:16:00:932   928   1120   AU   >>## RESUMED ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
2014-07-22   12:16:00:932   928   1120   AU      # 0 updates detected
2014-07-22   12:16:00:932   928   1120   AU   #########
2014-07-22   12:16:00:932   928   1120   AU   ## END ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
2014-07-22   12:16:00:932   928   1120   AU   #############
2014-07-22   12:16:00:932   928   1120   AU   Successfully wrote event for AU health state:0
2014-07-22   12:16:00:932   928   1120   AU   Featured notifications is disabled.
2014-07-22   12:16:00:932   928   1120   AU   AU setting next detection timeout to 2014-07-22 08:15:22
2014-07-22   12:16:00:932   928   1120   AU   Successfully wrote event for AU health state:0
2014-07-22   12:16:00:932   928   1120   AU   Successfully wrote event for AU health state:0
2014-07-22   12:16:05:931   928   a58   Report   REPORT EVENT: {25E75367-1205-4F59-A812-02DA28BB3234}   2014-07-22 12:16:00:932+0800   1
147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows
Update Client successfully detected 0 updates.
2014-07-22   12:16:05:931   928   a58   Report   REPORT EVENT: {FE1434F8-C6AF-4F87-B3DF-6E4D6C4B05FB}   2014-07-22 12:16:00:932+0800   1
156   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Pre-Deployment Check   Reporting
client status.
2014-07-22   12:16:05:931   928   a58   Report   CWERReporter finishing event handling. (00000000)
2014-07-22   12:30:05:116   928   a58   Report   Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
2014-07-22   12:30:05:131   928   a58   Report   Reporter successfully uploaded 2 events.
2014-07-22   14:05:29:584   928   10a0   AU   Triggering AU detection through DetectNow API
2014-07-22   14:05:29:584   928   10a0   AU   Triggering Online detection (interactive)
2014-07-22   14:05:29:584   928   1130   AU   #############
2014-07-22   14:05:29:584   928   1130   AU   ## START ## AU: Search for updates
2014-07-22   14:05:29:584   928   1130   AU   #########
2014-07-22   14:05:29:584   928   1130   AU   <<## SUBMITTED ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
2014-07-22   14:05:29:584   928   8e0   Agent   *************
2014-07-22   14:05:29:584   928   8e0   Agent   ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   14:05:29:584   928   8e0   Agent   *********
2014-07-22   14:05:29:584   928   8e0   Agent      * Online = Yes; Ignore download priority = No
2014-07-22   14:05:29:584   928   8e0   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-22   14:05:29:584   928   8e0   Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-22   14:05:29:584   928   8e0   Agent      * Search Scope = {Machine}
2014-07-22   14:05:29:584   928   8e0   Setup   Checking for agent SelfUpdate
2014-07-22   14:05:29:584   928   8e0   Setup   Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-22   14:05:29:584   928   8e0   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   14:05:29:600   928   8e0   Misc   Microsoft signed: Yes
2014-07-22   14:05:29:616   928   8e0   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-22   14:05:29:631   928   8e0   Misc   Microsoft signed: Yes
2014-07-22   14:05:29:631   928   8e0   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   14:05:29:631   928   8e0   Misc   Microsoft signed: Yes
2014-07-22   14:05:29:647   928   8e0   Misc   Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-22   14:05:29:662   928   8e0   Misc   Microsoft signed: Yes
2014-07-22   14:05:29:662   928   8e0   Setup   Determining whether a new setup handler needs to be downloaded
2014-07-22   14:05:29:662   928   8e0   Setup   SelfUpdate handler is not found. It will be downloaded
2014-07-22   14:05:29:662   928   8e0   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   14:05:29:662   928   8e0   Setup   Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   14:05:29:662   928   8e0   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   14:05:29:694   928   8e0   Setup   Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   14:05:29:694   928   8e0   Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-07-22   14:05:29:709   928   8e0   Setup   Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-07-22   14:05:29:725   928   8e0   Setup   SelfUpdate check completed. SelfUpdate is NOT required.
2014-07-22   14:05:30:037   928   8e0   PT   +++++++++++ PT: Synchronizing server updates +++++++++++
2014-07-22   14:05:30:037   928   8e0   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   14:05:30:053   928   8e0   PT   WARNING: Cached cookie has expired or new PID is available
2014-07-22   14:05:30:053   928   8e0   PT   Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
2014-07-22   14:05:30:053   928   8e0   PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
2014-07-22   14:05:35:630   928   8e0   PT   +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-07-22   14:05:35:630   928   8e0   PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
2014-07-22   14:05:36:411   928   8e0   Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
2014-07-22   14:05:36:411   928   8e0   Agent   *********
2014-07-22   14:05:36:411   928   8e0   Agent   ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-22   14:05:36:411   928   8e0   Agent   *************
2014-07-22   14:05:36:411   928   1360   AU   >>## RESUMED ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
2014-07-22   14:05:36:411   928   1360   AU      # 0 updates detected
2014-07-22   14:05:36:411   928   1360   AU   #########
2014-07-22   14:05:36:411   928   1360   AU   ## END ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
2014-07-22   14:05:36:411   928   1360   AU   #############
2014-07-22   14:05:36:411   928   1360   AU   Successfully wrote event for AU health state:0
2014-07-22   14:05:36:411   928   1360   AU   Featured notifications is disabled.
2014-07-22   14:05:36:411   928   1360   AU   AU setting next detection timeout to 2014-07-22 10:01:01
2014-07-22   14:05:36:411   928   1360   AU   Successfully wrote event for AU health state:0
2014-07-22   14:05:36:411   928   1360   AU   Successfully wrote event for AU health state:0
2014-07-22   14:05:41:410   928   8e0   Report   REPORT EVENT: {6A2B180E-A95F-42F7-B775-5750DFFD6ECD}   2014-07-22 14:05:36:411+0800   1
147   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Software Synchronization   Windows
Update Client successfully detected 0 updates.
2014-07-22   14:05:41:410   928   8e0   Report   REPORT EVENT: {83041427-693D-4A42-AED0-E8E7BFB8E7E3}   2014-07-22 14:05:36:411+0800   1
156   101   {00000000-0000-0000-0000-000000000000}   0   0   AutomaticUpdates   Success   Pre-Deployment Check   Reporting
client status.
2014-07-22   14:05:41:410   928   8e0   Report   CWERReporter finishing event handling. (00000000)

No Service Pack 1 installed. Does this mean that no updates will be detected if SP1 is not installed? thanks
That's exactly what that means!
Updates have not been available for Windows Server 2008 R2 *RTM* systems since April, 2013.
http://support.microsoft.com/lifecycle/?p1=14134
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Antimalware Overall Status and History - Report

Good morning,
I have setup a subscription to the default report in SCCM named "Antimalware Overall Status and History". When the report is sent out it sends a nice pie chart with categories underneath it. The categories are the following :-
- Protected
- At Risk
- Not yet Installed
- Client Not Supported
- Inactive
- Configuration Manager Client Not Installed
The report works great and it adds all of our clients in to the correct category. However my question is - How does SCCM determine which category clients are added to. Are there certain requirements that a client must meet before it is added to the "Protected"
category.
Also is it possible to edit the settings for these categories?
Regards,

Hi,
Since it is related to SCCM, I recommend you to ask in the forum below for professional assistance:
http://social.technet.microsoft.com/Forums/en-US/home?forum=configmanagergeneral
I am really sorry that I moved it to this forum by mistake. Sorry for the inconvenience.
Best regards,
Susie

How the sales order header status update?

Hello,
In the sales order header "STATUS" tab is there, under this status tab we can find OBJECT status if we click that object status it shows the Object number,Object category,status profile and status with status no. on which bases this status will update in the sales order header?
my case is Status "10-xxxx" set automatically for some orders.
Could you plz let me know on which bases, the status will be updated in the sales order?
Regards|KS

Hi
SAPu2019S GENERAL STATUS MANAGEMENT FUNCTIONALITY
General Status Management replaced order status management functionality in recent SAP releases (4.6C). This discussion will address general status management, as this is how SAP allows user statuses for controlling objects in this and future releases.
General Status Management applies to internal orders, project definitions, WBS elements, production orders and many other objects in SAP. For the purposes of this discussion we will concentrate on status management for internal orders and WBS elements. A list of all objects relevant for status management will be made available upon request.
A status is an indicator that fulfills two functions. First, it informs you that a particular status has been reached. For example, an internal order has been created and released; a settlement rule has been entered; a particular business transaction has been executed, etc. Second, it influences the business transactions you can perform for a particular status. A status can allow a business transaction; allow a business transaction but issue a warning message; or prohibit a business transaction altogether. If a warning message is issued it is up to the user whether the business transaction is carried out or not.
Statuses can be used to control and communicate. Statuses can be used in reporting (show me a report of all internal orders with a status of TECO, or technically complete). Statuses can be used as selection criteria (select all internal orders with a status of CLSD, or closed). Statuses can communicate the state of an object (ready for archiving, not ready for settlement execution).
There are SAP standard delivered statuses that apply to all object types. These are known as SYSTEM STATUSES. CRTD, REL, SETC, TECO are examples of SAP standard system statuses. SAP standard system statuses cannot be removed from use. You cannot override the SAP system status with a user status. You cannot change the behavior of an SAP system status.
User statuses (or user defined statuses) exist in addition to SAP standard statuses. User statuses are intended to augment or refine SAP standard statuses, not replace them. There is no limitation to the number of user statuses that can be created. Both system and user statuses influence business transactions in the same way.
An object can have multiple statuses active at the same time. A plant maintenance order can have released, preliminarily costed, work order printed and confirmed statuses all at the same time. For SAP display purposes only one status can be displayed on the status line in master data screens, but it is possible to see all active statuses for an object at one time by drilling down into the master data screens.
A STATUS PROFILE, or user status profile, contains individual user statuses and the business transaction rules defined for those statuses. There is no limit to the number of user status profiles that can be maintained in SAP. A user status profile is assigned to an order type or a project profile in configuration. This user status profile is then defaulted into all objects that reference that order type or project profile. A users status profile can be overwritten (or deleted) in an individual object (via native master data screens), but only if a user status has yet to be activated for that particular object. Once a user status has been activated for that object the user status profile cannot be changed.
HOW STATUS MANAGEMENT WORKS
When an object (internal order, WBS element, production order) is created SAP assigns the system status CRTD. MIT automatically releases the order, so the system status REL is also activated. If there is a user status profile defined in the order type (or project profile) this is carried over into the internal order (or WBS element). If not, only the SAP system statuses will apply to this object.
When a user executes a business transaction for this object, SAP checks the user status to see if that business transaction can be executed without any additional influence from a user status, can be executed but with a warning message being issued, or cannot be executed at all. SAP also checks whether the business transaction sets or deletes any other user statuses within the user status profile.
A user status may also be maintained directly in the object master data. Accessing the master data screens allows a user to manually maintain user statuses. If necessary, an authorization code can be assigned to a user status to ensure that no unauthorized persons can change the status of an object. Once changed, the new user status is fully active and acts no differently than if a business transaction set the user status.
Status management and business transaction control only work with standard SAP transactions. Z transactions will not show up on the business transaction list for an object. The business transaction table is configurable, but SAP strongly recommends not changing that table. SAP directly updates that table via support packs and it is often impacted during upgrades.
Authorization codes / keys are available in user statuses. The authorization code is checked only when user statuses are being set manually, from within the objectu2019s master data screens. This ensures the user has the proper authorization to set that status for that particular object. However, it is important to understand that SAP sets a user status in reaction to a business transaction it does not perform an authorization check.

STPPOD - DELVRY03 -GR Status Update in SNC

When we create an ASN in SNC with single material, mutiple line items corresponding to different PO's with a specific delivery date and when we post GR in ECC against this ASN and to send POD status update to SNC when RSMIPROACT batch job is run - We are noticing GR status update is happeing for the material in one line item with one PO but the other line item for the same material with different PO is not getting status update.
when we checked the ECC - DELVRY03 -Idocs they are getting generated only for single line item of ASN not for other line item.
Note : This scenario is with ASN with multiple line items here the Material is only one - Each line item has same material but different PO and whole of ASN would be with specific delivery date.
Can any one pls let me know if an ASN with multiple line items ( for single material) when GR is posted and when we send the GR status info (POD) to SNC thru Batch job - how it works.
I have checked PO history for the 2 PO's of same material - it is getting updated correctly.
Would appreciate your immediate help.
Regards,
Mahesh

Hi Mahesh
I have created an ASN for the same material with specific delivery date, with mulitiple line items belonging to different PO.
I have posted a STPPOD idoc from ECC against the inbound delivery using VL32N.(Goods Reciept against inbound delivery)
It is posting to all the PO's and all are updated properly
Also can you check whether you DELVRY03 idoc has E1EDL24(Delivery Item) as many as your ASN line items????
Like if you three line items in ASN, then there should be three E1EDL24 segments carrying the info..
Best Regards
Vinod
Edited by: Vinod Kumar Pedapati on Sep 16, 2010 11:35 AM

Sysprep removes Windows Update History -- good or bad?

My Windows 7 SP1 reference image was not showing IE 9 as an optional update to install. IE9 was not blocked by any Group Policy and I should have had all the prerequisites installed as there was nothing left to install in Windows Update (before today's
Patch Tuesday updates, that is...)
So I rolled back my reference image from 6 months ago and everything showed correctly and updated properly through Windows Update. I then sysprepped that system again and let it come up normally.
But in doing this, I noticed that the Windows Update history -- was blanked out after the system came back up Is this expected when running sysprep?
If so, is it *possible* that IE9 was not visible as an update to be installed in Windows Update because it couldn't see the prerequisites in the Windows Update history?
Or am I reading too much into sysprep blanking the windows update history here?

Hi,
Based on my research, I found that the Windows update history data which stored in %windir%softwaredistribution would be deleted when after running sysprep.
So the Windows Update do not display the update history. But it still do not flag the updates which are already installed as available if you click “Check updates online” button.
Also, I need to advise that the IE 9 is an important update rather than the optional. Just have not been selected in the list of important category by default.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact
[email protected]
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Downloading images used to go automatically to the last folder used to save images, even when reopening Firefox. In just the past few days, possibly coinciding wih the most recent updates, the folder defaults to the 'Downloads' folder. This is most annoyi

Downloading images used to go automatically to the last folder used to save images, even when reopening Firefox. In just the past few days, possibly coinciding wih the most recent updates, the folder defaults to the 'Downloads' folder. This is most annoying. What happened? Internet Explorer 8.0 did the same thing. This was one of the reasons why I started using Firefox to download all images. I went into Tools>Options and it only lets me set another folder. I dont want to set a specific folder I want it to always go to the last folder used. So what gives?
== This happened ==
Every time Firefox opened
== possibly when the most recent updates were installed, a few days ago

Thanks jscher 2000. I guess I didn't make it clear. "It restarts with all the addons activated, and resumes with the tabs that were open before closing it." IE, it's running fine now with all the extensions activated. Everything is OK now.
So something in the Firefox code was causing the bad behavior. It's not essential that I find out what the problem was - I'm just curious. And if anybody else has this same problem, it might be nice to have it corrected at the source.

Status update for MeeGo on the N900

Here's a copy of the text sent by Harri Hakulinen from Nokia. He is the project lead for MeeGo on the N900. This message was sent to the MeeGo developer mailing list just now:
Hello MeeGos !
This is brief status update of "MeeGo to N900" project. This project is currently running as Nokia project, and I am Nokia project lead for it. The current closed mode of development is not the target for us at all, but rather transitional condition. As already discussed by Valtteri in TSG meeting, we are looking into going more open mode shortly. One reason why we have done this on this way is that at the same time we have been trying to handle opening of many currenly closed components that are needed in MeeGo and to build feasible MeeGo images for N900.
However, a lot of related work is already done completely open, you can find more info from places like ofono.org, connman.net and meego.gitorious.org . So if you are eager to contribute or want to closely follow whats happening, please work on those.
As you know, we have delivered working MeeGo images for N900 as part of first code drop in the end of March. At that state we were using older kernel version on N900 than on Atom side, as we used the same kernel (.28) than what is used in Maemo 5 based products today. We ended up doing that simply because lack of time to contribute and port all the drivers to the newer kernels.
Now, for the upcoming May release of MeeGo, we are going to use the same kernel version (.33) than Atom based devices are using. For that we need to submit number of ARM-architecture patches to MeeGo as well, because many of the required ones have just been contibuted upstream kernel and were not available in .33 version originally.
We have already enabled most of the main drivers, like LCD, GFX, Wlan and BT. Still, there is a lot to do in order to enable .33 on N900, like audio drivers, and modem subsystem including SSI buss driver, modem data and audio drivers etc. Our adaptation guys are in fact contributing those modem subsystem related drivers as we speak, and if you are following kernel mailing lists you can see how that goes on.
Besides of enabling the new kernel, we are working with number of smaller and bigger issues for N900. Starting from the beginning, we are now based on ARMv7 combiled code, so the code should be better optimised for N900 now. ARMv5 compilation that was in use for code drop will still be there, and it also seems to be used at least by community project that is planning to release MeeGo for good old N810 tablets
Also, we are planning to enable dual booting of Maemo 5 and MeeGo for the upcoming release. So that will be offered as 3rd way to setup MeeGo to N900, including the existing "native" MeeGo only on N900 and chroot based MeeGo on Maemo 5 setups. Taking the dual boot mode into use likely includes upgrade to Maemo5 kernel as well, but that should not be big issue in the process of enabling that.
As I don't want to go ahead of others working on MeeGo architecture and other issues I will stop now, but I will report again when we have more to tell about the subject.
Br,
// Harri

Here's another update..
It seems that MeeGo on the N900 is not directly being driven by Nokia! It's an open project.. so the net result is MeeGo on the N900 may look and feel very different to Meego on the N900's sucessor
Either way, I'm certainly greatful for their efforts!
Hello Meego's,
As indicated in my previous mail about "MeeGo for N900" status, we were planning to open up our MeeGo work around N900. Now I am happy to announce, that we are there
First, to make it absolute clear for everybody: This is about open MeeGo adaptation to N900 device.
Like any other MeeGo project, it is open source project for all applicaple purposes, and does NOT directly have links to any potential Nokia product or potential product plans. So, based on this or any other of my posts, please do NOT start or continue speculation of upcoming Nokia MeeGo releases. That is practically not helpfull, and mostly only takes our time when we need to explain our words and actions in detail to various directions.
From our part, we are trying to implement the open development model that has been discussed now so many times around MeeGo. On practical terms, we are trying to work based on proposal by Carsten Munk, see
http://wiki.meego.com/Proposal_for_Best_Practices_for_working_in_a_MeeGo_team
We have already created some resources that will be used by the team, you can learn about those and the upcoming ones from http://wiki.meego.com/ARM/N900. We have IRC channel for realtime discussion, we will use meego-dev mailing list for normal discussions and announcements, and we will have Gitorius project for code.
We will evolve our practicies during the work, so if you are interested, stay tuned to those channels. I belive that soon we are also able to figure out, what is best way for community members to help us in development, and then effectively be part of the team.
I would also like to use this as opportunity to introduce the team behind this work (so far) and also thank them about their hard work and long hours. We have team that consist of some Nokia subcontractors and also growing team of Nokia personel:
"MeeGo for N900" team (so far)
- Cybercom Turku team; Marko Saukko, Jouni Peltonen, Sami Sirkiä, Jari Smura and Luka Milovanov.
- Cybercom Tampere team; Kalle Lampila,Teemu Tuominen,Tuukka Mäkinen and Ville Marjusaari.
- Carsten Munk via Nomovok
- Jarkko Nikula via Atomide
- Jan-Simon Möller from Linuxfoundation
- Nokia team; Alexander Kanevskiy, Felipe Contreras, Markus Lehtonen, Ameya Palande, Sakari Poussa, Roger Quadros and me.
In addition to official project team, many Nokia people have helped us despite their hectic daily work, even with their free time. Most of them are driven by the desire to open, repurpose and upstream all relevant sw that has been originally created for Maemo 5 based N900 product during previous years.
Marko, Jouni, Sami & Luka and Markus were working with me already on last year when we did prototypes and interoperability tests of Maemo & Moblin stuff combined in different ways. Based on those we had pretty good picture of what we are doing and why.
And of course, we have had very good and productive co-operation with various Intel teams since those times. Anas Nashif and many others from Intel's MeeGo team have done a lot for us by enabling ARM stuff in MeeGo OBS and repositories.
Last but not least, I want to give special thanks to Stskeeps (alias Carsten Munk . He has teached us how to operate on open, and he has also done respectable amount of this work since early days of Meego. In addition to that, I belive that his earlier work on Maemo community and on Mer project has in fact inspired all of us and shown a way to MeeGo alredy years ago.
Br,
//Harri

Unable to run bapis for project status update and date update together

Hi Experts,
I have a requirement to update the dates and status of a project WBS at level 4. I am trying to do update the CJ02 Transaction using standard BAPI available. I need to do both Date update and status update in the same LOOP PASS   i am using the below mention bapi. when i am doing so i am getting an error Project 'A._____' has been currently processed by ID i.e. my id.
I have tried putting a wait for 2 seconds in the code but its still not working. please find the order below in which i am calling the bapi.
Loop at itab.
if date_changed = 'X'.
      CALL FUNCTION 'BAPI_PROJECT_MAINTAIN'
      READ TABLE it_error WITH KEY message_type = c_e.
      IF sy-subrc <> 0.
Commit
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
             EXPORTING
                  wait   = c_x
             IMPORTING
                  return = s_ret.
   endif.
endif.
if Status_change = 'X'.
      CALL FUNCTION 'BAPI_PS_INITIALIZATION' .
      CALL FUNCTION 'BAPI_BUS2054_SET_STATUS'
      READ TABLE t_result WITH KEY message_type = c_e.
      IF sy-subrc NE 0.
        CALL FUNCTION 'BAPI_PS_PRECOMMIT'
             TABLES
                  et_return = t_ret.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
             EXPORTING
                  wait   = c_x
             IMPORTING
                  return = s_ret.
     ENDIF.
endif.
    WAIT UP TO 4 SECONDS.
endloop.

Try to use
SET UPDATE TASK LOCAL.
before each BAPI call.
Did you try to debug through your code, leaving sufficient time between BAPI calls? If it does work like that, then the above statement might help.

Delivery status update in sales document at PGI

Normally system updates the delivery status of sales document line level, when a delivery document is created with respect to that sales document line.
But I want system to update the delivery status (in sales doc. line) when PGI is done for respective delivery document; not at the creation of delivery document. Below I have shown the status updating scenarios that I expect.
Scenario 1
Sales doc line qty: 100 PCs
Delivery Doc qty: 50 PCs
PGI: Not done
Status in Sales document line should be A (Open)
Scenario 2
Sales doc line qty: 100 PCs
Delivery Doc qty: 50 PCs
PGI: 50 PCs
Status in Sales document line should be B (Partially delivered)
Scenario 3
Sales doc line qty: 100 PCs
Delivery Doc qty: 100 PCs
PGI: 100 PCs
Status in Sales document line should be C (Fully delivered)
Can anyone propose a possible way of doing this (configuration/ user exits/ BADI etc,)?
Thanks,
Ramindu

Hi,
I dont know it with the use of ABAP development, but by functional logic, can suggest you to configure the rush order sales configuration for your particular sales order.
just check that availability of that particualar sales order is met or not prior to it.
and then automatically when your delivery doc is created, PGI would be done and the status of your sales order would be updated with it.
try it out on your development client, if it works out.
regards,
Siddharth.

HT4314 hello i have an ipod touch 4 5.1.1 and i can't post status updates or have a profil picture what is the problem and my sister has it and we have the same itunes account in game center

hello i have an ipod touch 4 5.1.1 and i can't post status updates or have a profil picture what is the problem and my sister has it and we have the same itunes account in game center

And the answer is:
williamfromlongueuil wrote:
we have the same itunes account in game center
You need to have your own account... DUH....

How can I see my software update history?

Hi guys I just wonder how can I see my system software update history?
on Lion we can see in Preferences/Sofware Updates/History but Mountain Lion we dont see to same place?

go to applications - utlilities - system information.app - software - installations
this may help you

Status Update of Service Order From Billing Document

Dear Experts,
I am told to change the User status of Service Order once the Billing Document is Generated.
Here we are in CRM 2007 and i have done the status update of previous document but here
Billing document is not possible to read through CRM_ORDER_READ (function module).
Do any one have any idea how do i proceed.
Thanks,
SA

hi sa
to change the service order user status , when biling document is generated
make an implementation of bill_acc_if bai and in the method ENRICH_ACC_DOCUMENT
read order data using crm_order_read and change the status using
CRM_STATUS_CHANGE_EXTERN
thnks
sam

Can´t access my files on Creative Cloud. "Page temporarily unavailable. We will return soon." "We are working quickly to resolve the problem and apologize for the delay. Check back later or visit our website for status updates. In addition, you can get he

Hello,
For a few days I have been trying to access my files on Creative Cloud web without success. I´ve got this message only:
"Page temporarily unavailable. We will return soon."
"We are working quickly to resolve the problem and apologize for the delay.
Check back later or visit our website for status updates.
In addition, you can get help in the forums of the Creative Cloud.
Thank you for understanding!"
(I used Google Translate)
Somebody help?

You do not need ?&promoid=KRUVP at the end of the url but it should not matter.
One thing to check is if your hosts file is modified. Open the Command Prompt and type: notepad %systemroot%\system32\drivers\etc\hosts
This will open a read-only copy of your host file in Notepad. Are there any entries in this file regarding adobe.com?
The other thing you can do is open the Developer Tools in the Chrome browser. On Windows press Ctrl + Shift to open them. Switch to the Network tab. Reload the page by pressing Ctrl + r. Check for any 4xx or 5xx errors which should be colored red.
Post screenshots of your results or send me a private forum message with the information.

Status updates history period default

Similar Messages

Maybe you are looking for