Business Transaction Creation 
This function enables you to create business transactions - business activities or leads - after the external list data is mapped successfully to SAP standard structures.
Note
You can create business transactions for the successfully mapped records only if:
The mapping format used is of type Business Partners and Activities or Business Partners and Leads or Activities or Leads.
The mapping format used is of type Business Partners and Activities or Business Partners and Leads, the records do not contain any postal errors, are not marked as duplicates and Business Partners have been maintained for these records.
Prerequisites
If the mapping format used is of type Business Partners and Activities or Business Partners and Leads, you have executed the Upload File, Map Data and Business Partner Maintenance steps, or selected the steps for execution.
If the mapping format used is of type Activities or Leads, you have executed the Upload File and Map Data steps, or selected the steps for execution.
Activities
To execute this step, select the Create Business Transactions option, specify the error attribute, and set the start data.
Data Processing During Business Transaction Creation
An External List file could contain response data in addition to either B2B data (organization and contact person data) or B2C data (person data), depending on the fields mapped in the mapping format used for an external list.
During processing, Business Activities are created for response data if the mapping format is of type Business Partners and Activities or Activities. Leads are created for response data if the mapping format is of type Business Partners and Leads or Leads.
The default implementation class is CL_DEF_IM_CRM_MKTLIST_BADI. If there is no active implementation for the Business Add-In Define Execution of Steps (CRM_MKTLIST_BADI), then the default implementation for the method CREATE_BUSINESS_TRANSACTIONS is used to create business transactions.
This method calls the following methods to create business transactions:
A private method, CREATE_ACTIVITIES, in the default implementation class to create business activities if activity data has been mapped.
A private method, CREATE_LEADS, in the default implementation class to create leads if lead data has been mapped.
The following steps are performed within these methods for each mapped record:
A check is carried out to ascertain if a valid process type was mapped successfully. If the process type is not provided, the process type is taken from the mapped template ID and checks are performed to ascertain:
Whether the leading transaction category of the mapped process type is a business activity (in CREATE_ACTIVITY) or lead (in CREATE_LEAD).
Whether the process type is not blocked
If the check fails, the business activity or lead is not created for this particular record.
NoteIf the personalized response code is mapped, the corresponding outbound details (business partners contacted, campaign element for which business partners were contacted, transaction GUID and transaction type that was used to record the interaction) are read.
End of the note.Business partners (Activity Partner and/or Contact Person for business activity, Prospect and/or Contact Person for lead) are taken from:
The external list item table (CRMD_MKTLIST_I) if the mapping format used is of type Business Partners and Activities or Business Partners and Leads
The mapped business partner IDs or Personalized Response Code from the business partner and campaign identification table (CRMD_MKTLIST_BCI) if the mapping format used is of type Activities or Leads.
If business partners cannot be determined, the business activity or lead is not created for this particular record.
Business partners are assigned to the business activity or lead based on the partner functions supported for the process type:
In the case of B2B data, Organization is the Activity Partner for Business Activity or Prospect for Lead, while Person is the Contact Person for Business Activity and Lead.
In the case of B2C data, Person is the Activity Partner and Contact Person for Business Activity or Prospect and Contact Person for Lead.
Survey answers are converted to internal format and submitted. In case a lead is being created and qualification level has been assigned to the questionnaire, automatic qualification level is determined from the survey answers.
If the conversion fails, business activity or lead is not created for this particular record.
Header data for the business activity or lead is prepared.
NoteDocument flow data is prepared for the business activity or the lead. The following are the predecessors for the business activity or the lead:
Campaign element
Business transaction - if it was used to record the outbound interaction.
Interaction object - if it was used to record the outbound interaction
End of the note.A check is performed if a valid campaign is either mapped in the business partner and campaign identification table (CRMD_MKTLIST_BCI) or determined using the Personalized Response Code. If the check fails, the business activity or lead is not created for this particular record.
Data on dates and user status is prepared for the business activity or lead. Business activities are created with actual dates, a check is performed to find if date type ORDERACTUAL is supported for the process type. Leads are created with Start Date and Expected End Date, a check is performed to find if date types LEAD_START and LEAD_END are supported for the process type. A check is performed if the mapped user status is allowed for the process type.
If the checks fail, business activity or lead is not created for this particular record.
Finally, Business Activities and Leads are created by calling the function CRM_ORDER_MAINTAIN and saved by calling the function CRM_ORDER_SAVE.
The transaction GUIDs for successfully created business activities or leads are exported in the export parameter ET_TRANSACTION_GUIDS to be maintained later on in the external list item table (CRMD_MKTLIST_I).
NoteAny error messages displayed during processing in CRM_ORDER_MAINTAIN and CRM_ORDER_SAVE are recorded in the application logs. They are read from the application log and exported in the export parameter ET_MESSAGE to be maintained in the External List error table CRMD_MKTLIST_E.
Errors occurring during the execution of the Create Business Transactions step are logged. These errors can be identified if the button next to Create Business Transactions on the Process Steps tab page contains a red icon. Error details can be viewed by clicking this button.
Errors may occur in the process due to erroneous response data or other system-related problems.
You cannot repeat the step Create Business Transactions by using the repeat attribute All Data Records. If this step is repeated, only errors and unprocessed records are processed again.
End of the note.