Support Pack Status not updated in System Component Information

Hi Experts,
We have installed ECC 6.0 with Ehp3 and AFS 603 on AIX 6.1 and db6 V 9.1. We recently added the Vistex Incentive and Payback Module and Vistex Global Functions Add Ons. After the base install the Support pack 1-4 were applied for both Vistex components. For IRMGLB the status screen (System/Status) shows the SP highest Level = 03, while in SPAM screen it shows that Support Pack for for the Component IRMGLB is imported successfully.Because of this we can not apply the remaining Support Packs. For the other component (IRMIPM) Support Pack level 04 is correctly displayed.
Any idea what are we missing? Any help is greatly appreciated.
Thanks
Suhail

For future referers, Vistex says its a known issue.
Hello,
It is a known issue but it would not impact any of the functionality.
It can only be fixed in the subsequent release with conjunction with
SAP.
Thanks,
Vistex Support

Similar Messages

Standard process practice to apply Support pack in 3 tier Landscape system.

Dear All,
I know how to apply the support pack in SAP system, but I am interesting to know the standard process practice to apply Support pack in 3 tier Landscape system. For e.g we have development server -
 QA -
 PRD
What is the process to apply support pack in above mention landscape system.
I would like to request all expert help me understand this.
Thanks in advance
Dinesh M
Edited by: dineshdm marotkar on May 13, 2008 12:28 PM

Hi,
If you have only one common transport directory then you have to uncar the files only once.
Uncar should be done once per transport directory.
Before performing the import of support packages if you have done any changes to standard sap programsthen you have to lock them in the reqests and while importing the support packages u have to perofrm spau and spdd adjustments any ways sap will allow you this prior to abap screen generation.
First you have apply the patches on test and then qa and then prd. Make sure you have recent spam/saint update installed.
Also perofrm a kernal upgrade after updating the spam/saint.
Perform a full and tlog backup before importing support pacakges.Because sap does not support uninstalling of support packages.
Regards,
Vamshi.

Pre-requisites for Support Packs in BI 7.0 System

Hello Everyone,
We are planning on applying support packs to our BI 7.0 system where we currently are at SP13 and we are not applying any support packs in ECC 6.0 system.
The question is,
Do we have to clear out the delta queues in ECC system before we can apply the support packs in BW system.
We will clear out the RSA7 in BW system.
So, the concern is do we need to have downtime in ECC if so....would it have to be through out the support pack process in BI system.
Please let me know would data be corrupted in ECC if we do not clear out the delta queues.
Because technically, we are not applying any changes in ECC system. All the support pack activities will be performed in BI environment and the RSA7 within BI will be taken care of. So, am not sure why would we have to clear out the delta queues in ECC when applying support packs in BI system which does not change anything on ECC side.
Any input would be appreciated.
Thanks
Dharma.

I am not sure about first two questions that you have asked.
Whenever you applying support packages in your BI system, no trasaction code should be executed. otherwise you would short dumps in your BI system.
you should lock all the userids before you go for upgrade. And no need of downtime in ECC but you should not do any load extraction from R/3.
Morever best thing is upgrading ECC as well. it is better to have both systems upgraded and in same level.
Hope my reply would help you in some extent.

Listing system component information

I'd like to be able to get (and then display) the system component information in my .NET program using the .NET connector.
(The information contained within System->Status...->Component Information)
Any idea on how to get this info?
(More generally, I find that I often run into the problem of "how do I do xyz"-- and I wonder if there is an RFC to do this somewhere-- and then I spend forever looking for one, sometimes finding what I'm looking for and sometimes not. Is there a "recommended" way of "finding stuff"?)

Hello Tom,
the fm is also available in our 4.6C system. Could you provide some more informations regarding your release.
Think that the rfc is part of the solution manager installation (as the development class is named "Solution manager").
I didn't find another rfc delivering the data. There are only some function modules (w/o rfc flag). Perhaps you can have a look at these fm's (starting with OCS* or SPAM*, e.g. SPAM_READ_PAT03). If one of these delivers the required data, you can modify the fm by setting the rfc flag, or copy it.
Nevertheless, it should be no problem to develop an own rfc, providing the information from database tables UVERS and PAT03.
Best regards
Stephan
Edited by: Stephan Theis on Feb 26, 2008 8:35 AM

CRM line item status not updated when delivery is deleted in ECC

Hi All,
When order is created in CRM it gets replicated to ECC.When delivery is created in ECC, the System Status in CRM at the line item level is changed to completed and also Delivery completed status is created in CRm..
Now when we delete the delivery, the Delivery completed status is deleted in CRM but the Completed status is not changed to In Process.It remains as Completed.This used to work fine before we applied support packs last weekend.We are currently at support pack level 10 for CRM.
Please advice
Thanks and Regards

In CRM4 standard, changes to orders in R/3 or ECC do not replicate back to CRM
Check out this SAPnote
https://service.sap.com/sap/support/notes/710874

Final Settlement for Extended Rebate - agreement status not updated

Hi,
When doing final settlement via the Extended rebate, a CM is generated, but the status of the agreement is not updated to D. Any configurations needed or steps to be done? I thought it should be automatically updated by the system..
Thanks,

Hello
Refer following links with SAP Note for reference/understanding:
- The sales volume for Rebate agreement is not current
- Sales volume not current in Rebates
- 456458 - FAQ: How does SDBONT06 work
Thanks & Regards
JP

DLV status not updated in Process order

Hi guys,
I did GR and got goods receipt documents but system is not updating DLV status in process order.
Actually i have by-product and co-products as components in order. I did posting of by-product from Confirmation screen COR6N and for co-products i did MB31 and goods movement doc. get generated. Qty. is also updated in order but NOT the dlv status.
Pl.suggest

Dear,
This is System status and you cannnot maintain it manually once that Business Transaction(FULL Delivery) happens System will automatically sets that status.
DLV status updated once Del completed tick is activated in order header, This tick will get uodated once you do GR for complete qty.
You need to Final confirm (CNF) the Order to get the DLV Status.
Or if the Delivery completed indicator is set in the Process Order, then also th System status will be DLV.
If you want to make it manually then goto co02, enter the order, goto goods receipt tab page and activate delivery completed tick and save...DLV is activated in the head as status.
Please check in BS22-I0012
Regards,
R.Brahmankar

SPD 2013 WorkFlow Status Column: Status Not Updated

We are having an issue with the status display of the SPD Designer Workflow status column which is a read only column added by SharePoint to show the status of the workflow. We have some SharePoint 2013 Workflows built using SharePoint Designer that are
attached to specific SharePoint Document Libraries. The expected behavior is for this column to show the workflow statuses (Not Started, Starting Workflow, In Progress and Completed.
Based on our observation this status is showing up although the column does get added for the Workflow that we have. Is there any other dependency for SPD Workflows that are attached to Document Libraries to show the status correctly? Any other settings/configurations
to be made?
Regards,
Vikram
Blog: http://dotnetupdate.blogspot.com |

Hi Venkadesh,
It is by design that 2013 workflow will show stage name in the workflow status column when
Automatically update the workflow status to the current stage name is checked.
And the workflow status column will be blank when Automatically update the workflow status to the current stage name is unchecked.
For existing workflows, the workflow status will still exists with the previous values after unchecking Automatically update the workflow status to the current stage name.
We can use Set Workflow Status action to update the workflow status value based on our needs.
Best regards,
Victoria
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Layout Status not updated following upgrade of RH5 project to RH7

I have over thirty RH5 projects to upgrade to RH7 with two
layouts for each: Microsoft HTML Help (Primary Layout) &
Printed Documentation.
While upgrading the first project I noticed that running the
File > Batch Generate... option following the upgrade does not
update the layout Status to "Generated". I found out that the
layout files are actually updated but the Status still shows as
"Out of date".
Running File > View Primary Layout (after running the
Batch Generate) displays the message, "Microsoft HTML Help output
is out of date. Would you like to compile before running?" with
Yes, No and Cancel options. Clicking the Yes button generates the
Primary Layout again, but this does not update the layout Status to
"Generated" either.
For the status of your layouts to be updated you must close
your upgraded project, reopen it & generate the layouts again.
I have spent much of this afternoon confirming the above
information, I hope that this posting saves you some time that
might be spent wondering why your layout status is not
updating.

You may need to stop all processes of the shadow instance that are running with the old limitations. I'd try the following:
ps -ef | grep sapstart
then kill the process of the shadow instance (check for the system number of the shadow instance to identify).
I'd also try to stop the instance first so all shared memory segments are cleared - and then try to manually start it:
cd <upgrade-directory/bin
./SAPup stopshd
./SAPup startshd
You may assign the user directly to the project but this won't be taken into account if the assignment is not set in /etc/user_attr.,
Markus

RNOTIFUPDATE01 - SAP Status not updated from Service Desk msgs

Hi Folks,
Already for some days we're facing the issue that SAP status of Solution Manager msgs that are sent to SAP is not updated in the SolMan itself.
So, if a msg is send to SAP, and SAP made an update and changed their status to 'Customer Action' or 'Solution Provided', the status in SolMan is still 'Sent to SAP'. Only at the marketplace we're able to see the real status.
The job RNOTIFUPDATE01 runs successfully every hour, no errors listed.
However when I run the job manually in SE38, i get a message like:
9999017765 012005041000000066052008 Read/Update Error
9999017765 012005041000000066052008 Locked, Entry in DNOD_UPDATE Successful
Searching for these errors in the notes, gave me some results, but unfortunately these corrections are already in our system.
Our patch level is SAPKA70015, SAPKB70015 and SAPKITL426.
I'm not 100% sure, but I think that it is related to installation number, as some msgs are updated and other aren't.
Does any of you has an idea?
Thanks a lot for your help folks!
Roel

Hello Roel,
The update of the status in the Solution Manager service desk document (usually SLFN), to match the SAP one, is managed by the method AISDK_SP_CHECK_DNO. To configure this, do as follows:
- Execute transaction SPPFC, selecting the Application DNO_NOTIF
- Open the action profile SLFN0001_STANDARD_DNO (or the one you created as a copy)
- Open the action definition SLFN0001_STANDARD_DNO_CHECK (or the one you created as a copy)
- Under "Processing Types", check if the method AISDK_SP_CHECK_DNO is set (if not, set it as the method to be called)
- Check the method parameters:
USER_STATUS1 is the status that was set BEFORE SAP answers
USER_STATUS2 is the status that will be set WHEN SAP answers (this is the one you should modify)
Save everything and test.
Please let me know if this works for you.
Best Regards,
Cristiano Canzone

Can not update my system and not able to repair disk

I havn't used my macbook pro for about a year, and recently I need to travel to another place and need it with me.
I see in AppStore that there is an update for my ios, I downloaded it, and run the install.
however, when updating my system. I run into some error, the installer says the update installation failed, and I should restart the computer and repair the disk before continue.
I tried to restart in safeboot, not working, the screen stucks at the apple logo for over half an hour.
And tried to restart with my harddrive, the system tells me I can not select that disk to restart.
I an able to run disk utility from the installer. I can verify disk permissions .
But when I run the disk verify, it gives me an error:
Verifying volume "Macintosh HD"
Checking file system
Performing live verification
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
The volume Machitosh HD could not be verified completely.
Error: This disk needs to be repaired. Click repair Disk.
But the "Repair Disk" button (and the repair permission button)is gray and can not be pressed, when put my mouse over the "repair disk" button, a line of text shows up:
"repair the structure of the disk's file system, if necessary
Not available becaue the selected disk can't be written to."
the repair permission gives me "Not available becaue the selected disk can't be written to." as well.
What do I do now?

QiaQiaC,
which model MacBook Pro do you have, and which version of OS X is installed on it?

Connector Status not updating

As a result of a dramatic failure of communication the SCSM workflow AD account was deleted and recreated, after some muching about everything in SCSM is now working normally again except the config manager and AD connectors are not updating their status.
I initially thought they were not running at all but I have confirmed that they are in fact synchronizing data from their respective sources and its just the display of the status that is not updating. I tried deleting them and recreating them and
now they display no status i.e. the start time, finish time, status, and Percentage columns are all blank.
I have done a bit of research and believe that the problem is that the relationships between the Connectors and their respective SyncStatus objects is missing/broken, and for some reason creating new Connectors either does not establish a corresponding
SyncStatus object or does but does not relate it to the connector.
I have a couple of reasons for this hypothesis first is when I run this powershell*:
$connectorDispName="Your Connector Name Here"
#Following will return in instance of Microsoft.EnterpriseManagement.ServiceManager.Sdk.Connectors.ADConnector
$myConnector=Get-SCSMConnector -DisplayName $connectorDispName
#Get the EMO object for relationship lookup
$emoConnObj=$myConnector.ConnectorObject
#Relationship id can be retrieved with following:
#Get-SCRelationship -Name 'Microsoft.SystemCenter.LinkingFramework.DataSourceHostSyncStatus'|select id
$relationshipId='1548950d-6cea-d9c1-11ec-53701fbcbbec'
#Find the matching relationship object (with the above relationshipId)
$relationshipObject=Get-SCRelationshipInstance -sourceInstance $emoConnObj|?{$_.RelationshipId -eq $relationshipId}
#$relationshipObject.TargetObject contains an EMO.
#Grab the id and use Get-SCClassInstance to return a type of Microsoft.SystemCenter.LinkingFramework.SyncStatus
$syncStatusObj=Get-SCClassInstance -Id $relationshipObject.TargetObject.Id
The following error is returned:
Get-SCClassInstance : Cannot validate argument on Parameter 'Id'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
At D:\tools\scripts\ConnectorSyncStatus.ps1:14 char:40
+ $syncStatusObj=Get-SCClassInstance -Id $relationshipObject.TargetObject.Id
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Get-SCClassInstance], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.SystemCenter.Core.Commands.GetSCClassInstanceCommand
Possibly the Powershell is incorrect but this result implies to me that the Get-SCRelationshipInstance call is returning a null value for the syncstatus object which is being fed into the Get-SCClassinstance call.
My second reason for this hypothesis is the following SQL results:
select RelationshipTypeId from dbo.RelationshipType
where dbo.relationshiptype.RelationshipTypeName = 'Microsoft.SystemCenter.LinkingFramework.DataSourceHostSyncStatus';
1548950D-6CEA-D9C1-11EC-53701FBCBBEC
select * from dbo.relationship
where RelationshipTypeId = '1548950D-6CEA-D9C1-11EC-53701FBCBBEC';
Returns no results.
This implies to me that there are no instances of the relationship linking a Connector to its corresponding SyncStatus object.
I am not an SQL or Powershell expert but I know enough to be dangerous, so does my reasoning seem correct? And if so how could I fix this?
Thanks In advance
* this Powershell is not of my own devising, I cribbed it from
Steve IAnson in this question:
Query Connector Status

Yes there is every 1 minute there is a squence of entires as follows:
Source: Lfx Service
Event: ID 3334
Data:
Error setting status for property &. Error:The relationship source specified in the discovery data item is not valid.
Relationship source ID: ae5465d3-2565-c7d3-0de2-acc994c1e928
Rule ID: eb496966-4fb7-45bd-bdda-b689af383733
Instance:
<?xml version="1.0" encoding="utf-16"?>
<RelationshipInstance TypeId="{1548950d-6cea-d9c1-11ec-53701fbcbbec}" SourceTypeId="{71f6cfcd-99b3-3a07-471d-bb9c4bf5ba76}" TargetTypeId="{2d4afd51-d2ff-92c6-266f-2b6060000dae}">
<Settings />
<SourceRole>
<Settings>
<Setting>
<Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
<Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
</Setting>
</Settings>
</SourceRole>
<TargetRole>
<Settings>
<Setting>
<Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
<Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
</Setting>
</Settings>
</TargetRole>
</RelationshipInstance>
Status data:ConnectorId:ec4a037e-e0f0-47a2-b7e7-7932eba2a0ac;
BaseManagementEntityId:e22fffb2-9b85-de47-fe3d-875914b21797;
LastRunStartTime:25/11/2014 2:00:44 AM;
LastRunFinishTime:25/11/2014 2:02:57 AM;
NextSyncTime:27/11/2014 2:00:00 AM;
Status:FinishedSuccess;
SyncPercent:100;
MaxValue:100;
MinValue:0;.
Source:OpsMgr SDK Service
Event ID: 26319
Data:
An exception was thrown while processing ProcessDiscoveryData for session ID uuid:e47c3453-2524-44af-a9d9-2475e3a204a6;id=3.
Exception message: The relationship source specified in the discovery data item is not valid.
Relationship source ID: ae5465d3-2565-c7d3-0de2-acc994c1e928
Rule ID: eb496966-4fb7-45bd-bdda-b689af383733
Instance:
<?xml version="1.0" encoding="utf-16"?>
<RelationshipInstance TypeId="{1548950d-6cea-d9c1-11ec-53701fbcbbec}" SourceTypeId="{71f6cfcd-99b3-3a07-471d-bb9c4bf5ba76}" TargetTypeId="{2d4afd51-d2ff-92c6-266f-2b6060000dae}">
<Settings />
<SourceRole>
<Settings>
<Setting>
<Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
<Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
</Setting>
</Settings>
</SourceRole>
<TargetRole>
<Settings>
<Setting>
<Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
<Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
</Setting>
</Settings>
</TargetRole>
</RelationshipInstance>
Full Exception: Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipSourceException: The relationship source specified in the discovery data item is not valid.
Relationship source ID: ae5465d3-2565-c7d3-0de2-acc994c1e928
Rule ID: eb496966-4fb7-45bd-bdda-b689af383733
Instance:
<?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{1548950d-6cea-d9c1-11ec-53701fbcbbec}" SourceTypeId="{71f6cfcd-99b3-3a07-471d-bb9c4bf5ba76}" TargetTypeId="{2d4afd51-d2ff-92c6-266f-2b6060000dae}">
<Settings />
<SourceRole>
<Settings>
<Setting>
<Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
<Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
</Setting>
</Settings>
</SourceRole>
<TargetRole>
<Settings>
<Setting>
<Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
<Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
</Setting>
</Settings>
</TargetRole>
</RelationshipInstance>
at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.BulkUpsertRelationshipInstances(DiscoveryDatabaseApi dbApi, DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData)
at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.BulkAddUpdate(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)
at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.Write(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)
at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithNoRetryUnauthorized(DiscoveryDatabaseApi dbApi, Boolean useProcessContext)
at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.ProcessIncrementalDiscoveryData(DatabaseConnection databaseConnection)
at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.Process()
at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithRetry(HandleProcessing handleProcessing, RetryPolicy retryPolicy)
at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.ProcessDiscoveryDataWithRetry(DatabaseConnection dbconnection, Guid discoverySourceId, IList`1 sdkEntityInstances, IDictionary`2 streams, IContext context)
at Microsoft.EnterpriseManagement.ServiceDataLayer.ConnectorFrameworkConfigurationService.ProcessDiscoveryData(Guid discoverySourceId, IList`1 entityInstances, IDictionary`2 streams, ObjectChangelist`1 extensions)
Source:DataAccessLayer
Event ID: 33333
Data:
Data Access Layer rejected retry on SqlError:
Request: ProcessRelationshipStagingForUpsert -- (TransactionId=732419), (DiscoverySourceId=eb496966-4fb7-45bd-bdda-b689af383733), (TimeGenerated=26/11/2014 9:31:53 PM), (PerformHealthServiceCheck=False), (HealthServiceId=), (RETURN_VALUE=1)
Class: 16
Number: 777980002
Message: The specified relationship doesn't have a valid source.

Transfer requirement status not updated after TO confirmation

Hi Experts,
I have an issue with transfer requirement which is not updated with completed status even after Transfer Order completed.
Once TO is completed, relevant TR should be updated with completed status. We have many TR in open status even they are completed.
Could you please help me out how to resolve the issue.
Regards
Gowri Sankar

Hi
You can use the Warehouse activity monitor (LL01) to select the completed TR's and select the d''delivery completed' button and this will get rid of them
I hope that this helps
Frenchy

SC Item in Transfer process active - follow on document status not updated

Hi Gurus,
    Follow on document is not updated in SRM after PO creation. Ours is classic scenario (SRM 5.5, ECC6.0) and passed thru the following steps - SC (FFT) created, document approved, sent to SoCo, purchaser assigned vendor and created PO, PO created in ECC.
In SRM SoCo screen displays message 'PO created 45xxxxxxxxxx' successfully. Checked the BE PO 45xxxxxxx that was created successfully.
Ran BBP_GET_STATUS_2 and CLEAN_REQREQ_UP jobs. jobs finished successfully. But status is not updated in SRM. RZ20/SLG1 does not have any errors.
BBP_PD shows following statuses:
     I105   Awaiting Approval         X
     I1021 Created
     I1038 Complete
     I1106 SC ordered
     I1129 Approved
     I1111 Item in Transfer process
                    The last status I1111 is still active.
Any advise are welcome. Not sure if I am missing any OSS Notes.
Regards
Viktor Paul

Hi,
1. Check in table BBP_DOCUMENT_TAB if the entry exists use CLEAN_REQREQ_UP program.
2. If entry in the table not exists then check in transaction BBP_PD if the follow on document ( PO ) Number reserved for
the SC .. then use FM BBP_PD_SC_RESUBMIT.
3. none of these use normal process execute BBP_REQREQ_TRANSFER And then use CLEAN_REQREQ_UP
Thanks,
prasad.s

OEM - Oracle Job Status Not Updated

Hi all, on the OEM I have some job scheduled for export and for backup (rman).
Normally everything is ok, but now, after installing SP1 of Windows Server 2003, I can see the job starting but never finish. In reality the job is finished and I can see it on the output file.
Seems to be that on the OEM the status of the job is not updated.
This is a Fail Safe installation of Oracle 9.02 patch set 04.
Please advise.
Cheers.
Franco

Hold on, I am sure there is some confusion going on here. The registry settings are using used if there is a problem with refreshing planning, I thought the problem relates to business rule status not being updated?
If you want to understand about processing rules in the background then you can take a look at :- http://download.oracle.com/docs/cd/E12825_01/epm.111/hp_admin/ch02s07s06.html
This may not resolve your isssue, maybe there is a communication issue somewhere.
Cheers
John
http://john-goodwin.blogspot.com/

Support Pack Status not updated in System Component Information

Similar Messages

Maybe you are looking for