Hi All,
I am having json like this..
var data=
{
[
{
"name":"fsdf",
"id":"dfd",
"child":[
{
name:"a",
class:"1"
},
{
name:"b",
class:"2"
}
]
},
{..................................}
]
};
I want to bind "class" in the json for the "text" property in tree node in xml view.
Please suggest me on this how to set path for the above requirement.
Thanks in Advance.
Hi all,
i have used coding from standard sap program RPTEUP10 in my z program
to insert time events in table teven.
i am getting the below error.
00011276 FILL_NT1_FROM_PDC I I
here 00011276 refers to the personal no.
any suggestions please.
Hi Guys,
I'm trying to work out if it is possible to use one common as2 url for multiple trading partners.
The url would look like https://b2b.yourcompany.com
We use SAP Web Dispatcher to forward requests to PI. In PI, we use AS2 Adapter from SAP B2B Add-On. In web dispatcher, we only can redirect requests based on hostname, protocol, port and etc. I see source ip address would be an option to differentiate partners but it is not available in web dispatcher redirect module.
Is it possible? If so, what's the best way to route messages to different sender channel?
Thanks in advance.
Hello,
We are currently using the alerting module to monitor our jobs.
We have a basic setup
For some reason we always get an OP message "Could not send alert to [emailTXTMSG@company.com]. All this address contains is a distribution list of cell numbers with wireless provider extensions on the end so you can send out through email and receive as a txt message. We get the alert but what ends up happening is the email gateway continues to resend the alert unless we go in a delete the job that failed. The other alert sends out correctly.
Any ideas?
Thanks.
Hi,
I've realized a query that join the VBAK, VBAP, VBEP to LIPS and LIKP. The query works, but it's too slow.
How I can create an internal table with the following fields?
| VBAP-VBELN | VBAP-POSNR | VBEP-ETENR | VBEP-EDATU | LIPS-VBELN | LIPS_POSNR | LIKP-WADAT_IST |
|---|---|---|---|---|---|---|
| Key | Key | Key | Output | Output (sort) | Output (sort) | Output |
I need this table to extract:
I'm open to apply other solutions.
Excuse me, but i'm not skilled as abaper.
Thanks and best regards.
Antonio
Hi ,
I have created a simple datawindow in Powerbuilder classic 12.5 build 5609 and I have Imported to Powerbuilder NET same version and build.
When I try to see the retrieval arguments I get the below
As you can see from above the second and third retrieval argument are not showing.
So what I did (anyone would have done this) I retyped them. And of course I got the below
Any ideas ?
Appreciate any help you could give me.
thank you
Hi Experts,
Today we have done few configuration related to AD and UME integration which doesn't go well. Please provide your valuable suggestions to overcome the issues. Steps what we followed are :
1. We have created service user in Ad
2. Configured service user with SPN (service prinicpal name)
3.Logged into nwa : http://hostname:port/nwa
4. Done UME configurations, please check attached doc for screenshot
5.Restart AS Java
We are looking to load the AD users into UME, could you please suggest what needs to be done after these steps.
Thanks,
Lokesh
Hi Guru's,
in the sap note 2001016 and 2001498 and other on the same matter, is mentioned the sapnote 1996524, but this note is not released for customers yet.
Does anyone has opened a message to the support or could share more information about it?
As it's a mandatory step for implement the solution we cannot try the entire procedure.
The title of sapnote 2001498 is "eDocument Italy - Fattura: Data Dictionary Objects (Prerequisite for Note 1996524)"...
Thanks to all for useful informations.
Gabriele
It doesn't look like we will get a clear roadmap from SAP on the future of PowerBuilder. It doesn't look like there is any chance of PowerBuilder being Open sourced or handed over to a third party more interested in investing in it.
So... would it be possible to create a mono-like project for PowerBuilder? and would it be beneficial for the PB community?
Greetings,
We are in process of integrating SAP PM and GIS. We are thinking of storing GIS spatial data into SAP tables.We are not using HANA.
Can anyone please advise how to achieve this.
Any idea, whether we can run spatial analysis in SAP, without relying on GIS?
Regards,
Ahmed
This page provides domain-specific information on how to add fields or capabilities to your solution, reconfigure your solution, or integrate your solution within your software landscape. The documents are typically enriched with screenshots, instructions, and - where necessary - sample code.
The documents are valid for releases EhP5 to MDG7.0.
Disclaimer
SAP code or application samples and tutorials are NOT FOR PRODUCTION USE . You may not demonstrate, test, examine, evaluate or otherwise use them in a live operating environment or with data that has not been sufficiently backed up. You may not rent, lease, lend, or resell SAP code or application samples and tutorials.
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| Smart Business | |||
New May 2014 Configuration and Use of Smart Business for SAP Master Data Governance | SAP Smart Business applications provide insight into the real-time operations of your business by collecting and displaying KPIs directly in your browser. To do this, SAP Smart Business combines the data and analytical power of SAP HANA with the integration and the interface components of SAP Business Suite. To enable the implementation of SAP Smart Business applications in SAP Master Data Governance, this guide describes the tasks and concepts necessary for initial setup and configuration of all components in the SAP Smart Business system landscape. | MDG7.0 (Feature Pack) | MDG7.0 (Feature Pack) |
| HANA | |||
New May 2014 HANA Drill Down: Extensibility Guide | The SAP HANA-based search of master data is one of several ways of searching master data that reside in SAP HANA. You can create a HANA view and configure it to explore the master data or to perform a drilldown search. This guide describes how you can flexibly extend the drilldown application with custom buttons and hyperlinks that enable navigation to other UIs. | MDG7.0 (Feature Pack) | MDG7.0 (Feature Pack) |
SAP | You can use this document to implement the access class interface for your reuse model so that the HANA-based search of master data can retrieve both active data and inactive data. | MDG7.0 | MDG7.0 (Feature Pack) |
| The SAP HANA-based search of master data is one of several ways of searching master data that reside in SAP HANA. You can create a HANA view and configure it to explore the master data or to perform a drilldown search. If the HANA view contains attributes with technical keys (such as Country Keys or Region Codes), the drilldown search results display technical keys instead of text descriptions. To ensure that text descriptions display in the browser panes and result sets of the drilldown search, you must manually modify your generated SAP HANA views in SAP HANA Studio by adding text joins to the corresponding text tables. | MDG7.0 | MDG7.0 (Feature Pack) | |
| BI Content | |||
With MDG 6.0 EHP6, SAP supports BI Content; reports and functions that analyze how effectively change requests are processed in your organization. You must activate the content first, as described in this document. You can analyze change requests from the following perspectives:
| EhP6 | MDG7.0 (Feature Pack) | |
| User Interface | |||
How to use a customer specific UIBB in MDG application 'Create Change Request' | This tutorial describes how to use a customer specific UIBB in the MDG application 'Create Change Request' (WebDynproApplication usmd_crequest_create). | MDG6.1 | MDG7.0 (Feature Pack) |
Customizing Navigation for Change Request Steps in the User Interface for Multi-Record Processing | In multi-record processing, you can define different user interfaces for the same change request step. For example, you can make the initial step appear different to the approval step or the processing step. | MDG6.1 | MDG7.0 (Feature Pack) |
| Creating a UI Configuration and Integrating it with the MDG Communicator | You can copy an existing UI Configuration and adapt it to your needs. As an example, we copy the Component Configuration of the Overview Floorplan (OVP) USMD_SF_CARR_OVP and delete the attachment User Interface Building Block (UIBB). | MDG6.1 | MDG7.0 (Feature Pack) |
| Customizing Navigation for Change Request Steps in the User Interface for Single-Object Processing | During Single Object Processing, you want to define different User Interfaces for individual Change Request steps. For example, in a Supplier Scenario you might want one step to make the general data visible, and, in another step you might want only the purchasing organization data to be visible. | MDG6.1 | MDG7.0 (Feature Pack) |
| How to Add Fields to the Change Request UI (MDG EhP6) | This article describes how you can do this with the new UI technologies that are used by the domain specific Web Dynpro applications for material and supplier with enhancement package 6. | EhP5 | MDG7.0 (Feature Pack) |
| Hiding Fields in the Change Request User Interface | You want to hide fields of the change request UI. For example you do not want to allow users to enter a due date when submitting a change request. | EhP5 | MDG6.1 |
| Enhancement of the User Interface Building Block for Change Requests | In this example, you require an extra parameter to control the process and the workflow for change requests - Requesting Business Area. You do not model this parameter is as part of the MDG data model because it is not part of the business context. Instead, you store the parameter together with the change request number in a Z-table. In addition, you place the parameter on the change request UIBB on the tab for the general data. The user can select from business areas defined in Customizing. (The relevant data element is GSBER and the relevant table is TGSB). When a user opens the change request for display, the Requesting Business Area parameter is displayed and cannot be changed. | EhP6 | MDG7.0 (Feature Pack) |
| Video tutorial on how to create a lean request step with a role-specific UI and less strict data validations in MDG for Custom Objects. | EhP6 | MDG7.0 (Feature Pack) | |
New December 2014Default | This document describes how to initialize fields of the Single Object Maintenance UI with default values. Different techniques for custom UIs and SAP-owned UIs are discussed. | MDG7.0 (Feature Pack) | MDG7.0 (Feature Pack) |
| API | |||
| Updated January 2014 Application Programming Interface Customizing Guide | Depending on the software release, MDG offers different APIs for consumption with different functional scopes. This guide describes the Application Programming Interfaces for each release. | EhP5 | MDG7.0 (Feature Pack) |
Updated June 2014How to Read Approval Info for Master Data by Calling MDG API | This document applies for all MDG master data. It is especially useful for the G/L Account because of the SOX (Sarbanes-Oxley Act) compliance. In the G/L Account area, MDG-F is also known for its SOX compliance. SOX requires thorough tracking of changes with approval processes. This document shows you how to get relevant approval information for the G/L Account by calling all MDG APIs. | EhP5 | MDG7.0 (Feature Pack) |
Workflow | |||
| How-to handle Entities with type 4 in BRF+ | This article explains how entity types 4 with 1:1 and 1:N cardinality are handled in BRF+ by an small example. | EhP5 | MDG7.0 (Feature Pack) |
| How to Check or Derive an Attribute Value in MDG Using BRFPlus | With SAP Master Data Governance you can use BRFplus to define rules for checking attribute values or to derive them. This step-by-step guide shows you how to create such a rule. This procedure can be applied to any MDG application or data model. The MDG for Custom Objects Example Scenario is used as an easy to understand basis for this how to document. | EhP5 | MDG7.0 (Feature Pack) |
BADI USMD_SSW_RULE_CONTEXT_PREPARE | EhP5 | MDG7.0 (Feature Pack) | |
| Rule Based Workflow: Enhancement for parallel workitems | BADI USMD_SSW_PARA_RESULT_HANDLER | EhP5 | MDG7.0 (Feature Pack) |
| Rule Based Workflow: Enhancement for Flexible User Determination | BADI USMD_SSW_DYNAMIC_AGENT_SELECT | EhP5 | MDG7.0 (Feature Pack) |
BADI USMD_SSW_SYSTEM_METHOD_CALLER | EhP5 | MDG7.0 (Feature Pack) | |
Sending an E-mail notification from the rules-based workflow | EhP5 | MDG7.0 (Feature Pack) | |
Setting up extended workflow notifications in order to send out e-mails when new workflow items are generated (also allows you to include a link to the workflow inbox in the generated e-mail). | EhP5 | MDG7.0 (Feature Pack) | |
| How to add an additional task to the inbox | You create own workflow definitions with new workflow tasks and want to see the corresponding workitems in the MDG inbox. | EhP5 | MDG7.0 (Feature Pack) |
Description how to trigger an Email to all users involved once a change request is finally approved. The Email contains a protocol of the change request incl. changes and associated metadata. | EhP5 | MDG7.0 (Feature Pack) | |
| Extensibility | |||
Description how to extend new attributes for entity type | EhP5 | MDG7.0 (Feature Pack) | |
| SAP How-To Guide Develop a Custom Master Data Object in SAP Master Data Governance (ERP 6 EhP5 and EhP6) | Many companies want to manage custom object in a central Master data system to be able to harmonize this information across the landscape. Custom objects can be individual defined object such as assets or locations. Custom objects are typically less complex master data object with a small and simple data model. | EhP5 | MDG7.0 (Feature Pack) |
| This tutorial describes how to create an enrichment spot implementation with user interaction in Master Data Governance. The implementation is called when executing Checking for non-existent objects in the object list of a change requesta consistency check in the Single Processing UI (WebDynpro Application usmd_entity_value2). | EhP6 | MDG7.0 (Feature Pack) | |
| Enrichment of Master Data in MDG – Generic Guide and Sample Implementation | You can use the enrichment framework to enrich the MDG data with external services or with internal logic. The enrichment framework also supports embedding of specific UIs for enrichment. The first section of this guide provides a generic overview of how enrichment works. The second section provides an example of address validation. | MDG7.0 (Feature Pack) | MDG7.0 (Feature Pack) |
| Checking for non-existent objects in the object list of a change request | SAP Master Data Governance offers the feature to include the keys of objects that do not yet exist in the object list of a change request. Rather than waiting until all data is ready before specifying changes, you can work simultaneously on object creation and the processing of the change request. This document shows how to implement BAdIs that provide warnings and errors about non-existent objects | EhP6 | MDG7.0 (Feature Pack) |
| Value Mapping | |||
You want to maintain mass value mapping (customizing mapping) via file export/import. | EhP5 | MDG7.0 (Feature Pack) | |
| Data Replication | |||
You want to replicate data from your customer-specific data model to target systems (using flex option). | EhP5 | MDG7.0 (Feature Pack) |
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| A zip file containing a spreadsheet for the Financials data model. | MDG7.0 | MDG7.0 (Feature Pack) | |
| Updated May 2014 SAP How-To Guide for MDG-F - Overview | This guide provides you with foundation knowledge about financial data and its related governance solution financial governance (MDG-F). | MDG7.0 | MDG7.0 (Feature Pack) |
| New May 2014 Entity Derivation in MDG-F | Explains how to implement a custom cross-entity derivation for MDG-F entity types. It covers the key concepts and implementation details in general and includes a real-life example of the MDG-F data model 0G. | MDG7.0 (Feature Pack) | MDG7.0 (Feature Pack) |
| New May 2014 Enable Changeable IDs in MDG-F | Explains how to enable the new functionality of changeable IDs for MDG-F entities. It describes the key concepts and implementation details as well as possible enhancement options. | MDG7.0 (Feature Pack) | MDG7.0 (Feature Pack) |
| New May 2014 Enable multi-copy of Accounts in Company Code in MDG-F | Explains how to enable the new functionality for copying a single Account in Company Code to multiple target Accounts in Company Code. It describes the key concepts and implementation details as well as possible enhancement options. | MDG7.0 (Feature Pack) | MDG7.0 (Feature Pack) |
| New May 2014 Enable HANA Search in MDG-F | Explains how to enable the new functionality for HANA search. It describes the key concepts and implementation details as well as possible enhancement options. | MDG7.0 (Feature Pack) | MDG7.0 (Feature Pack) |
| New May 2014 Enable Primary Cost Elements for Accounts in MDG-F | Explains how to enable the new functionality for the one-step creation of Primary Cost Elements for Accounts. It describes the key concepts and implementation details as well as possible enhancement options. | MDG7.0 (Feature Pack) | MDG7.0 (Feature Pack) |
New May 2014 Enable Dynamic Parallel Approval for Company Code Data in Rule-based Workflow (Available since EhP5.) | Shows you how to create parallel approval workflow steps using a rule-based workflow when the parallel number is determined dynamically. | EhP5 | MDG7.0 (Feature Pack) |
Using the Master Data Management Generic Extractor (MDMGX) for Initial Load in MDG-F | Foundation knowledge to perform an initial load of master data into the financial governance (MDG-F) data model. | MDG7.0 | MDG7.0 (Feature Pack) |
Updated May 2014 | Foundation knowledge to extend the MDG-F data model by new fields. | MDG7.0 | MDG7.0 (Feature Pack) |
ALE Replication from MDG Hub to ERP Using the Same Client in MDG-F | Foundation knowledge for setting up an ALE scenario for the replication of MDG_F entities into the same physical client system. (MDG hub and ERP system share the same client.) | MDG7.0 | MDG7.0 (Feature Pack) |
| Enhancing the change request user interface in MDG-F | Example how to display an additional account form in the create change request application only when the A-segment account is processed in the change request. | EhP5 | MDG6.1 |
| Remote Where-Used List: Example Implementation | This guide demonstrates how to use the remote where-used-list in MDG. The standard delivery includes a generic user interface and an example Business Add-In (BAdI) implementation for the ACCOUNT entity type of the 0G data model. In this document, we use the default implementation as an example of all implementations. | EhP6 | MDG6.1 |
| In this article we look at two different approaches for extending the 0G data model of MDG-F. In the first section, we extend the 0G model directly. In the second section, we extend a copy of 0G. Finally, we compare the advantages and disadvantages of the two approaches. | EhP6 | MDG6.1 |
Title/Group | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
Extensibility | |||
| Best Practice for Maintenance Status | This guide provides background information about the maintenance statuses for the material master and the use of the maintenance statuses in MDG for Material. | all | all |
| Maintenance for Multiple Materials | The guide provides some insights on the applicability of the features to create or change multiple materials, also with respect of boundary conditions and limitations. | all | all |
| Set Up Parallel Change Requests for Material | Change Request in parallel for a single Business Object enables you to activate or reject a change request independently from the processing results of other change requests for the same business object. This guide gives some background information and explanation for setting up Parallel Change Requests for the Business Object Material. | MDG7.0 | MDG7.0 (Feature Pack) |
| Create new User Interfaces for Multiple-Record Processing | Multiple-Record Processing offers a streamlined process, with a UI that enables you to create change requests for multiple records with greater efficiency. This guide shows how to create new configurations for material. | MDG7.0 | MDG7.0 (Feature Pack) |
You use this guide to extend the MDG-M data model by a new entity type. The attribute values of the new entity type will be copied to the corresponding ERP tables (reuse option) after activation of the change request. | EhP6 | MDG7.0 (Feature Pack) | |
| Extend MDG-M Data Model by a New Entity Type (Standard-ERP Table, Reuse Option) | You can use this guide to extend the MDG-M data model by a new entity type. The attribute values of the new entity type are copied to the corresponding ERP tables (reuse option) after activation of the change request. For additional information about how to extend the UI, see : | EhP6 | MDG7.0 (Feature Pack) |
| You can use this guide to extend the MDG-M data model by a new field. The system copies attribute values of the new field to the corresponding ERP table (reuse option) after activation of the change request. | EhP6 | MDG7.0 (Feature Pack) | |
| This guide describes how to extend the preconfigured content of MDG-M with customer z-fields from the existing backend tables. | EhP6 | MDG7.0 (Feature Pack) | |
This guide describes how to extend the UI of Master Data Governance for Material to display additional data. | EhP6 | MDG7.0 (Feature Pack) | |
| Adjust MDG-M Homepage | This guide describes how to extend the Homepage of Master Data Governance for Material to display additional links | EhP6 | MDG7.0 (Feature Pack) |
| Create Custom Print Forms | This guide shows you how to create a custom print form to support different layouts and custom fields. | MDG7.0 | MDG7.0 (Feature Pack) |
| Extend Model with Complex Backend Data (e.g. MLAN) | This guide describes how to extend the preconfigured content of Master Data Governance for Material, contained in the data model MM, with Tax Data. | EhP5 | MDG7.0 (Feature Pack) |
| Central guide for SAP MDG-M extensibility | Includes topics such as field extensions, table extensions, UI adaptation, etc. | EhP5 | EhP5 |
This guide describes how to adapt the generic UI of Master Data Governance for Material in EhP5. | EhP5 | EhP5 | |
| File Up and Download | This How To Guide shows how the CSV file download and upload functionality can be used for MDG materials. | EhP5 | EhP5 |
Checks and Derivations | |||
This how-to guide gives an overview of the checks which are used in MDG-M and gives examples for checks and derivations built in BRF+. | EhP5 | MDG7.0 (Feature Pack) | |
Workflow | |||
| Enable Dynamic Parallel Approval for Company Code Data in Rule-based Workflow | This document shows you how to create parallel approval workflow steps using a rule-based workflow when the parallel number is determined dynamically. | MDG6.1 | MDG7.0 (Feature Pack) |
| Follow-up Work Item to Maintain Material Related Objects | This guide describes how to integrate follow-up work items for material related objects into the MDG Change Request process. | MDG6.1 | MDG7.0 (Feature Pack) |
| Rule Based Workflow with Partial Activation | When using the rule-based workflow, the process pattern '06 Activation (Bypass Snapshot)' means that the material is activated, even if the material record was changed in the backend system since the change request was created. Any backend changes are lost upon activation. You can adjust this behavior with SAP Note 1797009. | MDG6.1 | MDG7.0 (Feature Pack) |
BADI USMD_SSW_RULE_CONTEXT_PREPARE | EhP5 | MDG7.0 (Feature Pack) | |
| Rule Based Workflow: Enhancement for parallel workitems | BADI USMD_SSW_PARA_RESULT_HANDLER | EhP5 | MDG7.0 (Feature Pack) |
| Rule Based Workflow: Enhancement for Flexible User Determination | BADI USMD_SSW_DYNAMIC_AGENT_SELECT | EhP5 | MDG7.0 (Feature Pack) |
BADI USMD_SSW_SYSTEM_METHOD_CALLER | EhP5 | MDG7.0 (Feature Pack) | |
Sending an E-mail notification from the rules-based workflow | EhP5 | MDG7.0 (Feature Pack) | |
Setting up extended workflow notifications in order to send out e-mails when new workflow items are generated (also allows you to include a link to the workflow inbox in the generated e-mail). | EhP5 | MDG7.0 (Feature Pack) | |
| Performance | |||
| Performance Tweaks | Besides the official sizing guide for customer system landscapes, this guide focuses on the MDGM application and how it can be accelerated. The findings are based on the “Create Material” scenario but can also be applied to the “Change Material” scenario. | MDG6.1 | MDG7.0 (Feature Pack) |
| Performance Tweaks | Besides the official sizing guide for customer system landscapes, this guide focuses on the MDGM application and how it can be accelerated. The findings are based on the “Create Material” scenario but can also be applied to the “Change Material” scenario. | EhP6 | EhP6 |
Data Models | |||
| Data Model Metadata | A zip file containing a spreadsheet for the Material data model. This spreadsheet contains information about the data model, the MaterialERPBulkReplicateRequest and related backend data. | EhP5 | MDG7.0 (Feature Pack) |
| Search | |||
| Enhance the Material Search (EhP5) | Adding extra fields to the search template | EhP5 | EhP5 |
| Replace Enterprise Search by DB or alternative search provider | For the standard delivery scope, MDG-M requires a fully configured Enterprise Search (ES). To mitigate this dependency, this guide describes how to adapt MDG-M so that another search provider can be used. The example focuses on integrating a Database base search (DB search), but other search providers can be supported in a similar way. | MDG6.1 | MDG7.0 (Feature Pack) |
| Enhance the Material Search (EhP6 on) | With MDG for Material master data it is possible to extend the data model MM. If you want to search also with these new fields you have to extend the search too. | EhP6 | MDG7.0 (Feature Pack) |
| Data Import/Data Replication | |||
| Using Data Import Framework (DIF) | You can use the Import Master Data service to import files containing material and classification data to the MDG system. This guide provides background information about the Data Import Framework (DIF) and describes how to use the DIF to upload material data from a CSV file using a BAdI for the file conversion. | EhP6 | MDG7.0 (Feature Pack) |
| Using Data Replication Framework (DRF) | This guide provides background information about the Data Replication Framework (DRF). The guide also describes how to set up the system to enable immediate distribution of changes in the material master during activation of the material (SAP Note 1764329). | EhP6 | MDG7.0 (Feature Pack) |
| Using Enterprise Material Services (SOA) | This guide explains how to enhance the asynchronous SAP Material Enterprise Services MaterialERPBulkReplicateRequest_In | MDG6.1 | MDG7.0 (Feature Pack) |
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| New January 2015Copying of Business Partners (SAP Note 2020896) | Refer to the SAP Note linked to here. A how to guide for using the BEC cloner is attached to the Note. Make sure you read the disclaimer in the attached document. | MDG 7.0 SP3 | MDG 7.0 |
| Extending SAP Master Data Governance for Supplier - Part 1 | Data Model Extensions | EhP5 | EhP5 |
| Extending SAP Master Data Governance for Supplier - Part 2 | User Interface Extension | EhP5 | EhP5 |
| SAP How-To Guide: Extend the MDG Business Partner - Overview | This guide provides you with the foundation knowledge you need to extend business partner data and its related governance solutions: customer governance (MDG-C) and supplier governance (MDG-S). | EhP6 | MDG7.0 (Feature Pack) |
| You can use this guide to extend the MDG Business Partner (including MDG-C and MDG-S) by creating and registering a custom handler class. | EhP6 | MDG7.0 (Feature Pack) | |
| SAP How-To Guide: Extend the MDG Business Partner - Create or Redefine a UI Feeder Class | You can use this guide to extend the MDG Business Partner by creating or redefining a feeder class for the user interface. | EhP6 | MDG7.0 (Feature Pack) |
| SAP How-To Guide: Extend MDG-S Data Model by a new Entity Type (Flex Option) | You can use this guide to extend the MDG-S /MDG-C data model by a new entity type. The attributes of the new entity type only exist in the MDG context and not in the ERP data models (flex option). | EhP6 | MDG7.0 (Feature Pack) |
| SAP How-To Guide: Extend MDG-S Data Model by a New Field (Reuse Option) | You can use this guide to extend the MDG-S data model or the MDG-C data model by adding attributes that already exist as database fields in the appropriate customer include of the SAP Business Partner / Vendor / Customer (MDG reuse option). | EhP6 | MDG7.0 (Feature Pack) |
| SAP How-To Guide: Extend the MDG Business Partner – Node Extension (Reuse Option) | You can use this guide to extend the data model for supplier governance (MDG-S) or for customer governance (MDG-S) by creating a new node, using the reuse entity type. | EhP6 | MDG7.0 (Feature Pack) |
| SAP How-To Guide: Extend the MDG BP – Ensure Auto-creation of ERP Vendors with MDG-S | You can use this guide to extend supplier governance (MDG-S) by ensuring that every time a user creates a supplier using the main user interface for supplier governance, the solution always creates an ERP vendor record. | EhP6 | MDG7.0 (Feature Pack) |
You can use this guide to extend the customer governance and supplier governance so that MDG users who are only interested in the environment of their local business system only get to see entries for this local business system (such as company codes and payment terms). | EhP6 | MDG7.0 (Feature Pack) | |
| Installing, Configuring, and Using the Excel Upload for Business Partner | You can upload business Partner data in batch to MDG-S from a .csv file. This document provides the installation and configuration instructions, a link to the relevant source code and excel file, and instructions on how to use the excel upload. | EhP6 | MDG7.0 (Feature Pack) |
| Archived Guides | |||
| SAP How-To Guide: Extend MDG-S / MDG-C Data Model by a New Field (Reuse Option) | You can use this guide to extend the MDG-S data model or the MDG-C data model by adding attributes that already exist as database fields in the appropriate customer include of the SAP Business Partner / Vendor / Customer (MDG reuse option). | EhP6 | |
| SAP How-To Guide: Extend MDG-S / MDG-C Data Model by a New Entity Type (Flex Option) | You can use this guide to extend the MDG-S /MDG-C data model by a new Entity Type. The attributes of the new entity only exist in the MDG context and not in the ERP data models (flex option). Note: This is not the right guide for you if you need an extension where the data is stored in tables outside of MDG (i.e. Partner Functions). | EhP6 | |
| Data Models | |||
A zip file containing separate spreadsheets for Business Partner, Supplier, and Customer. Each spreadsheet contains information about the following:
| EhP6 | MDG7.0 (Feature Pack) |
Title | Description and Documents | Valid-From | Valid-To |
|---|---|---|---|
| New December 2013Using Enhanced Integration of CRM with MDG for Customers (MDG-C) in a CRM/ERP Data Exchange | This guide describes how to use enhanced integration of CRM with MDG for Customers in a CRM / ERP Data Exchange Scenario. | EhP6 | MDG7.0 (Feature Pack) |
| A cross-system master data process for supplier | Implementation details for a simplified cross system Supplier On-boarding scenario leveraging SAP's Enterprise Master Data Management portfolio consisting of SAP NetWeaver Master Data and SAP Master Data Governance. The overarching process is modeled using SAP NetWeaver Business Process Management. | EhP5 | MDG7.0 (Feature Pack) |
| Customizing Integration Between MDG and ERP | The intention of this document is to support SAP MDG implementation projects with general guidelines, templates and links to documentation that can be a basis for the synchronization process – including lists of customizing objects that might be affected. | EhP6 | MDG7.0 (Feature Pack) |
Hi all,
I have the following problem:
So we have a difference between the WIP calculation and WIP release.
I was not able to identify the reason for this difference. Do you have any idea, where did the difference come from?
I would be delighted for any hint.
p.s. What I have checked so far:
Dear all,
I'm using ALE to transfer MM from SAP system to another SAP system.
I made a conversion rule (BD79) but I have an issue with the field MATNR and the leading zeros.
Example:
Sender system : MATNR = 123456789
Receiver system : MATNR = 000000000123456789
I know that I have to use the CONVERSION_EXIT_ALPHA_OUTPUT ; but I do not know where use it ? in BD79 ?
Could you kindly help me.
In advance many thanks.
Virginie. Frigo
Hi All,
I have a requirment like
my source have 2 fields
field1 having data 1cc2cc3cc4cc5cc
feild2 having data accbccdddcceccfffffcc
in need output like 1cc2cc333cc4cc55555cc please help me to get this type of output.
Note cc means context change, we need to reah values of contexts with source and generate like that.
Thanks,
Venu.
Hi,
I want user's ideal session to be turned off (logged off) after certain duration. I don't want to use inbuilt functionality of just screen locking.
Can I do this using SDK? If yes then please let me know how?
I am new for SDK so kindly mention it in layman language.
Hi there,
I think I know the answer to this already, but here goes...
I need to use a tuple expression in a *REC statement (in place of the old-fashioned GET) but I want it to be dynamic, so at least one of the tuple members changes at runtime.
To use the basic example from SAP Help, but amended slightly, let's say this is the standard expression:
*XDIM_MEMBERSET P_ACCT = CE0004010,CE0652000
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=%VALUE%/([P_ACCT].[CE0652000],[P_ACTIVITY].[LABPRD],[P_ENTITY].[E123]), P_ACCT="CE0661000")
*ENDWHENBut what if the P_ENTITY member should be dynamic, depending on the ENTITY member the user selects in the DM package? What I WANT to do is something like this:
*XDIM_MEMBERSET P_ACCT = CE0004010,CE0652000
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=%VALUE%/([P_ACCT].[CE0652000],[P_ACTIVITY].[LABPRD],[P_ENTITY].[%ENTITY_SET%]), P_ACCT="CE0661000")
*ENDWHEN
...but it doesn't work. Is this even possible? And if so, what am I doing wrong?
Thanks very much,
Jason
PS. I'm already using a lookup to pull out a tax% in the same script, so I can't use it for this as well...
Hi Everyboby,
I have a small requirement. i created a universe level filter for date (from date & to date) what ever the values am passing from universe to webi report in the webi report level. i need to show that particular values in the report header.
i think i need to (IsPromptAnswered).
please give me the syntax.
Thanks n Regards,
Stefen.
Hello,
We are getting a field missing in a record in PSA for the datasource 0HR_OTYPEOBJECT_TEXT because of which PSA is in red state. This record came today with a missing field. Should I ask for a functional to check it first ? How can I check the base tables on which this is created ?
Thanks
MV
Has anyone had any problems when using the RFC Accessor Lookup Service in a load balancing environment?
When I run the below code in our single server development and quality assurance environments it works fine, however when I run it in our staging environment, which has load balancing configured, it fails if both of the servers are on but if only one of the servers are on it works fine.
InputParameters inputParameters = container.getInputParameters();
Channel channel = inputParameters.getChannel(rfcChannelName);
RfcAccessor rfcAccessor = LookupService.getRfcAccessor(channel);
XmlPayload request = getXmlPayloadRequest();
XmlPayload response = rfcAccessor.call(request);
The error that we receive if both servers are on is:
Technical error when calling an adapter remotely. The HMI method with the ID process was called with an incorrect session status. The system accessor object is missing
Any ideas as to where I should start looking? We are running PI 7.11 and the code is called in the init method of the message mapping.
Thanks in advance,
Jon
I've recently come across articles from 2009 through 2011 that discuss a phasing out of BEx (Query Designer, Report Designer, etc.) by 2016. Is this still in the cards for SAP or do they now plan on support BEx for the foreseeable future?