Release Strategy
Definition
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
Definition
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:
Monday, October 13, 2008
Subscribe to:
Post Comments (Atom)
Archives
-
▼
2008
(167)
-
▼
October
(145)
- SAP ALE ABAP DETIAL
- SAP ABAP ALE IDOC'S
- SAP - DIFFERENCE BETWEEN CONVERSION AND INTERFACE
- BAPI AND IDOC ALE
- SAP ABAP MESSAGE CONTORL
- SAP IDOC'S IN ABAP INTRODUCTION
- SAP ABAP IDOC'S OUTLOOK
- SAP ABAP IDOC PROCESSING
- SAP ABAP IDOC'S BASIC TOOLS I
- SAP ABAP IDOC'S BASIC TOOLS II
- SAP ABAP IDOC'S INBOUND BASIC TOOLS III
- SAP IDOC OUT BOUND TRIGGERS II
- SAP IDOCS OUTBOUND TRIGGER II
- SAP IDOC'S OUTBOUND TRIGGER III
- SAP Work flow based outbound Idoc's
- SAP ALE Change Pointers
- SAP Dispatching ALE IDocs for Change Pointers
- SAP IDOC design and Processing
- SAP Creation of the IDoc Data
- SAP Developing an Outbound IDoc Function
- SAP Converting Data into IDoc Segment Format
- SAP Partner Profiles and Ports
- SAP Defining the partner profile for ALE IDOC
- SAP Data Ports ( WE21 ) in idoc
- SAP RFC in R/3
- SAP Workflow from Change Documents
- SAP ALE Distribution Scenario
- SAP Useful ALE Transaction Codes
- BAPI Creating IDocs and ALE Interface
- R/3 RFC from MS Office Via Visual Basic
- SD WORK FLOW SCENARIOS I
- SD WORK FLOW SCENARIOS II
- SD WORK FLOW SCENARIOS III
- SD WORK FLOW SCENARIOS IV
- SD WORK FLOW SCENARIOS V
- SD WORK FLOW SCENARIOS VI
- SD WORK FLOW SCENARIOS VII
- MM WORK FLOW SCENORIOS I
- MM WORK FLOW SCENORIOS II
- MM WORK FLOW SCENORIOS III
- MM WORK FLOW SCENORIOS IV
- MM WORK FLOW SCENORIOS V
- MM WORK FLOW SCENORIOS VI
- MM WORK FLOW SCENARIOS VII
- MM WORK FLOW SCENARIOS VIII
- MM WORK FLOW SCENARIOS IX
- MM WORK FLOW SCENARIOS X
- MM WORK FLOW SCENARIOS XI
- WORK FLOW SCENARIOS in SAP ABAP
- SAP ABAP WORK FLOW I
- SAP ABAP WORK FLOW II
- SAP ABAP WORK FLOW III
- SAP ABAP Work Flow IV
- SAP ABAP Workflow Technology
- SAP OPTIMIZATION
- abap type key ward
- PERFORMENCE TIPS
- SAP ABAP INTERNAL TABLES IN BRIEF
- SAP ABAP RUN TIME ANALASIS
- MEMORY In SAP ABAP
- NAVIGATION In SAP ABAP
- WORK BENCH AND TOOLS In SAP ABAP
- DATA OBJECTS AND STATEMENTS In SAP ABAP
- INTERNAL PROGRAM MODULARIZATION In SAP ABAP
- SAP ABAP CONSITENCEY THROUGH INPUT CHECKS
- RUN TIME ENVIRONMENT In SAP ABAP
- SAP ABAP INTER TABLE OPERATIONS
- STATEMENTS In SAP ABAP
- SAP ABAP INTERNAL TABLES
- SAP ABAP SUB ROUTIENS
- SAP ABAP FUNCTION MODULES AND GROUPS
- SAP ABAP QUARY ADMINSTRATION
- SAP ABAP SAVING LISTS AND BACK GROUND PROCESSING
- SAP ABAP PROGRAM INTERFACE
- SAP ABAP LOCK CONCEPT
- SAP ABAP AUTHORISATION CHECKS
- SAP ABAP PERFORMENCE TIPS
- In SAP SYSTEM FIELDS
- SAP ABAP CONTROL BLOCKS
- SAP ABAP BUFFERING
- SAP ABAP MATCH CODE OBJECTS
- SAP ABAP LOCKS
- SAP SAMPLE CODE FOR OUTPUT TO EXCEL AND IN PUT FIL...
- SAP MULTIPLE INTERACTIVE REPORT SAMPLE CODE
- MULTIPLE INTERACTIVE REPORT SAMPLE CODE II
- CALLING PROGRAM AND PASSING DATA
- SAP TECHNIQUES FOR LIST CREATION AND SAP QUARY
- SAP SELECTION SCREENS ABAP REPORT
- SAP ABAP FAQ ON SCRIPTS I
- SAP ABAP FAQ ON SCRIPTS II
- SAP ABAP FAQ ON SCRIPTS III
- IN SAP ABAP TABLE TYPES
- SAP ABAP TYPES OF VIEWS
- SAP ABAP DATA BASE UPDATES COMPLETE
- SAP ABAP LOCK CONCEPT
- SAP ORGANIZING DATABASE UPDATES
- SAP ENHANCEMENTS TO DICTIONERY ELEMENTS
- DATA BASE DIALOG IN ABAP
- ABAP DICTIONARY I
- PERFORMANCE DURING TABLE ACCESS
-
▼
October
(145)
No comments:
Post a Comment