Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-AF (Application Component) Application Framework⤷
USMD_REMOTE_WUL_FRW (Package) Remote where used list in framework
IMG Activity
| ID | USMD_REMOTE_WHERE_US | BAdI: Remote Where-Used List |
| Transaction Code | S_BT6_28000062 | (empty) |
| Created on | 20110114 | |
| Customizing Attributes | REMOTE_WHERE_USED | BAdI: Remote Where-Used List |
| Customizing Activity | USMD_REMOTE_WHERE_US | BAdI: Remote Where-Used List |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | USMD_REMOTE_WHERE_USED |
Use
This Business Add-In (BAdI) is used in the Data Quality and Search (CA-MDG-DQ) component.
You can use this BAdI to display a list of entities used in Master Data Governance in theremote system.
This BAdI contains the following filters:
- Data model
- Entity type
Each implementation is used for searching remote where-used lists for one entity type.
This BAdI has one interface method, GET_REMOTE_WHERE_USED_LIST, containing the following parameters:
Import Parameters
- IV_ENTITY_TYPE: Specifies the entity type you want to search
- IT_ENTITY_SEL: Contains the value of each key
- IS_REMOTE_SYSTEM: Sets the remote destination. You can only specify one system at a time.
- IV_MAX_HIT: Sets the maximum number of search results
Export Parameters
- ET_RESULT: Displays search results, including the business system name, key columns, and text columns of the data lines that the entity uses
- ET_MESSAGE: Reports error messages
Requirements
- You have configured the business system, logical system, and RFC destination in Customizing for Data Replication under Define Custom Settings for Data Replication -> Define Technical Settings-> Define Technical Settings for Business Systems.
- You have created a user for the RFC destination with the authorization to view tables S_TABU_DIS and S_TABU_NAM and to display activities with corresponding table names. This authorization is required because in the default implementation, the remote function module TABLE_ENTRIES_GET_VIA_RFC is used to retrieve remote data.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
BAdI Implementations
- MDG_BS_FIN_RMT_WHERE_USED
It searches table T030 in the remote system to see if the given accounts are used there.
You can use the following implementation options as an alternative to the BAdI implementation:
- Use the remote function call module TABLE_ENTRIES_GET_VIA_RFC as used in the default implementation to retrieve remote data stored in tables.
- If there are operational data providers (ODP) modeled in the remote system for the area that you want to search, and you are familiar with the ODP API, you can follow the instructions below in the remote system:
- Build a query for each ODP.
- Create a remote function call module, using class CL_BS_ANLY_LIST_SERVICES to access the ODP (in the query).
- In the enhancement implementation of the MDG system, call the RFC you created.
- If SAP NetWeaver Enterprise Search is used in your MDG landscape, you can use this in your BAdI implementation provided you are familiar with the Enterprise Search API.
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
In the default implementation, the data model is 0G and the entity type is ACCOUNT.
Business Attributes
| ASAP Roadmap ID | 899 | not to be assigned |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20110114 |
| SAP Release Created in | 703 |
