SAP - Master Data Management
MDM History
MDM Overview
Console
• Console Introduction
• Repository Structures
• Taxonomy/Lookup/Hierarchy
• Qualifier/ Relationship
• Multilingual Support
Data Manager
• Data Manager Introduction
• MDM Modes
• Record Mode
• Hierarchy Mode
• Taxonomy Mode
• Matching Mode
• Workflow
• Browser embedded
Import Manager
• Import Manager Overview
• Configure Import Manager
• Import Map file
• Pre-requisites for Data Import
• Monitoring Import Status
• Performing Data Import
• Transformations
• Table joins and Lookup
• Splitting fields
• Partitioning
• Pivot and Reverse Pivot
Syndicator
• Syndicator Overview
• Maps and Map properties
• Item Mapping
• Destination Items
• Custom Item
• Syndicating Records
Master Data Harmonization
Rich Product Content Management RPCM (Overview)
Global Data Synchronization (Overview)
Integration scenario with XI
Security and User Management
Performance
For further details and demo , you can reach us at
Sree
sapmdm.co.in@gmail.com
Mobile: 9620852299
Showing posts with label sap mdm training. Show all posts
Showing posts with label sap mdm training. Show all posts
Monday, December 27, 2010
Tuesday, June 15, 2010
SAP ONLINE TRAINING FOR MDM, BI, XI/PI, EP, ABAP,WORKFLOW, HR,abap,workflow, webdynpro,BASIS, RUNSAP,BIW,PS,CS,SOLUTION MANAGER, ABAP-HR,NETWEAVER,TU
Dear Techies,
We offer the following Training Courses :
SAP MDM, EP, BW/BI 7.0, FI/CO, HR , ABAP , BASIS & SECURITY,
SD ,CRM , MM ,PP, HR, ABAP-HR , PI/XI TRAINING,QA TRAINING
TRAINING HIGHLIGHTS :
• Highly Qualified Instructors in IT industry
• Limited enrollment.
ONLINE Training (Using Desktop Sharing Method)
one-to-one training, highly interactive
• You can get trained from where you are.
• Remote training from our experienced trainers
• Weekdays and weekend batches available.
• FREE DEMO available for interested students.
For further details please reach us at
Sree
info@sapmdm.co.in
www.sapmdm.co.in
We offer the following Training Courses :
SAP MDM, EP, BW/BI 7.0, FI/CO, HR , ABAP , BASIS & SECURITY,
SD ,CRM , MM ,PP, HR, ABAP-HR , PI/XI TRAINING,QA TRAINING
TRAINING HIGHLIGHTS :
• Highly Qualified Instructors in IT industry
• Limited enrollment.
ONLINE Training (Using Desktop Sharing Method)
one-to-one training, highly interactive
• You can get trained from where you are.
• Remote training from our experienced trainers
• Weekdays and weekend batches available.
• FREE DEMO available for interested students.
For further details please reach us at
Sree
info@sapmdm.co.in
www.sapmdm.co.in
Wednesday, July 1, 2009
SAP MDM ONLINE TRAINING
Hi,
We offer the following Online Training Courses :
SAP MDM,
EP,BW / BI 7.0,FI/CO, HR , ABAP , BASIS & SECURITY, SD / CRM , MM / PP, HR, ABAP-HR , PI/XI TRAINING,QA TRAINING
For further details please reach us at
Sree
+91-9949512008
www.sapmdm.co.in
We offer the following Online Training Courses :
SAP MDM,
EP,BW / BI 7.0,FI/CO, HR , ABAP , BASIS & SECURITY, SD / CRM , MM / PP, HR, ABAP-HR , PI/XI TRAINING,QA TRAINING
For further details please reach us at
Sree
+91-9949512008
www.sapmdm.co.in
Friday, February 27, 2009
Controlled\Restricted Access to Data in MDM sai charan singh
Controlled\Restricted Access to Data in MDM
sai charan singh
MDM provides security through Users, Roles and Privileges.
Each user has his own user access, with his own user name and password.
Each roles defines the permitted area and restricted section in the repository.
Privileges are to defined on tables, fields and functions as executable, read-only or read/write.
User:
When you create a new user you have to give a user name, password and assign role to the user, by default a 'Default' role is assigned, when you assign any other role then default role is replaced. When you create a repository by default an Admin user, with blank password is created, which you use to log into the repository. You can set a custom password for Admin but you cannot delete user Admin.
image
Roles:
When you create a new role you have to give a name to that role and assign different users to this role, by default all functions are enabled for execute and tables/fields are enabled to read/write. When you create a repository by default two roles are created, First role being Admin, with all functions enables to execute and tables/fields enabled to read/write and this roles cannot be edited, the second role created is Default, which also has all functions enabled to execute and tables/fields enabled to read/write but this role can be edited and changes can be made to functions and tables/fields, remember this role is the one assigned when you create a new user. Both the roles cannot be deleted.
image
Privileges:
Creating users and roles might be childs game, but when it comes to setting the right privileges then its MEN AT WORK, its very important to assign the right functionality to each role.
The second tab while creating roles, there are the list of functions provided, differentiate each role, understand why this role is required, for example, you want the user assigned to this role only to read and write data, then dont grant him permission to delete records, go through each and every function and set the right access, if you change the first row, functions[default] then by default all rows are effected.
The third tab while creating roles, has different tables and when you expand those you will find different fields. Hear you can set access at table level or for individual field. Tables n fields can be set with read-only or read/write access.
image
Constraints:
Once of the most important part actually for which I started this blog is this, constraints, you can find a constraint column as the last column in tables/fields tab while creating a role. Generally you dont want to give access to a role for complete table, you want to filter a group of records and then give access to them, then you should create a Mask or Named search and then select read-only access for all rows and only for the required Mask or Named search select read/write or select a constraint on a lookup table.
image
1. By default for all constraints, 'ALL' option is selected. By selecting the drop down list you can select you own options, its an multi-valued field.
2. Previous only Masks and Look up tables were allowed to be constrained, but now from SP6 even Named searches can be constrained.
3. When it comes to look up tables only non-Multi-valued fields with respect to main table are allowed, that means qualified tables and multi-valued lookup fields in Main table are not available for Constraints.
4. When you select a lookup tables value as an constraint, automatically both Main table and the lookup table gets short listed(Both the tables have records with respect to that constraint).
sai charan singh
MDM provides security through Users, Roles and Privileges.
Each user has his own user access, with his own user name and password.
Each roles defines the permitted area and restricted section in the repository.
Privileges are to defined on tables, fields and functions as executable, read-only or read/write.
User:
When you create a new user you have to give a user name, password and assign role to the user, by default a 'Default' role is assigned, when you assign any other role then default role is replaced. When you create a repository by default an Admin user, with blank password is created, which you use to log into the repository. You can set a custom password for Admin but you cannot delete user Admin.
image
Roles:
When you create a new role you have to give a name to that role and assign different users to this role, by default all functions are enabled for execute and tables/fields are enabled to read/write. When you create a repository by default two roles are created, First role being Admin, with all functions enables to execute and tables/fields enabled to read/write and this roles cannot be edited, the second role created is Default, which also has all functions enabled to execute and tables/fields enabled to read/write but this role can be edited and changes can be made to functions and tables/fields, remember this role is the one assigned when you create a new user. Both the roles cannot be deleted.
image
Privileges:
Creating users and roles might be childs game, but when it comes to setting the right privileges then its MEN AT WORK, its very important to assign the right functionality to each role.
The second tab while creating roles, there are the list of functions provided, differentiate each role, understand why this role is required, for example, you want the user assigned to this role only to read and write data, then dont grant him permission to delete records, go through each and every function and set the right access, if you change the first row, functions[default] then by default all rows are effected.
The third tab while creating roles, has different tables and when you expand those you will find different fields. Hear you can set access at table level or for individual field. Tables n fields can be set with read-only or read/write access.
image
Constraints:
Once of the most important part actually for which I started this blog is this, constraints, you can find a constraint column as the last column in tables/fields tab while creating a role. Generally you dont want to give access to a role for complete table, you want to filter a group of records and then give access to them, then you should create a Mask or Named search and then select read-only access for all rows and only for the required Mask or Named search select read/write or select a constraint on a lookup table.
image
1. By default for all constraints, 'ALL' option is selected. By selecting the drop down list you can select you own options, its an multi-valued field.
2. Previous only Masks and Look up tables were allowed to be constrained, but now from SP6 even Named searches can be constrained.
3. When it comes to look up tables only non-Multi-valued fields with respect to main table are allowed, that means qualified tables and multi-valued lookup fields in Main table are not available for Constraints.
4. When you select a lookup tables value as an constraint, automatically both Main table and the lookup table gets short listed(Both the tables have records with respect to that constraint).
Saturday, January 31, 2009
Product configuration with the SAP SRM-MDM-Catalog 2.0 Daniel Busse
Product configuration with the SAP SRM-MDM-Catalog 2.0
Daniel Busse
Introduction:
The procurement of MRO goods in the company is increasingly electronically. Many companies put e-procurement systems to automate the procurement process and save costs. SAP AG offers with the SRM-MDM catalogueue a solution, based on the SAP NetWeaver MDM-based and using OCI with the SAP SRM. The proposed application is one of the possibilities which potentially could offer configuration options.
The Problems:
When searching for the products, the user can search among different (depending on the setting) choose. Then he receives a list of results to those from matching catalogue products to select and order. No additional information about the product, such as business card information’s can be added.
In the standard SRM-MDM catalogue, the user can select only the products which are store physically in the catalogue.
The proposed application provides the user the option to stored variants to configure and enrich a product with additional information about itself.
The Solution:
The order process without configuration looks like that :
image
Just add a single step to the standard process :
image
The product configuration is realized by a Java Web Dynpro application. When you click on the product, attributes in a selection screen stored in the MDM repository for this product appear. The information such as name and attribute values are defined in the Taxonomy and associated to the products. It can have information such as labelling of working clothes. This configuration and additional details will be concatenated and shown in a custom box. They will be transfer via OCI to the SRM module.
image
In the shopping basket the product configuration is shown in a separated field.
image
The application allows, presented in a user-friendly form, the configuration of products. Information not included in the MDM repository can be stored while order process is running. The total order includes the product, its configuration and any additional information which was entered.
Thanks to Nico Razlow who created this application and helped me to write this blog.
Daniel Busse Daniel Busse was born in 1981 in Mühlhausen/Germany. After high school graduation, he completed military service and studied business information at the Stuttgart Media University. Now he works for IBSolution GmbH, the innovative SAP NetWeaver consulting company. He is member of the R&D department at the IBSolution Labs in Heilbronn, Germany and finished his diploma thesis about catalog data management with SRM-MDM-CATALOG tool. His fields of activity are SRM-MDM-CATALOG, SAP Netweaver Visual Composer and Guided Procedures.
Daniel Busse
Introduction:
The procurement of MRO goods in the company is increasingly electronically. Many companies put e-procurement systems to automate the procurement process and save costs. SAP AG offers with the SRM-MDM catalogueue a solution, based on the SAP NetWeaver MDM-based and using OCI with the SAP SRM. The proposed application is one of the possibilities which potentially could offer configuration options.
The Problems:
When searching for the products, the user can search among different (depending on the setting) choose. Then he receives a list of results to those from matching catalogue products to select and order. No additional information about the product, such as business card information’s can be added.
In the standard SRM-MDM catalogue, the user can select only the products which are store physically in the catalogue.
The proposed application provides the user the option to stored variants to configure and enrich a product with additional information about itself.
The Solution:
The order process without configuration looks like that :
image
Just add a single step to the standard process :
image
The product configuration is realized by a Java Web Dynpro application. When you click on the product, attributes in a selection screen stored in the MDM repository for this product appear. The information such as name and attribute values are defined in the Taxonomy and associated to the products. It can have information such as labelling of working clothes. This configuration and additional details will be concatenated and shown in a custom box. They will be transfer via OCI to the SRM module.
image
In the shopping basket the product configuration is shown in a separated field.
image
The application allows, presented in a user-friendly form, the configuration of products. Information not included in the MDM repository can be stored while order process is running. The total order includes the product, its configuration and any additional information which was entered.
Thanks to Nico Razlow who created this application and helped me to write this blog.
Daniel Busse Daniel Busse was born in 1981 in Mühlhausen/Germany. After high school graduation, he completed military service and studied business information at the Stuttgart Media University. Now he works for IBSolution GmbH, the innovative SAP NetWeaver consulting company. He is member of the R&D department at the IBSolution Labs in Heilbronn, Germany and finished his diploma thesis about catalog data management with SRM-MDM-CATALOG tool. His fields of activity are SRM-MDM-CATALOG, SAP Netweaver Visual Composer and Guided Procedures.
Friday, January 23, 2009
Root Cause Analysis for SAP MDM 5.5 SP06 with SAP Solution Manager Diagnostics Detlef Thoms SAP Employee
For today's complex IT solutions, analyzing the root cause of an incident requires a systematic top down approach to finally pinpoint to the root cause of an incident. SAP MDM 5.5 SP06 Patch1 or higher can be integrated into the Root Cause Analysis scenario in SAP Solution Manager as of Solution Manager 4.0 SP15. Solution Manager Diagnostics provides two applications to perform workload analysis:
The E2E Workload Analysis application provides hourly aggregated performance and resource consumption data. It allows comparing performance data of multiple systems and has a very flexible data display. It provides solution wide performance data and allows isolating a system or software component that caused performance problems. The E2E Workload Analysis is the starting point for Root Cause Analysis of performance problems.
Wily Introscope provides non-aggregated performance and resource data for MDM and Java Systems. It can be used to perform detailed analysis of the MDM or Java System once the E2E Workload Analysis isolates a system or software component that caused performance problems. The Introscope Enterprise Manager is part of the CA Wily Introscope system management application. It is installed as part of SAP Solution Manager.
Since the new capabilities have been recently released I would like to point you to some resources that demonstrate how to perform Root Cause Analysis for SAP MDM using SAP Solution Manager.
The first one is a setup guide: "How To...setup SMD for MDM Root Cause Analysis - MDM 5.5 SP06"
http://service.sap.com/installMDM > Operations > MDM 5.5 - Monitoring Guides (ZIP File)
A second guide describes how to perform a root cause analysis:
"How to Perform Root Cause Analysis for Master Data Management with Solution Manager Diagnostics"
In addition a further SDN article and a presentation give an overview of the new capabilities:
„Root cause Analysis with Solution Manager Diagnostics for MDM"
„Monitoring Capabilities and Root Cause Analysis for SAP MDM"
A Know How Network Call (KHNC) will be given on April 30th. The presentation will be recorded and can then be found here.
SAP NetWeaver RIG is also planning a feedback project on the usage of Solution Manager Diagnostics for MDM - purpose of this is to gather customer feedback about the new functionalities for Root Cause Analysis and Monitoring. If you are right now working or will work with the new capabilities, please let me (detlef.thoms@sap.com) know. We have prepared a brief questionnaire to roll-in your feedback and requirements into the next version!
Detlef Thoms is a RIG Expert for SAP MDM and a member of the SAP NetWeaver Regional Implementation Group(RIG).
The E2E Workload Analysis application provides hourly aggregated performance and resource consumption data. It allows comparing performance data of multiple systems and has a very flexible data display. It provides solution wide performance data and allows isolating a system or software component that caused performance problems. The E2E Workload Analysis is the starting point for Root Cause Analysis of performance problems.
Wily Introscope provides non-aggregated performance and resource data for MDM and Java Systems. It can be used to perform detailed analysis of the MDM or Java System once the E2E Workload Analysis isolates a system or software component that caused performance problems. The Introscope Enterprise Manager is part of the CA Wily Introscope system management application. It is installed as part of SAP Solution Manager.
Since the new capabilities have been recently released I would like to point you to some resources that demonstrate how to perform Root Cause Analysis for SAP MDM using SAP Solution Manager.
The first one is a setup guide: "How To...setup SMD for MDM Root Cause Analysis - MDM 5.5 SP06"
http://service.sap.com/installMDM > Operations > MDM 5.5 - Monitoring Guides (ZIP File)
A second guide describes how to perform a root cause analysis:
"How to Perform Root Cause Analysis for Master Data Management with Solution Manager Diagnostics"
In addition a further SDN article and a presentation give an overview of the new capabilities:
„Root cause Analysis with Solution Manager Diagnostics for MDM"
„Monitoring Capabilities and Root Cause Analysis for SAP MDM"
A Know How Network Call (KHNC) will be given on April 30th. The presentation will be recorded and can then be found here.
SAP NetWeaver RIG is also planning a feedback project on the usage of Solution Manager Diagnostics for MDM - purpose of this is to gather customer feedback about the new functionalities for Root Cause Analysis and Monitoring. If you are right now working or will work with the new capabilities, please let me (detlef.thoms@sap.com) know. We have prepared a brief questionnaire to roll-in your feedback and requirements into the next version!
Detlef Thoms is a RIG Expert for SAP MDM and a member of the SAP NetWeaver Regional Implementation Group(RIG).
SAP MDM integration with R/3 system by Ravi Kumar
We all know what are the different It scenarios supported by MDM, namely:
Master Data Consolidation
*
– Cleansing and de-duplication
*
–Data normalization including categorization and taxonomy management
*
–New interactive consolidation capabilities
•Master Data Harmonization
*
–Automated synchronization of globally relevant master data information
*
–New interactive distribution capabilities
•Central Master Data Management
*
–One-stop data maintenance
*
–Ongoing master data quality
In this Blog I will try to cover the different steps required for integrating MDM with R/3 system which is the source of Master data.After cleansing and de-duplication of Data in MDM all changes/ updates will be reflecting back in SAP R/3. this step by step procedure should help in understanding the procedure for implementing MDM IT scenarios. :)
Different settings required for doing this are:
* Settings in R3
* Settings in XI
* Settings in MDM
* MDM console
* Import Manager
* Syndication Manager
MDM Process flow
Process Flow: Trigger Idoc containing Masters from R/3.XI converts these Idocs to XML files and places in ready folder for Inbound port. Files received by Import Manager into MDM and after changes etal via Syndicator Manager xml file placed in Ready folder of outbound Port from where it will be picked by XI and sent to R/3 using the Idocs.
Setting in R/3:
Step 1
T.Code: SALE
Define Logical System
Sender Logical System:
Receiver Logical System:
Step 2: T.code: SALE
Assign Client to Sender Logical System:
Step 3:
Create RFC destination of type ‘3' for SAP XI system using transaction - SM59
Step 4:
Create a Distribution model through T.Code: SALE/BD64
Here we need to mention Sender Client (DEVCLNT500) and Receiver Client (XICLNT100) and Message type (MATMAS)
Step 5:
Using T.Code: WE21
Maintain Ports for IDoc Processing
Step: 6
Maintain Partner Profile using the T.code: WE20
Step 7:
Using BD12/BD10 T.code to Send Customer IDoc or material IDoc
Using T.code WE02 we can confirm or see the message transformations.
Now we are able to generate IDoc from R/3 containing the master data.
Settings in MDM:
Select the repository for which you want to do the settings.
Go to "Admin" and select "Client Systems" and right click on it and create your client system
Then go to "Ports" for creating a Port for Client System
Here you are defining the Outbound Port for the Client system (MDC R/3) defined in previous step.
You have an option of processing the data Automatically/manually.
After Saving the "Port" and "Client System" you need to ensure the folders in respective repository has been created in server.
Because "Ready" is the folder where all the files get exchange from.
Similar steps should be repeated for Inbound Port.
MDM Import Manager: Assuming that all the settings are done in XI also we move to Import manager where we will select the file to be imported and steps to be followed for import of Data into MDM
Step 1: Login to Import Manager and connect to Source file. Select type as PORT. System automatically connects to the Inbound Port of the repository logged into.
Step 2: Do all Field mapping and value mapping in Map Field/Value tab.we can use the standard maps provided in Business content or do all mappings manually and save the map.
Step 3: Go to match records Tab select the Field used for Matching records and select the import action. PS : For each record we can manually override create/skip as import action.
Step 4: After all mappings has been done and import action is Ready to Import in Import status tab execute the import
This will import the records contained in the xml file from the Ready folder into MDM.GO to Data manager and check all records created from R3.
Syndicator Manager MDM:
Any changes made in MDM data manager based upon the validations/Assignemnts and Business rules the changed record should be syndicated back to R3 which is Data source.
Step 1: Login to Syndicator Manager giving the repository name. select File> Destination Properties and select Port as shown:
Select the remote system R3 in this case
Select the Port which we have created for Outbound port where the Syndicated file can be placed in XML format.
Step 2: Do all the mappings again. Use the standard maps provided in Business content or do it manually like in Import manager. We have the options of selecting few records based on search parameters. We also have the option of Supressing all unchanged records in map Properties. This will select only those records which has been changed in Data manager instead of all existing records.
Step 3: In Destination Preview we can actually see all records with the values for fields before syndicating. This should be always done before executing to reduce the erroneous /incomplete data flow. Once you have all the details execute the syndication.
Step 4: Check the IDoc list in SAP. In case of status 51 do the further analysis why it has failed.
RESULT: data changed in MDM Data manager will be updated in SAP R3 system provided all the mappings are correct.
Ravi Kumar is Consultant with Infosys.
Master Data Consolidation
*
– Cleansing and de-duplication
*
–Data normalization including categorization and taxonomy management
*
–New interactive consolidation capabilities
•Master Data Harmonization
*
–Automated synchronization of globally relevant master data information
*
–New interactive distribution capabilities
•Central Master Data Management
*
–One-stop data maintenance
*
–Ongoing master data quality
In this Blog I will try to cover the different steps required for integrating MDM with R/3 system which is the source of Master data.After cleansing and de-duplication of Data in MDM all changes/ updates will be reflecting back in SAP R/3. this step by step procedure should help in understanding the procedure for implementing MDM IT scenarios. :)
Different settings required for doing this are:
* Settings in R3
* Settings in XI
* Settings in MDM
* MDM console
* Import Manager
* Syndication Manager
MDM Process flow
Process Flow: Trigger Idoc containing Masters from R/3.XI converts these Idocs to XML files and places in ready folder for Inbound port. Files received by Import Manager into MDM and after changes etal via Syndicator Manager xml file placed in Ready folder of outbound Port from where it will be picked by XI and sent to R/3 using the Idocs.
Setting in R/3:
Step 1
T.Code: SALE
Define Logical System
Sender Logical System:
Receiver Logical System:
Step 2: T.code: SALE
Assign Client to Sender Logical System:
Step 3:
Create RFC destination of type ‘3' for SAP XI system using transaction - SM59
Step 4:
Create a Distribution model through T.Code: SALE/BD64
Here we need to mention Sender Client (DEVCLNT500) and Receiver Client (XICLNT100) and Message type (MATMAS)
Step 5:
Using T.Code: WE21
Maintain Ports for IDoc Processing
Step: 6
Maintain Partner Profile using the T.code: WE20
Step 7:
Using BD12/BD10 T.code to Send Customer IDoc or material IDoc
Using T.code WE02 we can confirm or see the message transformations.
Now we are able to generate IDoc from R/3 containing the master data.
Settings in MDM:
Select the repository for which you want to do the settings.
Go to "Admin" and select "Client Systems" and right click on it and create your client system
Then go to "Ports" for creating a Port for Client System
Here you are defining the Outbound Port for the Client system (MDC R/3) defined in previous step.
You have an option of processing the data Automatically/manually.
After Saving the "Port" and "Client System" you need to ensure the folders in respective repository has been created in server.
Because "Ready" is the folder where all the files get exchange from.
Similar steps should be repeated for Inbound Port.
MDM Import Manager: Assuming that all the settings are done in XI also we move to Import manager where we will select the file to be imported and steps to be followed for import of Data into MDM
Step 1: Login to Import Manager and connect to Source file. Select type as PORT. System automatically connects to the Inbound Port of the repository logged into.
Step 2: Do all Field mapping and value mapping in Map Field/Value tab.we can use the standard maps provided in Business content or do all mappings manually and save the map.
Step 3: Go to match records Tab select the Field used for Matching records and select the import action. PS : For each record we can manually override create/skip as import action.
Step 4: After all mappings has been done and import action is Ready to Import in Import status tab execute the import
This will import the records contained in the xml file from the Ready folder into MDM.GO to Data manager and check all records created from R3.
Syndicator Manager MDM:
Any changes made in MDM data manager based upon the validations/Assignemnts and Business rules the changed record should be syndicated back to R3 which is Data source.
Step 1: Login to Syndicator Manager giving the repository name. select File> Destination Properties and select Port as shown:
Select the remote system R3 in this case
Select the Port which we have created for Outbound port where the Syndicated file can be placed in XML format.
Step 2: Do all the mappings again. Use the standard maps provided in Business content or do it manually like in Import manager. We have the options of selecting few records based on search parameters. We also have the option of Supressing all unchanged records in map Properties. This will select only those records which has been changed in Data manager instead of all existing records.
Step 3: In Destination Preview we can actually see all records with the values for fields before syndicating. This should be always done before executing to reduce the erroneous /incomplete data flow. Once you have all the details execute the syndication.
Step 4: Check the IDoc list in SAP. In case of status 51 do the further analysis why it has failed.
RESULT: data changed in MDM Data manager will be updated in SAP R3 system provided all the mappings are correct.
Ravi Kumar is Consultant with Infosys.
Subscribe to:
Posts (Atom)
Latest updates from sdn.sap.com
SAP Developer Network Latest Updates
Posts
