Hierarchy
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JAS (Package) Application development R/3 Publishing Advertising System***
IMG Activity
| ID | ISM_PFOBJ_BONU3 | Define Condition Technique for Partner Settlement |
| Transaction Code | S_KK4_82000152 | (empty) |
| Created on | 20000502 | |
| Customizing Attributes | ISM_PFOBJ_BONU3 | Define Condition Technique for Partner Settlement |
| Customizing Activity | SIMG_CFMENUOLSDBONU3 | Condition Technique For Rebate Processing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISM_PFOBJ_BONU3 |
Condition types that are used for partner settlement must be made known to pricing for the IS-M/AM order (application JA) and commission determination (application JC). They must also be created as bonus condition types in application V (Sales and Distribution).
In this step you perform the activities required in application V. Parallel activities that are to be performed in applications JA and JC are described for each step.
Activities
(This IMG node references an IMG node from SD pricing and therefore contains the same activities as this node).
Field catalog bonus
Contain admissible fields for condition tables in application V. The same fields must also exist in applications JA and JC.
Maintain condition tables for bonus
Condition tables determine determination-relevant attributes for a media partnership. These condition tables are created here (in application V) and not in applications JA and JC.
Example
Media partnerships are to apply to those orders in a particular sales organization for which the system has determined a particular partner object. In this case, condition table 201 with the sales organization and partner object fields is suitable.
Maintain access sequences
Bonus-relevant access sequences (example PFBO) refer to the condition tables defined here. The same access sequences must also be created in applications JA and JC. You can copy the example access sequence PFBO that also refers to application V (even though it belongs to application JA or JC in which this condition table does not exist).
Define condition types
Percentage condition types of class C (expense reimbursement)
with reference to a bonus-relevant access sequence (example PFBO). The same condition types must also be created in applications JA and JC. You should also enter the condition type with the same name in reference application V as the reference condition type.
Maintain pricing procedure
This activity must be performed in applications JA, JA and JC and not in application V. Unlike the standard, you should enter requirement 513, value formula 223 and no basic formula for the condition types used in partner settlement.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | 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 | ISM_PFOBJ_BONU3 | 0 | I170007156 | Revenue Distribution |
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 |
| VV_T685A_VA | V - View | SM30 | 0000000020 | Define Condition Types | ||
| VVC_T683_VA | C - View cluster | SM34 | 0000000008 | Maintain Pricing Procedures | ||
| VVC_T682_VA | C - View cluster | SM34 | 0000000888 | Maintain Access Sequences | ||
| VV_T681F_VE | V - View | SM30 | 0030000000 | Field catalog for rebates | ||
| IMGDUMMY | D - Dummy object | OV20 | 0000000001 | Maintain condition tables for rebate |
History
| Last changed by/on | SAP | 20000530 |
| SAP Release Created in | 46C |
