How is Idoc MBGMCR triggered/Configured in SRM Extended classic scenario

Hello All,
In the existing scenario, when confirmation is created in SUS portal, corresponding confirmation gets created in EBP .
Once the confirmation in EBP gets approved ,we want corresponding confirmation creation in backend system (ECC) .
I thought of using the standard idoc of basic type MBGMCR01 and message type MBGMCR for the above requirement.
But I am unable to find how to configure the triggering of idoc MBGMCR during creation of confirmation in EBP.
If anybody has an idea of message control method in SRM or how is idoc MBGMCR gets triggered, please let me know.
Thanks in advance.

Hi Anuradha,
You would require to set up distribution model , tcode - BD64
SAP NetWeaver ->Application Server ->IDOC Interface / Application Link Enabling (ALE) -> Modeling and Implementing Business Processes ->Master Data Distribution ->Distribution Using Object Classes ->Model Distribution Using Classes.
Once the distribution model is set up you can assign the message type MBGMCR.
Hope this helps you.
Regards,
Ashish

Similar Messages

Configuration steps for Extended Classic Scenario

Hi All,
Could you please let me know what are the configuration steps required for extended classic scenario.
Thanks in advance

Hi,
Important Settings that Determine the Extended Classic Scenario
The following settings are required for the extended classic scenario:
u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
This is for your additional information.
Hope this helps.
Regards,
Vikas

SRM: Extended Classic scenario: Request your help.

Hi Guru's,
We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
in our project the SRM box is : G3OSBSR102.
R/3 backend Box is : RCHSBR3142.
Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
1) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
2) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
Many Thanks,
Prasad NN.

Dear Prasad,
To work on Extended Classic Scenario, you just have to maintain the following configuration in SPRO:
>SAP Supplier Relationship Management
>SRM Server
>Cross-Application Basic Settings
>Activate Extended Classic Scenario
Check the flag "Extended Classic Scenario Active".
You dont have to manipulate "BE_LOG_SYSTEM" field to choose your scenario.
Regards
Thiago Salvador

SRM Extended Classic Scenario

HI,
Please let me know in the extended classic scenario when the PO is created in SRM does the same PO number gets created in the backend system.Also is the PO created in the Backend system can be opened in transaction ME21N or it can be viewed only in ME22N transaction.
Thanks,
Manu

While configuring consultant has to maintain the same number range in both systems. This way the PO number created in SRM system remains the same as in backend ECC system.
This PO is only readable in backend system. Only ME23.. transactions can be used to view this. If user is allowed to modiify this PO in backend system it will lead to inconsistency between the systems.

STO in a SRM Extended classic Scenario

Hi All,
Although I have implemented STO process in a classic scenario, I have not implemented or not sure if possible in a Extended Classic Scenario. Please advise on how STO could be implemented in SRM 7.0 ECS scenario. Will award appropriately.
Regards
Rao.

Hi,
STO is not a supported PO type for classic or ECS.
Since you have managed to do with the classic earlier, the logic would be pretty similar in my opinion. Both will called to the BAPI_PO_CREATE1 eventually and i also believe you have made data adjustment in the SRM/ERP BADI before the classic PO data is used for the document creation.
Likewise for ECS PO, we have BADI for the ECS PO too. By adjusting the necessary data before document creation, you should achive the same end result.
However there is a major difference between classic and ECS PO - the latter cannot be edited in the ERP at all if that is a requirement which you have done in the earlier PO.
Regards.
YS

On Time Delivery Metric ( SRM Extended Classic Scenario)

Can anyone provide feedback on how you are measuring suppliers on time delivery performance based on SRM Extended classic POs. We are currently trying to use the Stat-Rel Date (SLFDT) in R3 to measure Original commitment date vs. Actual delivery date to get our OTD Metric However when we create an ECS PO with Reference to an R3 Requistion the SLFDT date is populated with the Requistion delivery date and not the delivery date on the Purchase Order.
R3 Version ECC 6.0 SP 12
SRM 5.0 SP 9
Thanks,
Erick Sick

Hi,
Have you defined your Log systems in both SRM and ECC? Have you assigned a client to the logical system? Are you sure that all RFC connections are working fine?
Regards,
Nikhil

SAP eSourcing with SRM Extended Classic Scenario

Hi Team,
We are using ECC 6.0 with eSourcing. Currently we use SRM 5.0 with Classic Scenario.
Now we are planning an upgrade from SRM 5.5 to SRM 7.0 and want to do the Extended Classic Scenario. This will help us to do additional functionalities of SRM.
eSourcing can be used for Strategic RFx and CLM functionalities.
SRM can be used for SC, Operational Sourcing and PO. We can also use the SRM-SUS Scenario for PO confirmation and Invoices.
Have any one used eSourcing with SRM Extended Classic? In that case, please provide some light into how to use all these application to better streamline the overall Source to Procure strategy.
Also, do you think Classic is the way to go or Extended Classic is better? Any documents or pictures are greatly appreciated.
Thanks
Jogy

Hi
SAP provide standard integration b/w ECC and Esourcing/ CLM (PR (both inbound and outbound). However in case you decide to go with extended classic scenario,you might need e Sourcing/ CLM integration with SRM (since PO would be created in SRM) which is not provided out of the box by SAP. However custom interface (based on flat file transfer) can be built b/w SAP SRM and e Sourcing.
MM-SUS scenario is not much different from EBP-SUS scenario in terms of functionality.
Regards
Mudit Saini

Tolerances in SRM extended classic scenario

Hi all,
I have a question regarding tolerances in extended classic scenario and I hope that somebody could help me.
We use extended classic scenario. The tolerance group is attached to TOG attribute in PPOMA_BBP, tolerance key is DQ.
We also tried to use tolerance key CF, but it seems as if CF is not applicable for GR?
However, whenever we try to confirm more than PO quantity, we get an error message. PO Ordered quantity exceeded by 1 EA
It seems so that SRM has a double tolerance check
one in SRM against defined tolerance (via attribute TOG)
one in R/3 against the PO tolerance
Now my question: Is this the expected behaviour or a bug? We do not want to maintain two tolerances. And furthermore most of the time we have POs without a material master. Are there any possibilities to skip the PO tolerance check?
Thanks for your help,
Martina
Edited by: Martina A. on Jan 15, 2008 1:13 PM

Hi
Depending on the SRM version you are using, Please go through the links, which will definitely help ->
Condition Type SRM - ECC
Tolerance in SRM and ECC (BE R/3)
Tolerance
Re: SC Budget check without SAP Fund Mgmt
TOG parameter and tolerance checks better understanding
Setting EKPO-UNTTO with BAPI_PO_Create
Re: SRM: many confirmation for PO
Please maintain the "TOG" attribute in PPOMABBP transaction in SRM.._
Do let me know.
Regards
- Atul

Extended Classic Scenario - how does the integration work ?

Hi,
Apologies for asking a basic question, but we are looking at requirements for integrating SRM with R/3 using the extended classic scenario and I need to understand how the integration actually works ? How is the data transferred between the 2 systems ? Does it use BADI's, idocs etc ?
Many thanks,
fiona

Hi Olaf,
I just wanted to give some precision on what you said (in the thread How to "see" PO in EBP ? also)
The Extended classic scenario only refers to the local PO creation replicated in R/3.
In this scenario, in the R/3 PO only the data not managed/sent from the SRM are available for modification (which depends on the SRM version you use)
The "PR transfer from R/3" is called "Plan driven procurement", and in this scenario only RFC is used, the qRFC are only used for BDocs of the CRM Middleware.
Regards.
Vadim

Extended Classic Scenario Pricing issue, can I over come by using SRM-MDM?.

Hi SRM GURU'S,
I am using ECC 6.0, SRM 5.5, SUS, LAC, cFolders and SRM-MDM with Extended Classic Scenario.
My Question is : In case of Extended classic scenario, there is issue with Pricing and conditions. Is there any possibility to overcome this issue by using SRM-MDM. Or do I have to go for IPC. My client has not brought IPC. I have to cover Pricing with the above components.
Anyone suggest me, how to proceed. Thanks in Advance. Awaiting for quick response.
Thanks & Regards,
John.

Hi Masa,
We can maintain Price and conditions as a record in CCM for Particular Material or Vendor. When you add that record to shopping cart it will update. I mean, If the provision is available in MDM, I don't want to use the Two components for same functionality.
If I use IPC, Is there separate license for that. What else need to be updated to use IPC (Patches etc).
If you have IPC configuration material, could you please share with me? How to bridge the SRM Conditions and ECC Conditions?
Please clearly give me details. I really appreciate you.
Regards,
John.

In an extended classic scenario, how can we make few purchase orders to sta

Hi All,
In an extended classic scenario, how can we make few purchase orders to stay local (i.e. without copying it to the back end). The decision criteria to stay local is information other than product category, i.e. using pcard and the cart value.
Thanks
Murali

Murali,
As I said usually this integration is done using ALE - IDOCs. You can find the all the configuration do be done here.
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
In this the filtering can be done at two levels.
1. Data Filtering
2. Segment Filtering
Data Filtering:
Data filtering can be done in dustribution model where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Look at BD64 where you can do the config for data filtering.
Regards,
Ravi
Note : Please mark the helpful answers

SRM EXTENDED CLASSIC - INVOICE QTY in Statistics Section of Item

SRM Gurus,
i require to select the Invoiced quantity of a PO , which is seen on the Statistic section of the item details of a Process Purchase Order SRM Screen. The Invoices are created in ECC and not in SRM . (Extended Classic Scenario)
Can any one let me know which table has this info or how i can get this in SRM System ?
WIll definitely assign points for answers. thank you.

Dear Prasad,
To work on Extended Classic Scenario, you just have to maintain the following configuration in SPRO:
>SAP Supplier Relationship Management
>SRM Server
>Cross-Application Basic Settings
>Activate Extended Classic Scenario
Check the flag "Extended Classic Scenario Active".
You dont have to manipulate "BE_LOG_SYSTEM" field to choose your scenario.
Regards
Thiago Salvador

PO text transfer to Back-end in case of Extended Classic Scenario in SRM 4.

Dear experts,
My system is in SRM 4.0 in Extended Classic Scenario. We use in the PO internal note text and vendor But thses texts are not transfered to Back-end.
Is it normal?
Do I need to customize something?
Can it be achieved by BADi? How then?
OR is it only possible from SRM 5.0?
Thanks in advance
RD

Yes you can do this. Implement BADI BBP_CREATE_BE_PO_NEW, Refer parameter IS_SC_DOCUMENT>LONGTEXT, and CS_PO_DOCUMENT>IT_PO_ITEM_TEXT. Map the exact text-id of the R/3.
Note: if this BADI is not present, use BBP_CREATE_PO_BACK
Regards, IA

Use of Purchase info records in SRM SC in Extended Classic scenario

Hi All,
We have implemented SRM 7.13 with Extended classic scenario. If we have Purchase info record in SAP ECC for the material, it gets populated in SRM SC in Source of supply Tab but the price of Purchase info record does not get updated in the SC line item.
Can anyone let me know which configurations is required to fetch the Purchase info record price or we need to have a customization to achieve this.
Thanks,
Ankur

HI Ankur
when you say the price did not get updated did you check the sequence which is used for price determination ?
1. User entry
2. Contracts
3. Info record
If still you think it is an issue please check the report EBP_GET_BACKEND_PRICES and let me know if your problem gets fixed?
Regards
Vinita

Attachment transfer of PO from SRM to Back end for extended classic scenario

Hi Experts,
We are using the SRM 7.0 with EHP 701 and ECC 6 , we have a SRM requirement where we need to transfer the attachment of a PO to back end ECC. I tried to implement the note 1594966 , but it doesn't work . we are using Extended classic scenario. Please suggest some SAP notes or the procedure to be followed to achieve this.
Thanks ,
Aishwarya.M

As far as I am aware this functionality of transferring attachment is not supported in Ext classic scneario
http://scn.sap.com/thread/1873708
Also I suggest you should debug and see if its sending attachment from SRM if yes then
could be something missing at ECC side , To debug use this
http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=340264144
You may also check in SXI_monitor and see if attachment is being recieved and sent from SRM and ECC respectively
Are you configuring this for the 1 st time or its an error which u encountered?
You must raise a NOte to SAP for the same till a solution is found .
This one is another which you can check ..
http://wiki.scn.sap.com/wiki/display/SRM/Transfering+shopping+cart+attachments+to+the+backend+system

How is Idoc MBGMCR triggered/Configured in SRM Extended classic scenario

Similar Messages

Maybe you are looking for