Sales Doc Overall status not updating in DSO

Hi All,
In ECC status of the Sales Document has changed from B to C. However in the DSO status still shows as C. Delta has pushed through successfully. Please see the screenshot below. Why is the status not changing in DSO?
How to handle this issue?
Regards,
DTD

Dear Dhanuka
If the sale order item is the key field and the status is in the data field in the DSO you will not have an issue in the cube.
Please find the example below
1. DSO - Sales order X1 / 10 overall status B   keyfigure 100
2. Cube - Sales order X1 / 10 overall status B   keyfigure 100
After the Full DTP - Overall status will be overwritten in DSO
3. DSO - Sales order X1 / 10 overall status C   keyfigure 100
4. Cube - Sales order X1 / 10 overall status B   keyfigure 100
5. Cube - Sales order X1 / 10 overall status B   keyfigure -100
6. Cube - Sales order X1 / 10 overall status C   keyfigure   100
Regards
Gajesh

Similar Messages

Need function module for Sales order overall status

Dear Team,
Our requriement is we need to capture sales orders overall status 'compleated' in header and item datat details.
Could you please let me know what are function modules available for to get the over all status for sales orders, (header and item)
Thanks & Regards,
MK.

Hi MK,
Use any of this FMs.
C1CE_VBUK_READ
SD_VBUP_READ_WITH_VBELN
WCB_VBUK_READ
Note that the values are in table VBUK and you can do a select statement from that table to get what you need.
Regards,
Peter

Delta records not updating from DSO to CUBE in BI 7

Hi Experts,
Delta records not updating from DSO to CUBE
in DSO keyfigure value showing '0' but in CUBE same record showing '-I '
I cheked in Change log table in DSO its have 5 records
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - -1
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M -   0
ODSR_4LIF02ZV32F1M85DXHUCSH0DL -   0
ODSR_4LIF02ZV32F1M85DXHUCSH0DL -   1
ODSR_4LH8CXKUJPW2JDS0LC775N4MH -   0
but active data table have one record - 0
how to corrcct the delta load??
Regards,
Jai

Hi,
I think initially the value was 0 (ODSR_4LH8CXKUJPW2JDS0LC775N4MH - 0, new image in changelog) and this got loaded to the cube.
Then the value got changed to 1 (ODSR_4LIF02ZV32F1M85DXHUCSH0DL - 0, before image & ODSR_4LIF02ZV32F1M85DXHUCSH0DL - 1, after image). Now this record updates the cube with value 1. The cube has 2 records, one with 0 value and the other with 1.
The value got changed again to 0 (ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - (-1), before image &
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - 0, after image). Now these records get aggregated and update the cube with (-1).
The cube has 3 records, with 0, 1 and -1 values....the effective total is 0 which is correct.
Is this not what you see in the cube? were the earlier req deleted from the cube?

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

In Sales Order Overall Status is Blocked

Hi Gurus,
I got an issue with Sales Order. Here delivery is complete and billing is complete. In document flow it is showing it is complete.
If you check overall status of the order it is showing as blocked.
What could be the reason.
Thanks.
Regards,
Varada

Check the copy control routines which you are using between your sales document to delivery to billing.
Maybe the routine is not taking into account the blocks. You need to ensure that the logic is written by abaper to take billing/delivery blocks in account before subsequent processing.
Thanks

Sales Order Overall Status

My overall status for my sales order is not shoing as being completed. My item category that is the same in each sales order is a non tangible item and will need to be split into different delvieries at times so the completion rule for this is B and the billing relevance is A...the sales order does indicate the delviery status as complete...the accounting document is cleared but for some reason my over all status is "being processed" has anyone ran into this before? What were the corrections?

hi,
Please check alsoVBFA to confirm whether the status is correct or not.
For header status, it gets calculated based on all item statuses.
say to ABAPER to deubgg these FM's
RV_XVBUP_MAINTAIN for item
RV_XVBUK_MAINTAIN for header
please also check 207875
balajia

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/

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]

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.

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

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

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.

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

Sales Doc Overall status not updating in DSO

Similar Messages

Maybe you are looking for