1. Why can I modify a purchase requisition although I set the changeability of the release indicator to '1' ('Cannot be changed')?

Transcription

1 Nte Language: English Versin: 10 Validity: Valid Since Summary Symptm FAQ Release Strategy List f questins : 1. Why can I mdify a purchase requisitin althugh I set the changeability f the release indicatr t '1' ('Cannt be changed')? 2. Is it pssible t mdify the verall release status (V_T161-GSFRG) f the dcument type fr a purchase requisitin? Why is the database table field Overall release f purchase requisitins (EBAN-GSFRG) set as verall whereas the item is subject t an item-wise release strategy? 3. Why is the release strategy nt reset? 4. Why is the release strategy nt determined? 5. Why is there n release strategy determinatin fr the qutatins (ME47)? 6. Why des the system nt display the purchase requisin I duble click n with ME55 (scpe f list F)? 7. Why can I nt select several purchase requisitins with ME55 and scpe f list ALV grid? 8. Why is the database table ekk nt updated when I use transactin ME28 t release purchase rders? 9. What authrity check is perfrmed with release transactins ME29N and ME54N? 10. Why d I have t switch t change mde in rder t release with transactin ME54N? 11. Is it pssible t create a purchase rder with reference t a purchase requisitin nt yet released? Is it pssible t create a purchase rder with reference t a request f qutatin nt yet released? 12. Is it pssible t cancel a release strategy when the purchase rder has been printed ut? 13. Hw is the currency cnverted? 14. Can I use a blank characteristic s that this characteristic will nt be cnsidered during the release strategy determinatin? 15. Why can I nt input mre that 999 entries fr a characteristic like cst center (KOSTL)? Page 1 f 8

2 16. Why is there n release strategy determinatin when a prgram changes in backgrund a purchasing dcument which crrespnds t the classificatin f a release strategy? Mre Terms FAQ Release Strategy Cause and Prerequisites FAQ Release Strategy Slutin 1. Questin : Why can I mdify a purchase requisitin althugh I set the changeability f the release indicatr t '1' ('Cannt be changed')? The purchase requisitin is nt mdifiable via a purchasing transactin like ME52 r ME52N. But it is pssible t change the purchase requisitin frm any ther external applicatin like sales rder, planned rder, maintenance rder r netwrk. The Changeability functinality nly cncerns the purchasing transactins. This is intended and a new release strategy determinatin takes place if there is a mdificatin f the data in the external applicatin. 2. Questin : Is it pssible t mdify the verall release status (V_T161-GSFRG) f the dcument type fr a purchase requisitin? Why is the database table field Overall release f purchase requisitins (EBAN-GSFRG) set as verall whereas the item is subject t an item-wise release strategy? SAP des nt recmmend t mdify the verall release status (V_T161-GSFRG) f the dcument type fr a purchase requisitin (custmizing - transactin OMEB). The risk is t create incnsistencies in database table EBAN. If a purchase requisitin is subject t an verall release strategy and yu change the dcument type frm verall t item-wise release, the system can determine an item-wise release strategy when yu mdify ne item with ME52. This item is nw subject t a single release strategy when all ther items are still subject t the frmer verall release strategy. And the verall release field (EBAN-GSFRG) is still set as verall fr all items. If yu d the same change with ME52N, the items nt mdified are n lnger subject t the frmer verall release strategy and EBAN-GSFRG is set as item-wise fr all items. But the requisitin prcessing state (EBAN-BANPR) remains in status release cmpleted (05) fr the items nt mdified Page 2 f 8

3 3. Questin : Why is the release strategy nt reset? A reset f the release strategy nly takes place if - the changeability f the release indicatr is set t '4' in case f a purchase requisitin and '4' r '6' in case f anther purchasing dcument (purchase rder, request fr qutatin, cntract, scheduling agreement), - the dcument is still subject t the previus release strategy, - the new TOTAL NET ORDER VALUE is higher than the ld ne. The ttal net rder value is linked t CEKKO-GNETW fr a purchase rder, CEBAN-GSWRT fr a purchase requisitin item-wise release and CEBAN-GFWRT fr a purchase requisitin verall release. If yu have maintained a Tlerance fr value changes during release (V_161S-TLFAE), the release strategy is reset when the value f the dcument is higher than the percentage yu have specified and if the dcument is still subject t the previus release strategy. 4. Questin : Why is the release strategy nt determined? Please check the fllwing pints : Yu can nt use Release withut classificatin and Release with classificatin. If there is an entry present in Release Grup table (T16FG-FRGOT) nly release with classificatin can be used. If yu use versin management, the determinatin f the release strategy starts when the versin is cmpleted. Yu cmplete a versin by setting the "versin cmpleted" indicatr in the versin tab. Cst Center values (CEBAN-KOSTL) and Vendr values (CEBAN-LIFNR) in the release strategy characteristics shuld be entered with leading zers. This is true fr the ther structures as well (CEKKO and CESSR). See nte Fr OVERALL RELEASE (purchase rder and purchase requisitin) the item fields such as Plant and Material Grup will be aggregated t header level. Fr example yu use Plant as ne f yur characteristics. If all items d nt belng t the same plant then the relase strategy will nt be fund unless yu have maintained a blank value as ne f yur allwed values fr the characteristic Plant. If all items Page 3 f 8

4 belng t the same plant then that plant is aggregated t the header; if ne r mre is different then a blank is aggregated t the header. See nte If yu use a release user exit t derive the cmmunicatin structure the fllwing statements must be in the cde (see nte ): - E_CEBAN = I_CEBAN (EXIT_SAPLEBND_001 and EXIT_SAPBELND_004) - E_CEKKO = I_CEKKO (EXIT_SAPLEBND_002) 5. Questin : Why is there n release strategy fr the qutatins (ME47)? The release strategy determinatin takes nly place when yu mdify the request f qutatin via ME Questin : Why des the system nt display the purchase requisin I duble click n with ME55 (scpe f list F)? If yu have previusly selected ne r several dcuments the prgram determines the first dcument selected and nt necessary the ne yu duble click n. The purchase requisitins will be displayed ne after the ther and t d s each purchase requisitin displayed is deselected. On the ther hand, if n dcument is marked, the system displays the dcument yu duble click n because the prgram selects the dcument accrding t the psitin f the cursr and nt the mark. 7. Questin : Why can I nt select several purchase requisitins with ME55 and scpe f list ALV grid? As frm release 470, yu can use scpe f list ALV grid with ME55. This cnstitutes a new design and was develpped in rder t achieve accessibility requirements. It was nt the aim t guarantee abslute identical functinning as with the ther scpes. The behaviur is mre user-friendly than with the ld scpe f list. With scpe f list ALV grid it is n lnger pssible t select several purchase requisitins and release them all tgether. This was dne n purpse and the user shuld release the dcuments withut the checkbx selectin Page 4 f 8

5 8. Questin : Why is the database table ekk nt updated when I use transactin ME28 t release purchase rders? First check that the transactin/event key (vrga) fr ME28 in pled table T160 (SAP Transactin Cntrl, Purchasing) is EF. Then check if a cmmit wrk in a user-exit des nt interfere with lgic f transactin ME Questin : What authrity check is perfrmed with release transactins ME29N and ME54N? With the Release Purchase Order (ME29N) and Release Purchase Requisitin (ME54N) transactins, an AUTHORIZED persn can display/change the current versin f the dcument and effect release with his release cdes. An authrity check is perfrmed n bject M_EINK_FRG fr transactin ME29N and bject M_BANF_FRG fr transactin ME54N. With the authrizatin bject M_EINK_FRG, yu can determine which purchasing dcuments the user may release via the release grup (FRGGR) and which release cdes (FRGCO) he may use when ding s. The authrizatin bject M_BANF_FRG enables yu t restrict the release f purchase requisitins via the release cde (FRGCD). 10. Questin : Why d I have t switch t change mde in rder t release with transactin ME54N? When yu select with ME54N a purchase requisitin that cannt be released the system switches t display mde and if then yu select a releasable purchase requisitin the system keeps the display mde due t technical reasns. Cnsequently yu have t switch t Change mde by clicking n the Change/Display buttn (F7). 11. Questin : Is it pssible t create a purchase rder with reference t a purchase requisitin nt yet released? Is it pssible t create a purchase rder with reference t a request f qutatin nt yet released? Page 5 f 8

6 It is nt pssible t create a purchase rder if the referenced purchase requisitin is nt released. But the system allws yu t put the purchase rder n hld and then release the purchase requisitin. On the ther hand yu can create a purchase rder with reference t an unreleased request f qutatin. 12. Questin : Is it pssible t cancel a release strategy when the purchase rder has been printed ut? With ME29N yu cannt cancel a release strategy nce the dcument has been printed ut. This behaviur cnstitutes a new design. Regarding ME28 it has been decided t keep the ld behaviur and yu can cancel the release if there is n message (n NAST recrd) r at least ne message which has nt been printed ut. 13. Questin : Hw is the currency cnverted? The header currency is cnverted t lcal currency (cmpany cde currency) and then the lcal currency is cnverted t the characteristic currency. 14. Questin : Can I use a blank characteristic s that this characteristic will nt be cnsidered during the release strategy determinatin? Unfrtunately there is n mechanism like entering a blank r * in rder t make classificatin understand this characteristic is nt relevant. The characteristic and its values will always been taken in cnsideratin. In case yu use a 'nn-aggregated' field in yur release strategy yu need t enter all pssible values fr the crrespnding characteristic (as a range - just in case f numeric characteristics). Example: Yu use item-wise release strategy fr purchase requisitins and the plant is used in the release strategy (characteristic CEBAN-WERKS). Release strategy determinatin will be prcessed item by item. There will always be just ne value fr the plant (frm the current item), multiple values and thus aggregatin is nt pssible. In this case yu have t enter all pssible values fr the characteristic CEBAN-WERKS. In case yu use an 'aggregated' field in yur release strategy (which is pssible fr verall release strategy fr PRs and release strategy fr POs) Page 6 f 8

7 and multiple values are used fr that field n a purchasing dcument, yu can use a blank value fr the crrespnding characteristic if yu'd like the release strategy be applied. Example: Yu use release strategy fr a PO and the plant is ne f the relevant fields (characteristic CEKKO-WERKS). Yu enter a first PO item with plant 0001 and a secnd item with plant Since there are multiple values fr the plant the system will 'aggregate' t blank value and use blank value fr searching fr a release strategy. Since yu have maintained a blank value fr characteristic CEKKO-WERKS the system will find the crrespnding release strategy. In this case please pay attentin t nte It causes an errr in case blank values are used fr release strategies Even when the lng text just talks abut prcess rders the impact f the side effect is mre general. Please take care nte is implemented, it crrects nte Questin : Why can I nt input mre that 999 entries fr a characteristic like cstcenter (KOSTL)? The cst center field ( CEBAN-KOSTL) is defined as a CHAR field and alsthe reference characteristic fr this field has a CHAR frmat. Therefre yu can nly assign less than 999 values (see nte ). 16. Questin : Why is there n release strategy determinatin when a prgram changes in backgrund a purchasing dcument which crrespnds t the classificatin f a release strategy? This is the system design that a release strategy determinatin can nly be triggered thrugh a user actin and nt by changes made in backgrund prcess. If yu create a dcument (e.g. PO, Cntract, etc), the determinatin f the release strategy takes place nly in case f a user event like checking r saving the dcument. Header Data Release Status: Released fr Custmer Released n: :12:11 Master Language: English Pririty: Recmmendatins/additinal inf Categry: FAQ Page 7 f 8

8 Primary Cmpnent MM-PUR-GF-REL Release (Apprval) Valid Releases Sftware Cmpnent Release Frm Release SAP_APPL 45 45B 45B SAP_APPL 46 46B 46B SAP_APPL 46C 46C 46C SAP_APPL SAP_APPL SAP_APPL T Release and Subsequent Supprt Packages Supprt Packages Release Package Name SAP_APPL 45B SAPKH45B51 SAP_APPL 46B SAPKH46B39 SAP_APPL 46C SAPKH46C31 Related Ntes Number Shrt Text ME28 - release reset fr already utputted POs FAQ: Release strategies in purchasing Page 8 f 8