Skip to Content

PR Overall Release Strategy config gives no error but strategy not kicking in

Good Day,

I have attached my config for overall release strategy. CL30N gives no issues and when I check the release startegy in SPRO all is green. Upon creating the PR no release strategy is picked up. Only when we debug and manually set the values will the release tab in header appear:

FRGST NEW: Z1

FRGGR NEW: A1

FRGKZ: X

FRGRL:X

Please see attached screenshots of config. Am I missing anything or configured something incorrectly in the release strategy?

Document type ZIS configured for overall release:

1.png

Characteristics for overall release:

2.png

3.png

4.png

Class for overall release:

5.png

Release group:

6.png

Release code:

7.png

Release indicators

8.png

9.png

Release strategy

10.png

1.png (36.5 kB)
2.png (38.4 kB)
3.png (38.6 kB)
4.png (41.8 kB)
5.png (35.0 kB)
6.png (25.7 kB)
7.png (16.7 kB)
8.png (26.1 kB)
9.png (26.6 kB)
10.png (30.6 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

8 Answers

  • Oct 23, 2017 at 11:20 AM

    8 screenshots and the most important is missing, the screenshot from your PO that shows that the values for all your characteristics are in place.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 23, 2017 at 11:39 AM

    What field has no value when you debug? Which values do you enter?

    This PR is with a delivery date of October 19, while we have the 23rd today, does it mean this PR was already created before you did your customizing?

    Can you try with a brand new PR (not copying any old)

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 23, 2017 at 12:03 PM

    You must not mix the fields that are a result of a found strategy with the values for fields that are basis to find a strategy.

    All your fields mentioned can only have a value after the strategy was found.

    Basis for strategy to be found are your 3 characteristics, the value GFWRT is probably there, the document type BSART too, but I doubt that GSFRG has any value, as this is usually the result of a release, documenting how the requisition was released.

    Exclude this characteristic from your strategy and see.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 23, 2017 at 11:26 AM

    11.png

    12.png

    13.png

    Characteristics:

    14.png

    CL30N

    15.png

    Check release strategy:

    16.png

    PR has document type ZIS, value > than 0.00 ZAR and document type is configured for overall release but still no release header tab:

    17.png

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 23, 2017 at 02:10 PM

    Can you check this KBA document 1497235 - Release strategy is not determined for Purchase Requisition in t-code ME51(N)/ME52(N) or Purchase Order in t-code ME21(N)/ME22(N)

    Check all the points written in the resolution part.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 24, 2017 at 10:39 AM

    From the customizing and classification I can't see anything wrong, remains just

    the user exit (Enhancement M06B0002, EXIT_SAPLEBND_001, ZXM06U13) that need to be checked. it has to have a statement:

    E_CEBAN = I_CEBAN

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 24, 2017 at 12:31 PM

    Program ZXM06U13 does not exist

    Message No. DS017

    Diagnosis

    The program you specified does not exist.

    Procedure

    If are creating a new program, acknowledge the message and continue.
    If you are trying to access an existing program, check the spelling. For a list of existing programs, select Utilties -> Find program.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 23, 2017 at 02:13 PM

    run report RCCLZUOB in test mode and see if it lists inconsistent entries.

    Add comment
    10|10000 characters needed characters exceeded