on 09-15-2014 5:48 PM
Hello Gurus,
In T-code IW41, when we trying to time confirm the already "Final Confirmed" operation it will give a error message as "Order XXX is already confirmed which is acceptable behavior.
But I just wondering why this is not validating in IW42,
In T-code IW42 final confirmed operations are loaded and all the time are repeating and accumulated
End-User can Time confirm the operation n times even final confirmation indicator ticked.
IS this the stranded behavior? how to prevent this?
Do I need to use CONF*? or can I prevent this from config?
If so which one? Please help
Thanks
Ashok M
Ashok,
User Exit CONFPM03 (include ZXCOFU03).
Put this code
IF afvgd_imp-rmzhl IS NOT INITIAL.
DATA: v_opr TYPE char4,
v_text TYPE char40.
DATA:i_stat LIKE jstat OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'STATUS_READ'
EXPORTING
objnr = afvgd_imp-objnr
only_active = 'X'
TABLES
status = i_stat.
LOOP AT i_stat.
IF i_stat-stat = 'I0009'.
v_opr = afvgd_imp-vornr.
CONCATENATE v_opr 'Operation already confirmed' INTO v_text SEPARATED BY space.
MESSAGE: v_text TYPE 'E'.
CLEAR: v_text, v_opr.
ENDIF.
ENDLOOP.
ENDIF.
This should address your issue.
I was trying to arrange an error message while confirming already confirmed operation. The error message was appearing in IW41 as expected and stopping user from confirming already confirmed operation.
The good news is that this code is suppressing the confirmed operations from list of operation in IW42. This is exactly anyone's requirement like yours too, who does not want to confirm operations multiple times. You may test and confirm. I tested it repeatedly.
Best of Luck
KJogeswaraRao
10/02/2016
Above Code improvised to make it applicable to only fully confirmed Operations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks all for the responses
AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ashok,
You can use user-exit CONFPM03 to exclude operations under your own customer-specific logic.
PeteA
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Greetings Ashok,
Can you explain what is your exact requirement? In both transactions you will get the standard "Status Management" dialog and only after confirming in, you can equally post n confirmations after the "final" one for an Order.
Is your aim to prevent any Confirmations after Final Confirmation and status CNF? If so, then you can use User Status with a status that is Set by the final confirmation and that Forbids any confirmations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.