‘493900 - FAQ: Release Strategy Component MM-PUR-GF-REL Rese (Aoprova), Version 13, Releases On 18.12.2013 1 sympton Faq Release strategy List of questions = 1, why can T wodify a purchase requisition although T set the changeabiTity of the release indicator to "1" (cannot be changes")? 2. 15 4% possible to modsfy the overall release status (J_TIG1-G5FR) of the decunent type for a purchase requisitton?aty 4s the database table field overall release of purchase requisitions (GEAN-GSFRG) set 4s overall whereas the iter 1s subject fo an itenrnise release strategy? 3. why is the release strategy not reset? 4. thy 48 the release strategy not determined? 5. Why 45 there no release strategy deternination for the quotations (HF47)? Why does the systen not display the purchase requisition T double-click on with MESS (scope of Tist 7 Why can x not select several purchase requisitions with MESS and scope of ist ALY orf? Why 45 the database table ekko not updated when T use transaction MEZE to release purchase orders? What authority check 4s performed with release transactions ME25\ and MESEN? 10. Why do £ have to switch to change mode in order to release with transaction MESAN? 11. Is it possible to create 2 purchase order with reference to a purchase requisition not yet released?rs it possible to create a purchase order with reference to a request of quotation not yet released? 12, Ts st possible to cancel a release strategy wien the purchase order has been printed out? 13. Hom 4s the currency converted? 14. can T use a blank characteristic s0 that this characteristic will not be considered during the release stratesy 15. why can 1 not Input more that 999 entries for a characteristic Tike cost center (KOStL)? 16. why Vs there no release strategy determination when a program changes in background & purchasing docusent which corresponds ‘co the classification of a release strategy? I other Terms aq nelease strategy | Reason and prerequisites Faq Release Strategy | solution 1, question: Wy can X modify a purchase requisition aTthough 1 set the changeabiity of the release indicator to 1" (cannot be changed”)? ‘the purchase requisition is not modifiable via a purchasing transaction Ike ME52 or MESZN. aut (¢ 1s possible to change the purchase requisition fro any other external application Tike sales order, planned order, maintenance order or network ‘the changeabi ity functionality only concerns the purchasing transactions. this 15 intended and a new release strategy determination cakes place if there is a Modification of the data in che external application. 2. question : 15 48 possible to modify the overall release status (V_TI61-cS°R0) of the document type for 4 purchase requisition? Wy {s'the database table field overall release of purchase requisitions (EBaN-csfRa) set as overall whereas the item is subject to fn tterrise release steategy?‘SAP does not recommend to modify the overall release status (V_TIG1-GSFRG) of the document type for a purchase requisition (custow'zing ~ transaction O4€8) ‘ne risk is to create inconsistencies in database table EEA IF a purchase requisition fs subject co an overall release strategy and you change the docurent type fron overall to ftenenise release, the system can determine an itenmise release strategy when you modify ane Item with MES2. This ‘ter 1s now subject to a Single release strategy when all other itens are stil] subject to the fooer overall release strategy. And the averall release flelé (eans-asene) is stiT] set as overall for aT? itens 4f you do the sane change with MES2N, the ‘ters not modified are no longer subject to the former overall release strategy 2nd E8AN- rte is set as itenowise for all ivens. gut the reavisition processing state (C2AN-AANPR) renains in status release completed (08) For the Stens not most fied. 3. question + iy is the release strategy not resee? ‘A reset of the release strategy only takes place 1f + the changeabiTity of the release incfcator is set to '4° in case of a purchase requisition and °4" or '6" in case of another purchasing cocunent (purchase order, request for quotation, contract, scheduling agreenent) 1+ the docunent {5 stfTl subject to the previous release strategy. 4 the nen TOTAL NEY ORDER VALUE 5 higher than the olé one, ‘he total ret order value is Tinked to CEHKO-cNEIW for 2 purchase order, CEBAN-cSWRI for 2 purchase requisition item-wise release and ctamy-atat for a purchase requisition overall release. If you have waintaines a Tolerance for value changes éuring release (V_I6IS-TLFAE), the release strategy is reset when the value of ‘the cocurent is higher than the percentage you have specified and if the docurent is stiT1 subject to the previous release strategy 4 question + Why 15 the release strategy not determined? lease check the Following points + You can not use Release without classification and Release with classification, 16 hare 3 an entry present in Release Group table (TIGFG-FRGOT) only release With classification can be Used + TF you use version managenent, the detersination of the release strategy starts when the version is completed vou complete a version by setting the "version completed” Sndicator in the version ab, + cost canter values (CEBAN-KOSTL) and Vendor Values (CEBAN-LZFNA) In the release strategy characterlstics should be entered with leading zeros: This 15 true for the other structures as well (CKO and CESSR). See note 52225 + For OVERALL RELEASE (purchase order and purchase requisition) the ‘zen fields such as Plant and Material croup wiTl be aggregated to header Tevel. Far example you use Plant as one of your characteristics. rf alll items do not belong to the sane plant then the relase stratesy wilt not be found unless you have maintained a blank value as one of your alloed values for the characteristic plane. If all ‘eens belong to the sane plant then that plant 1s aggregated to the header’ if ane or nore 1s different then a blank is aggregated to the header. See note 47089, + AF you use a release user exit to derive the conmunication structure the following statenents must be in the code (see note S786): + E_CEHAN = FcEeaN (EXIT_SAPLEENO_0O1 and EXIT_sAPBELNO_004) + ELcERKO = TceeRo (ExTT_SAPLERNO 002) 5. question Why 1s there no release strategy for the quotations 7)? ‘The release strategy deterwination takes only place when you rodify the request of quotation via HEA2. 5. question : Why does the system not display the purchase requision 1 double click on with MESS (scope of Tist A)? af you have previously selected one or several docunents the progran determines the first docunant selected and not necessary the one you eouble click on. the purchase requisitions will be displayed one after the other and to do so each purchase requisition displayed 4s ceselected fn the other hand, if ro docunent is marked, the systen displays the docurent you double click on because the program selects the document according 0 the position of the curser and not the mark7. Question Why can I not select several purchase requisitions with MESS and scope of Tist ALV grid? ‘As from release 470, you can use scope of list ALV grid mith MESS, This constitutes 4 new design and was developped in order to achieve accessibility requirements. It mas not the aim to guarantee absolute identical functionning as with the other scopes. the behaviour 15 wore user-friendly than with the old scope of Vist With scope of 11st ALV grid tt 1s no longer possible to select several purchase requisitions and release thes 211 together. this was done on purpose and the user should release the documents without the checkbox selection. 8, question hy 15 the database table ekko not updated when 1 use transaction MEZB to release purchase orders? First check that the transaction/event key (¥orga) for MEZS Jn pooled table 1260 (SAP Transaction control, Purchasing) is EF ‘then check 4 4 commit work ina user-exst does not interfere with lopie of transaction ME2S. 3. question what authority check 45 perforned with release transactions ME29N and MES4N? With the Release Purchase order (ME29N) and Release Purchase Requisition (HESEN) transactions, an AUTHORIZED person can isplay/change the current version of the docusent and effect release with his release codes. ‘na authority check is performed on object *LEINK AG for both transactions ME2ON and MESAN. Wich the authorization object M_EIN_PRG, you can determine which purchasing documents the user way release via the release group (FAGGRD and nivich release codes (FREED) he may use When coing 50. ‘the authorization object LEANF_FAG enables you to restrict the release of purchase requisitions via the release cade (FRECD). 10. question = Why 60 T have to switch to change mode in order to release with transaction MESAN? Winen you select with WESEN a purchase requisition that cannot be released the system switches to display node and if then you seTect Change node by licking on the change/O%eplay button (7). 11. question: 4s it possible to create 2 purchase order with reference to 2 purchase requisition not yet released? Is it possible to create a purchase order with reference to a request of quotation not yet released? 1€ 1s not possible to create a purchase order if the referenced purchase requisition is not released. aut the system aTTons you to put the purchase order on hold and then release the purchase requisition. (the other hand you can create a purchase order with reference to an unreleased request of quotation. 12. question : 4s it possible to cancel a release strategy when the purchase order has been printed out? With m20" you cannot cancel a release strategy once the docunent has been printed out. This behaviour constitutes a new design Regarding MEZS ie has been decided to keep the old behaviour and you can cancel the release if there 1s no message (90 NAST record) or at Teast one message which has not been printed out. 13, question ow fs. the currency converted? ‘the header currency {s converted to local currency (eonpary code currency) and then the Tocal currency is converted to the characteristic currency, 4. question can 1 use a blank characteristic so that this characteristic mill not be considered curing the release strategy determination?‘Unfortunately there is no mechanism like entering a blank or * in order to make classification understand this characteristic is not relevant ‘he characteristic and its values wit always been taken sn consideration sn case you use a ‘non-aggregated’ Feld in your reTease strategy you need to enter a1? possible values for the corresponding characteristic (as a range ~ just In case of muperic characteristics) ‘Goample: vou use icerwise release strategy for purchase requisitions and the plant is used in the release strategy (characteristic Lass-Wenes). Release strategy determination wiTl e processed item by Tes. there will alWays be just one value for the plant (From ‘the current tan), multiple values ané thus 2qgregation is not possible, In this case you have to enter 211 possible values for the ‘characteristic CEAAN-HERKS. In case you use an ‘agpregated" field in your release strategy (which is possible for overall release strategy for PRs and release ‘strategy for 0s) and multiple values are used for that field on a purchasing docunent, you can use a blank value for the corresponding characteristic if you'd like the release strategy be applied ‘ample: You use release strategy for 2 PO and the plant 15 one of the relevant Fielés (characteristic CERKO-WERKS). You enter 2 ‘First #o ite with plart 0001 and a second item with plant 0002. since there are multiple values for the plant the systen wiTl ‘aggregate’ to blank value and use lark value for searching for a release strategy, since you have maintained a Blark valve for characteristic CEAKO-WERKS the system wiTT find the corresponding release strategy. 1m ehis case please pay attention to rote 752565 4 causes an error in case Blank values are used for release strategies even when the Tong ext just talks about process orders the impact of the side effect is more general please take care note 7S4178 is inplenented, it corrects note 752566, 15, question = ry can X not Input more that 999 entries for a characteristic Tike costeenter (KOS)? ‘The cost center field ( cEBAN-KOSTL) Is defined as a GUAR Field and alsothe reference characteristic for this fleld has 2 cHAR format. therefore you can only assign Tess than 999 values (See nate 534226), 18, question = Why is there no release strategy determination when a progran changes in background a purchasing document which corresponds te the classification of a release strategy? ‘inis 15 the system Gesign that a release strategy determination can only be triggereé through a user action and not by changes wade ‘in background process. If you create a document (e.g. 0, Contract, ete), the determination of the release strategy takes place only in case of 2 user event ‘ike checking or saving the document | Manual Activites | Software Components conn Conn stn aon ae oon cao wan wan cose| Support Package SAP_APPL AG saps | This document rotors to | This document is referenced by overs Resragesaeasestseny whan cos cone changed as anerra) utile catenin in chat oso relate selany needed be subject tleave satiny even terse locked (LOEKZ = 8 Wht ols ae checked fr cae stalag for PONGanvac, ‘elton of PR dos notes no olen satan, lass aetna opon aa alae a EZ Relase ata not accsacon in uchase ea contac sche oceans, FAO Release sates in ponaing