⤷ SD-SLS (Application Component) Sales
⤷ ERP_SALES_O2C_SLS (Package) ERP Sales Order 2 Cash - Sales
|ID||BADI_O2C_TEL_ACTIVE||Enable Telephony Integration|
|Customizing Attributes||BADI_O2C_TEL_ACTIVE||Enable Telephony Integration|
|Customizing Activity||BADI_O2C_TEL_ACTIVE||Enable Telephony Integration|
|Document Class||SIMG||Hypertext: Object Class - Class to which a document belongs.|
This Business Add-In (BAdI) is used to control whether or not telephony integration is enabled within the Internal Sales Representative portal role. You can control each user's individual access to this feature.
You can also specify whether the system should register a user's function call to the telephony server prior to any other function call. The need for this protocol may vary among different telephony servers.
This BAdI is called when the following portal iViews containing telephony functionality are launched:
- The Access Customer Cockpit iView. If the BAdI implementation enables telephony integration for a user, an additional Retrieve Call button becomes visible.
- The Customer Cockpit iView. If the BAdI implementation enables telephony integration for a user, telephone numbers are rendered as links which, when selected, trigger an outbound call.
- The Customer Search iView. If the BAdI implementation enables telephony integration for a user, telephone numbers are rendered as links which, when selected, trigger an outbound call.
In general, the implementation of telephony is based on theSAPphone. If the BAdI implementation enables telephony integration for a user but a user has currently no SAPphone workcenter assigned, an iView is launched that allows you to maintain the extension of your telephone device. The iViews contain the standard SAPphone transaction
SPHD, which provides this functionality.
The following BAdI method is called to control telephony integration and registration:
The BAdI implementation BADI_IM_O2C_TEL_ACTIVE enables telephony for any user. It also sets the flag for regitstration of the user to the telephony server.
The BAdI implementation BADI_IM_O2C_TEL_ACTIVE is not activated in the standard system.
This BAdI does not allow multiple use.
This BAdI is not filter-dependent.
|ASAP Roadmap ID||257||Create User Exits|
|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|
|Maintenance object type||E||Business Add-In - Definition|
|Last changed by/on||SAP||20080630|
|SAP Release Created in||604|