cancel
Showing results for 
Search instead for 
Did you mean: 

How To Write Not Equal To Effectively For Mtrl Group In Release Strategy For Purchase Order

Vikas_th
Discoverer
0 Kudos
674

We want to use material group in release strategy for purchase orders. There are total material 52 groups.

Three groups to be released by one user and remaining group purchase orders will be released by another users.

For 1st user the three groups have been written in classification BUT we are facing problem in writing 'Not Equal To'

effectively for the 2nd user. We want to write the classification as Mtrl Group: <> the 3 groups of the 1st user OR

Mtrl Group: <> space.

Is it possible ? If yes, how. Anybody if aware, please answer.

Thanks in advance,

PVish

Accepted Solutions (0)

Answers (3)

Answers (3)

BijayKumarBarik
Active Contributor
0 Kudos

Designing release strategies based on material groups may not help business in future for long run!

If you decided along with your business- You can have different material group coding.

1st Group------------------------2nd Group ----------------------3rd Group

MAT100001......................MAT20001................................MAT3001

MAT100002........................MAT20002....................................MAT3002

MAT100003....................MAT20003....................................MAT30003

Now you can design a custom table with Users and Material groups with release code

Release Code......Users.......................Materiel Groups

C1.........................U-1xxxxxxxxxxxxxxxxxxMAT100001

C2.........................U-2xxxxxxxxxxxxxxxxxxMAT20001

C3..........................U-3xxxxxxxxxxxxxxxxxxMAT3001

Discuss with ABAPer and design your own coding to triggers releaser based your business requirement.

rob_ariaans
Contributor
0 Kudos

You can look into writing your own logic in Enhancement M06E0004.

pataselano
Active Contributor
0 Kudos

It is not possible You must enter all possible value for the corresponding characteristic (as a range - just in case of numeric characteristics). Please see SAP note: 493900 - FAQ: Release Strategy, answer for question 14.,