Hello Naren
To automate the entire process, you have to write code but that is not the proper way. You can use MDMGX or the file upload method and set up jobs but the edition and CR you need to create manually before.
Kiran
Hello Naren
To automate the entire process, you have to write code but that is not the proper way. You can use MDMGX or the file upload method and set up jobs but the edition and CR you need to create manually before.
Kiran
Can you give one example? It shall be same in both.
Kiran
Hello Tarynn
In MDG 7 its the same...But there is a way out. Create a CR - as a Template and keep it in process always. Don't approve the CR. Kind of the dummy CR. Select only one company code and deselect rest.
While creating new CR, use this CR as template. Just change the data and it works perfect.
Kiran
Hi Kiran
My Hierarchy top node is suppose P1000 under which there is sub node P1100.
When I create profit center in MDG and replicate it in ECC. In KE53 it seems hiararchy area is P1000 which is correct.
Then in MDG I perform hierarchy assignment with processing muliple object and assign above created profit center under P1100 and replicate same in ECC.
Now in ECC it same in KE53 hierarchy area is P1000 and in KCH3 under P1100 their is assignment of above created profit center.Is reason for this?
It seems that for IDOC replication with WS 72100012 it creates only one idoc and not two idocs,Does it mean we need to assign WS72100012 to change rquest type Create Profit Center along with Process hiearchies?
Below are workflow steps for WS72100012
Did you need to assign processor under other workflow or configure rule based workflow?
Hi
Try activating below sets and let me know if it works.
use the transaction SFW_BROWSER and then open any of the MDG
Business functions and then open the switches and then switch BC sets
then double click to open the new screen here you give the BC set
names below and activate them in the same order.
CA-MDG-APP-BP_DE_VC_USMD004_C_02
CA-MDG-APP-BP_DE_VC_USMD004_C_03
CA-MDG-APP-BP_VC_USMD004_C_04
CA-MDG-APP-CUS_VC_USMD004_C_01
CA-MDG-APP-CUS_VC_USMD004_C_02
CA-MDG-APP-SUP_VC_USMD004_C_01
CA-MDG-APP-SUP_VC_USMD004_C_02
CA-MDG-APP-SUP_VC_USMD004_C_03
Hi Kiran,
I have checked all the above mentioned sets but were unable to found CA-MDG-APP-BP_VC_USMD004_C_04 .
All the other sets are already in active mode.
Regards,
PB
Hello Experts
Can we create hierarchy for ERP customer (Not BP) in MDG 7.0?. We are using ERP Customer UI. The standard CR Type to create hierarchy is for BP and not for ERP customer. I tried using the same business activity for ERP customer but it won't work.
If I have to create hierarchy for customer (like hierarchy in ECC - VDH1N) in MDG is there any way out?
Kiran
Hi Michael
Yes it is there in workflow bulider. But still no second idoc getting triggered. Is any setting for MDG change pointers for affected profit center so second IDOC trigeered automatically?
Hi SCN User,
See if the below SAP Note helps you in overcoming the error:
2058868 - Error message USMD1 079 when checking the model definition
Best Regards
Uday
Hello Tarynn,
I don't think there's any standard MDG functionality that could influence this.
Are you trying to influence the data??
If, yes, as suggested by you, this could be very achieved using derivations.
BAdI USMD_RULE_SERVICE_CROSS_ET
In the implementing class provide, the implementation for derive method.
Data updated here in will definitely be reflected in the CR data. You can add some data/delete some data on load itself.
If no, ie., if you are trying to manipulate only the selection and de-selection of rows on the UI, then that could be done by manipulating methods of the underlying feeder class. But yes, this has to be done via an enhancement.
Please let me know in case you need more information here.
Best Regards,
Avinash Bolisetty
Hello,
I think I can add a little here.
Key handling is generally done at the feeder class level.
There are multiple types of keys we generally deal with like semantic keys and technical keys.
Both of them have to generated newly whenever we are adding a new entry to the entity and this has to be done in the feeder class.
In case you want a new technical key, you can use the convinience API and it'll generate a key for you.
In case it is a semantic key like bank, we might want to handle it in the get_data of feeder class ourselves.
Please see what is the data that you are getting to the process event of the corresponding feeder class as soon as you add some data hit enter.
Then manipulate the key for the newly added key which is generated wrt to the current entity. You could use a simple counter.
This should definitely solve the issue.
This ideally should have been taken care of in the standard itself, but a simple redefinition like above would definitely solve the issue
Regards,
Avinash
Hello Thomas,
Looks like this is an issue with the wiring.
There are communicator related setting that we'll have to maintain while creating a new Z configuration.
Please check for the communicator related settings in the document DMM265 in page number 36. The document is related to custom objects, nevertheless, wiring should remain the same.
Once you create the correct wire for MDG_COMMUNICATOR and link it, as mentioned in the document, you should be able to get the CR UIBB in editable format.
Best Regards,
Avinash Bolisetty
Hello Swati,
This is controlled based on the fields mentioned in the match profile for the entered data model and main entity.
Go to MDGIMG-> General Settings-> Data Quality and Search -> Search and Duplicate Check-> Configure duplicate check for entity types.
A match profile has to be mapped here for the data model and main entity for which duplicate check has to be enabled.
Maintain the match profile fields under 'Define Search Applications' view cluster.
From then, the duplicates will be fetched based on the attributes entered in the match profile.
Best Regards,
Avinash Bolisetty
Hello,
Looks issue with MDG communicator and even we had the same issue,
Once you copied standard to your Z* UI then same has to be done for MDG communicator with the same name what is used for UI (Z* name),
If that is done then open the Z* MDG communicator then check the landing page or Page Id in the communicator (in our case we used Z*_BS-BP_OVP) and same has to be updated in your Z* UI in main page navigation, reason to use Z* is to reflect the custom changes in our UIs,
Make sure that communicator configuration name and your UI name matches,
Regards
Ajay
Hi Tarynn Sampson,
One of my clients had the same requirement in MDG-F.
We had to go via the enhancement route whereby the postable in all company codes field was unchecked and hidden by default.
Also all the postable flags for every company code was unchecked via the enhancement.
Best regards
Uday
Hi Taynn
If profit center accounting is active in taget ECC then we need to assign all company codes to newly created profit center and as MDG uses backend ECC customization by default in ZMDG all company codes are selected. It is same in ECC also