Documente Academic
Documente Profesional
Documente Cultură
Attachments:16
Added by Guest, last edited by Guest on Jun 05, 2009 (view
change)
show comment
Go to start of metadata
RELEASE PROCEDURE
Contents:
RELEASE PROCEDURE
CHARACTERISTICS
Initial screen:
Description screen:
CLASS
Initial screen:
Keywords screen:
Characteristics screen:
TIPPS TO REMEMBER
Debugging
CHARACTERISTICS
Path: Logistics > Central Functions > Classification > Characteristic (old
transaction: CT01, please use CT04 for maintenance of characteristics)
Initial screen:
Characteristic name
Description
Charactistics Group
optional, can be used to group together characteristics
setup is done in configuration (transaction O042)
Status
mandatory , specifies if the characteristic can be used
set up is done in configuration (transaction O042)
Data type
mandatory
a pop-up will display after a value for the format of the data type was
entered
Heading
editable
Value assignment
single values
multiple values
restrictable
Control entry
Description screen:
Enter descriptions and column heading in different languages
single value
multiple values
restrictable (e.g., to validity intervals)
Values maybe set as default,
Value hierarchies are possible.
CLASS
Path: Logistics > Central Functions > Classification > Class (transaction
CL01/CL02/CL03)
Initial screen:
Class
Class type
Description
Statuso mandatory, specifies if the class can be used already
Class groupo optional, can be used to group related classeso set up in
configuration (transaction O043)
Keywords screen:
User may enter keywords which may help him to find the referring class via
search tools
Characteristics screen:
Enter the characteristics associated with this class
Release Group:
Release group: 2 digit code which combined with a 2 digit strategy code
makes up the final release strategy
1.
2.
3.
Release object:
- used for purchase requisitions
- used for purchase orders & other purchasing documents
- used for the acceptance of service entrysheets
Class:Only one release class can be used for a certain release object.
E.g., requisitions can use class FRG_EBAN, other purchasing documents class
FRG_EKKO, while the release of service entrysheets may refer to class FRG_ESSR.
As mentioned, with release 4.0, there was a change with respect to the release
of purchase requisitions. Now, overall release on header level and item-wise
release are both possible.To use BOTH kinds of release strategy in a system, two
different classes must be created. One class will use the field CEBAN-GFWRT as
characteristic for the overall release. The other class to be used for the itembased release will use the field CEBAN-GSWRT instead. Note that you can only
use ONE type of release for each specific document type. To assign this correctly
during the configuration of a system, the document type to be used for overall
releases must have the overall release flag set (as depicted above).After having
set this flag, this document type will only look at the overall release strategy,
otherwise, the item-based release strategy will be used.Secondly, in the release
strategy configuration the two different classes to be used have to be set up as
well: one for overall releases, the other will again be used for the item-based
strategies.
Release code:
Release strategy:
The complete strategy is the combination of the release group and the
release code itself, each of them consisting of a 2 digit code.
Example: XX YY, here XX denotes the release group while YY
indicates the release code.
On the details screen, the release code(s) assigned to this strategy can
be entered. In addition, the release prerequisites must be set as
well as the release statuses and the values for the characteristics of
the assigned release class.
Workflow:
Using this option, roles maybe assigned to any of the release group/code
combinations.
10
20
30
In this example, release code 10 must be applied before release codes 20 and
30, and the release with code 20 must be executed before finally applying code
30.Release statuses:
The release status of a document is further specified by the release indicator.
This indicator may specify whether a document is, e.g., blocked, fixed against
MRP runs, or whether follow-on documents maybe created. This is illustrated by
another example for the three-step release procedure:
10
20
x
x
30
Release Indicator
S - Blocked
x
S - Blocked
x
ValueCEBAN-GSWRT
FRG_EBAN
100.00 USD - 500.00 USDCEBAN-
001
TIPPS TO REMEMBER
A release strategy cannot be used WITHOUT classification and WITH
classification at the same time. If there is any entry present in Release
Group table (T16FG-FRGOT), only releases WITH classification can be used.
Do not use hyphens for class names, instead, it is better to use an underscore.
When setting up the release indicators on the 'status' screen, the sequence
should start with a BLOCKED status and end with 'RELEASED for ORDER'. If
there is no 'RELEASED for ORDER' as last status, the user will be prompted
the warning message ME167: 'Please check release statuses'.
In the case of contracts, the target value is used for the release strategy
determination instead of the contract net value. With note 116685, this
logic has been enhanced considerably: If you maintain a target value in
the contract header, this value is set in field CEKKO-GNETW to determine a
possible release strategy. If no target value exists on header level, an
aggregation of the target values of the items is carried out instead.
header level, the release strategy is not assigned until the document is
saved. There is a check function which can be used to determine the
strategy before the document is saved.
Once a release strategy has been determined for purchasing documents (other
than requisitions) without any approval yet, any output conditions
assigned to the document will not be displayed on the message screen
until the release is approved. This is due to the fact that these documents
are blocked for printing intentionally.
For purchasing documents other than requisitions, item level fields such as
plant and material group which are used for strategy determination, will
be aggregated to the header level. E.g., for a certain release scenario, the
user wants to use the plant as one of the characteristics. If all items do
NOT belong to the same plant, one has to have a blank value as one of the
allowed values for a strategy to be selected. In addition, if all items belong
to the SAME plant, then this plant will aggregate to the header, if they are
not identical, a blank value will be passed to the header (please cf. note
47089 for further information).
If interval values shall be used for a certain characteristics, the 'multiple value'
flag must be set accordingly.
Regarding releases, there are differences between transaction ME54N & ME55:
ME54N is meant to be used for the interactive release OR change of a
requisition within the same one-screen-transaction environment as for
ME51N/ME52N/ME53N, while ME55 is meant for release purposes only. If
you only want to see requisitions which are subject to a particular release,
please use ME55.
Note 116685 contains an advance correction for lower mature releases (<45A)
to allow the system to use the total item value of a contract or scheduling
agreement for the determination of a release strategy if the target value is
blank.
Note 329898 - Customer exit revised for purchase order release process.
Note 303426 - Release strategy wrongly determined for purchasing documents.
Note 186809 - OMGQ/CL24: Inconsistency for release strategy class
Note 200204 - Release of purchasing documents: Problem with customer exit
Note 209470 - Purchasing documents: Release strategy for exchange rate
chances
Debugging
Purchase requisitions:
Program LEBNDU04 Function: ME_REL_STRATEGY_REQUISITION
Determines whether an item-based release or an overall release is used.\
ELSE.
IF I_EVENT EQ REL_POS.
E_EBAN = I_EBAN_NEW.
"??????????
ELSE.
IF NOT I_EBAN_NEW IS INITIAL AND T_GEBAN_NEW[]
IS INITIAL.
*... I_EBAN_NEW wird bei automatischen Banfen, z.B. aus
der Dispo, ...*
*... nicht gefllt, da nur eine Position bergeben
wird ..............*
T_GEBAN_NEW = I_EBAN_NEW.
APPEND T_GEBAN_NEW.
IF NOT I_EBKN_NEW IS INITIAL AND
"128075
T_GEBKN_NEW[] IS INITIAL.
"128075
T_GEBKN_NEW = I_EBKN_NEW.
"128075
APPEND T_GEBKN_NEW.
"128075
ENDIF.
"128075
ENDIF.
*... Strategieermittlung fr Gesamtwerte der Banf Gesamtfreigabe ...*
CALL FUNCTION 'ME_REL_GENERAL_STRATEGY_EBAN'
EXPORTING
I_CHANGE_OK = I_CHANGE_OK
I_XCLASS = I_XCLASS
IMPORTING
E_RESET
= E_RESET
E_EBAN
= E_EBAN
TABLES
T_GEBAN_NEW = T_GEBAN_NEW
T_GEBAN_OLD = T_GEBAN_OLD
T_GEBKN_NEW = T_GEBKN_NEW
T_GEBKN_OLD = T_GEBKN_OLD
EXCEPTIONS
OTHERS
= 0.
Program: LEBNDU01 - ME_REL_STRATEGIE_EBAN (for item-based
releases)
*- Verfahren bestimmen
------------------------------------------------CLEAR xclass.
IF i_xclass NE space.
SELECT * FROM t16fg WHERE frgot EQ '1'
AND frgfg EQ space.
xclass = 'X'.
EXIT.
ENDSELECT.
ENDIF.
IF xclass EQ space.
*
*... Prfen, ob sich an der Banf berhaupt was ge?ndert
hat ..........*
CHECK e_eban NE i_eban_old OR
"H101541
i_ebkn_new NE i_ebkn_old.
"H101541
*
CLEAR *ceban.
IF xchange NE space.
f1 = i_eban_old-menge * i_eban_old-preis
/ i_eban_old-peinh / 1000.
*ceban-gswrt = f1.
ENDIF.
PERFORM strategie_alt USING i_eban_new e_eban-frggr
e_eban-frgst.
ELSE.
PERFORM ceban_aufbauen USING i_eban_new
i_eban_old
strategies
are found.
EXIT.
ENDIF.
Purchase Orders:Program MM06EF0S_STRATEGIE_CEKKO: (if note
329898 is applied)
LEBNDF01:
Rel_strategie_werte
*- Wahrungsabhangiges Merkmal
-----------------------------------------*
IF merkmale-atfor EQ 'CURR'.
cwaers = xcabn-msehi.
"ob das so bleibt ?
MOVE <f1> TO refefw.
IF fwaers NE space AND hwaers NE space.
*- Bestellanforderungen, die nicht der Gesamtfreigabe
unterliegen -----*
*
IF fwaers NE hwaers.
"120688
*- Fremdw?hrung -> Hausw?hrung
----------------------------------------*
IF fwaers NE hwaers.
CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
EXPORTING
*
date
= bbedat
date
= sy-datum
foreign_amount = refefw
foreign_currency = fwaers
local_currency = hwaers
rate
= bwkurs
IMPORTING
local_amount
= refew.
refefw = refew.
ENDIF.
IF hwaers NE cwaers.
*------- Hauswahrung -> Merkmalswahrung
------------------------------*
CALL FUNCTION 'CONVERT_TO_FOREIGN_CURRENCY'
EXPORTING
date
= sy-datum
foreign_currency = cwaers
local_amount
= refefw
local_currency = hwaers
IMPORTING
foreign_amount = refew.
refefw = refew.
ENDIF.
ENDIF.
*- Nachkommastellen der Whrung bercksichtigen
-----------------------*
IF tcurx-currkey NE cwaers.
SELECT SINGLE * FROM tcurx WHERE currkey EQ
cwaers.
IF sy-subrc NE 0.
tcurx-currkey = cwaers.
"106107
tcurx-currdec = 2.
ENDIF.
ENDIF.
MOVE refefw TO xcomw-atflv.
MOVE refefw TO xcomw-slflv.
DO tcurx-currdec TIMES.
xcomw-atflv = xcomw-atflv / 10.
xcomw-slflv = xcomw-slflv / 10.
ENDDO.
APPEND xcomw.
ELSE.
*- Datum --------------------------------------------------------------*
IF merkmale-atfor EQ 'DATE'.
MOVE <f1> TO hdat-date.
MOVE hdat TO xcomw-atflv.
MOVE hdat TO xcomw-slflv.
APPEND xcomw.
*- sonstiges numerisches Merkmal
--------------------------------------*
ELSE.
MOVE <f1> TO xcomw-atflv.
xcomw-atflv = xcomw-atflv.
MOVE <f1> TO xcomw-slflv.
xcomw-slflv = xcomw-slflv.
APPEND xcomw.
ENDIF.
ENDIF.