PCNF's-Partial Confirmations & issues with them...

[JWood]

Is anybody aware of, (or even using) an arrangement that prompts end users to enter more detail than just a time quantity when PARTIALLY confirming operations?
The maintenance people for example will partially confirm an operation & you're left with no clue as to how far they actually got with that task.
Is there a prompt used anywhere that specifies the end user to include an explanation as to why it's a partial confirmation?
As things are, when dealing with work orders featuring operations that have been partially confirmed, I have to chase the relevant people to establish the real-life, physical status of the operation.
Given that we use a range of work centres, this is quite a mission.
We are using version R3 & I'm ignorant as to what our own Master Data people are capable of doing on site, but I'm making enquiries with them.
Given that our site is extremely unstable & fluid, our schedule suffers frequent changes.
Many operations, complete work orders & even Revisions are often being re-scheduled, even after work has begun, only to have the allocated resources then pointed elsewhere.
Can anybody relate to the problem we then experience given the multitude of Partial Confirmations & efforts required to establish details of work performed?

[PJA]

JWood

Yes, its quite common to develop additional functionality in SAP, including around the confirmation area.

You can the following approaches:
1. Configure the system to make certain fields mandatory
2. Use transaction variant which are a similar way of doing the above, though with a little more flexibility
3. Develop a customer-specific solution using the CONFPM* user-exits (see TCode SMOD)