Confirmation Configuration

[Former Member]

Hi All, we are trying to find out if there is a way to configure confirmations so that an operation can not be Final Confirmed (CNF) unless the previous operation(s) have been Final Confirmed. In other words, all preceding operations must be CNF before the current operation can be Final Confirmed. We are thinking if we can configure to just have it check to make sure the previous operation is CNF, this would suffice. We use TimeTicket confirmations via BAPI_PRODORDCONF_CREATE_TT & CO11N. We need each user's final confirmation on each operation (usually have a different user work each operation), so the automatic confirmation on milestone will not work.

Would appreciate any help.

David

[former_member196398 · Accepted solution]

David,

I am not sure whether the check I am suggesting would work for BAPI scenario. In confirmation Parameters, using transaction OPK4 for the Plant/Order type combination define Operation Sequence is checked and error message. Please try and provide the feedback whether it worked or not.

Regards,

Prasobh

[Former Member · Accepted solution]

Prasobh,

Yes this worked with CO11N as well as the bapi (as long as you don't yield the entire scheduled qty on the previous Partial Confirmation). With CO11N, the partial confirmation proposal defaults the yield field with the entire operation scheduled qty, so if you don't blank out the yield or reduce it, you will be able to Final Confirm the next operation. In most cases with the bapi, we pass in zero or less than the entire yield, so, at this point, we think it will work fine.

Thanks

David