Ansicht
Dokumentation
CRM_ICM_ACT06 - Assign Transaction Categories/Subcateogries to ICM Subobject Types
Fill RESBD Structure from EBP Component Structure General Data in Customer MasterThis documentation is copyright by SAP AG.
Objects and subobjects exist in both ICM and CRM. Although these objects and subobjects might have the definitions within the two systems, there is no automatic connection between them. These definitions enable you to publish or identify the business objects and subobjects from CRM for which you want to pay incentives and/or commissions from ICM.
In this activity, you specify which transaction object types and subobject types from CRM you want to assign to a particular transaction object type within the ICM engine. This information is used to fill the CRM -> ICM engine interface.
Examples of object types that are supported include:
- Sales order header,,,,- BUS2000115
- Sales order line item,,,,- BUS2000131
- Sales contract header,,- BUS2000121
- Sales contract line item,,- BUS2000134
- Resale order header,,,,- BUS20401
- Reasale order line item,,- BUS2040101
Other object types are planned for later releases.
Inside the ICM engine, you must define the object types and subobject types you want to use. Inside the CRM system, you then assign the transaction object types and subobject types to those ICM subobject types.
Based on the object types that you have chosen to use for paying incentives and/or commission, you must do the following:
- Maintain the corresponding two transaction object types (header + line item) as entries in this configuration table.
- Assign the corresponding subobject type you are using within the ICM engine.
RFUMSV00 - Advance Return for Tax on Sales/Purchases BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 1947 Date: 20240523 Time: 163646 sap01-206 ( 35 ms )
