365604 - FAQ: Release strategies in purchasing ‘comsorent Md PUR-GF-REL (Ro (Aare, Version: 31, Releasoo On 20.11.2012 1 sympton ‘The systen does nor determine the release strategy for purchase requisitions (Regs) or purchasing docuaents (for example, purchase orders, outTine agreements oF requests for quotation) | other Terms Ties, T26EG, TIS#C, frgzu, Fer, MOBEODOS, cA | Reason and prerequisites AL Sevtings in customizing 1 release group: You are only aTTowed to use one class for each release object (I-PRes, 2-Purchase order). when you use the overall release (@s of Release 4.01), you are only allowed to use one class for the overall release or Indivigual release Overall release and individual release %= not possible in the sane document. If you use overall release for purchase requisitions, this must be specities for the docunent type in customizing Cinéicater for V-TI61-GSFA6) and the release Group Gndicator for VATI6FG-FRGFG), During the overall release, the systen taker into account only the characteristics that are fdentical for aTl items. 1f, for example, ten 10 of a purchase requisition contatns satertal group 001 and ‘vem 20 contains miter‘al group 002, the material group is set to ELAW for the strategy determination, by Release indicator: ‘A release strategy must contain at Teast two release indicators. the First indicator must be defined as blocked ané the ast release indicator must be defined as released. 1f ths 1s not the case, the release status is not displayed correctly. if a value #5 entered in field "Value changes’ (VISIS-TLFAE), the system only checks for vaTue increases 1 you have purchase requisitions fron material reguirenents planving (MRP) (EBAN-ESTKZ = "6") that are subject to 2 release strategy, the system may reset 4 PRoq release when the RP Is restarted. In his case, you should set ‘Fix for material requirenents planning’ for the relevant release indicator (V-26is-FIxar) © Release statuses ‘A release tndicator must be assigned to each release status that 1s theoretically possible. thus, for example for five release codes that can be releases in any Sequence, you have to maintain 32 entries Caution: If the release strategy contains many release codes, the systen does not éisplay all the statuses in the window. tn order 20 cisplay these release statuses, you have to use the page down or page up keys on the keyboard since ‘the window has no scrol? bare 1. the characteristics of the class used must all be inked to the corresponding Fields of structure CEBAN (for purchase requisivions) o* cEKKo (for purchase orders). 2. The characteristics must be enteres a5 they are specified on the database, that is, the ite category must be entered in the internal format, for example (value 0-8), cost cancers or material munbers must be entered with easing zeros 3. Tf intervals are used for the characteristics, che corresponding characteristic mist be narked as mitiple value fn the classification 4. Ta characteristic 15 nomvaluated (blank entry), this Feld muse actuaTly be fied with blanks tn the dociment & blank entry can be useful when the overall release 15 used. A blank entry is fot to be seen as 2 wildcard (*). 1f, for example, all material groups of a release strategy should be subject to an update crategy, you must encer these explicitly in the classification. You cannot use a placsholder (wildcard). You ‘can maintsin a Blank entry a5 follows: 4. “enter the characteristic in transaction C104 (for releases < 4.6, transaction CTO2)- select ‘Value! Gi. be not maintain any entry in column ‘characteristic value’ 444. Tm the column ‘characteristic name", enter a text auch as, for example, ‘Blank entry’ and save the seceings Ww. The Blank entry that is maintained as such can now be selected from the F4 help in custonizing for the release strategy (pushbutton: classification) 5. IF you wake changes to the class (add or delete a characteristic), the system cannot deterwine the release for ‘eais class. then you must adjust aT] release strategies correspondingly. (IF you added a new characteristic, you must maintain the characteristic value) 5. working strategy must have classification status “I' (active) in transaction C124 or CL24N. Tf you delete release strategies, ensure that the strategy 4s also deleted in Cransaction c124 or CL20N wich the deletion in customizing, 7. You ean use report RCCLZUOE to check the consistency: Class type: OFZobject table: KSSK‘You can use transaction CL30 search for an object using the data of the purchase requisition/purchase order. Here, Ge 15 smortane that the object search determines exactly one strategy. If this 15 not the case, this inéFeates that ‘there are overlapping strategies in the system or that the release strategies in customizing do not correspond with ‘those fron transaction CL2é. see the previous point. TF the object search returns more than one result, the sySter subsequently determines an incorrect release strategy or no release strategy at all 3. user exit uring the individual release for purchase requisitions, the user exit is ca¥led in function aodule ME_AEL STRATEGIE EaAN, Sn the overall release, it 45 called 4a function module ME_AEL_GENERAL STRATEGY. CHAN. ‘enhancenent #0680002, xrT_sAPLEBNO 001, ZxM06U13) During the release for purchase orders the user exit in function module MEREL_STRATEGIELEKKO is calle, in releases > 3.1K fn program #NOGETOS_STRATECTE_CERKO CEnhancenent MOGEOOGE, EXIT_SAPLEBND 002, Z=M06022). ‘The data is avaiTable jn the user exit fn structure 1_cERAN ar 1LcEmK0, The transfer from this structure to the calling program rurs using structure E_ct2aN or ELCEKO. In the User exit, ILCLEAN MUSE be copied £0 ELEERAN oF LLCERKO must be copied to E_COMO anyahere in the user exit, for example E-CERAN = I_CKEN 44, important nates in connection with a nonenorking release strategy! Note 117391 —> as of Release 4.0, for the release of purchase requisitions: Kelease strategy does not work sporadically. Note 378718 > sympcon: neease stravegy works depensing on the user Documents nhich are created hy users who have no authorfzation for class type O32(obsecti CTCLALRKA) are not subsect to any release strategy ote 493900 > aq: Release strategy Note 086900 > Instruction for the transport of Release strategies ote 045951 > Transport of class data: systen/cHient note 010745 > copying class data to other clients Note 435250 > User exit deactivates after importing 8/2 support Packages Note 492414 > nccL2von revised Note 350703 > OMGQcK: Error message ‘No release group exists’ S. Deletion of release strategies: ‘he cables 116%, TGV, 1265S. 126EC and r16EG may contain entries from previus Custonizing settings (Such as old release groups) hich were deleted in customizing but not in the tables. This creates an Inconsistency. To eliminate the ‘inconsistency. proceed as foTlows: make all the deleted release settings in customizing again, save then, and then delete ‘then in the FoTlowing sequence: 4. The release strategies 21 The relense indicators 3. The release codes 4. The release group 5. the corresponding class (transaction LO2) if a new one mas created for the new release strategies ‘Then use transaction SE16 to check whether the entries were deleted in the tables naned above. Stecute the check resort in customizing Ceransaction OMGOCK oF OMGSCR) and ensure that a red traffic light is not displayed. Also refer to SAP Note 380703. vou can use report RCCLZU08 to check the consistency as aTready mentioned in point 2. 6, changing the release strategy wien the syster is running: We strongly recommend that you do NoT change an existing release strategy that is in use or its indivicual elerents (release code(s), release status and so on), 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 recommendation, the following inconsistencies or prablens may occur. For example, if you cancel a release, this can result in the systen issuing error message ME 108 (No new release ‘indicator can be determined’). 1t 1s also possible that certain release statuses that had the documents concerned before the corresponding release strategies were changed. are no longer available after the change. This weans chat the docurents concerned are in an inconsistent release status In this case, the only solution is to explicitly trigger the determination of @ new release strategy for the docurent | solution | Manual Activities: | This document refers to SAP NotKBA re483900 Tiansnot of Release stimienles (OMGO.OMGS) A: lease staleginin te sonice eseting lsae ta teooy to aoe AG: loses Szatany Hakase pocade ach no aoa sate sand opin dantenton dts anaercent | This document is referenced by 2507 srs 493900 savas ‘lease sale os oak termed else sate evevedio CLIO buLnain cstenseng ‘lease sale ot detrinad fr PR a MES NIMES on BO a MEP UNME D208) [EXPERT WEBINAR Wan and esc cotanin asus in Release Slag fr Puchtsing Docume Resale lease ta at tok aca FAO: Rolease Staion el ence. Pen Prods ate unaad a Hal 40 AG: Hoease erties he sonien use ont io chase aa lesa ‘Senin lesion daa to anahe chant “Tansporlat Relate evataie (ONGO OMGS|