Since SAP S/4 no longer supports sales activities, a new object – E4C Activity has been created, with proper transactions to manage it. It's recommended to all FSM Cloud Connector users to use solely this new object. Already existing sales activities can be easily transformed into E4C activities with the migration program.
The migration program can be found in /PACG/ECE package (program /PACG/ECE_ACTIVITY_TRANSFER).
Prerequisites
For the migration program to run correctly, the ‘E4C Activity’ flag in transaction/PACG/ECM_CPROP - General Properties of E4C must be enabled first. The activity type cannot be determined unless this flag is switched on.
Data Selection
To transfer sales activities to E4C activities using the migration program, the ‘Data selection’ section of it must be filled carefully. Leaving these fields empty results in migration of all the sales activities found.
To transfer one particular sales activity or a range of activity numbers, use the ‘Sales activity no.’ field.
Configuration update
The 'Configuration update' section of the program should be filled with classes below:
Inb. Data Create.Class - Change 'Incoming Message Attributes' for the message type /PACG/ECM_ACTIVITYIN - Inb. Data Creation class /PACG/ECM_CL_S_IDOC_I_ACTIVI_E
IDOC Creation Class - Change the 'Outgoing Class Assignment' for message type /PACG/ECM_ACTIVITYOUT - Idoc Class /PACG/ECM_CL_S_IDOC_O_ACTI_E
Data Selection Class - /PACG/ECM_CL_S_SEL_ACTIVITY_E
Leave the ‘Change IDOC processing class’ option empty if you want to transfer activities (for changing only the configuration classes, see the Post migration section.
Running the program
After filling the ‘Data selection’ and ‘Configuration update’ sections of the program, the user can run the program in either a test mode, or a regular mode.
To run the program in the test mode, make sure to check the ‘Test run’ option.
The program will display a warning window with a number of activities to transfer, and then logs showing which activities can be transformed, have already been processed or can't be mapped - no changes will be made in the database, however.
If run in the regular mode, the program will act similarly, with proper changes made in the database. First, a warning window displays the number of sales activities selected to be transformed.
If no fitting activity is found, an error log is displayed.
After clicking ‘Execute’ in the warning window, the transformation takes place. Eventually logs are displayed, confirming successful transformation for specified activities. All the logs can be found in /pacg/ece_acttr table (E4C: Log table with migrated sales activities).
Transformed activities (from the VBKA table) can now be found in the /PACG/ECM_ACTI table. They can also be retrieved in transactions /PACG/ECM_ACTI_VC01, /PACG/ECM_ACTI_VC02 or /PACG/ECM_ACTI_VC03.
Post migration
Once the migration is done and successful, set up the configuration for the E4C activity for your business process if it's not created already.
From this moment the new activities created will be E4C activity.
To automatically update the classes for configuration after successful migration, the ‘Change IDOC processing class’ option should be checked. Running the program with this setting won't result in new activities being transferred/created. Solely the classes will be updated.
Technical overview
Sales activity – E4C Activity Mapping Table
E4C Activity table field | Source | Source table field | Description |
ACTNR | VBKA | VBELN | E4C Activity Number (SD document no. of a sales activity in sales support) |
VKORG | VBKA | VKORG | Sales Organization |
VTWEG | VBKA | VTWEG | Distribution Channel |
SPART | VBKA | SPART | Division |
ACTI_TYPE | Based on E4C Activity code mapping in /pacg/ecm_actmae and VBKA | KTAAR | Activity type |
ACTI_STATUS | Based on SAP status mapping in /PACG/ECM_STAMAP and VBKA | KTAST | Activity status |
KUNNR | VBPA | KUNNR | Customer number (Partner number) |
KUNWE | VBPA | KUNNR | Ship-to-party |
CONTACT | VBPA | PARNR | Number of contact person |
PERNR | VBPA | PERNR | Personal Number |
ACTI TOPIC | Activity topic | ||
SUBJECT | Mapped from a text object with key value "TEXTID_SUBJ", name <sales activity number> and object "VBKA" | Subject | |
TECHNICIAN | Technician | ||
ADDRESS | Mapped from a text object with key value "TEXTID_ADDR", name <sales activity number> and object "VBKA" | Address – object key | |
PREV_ACTNR | VBKA | VGBEL | E4C Reference Activity Number (Document number of the reference document) |
SOURCE ACTNR | E4C Source Activity Number | ||
ACTI_START_DATE | VBKA | KTABG | Activity start date |
ACTI_START_TIME | VBKA | KTABT | Activity start time |
ACTI_END_DATE | VBKA | KTAEN | Activity end date |
ACTI_END_TIME | VBKA | KTAET | Activity end time |
DURATION | Duration in minutes | ||
ACTI_REM_DATE | Activity remainder date | ||
ACTI_REM_TIME | Activity remainder time | ||
ACTI_CHECKEDOUT | Proaxia append for VBKA table | /PACG/ECM_CHECKEDOUT | E4C CheckedOut |
COMPID | /PACG/ECM_SAASG | COMPID | E4C Company ID |
SERVICE_RATING | VBKA | Fields starting with "KTA-" and ending with a value predefined for each company | Service rating |
AUFNR | If an object relationship is found, object key is assigned the value of the order number, uses | objkey_b | Order number |
VORNR | AFVC | VORNR | Operation/Activity Number |
UVORN | AFVC | VORNR | Suboperation |
QMNUM | Notification number | ||
MANUM | Sequential task number | ||
EQUNR | Equipment number | ||
TPLNR | Functional location | ||
TEAM_ID | Team Id | ||
TIMEZONEID | Time zone | ||
EXECSTAGE | FSM Execution stage | ||
fOBJ_REF_TYPE | Manual, "Service call" (if order number not initial) or "Business Partner" (order number initial) |
| |
OBJKEY | /PACG/ECM_ACTI | If order number not initial, object key is assigned the value of the order number (AUFNR), otherwise KUNNR | Oder number or Customer number |
RELEAS_UDF_SEND | Release UDF was sent (or not) | ||
ERDAT | Date on which record was created | ||
ERZET | Entry time | ||
ERNAM | Name of person who created the object | ||
AEDAT | Changed on | ||
AEZET | Time last change was made | ||
AENAM | Name of person who changed object | ||
LOEKZ | Marked for deletion | ||
CLOUD_CREATED | Activity created from CloudApp | ||
CHANGEDBYSAP | Activity dates where changed by SAP | ||
DUMMY | Single-character Indicator |
After the transformation process, regardless of its success, subroutine manage_number_ranges is carried out, assuring the activity number range status is equal to the highest sales activity number range status. Number range objects are maintained in transaction SNRO.
RV_BELEG (no 23) - Number ranges for SD documents (sales activity)
/PACG/ECM1 – Number ranges for E4C Activities
