/AWS1/CL_PTSLEADINTERACTION¶
Represents a specific interaction or touchpoint with a lead customer. This structure captures details about communications, meetings, or other engagement activities that help track the lead's progression and engagement history.
CONSTRUCTOR¶
IMPORTING¶
Required arguments:¶
iv_sourcetype TYPE /AWS1/PTSLEADSOURCETYPE /AWS1/PTSLEADSOURCETYPE¶
Specifies the type of source that generated the lead interaction, such as "Event", "Website", "Referral", or "Campaign". This categorization helps track lead generation effectiveness across different channels.
iv_sourceid TYPE /AWS1/PTSLEADSOURCEID /AWS1/PTSLEADSOURCEID¶
The unique identifier of the specific source that generated the lead interaction. This ID provides traceability back to the original lead generation activity.
iv_sourcename TYPE /AWS1/PTSLEADSOURCENAME /AWS1/PTSLEADSOURCENAME¶
The descriptive name of the source that generated the lead interaction, providing a human-readable identifier for the lead generation channel or activity.
iv_customeraction TYPE /AWS1/PTSCUSTOMERACTION /AWS1/PTSCUSTOMERACTION¶
Describes the action taken by the customer during or as a result of the interaction, such as requesting information, scheduling a meeting, or expressing interest in a solution.
io_contact TYPE REF TO /AWS1/CL_PTSLEADCONTACT /AWS1/CL_PTSLEADCONTACT¶
Contains contact information for the customer representative involved in the lead interaction, including their name, title, and contact details.
Optional arguments:¶
iv_usecase TYPE /AWS1/PTSENGAGEMENTUSECASE /AWS1/PTSENGAGEMENTUSECASE¶
Describes the specific use case or business scenario discussed during the lead interaction. This helps categorize the customer's interests and potential solutions.
iv_interactiondate TYPE /AWS1/PTSDATETIME /AWS1/PTSDATETIME¶
The date and time when the lead interaction occurred, in ISO 8601 format (UTC). This timestamp helps track the chronology of lead engagement activities.
iv_businessproblem TYPE /AWS1/PTSENGAGEMENTCUSBUSINE00 /AWS1/PTSENGAGEMENTCUSBUSINE00¶
Describes the business problem or challenge that the customer discussed during the interaction. This information helps qualify the lead and identify appropriate solutions.
Queryable Attributes¶
SourceType¶
Specifies the type of source that generated the lead interaction, such as "Event", "Website", "Referral", or "Campaign". This categorization helps track lead generation effectiveness across different channels.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_SOURCETYPE() |
Getter for SOURCETYPE, with configurable default |
ASK_SOURCETYPE() |
Getter for SOURCETYPE w/ exceptions if field has no value |
HAS_SOURCETYPE() |
Determine if SOURCETYPE has a value |
SourceId¶
The unique identifier of the specific source that generated the lead interaction. This ID provides traceability back to the original lead generation activity.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_SOURCEID() |
Getter for SOURCEID, with configurable default |
ASK_SOURCEID() |
Getter for SOURCEID w/ exceptions if field has no value |
HAS_SOURCEID() |
Determine if SOURCEID has a value |
SourceName¶
The descriptive name of the source that generated the lead interaction, providing a human-readable identifier for the lead generation channel or activity.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_SOURCENAME() |
Getter for SOURCENAME, with configurable default |
ASK_SOURCENAME() |
Getter for SOURCENAME w/ exceptions if field has no value |
HAS_SOURCENAME() |
Determine if SOURCENAME has a value |
Usecase¶
Describes the specific use case or business scenario discussed during the lead interaction. This helps categorize the customer's interests and potential solutions.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_USECASE() |
Getter for USECASE, with configurable default |
ASK_USECASE() |
Getter for USECASE w/ exceptions if field has no value |
HAS_USECASE() |
Determine if USECASE has a value |
InteractionDate¶
The date and time when the lead interaction occurred, in ISO 8601 format (UTC). This timestamp helps track the chronology of lead engagement activities.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_INTERACTIONDATE() |
Getter for INTERACTIONDATE, with configurable default |
ASK_INTERACTIONDATE() |
Getter for INTERACTIONDATE w/ exceptions if field has no val |
HAS_INTERACTIONDATE() |
Determine if INTERACTIONDATE has a value |
CustomerAction¶
Describes the action taken by the customer during or as a result of the interaction, such as requesting information, scheduling a meeting, or expressing interest in a solution.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_CUSTOMERACTION() |
Getter for CUSTOMERACTION, with configurable default |
ASK_CUSTOMERACTION() |
Getter for CUSTOMERACTION w/ exceptions if field has no valu |
HAS_CUSTOMERACTION() |
Determine if CUSTOMERACTION has a value |
BusinessProblem¶
Describes the business problem or challenge that the customer discussed during the interaction. This information helps qualify the lead and identify appropriate solutions.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_BUSINESSPROBLEM() |
Getter for BUSINESSPROBLEM, with configurable default |
ASK_BUSINESSPROBLEM() |
Getter for BUSINESSPROBLEM w/ exceptions if field has no val |
HAS_BUSINESSPROBLEM() |
Determine if BUSINESSPROBLEM has a value |
Contact¶
Contains contact information for the customer representative involved in the lead interaction, including their name, title, and contact details.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_CONTACT() |
Getter for CONTACT |
Public Local Types In This Class¶
Internal table types, representing arrays and maps of this class, are defined as local types:
TT_LEADINTERACTIONLIST¶
TYPES TT_LEADINTERACTIONLIST TYPE STANDARD TABLE OF REF TO /AWS1/CL_PTSLEADINTERACTION WITH DEFAULT KEY
.