Dear Ashwin,
you can create the seperate roles for submitting the CR and approving step and assing that in WF uding the Role option in WF.
Dear Ashwin,
you can create the seperate roles for submitting the CR and approving step and assing that in WF uding the Role option in WF.
Sanjya,
check the message out put in the CR step 00,you can set it to error message.
I used the procedure for two BP`s that where created with wrong internal number and the client deleted the BP´s so the link was maintained and gave an error. So we had to delete the link between them and "recreate" the BP´s with correct numbering.
Hope this helps....
The first question: how does this field behave in transaction BP or XK02?
Hello Akshay,
1. you should delete the entries from the BP tables for the incorrect vendors.
2. Setup the vendor integration from direction vendor to BP and set up number assignment as same number.
3. use transaction FLBPC1 to create the BP again for those vendors with correct numbers.
Now these BP's will be available in MDG for display/change.
Regards,
Varun
Hello Sanjay,
Check if you have the message output set as standard as per Riccardo's suggestion, If it does not resolves the issue then you have to write an enhancement spot post these errors are changed to warnings and convert the message type to 'E' again.
Regards,
Varun
For cross-entity validations and derivations, you need to use the BADI. You cannot use the MDG validation & derivation BRF+ application. See this document for how to implement BAdI: USMD_RULE_SERVICE_CROSS_ET How To - MDGM: Checks and Derivations. The document is for MDG-M, but it applies to BP. For more information on the BRF+ application, see this document: How to Check or Derive an Attribute Value in MDG using BRFPlus.
HI Sanjay,
briefly tried in a 6.1 system and for me it works fine.
No clue what could be the problem. That's my configuration, please double check:
Best,
RIccardo
MDG Gurus,
The requirement is to auto-replicate (on activation) for the below scenarios
but should NOT auto-replicate for the below scenario
The auto-replication works fine for the first 3 scenarios mentioned above (BRF+ config has replication steps). The replication steps are not part of the Create Vendor (SUPPl1P1) but the auto replication is still triggered . The system behavior is surprising as it gives a feeling that the replication steps in the BRF+ have no role to play.
One of the options to prevent this is to change the Method Activate_2 of the object type BUS2250. This method has the parameter 'no_distribute'. But this would come across as a change to SAP software which may have future support ability issues.
Are there any other options ?
First of all, the first three scenarios are working NOT because of BRF+ but because the activation step actually distributes data. Try removing the distribution step and you will see that the record is still being distributed. Now, to be able to control the distribution via BRF+ only, you can create a sub-object in transaction SWO1 for object BUS2250. In this sub-object, redefine method ACTIVATE_2 to always set the value of NO_DISTRIBUTE to 'X'. This means that no distribution will be done automatically upon activation. Keep in mind that redefining methods in SWO1 means that you need to add the same logic in the original method in addition to making the changes you need. In case of method ACTIVATE_2, you need to remove this statement:
swc_get_element 'NO_DISTRIBUTE' no_distribute.
Instead, add this statement:
no_distribute = 'X'.
Everything else should be pretty much the same. You will need to define a new variable that replaces the object-private-mo_service variable because it is not going to visible in the BOR sub-object. See how object-private-mo_service is defined in the original program and just define the new variable in the sub-object.
Ah !! .. Ok ..So whats the point of having the replication steps in BRF+ if replication is triggered on activation.
Let me know when you figure out why.
Just curious... why the recommendation is to add the replication step when the replication is triggered on activation.
MDG-M has an explicit check to disable replication upon activation. There, a replication step makes sense.
and MDG - S does not have this ?
Nope
Hello Techies,
I have created a custom UIBB for Cost center screen wherein I have added a new field. I would like to populate the new field with a drop down values based on the company code entered. To do the validation, I have created a custom implementation to the badi USMD_UI_EVENT2. I have applied the filter condition to the cutom implementation with the Configuration that I created for custom UIBB.
The BADI implementation is not being called to perform the validations. When this BADI implementation would be called?
I would like to perform some validation checks like VISIBILITY / INVISIBILITY and perform f4 help values to the custom field that I added.
Thanks,
Kajal
Hi Peter,
Have you checked BADI USMD_SEARCH.
As per the documentation
The following options for modifying the search are available using interface methods:
Regards,
Raghu
Hi,
I have a case where we have separate employee numbers in ECC and CRM.
I have to replicate the org-model from ECC to CRM. Becuase we have different number maintained for Employees in ECC and CRM, the standard replication does not support this.
Can we Org-model data in MDM ? Can MDM support the mapping of different employee numbers used in Org-models of ECC and CRM ?
Hello Kajal,
If your MDG version is MDG 7.1 , then these BADIs are not called.
For modifying UI propertis during runtime you could use BADI USMD_ACC_FLD_PROP_CUST_DEP_SET.
For populating drop down values , you have to put your implementation in respective feeder class
Check this document for further details
https://scn.sap.com/docs/DOC-55226
Regards,
Raghu