Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Since SAP S/4 no longer supports sales activities, a new object – E4C FSM 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 ‘FSM Activity’ flag in transaction/PACG/ECM_CPROP - General Properties of E4CFSM Cloud Connector 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

Leave the ‘Change IDOC processing class’ option empty if you want to transfer activities, not configuration (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.

...

Info

'Send activities to FSM option is available with PACG200 SP03 and S4PACG200 SP03 or with the SAP note 3105329 available for PACG110 SP03, PACG200 SP01, PACG200 SP02

If the newly migrated activities should be sent to FSM the checkbox ‘Send activities to FSM’ must be ticketed. Otherwise activities will not be sent. In the older version of this report activities were sent to FSM by default.

...

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.

...

Expand
titleClick to see the same activity as an E4C activity (after running the migration program) in transaction /PACG/ECM_ACTI_VC03

Post migration

Once the migration is done and successful, set up the configuration for the E4C activity FSM Activity for your business process if it's not created already.

...

From this moment new activities created will be E4C activities.

Post migration configuration update

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.

...

  • 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

Anchor
_Toc38459311
_Toc38459311
Technical overview

Expand
titleClick to expand the technical overview

Sales activity –

E4C

FSM Activity Mapping Table

E4C

FSM Activity table field

Source

Source table field

Description

ACTNR

VBKA

VBELN

E4C

FSM 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

FSM 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.

  • RV_BELEG (no 23) - Number ranges for SD documents (sales activity)

  • /PACG/ECM1 – Number ranges for E4C Activities

...