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 | ISPAM_ERLV_KSCHL_UMS | Maintain Exception List for Converting Condition Types |
| Transaction Code | S_KK4_74002077 | IMG Activity: ISPAM_ERLV_KSCHL_UMS |
| Created on | 19990816 | |
| Customizing Attributes | ISPAM_ERLV_KSCHL_UMS | Maintain Exception List for Converting Condition Types |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISPAM_ERLV_KSCHL_UMS |
This function is no longer supported as of Release 4.02.
Conversion of condition types for which revenue distribution is to be performed to revenue distribution condition types occurs using identical names. This means it is not necessary to make any entry in this table.
However, it may be necessary to introduce different keys for condition types in revenue distribution.
You should make a complete entry for the key (by making entries in all the fields) in this table.
Example
You use the same condition type in various pricing procedures in the predecessor application. During revenue distribution pricing, this condition type should have a different effect in the various pricing procedures.
Recommendation
This function increases the complexity of pricing considerably.
If you have a case where the same condition type in the application for which revenue distribution was performed is to have a different effect in revenue distribution, you should use various condition types in the application for which revenue distribution was performed and use the same names principle during revenue distribution.
You can use reference condition types in the calling application if necessary to reduce condition maintenance.
For migration
- Define the new condition type in the application for which revenue distribution was performed and do not remove the old one from the pricing procedure.
- Ensure that the old condition type is no longer found automatically (set the 'Manual' indicator in the pricing procedure, remove the access sequence in the condition type itself if necessary) and can also no longer be controlled manually (e.g. reset manual modification in the condition type itself. Reset all condition references to the new condition type).
- If necessary, you can define an additional condition type that reproduces the old condition type in the revenue distribution pricing procedure during the transitional period.
- Once revenue distribution has been performed for all documents in the system that contain this condition type, you can remove the old condition type from the pricing procedure.
Further notes
You can still perform original table maintenance during the transitional period using transaction SM30, table JHVTJH13, variant JE.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 3 | Nonrequired 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 | ISPAM_ERLV_KSCHL_UMS | 0 | I170007156 | Revenue Distribution |
| SIMG | ISPAM_ERLV_KSCHL_UMS | 1 | O I510000066 |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19990816 |
| SAP Release Created in |
