CMDM - Central Create

[Former Member]

Hi all

Can anyone offer some tips on how the handle the distribution process in CMDM scenario

- What are the additionl modelling requirements

- How to track the create status

- exception handling

- Vendor Id or Material number create

All comments welcome

Rgs

C

[Former Member · Accepted solution]

Hi Ccr,

These are the inputs from my side for your following queries :

What are the additionl modelling requirements

For effective CMDM, I feel you should have an User Interface- EP from where you can create data in MDM. This will be easily accessible by any 1 who has authority to cretae Data.

Also in MDM, it would be better if you add Workflows to govern the entire Procedure of Creation of Data.

How to track the create status

The Workflows that you add will be available to you as Jobs in the UWL in EP. Hence the entire procedure of creating Data will be known.

exception handling

I do not feel there is any scope of Exception. You will have Validations which will be basically ensuring that the data is entered in the Correct format.

Vendor Id or Material number create

For generation of material ID or Vendor ID- You can do it in 2 ways.

Externally- You can give your own Material no while creating the data.

Internally - You can use Auto-ID/ Calculated Fields to generate the Material No within MDM.

And if you want to harmonize data once it is created, you can easily create syndication maps for different systems and then distribute the data.

I hope it helps.

Thanks and Regards

Nitin Jain

[Former Member]

Hi,

• Your First Question and the Last question goes in Hand.While you design a data model with CMDM as ur scope, the main thing which u need to consider is the Number range interval. Number ranges depends on the business aspect(how far a vendor base or how many materials are used ).

Create a separate Lookup Table to hold the number range in MDM.

EP is a good-option to be used as a front end,since the enduser finds it difficult to work with Data Manager because its not user -friendly.

• If a workflow is trigered, In EP(also in Data Manager) you can see the Status of the creation(even updation of a record)

Thanks,

Felix

[Former Member]

Hi all, thanks for the input,

some more specific questions Anyone out there have any experience with modelling there repository to manage the distribution process?

- where we can define the target for system distribution

- how trigger the distribution

- notify the other parties (PI,target system admin)

- Monitor the create status in the target system

Regard

Con

[Former Member]

Hi Con,

• where we can define the target for system distribution

In syndication maps or XI depending on target system requirements.

• how trigger the distribution

MDSS settings can be an option.

Or workflow to trigger syndication (I didn’t done this)

• notify the other parties (PI,target system admin)

XI mails, or source systems workflows.

• Monitor the create status in the target system

As soon as its created in the target systems, change pointer or status IDoc can do the trick.

Hope this helps,

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/cmdm+process

+ An

[Former Member]

Hi Ccr,

Regarding your queries, followig are my inputs :

where we can define the target for system distribution

solution : In MDM Console, For a particular repository, GO to ADMIN node-> Remote Systems.

In MDM, every source and target system for MDM is created as a remote system. Hence you can define your remote system there.

Also for Data flow between the MDM and your target system, you will have to define a port.

You will find this under : Console->Repositroy->ADMIN->Port

Inbound Port- For data flowing from system into MDM

Outound Port- For data flowing from MDM into target system ( This be used for your requirement of distribution)

how trigger the distribution

This can be done in 3 ways :

1. Using MDM Workflows- you can create the complete flow of data in MDM WOrkflows, and then distribute the data to the target system using a SYNDCATE stencil.

2. Using MDSS - This is syndication server which can be used by creating a Syndication Map in the syndicator. In this map, you can choose the target system. Then define this map in the Outbound port that you had created in Console.

3. Using Syndicator- You manually also syndicate the data to your target system manually using syndicator.

The 2nd option will be the best if you want to automate your distribution process.

notify the other parties (PI,target system admin)

Create 1 user in MDM Console under the Admin->Users.

Then use the MDM Workflows, and using the Notify step, you can send mails to notify the ADMIN person of the target system.

Monitor the create status in the target system

As An has mentioned that IDOC status can be used for this. It also depends upon the target system. System can also poll constantly, or else if Xi is involved then it can be used. MDM distiributes data into a folder, from where the XI or the target system picks up the data. Depending upon the target system, the requirement can be fullfilled.

Hope it helps..

*Please reward points if useful

Thanks and Regards

Nitin Jain

[Former Member]

Thanks to all for the input. Very helpful

Has anyone ever modelling the repository with additional fields so the Data Adim.

-Can View/Select the systems where the records are or should be created - Qualified lookup prehaps.

-Can received a reciept from the traget system and reocrd this in MDM - a Pass Fail indicator

Any comments in this

Regards

Con

[Former Member]

Hi ccr,

Has anyone ever modelling the repository with additional fields so the Data Adim.

-Can View/Select the systems where the records are or should be created - Qualified lookup prehaps.

Sol - Frankly speaking I have not understood your requirement. What does the admin exactly want to see?

Additional Fields can be added in MDM based on the requirement.

If there are multiple sources, and you want to see the source system from where the data is coming into MDM, then you can keep a field in both Sources and MDM, which will hold the Source data Name. The list of the source systems can be maintained in a Look-up[Flat]. And according Mapping can be done. Hence then Admin will be able to identify the source system from where the Records are coming into MDM by making a search in the Data Manager.

Also the admin can always view the Logs on the Repository and the server level from the Console.

If something else, then please re-frame your question.

Can received a reciept from the traget system and reocrd this in MDM - a Pass Fail indicator

Solution-

1. You can create a field of type Boolean in MDM, which will hold the Values TRUE or FALSE. Hence this will be used as a flag in MDM, which can be populated in MDM based on the receipt( for ex, X, Y etc.). However again, this can be done while taking data into MDM. While exporting data from MDM, MDM will not be able to get any receipt from any target system.

But you can use this option while distributing data from MDM :

Suppress unchanged Records- This will suppress the records which have been distributed before, and they have not been changed. This avoids repititive distribution of Data.

I hope I have addressed your requirement. If not, then please explain your requirement again.

*Please reward points if useful.

Thanks and Regards

Nitin jain

[Former Member]

Let see if I can summaries:

Data Distribution for your target systems can be configured explicitly or implicitly

Explicit Distribution: Data Admin defines the target systems after records have been approved for distribution. A message is send back to the Admin after distribution to confirm the create status in the target systems.

Implicitly Distribution: Syndication is triggered (MDSS setting, workflow etc). Idoc pointer confirms create status for the records.

For the first option clearly there is an impact on the data model so that you can give more visibility to the user.

With the second option the distribution context is “hidden” in the underline configuration of MDM and PI so checking of errors (for a normal user) is more difficulty.

Anyone got experience with CMDM with an explicit distribution context?

Thanks all for the input to date

Regards

Con

[Former Member]

Hi ccr,

Thnx for explaining the requirement.

Explicit Distribution, According to me, it is not possible. As MDM can only import and export the data to the target system. And when MDM is exporting the data, the data will reach the target system.

But there is no way, that after create status, some flag gets automatically ticked in the MDM system as once the data is syndicated from MDM, it has no control over it.

But if you want to tick a flag just after the distribution of data from MDM, you can use workflows.

Start->Process->......->Syndicate->Assign->Stop

Hence, you can create an additional boolean field field in MDM and after distributing the data to the target system, MDM can directly assign TRUE to that Boolean Field.

Hence Admin will be able to view the syndicated records based on the value of that Boolean Field.

Lets see what others have to say.

Hope it helps.

Thanks and Regards

Nitin Jain

[Former Member]

Hi CCR,

When you are going for central master data creation ,the distribution process can be handled in the following ways.

What are the additional modelling requirements

- When master data is designed to be created centrally in MDM,it means you do not have any inbound interface so when there is a request for master creation there has to be some data custodian responsible for master creation.This can be done in one of the two ways

1) MDM data Manager centrally

2) Enterprise Portal

For this additional modelling required would be an Effective workflow design either in MDM or EP with roles and user defined so that data flow for master creation and enrichemnt is controlled.

An EP server nad UWL or Guided procedure configuration will be required.

Some Validation rules can be created so that Master record creation is complete and no Mandatory field is left empty or populated with incorrect data.

How to track the create status

- Create status can be tracked by using a Create stamp field.This field will get automatically updated with the date and time when the record is created ,then you can use a filter on this field to identify records date creation.

- Besides whenever you are using workflow for data creation then worflow details like teh job id nad the strat and end date can also be sued to identify record creation.

exception handling

Exception will not occur as MDM exception are related to errors in mDFM source file when ever imported into MDM

.So as you are creating the data directly in MDM there are no chances of exception in data.

Vendor Id or Material number create

- MDM still does not have the feature of Number assignment as in SAP R/3 or ECC.All that is possible in MDM is the assignment of an MDM internally generated id called as auto id which alwys gets incremented sequentially and cannot include alphanumeric data entry.

- So An MDM auto id field if created will automatically populate an id for the MDM rec when created.

- If you wnat any unique sequence for the number range may be you can sue MDM assignments for it.But how it will work i am not sure.

Hope This answers most of your queries

Kindly reward points if found useful

Thanks

Simona