Hi,
You have to merge and assign two release groups into one release class in your configuration where the plant shall be used as part of your release strategy. To overcome your outstanding "B" problem, you should assign "blank" value to your plant release characteristic in CL20N transaction for your related release strategy.
Cheers,
HT
| | | ---------------Original Message---------------
From: Daniele Campagnuolo
Sent: Tuesday, October 04, 2011 12:00 PM
Subject: Release Strategy for Purchase Requisition
Hi all,
I'm customizing the global release strategy for purchase requisition. I
cannot assign two different classes at global level, so I have managed a
class already used from an other release group.
The group A2, before updating, used only 3 characteristics PLANT/DOC. TYPE/VALUE
To use the same release strategy, i have added other 2 characteristics
(PURCH. GROUP and REQUISITIONER) at the FRG_EBAN class.
To trigger this strategy, the discriminant values are: PURCH.
GROUP/REQUISITIONER/DOC. TYPE/VALUE and not the PLANT.
In CL20N, I assigned all possible plant for my object.
I made these tests:
a - in ME51N, I create a p.req. with 2 item with the same PLANT, the
release strategy assigned is correct,
b - in ME51N, I create a p.req. with 2 item with 2 different plant, the system doesn't assign the release strategy.
The "b" test is an issue i have to solve, but I don't know how can manage it.
Could anyone help me, please?
I hope my problem is clear.
Thanks in advance.
Regards,
Daniele |
| __.____._ Copyright © 2011 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| |  ha_tran
SAP Logistics Material Management Top Contributor
Contributed the most posts in a group for 3 consecutive months to earn a Gold Achievement Popular White Papers
In the Spotlight   _.____.__ |
0 Response to "RE:[sap-log-mm] Release Strategy for Purchase Requisition"
Post a Comment