Hi, I have recently encountered a "funny" behavior: In case of a contract which already has PO's using it, after setting deletion indicator to all contract items (and completion version if necessary), the contract remains subject to release strategy. This is in contrast to the behavior of which canceling a contract with no PO's, On the latter case, after cancelation, the contract is no longer subject for release. 1. Do you know if this is "normal" intentional standard behavior ? 2. If so - Is there any way through customizing to change it, so it would no longer be subject to release once it is canceled, regardless of the POH ? 3. In attempt to cancel such an Item we do get a standard message: -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Not all contract release orders archived for item XXXXX Message no. 06809 Diagnosis Release orders still exist for contract item XXXXX. If the contract is archived and deleted before the release orders, the latter can then only be processed to a limited extent. Procedure You should only archive and delete the contract after you have archived the contract release orders -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This is messgae is warning only on my system. There is currently nothing which will avoid a user from deleteing contract even before the contratc release orders have been archived. Is there any way to convert that message to an error? when looking "where used" on 06 809 is looks "hard-coded" with 'W' type messgae. If I would like to perform my own custom validation to block deleting of a contract item with PO which are not yet archived, do you know where could I find the system's satrand logic for the original warning message? TIA, Chanan