| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Set up the prerequisites and run the migration program. Once the migration is successful set up the configuration for E4C activity creation if its not already activated.
Prerequisites:
Enable the 'E4C Activity' flag before running the migration program. The activity type cannot be determined unless the E4C Activity flag is switched on in transaction /PACG/ECM_CPROP - General Properties of E4C.
Migration Program Details:
The migration program can be found in /PACG/ECE package (program /PACG/ECE_ACTIVITY_TRANSFER). 
Activities to migrate are defined using Sales Organization number, Distribution Channel number, Division number, Sales activity number or creation date. 
Inb. Data Create.Class - Change 'Incoming Message Attributes' for the message type /PACG/ECM_ACTIVITYIN (New 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 (New Idoc Class: /PACG/ECM_CL_S_IDOC_O_ACTI_E)
Change IDOC processing class – after successful migration the checkbox should be checked to automatically update the classes for the configuration (the classes should be entered in the 'configuration update' section). With this setting new activities won't be transferred/created.
If no data is entered, the program will migrate all the sales activities found. The number of activities to transform is displayed in a warning window.
Displayed logs confirm successful transformation for a given activity. All the logs can be found in /pacg/ece_acttr table (E4C: Log table with migrated sales activities). 
Sales activities are stored in VBKA table. If the migration process succeeded, these activities can now be found in /PACG/ECM_ACTI table.
If no fitting activity is found, an error log is displayed.
If the 'Test run' checkbox is checked, the program will display logs showing which activities can be transformed, have already been processed or can't be mapped, but no changes will be made in the database. 
Post Migration:
Set up the configuration for the E4C activity for your business process if its not set up already.
...
The new activities created will be E4C activity.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
*Grey fields are E4C Activity-specific
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
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Let's access sales activity 100001720 via transaction VC03.
This activity can't be found in /PACG/ECM_ACTI_VC03 - Display E4C Activity transaction. 
Once the migration process has been launched for this activity, a confirmation log can be seen. 
The activity can now be seen as an E4C Activity in transaction /PACG/ECM_ACTI_VC03. 
...