Hello VINAY,
There is no way other than ABAPer solution. I see this can be managed through user-exits. You should be able to understand what is being written here. More than that you should have ABAP support who can understand this better.
This is a solution combining the ideas of both Maria (extra User status) and Pavan (User-exit). The proposed solution here applies once your Order attains the REL Sy.Status. (There is no issue before REL status). It goes like this:
You maintain 2 extra user-statuses suppose one being AARQ (Additional Approval Required) and the other ADAG (Additional Approval Given).
Logic
The user-exit PPCO0023 senses any component changes/additions in the Order. So the code to be developed like this:
Whenever a Component is added, code first looks into the system status of the Order with the help of function module 'STATUS_READ' and if it is REL, then computes its cost of this component/s, if it is found more than what you specify then the code sets the AARQ user status to the Order with the help of another function module 'STATUS_CHANGE_EXTERN'.
Then
1. A code to be given in user-exits IWO10009 to prevent any further processing of Order until the Order gets the ADAG user status from the approving authority. (Necessary Role modifications required to be done to prevent setting of these user-statuses by unauthorized users ).
2. Similarly A code to be given in the user-exit CONFPM02 to prevent Operation processing until the Order gets the ADAG status.
3. Also user-exit IWO10004 can be used to prevent Order TECO until the above user-status.
Sample usages of the user-exits are available in the links here:
User-exit PPCO0023
User-exit IWO10009
User-exits CONFPM02 and IWO10004
Good luck
KJogeswaraRao
