Hierarchy

⤷

⤷

IMG Activity
ID | CM_XX_FLEXDE03 | Define Derivation Paths |
Transaction Code | S_KK4_82000928 | IMG Activity: CM_XX_FLEXDE03 |
Created on | 20020114 | |
Customizing Attributes | CM_XX_204_2_2 | Multiple Use: Non-Critical Optional Activity, IS-HER-CM-AD, ASAP 204 |
Customizing Activity | CM_XX_FLEXDE03 | Maintenance Object: Define Derivation Paths |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CM_XX_FLEXDE03 |
Use
In this IMG activity, you can create your own derivation paths if the ones that SAP provides do not fully meet your requirements. Customer derivation paths must start with Y or Z. This naming convention also applies to the function modules you assign to your derivation paths. Here, you only need to define the technical name of the function module. The other actions required for function modules are described further on in this document.
The purpose of a derivation path is to provide one or more export parameters, which can also be structures. It is better to define the entire infotype structure and not only a single infotype field as an export parameter. You can restrict the number of fields later on when you implement the derivation path.
Every derivation path is based on the object for which you are retrieving information. This is usually a student, but can also be a program, or an organizational unit such as faculty. You must define the type of root object for the derivation path.
If you use the derivation path to retrieve only the attributes that are assigned directly to this root object (for example, the nationality for the root object student), you do not require an evaluation path. However, if you want to retrieve attributes of the student's programs and modules, or the external and internal qualifications the student has earned, you must enter the evaluation path you want the system to use when determining objects from the root object.
When you have defined all of the attributes you need for the derivation path, you can define which information the evaluation path should use to determine the export parameters of each object type. You can choose this information from the infotypes and additional info structures assigned to the object types. The additional info structures, for example, contain student account data and the details of tests and transcripts.
In some cases, a derivation path may require more than the root object, the period and this information to determine its export parameters. A typical example of additional parameters are the academic year and academic session. You can also define such additional import parameters for a derivation path. However when you do this, you can use the derivation path only in processes in which these parameters are used.
When you save a derivation path, the system generates the interface of the assigned function module. This interface consists of the derivation path import parameters and the table parameters of all infotypes or additional info structures assigned to the derivation path. You must also define the allowed entries for the function module, that is, derive the export parameters from the import and table parameters.
Requirements
Standard settings
Activities
- Enter an up to six-character alphanumeric key beginning with Y or Z and a description for each derivation path you create.
- Assign an object type to the derivation path.
- Enter a technical name starting with Y or Z for the function module.
- If required, assign an evaluation path and maintain the required parameters.
- Save the derivation path.
When you save the derivation path, the system generates the interfaces of the function module.
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
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 |
VC_T7PIQDP02P | C - View cluster | SM34 |
History
Last changed by/on | SAP | 20020503 |
SAP Release Created in | 464 |