Knowledge Management

Question:
Hi MMers,
Need help. Why my PO Release Strategy go missing when I maintain/add/delete/repeat PO messages(outout). This happens even after my PO has been released.
Any help is very much appreciated.
Answer:
Hi,
It sounds very surprised to get to know this particular problem as I have not heard of any similar problem so far. Are you quite sure that there has not been any change in your PO at all? (except for maintenance of output message type). What kind of PO was it? How would you see it happened?.
Cheers,
HT
_________________
Moderator:

Answer:
Hi Ha Tran,
It's true. The Release Straegy go missing AFTER I maintained my output messages. I have tested many POs (Normal PO-NB) by just changing the output messages. Then the Release Strategy go missing. This happened even for POs that have been released. This is serious.
Help.
Answer:
Hi,
What you should do is to let me know in details what you have set up your PO release strategy (including definition of release characteristics and release characteristics value and so on).
Cheers,
HT
_________________
Moderator:

Answer:
Hi Ha Tran,
My setup for PO Release Strategy is as follows:
Class ---> DRO_RELEASE
Class Type ---> 032
Characteristics ---> DRO_VALUE-Total net order value
DOCUMENT_TYPE-Order type
ZPO_APPROVER-Collective number-Approver
Release Group ---> Z1 (Class : DRO_RELEASE)
Release Codes ---> LA to LZ
Release Indicator ---> F (Changeability-6)
Release Straategy Z1/LA, Z1/LB, Z1/LC etc
Regards,
MMC
Answer:
Hai,
Are u in the initial stage of implementation ,then recreate the whole release str cycle..other wise check the rele stra consistency in the last of the release strategy setting.
reg
JIB
Answer:
Hi,
Did you activate any User Exit to control your release strategy? If yes, what was it?. Otherwise, I would recommend you of logging this problem to OSS. Post also the solution if any so that we can all sharing the experiences.
Cheers,
HT
_________________
Moderator:

Answer:
Hi Ha Tran,
Yes. I have activated the user exit M06E0004. Coding attached.
Function module ---> EXIT_SAPLEBND_002
INCLUDE ZXM06U22.
*----------------------------------------------------------------------*
* INCLUDE ZXM06U22 *
*----------------------------------------------------------------------*
* For the following Document Types, a check at the Collective No. field
* The 'Collective No. is a field entered by the PO creater to identify
* identify the PO approver.
* The logic below will not allow the PO creator and the Approver to be
* the same person
DATA: BEGIN OF TSYST.
INCLUDE STRUCTURE SYST.
DATA: END OF TSYST.
DATA: BEGIN OF T1.
INCLUDE STRUCTURE BEKPO.
DATA: END OF T1.
DATA: GV_POCRT TYPE CHAR1,
GV_UNAME LIKE SYST-UNAME,
GV_TCODE LIKE SYST-TCODE,
gv_first type char1,
PO_CREATOR LIKE EKKO-ERNAM.
CLEAR: GV_POCRT, gv_first.
TSYST = SYST.
* For all the document types listed below, check the Collective No.
* field
IF I_CEKKO-BSART = '2G' OR
I_CEKKO-BSART = '3G' OR
I_CEKKO-BSART = 'CNC' OR
I_CEKKO-BSART = 'CO' OR
I_CEKKO-BSART = 'MC' OR
I_CEKKO-BSART = 'MC1' OR
I_CEKKO-BSART = 'MC2' OR
I_CEKKO-BSART = 'MC3' OR
I_CEKKO-BSART = 'MC4' OR
I_CEKKO-BSART = 'MC5' OR
I_CEKKO-BSART = 'MC6' OR
I_CEKKO-BSART = 'MC7' OR
I_CEKKO-BSART = 'NB' OR
I_CEKKO-BSART = 'RO' OR
I_CEKKO-BSART = 'SO' OR
I_CEKKO-BSART = 'SOW' OR
I_CEKKO-BSART = 'MC8' OR
I_CEKKO-BSART = 'MC9' OR
I_CEKKO-BSART = 'MC10' OR
I_CEKKO-BSART = 'MC11' OR
I_CEKKO-BSART = 'MC12' OR
I_CEKKO-BSART = 'MC13' OR
I_CEKKO-BSART = 'TC' .
GV_UNAME = SY-UNAME+2(10).
* When the user changes PO, check if the user was the PO creator
IF TSYST-TCODE = 'ME22N' OR TSYST-TCODE = 'ME23N' or
tsyst-tcode = 'ME21N'.
READ TABLE IT_BEKPO INTO T1 INDEX 1.
SELECT SINGLE ERNAM INTO PO_CREATOR
FROM EKKO WHERE EBELN = T1-EBELN.
if sy-subrc = 0.
IF PO_CREATOR+2(10) = GV_UNAME.
GV_POCRT = 'X'.
ENDIF.
else.
gv_first = 'X'.
endif.
ENDIF.
CASE SY-UCOMM.
* When user clicks 'Check Document' button
WHEN 'MECHECKDOC'.
IF I_CEKKO-SUBMI = GV_UNAME.
IF GV_POCRT = 'X'.
MESSAGE E000(3 WITH
'Please enter an Authorized Approver'.
ELSEif gv_first = 'X'.
MESSAGE E000(3 WITH
'Please enter an Authorized Approver'.
else.
* do nothing
* EXIT.
ENDIF.
ENDIF.
* When user clicks 'Save Document' button
WHEN 'MESAVE'.
IF I_CEKKO-SUBMI = GV_UNAME.
IF GV_POCRT = 'X'.
MESSAGE E000(3 WITH
'Please enter an Authorized Approver'.
ELSEif gv_first = 'X'.
MESSAGE E000(3 WITH
'Please enter an Authorized Approver'.
ELSE.
* do nothing
* EXIT.
ENDIF.
ENDIF.
* When user does anything else
WHEN OTHERS.
EXIT.
ENDCASE.
ELSE.
* and if the Document Type is not listed above
* then the collective no field should be blank
IF NOT I_CEKKO-SUBMI IS INITIAL.
I_CEKKO-SUBMI = ' '.
ENDIF.
ENDIF.
* Export structure
E_CEKKO = I_CEKKO.
Answer:
Hi,
Let me know if you use other document type, would you get the same problem? I started thinking of the root cause of this problem originated from this User Exit. However, I would not make any further justification till getting additional confirmation from you.
Cheers,
HT
_________________
Moderator:

Answer:
Ha Tran,
I tested using other document types, they are ok - no problem.
So, I think the problem is because of the user exit.
Regards,
MMC