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

Similar Messages

SRM with PPS = Extended Classic Scenario

Does SRM Procurement for Public Sector (PPS) require Extended Classic Scenario? If so, could some one refer me to an official documentation that states such? Thanks.

http://wiki.sdn.sap.com/wiki/display/SRM/PPS-ProcurementforPublicSector-+enhancements
PPS is only possible by ECS only.
Muthu

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

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

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

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.

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

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

SRM Extended Classic with eSourcing

Hi Team,
We are using ECC 6.0 with eSourcing and SRM 5.0 with Classic Scenario.
Now we are planning an upgrade from SRM 5.0 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

Reservation with Extended classic scenario

Hi ;o)
I'm working at a costumer were we have extended classic scenario. We want to be able to make reservations in the backend if the item is on stock, and we have seen in a solution matrix from SAP that this should be possible.
The configuration for reservations should be done according to the guides - but no reservations is created when ordering a stock material.
I was searching on the developer network, and came across a topic, where it was stated that reservations could only be made with classic scenario (or using a BAdI where you switch the extended on and off depending on product category). Do any of you know if this is really a fact?
Thanks in advance
Maria Hvenegaard, Denmark

Hi
Read this first.
You can use BBP_CREATE_RES_BACK BADI using Se18 Transaction.
This BADI You can find in SPRO -> Supplier Rel. Mngmt. -> SRM Server -> Business Add-Ins -> Follow-on document generation -> Reservation in Backend System
If you want to create reservation, you have first to switch from ECS to classic scenario through BBP_EXTLOCALPO_BADI then you have to implement BBP_TARGET_OBJTYPE badi to determine the criteria to create a reservation in your backend.
We need to maintian the customising setings in SPRO Transaction.
Define objects in Back end systems. Maintain the document type EC or ECPO for Purchase Orders and not for creating reservations. Maintain number ranges (RS) and align the same to R/3 or backend systems. In setting up the org plan in the PPOMA_BBP Transaction, the attribute for resevation - Attribute BWA should be maintained too, if reservations are to be created in the backend system.
Movement Type Accounting Object
201 Cost Center
221 WBS-Element
231 Sales Order
241 Asset
Example :
logicalsystemname\201
Maintain the following Settings in the IMG using SPRO Transaction.
1.For internal Procurement > 1.Always Reservation for Material types Subjected to inv Mgmt
2.For External Procurement >1.Always purchase Requisition.
Note -> The plant that you use to create the shopping cart might not be extended to handle inventory management. Select a right plant which is extended to inventory management and you will see a reservation being created.
Be aware that:
- with the classic scenario you can create PR, PO and/or Reservations in R/3, but there is no local purchasing document (except the SC), so all functions around the local PO will not be possible.
- with the extended classic scenario, you can only create PO in the backend, but a local PO exists in SRM.
Concerning GR, it is possible to make it in SRM for both scenario
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Invoicing Plan functionality in Extended Classic scenario

Hi,
For PO's are created in SRM-Extended Classic scenario, kindly let me know on how to maitain Invoicing plans.
Thanks,
KB

Hi. You could use ERS.
Let's say you wanted an invoice plan to pay every month for 12 months, you could create a cart on an ERS vendor and order quantity 12, unit months.
Then every month the user could do a goods receipt for 1 month.
That would trigger an ERS invoice, just like an invoice plan would.
The only problem with this is that you are relying on the user to do the goods receipt.
Regards,
Dave.

Sharing attachment documents (e.g. for P.O.) in extended classic scenario

Dear SAP SRM gurus
in the SAP SRM extended classic scenarios (rel. 7.0) attachments of Purchase Order can be viewed also in the backend SAP ECC 6.0 as per SAP Notes n. 1582690 and 1057932 . But I am not sure if attachments are phiysically transmitted from SAP SRM to ECC or only document url is passed even though, as per SAP note n.1357551 it seems that only url is passed.
My customer wants to know if there is the possibility of not replicating them.
Any suggestions will be appreciated.
Many thanks in advance
Best regards
Gianluigi Brenna
Edited by: GIANLUIGI BRENNA on Jul 29, 2011 2:56 PM
Edited by: GIANLUIGI BRENNA on Jul 29, 2011 3:08 PM

Hello,
In extended classic scenario the attachments arent transferred to ECC as the source document is in SRM. The document in ECC is only a copy and it cant be modified also.
If we have to transfer attachments, then probably implicit enhancements to standard logic might be needed.
Regards,
Prasanna

SRM 7 : Vendor record replication in backend with Extended Classic Scenario

Hello,
We are implementing SRM 7 with Extended Classic Scenario and Supplier Self-registration.
Can you explain what is to be configured to get the new vendors replicated to the backend?
Thanks in advance.

Hi,
It is possible to transfer suppliers to ERP system, if you use 'Supplier registration with ERP' scenario. After registration and acceptance, newly registered suppliers would appear on supplier monitor from where you can transfer them to backend system.
Check the below link for more details:
http://help.sap.com/saphelp_srm50/helpdata/en/cf/35074152aff323e10000000a155106/frameset.htm
Regards,
Sanjeev

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

SAP eSourcing with SRM Extended Classic Scenario

Similar Messages

Maybe you are looking for