Hierarchy
⤷ ICM (Application Component) Incentive and Commission Management (ICM)
⤷ PFO130 (Package) Portfolio Assignment: Kernel Functions
IMG Activity
ID | _PFO_CONST | Define Attributes for Object Types |
Transaction Code | S_AEN_10000113 | (empty) |
Created on | 20041119 | |
Customizing Attributes | _PFO_CONST | Define Attributes for Object Types |
Customizing Activity | _PFO_CONST | Define Attributes for Object Types |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | _PFO_CONST |
Use
In this IMG activity, you define attributes for object types for portfolio assignment.
Requirements
You have carried out the following IMG activities:
- Define Object Types
- Define Assignment Role for Business Objects
- Define Assignment Role for Assignment Objects
Notes
You can select your own fields to define the attributes of object types. These fields must be included in structure PFO_S_CUSTOMER_FIELDS.
This structure can be enhanced with the Customizing Include CI_PFO_S_CUSTOMERFIELDS. Only fields that are added to this Include can be subsequently used to construct the corresponding tables.
Standard settings
Activities
Once you have assigned a predefined object type to an object kind, you navigate to a list of required activities.
Note that these are initial activities that are not subject to change once they have been processed. To make subsequent changes, you must change the automatically created objects directly in the object browser.
Carry out the activities in the specified order:
- Define Key: Determine which attributes make up the object key. The definition references the fields of structure PFO_S_CUSTOMER_FIELDS.
- Define attributes: Determine further attributes for the object key. Likewise, the definition references the fields of structure PFO_S_CUSTOMER_FIELDS.
- Generate table: Generate the object-specific database table.
- Save object: Saving generates control data that is stored on the database.
- Maintain combinations: Determine which segment types can be assigned to the object and in which role.
- Maintain origin: You use system IDs to manage the origin of the objects in portfolio assignment and to evaluate these. Here you assign the external system (RFC destination) a system ID.
- Maintain secondary index: You should create a secondary index in the object data table to optimize the performance of portfolio assignment. See the documentation on how to proceed here. We recommend creating a secondary index.
- Create RFC interface: You can use the following function modules as templates to set up the RFC connection.
Function group Function module
PFO_RFC_TEMPLATE_ZO PFO_RFC_GET_ASSIGNED_ZO
PFO_RFC_TEMPLATE_GO PFO_RFC_GET_ASSIGNED_GO
- Register methods: Finally you must instruct the system to use this method to process objects. You do this in this step. The commission system automatically generated the required entries.
Business Attributes
ASAP Roadmap ID | 105 | Define functions and processes |
Mandatory / Optional | 2 | Optional 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 | _PFO_CONST | 0 | KK40000031 | Incentive and Commission Management (ICM) |
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 |
IMGDUMMY | D - Dummy object | PFO_CUST_CONST |
History
Last changed by/on | SAP | 20041213 |
SAP Release Created in | 600 |