Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
ME0C (Package) Customizing R/3 Purchasing
IMG Activity
| ID | SIMG_CFMENUOLMEOMUP | Maint. Rel. Creation Profile for Sched. Agmt. w. Rel. Docu. |
| Transaction Code | S_ALR_87002255 | IMG Activity: SIMG_CFMENUOLMEOMUP |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLMEOMUP | Maint. Rel. Creation Profile for Sched. Agmt. w. Rel. Docu. |
| Customizing Activity | SIMG_CFMENUOLMEOMUP | Maint. Rel. Creation Profile for Sched. Agmt. w. Rel. Docu. |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLMEOMUP |
In this step, you can define the release creation profile.
The latter is an instrument for determining which criteria are used to generate releases against a scheduling agreement and transmit them to the vendor.
You assign the creation profile to the scheduling agreement item in the additional data.
The creation profile controls the creation periodicity of the releases and - starting from the current date of release creation - the way in which the quantities are aggregated.
In the release creation profile, you can define
- General Parameters
- Which creation strategy is the basis for JIT delivery schedules and scheduling agreements.
- How backlog and immediate requirements are taken into account during release creation.
- Aggregation and release horizon
If and how schedule lines should be aggregated during release creation. - Release creation periodicity
With which periodicity scheduling agreement releases are created - Tolerance profile
That for releases created as a result of changed schedule lines, the system performs a tolerance check - Internet release
Whether an Internet release is created during release creation
Example:
A release creation profile for a scheduling agreement for which delivery schedule lines have been maintained over several years can provide that releases are transmitted weekly from 1.1. to 12.31 of the first year. The release quantities are to be aggregated as follows:
For a period of 10 days starting from the current date of release creation, no aggregation; from the tenth to the thirtieth day, on a daily basis; and from the thirtieth day to the sixtieth day, on a monthly basis.
Example
Requirements
Standard settings
Recommendation
If you have not specified a time in the schedule lines, you should work with aggregation in the creation profile so that lines with the same date are consolidated when releases are created.
The reason for this is the following situation when comparing releases:
If several schedule lines having the same date/time key exist, an accurate comparison of releases is difficult because there is no clear assignment.
Activities
Further notes
For more information, see the field help and documentation for Purchasing (MM-PUR) in the section Creation Profile.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUOLMEOMUP | 0 | HLA0001538 | Scheduling Agreement |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_T163P | V - View | SM30 | 0000000000 | Define Transm. Profile for Sched. Agmt. with Release Docu. |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
