Cannot return from TECO after a Work Order has been business closed.

[Former Member]

When a work order in our system has been Technically Completed and then Business Completed, the work order saves correctly. However when the Business completion is cancelled and TECO is set, the order will now no longer be able to change its status back down to work in progess or planning stages.

The Status Profile of the order type is set so that when when the CLSD - Business Closed (80-90) status is active, only COMP - Technically Complete (80) and CLSD (90) statuses are available. The status COMP is set so that all statuses are available (20-90) however once the Work Order has been Business Closed, the system acts as if the CLSD status is still active.is situation.

This situation occurs in both our Development system and our test system. In our Development system to provide a work around, I have changed the parameters of the CLSD status to the same as what COMP should be (it has been changed to 20-90). This has solved the problem. This shows that the system is not registering the cancellation of business closure.

Has anyone experienced this before or is it a known bug/problem?

Thank you in advance for your help.
Nye

[Former Member · Accepted solution]

Here is the status profile. Do you need any other information?

[Former Member · Accepted solution]

In User Status Business Transactions, Cancellation of Business Completion has not been defined. Only TECO revoke business transaction is available.

So, if you cancel the Business Completion, then the concern user status should be set manually only.

[Former Member · Accepted solution]

There is no Business Transaction called "Cancellation of Business Completion". "Revoke Technical Completion" has been defined for the correct status - COMP.

To clarify, the problem does not occur when the order is in the CLSD status. Rather it occurs when the order has been Business Completed, then the Business completion has been cancelled. At this point, the status profile will not allow me to cancel the Technical Completion. Importantly, this problem does not occur if I do not Business Complete the order.

[peter_atkin · Accepted solution]

Nye,

Send us a screen-shot of the order when you are performing this process, make sure we can see the system/user statuses and the error messages.

PeteA

[Former Member · Accepted solution]

That's what my earlier post has been referred.

Once you do Business Completion cancellation, you have to set the required status manually. After maintaining the appropriate status, then do TECO cancellation.

[sebastian_lenartowicz · Accepted solution]

Greetings Maheswaran,

The status control here is that COMP is a numbered status, so it is set to "Set" if you Technically Complete. As far as status control goes, this is the same for the business transactions as defined in OIBS when you Cancel Business Completion. so the COMP status is set for both those transactions.

The business transactions are a red herring here - the issue is that the user status number control works improperly as seems evident from Nye's screenshot. For whatever reason the last user status prohibits status change to a lower one - despite being inactive at the time.

[sebastian_lenartowicz · Accepted solution]

Gents,

I believe the note Note 159553 - Error messages BS042,BS043 addresses this issue.

I have been able to independently replicate this issue on an IDES system. (SAP ECC 6.0 SAP_APPL 605)

The business transaction / workflow control is actually irrelevant. The issue will occur for an Order status profile as pictured by Nye. I.e. there will be an error message:

"Status WIP is not allowed (ORD #)

Message no. BS043

Diagnosis

User status 'WIP' has reference number 70.  In the current object status 'ORD 821468' the reference number of a status must be at least 80.

Procedure

You can only set user status whose reference number is at least 80."

Obviously information in this message is wrong, since COMP should allow a reference status as low as 20 in this case. The note mentioned explains that the highest status attained will determine the lowest status allowed according to the program logic ("status memory").

It is also not relevant if the Order is saved - if you only go into IW31 and change the user statuses in the Order in sequence, then go back from CLSD to COMP to WIP - the same message will occur.

[peter_atkin]

Nye,

Can you send screen-shots of you status profile (OIBS) and also the underlying transaction control settings

PeteA