 (/forums) Recent (/index) Categories (/categories) Tags (/tags) Users (/users) Badges (/badges)  (/ask)

Resolved 365604 - FAQ: Release strategies in purchasing (/19-365604-faq-release-strategies-in-purchasing)

Consulting V

Super User (/profile/833-admin) (/badges/6-sherlock-holmes) MM/P2P (/forums/12-mm-p2p) Sunday, 02 April 2017  Subscribe via email

Symptom
The system does not determine the release strategy for purchase requisitions (PReqs) or purchasing documents (for example, purchase orders, outline agre
or requests for quotation).

Other Terms
T16FS, T16FG, T16FC, frgzu, frgrl, M06E0005, FAQ
Reason and Prerequisites
1. Settings in Customizing

a) Release group:
You are only allowed to use one class for each release object (1=PReq, 2=Purchase order). When you use the overall release (as of Release 4.0A), you are
allowed to use one class for the overall release or individual release. Overall release and individual release is not possible in the same document. If you use
release for purchase requisitions, this must be specified for the document type in Customizing (indicator for V_T161-GSFRG) and the release group (indicato
V_T16FG-FRGFG). During the overall release, the system takes into account only the characteristics that are identical for all items. If, for example, item 10 o
purchase requisition contains material group 001 and item 20 contains material group 002, the material group is set to BLANK for the strategy determination.
b) Release indicator:
A release strategy must contain at least two release indicators. The first indicator must be defined as blocked and the last release indicator must be defined a
released. If this is not the case, the release status is not displayed correctly. If a value is entered in field 'Value changes' (V_161S-TLFAE), the system only ch
value increases.
If you have purchase requisitions from material requirements planning (MRP) (EBAN-ESTKZ = 'B') that are subject to a release strategy, the system may res
PReq release when the MRP is restarted. In this case, you should set 'Fix for material requirements planning' for the relevant release indicator (V_161S-FIXB
c) Release statuses:
A release indicator must be assigned to each release status that is theoretically possible. Thus, for example for five release codes that can be released in an
sequence, you have to maintain 32 entries.
Caution: If the release strategy contains many release codes, the system does not display all the statuses in the window. In order to display these release sta
you have to use the page down or page up keys on the keyboard since the window has no scroll bar.
2. Settings in the classification
1. The characteristics of the class used must all be linked to the corresponding fields of structure CEBAN (for purchase requisitions) or CEKKO (for purcha
orders).
2. The characteristics must be entered as they are specified on the database, that is, the item category must be entered in the internal format, for example
0-9), cost centers or material numbers must be entered with leading zeros.
3. If intervals are used for the characteristics, the corresponding characteristic must be marked as multiple value in the classification.
4. If a characteristic is non-valuated (blank entry), this field must actually be filled with blanks in the document. A blank entry can be useful when the overa
release is used. A blank entry is not to be seen as a wildcard (*). If, for example, all material groups of a release strategy should be subject to an update
strategy, you must enter these explicitly in the classification. You cannot use a placeholder (wildcard). You can maintain a blank entry as follows:
i. -Enter the characteristic in transaction CT04 (for releases < 4.6, transaction CT02)- Select 'Value'
ii. Do not maintain any entry in column 'Characteristic value'
iii. In the column 'Characteristic name', enter a text such as, for example, 'Blank entry' and save the settings
iv. The blank entry that is maintained as such can now be selected from the F4 help in Customizing for the release strategy (pushbutton: Classification).
5. If you make changes to the class (add or delete a characteristic), the system cannot determine the release for this class. Then you must adjust all releas
strategies correspondingly. (If you added a new characteristic, you must maintain the characteristic value).
6. A working strategy must have classification status '1' (active) in transaction CL24 or CL24N. If you delete release strategies, ensure that the strategy is a
deleted in transaction CL24 or CL24N with the deletion in Customizing.
7. You can use report RCCLZUOB to check the consistency: Class type: 032Object table: KSSK
You can use transaction CL30 search for an object using the data of the purchase requisition/purchase order. Here, it is important that the object search dete
exactly one strategy. If this is not the case, this indicates that there are overlapping strategies in the system or that the release strategies in Customizing do n
correspond with those from transaction CL24. See the previous point. If the object search returns more than one result, the system subsequently determines
incorrect release strategy or no release strategy at all.
3. User exit
During the individual release for purchase requisitions, the user exit is called in function module ME_REL_STRATEGIE_EBAN, in the overall release,
called in function module ME_REL_GENERAL_STRATEGY_EBAN.
(Enhancement M06B0002, EXIT_SAPLEBND_001, ZXM06U13)

During the release for purchase orders the user exit in function module ME_REL_STRATEGIE_EKKO is called, in releases > 3.1X in program
MM06EF0S_STRATEGIE_CEKKO (Enhancement M06E0004, EXIT_SAPLEBND_002, ZXM06U22).

The data is available in the user exit in structure I_CEBAN or I_CEKKO. The transfer from this structure to the calling program runs using structure E_
or E_CEKKO. In the user exit, I_CEBAN must be copied to E_CEBAN or I_CEKKO must be copied to E_CEKKO anywhere in the user exit, for examp
E_CEBAN = I_CEBAN.
4. Important notes in connection with a non-working release strategy:
Note 117391 --> as of Release 4.0, for the release of purchase requisitions; Release strategy does not work sporadically.
Note 378718 > symptom: Release strategy works depending on the user.
Documents which are created by users who have no authorization for class type 032(object: C_TCLA_BKA) are not subject to any release strategy.
Note 493900 > FAQ: Release strategy
Note 086900 > Instruction for the transport of Release strategies
Note 045951 > Transport of class data: System/client
Note 010745 > Copying class data to other clients
Note 435150 > User exit deactivated after importing R/3 Support Packages
Note 493414 > RCCLZUOB revised
Note 350703 > OMGQCK: Error message 'No release group exists'
/
 5. Deletion of release strategies:
The tables T16FK, T16FV, T16FS, T16FC and T16FG may contain entries from previous Customizing settings (such as old release groups) which were dele
Customizing but not in the tables. This creates an inconsistency. To eliminate the inconsistency, proceed as follows: Make all the deleted release settings in
Customizing again, save them, and then delete them in the following sequence:
1. The release strategies
2. The release indicators
3. The release codes
4. The release group
5. The corresponding class (transaction CL02) if a new one was created for the new release strategies.
Then use transaction SE16 to check whether the entries were deleted in the tables named above. Execute the check report in Customizing (transaction OMG
OMGSCK) and ensure that a red traffic light is not displayed. Also refer to SAP Note 350703. You can use report RCCLZUOB to check the consistency as al
mentioned in point 2f.
6. Changing the release strategy when the system is running:
We strongly recommend that you do NOT change an existing release strategy that is in use or its individual elements (release code(s), release status and so
especially if documents already exist in the system that use this release strategy. However, if you make these types of changes in spite of this recommendati
following inconsistencies or problems may occur. For example, if you cancel a release, this can result in the system issuing error message ME 108 ('No new
indicator can be determined'). It is also possible that certain release statuses that had the documents concerned before the corresponding release strategies
changed, are no longer available after the change. This means that the documents concerned are in an inconsistent release status.
In this case, the only solution is to explicitly trigger the determination of a new release strategy for the document concerned.
Solution
References: This document refers to

Number Title
86900 Transport of Release strategies (OMGQ,OMGS) (https://launchpad.support.sap.com/#/notes/86900)
672719 FAQ: Release strategies in the service (https://launchpad.support.sap.com/#/notes/672719)
662993 Resetting a release that already took place (https://launchpad.support.sap.com/#/notes/662993)
493900 FAQ: Release Strategy (https://launchpad.support.sap.com/#/notes/493900)
45951 Transporting class data: system / client (https://launchpad.support.sap.com/#/notes/45951)
378718 Release procedure purch.:no release strategy assgnd (https://launchpad.support.sap.com/#/notes/378718)
329898 User exit revised for purchase order release (https://launchpad.support.sap.com/#/notes/329898)
207490 Release procedure purchasing: Documentation for Customizing (https://launchpad.support.sap.com/#/notes/207490)
117391 Rel. proced. PReq:Problems after upgrade to Rel 4.0 (https://launchpad.support.sap.com/#/notes/117391)
10745 Copying classification data to another client (https://launchpad.support.sap.com/#/notes/10745)

This document is referenced by

Number Title
2445131 [WEBINAR] Identify and resolve common issues in Release Strategies for Purchasing Documents
(https://launchpad.support.sap.com/#/notes/2445131)
1635346 Issues with release strategies in purchase requisitions/purchase orders (https://launchpad.support.sap.com/#/notes/1635346)
672719 FAQ: Release strategies in the service (https://launchpad.support.sap.com/#/notes/672719)
493900 FAQ: Release Strategy (https://launchpad.support.sap.com/#/notes/493900)
662993 Resetting a release that already took place (https://launchpad.support.sap.com/#/notes/662993)
207490 Release procedure purchasing: Documentation for Customizing (https://launchpad.support.sap.com/#/notes/207490)
329898 User exit revised for purchase order release (https://launchpad.support.sap.com/#/notes/329898)
45951 Transporting class data: system / client (https://launchpad.support.sap.com/#/notes/45951)
117391 Rel. proced. PReq:Problems after upgrade to Rel 4.0 (https://launchpad.support.sap.com/#/notes/117391)
378718 Release procedure purch.:no release strategy assgnd (https://launchpad.support.sap.com/#/notes/378718)
86900 Transport of Release strategies (OMGQ,OMGS) (https://launchpad.support.sap.com/#/notes/86900)
10745 Copying classification data to another client (https://launchpad.support.sap.com/#/notes/10745)

 SAP MM (/tags/23-sap-mm)  OSS Notes (/tags/35-oss-notes)  SAP OSS (/tags/36-sap-oss)  Release Strategies (/tags/37-release-strategies)  PO Release Strategy (/tags/38-po-release-strategy)

Share Tweet

Responses (0)


There are no replies made for this post yet.
Be one of the first to reply to this post!