x Define Release Procedure for Scheduling Agreements
In this step, you set up the release procedure for scheduling agreements and can link it to workflow. (Note that in this context "releasing" means "approving", or giving the "green light" to a document.)
Requirements
x In the case of a release procedure linked to workflow, you must have previously created the user names, positions, jobs, etc. that you here assign to the release code in the organizational plan and must have linked them to the relevant standard tasks in task-specific Customizing (Basis -> Business Management -> Business Workflow -> Perform Task-Specific Customizing).
x You must assign the authorization M_EINK_FRG to the persons who are to be involved in the release procedure (Authorization Management -> Create Authorization Profiles and Assign to Users).
Activities
Here you define the following:
x Release group
x Release codes
x Release indicator x Release strategy x Workflow
Release group
Create a release group for your release procedure and assign it to a class. In the process, you assign
release conditions to the release procedure.
Release codes
Here you create the release codes you need for your release strategy and assign the codes to your release group. If a release code is to be used in workflow, indicate this accordingly in the Workflow field
The Workflow indicator is also used to control role resolution:
x "1 - Role Resolution with Group, Code and Plant (T16FW)"
Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow (see below).
x "9 - Role Resolution via User Exit"
Here you use the customer exit M06E0005 to define a role resolution of your own.
Release indicators
A release indicator shows the release status of a scheduling agreement.
Via the following settings, you can define the release indicators you need for your release procedure:
x The Released indicator is used to specify whether messages (scheduling agreement documents in output format) may be transmitted for a scheduling agreement with this indicator.
x The Changeability indicator shows the effect of changes to the scheduling agreement (a change to an agreement may require a new release strategy to be determined, for instance).
By means of the Value change indicator, you can specify that the release strategy is to be re-started if a scheduling agreement is changed and the value of an agreement item thereby increases by a certain percentage (e.g. 10%). Set the Changeability indicator to - "4 Changeable, new release in case of new strategy or value change" or "6 - Changeable, new release in case of new strategy or value change/outputted" and enter a percentage in the Value change field.
Attention:
The following release indicators are necessary for every release procedure:
o Release indicator for initial status
If the scheduling agreement is subject to a release strategy, it must normally be released
before it can be transmitted to the vendor. Therefore, when a scheduling agreement is created, it is assigned a release indicator that blocks it from being outputted in message form.
The Released indicator must not be selected for this indicator.
o Release indicator for released status
This indicator is assigned to the RFQ when it is released.
The Released indicator must be selected for this indicator.
Release strategies
Create a release strategy for your release group and assign your release codes accordingly.
x Release prerequisites
With the release prerequisites, you specify the order in which the individual release points (individuals or departments) represented by the release codes may release the document. Example
The following table shows release prerequisites for a strategy with four release codes: Code/Release prerequisite
|
|
| 01 | 02 | 03 | 04 |
|
| 01 | - | [ ] | [ ] | [ ] |
|
| 02 | [x] | - | [ ] | [ ] |
|
| 03 | [x] | [x] | - | [ ] |
|
| 04 | [x] | [x] | [x] | - |
In this release strategy, the codes 01, 02, 03, and 04 must successively release the scheduling agreement.
Read the table from left to right. For instance, the third line for release code 03: For code 03,
release via code 01 and code 02 is a prerequisite. That is to say, the scheduling agreement must be released via codes 01 and 02 before it can be released via code 03.
x Release statuses
Here you specify the status a scheduling agreement has after certain release points have effected release.
Specify which release indicator/status a scheduling agreement is to have after having been released via a certain release code.
x Classification
In classification, you maintain the values assigned to the characteristics. Via the characteristics and their values, you specify the scheduling agreements to which your release strategy is assigned. Maintain values (individual values or intervals) for your characteristics.
Example
Two characteristics and their values have been maintained in classification for release strategy
'EA':
- Document type - 'NB - standard purchase order'
- Total value - above $10,000
All POs with the document type 'NB' and a total value in excess of $10,000 are thus subject to a release procedure with the release strategy 'EA'.
x Release simulation
The release simulation function enables you to check which status a scheduling agreement will achieve with your release strategy if release is effected by a certain release point.
Choose "Simulate release" and release the document with the desired release code by double- clicking. The system shows you which status the scheduling agreement now has as a result of this release.
Workflow
Assign a processor ID to your workflow-relevant release codes. The processor (member of staff responsible for processing the document) will then receive a work item when he or she is required to effect release.
You can assign a processor ID either directly or indirectly:
o Direct processor assignment: Enter a user name.
o Indirect processor assignment:
Enter a job, for example, or a position. At runtime, the system will then determine the member(s) of staff responsible for processing the document.
x Define Tolerance Limit for Archiving
In this step, you specify the periods that must expire before:
x A scheduling agreement item is deactivated, and
x A deactivated scheduling agreement item is archived
Activities
1. Maintain the minimum time periods in days for the archiving of scheduling agreements.
2. Maintain the additional checking criteria for
o Target quantity reached
o Target value reached
o Validity period expired
If you are using the "Subsequent Settlement" functionality (for end-of- period volume-based rebates), the residence time set there works as logically "AND-linked" to the residence time of the document type maintained here.
x Conditions
In this section, you make the system settings that are relevant to the maintenance of conditions and price determination in the purchase of materials.
x Automatic Document Adjustment
In this step, you make the system settings required for application- specific activities (adjusting purchase orders, generating documents for
order optimizing etc.) when conditions change. There are two types of system settings:
1. Settings for condition index updates
2. Settings for the creation of document indices for certain documents
Condition index update involves the updating of change pointers when conditions are created or changed. These change pointers are analyzed by the system when the worklist is created for various applications. The updating of change pointers must be activated for each message category.
The message category "CONDBI" is used for the relevant document categories. You can activate the updating of change pointers in Activate Change Pointers.
Under Define Extent of Change, you can define the condition changes (condition amount, start and end of the validity period, scales) for which change pointers are updated.
In the settings for creating document indices for various documents, you define the condition types
(purchase price, discounts etc.) for which document indices are created.
The document indices record which particular conditions for the condition types specified were involved for these document items. For this purpose, the document indices also contain the condition key and the condition table of the condition record.
Standard Settings
The standard system contains all the required entries for message category CONBI for adjusting the document categories to be maintained.
Further Notes
Message category "CONDBI" for condition index updates is also used for document adjustment in purchase orders, order optimizing, scheduling agreements and pricing documents.
To enable the creation of document indices for pricing documents, the "document creation" indicator must be maintained in the Pricing Type.
x Control Document Adjustment
This step contains the various application areas in which automatic document adjustment is relevant.
The system automatically checks in every application area the allowed condition types and tables for the various applications and functions.
You can only enter master conditions, i.e. conditions with their own access sequence. The system does, however, take conditions with supplementary conditions into account.
The restriction to the updates at condition type table level allows you to only include the conditions in the
document index updates that change quickly. This reduces the volume of data processed.
x Control Purchasing Document Adjustment
In this step you define parameters for automatic document adjustment due to condition changes.
Condition types used in rebate processing cannot be entered in this way, as updates are controlled via other conditions.
No comments:
Post a Comment