Pricing in MDM?

[Former Member]

We are looking at SAP MDM for both handling new/changed materials and prices received from vendors.

We have today a lot of BID prices (customer prices) received every day.

How is functionality in SAP MDM for handling prices with delta changes to SAP ERP?

We are today using Sales deals in SAP for handling customer prices.

We would like to use SAP MDM in the future for updating these prices.

There are requiered a lot of logic and format controls on the files received from vendors.

How is this handled in MDM?

Best regards,

Terje

[Former Member]

OK

[Former Member]

e

[Former Member]

The most important question wasn't asked -- what is the volume of the daily price updates? Do you expect to update a majority of the records with new/updated prices every day? If so, I'd consider not storing the data in MDM. Not all data must be managed in MDM, and you should try to limit yourself to relatively non-transient data.

[former_member201266]

Hi Terje,

I completely agree with all the above comments and like to tell give you an scenario which will help you to solve your problem,

First as SAP standard Repository's use; you to use an Qualified table for pricing with different required fields(price, date) etc...

Now you can create an Workflow where in, when ever an new price is been update it's reflected in the price qualified table along with the date its been updated. By doing so you will have the updated price shown in your main table and all the old prices will be saved in the qualified lookup table along with there dates.

Now as you say there are lots of prices which have to chaged on regular basiscs, so initially you create an MAP using import manager and select the option for only updating the matched feilds and call the workflow for that map and save the MAP. By doing so you can simple use this map every time there is change in the prices.

The only task for you is, first to design an repository with proper structure, then create a workflow and the a map in import manager; then rest of the work is as simple as simple.

Cheers & Regards,

Cherry.

[Former Member]

Hi Terje,

Now I can see many queries in your post:

1. For the Delta changes in the prices: Now, we have Workflows in SAP MDM which can be used to catch the Delta changes in the Prices ( WIth the help of Validations ).

2. Hence any updates on the price can be taken into MDM Workflows and then necessary action can be taken on those records.

3. But if you want to maintain the Versions of the Prices, I am afraid that this is not possible in MDM. Only the latest Price will be eventually stored in MDM. However, you can track any changes using Change Tracking Functionality in MDM.

4. New Records can be handled very easily in MDM.

Also if you have to maintain more than 1 value for Price, you can do it by making the Price as Multi-Valued in MDM.

Hope it helps.

Thanks and Regards

Nitin Jain

[Former Member]

Hi Terje,

As far as I understand your requirement.It can be met within MDM by creating a proper data model.

For eg : MDM can be used to handle Prices information within MDM by utilizing the qualified table feature in MDM.

Price is a field whose value ill depend on other parameters may be location ,market etc.For such kind of dependent data we can use qualifer and non qualifier concept.It will use the values from other field to populate the price field.

MDM is capable to handle both delta load as well as full load also if you have some data stored in MDM you have the option to update it with new values or replace it as well.

As for logics MDM has Assignments and Calculated field option where we can build expressions to calculate and derive some logics .

Hope it helped

Kindly reward points if found useful

Thanks

Simona

[Former Member]

Lookup Qualified Flat is best suited to your scenario. Basically pricing information is a transactional data as it frequently changes on the base of country/region. So a lookup qualified flat is maintained in MDM for these kind of data in which Price will be a qualifier and Region will be non-qualifier and at record cretion Price will qualify on the basis of region.

Now in main table record you can maintain more than one region for a single material with different prices basedon the region.

Please rewrd if helpful.

BR,

Alok