cancel
Showing results for 
Search instead for 
Did you mean: 

No status object is available for SDI 0 error coming

Former Member
0 Kudos

Hi,

In my sales order , when iam going to add the same material as one more line item iam getting the following error message and system not allowing the user to save the document

"No status object is available for sdi0

Object number TM000000001VB (Message BS001)

We activated status profiile and we get the object number status starts with "vb............." but for some items the above object number starting with "TM ....." is coming and system throwing error

Please assist.

Accepted Solutions (1)

Accepted Solutions (1)

Lakshmipathi
Active Contributor
0 Kudos

I feel you need to run the program RIORDST1 to reset the status

thanks

G. Lakshmipathi

Former Member
0 Kudos

Thanks for your reply

But the mentioned programme is only for ps/cs orders . But iam facing problem in sale orders

Plz suggest

Former Member
0 Kudos

Dear Marthanda,

Is there any Status Profile attachec in to your Sales Order Type in T. Code: VOV8 (Tab: Transaction Flow, Field: Status Profile)?

If yes, remove it.

If not, then...

Check error with:

T. Code: SM13/ ST22

For more info, refer link:

Hope, this may help you.

Best Regards,

Amit

VishnAndr
Active Contributor
0 Kudos

What do you mean "remove it"? What if i need status profile to be attached to sales document type?

Edited by: Andrey Vishnevskiy on Dec 9, 2008 1:04 PM

Former Member
0 Kudos

Hi Andr,

Can you please provide me with the solution which u used for this problem,

I am also facing the smilier problem.

Br, Prashant

Former Member
0 Kudos

Hi,

report RIORDST1 fixes PM/CS orders. It does not seem applicable for sales orders.

Regards,

Bruno

Answers (1)

Answers (1)

prateek_dhawan18
Participant
0 Kudos

Hello

When ever such an error occur , start your debugging and create break-point at commit work and rollback work.

Now f8 , when the execution stops at commit work, just check the ABAP Stack and you will see the EXIT/Custom code in which this commit has occurred,

The error usually occurs when an unexpected commit work is called.