SAP MDM-XI-R/3 Scenario

Hi,
I'm working on MDM-XI-R/3 integration. The integration between R/3 and MDM has been done.
First XI posts Idoc ADRMAS and then posts Idoc DEBMAS.
We tried sending the data thrice. the first two times ADRMAS was getting posted to the application successfully and DEBMAS was under status 30. It still is under processing.
The third time when i sent it, ADRMAS gave me an error status 51 saying the function module(not sure of the name) is not allowed. the status of the DEBMAS is the same.
Any ideas what is the problem?
It will be highly appreciated if anyone of you come up with solutions.
Points will be rewarded surely.

Hi,
I guess the Inbound process code must be having different function module.
The combinations are as follows.
DEB2 for DEBMAS (module IDOC_INPUT_DEBITOR_MDM)
CRE2 for CREMAS (module IDOC_INPUT_CREDITOR_MDM)
BAPI_MDM for ADRMAS, ADR2MAS and ADR3MAS (module BAPI_IDOC_INPUT_MDM)
MAT2 for MATMAS (module IDOC_INPUT_MATMAS_MDM)
So check in your case is the process code is BAPI_MDM and function module is BAPI_IDOC_INPUT_MDM. You can also see the attached FM for a process code in tcode WE42.
Regards,
Mandar

Similar Messages

Scenarios bundle and sample excel files for customer for SAP MDM

Hi:
In SAP MDM we have the business content which has the archive of the models like customer etc. We also get scenarios bundle with some sample data for customer to load into the above model.
I have the archive but not teh excel files/Scenarios bundle for customer. So I am not sure where can i download it from on SAP network. I could not locate them in the dump of software and not sure if it is not downloaded.
Thanks.
Regards,
Roopa

Hi Roopa,
Along with the Business content, SAP has also provided some additional helpful information about the same.
Field_Mapping_and_Check_Tables.zip
https://service.sap.com/~sapidb/012003146900000761622008E/Field_Mapping_and_Check_Tables.zip
MDM_Customer_Content.pdf
https://service.sap.com/~sapidb/012006153200000057662009E/MDM_Customer_Content.pdf
Apart from this, I was not able to find sample data for Customer Master, however, I have got sample repositories for Business Partner and Product Repositories.
MDM Business Partner Repository : consists of 21,000 records that are partly ITelO related. Each record is made up of the following attribute groups: Personal Data, Address Data, and Communication Data
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8048f213-0c0e-2b10-7c97-9d8bba9a7541
MDM Product Repository : consists of 100 records which are ITelO related. Each record is made up of the following attributes: Product Name, Product Group, Manufacturer
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9097399d-090e-2b10-d6b7-8881cef03b31
This info is avaliable from SAP on SDN itself.
Hope this info helps
Thanks and Regards
Nitin jain

SRM Product / Material creation - Data flow to SAP MDM

Dear SAP friends,
I need your help with 2 issues. Thanks in advance for your collaboration.
Our client needs to create products and make them available to purchase almost immediately.
The scenario we had working for the last 2 years was: product creation in SRM (fields: short description / product category / measure unit), that would then be sent to SAP MDM for data enrichment, through BBP_CCM_TRANSFER_CATALOG (JOB running every 1 minute). This solution worked well for the last 2 years.
Recently, we are having some problems with this job. We noticed that, sometimes SRM doesn´t send the new products to MDM, and we think it´s a report performance problem. The report doesn´t maintain is normal behavior when executed every 1 minute.
SAP advice is to only run this report once a day. That would obviously require having a minimum time frame of 1 day between product creation and its availability (purchase), which isn´t acceptable in this client business model.
Question 1: Did anyone have a client with similar requirement? What was the implemented solution?
Because of report performance problems, we are running it (BBP_CCM_TRANSFER_CATALOG) every 5 minutes. It happens that sometimes, more than one catalog manager creates products in that time frame, and MDIS when importing the products to MDM, creates one unique workflow JOB making it impossible to assign it to both catalog managers for enrichment.
Question 2: How can we ensure that SRM sends only one product per xml files sent to XI / PI ? Or, perhaps, ensure that XI / PI splits the xml file sent from SRM into several files with one product each.
Thank you very much for your help in advance,
Best Regards,
João S. Carvalho

Hi meka
In product costing values flows as follows;
In product cost calculation raw material prices are costed which comes from material master in MM01
Product operations: i.e material BOM and master receipe or routings from PP module.From PP module operation costs comes in product costing.
In CO module: In Tcode KP26 we maintain activity\cost center planning for activities like machine hours, set up hours, labour hours etc.Here we define plan quantity and plan prices.
In Cost Sheet (KZS2) we maintain base cost elements & overheads and While order creation we calculate planned cost of that particular material.and then check the variances after getting actual cost of product.
Hope this will help you and if found useful assign points.
Let me know if you need more information.
Regards
Nilesh.

Data Import from SAP R/3 to SAP MDM 7.1 without SAP PI

Hi All,
I have a requirement to import Vendor Master data from SAP R/3 to SAP MDM 7.1 on a regular basis. What are the Options available for data transfer between these two systems without any middleware(like SAP PI,etc). I checked the SAP Documentation and found the scenarios with SAP PI as middleware.
I have few very basic ideas:
1) Will there be any way for SAP MDM to pick a file from certain location and load the data..
2) Shall I use MDM ABAP API to write a program to connect to MDM Repository and schedule this at regular intervals to achieve the data transfer.
Pls suggest the best design approach..
Thanks in advance.

1) Will there be any way for SAP MDM to pick a file from certain location and load the data..
ANS : No, MDM will not pick up the file, file can be pick up from MDM Inbound folder and send from outbound folder for automize process and for MDM manual Process you can pick up and send file to local desktop, network shared path
2) Shall I use MDM ABAP API to write a program to connect to MDM Repository and schedule this at regular intervals to achieve the data transfer.
ANS : require to write code at ABAP side
so ABAP program will pick or send data file to MDM folder
Note following point
1. Require to write ABAP Program which will pick or send data file to MDM outbound / Inbound folder
2. Require to do some technical setting for ABAP program at SAP side, technical person will help regarding this matter
Note : There are many disadvantage and time consuming procss, monitoring file and it is not advisable to go without any intermidiate software for e.g PI, Tibco
Thanks,
Jignesh Patel

Brief discussion on SAP XI and its' Integration with SAP MDM.

Hi,
I have never worked on SAP XI.
I am discussing it on brief, please give your valuable replies.
SAP XI consists of System Landascape Directory(SLD).
SLD Consists of Business System and Techinical System.
Technical System contains all information about the software
component. The Business System consists of Inbound and Outbound Business
System which are used as logical names for data transfer.
There is communication Channel for Receiver and Sender Business System and n agreement
is signed between Sender and Receiver.
Outbound Interface defined for Business System Outbound and Techical System associated
with the Business System,
Inbound Interface defined for Business System Inbound and Techical System associated
with the Business System.
In SAP NetWeaver XI Integration Directory, we have defined the Integration Scenarios,
Actions, Interface Objects, Mapping Objects, Adapters Objects.
Mapping Object defines the Structure and Value Mapping.
Adapter Objects defines the Adapter program which implements RFC Adapter, FTP Adapter logic.
FTP Adapter is used for XI-MDM Communication.
RFC Adapter is used for XI-ECC Communication.
Integration Repository: Both Outbound and Inbound Interfaces are Mapped with Value mapping and
Structure Mapping inside Integration Repository.
The File Adapter takes the File from the Outbound port of MDM System
and sends it as IDOC to Receiver Business System.
Value Mapping must be done between Sender and Receiver interfaces.
Value Mapping is done by XSLT or Java based program.
SAP NetWeaver XI Integration Server at runtime:
Message Split, Interface Determination, Receiver Identifaction, Mapping, Techincal Routing
and Call Adapter Proccess are done.
In SAP XI 3.0 and MDM 5.5:
Step 1: Create busines system as service.
Step 2: Create communication channel for each business service. If the system can communicate
through different channels, then create all possible channel types if necessary.
Step 3: Create receiver agreement between the systems.
Step 4: Interface determination:
- Here you see for the first time the software component mentioned;
there are some special requirements regarding this software component in relation to the customizing ID mapping.
- To modify this software component, the customer needs to copy the SAP standard delivered software component
into its own namespace. The customer is able to modify to create archives
for the customized ID mapping.
Receiver determination.
Configure an FTP Server on the MDS.
Create a send folder for outbound messages using outbound port(s) for
remote systems(s).
Create receive folder inbound messages using inbound port(s) for remote systems.
This ia all about concept of SAP XI Infractsture and its' Integration with SAP MDM 5.5.
Regards
Kaushik Banerjee

Hi Kaushik,
You must be aware of File types that MDM Import Manager can Import i.e. we have XML, Excel etc. Now there are two transactions to extract data from R3
1. MDMGX -
         - For lookup table extraction
         - Output in XML format which MDM can import without using XI.
          - FTP can be configured to put the file in the desired folder which will be then picked by Import Server.
2. MDM_CLNT_EXTR -
          - For Main table records.
          - Output is in Idoc format which MDM doesn't understand hence we need XI in between which converts Idoc file received from R3 into XML which can then be imported using Import Manager or Import Server. For this we need to implement XI Scenario that consists of Source System, Receiver System, Type of Data etc.
Just a basic understanding...
Regards,
Jitesh Talreja

What is DB View in SAP MDM 7.1? How to create it?

Hi All,
Could you please let me know that what is DB view in SAP MDM 7.1?
I came to know that sap provides a special tool which does the creation of DB views.
Where will I get those tool details? and How to create it?
Thanks in advance,
Nirmala.
Edited by: C Nirmala on Oct 25, 2010 12:40 PM

Hello
This DB view is not part of standered shipmet. for that you need to contact SAP repsentative.
for more details you can refer below threads
DB Views in MDM
Re: MDM and Data Services Integration Scenarios - Part I: Advanced Consolidatio
Hope it helps
Rgds
Deep

SAP MDM field status and SAP ERP field status

Just wanted to understand what are the implications of a field status mismatch between SAP MDM and SAP ECC for Vendor Masters. Further, what happens in a scenario where the vendor master data is changed directly in SAP ECC. I am presuming that both systems will not be in sync as the MDM system talks one way and updates the SAP ECC system. Or is there a feasibility whereby any change carried out in SAP ECC is also routed back to SAP MDM.

Hi,
Basically MDM is implemented in order to maintain Master Data at single location, such that control can be incorporate in flow of Master Data.
Thus it is recommended that master data should be changed or created in MDM itself and than syndicated to other systems.
But in case Master Data need to be changed in ECC, MDM ABAP API's can be used to update data in MDM Repositories directly from ECC so that Master Data remains in Sync.
(Using MDM ABAP APIs, code can e developed in ECC to update fields in MDM.)
Regards,

Filter the results set for custom iviews in SAP MDM

We have a scenario where based on the user name/user role we want to filter the results retrieved by an search result iview developed for accessing data from SAP MDM Repository.
E.g.
We have a lookup table called Plants which contains master data pertaining to manufacturing plants.
The portal user P00100xxyy is responsible for maintaining master data for a plant 1101. However, the plant lookup contains data for other plants as well.
We would like to prevent the user P00100xxyy to see/modify data for other plants in the table.
We have explored the core MDM functionality of security/constraints. It does not provide row level granularity and we are hoping that the iview approach can help us achieve row level filters.

Hi Rajni thanx for ur prompt reply
The actual problem is that :
we have approx near about 100 Account Group, so it would become very complex to replicate same condition 100 times
AND
these account group may keep on increasing so even maintenance point of view it would be hard to maintain.
can u tell me some other way to do it, i mean is there any other feature by which we can perform validation in MDM.
Regards
Kuldeep

SAP MDM == PI== SAP ECC, IDOC posting

Hi,
We are integrating SAP ECC 6.0 with SAp MDM 7.1 SP04 using PI 7.1 as a interface. Scenario is SAP MDM ==>PI==> SAp ECC. I would be creating record in ECC and will be posted in SAp ECC through PI. We will be creating Basic Data (MARA), Plant level data (MARC), Sales Level data (MVKE), and Valuation level Data (MBEW) in MDM. IDOC used is MATMAS05.
Plant level data (MARC) will activate various views in Material master like Purchasing, Sales plant general data, MRP views and accounting views...right
I donu2019t want to activate MRP view but need plant level data i.e. Plant and profit center to populate in MARC table. Means same Material Type but some Materials donu2019t have MRP view activated and some may have alongwith other plant related views.
I tried creating record without passing MRP related fields but still IDOC failed saying MRP type is mandatory. (Which means it is activating MRP view)
Do we have separate IDOC for MDM integration?? Do I need to enhance IDOC??
Warm regards,
Rc
NOTE - This is possible while manual creation as will as through BAPI.

Hi,
Have you checked MDM71_Material_Content.pdf page no 20.
3.3.2 Business Scenario: MDM710_Outbound.
You also need MDM PI content to install and run this Scenario..
Hope it helps if you go through MDM71_Material_Content.pdf
As you said, I tried creating record without passing MRP related fields but still IDOC failed saying MRP type is mandatory
Try passing any constant through PI Message Mapping to inbound IDOC (Receiving System, ECC)
Thanks and Regards,
Mandeep Saini

Central Contract, MDM Catalog, and classic scenario

Dear SAP experts,
We are in SRM 7.01 with backend ECC 6.05 deploying classic scenario. We are using Central Contract Management in which we negotiate contract in SRM and later distribute it to ECC. We also plan to use SRM-MDM Catalog.
We notice that if we are using classic scenaro, the contract that is used as reference is the contract number in ECC (the one distributed from SRM). So at first we assume that if we want to push the contract data to MDM, we should have pushed the ECC Contract number. However we find out that actually SAP block the ECC Contract coming as distribution from SRM to go to MDM.
Our second option is to use distribution of contract from SRM to catalog. It does using SRM contract number. We create SC and then we pull the catalog item from the catalog (which contain SRM contract number) and then we order. However we end up with 'error in process' in which the system try to create a PR instead in the ECC (meaning that the contract number cannot be read).
We're puzzled with this. How can we use the combination of central contract, MDM catalog and classic scenario? Can we use the combination?
Best regards,
John

Maria
If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
Then local contract data should pick as SOS from the vendor list.
If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
Let me know if the above works or not.
PS : Reward points if helpful.
Regards
Jagadish

Need to integrate SAP MDM 5.5 with BW

Hi,
I am working on SAP MDM for last 4 months.
I don't have any knowledge of BW.
I need to integrate SAP MDM 5.5 with BW.
I have checked with SAP R/3 SAINT transaction
that MDM_TECH 555_700 is installed.
Now, I have created logical connection with MDMAPI transaction.
I have created an file named allow.ip and saved this in
C:\Configuration.
In allow.ip, I wrote the ip address of R/3 System.
I didn't create any deny.ip.
In MDS.ini , I have given location.
TrustFiles Dir=C:\configuration
Now, I have to find the OHD from BW.
I need to see how?
First of all that logical connection is not working.
There is a Connect Function module mdm_accessor_connect .
Here we have to give RFC target system.
Now I created a RFC target system.
I created a type 3 ABAP based RFC target system.
Would it be TCP/IP based system?
Here is the step where my Logical System creation failing.
How to get the OHD Connection object from BW System?
Regards
Kaushik Banerjee
Edited by: Kaushik Banerjee on Sep 22, 2008 11:33 AM

Hi ,
It is possible to transfer data directly from BI to MDM without using XI.I have worked on the same scenario.
Below is the link which will help u .
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e01d1085-5a51-2a10-2292-b52eb7500180
But u need to take BI"s help to do so.
MDM BI Integration using ABAP API
Hope this is helpful

For sap mdm do i need to know webdynpro abap or java

hi
i want to learn sap mdm, then do i need to have knowledge in any of following languages?
1. webdynpro abap
2.webdynpro java
3. normal java( core java/j2ee )
4. normal abap
thanks
akhil

If you are using ABAP APIs then normal ABAP knowledge will come in handy
If u want to connect your MDM server to a portal system, then Portal knowledge will come in handy
Even the basic MDM scenarios are generally done by using Exchange Infrastructure
so basic knowledge of that is essential

SAP MDM Implementation Methodology and Architecture

Hello,
I wanted know what are the standard approaches for MDM architecture and MDM Implementation:
MDM Implementation phases:
what are standard phases recomended by SAP?
Architecture:
what are different mdm architectures that an Enterprise can think of?

Hello SudhaViz
SAP MDM can work as independent solution for master data management.
SAP MDM has own servers( MDM Server, Import Server, Sysndication Server, Layout Server, and user application s for server management and master data management.
SAP MDM can work with different RDBMS like as Oracle , MS SQL, My SQL, DB2.
Here is good presentation about SAP MDM and it's business scenarios:
http://www.sdn.sap.com/irj/scn/index?rid=/media/uuid/0030d731-65ac-2d10-6197-d64f34811d94
Here is detail documentation :
http://help.sap.com/saphelp_nwmdm71/helpdata/en/mdm_index.htm
Regards
Kanstantsin Chernichenka

SAP MDM and Zycus or Zoomix or Kalido or Trillium

Hi All,
please, could you help me to understand better which is the best enterprise-wide master data management software solution for harmonizing, storing and managing master data over time??
Even if Ill use SAP MDM; I need to cleanse and harmonize MD.
What about Zynapse? Kalido? Zoomix? Trillium??
Thank u in advance
Regards,
da

Hi,
Kalido MDM :
Master (reference) data management is thought as a special form of data warehouse federation(A federated data warehouse consists of a set of data warehouse instances that operate semi-autonomously, are generally geographically or organizationally disparate, but which can be thought of as one large data warehouse).
   However, experience shows that such systems are complex to manage and that, over time,the absence of a common warehouse (a single common source of master data) leads to inconsistency and frequent errors in transactional data.
    Furthermore, such systems generally do not easily lend themselves to being rapidly adapted to new business requirements since they are often dependent upon writing low-level code to effect the revisions.
            The high level architecture for a federated set of data warehouses with integrated data, based on maintenance of master data using a Master Data Warehouse, which supplies
master data to both the data warehouse federation and the underlying source systems.
It is important to note here that the Master Data Warehouse is in effect an operational system since it manages all master data flowing through the organization.
This demands effective processes and procedures for management and ownership of master data.
SAP MDM
Companies striving to accelerate business growth and improve business performance need to innovate and remain flexible to dynamic market forces. NetWeaver provides the ideal platform for enabling such innovation and flexibility. Satyams NetWeaver Practice provides a host of solutions based on the primary user interface (EP) framework, the primary integration engine (XI), the primary data management tool (MDM), and the business process orchestration tool that enable customers to:
     Design, build, and implement new business processes
     Knit together disparate processes and systems
     Develop a unified view of information from every facet of the organization, and deliver it to stakeholders when and how they need it through a dedicated NetWeaver Center of Excellence
SAP Master Data Management (SAP MDM) enables master data on customers, partners and products to be consolidated and harmonized across the enterprise, making it available to all staff and business partners. A key component of SAP NetWeaver, SAP MDM ensures data integrity across all IT systems.
The SAP NetWeaver Master Data Management (SAP NetWeaver MDM) component of SAP NetWeaver creates the preconditions for enterprise services and business process management. The functionality represents customers, products, employees, vendors, and user-defined data objects in unified form. With SAP NetWeaver MDM, customers can manage master data and supplemental content, such as texts, PDF documents, high-resolution images, or diagrams in a central business information warehouse.
SAP Master Data Management (SAP MDM) is a component of SAP's NetWeaver product group and is used as a platform to consolidate, cleanse and synchronise a single version of the truth for master data within a heterogeneous application landscape. It has the ability to distribute internally and externally to SAP and non-SAP applications. SAP MDM is a key enabler of SAP Enterprise Service-Oriented Architecture. Standard system architecture would consist of a single central MDM server connected to client systems through SAP Exchange Infrastructure using XML documents, although connectivity without SAP XI can also be achieved. There are five standard implementation scenarios:
Content Consolidation - centralised cleansing, de-duplication and consolidation, enabling key mapping and consolidated group reporting in SAP BI. No re-distribution of cleansed data.
Master Data Harmonisation - as for Content Consolidation, plus re-distribution of cleansed, consolidated master data.
Central Master Data Management - as for Master Data Harmonisation, but all master data is maintained in the central MDM system. No maintenance of master data occurs in the connected client systems.
Rich Product Content Management - Catalogue management and publishing. Uses elements of Content Consolidation to centrally store rich content (images, PDF files, video, sound etc.) together with standard content in order to produce product catalogues (web or print). Has standard adapters to export content to DTP packages.
Global Data Synchronization - provides consistent trade item information exchange with retailers through data hubs (e.g. 1SYNC) Some features (for example, workflow) require custom development out of the box to provide screens for end users to use.
Trillium :
It is basically used for Data profiling.It can be used for data enhancements with certain address masters and other masters avaialble in the box. There is a lot of data quality analysis can be done in Trillium
Advantages of Zoomix :
1.Fast, accurate, automated, self-learning system :
2.No scripting or rule development required Zoomix Accelerator never requires the development of scripts or the manual definition or maintenance of data processing rules. The system automatically interprets data to learn the optimal matching, normalization and classification required for any data domain.
3.Processes all types of complex corporate data Zoomix Accelerator works equally well with product data, customer data, supplier data, financial data, etc. in any language or combination of languages.
4.Rapid integration into existing applications and business workflows The system's integration with daily user workflow provides objective, on-the-fly data correction. Erroneous, duplicated and incorrectly categorized data are repaired immediately, without disrupting routine business functions.
Reward points if helpful
Regards
nisha
Edited by: Nisha Lalwani on Mar 4, 2008 2:25 PM

Web services @ SAP MDM

Hello Experts,
What is the use of web services for SAP MDM??
And how can we achive it!!!
Can anyone take sometime in explaining it in simple words..
Thanks in advance.
Kind Regards
Eva

Hi Eva,
MDM Web services are open interfaces to the MDM Server and provide synchronous access to MDM for the consumer of the Web services. They are based on the Simple Object Access Protocol (SOAP) and Web Services Description Language (WSDL) standards.
MDM Web services are used to customize and build functionality into an application and can be integrated into various business scenarios to provide the following capabilities:
●      Data management u2013 create, read, update, and delete
●      Access to central key mapping u2013 create, read
●      Checkout management u2013 checkout, check in, join checkout, unjoin checkout
●      Consolidation of records using the matching functionality
●      Execution of assignments
●      Validation
●      Workflow management u2013 launch, get job status
●      Syndication of records
Refer attached Link for more informatin
[http://help.sap.com/saphelp_nwmdm71/helpdata/en/49/06eac7dc78132ee10000000a421937/frameset.htm]
Cheers,
Rc

SAP MDM-XI-R/3 Scenario

Similar Messages

Maybe you are looking for