Colgate AC-SOLMAN Integration enhancement

1. Business Task:

1.1 Incident Type:

Need entry in table /bti/te_int_mapp and /bti/te_int_conv

Replace EXTSYS_NO, EXTSYS_NAME with what you already have.

Replace EXTSYS_NO, EXTSYS_NAME with what you already have. EXTFLD_ID should have list of possible incident types from CRMC_SRQM_PRBCAT and the equivalent values from AC in EXTFLD_VAL

For any fields from CRMD_ORDERADM_D and CRMD_ACTIVITY_H, add them to table /BTI/TE_INT_FMAP

Eg: fill in the right custom field ID with a prefix of CF_ in the column BTI_TE_FIELDNAME

1.2 Partner fields:

To copy partners from incident to business task, create entry in /bti/te_tvarv. The variant name will be a prefix of PARTNER_ followed by a partner function name. eg: PARTHER_0000001. In the column LOW, add the task custom field for the relevant partner function.

1.3 Project field in Business task:

To default project for a business task based on the incident field, create an entry in TVARV for a variant COL_PRJIC_ XXX where XXX is CRMC_SRQM_PRBCAT-PROBLEM_CATEGORY and value in field LOW will the corresponding project ID from /BTI/TE_PROJ.

2. Transport Request:

Activate user-exit 0730 by adding an entry to table /BTI/TE_EXITC.

Also require TVARV entries to get default values.

COL_TR_OWNER_FIELD - Configure which partner function value must copied to as transport owner. 

COL_TR_DEFAULT_CLIENT - Default client

COL_BT_SYSTEM_FIELD - The custom field in business task that stores the system name

COL_TARGET_BY_SYS_NNN - When NNN is the system ID. This should have the target ID. As you stated in the requirement document, if system LAP then target will LAD. So entry will COL_TARGET_BY_SYS_ LAP and in column LOW, AC target ID whose SID is LAD and must be source target.

3. Transport Form:

3.1 Exit 610 to copy BT CF values to TF CF(For TR Created from BT)

Activate user-exit 0610 by adding an entry to table /BTI/TE_EXITC. This will copy values of configured fields of BT to TF only when the transport is created from a business task.

Also require TVARV entries to get default values.

COL_COPY_BT_TO_TF_NNN - Configure from which CF field BT to be copied to CF of TF where NNN is customer field ID of BT and the column will have CF ID of TF.

COL_PATH_BY_SYS_NNN - Confirm to choose the right path based on the system selected in BT. NNN is the system name and Column LOW will have the corresponding path ID which you can find in table /BTI/TE_PATH.

3.2 Exit 960 to copy BT CF values to TF CF(For TR created from SAP GUI)

This is required when a TR is created in SAP GUI that do not have a link to a BT when creating TF. That said, this doesn't populate the values after adding the business task but populates after saving it and works only for custom fields. Therefore make the relevant fields non-mandatory. The TVARV configuration in 3.1 is also required here. 

Add exit ZTE_COLGATE_EXIT_0960 to table /BTI/TE_EXITC.

4. Other Validations:

Making the fields non-modifiable is not possible. Alternatively added validation through user-exits to raise error if the user tried to change a task after its related IR is completed.

Activate user-exit 0040 by adding an entry to table /BTI/TE_EXITC.

This required a TVARV entry.

COL_STATUS_NO_CHANGE - Possible status for completion.

It is not possible to make a particular field mandatory based on the valued of other fields. So another user-exit to make approval fields mandatory based on the priority of BT and TF with TVARV entry as well.

COL_APPROVAL_FIELD - Configure the CF ID of approval fields in TF.