Kontakt

Ansicht
Dokumentation

CRMV_MASS_MAPP - Assign Fields for Mass Changes

CRMV_MASS_MAPP - Assign Fields for Mass Changes

Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

The mass change function is based on the following interface structures:

  • Sales orders
  • CRMT_UIU_SLSORD_MASSUPDATE_HDR

  • CRMT_UIU_SLSORD_MASSUPDATE_ITM

  • Rebate agreements
  • CRMT_REBATEAGR_MASSUPDATE_HEAD

  • CRMT_REBATEAGR_MASSUPDATE_ITEM

These interface structures contain all the fields that you can change using the mass change function. It also contains those that change with a changeable field during a mass change due to their dependency on it, but are not changeable themselves.

For sales orders, only those fields in the substructures CRMT_SALESORD_MASSCHNG_HEAD2 and CRMT_SALESORD_MASSCHNG_ITEM2 are changeable, therefore you can execute a mass change for these fields only.

In this IMG activity, you map the interface structure's fields to the transaction's object fields and assign the interface structure's fields to the object fields. SAP already ships mapping for certain fields as standard.

If you want to include additional fields in the mass change function, you must supplement the mapping for these fields (see Activities).

If you want to use an additional field for mass changes, you first have to add it to the user interface structures listed above.

  1. Make sure that the field can be changed.
For example, the partner function sold-to party cannot be changed at item level and therefore should not be assigned.
Extend the relevant user interface structure in transaction SE11 to include the new field and define the relevant data for this field.
  1. Enter the new field in this IMG activity (Customizing table CRMC_MASS_MAPP (Mapping Table of the 1O Mass Update Layer). Specify the following keys for this entry:
  • Name of the user interface structure, that is for example, CRMT_UIU_SLSORD_MASSUPDATE_ITM for mass changes to order items or CRMT_UIU_SLSORD_MASSUPDATE_HDR for mass changes at header level

  • Name of the field in this structure

  • Object key for the field for complex objects, such as partner or status

The object key for the partner, for example, is the technical ID of the partner function, that is, 00000002 for ship-to party or 00000035 for vendor. You can find these values in table CRMC_PARTNER_FCT.
The object key for the status refers to the system status. The technical name for releasedis I1004and I1003 for in process. You can find these values in program CRM_STATUS_CON (transaction SE38).
  • Object name

Object name of the object field to which the field of the user interface structure is to be mapped.
  • Name of the object field

  • Object key field

For complex objects, also specify the corresponding field for the object key, such as the partner function for the business partner.

Note:

Simply adding the field to the Customizing table CRMC_MASS_MAPP is not enough. The corresponding fields have to be entered in the user interface structure before they can actually be changed. Additionally you have to enhance the CRM WebClient UI.

Example for a simple object

Name of the user interface structure: CRMT_UIU_SLSORD_MASSUPDATE_ITM
Name of the user interface field: DELIVERY_BLOCK
Object key: not required
Object name: SHIPPING
Object field: DELIVERY_BLOCK
Corresponding field for the object key: not required

Example 1 for complex objects

Name of the user interface structure: CRMT_UIU_SLSORD_MASSUPDATE_ITM
Name of the user interface field: VENDOR
Object key: 00000035
Object name: PARTNER
Object field: PARTNER_NO
Corresponding field for the object key: PARTNER_FCT

Example 2 for complex objects

Name of the user interface structure: CRMT_UIU_SLSORD_MASSUPDATE_ITM
Name of the user interface field: STATUS_RELEASED
Object key: I1004
Object name: STATUS
Object field: ACTIVATE
Corresponding field for the object key: STATUS






Vendor Master (General Section)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 5052 Date: 20240523 Time: 181043     sap01-206 ( 67 ms )