The release strategy defines the approval process for purchase requisitions. The strategy specifies the release codes with which a complete purchase requisition or a requisition item must be released (approved) and the sequence in which approvals have to be given. You can assign a maximum of eight release codes to the release strategy.The assignment of the release strategy to a complete purchase requisition or a requisition item is based on the release conditions.
If the release strategy assignment process is carried out on an item-by-item basis, a single purchase requisition can contain items with different strategies. The individual items can thus be released separately for the issue of RFQs or POs.Release strategies KF and TF have been defined.
Release Code
The release code (denoting a release point) is a two-character ID allowing a person to process a requisition item. The release codes are defined in the Customizing facility of Purchasing and assigned to the release strategy. Who may work with which release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
The assignment of a release codes to processors (processing staff members) can additionally be defined as follows:
Organizationally In this case, the relevant department stipulates which users will be working with which release codes..With organizational release codes, a purchase requisition item can be released or the release cancelled.
In Customizing In this case, there must be a linkage with SAP Business Workflow. You must define the release codes for which Workflow is to automatically determine the responsible processor. These release codes are designated as workflow-relevant. A processor ID is assigned to the workflow-relevant release codes. The processor assignment can be carried out directly or indirectly:
Directly The processor is a user name.
Indirectly The processor ID is a job or a position, for example. At the runtime, the system then determines the responsible processing staff member. Jobs are general work areas within an enterprise that are described by tasks (e.g. Executive Board).Positions are to be understood as planned employees and can, for example, be held by a user. E.g. position of Sales Manager (held by user SEAGOON).With workflow-relevant release codes, refusal is possible in addition to release and cancellation of release.An individual release strategy can comprise both organizational and workflow-relevant release codes.The organizational release codes T1 and T2 (Technical Services) and the workflow relevant release codes KY (Sales Manager) and EX (Executive Board) have been
defined.
Release Prerequisites
The release prerequisites indicate the sequence in which a complete purchase requisition or requisition item must be approved via the release codes. The release prerequisites are defined in Customizing for Purchasing (in the release strategy).
Release strategy KF (purchase orders up to $10,000)
With the two-step release strategy KF, release by either T1 or T2 is the prerequisite for release with KY. That is to say, a member of the Technical Services staff (T1 or T2) must release the requisition item before the more senior level of Sales Manager (KY).
Release strategy TF (purchase orders above $10,000)
Release strategy TF basically corresponds to the strategy KF. However, the requisition item must additionally be released by a member of the Executive Board (release code EX). A prerequisite for release by EX is release by the Sales Manager (release code KY).
Release Indicator
When a complete requisition or a requisition item has been processed via a release code, a release indicator is assigned to it. The latter shows whether:
The requisition can be changed by materials planning and control
An RFQ referencing the item can be created
A PO referencing the item can be issued
Purchasing can change the quantity or the delivery date
The item can be changed subsequent to the start of the release procedure You define when the system sets which release indicator in Customizing for Purchasing under "Set Up Procedure with Classification".Release indicators for strategy KF:
An RFQ or a PO referencing the requisition item can be created if releases have been effected by T1 or T2 and then with KY. Release indicators for strategy TF:
RELATED POSTS
WORK FLOW IN MM PART 3
MySAP environment security solutions
SAP authorization and client administration in mysap.com
If the release strategy assignment process is carried out on an item-by-item basis, a single purchase requisition can contain items with different strategies. The individual items can thus be released separately for the issue of RFQs or POs.Release strategies KF and TF have been defined.
Release Code
The release code (denoting a release point) is a two-character ID allowing a person to process a requisition item. The release codes are defined in the Customizing facility of Purchasing and assigned to the release strategy. Who may work with which release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
The assignment of a release codes to processors (processing staff members) can additionally be defined as follows:
Organizationally In this case, the relevant department stipulates which users will be working with which release codes..With organizational release codes, a purchase requisition item can be released or the release cancelled.
In Customizing In this case, there must be a linkage with SAP Business Workflow. You must define the release codes for which Workflow is to automatically determine the responsible processor. These release codes are designated as workflow-relevant. A processor ID is assigned to the workflow-relevant release codes. The processor assignment can be carried out directly or indirectly:
Directly The processor is a user name.
Indirectly The processor ID is a job or a position, for example. At the runtime, the system then determines the responsible processing staff member. Jobs are general work areas within an enterprise that are described by tasks (e.g. Executive Board).Positions are to be understood as planned employees and can, for example, be held by a user. E.g. position of Sales Manager (held by user SEAGOON).With workflow-relevant release codes, refusal is possible in addition to release and cancellation of release.An individual release strategy can comprise both organizational and workflow-relevant release codes.The organizational release codes T1 and T2 (Technical Services) and the workflow relevant release codes KY (Sales Manager) and EX (Executive Board) have been
defined.
Release Prerequisites
The release prerequisites indicate the sequence in which a complete purchase requisition or requisition item must be approved via the release codes. The release prerequisites are defined in Customizing for Purchasing (in the release strategy).
Release strategy KF (purchase orders up to $10,000)
With the two-step release strategy KF, release by either T1 or T2 is the prerequisite for release with KY. That is to say, a member of the Technical Services staff (T1 or T2) must release the requisition item before the more senior level of Sales Manager (KY).
Release strategy TF (purchase orders above $10,000)
Release strategy TF basically corresponds to the strategy KF. However, the requisition item must additionally be released by a member of the Executive Board (release code EX). A prerequisite for release by EX is release by the Sales Manager (release code KY).
Release Indicator
When a complete requisition or a requisition item has been processed via a release code, a release indicator is assigned to it. The latter shows whether:
The requisition can be changed by materials planning and control
An RFQ referencing the item can be created
A PO referencing the item can be issued
Purchasing can change the quantity or the delivery date
The item can be changed subsequent to the start of the release procedure You define when the system sets which release indicator in Customizing for Purchasing under "Set Up Procedure with Classification".Release indicators for strategy KF:
An RFQ or a PO referencing the requisition item can be created if releases have been effected by T1 or T2 and then with KY. Release indicators for strategy TF:
RELATED POSTS
WORK FLOW IN MM PART 3
MySAP environment security solutions
SAP authorization and client administration in mysap.com
No comments :
Post a Comment