Material creation process in SRM-MDM

Dear All,
I am new to SRM. Please correct me about material creation procedure in SRM if I am wrong:
Normally in classic/extended classic scenario, material first created in MM and then it replicated to SRM. Base on configuration setting for number range, system either create the product ID same as material number number in SRM when it replicated into SRM. In final steps, the product information will upload into MDM either XI integration or manually via excel upload.
My question:
+ Is it possible to automatic create product without XI via T.Code - MDMGX in MDM.
+ If the replicated product ID of SRM is different then MM material number, which number we should consider for creating product
MDM.
Thanks in advance.
BR
Jennifer

Hi Jennifer,
Answer1) You can only replicate Product Groups, Currencies and Unit of Measures through t-code MDMGX. XI/PI is required for Contract and Product Catalogs.
Answer 2) If the replicated product ID of SRM is different then MM material number, you should enter MM material number and in External Web Service Configuration for that internal catalog, uncheck "Do not check Product" indicator so that SRM will not check the Product ID and when item goes to backend system, it will have correct MM material number.
Thanks,
Anshuk Saxena

Similar Messages

Material creation in ECC Frm MDM

Hi Gurus,
Has any one tried creating new Material records in ECC frm MDM?
I have a scenario wherein a user logins from EP and creates a new material record.This triggers the MDM workflow and the enrichment of the record happens.
Finally this material needs to be posted in ECC using XI.
I have tried doing this but however, the idocs fails saying that the Material Does not exists or is not activated..
Can any one guide me on this.
Helpful answers will be rewarded
Thanks
Simona

Hi Harrison,
I am entering the material number from MDM which comes under the external number range for that material type.
I have also checked with the settings and found that,the material type that i am using excepts both internal and external numbering.
So the material number should not be a problem rite?
But the error message says something abot activating the material,how can that be done from MDM?
Thanks & Regards
Simona

Need SMP link for SRM MDM GUI setup

Hello all,
Can any one help me by providing the link for the following downloads in SMP.?
-- SRM MDM Console
-- SRM MDM Import Manager
-- SRM MDM Workflow
Thanks,
Dinesh.

Dinesh -
Procurement Catalog Management based on SAP NetWeaver Master Data Management allows you to create, cleanse and manage your centralized supplier catalog facilitating a smooth flow in the procurement process.
SAP NetWeaver Master Data Management technology ensures data integrity and enables the content management processes in SRM-MDM Catalog. It lets you manage data and communication in an integrated environment for streamlined catalog content management.
first of all you can get all relevant materials for SAP MDM latest in below link
https://websmp203.sap-ag.de/installmdm71/
for console, IM, DM and syndicator as well.
for SRM MDM perspective follow
SAP MDM Procurement Catalog Management
in this you can also get wiki for SRM MDM solution.
HTH
thx
Deep

SRM-MDM catalog 3.0 - Installation Process

Hi All,
I'm in the process of installing SRM-MDM catalog 3.0 but I'm not sure about the correct installation process.
The SRM-MDM catalog 3.0 installation guide indicates that the following instances are mandatory for SRM-MDM Catalog system:
1- Java system with the central instance, the central services instance, the database instance
2- MDM Server, and MDM Import Server
We have covered the first point by installing an SRM 7.0 JAVA system. Regarding the second requirement, I have some doubts in the way it should be completed. What we did so far was to install the SRM-MDM catalog 3.0 from the MDM 7.1 installation master. So, we now have two MDM server instances: MDS and MDIS.
I'm stuck now. I'm not sure on how to connect my SR-MDM system to the JAVA DB (created in step 1) to create a new MDM schema within it. This makes me wonder if I've followed the correct process. Could you please clarify and explain which steps should be performed to get my SRM-MDM system up and running? Actually my main concern is..Should I first install a MDM system as it's described in MDM IG, and after that perform the installation of the SRM-MDM catalog as I've already done in step 2?
Hope being clear enough I'll wait for your suggestions.
Thanks and regards

Hi Diego.
The Installation Note Number for SRM-MDM Catalog 3.0 is : 1177779. The recommended steps would be to follow how the Installation Guide recommends you to do so.
But still your assumption is correct. MDM landscapes and Java landscapes are both different set of categories to be installed to make the Catalog scenario to be successfull.
Step 1: Make sure you have the back end database server(SQL/Oracle/???) is installed.
Step 2: Make sure all the MDM components(MDS, MDIS, etc) is installed.
Step 3: Make sure Java WebAS is installed correctly.
Step 4: Now deploy the Catalog SCA and MDM Connector deployed in the Java WebAS.
Step 5: You can unarchive and load the repository.
Step 6: Try to launch the catalog using the URL provided to check and make sure if the connection is fine.
Also what Masa has mentioned is the communication path how the whole process is achieved technically and that doesn't mean that it has to be in the same order which he has mentioned. The below sequence is just an path to describe how the communication is achieved technically.
User -> Browser(Search UI deployed on AS Java) -> (Java API on AS Java) -> MDM Server -> MDM Repository -> DB
Relating Masa's path with the above steps
User ->
Browser(Search UI deployed on AS Java) -> Step 3 and 4
(Java API on AS Java) -> Step 3 and 4
MDM Server -> Step 2
MDM Repository -> Step5
DB-> Step 1
Hope this helps.
Regards
Bala
Edited by: chandar_sap on Aug 30, 2010 6:16 PM

XI Integration scenario for material replication from SRM to SRM-MDM

Hi Guys,
We are working with the following landscape:
SRM Server 5.5
ECC 6.0
SRM-MDM 5.5 SP6
PI 2005_1_700 SP0006
I have a question for you about replication of the material master form SRM EBP to SRM-MDM.
In XI we are trying to configure this scenario. For this we have imported the following XI Content:
- SAP SRM Server 5.5
- SAP SRM-MDM 2.0
We have the following problem; that when tring to configure the this scenario we are getting GUID errors. Probable because some XI content is missing. In the SRM-MDM 2.0 XI content we also see that SRM 6.0 scenario's are avilable in the currenlty imported XI content, but when clicking on 'Edit action' in these scenario's we are getting the following error:
"Software component version with GUID XXXXXXXXXX... does not exists"
Can any one tell me why SRM 6.0 scenario's are availble in the XI content for SRM-MDM 2.0, and which additional XI content we need to import to get rid of these GUID error's?
Becasue of this the configuration in the Integration Directory fails.Transfering the integration scenario to the Integration directory gives a couple of errors: "Unable to load action. Check whether all necessary actions have been released in the integration repository".
Hopefully some of you know what to do, because I am currenlty stuck....... Do we need to import additional XI content, or maybe the Xi content for SRM 6.0. If so where can I get the XI content for SRM 6.0. It is not available on the SAP Support portal as a download.
Thx In advance.
Regards,
Wouter

Hi,
>"Software component version with GUID XXXXXXXXXX... does not exists"
try updating SLD (CIM DATA) with the latest patch available
Regards,
Michal KRawczyk

Process flow of material creation

hi sap gurus,myself rekha
i want to know the process flow of material creation-FERT

Check below link .You have to use transaction MM01 to create material.
https://www.google.com.au/search?q=process+flow+for+material+creation&oq=process+flow+for+material+creation&aqs=chrome..69i57.9710j0j8&sourceid=chrome&espv=210&es_sm=122&ie=UTF-8#q=process+flow+for+material+creation%2Bsap

Material Replication from ERP to MDM (SRM-MDM Catalog)

Hi Experts,
I would like to replicate the material master from the ERP system into the MDM (SRM-MDM Catalog)?
I don't want to replicate the materials from ERP to SRM, and then from SRM to MDM.
1. Does ERP provide any transactions to achieve this ( like MECCM / MDM_CLNT_EXTR) ?
2. Is there a necessity to use the PI system in these communications? If so, what Integration Scenario I need to use in PI Enterprise Repository?
3. Any further changes to Materials in the ERP system should automatically replicate into the MDM system.
From SRM, I create SC with items from Materials in MDM.
Please let me know if you require more information.
Thanks
Kasee

Dear Krupa,
Thank you for your quick reply.
So we should consider the scenario where SRM is the central repository for the contracts, and all the changes done in SRM should be replicated to ERP.
In this scenario, do you know which steps should be done to allow contract replication from SRM to ERP? I already created a central contract in SRM but there is no message sent to PI.
Thanks in advance.
Regards,
Andreia

Is use of flat file in SRM-MDM catalog search UI possible ?

Hello,
When user looks for materials inside SRM-MDM catalog (using search user interface), search is done manually with free form or drill down search.
Then, among the search result, user has to select items he wants to add to his shopping cart and finally transfer those items from his shopping cart overview inside SRM.
Is it possible to automate this user selection using for exemple a flat file uploading (or any other way you could know) ?
This flat file will have material number (or service), supplier code and quantity (no more information).
The aim of the request is to help requester to not have to select each item one by one (in the search result) knowing that :
- SC will have more than a hundred items,
- delivery time and price (for example) must be checked in MDM, being the master data reference
- materials (or service) to order are received by requester via a flat file without any information about prices, so i cannot upload my flat file directly into SRM because file missing data must come from MDM.
With this process, user should have only to transfer items automatically selected.
Could you please share your advises ?
We use SAP MDM 5.5.
Regards.
Laurent.

Hello Masa,
Masayuki Sekihara wrote:
A vendor look at buyer stock information like VMI and fill stock weekly base. So the vendor sends material number and quantity information as flat file to buyer. Buyer should create SC from flat file and price information should fetch from catalog.
Yes, your are correct: example you gave corresponds to process for my SC uploading.
Regards.
Laurent.

Third Party Processing in SRM 4.0

Hi,
We are working on Third Party Processing in SRM4.0 & SAP R/3 4.7.
We were able to transfer the Third party Requisition from Backend R/3 to SRM 4.0 Sourcing Cockpit as an External Requirement.
When we try to process the Third Party External Requirement to create a PO in Sourcing Cockpit, the system is not identifying the Customer Number as a Business Partner in SRM 4.0 and it is throwing a dump with the error message 'Partner xxxxxxxxxx not found'
Please help us to understand the procedure for replicating the Backend R/3 Customer Masters and its Address into SRM 4.0
Where can i find documentation for Third Party Processing in SRM 4.0 as i could not find anything in SAP Help
Please do let me know if you need any details/clarifications
Thanks in advance
Regards,
Sunil

Hi Vitthavat,
All you have done is fine.
As per you SO - PR is already automated, now to automate PO creation from PR:
Do the following thing:
1. Activate u2018Automatic PO' indicator for material master
2. Activate u2018Automatic PO' indicator for vendor master
3. The purchase requisitions with vendor assignments are converted into POs by a batch job using transaction ME59/ME59N and ABAP program with requisite parameters.
This ensures automatic creation of POs.
So result: When SO is saved PR and corresponding PO will be generated automatically.
Your problem will be solved.
Regards,
Anirban Roy

Scenario - ( EC6 - XI - SRM-MDM Catalog )

Hi,
I am working on Scenario"Transfer Info records and contracts from ERP, Auto Import of contract and info Records from ERP".
Scenario:

Sender Side:
=>Run Tcode: MECCM in ERP system and send Purchasing info records to Catalog system via XI.
Recvr Side:
=>Same will be received as XML file in a file location(FTP Server running on SRM MDM catalog system).

XI Side:
=>I have uploaded XI Content in repository and same has been transported to Integration Directory also.
=>Using Intergation scenario configurator i have done all configurations in Integration Directory also.
=>I have configured XPATH in condition field for interface determination as dicussed in SAP OSS Note 967088 to be used for ths scenario.
=>Now when i am running the tcode from sender side message is getting stuck in SXMB_MONI with error: No receiver Determined.
I can understand there is some problem in Receiver Determination. When i tried to check all settings, only thing i found fishy was There was no Interface mapping being displayed in Interface determination but condition field is filled as discussed in SAP note 967088.
I doubt there is some problem in interface determination only.
Expert comments are required. I can send you screenshots if required.
Any help is appriciated.
Thanks,
Vijay Raheja

Here is the XML Payload
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:CatalogueUpdateNotification xmlns:nr1="http://sap.com/xi/SAPGlobal/Global">
- <MessageHeader>
<ID />
<CreationDateTime />
</MessageHeader>
- <Catalogue actionCode="04">
<CompleteTransmissionIndicator>TRUE</CompleteTransmissionIndicator>
<ID>SRM-MDM CATALOG</ID>
<TypeCode>04</TypeCode>
- <Model>
- <PropertyDataType actionCode="04">
<ID schemeAgencyID="">PURCHORG_TYPE</ID>
<FormatCode>String</FormatCode>
</PropertyDataType>
- <PropertyDataType actionCode="04">
<ID schemeAgencyID="">PURCHINF_TYPE</ID>
<FormatCode>String</FormatCode>
</PropertyDataType>
- <Property actionCode="04">
<ID schemeAgencyID="">PURCHORG</ID>
<PreferredName languageCode="EN">Purchasing Organization</PreferredName>
- <PropertyDataTypeReference>
<ID schemeAgencyID="">PURCHORG_TYPE</ID>
</PropertyDataTypeReference>
<AspectID>LIST_VIEW</AspectID>
<AspectID>DETAIL_VIEW</AspectID>
<TargetInterfaceElementID schemeID="01">NEW_ITEM-PURCHORG</TargetInterfaceElementID>
<MultipleValueIndicator>false</MultipleValueIndicator>
<TextSearchableIndicator>false</TextSearchableIndicator>
<ParametricSearchableIndicator>false</ParametricSearchableIndicator>
<ValuationRequiredIndicator>false</ValuationRequiredIndicator>
</Property>
- <Property actionCode="04">
<ID schemeAgencyID="">INFREC</ID>
<PreferredName languageCode="EN">Number of Purchasing Info Record</PreferredName>
- <PropertyDataTypeReference>
<ID schemeAgencyID="">PURCHINF_TYPE</ID>
</PropertyDataTypeReference>
<AspectID>LIST_VIEW</AspectID>
<AspectID>DETAIL_VIEW</AspectID>
<TargetInterfaceElementID schemeID="01">NEW_ITEM-PURCHINFREC</TargetInterfaceElementID>
<MultipleValueIndicator>false</MultipleValueIndicator>
<TextSearchableIndicator>false</TextSearchableIndicator>
<ParametricSearchableIndicator>false</ParametricSearchableIndicator>
<ValuationRequiredIndicator>false</ValuationRequiredIndicator>
</Property>
- <CatalogueSchema actionCode="04">
<ID>MMPUR_CAT</ID>
<CatalogueSectionListCompleteTransmissionIndicator>true</CatalogueSectionListCompleteTransmissionIndicator>
- <CatalogueItemProperty>
- <PropertyReference>
<ID schemeAgencyID="">PURCHORG</ID>
</PropertyReference>
<OrdinalNumberValue>1</OrdinalNumberValue>
</CatalogueItemProperty>
- <CatalogueItemProperty>
- <PropertyReference>
<ID schemeAgencyID="">INFREC</ID>
</PropertyReference>
<OrdinalNumberValue>2</OrdinalNumberValue>
</CatalogueItemProperty>
- <CatalogueSection actionCode="04">
<ID>001</ID>
<Name languageCode="EN">metal processing</Name>
</CatalogueSection>
</CatalogueSchema>
</Model>
- <Content>
<CatalogueSchemaID>MMPUR_CAT</CatalogueSchemaID>
- <CatalogueItem actionCode="04">
<PropertyValuationListCompleteTransmissionIndicator>true</PropertyValuationListCompleteTransmissionIndicator>
<ID>5300000000__________00000RBB1____0______</ID>
<Description languageCode="EN">srm material 1</Description>
- <Classification>
<CatalogueSchemaID>MMPUR_CAT</CatalogueSchemaID>
<CatalogueSectionID>001</CatalogueSectionID>
</Classification>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/PRICE</ID>
</PropertyReference>
- <ValueGroup>
<ID>1</ID>
<OrdinalNumberValue>1</OrdinalNumberValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/AMOUNT</ID>
</PropertyReference>
- <ValueGroup>
<ParentID>1</ParentID>
- <PropertyValue>
- <AmountSpecification>
<Amount currencyCode="EUR">0.0</Amount>
</AmountSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/PRICE_BASIS_QUANTITY</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <QuantitySpecification>
<Quantity unitCode="EA">2.0</Quantity>
</QuantitySpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/CONTRACT_ID</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
<NameSpecification />
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/CONTRACT_ITEM_ID</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>00000</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/LEAD_TIME</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>0</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/ORDER_UNIT</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>EA</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/PRODUCT_GROUP</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>001</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/PRODUCT_ID</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>000000000000000011</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/SUPPLIER_ID</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>RBDE1</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">PURCHORG</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>RBB1</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">INFREC</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>5300000000</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
</CatalogueItem>
- <CatalogueItem actionCode="04">
<PropertyValuationListCompleteTransmissionIndicator>true</PropertyValuationListCompleteTransmissionIndicator>
<ID>5300000000__________00000RBB1RBBE0______</ID>
<Description languageCode="EN">srm material 1</Description>
- <Classification>
<CatalogueSchemaID>MMPUR_CAT</CatalogueSchemaID>
<CatalogueSectionID>001</CatalogueSectionID>
</Classification>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/PRICE</ID>
</PropertyReference>
- <ValueGroup>
<ID>1</ID>
<OrdinalNumberValue>1</OrdinalNumberValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/AMOUNT</ID>
</PropertyReference>
- <ValueGroup>
<ParentID>1</ParentID>
- <PropertyValue>
- <AmountSpecification>
<Amount currencyCode="EUR">200.0</Amount>
</AmountSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/PRICE_BASIS_QUANTITY</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <QuantitySpecification>
<Quantity unitCode="EA">2.0</Quantity>
</QuantitySpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/CONTRACT_ID</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
<NameSpecification />
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/CONTRACT_ITEM_ID</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>00000</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/LEAD_TIME</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>5</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/ORDER_UNIT</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>EA</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/PRODUCT_GROUP</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>001</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/PRODUCT_ID</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>000000000000000011</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">/CCM/SUPPLIER_ID</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>RBDE1</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">PURCHORG</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>RBB1</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
- <PropertyValuation actionCode="04">
- <PropertyReference>
<ID schemeAgencyID="">INFREC</ID>
</PropertyReference>
- <ValueGroup>
- <PropertyValue>
- <NameSpecification>
<Name>5300000000</Name>
</NameSpecification>
</PropertyValue>
</ValueGroup>
</PropertyValuation>
</CatalogueItem>
</Content>
</Catalogue>
</nr1:CatalogueUpdateNotification>
Thanks,
Vijay Raheja

SRM 7.0 and SRM MDM Installation query

Hi,
I have installed Both AS ABAP and AS JAVA Stack separately and going forward I need to know
1) Do I need to install any other servers other than this like EP and PI etc?
2) I also wanted to install SRM MDM, for that I have gone through some documents and threads and found that
Prerequisites
1. SRM Server- Installed with ORACLE database
2) For SRM MDM
Ø Download the SRM-MDM Catalog 2.0 installable from Market Place-- Done
Ø Install the MDM Server and other GUI Clients--Done
Ø UnArchive the SRM-MDM repository available with the installables only
 Need help for
 . Not able to find DBMS server
 . User
 . Password for DBMS setting
Ø Deploy the two SCA files - MDMJavaAPI and SRMMDMCAT on WAS and restart the Portal- Done
Ø Access the Config UI by using the URL http://:/SRM-MDM/SRM_MDM and change the layout as per the requirement. In this you can specify the fields to be displayed for Search, type of UI etc for the particular user
. Where I can get the "Port"
Will follow the below steps once the above issues are resolved
*Create the Web Service in SRM system and specify all the required
parameters. You should get the SRM-MDM configuration guide from Market
Place.
*Change the Org Plan in SRM to assign the Catalog to the SRM users.
*Login into EBP and select SHOP, you should get the SRM-MDM Catalog link
if all the configurations are there in place.)
3. Web Application Server
> Is seperate WAS required even after installing SRM AS JAVA stack, if yes what to install
 4) In the market place I have found that SRM MDM install.exe and in that there are two options to execute. Install MDM
 . Install SRM MDM
 Do I need to install both or only one or is this not required, if I install SRM MDM my question is what is the use of
 the above point 2 steps process this one
 Thanks,
 Jairaj
Edited by: M Jairaj on Feb 3, 2010 3:43 PM

Hi,
> I have installed Both AS ABAP and AS JAVA Stack separately and going forward I need to know
>
> 1) Do I need to install any other servers other than this like EP and PI etc?
>
As you have already installed Java stack then it will be your EP. You don't need PI for SRM MDM.
> 2) I also wanted to install SRM MDM, for that I have gone through some documents and threads and found that
>
> Need help for
>
> . Not able to find DBMS server
The DBMS Server property defines the network identification string of the DBMS instance / machine / server that is used by the DBMSspecific client on the MDM Server machine to connect to the DBMS. The brand of DBMS on which the repository is running is shown in the DBMS Type property.
NOTE ►► When you mount two MDM repositories with the same name (but located on different DBMS Servers) on the same MDM Server, MDM distinguishes them in the Console Hierarchy pane by appending the name of the DBMS Server in angular brackets to the repository name (e.g. u201Crepository <server>u201D).
> . User
> . Password for DBMS setting
>
ent. In this you can specify the fields to be displayed for Search, type of UI etc for the particular user
>
> . Where I can get the "Port"
>
Note 1414670 - MDM 7.1: Adjusting MDS port in MDIS and MDSS ini files
Check SAP Note 1077701 - SRM-MDM Catalog - FAQ
> 4) In the market place I have found that SRM MDM install.exe and in that there are two options to execute. Install MDM
> . Install SRM MDM
>
Check installation guide for this.
Thanks
Sunny

Supplier Group Creation Error in SRM 7.0

Hello,
We are on SRM 7.0, SP 9. When creating a root supplier group using tcode PPOCV_BBP in SRM, we are getting a "DATA_LENGTH_0", "CX_SY_RANGE_OUT_OF_BOUNDS" error in the program "SAPLRHOMDETAIL_PP01".
This error happens during the new supplier group creation process, when we change the default name of the vendor group with a custom name and try to save the new supplier group.
Please let me know if any one has come across this issue.
Thanks,
Raj

HI Raj,
you have to implement the note 1572049 to resolve this issue.
Regards
Ajay
Edited by: ajay ch on Aug 15, 2011 10:57 AM

Material Creation Using BDCs.

Hi all,
I have developed a program for Material Creation using BDC.
Material is Being created and that is working well and good.Here i have a Requirement to update the Newly creted material in Ztable.So when i use call transaction mathod,i have written code for updation under the line CALL TRANSACTION.where in iam getting newly creatde material from MARA table,and so it is working perfectly fine..
But our requirement should be sessions method,so when i use sessions method and exeute the program..we face the problem of updation.
the piece of code for updation is updating previously created material.
Literally speaking only the sessions are created ,when the program is executed,material is not created when program is run.Material is only created when the sessions are processed using SM35,
So how should i do here,where should be the updation code written and where will we get the newly created material in sessions method..
Pls Help me in solving this problem

hai priyanaka it might be due to configuration problem
bcos manulay also ur gettign this , so just consult ur MM consultant for soem setting
regards
afzal

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

SRM MDM 3.0 Integration with PI 7.1

I have the integration scenario where Supplier list need to transfer from SRM 7.0 to MDM 7.1 using the PI 7.1.
Imported the content into ESR (SRM Server 7.0,SRM MDM catalog 3.0 ) . I have 2 issues.
1. Try to transfer the process integration scenario from ESR to ID , I am able to see the SRM_MDM_Catalog_30 scenario. But when it did not allow me to assign the business systems and connections .
It throws an error saying that" Cannot load action; check whether all the required actions have been released in the Enterprise Services Repository". So I have done all the steps manually.
I have created the Interface determination with the following details :
Sender Interface: CataloguePublicationRequest_Out
Sender Namespace: http://sap.com/xi/EBP
Receiver Namespace: http://sap.com/xi/SRM-MDMCatalog
Receiver Interface: MDMSupplierListTransmission_In
The issue is, it does give me the option to select the any operationmappign with the above details.
Any steps in ESR missing or any CacheRefresh issue?
Thanks in advance for any suggestion.

Check the Operation mapping,like what is anbound interface and outbound interface, these details should match with interface determination details(outbound interface details).if you have configured perfectly then it will show the operation mapping.
still if you have a problem then better to refresh the cache,it will solve the problem.even you can manually type the operation mapping name in Interface determination,and test end to end.
if it is also not working out,then create one interface copy objects from two name sapces http://sap.com/xi/EBP
, http://sap.com/xi/SRM-MDMCatalog . and finish ESR and and finish ID too..
Regards,
Raj

Material creation process in SRM-MDM

Similar Messages

Maybe you are looking for