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

Similar Messages

Component Status not updating since upgrade from SCCM2012 SP1 CU3 to SCCM2012 R2

Since upgrading to SCCM2012 R2 three days ago, in the Configuration Manager console when we go to Monitoring > System Status > Component Status and view the status messages for any component, there are no entries since the time of our upgrade. All
components are this way.
I've checked the logs and information is flowing through them and everything else seems to be running smoothly, but there are no updates to items in Component Status. There was only one warning in the R2 prereq checker, the ConfigMgrPrereq.log shows:
<11-08-2013 15:33:30> ERROR: Site server does not have create child permission on AD 'System Management'
<11-08-2013 15:33:30> WARN: Site server does not have delete child permission on AD 'System Management'
<11-08-2013 15:33:30> [primary site server]; Verify site server permissions to publish to Active Directory.; Warning; The site server might be unable to publish to Active Directory. The computer account for
the site server must have Full Control permissions to the System Management container in its Active Directory domain. You can ignore this warning if you have manually verified these permissions. For more information about your options to configure required
permissions, see http://go.microsoft.com/fwlink/p/?LinkId=233190.
I have confirmed via ADUC and ADSIEdit that the primary site server computer account does have full control over the System Management container.
We are running a single site server with separately hosted site database server and several remote distribution point site systems. Any help would be greatly appreciated.

Problem solved!
I was looking in the statmgr.log file and spotted an error about a bad SQL transaction. Some searching on this lead me to this Microsoft KB article: http://support.microsoft.com/KB/884123. Even though it is for SMS2003 it lead me to check the
\inboxes\statmgr.box\retry\ folder and sure enough there were ~5100 .sql files waiting. As per the instructions in the document, I stopped the SMS_EXECUTIVE service, deleted the oldest .sql file and then restarted the service. The file count in
the \Retry\ folder is dropping and status messages are flowing. I now just have to wait for the 6 days of status messages to process.
Thanks everyone for your assistance :)

Print Module templates layouts do not update on the fly

Print layouts do not update on the fly when attempting to choose between various Print Module>Template Browser> Lightroom or User templates. This occurs in all three Layout Styles. The very first layout chosen in Single Image/Contact Sheet, Picture Package, or Custom Package is the permanent 'default' and cannot be changed. The Preview will show as expected however any image stays stuck in the very first layout I chose after installing LR4 beta.
For example, I first chose Template Browser>Lightroom Templates>Maximum Size, and Layout Style>Single Image/Contact Sheet. Clicking through any other Templates (Lightroom or User defined) will alter the preview but not the layout display in the Print window. Same problem in either of the other Layout styles. I have been trying for days to rectify this, but it seems somehow more difficult than LR3. and not what I expect.
As a comparison, using the same steps in LR3 works perfectly as all print template/layouts can be changed on the fly as expected. I have no problems generating different layouts in LR3 and have been using LR print module since version 1 without this issue.
Is this a bug or are there any extra steps or workarounds I have not discovered? Any other testers seen this?

Update with more info. What am I doing wrong, if anything?
Print layouts do not update on the fly when attempting to choose between various Print Module>Template Browser> Lightroom or User templates. This is not a hang since the layouts do not change after the initial choice no matter how much time elapsed.
iMac OS 10.6.8. 8GB RAM.Processor Intel Core 2 Duo. NVIDIA GeForce 8800 GS.
The steps as follows:
1) Lightroom 3.6 & LR4Beta exist side by side.
2) LR4 Beta> Print Module;
3) From filmstrip choose image;
4) Template Browser> Lightroom4Beta Templates>Maximum Size;
5) Preview displays as expected;
6) Layout Styles>Single Image/Contact Sheets
7) Template Browser> Lightroom4Beta Templates>click through any other templates (Lightroom or User defined);
8) Image layout in main window does not update;
9) Previews update;
10) Layout Style>Picture Package;
11) Template Browser>Maximum size is then automatically shown, however the template in the main window is actually (1) 7x5, (2) 2.5x3.5;
12) Any further attempts to change the layouts regardless of Style Layout choices are not successful.
13) Close LR4Beta>re-open LR4Beta;
14) Repeat test;
15) Print Module layouts do not update on the fly as expected;
16) Close LR4Beta and all applications;
17) Reboot iMac.
18) Open LR4Beta only;
19) LR4Beta>Print Module>Template Browser >Lightroom Templates>Maximum Size;
20) Image displays in main layout window with Template and Preview display as expected;
21) Choose different image>Template Browser>Lightroom Templates>Maximum Size;
22) Click through templates, layouts DO NOT update in main window although previews do automatically update.
23) CONCLUSION - In Lightroom 4 Beta>Print Module>Template Browser, image layouts do not change after initial choice as expected.
I posted this on Photoshop.com as a problem.

Regisrty keys HKEY_CLASSES_ROOT\Photoshop.Application\CLSID and \CurVer are not updated after upgrading to cc 2014

Regisrty keys HKEY_CLASSES_ROOT\Photoshop.Application\CLSID and \CurVer are not updated after upgrading to cc 2014
this cause to "cant create ActiveX object" error in VB Scripts
win7 x64, ps cc 2014 x64
any ideas? thnks

All I can so is show you what I see in that area of my Windows 7 registry but I have CS2, CS6 32, CS6 64, CC 32, CC 64 and CC 2014 64 installed. 6 versions yet there seem to be 9 Photoshop Application dot keys.
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Photoshop.Application]
@="Photoshop Application"
[HKEY_CLASSES_ROOT\Photoshop.Application\CLSID]
@="{702fe898-3f8a-483f-8ca6-3bad95fa2489}"
[HKEY_CLASSES_ROOT\Photoshop.Application\CurVer]
@="Photoshop.Application.80"
[HKEY_CLASSES_ROOT\Photoshop.Application.60]
@="Photoshop Application"
[HKEY_CLASSES_ROOT\Photoshop.Application.60\CLSID]
@="{99aea70e-4d13-44bf-a878-33345cbfcbc8}"
[HKEY_CLASSES_ROOT\Photoshop.Application.60.1]
@="Photoshop CS6 Application"
[HKEY_CLASSES_ROOT\Photoshop.Application.60.1\CLSID]
@="{6DECC242-87EF-11cf-86B4-444553540000}"
[HKEY_CLASSES_ROOT\Photoshop.Application.70]
@="Photoshop Application"
[HKEY_CLASSES_ROOT\Photoshop.Application.70\CLSID]
@="{951ec38c-3de6-4bb8-8246-adf182e6421d}"
[HKEY_CLASSES_ROOT\Photoshop.Application.70.1]
@="Photoshop CC Application"
[HKEY_CLASSES_ROOT\Photoshop.Application.70.1\CLSID]
@="{6DECC242-87EF-11cf-86B4-444553540000}"
[HKEY_CLASSES_ROOT\Photoshop.Application.80]
@="Photoshop Application"
[HKEY_CLASSES_ROOT\Photoshop.Application.80\CLSID]
@="{702fe898-3f8a-483f-8ca6-3bad95fa2489}"
[HKEY_CLASSES_ROOT\Photoshop.Application.80.1]
@="Photoshop CC 2014 Application"
[HKEY_CLASSES_ROOT\Photoshop.Application.80.1\CLSID]
@="{6DECC242-87EF-11cf-86B4-444553540000}"
[HKEY_CLASSES_ROOT\Photoshop.Application.9]
@="Photoshop CS2 Application"
[HKEY_CLASSES_ROOT\Photoshop.Application.9\CLSID]
@="{16aa0b9e-79ac-43b5-86ca-ab961fbeed5f}"
[HKEY_CLASSES_ROOT\Photoshop.Application.9.1]
@="Photoshop CS2 Application"
[HKEY_CLASSES_ROOT\Photoshop.Application.9.1\CLSID]
@="{6DECC242-87EF-11cf-86B4-444553540000}"

HT1414 i phone not updating or upgrading

hi ,
my i phone 4 is not updating or upgrading and i've tried all things its said to do but it keeps coming up with sorry the i phone can't conect to the apple software?

If the iPhone is locked to O2 then only O2 can unlock it contact them and understand their terms for unlocking

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

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

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.

IMovie will not update after upgrading to iOS Yosemite

Have upgraded to Yosemite on iMac and Mac book, but iMovie will not update on either devices...it begins the long update and never seems to complete. On the iMac it says "no updates available" but the iMovie icon is crossed out on desktop. Says that version is not compatable. Macbook is showing an update for iMovie, but have tried several times to update and has not worked yet. Any suggestions???

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen. Click the Clear Display icon in the toolbar. Then take one of the actions that you're having trouble with. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

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

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]

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

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/

Consolidation/Calculation Status not updating

Has anyone experienced this problem: You have made either a metadata or rule change and all of your consolidation status's change to CN. You run "Consolidate All With Data" to get everything caught back up, but the consolidation status stays as CN even though the consolidation completed. Any ideas on what would cause this? Possible data corruption? The data appears to be correct it is just the status that is not updating.

I have seen this issue on my end a lot. This usually happens with us when a section (Entity or Account) is locked. The consolidation runs but the status does not change because it is not allowing for all the children to roll up to the parents. Check to see if one of your Entity is locked.

Layout Status not updated following upgrade of RH5 project to RH7

Similar Messages

Maybe you are looking for