Hi Gurus,
We are implementing MDG 6.1 in co-deploy mode.
What is the simplest strategy to be able to edit the account group in Customer record in MDG-C?
I read that before : http://scn.sap.com/thread/3314802
I understand account group is determined by config related to BP role category FLCU01 (if we pick that one) but it is self-evident we want to choose the account group.
Thanks in advance
Hello,
I am setting up the basic MDG for Material scenario and currently have a few questions about the workflow configuration. In transaction SWDD I can view the configuration for workflow WS60800086. There seem to be a number of steps related to determining the correct agents to assign to the new change request. The step "Dialogue Processing" is set to a rule 60800140. When I examine the rule, it is assigned to this function module: USMD5_SSW_CR_USER_AGT_DET. I took a look briefly through the code and it looks like it's doing something at the org level, like reading in the org structure of the user who created the change request. But I can't seem to figure out what exactly the rule is doing.
Can someone provide some input on this?
Hi,
Does anybody know what is the difference between Vendor UI and Supplier UI in SAP MDG-S? Is there a blog/article that shows the difference in UI?
MDG-S config guide says this.
MDG-S offers two different groups of change request types that support either the supplier UI or the vendor UI. Only one of these groups should be used. If you intend to use the vendor UI as alternative to the supplier UI proceed as ...........
I would like to know what is the difference specially in UI screens, so we can go for the one what suits us better.
Thanks
Pravin
Dear Experts,
I have extended the BP data model with the new custom entity to store KNVA/KNVD related values
While creating the change request I am able to perform all the operations in UIBB, once change request approved data has to move from staging to Active are (api)
I am also handled all those using my custom handler class (inherited CL_MDG_BS_FND_HANDLER ) and I am able to save the data into database table . In my case custom UIBB data is getting saved into KNVA and KNVD tables.
The issue I am facing here is , after approving the change request if I open the change request to view the data then all UIBB data is coming as blank
I am assuming data is not getting moved to properly from API à staging.I tried to debug the standard UIBB’s to check from where data is getting from and I can see data is coming get_data method (IF_FPM_GUIBB_LIST~GET_DATA ) inside that it actually getting the data from using method get_collection_data( lr_data ).
But in my case get_collection_data( lr_data ) method not able to get data because lo_entity is not bound .
----- retrieve for all entities
lo_entity = lo_iterator->get_by_index( iv_start_index ).
WHILE lo_entity IS BOUND.
IF NOT iv_row_count IS INITIAL
AND sy-index > iv_row_count.
EXIT.
ENDIF.
*----- proper data
TRY.
CALL METHOD get_entity_data
EXPORTING
io_access = lo_entity
CHANGING
cs_data = <ls_data>.
CATCH cx_bol_exception.
Hi Gurus
We are implementing MDG 6.1 in co-deploy mode.
To get Dashboards in BCV can you confirm we just need to install BI java server? Or do we need to install SAP BusinessObjects Xcelsius Enterprise 2008 SP02(Client) as well and SAP Business Explorer (BI) Patch 9 (Client) as well?
Thanks in advance.
Hi Experts,
I am looking for some clarification of an understanding.
1. As per my understanding of Flex mode and Reuse mode is:
Flex mode:
In flex mode after final level of activation approved data will save in to MDG structures will not automatically updated in the ERP table and structures. We have replicate the data to ERP or any other downstream system
Reuse mode:
in case of Reuse after final activation data will automatically get save into ERP tables of current system. If you want to replicate it to another systems then you have to do a Replication set up.
Is my understanding is correct ?
2. Is there any relation with MDG deployment strategy of on top of operational ERP and as a standalone hub with reuse option and Flex option ?
Can we say that if MDG deployed as standalone hub then the data storage follow Flex option and if we deploy MDG on top of operational ERP then it will follow reuse option ?
Is the categorization is correct ?
3. How to mention any Data model or any entity storage as Flex or Reuse option ?
In standalone MDG hub deployment can we store data using reuse option ?
Regards,
Soumya De
Hi all,
we are faced with a new issue regarding Partner Profile in WE20.
Our Company starts getting EDI-orders from a big group of customers.
In order to avoid maintaining a Partner Profile for each one of them, we are thinking about setting up a customer hierarchy for this group.
They have a common IT-partner who will send their EDI-orders to us.
My question is now: How to set this up in the Partner Profile.
Any ideas?
Thanks in advance
Cornelia
Hello All,
We have a MM data model which is extended with custom fields. The data model is active and SMT mappings is also done.
We added 4 more custom fields to MM model and re-activated. did SMT again and adjusted the Change requests.
Now during 'create material' , the data for these 4 custom fields is getting saved in MARA upon activation. check at mm03.
Suppose we try to edit the same material.i.e. 'change material', we are able to modify the 4 fields also but upon changes and activation, the updates are not getting saved in MARA for only these 4 fields. check at mm03, only create entries exists for these 4 fields but not change.
We have other custom fields also for which the data gets saved either on 'create' or 'change'. but fails to happen only for these fields.
Any ideas?
Thank You in advance.
Shaila.
Hello Experts,
We are facing a problem when i test the report 'ESH_TEST_SEARCH'
Attached error occurs. Any help will be appreciated.
The errors comes in our QA server but not in DEV server
Thank You,
Shaila.
Hi, all.
I'm Derby Lim.
Set in field property BADI ( USMD_ACC_FLD_PROP_CUST_DEP_SET ) lots fields as required.
When I press check button, some(= only MATERIAL entity) fields are checked if not entered like showing following messages.
Other entities' fields are not checked if not entered.
I found that It works on entities have self key. eg. MATERIAL, CARR.
How to fix it? to works on all entities?
Would l rather add custom required check logic for entities don't have self key?
Thanks in advance
Hi MDG Experts,
We are setting up MDG-S and have implemented the Vendor UI. But, we have a Fatal Error, CVI role customizing for direction BP to vendor is not unique (as below). I have located the screens to Set BP Role Category for Direction BP to Vendor, but would welcome any guidance as to what to add or change in order to correct this problem.
Thanks!
Matt
CVI role Customizing for direction BP to vendor is not
unique
Message
no. MDG_BS_SUPPL_HARM020
Diagnosis
The Vendor
UI requires a unique Customizing for business partner roles in the direction BP
to Vendor. The Customizing only must contain a single entry.
System Response
The harmonization report MDG_BS_SUPPL_HARM cannot decide
which role you want to use.
The Vendor
UI displays an error message preventing the creation of vendors.
Procedure
Check and correct the Customizing settings for the business
partner number range under SAP
Customizing Implementation Guide -> Cross-Application Components -> Master
Data Synchronization -> Customer/Vendor Integration -> Business
Partner Settings -> Set
BP Role Category for Direction BP to Vendor.
Hi to all,
I defined 2 attributes of PCTR entity as "authorization Relevant attributes",
during the Creation of the Change Request the Authority-check for the object USMD_MDAT is ok;
The strange behaviour happens when I call standard wda reports such as usmd_change_document (Mass Change) : if the entity isn't active the relevant attributes aren't correctly filled and the authority-check is performed with blank KEY FIELDS.
I found the check is in cl_usmd_mdf_dbaccess_services=>filter_data
LOOP AT ct_data INTO <ls_data>. * Ignore all inactive data. CHECK <ld_active> = usmd1_cs_active-active.
in this way the authority performed in CL_USMD_AUTHORITY->CHECK_AUTH_DATA isn't correct..the key fields of the entity are filled correctly but the attributes are filled with spaces
any ideas?
Thank you!
Hello
MDG-F Screens (Data Model 0G) are based on feeder class 'CL_USMD_ENTITY_VALUE2_PROXY'. May I know what object to change to limit the drop down values for a field?
Also if I have implemented an ABAP based search help (se11 search help) and want to pass some parameters to Search help function module exit to limit its output list, how can I do it from MDG?
Many Thanks in advance
regards
Pranav
hi gurus,
please help me to know if there is any option of "advanced" or "quick" search option in MDG EHP6.0?
Give me some inputs if any configuration is necessary for that as my client is asking for the above options in search tab screen of nwbc, and i am unable to find any such tab in the screen for material governance or anywhere for material search option.
Hi
We are implementing MDG 6.1 for Customers in co-deployment mode, meaning users that can create a CR can also access XD02 t-code;
Those users have XD02 in authorization object TCD.
How can we prevent them from using t-code XD02? We do not want them to bypass approval workflows.
Thanks
Hi,
I need to upload VENDOR intial data in MDG, I only find BAPI_VENDOR_CREATE for that.
Please suggest me the suitable one.
Samrat
I just wanted to know if SAP MDG 6.1 SP 3.0 is compatible with SAP ECC EHP6 7.0.
Also let me know the thread if any where i can see details pertaining to SAP MDG compatibility listed with various SAP ECC systems.
Has anyone implemented Dual Control for MDG-Supllier ?
Hi,
I am new to the SAP MDG development .
Pls share me the suitable documents thats give me the detail step of mdg implementation.
Hi,
In MDG- I have extended Supplier General section by extending BP_CENTRL with custom fields. I am able to see them under General Section for the Supplier Governance but they are also visible under Customer.
Is there any way to disable for Customer.
Thanks,
Shailaja.