...
Technical overview
Expand |
---|
title | Click to expand the technical overview |
---|
|
Sales activity – E4C Activity Mapping TableE4C 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 RELGRAPHLK structure | 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) |
| Cloud message type
| 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. Image ModifiedImage Modified |
Testing
Let's access sales activity 100001720 via transaction VC03.
...