Settype CRMM_PR_SALESA attributes mapping logic between CRM and ERP

[JerryWang]

When I create a material in ERP and download to CRM, corresponding data is generated for settype CRMM_PR_SALESA.

It contains the following data downloaded from ERP:

PROCESS_UNIT

Unit of Measure in Which the Product Is Sold

In ERP, it is stored in table MVKE-VRKME.

Maintained in ERP via tcode MM02:

In CRM WebUI, it is displayed in this field.

CASH_DISC

Specifies Whether a Cash Discount Can Be Given for the Prod.

Checkbox maintained in ERP:

table field: MVKE-SKTOF

In CRM:

MIN_ORDER

A minimum order quantity in base units of measure, which is the minimum quantity a customer can specify during order entry.

table field: MVKE-AUMNG. In my example, in CRM it is maintained as 3:

In CRM, it is 0.25 BT

Because in ERP, it is maintained as 1 BT = 12 EA in ERP.

S_ITEM_CAT_GROUP

Distribution-Chain-Dependent Item Category Group. It could be different from standard item category group maintained in material level.

In CRM, this item category group is displayed:

CRMT_DELY_UNIT

Delivery quantity together with unit:

In CRM:

LOC_BUPA

Delivering Location

Plant 0001 must be downloaded into CRM first before this material is downloaded. For detail please refer to this blog How to download ERP plant into CRM via request download .

UNSALE_NOT_VAR

You can maintain the sales unit for each material and sales organization/distribution channel. The sales unit is proposed in Sales and Distribution (SD) documents such as sales orders. If a variable sales unit is not allowed, the unit specified in documents may not differ from that in the master record.

In ERP:


In CRM:


PRICE_PRODUCT

used in pricing scenario: Material master record that the system uses as a reference for pricing purposes.

In ERP:

In CRM:

The detail mapping logic is implemented in this subroutine:

PROCESS_UNIT