7059_TSCM_50-2ª_parte_(12-16)
96 pág.

7059_TSCM_50-2ª_parte_(12-16)


DisciplinaConsultoria737 materiais2.633 seguidores
Pré-visualização15 páginas
Release status
Requisn.
Item 10
Strategy S1
blocked
Create requisn.
Overview of the Business Process
 
 
 
„ The release strategy defines the release (clearance, approval or authorization) process. The strategy 
specifies the conditions under which a requisition or external purchasing document must be 
approved, the individuals or departments required to approve it and the sequence in which the 
approvals must be granted. 
„ The assignment of a release strategy to a purchase requisition is carried out automatically and is 
based on the release conditions. In the case of the procedure with classification, the conditions are 
defined using characteristic values and are stored in Customizing. If a requisition or an external 
purchasing document fulfills the conditions, the document has to be released in accordance with the 
release strategy. 
„ Each individual or department required to approve a requisition within the framework of a release 
strategy represents a release point. A release strategy can include up to eight such release points. A 
release point is identified by a two-character key (the release code). Each person involved in the 
release procedure signifies approval (gives the green light) using their release code. You can also 
cancel a previously effected release (that is, reset the original release status) using this code. 
„ The release indicator reflects the current release status. It is determined automatically and defines 
whether, for example, an RFQ or a PO can be created with reference to the item in question. 
 
© SAP AG TSCM50 14-10 
\uf8e9 SAP AG 2002
Definition of Release Criteria
Dictionary
Communication
structure
Plant
Mat. group
Item category
Acct. assgt. cat.
Value
...
Classification
 Definition of
 characteristic Definition of class
Customizing
Definition of 
 release group
Charact. PLANT
Charact. VALUE
Class FRBANF
Class type 032
Charact- : PLANT
eristics : VALUE
Release
group
01
Rel.
obj.
PReq.
Release
class
FRBANF
x
x
x
x
x
\u2022Multi-value
\u2022Ref. 
table field
\u2022Unformatted
\u2022Multi-value
\u2022Ref. 
table field
\u2022Unformatted
\u2022 Interval values
allowed
 
 
 
„ To be able to work with the release procedure with classification, you must create a release class 
with characteristics in addition to making the other Customizing settings. You set up a release class 
with characteristics via the classification system. 
„ The communication structures CEBAN (for purchase requisitions) and CEKKO (for external 
purchasing documents) contain all the fields that can be defined as release characteristics. If you 
have additional requirements, take advantage of the user exit made available by the SAP system. 
„ All release conditions must be defined as classification characteristics. Part of the characteristic 
definition is a link to a field of the communication structures CEBAN or CEKKO. The classification 
characteristics should have the attribute multi-value, so that you not only maintain the characteristic 
values as single values but also can enter several values, if necessary. For characteristics of the data 
type NUM or CURR, you should also allow interval values. 
„ You group together all characteristics that you wish to use in release strategies for purchase 
requisitions or external purchasing documents in a class. The class must be assigned to the class type 
032. You can define a class for purchase requisitions, a class for external purchasing documents, and 
a class for service entry sheets. The release class is assigned to the release object in Customizing (1 = 
purchase requisition, 2 = external purchasing documents, 3 = service acceptance). 
 
© SAP AG TSCM50 14-11 
\uf8e9 SAP AG 2002
Customizing the Release Procedure
Definition of release codes11
Rel. group
01
01
Rel. code
CO
TK
Workflow Description
Controlling
Technical
Definition of release indicators22
Rel. ind.
1
2
...
Description
Not released
Fixed
x
RFQ
x
PO
x
Field ref.
F203
Chgbl. Val. chg.
Definition of release strategy33
Release group 01, strategy S1
Release codes: CO, TKaa
Release
prerequisite
bb Release
statuses
cc Classificationdd
CO TK Rel. ind.
1 Not released
1 Not released
2 Released
x
x x
Char.
PLANT
VALUE
Value
1000, 2000
> 1000
 Code/prerequisite
CO TK
CO
TK x
 
 
 
„ You define release codes, release indicators, and release strategies in Customizing for Purchasing. A 
prerequisite for customizing a release strategy is the definition of release classes with release 
characteristics. 
„ The release code is a two-character key identifying a release point. Each person involved in the 
release procedure signifies approval in a release transaction using his or her release code. 
„ The release indicator reflects the current release status. Depending on the release indicator, specify 
whether it is possible to change documents that have been partially or completely released, or 
whether a document must pass through the release procedure all over again if it is changed. 
„ The release strategy defines the approval process. The definition of a release strategy comprises 
specification of the prerequisites for release points (that is the order in which the release points must 
signify approval), the release status, and the release conditions in the form of characteristic values for 
classification. 
„ Release strategies are uniquely identified via a four-character key. The first two characters of this 
key denote the release group, the last two the strategy. A release group must be assigned to a release 
object (for example, two equals purchasing documents) and a release class. 
 
© SAP AG TSCM50 14-12 
\uf8e9 SAP AG 1999
User Authorizations and Release Procedures
PReq
Release CO 9
TK 9
Controlling
Department
Technical Services
Department
User
authorizations
Authorization object
M_EINK_FRG
Value: CO
User
authorizations
Authorization object
M_EINK_FRG
Value: TK
Meyer Smith
Release CO Release TK
 
 
 
„ The authorization object Release code and group in Purchasing (M_EINK_FRG) determines which 
users can release requisitions and external purchasing documents with which release code. 
„ If you use the release procedure for purchase requisitions without classification, you must create 
authorizations for the authorization object Release code in purchase requisitions (M_BANF_FRG). 
 
© SAP AG TSCM50 14-13 
\uf8e9 SAP AG 2002
PReq.
Item 10
Starting situation Effect releases (signify approval)
+ + +
Release
point 1
o.k. 9
Release
point 3
o.k. 9
PReq.
Item 10
Individual release
PReq.
Item 10
Collective release
Release point
o.k. 9
Release point
o.k. 9
Strategy S1Strategy S1
blockedblocked
Release
point 2
o.k. 9
Release
point 4
o.k. 9
Convert requisitionConvert requisition
into RFQinto RFQ
Convert requisitionConvert requisition
into POinto PO
Release of Requisitions and Ext. Purchasing Docs.
 
 
 
„ Purchase requisitions can be released (cleared or approved) individually or collectively. If you use 
the collective procedure, you process all the requisitions awaiting release using your release code on 
the basis of a list. This method is recommended for frequent releases. 
„ The release (clearance or approval) of purchase orders, contracts, scheduling agreements, and so on 
is effected from a list. 
„ Only those documents that satisfy the release prerequisites can be released. 
„ Each release point involved in the release procedure must approve a document that is subject to 
release. In the course of the approval process, the release status of the document changes. This status 
is shown by the release indicator, which also governs the