Extended Classic Scenarios Basic Queries

Dear SRM Experts,
I am working in the demo of extended classic scenario in SRM 7.0. I have some basic questions on it, Kindly reply for my doubts :
1. Do SRM-SUS Scenario applicable for all three procurements
     a. Self-Service Procurement
     b. Plan Driven Procurement
     c. Service Procurement.
or applicatbility only for Service Procurement .
2. Is it necessary to implement MM-SUS (Classic Scenario) first before implement of SRM-SUS? (Setting UP IDocs etc)
while i will only use XML Communication in XI(will select the Service_Procurement_Supplier_Enablement configuration scenario)
3. Is the configuration for Distribution Model and Partner Profiles necessary between SRM and SUS Communication in extended classic scenario?
Thanks.
Regards
Pawan

Hi Pawan,
Pl go through the following links for better understanding
difference between MM-SUS and SRM-SUS
SRM 7.0 SUS with ECS
Supplier Self Service (SRM-SUS)
Regards,
Nikhil

Similar Messages

Problem in Extended Classic Scenario related to PO

hi,
we are using Extended classic scenario in our client. User has created a SC .when we are going to create a PO system is showing an error Purchase Group B01 does not exist.
This Purchase group is not created in R3 or neither replicated to SRM.and it is not assigned in the Org structure.
Kindly Let me know from where the purchase Group might be Picked apart from the org Structure.
regards
subhash

Hi
Can you check your SC how this Purchase group picked form your basic data ?
since this purchase group is existing in srm thats why it picked while create sc right?
regards
Muthu

Freight is not updated in R/3 in the Extended Classic scenario

Friends,
Freight is not updated in R/3 in the Extended Classic scenario.
Once a PO is ordered, if a freight condition in SRM is applied, it does not get updated in R/3.
We have created a condition for Freight (Value and Percentage)in Create
Payment Conditions using the following menu path:
spro
--> Supplier Relationship Management
--> SRM Server
--> Cross-Application Basic Settings
--> Pricing
--> Process Payment Conditions
When creating a Purchase Order in SRM in the "Item Data" tab, there is
a"Pricing" option. Choose "Pricing" and select "Add Further Conditions"
from the drop down menu. Here Freight is available. Add Freight and
the PO record in SRM is updated with the Freight Condition. However,
upon ordering, the Freight condition does not transfer to the PO
recordin R/3.
We've heard this can be achieved by enhancement: only ie by implementing
set of BADIs.. But does anyone know WHICH BADIs we need? Or how we could find out? Thanks.

Hi
 You can either of these BADIs to handlwe the scenario.
BBP_CREATE_BE_PO_NEW Exit while creating a purchase order in the backend system
BBP_CREATE_PO_BACK OLD Exit while creating a PO in the backend system
BBP_ECS_PO_OUT_BADI ECS: PO Transfer to Logistics Backend
BBP_EXTLOCALPO_BADI Control Extended Classic Scenario
Hope this will help.
Please reward suitable points.
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

Extended Classic Scenario - SHC: Buffer table not up to date

Hello all,
I'm working in SRM_SERVER 550, SAPKIBKT11, and having issues using BACKEND PURCHASING ORGANISATIONS and the Extended Classic Scenario.
According to SAP note 944918 the following indicator should not be required to be set:
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario --> extended classic scenario active.
I did set the Backend Purch. Grps Responsible indicator, and I did create organizational units specifically for the backend purch. grps.
We need to set the main part of all SHCs to ECS, but when I do set the indicator in customizing to "extended classic scenario = active", I get a dump in my web environment: 'buffer table not up to date'.
What is causing this failure in my SHC?
I tried to implement BAdI "BBP_EXTLOCALPO_BADI" (method DETERMINE_EXTPO) like described below here: without the line bbp_extpo_gl-bbpexpo = 'X'., I can continue and create the SHCs. Problem is though: all SHCs will get marked as Classic Scenario. So, to make sure the SHCs will always get marked as ECS, I have added this line in the BAdI. Unfortunately this immediately results in the 'buffer table not up to date' error in the SHC itself, as soon as I try to open the details of the new item.
Hope you help me out here?? It doesn't seem to be related to the BAdI, but somehow the system doesn't allow me to mark SHC items as ECS.
Thanks & Regards,
Berend Oosterhoff
SRM Consultant Accenture Technology Solutions - The Netherlands.
BAdI BBP_EXTLOCALPO_BADI:
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
data definition----------------------------------------------------*
DATA:    wa_mattype     TYPE BAPIMATDOA,
           wa_char18      TYPE MATNR,
           attrib_tab     TYPE TABLE OF bbp_attributes,
           wa_attrib_tab TYPE bbp_attributes,
           wa_value       TYPE om_attrval,
           wa_product_id TYPE comt_product_id.
    bbp_extpo_gl-bbpexpo = 'X'.
from here I did the specific selection for the SC, but that's not relevant here.

Hi Prashant,
Thanks for your quick reply!
Note 1085700 is about Short Dumps when creating or changing a contract. I am trying to create a Shopping Cart, without a reference to a contract. BAdI BBP_DOC_CHANGE_BADI is not active in our system.
Any other thoughts?
Regards,
Berend

Organization structure in extended classic scenario

Hi All
I am trying to configure extended classic scenario on SAP SRM 7.0. I have made the following settings for the same:
1. In SPRO->SRM Server-> Technical Basic Settings -> Define backend system from product category, I have specified target system as SRM system and not ECD system
2. In SPRO->SRM Server->Cross Application Basic Settings-> Activate Extended Classic Scenario, I have selected all the options including "Back end purchasing group responsible"
I have a few doubts.
1. In organization Structure (PPOMA_BBP) Comapny code is corresponding to company code in back end but do I have to create local purchasing organization and local purchasing group i.e. in Functions-> Corresponds I'll have to leave blank. plz suggest
2. Also is IPC configuration mandatory for extended classic scenario
Plz give your suggestion on above mentioned issue
Regards
Pawan Keshwani
Edited by: pawankeshwani on Mar 18, 2011 8:33 AM

Hi Pawan,
No you should mention Purch Org & Purch Grp also wrt your backend (ECC).
IPC need not be configured separately from SRM 5.0 onwards. To ascertain if IPC is working fine just run the report : RSVMCRT_HEALTH_CHECK. You should see 4 success messages. Else get in touch with Basis to enable Virtual Machine Container (VMC)
Regards,
Nikhil

Extended classic scenario triggered on company code

Good morning,
I have a system with SRM 5.0. I would like to have both classic and extended classic scenario, I know that it is possible to activate extended classic only for a product category with BADI BBP_EXTLOCALPO_BADI , but my question is: Is it possible to activate it for a company code? If yes, is it with the same BADI ?
Thanks in advance
Charlotte

Hi
Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.
This is done via the customizing point "Activate ECS": just flag the check-box, and all you classic items (i.e. those for which a backend has been determined) become extended classic.
Here is the SRM - IMG path:
SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
You can then fine-tune the scenario by using the BADI BBP_EXTLOCALPO_BADI.
Note- The BADI BBP_EXTLOCAL_PO_BADI can be used to activate the classic scenario based on the proguct categories .
You can choose to have the 3 scenarios working on the same SRM system depending on product category (standard) or any other business rule through the BADI BBP_EXTLOCALPO_BADI. The BADI is mandatory if you want the Classic and the Extended Classic to work together
Exactly, this BADI allow you to implement your own business rule for backend determination in a multiple Backends environment (Standard customizing is only based on Product categories)
As soon as you use BADI BBP_EXTLOCALPO_BADI , you don't have to use the ECS scenario activation customizing point (the rule is overwritten with the BADI result). The BADI BBP_DETERMINE_LOGSYS will only help in your case, if you have several Backend where to create PO documents.
PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.
Other related links ->
Classic Scenanio and Extended Classic Scenario
Extended Classic vs Standalone
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Classic / Extended Classic Scenario for Shopping Cart
Re: Classic Scenanio and Extended Classic Scenario
Re: Switching from Classic to Extended Classic
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Change from ECS to Classic Scenario
Re: Changing the Global Control of Extended Classic Scenario
Re: Technical Scenario Switch: From Standalone To Extended Classic
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

PO status Held in extended classic scenario

Hello SRM gurus,
         I am very new to SRM with MM background. I have a question which i think you guys might have come across earlier.
We are using version 5.5 extended classic scenario, replicated all the vendors and materials from R/3 to SRM, did all the basic configuration needed, we are able to see those vendors and materials in SRM also. here is the issue. we are trying to add an item to the shopping cart which in turn creates a PO in SRM so that it automatically replicates in R/3. But the PO status in SRM is Held and we found out that vendor is not assigned to the PO which is very clear why the PO has been held. So what could be reason the vendor is not getting assigned to the PO though we have the inforecord and source list(checked the fix indicator also)for the same material and vendor in R/3 ?
I'm sure many of u would have come across this issue. please help me out.

Hi Satya
      Thanks for your quick response.
1) We are using Workflow without approval process
2) I checked BBP_NUM_SUSPO in SRM server. There is nothing in there. Is this the correct number range for PO? I checked OMH6 in R/3. please tell me how to sync it.
   When we try to post it after editing the PO with vendor number, we are getting Waiting for approval error though we have activated Without workflow approval process. let me know why is it showing that error?
We have another strange issue which is, We have assigned a material say M01 to a pur.group P01,Pur.org POrg1 and vendor V01 and have info record and source list, but we don't see this Pur.grp when we create the shopping cart and it defaults to some other pur.grp say AP01 which we deleted long back. can you tell me where it is picking up the deleted ones?
thanks
Pradheep.

Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
Please provide some help in solving this issue.

Hello,
This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC). And accepting the SES in ML81N will generate GR posting.
For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
So basically, for service items you create confirmation and for materials you create ASN.
Regards,
Prasanna

Convert classic in extended classic scenario

hai,
i wanted to convert classis scenario into extended classic scenario.what are all the steps that i needed to be follow.does it require any implementation of badi?how the po will be sent to the r3 in display mode?
could anyone give the solution
Edited by: chakradhar nannapaneni on May 11, 2009 12:45 PM

Hi,
1.     Activate the extended classic scenario
When the extended classic scenario is set, SRM generates a local purchase order for each item in the shopping cart. All follow-on documents are created in the backend system as well as locally in the SRM
2.     Activate IPC pricing
Since SRM 3.5 IPC (Internet Pricing Configurator) pricing is mandatory for extended classic implementations.
In the classic scenario you can replace the IPC by the simplified pricing
IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Cross-Application Basic Settings  Activate Extended Classic Scenario
IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Business Add-ins for SRM Pricing
Check whether the BAdIs relevant for the pricing are activated correctly and filled with the correct coding:
BAdI                                     I            PC Pricing (Extended)          Simplified Pricing (Classic)
BAdI: BBP_PRICEDATA_READ
Implementation:. BBP_PRODUCT_PRICE                     Not active         Active
*BAdI: PRODUCT_UPDATE2
Implementation. IPC_UPD_PROD_BUFFER2     Active         Not active
Regards,
Abraham

Question on Purchasing documents in extended classic scenario

Hi friends
How to create local purchasing documents i.e po,confirmations,invoice, in extended classic scenario
Please let me know the path
regards
venkat reddy

Hi Venkat,
The user interface and the process is same for local documents. However the result of document posting (either backend or local) depends on the setting in SPRO --> SRM --> Technical basic Settings --> Define backend system for product category.
Here you can define the target system as the system of document posting. If the terget system specified here is your SRM system, then it will create local documents in SRM.
Regards,
Prashant
Do reward points for helpful answers

Classic Scenario to Extended Classic Scenario

Hi friends,
   We have a requirement to migrate an existing SRM 5.0 solution from Classic to Extended Classic scenario.
   Is there any best practices document available from SAP in this regard? Also what are the things that need to be taken care of in particular? It would be great if some one can share his/her practical experience.
   Thanks in advance!
Best regards,
Pradip

Hello
If it is Plan driven procurement involved, better to go for 'Classic' scenario. Extended classic scenario is best suited for self service procurement of indirect material.(of course both scenario are best for indirect material!)
Now Switching over to Classic ti Extended classic:
1) Technical settings-->Define product categories for backend
    Here source sys is ERP backend and the Target sys is SRM client
2) Nu. ranges for Local P.Os
3) In Cross application basic settings, Activate extended Classing Scenario and Backend pur.grp responsible
4) In Define Objects in Backend system(Pur.req, Resrv, P.O)
    Ensure no entries are there. Since this step is not required for Extended classic
5) BAdi need to be activated.
Before all these, ensure there is no pending documents/transactions exists. All need to be closed. No open purchase documents!
The best guide for ref. is by Shah Khan.
Regards

Pricing in Extended Classic Scenario.

Dear SRM Experts,
System: SRM Server5.5.
Technical Scenario: Extended Classic Scenario.
I have done base line configuration in SRM server. IPC ia active.
[A]
What configuration need to be done for pricing i.e CALCULATION SCHEMA in Ext.Classic Scenario?
""" I have maintained Number Ranges """""""

Also what configguration needs to be done for IV?
"""I have maintained Number Ranges for local Invoices"""
[C]
How will accounting entries be made in R/3......do i need to maintain any attributes or any configuration?
I will reward points for all helpful answer.
Best Regards,
ANIL RAJPAL.

Hi Anil,
The majore part of pricing is in SD or CRM area right and for that they are using IPC, in SRM we are also using the IPC for the pricing which we need to pull from R/3 and used in SRM system.
For Configuring the IPC u need to config following settings.
1) IPC should be up and running.
2) Go in SPRO-> SRM server-> Cross Application Settings-> Pricing->Process Condition Types->Process Calculation Schema->Process Condition Groups->Check Technical and Customizing Settings for Conditions.
These are the basic setting u need to do for running IPC.
BR
Vijay Mittal
Please award the points if it solve ur query.

Multiple PO document types/transaction types in Extended Classic scenario

Hi All,
We are on SRM_SERVER 550, Extended Classic Scenario.
We have a requirement where we need to create multiple PO document types (based on certain criteria).
I have noticed that in standard, there are only 2 transaction types provided for SRM PO - ECPO and ECDP.
We need more document types and these should be triggerred automatically after SC is approved.
I understand that we need to maintain all the PO transaction types in SRM, number ranges in SRM then maintain the same transaction types as PO document types in R/3 and same number ranges in R/3.
I also understand that the change for document type needs to be done in BBP_DOC_CHANGE_BADI.
I have 2 specific questions:
1. We need to maintain attribute BSA for the users. Here we need to mention the document type and source system. What should be the source system mained in attribute BSA for ECS? Should it be the SRM system or R/3 system?
2. In BBP_DOC_CHANGE_BADI to change the PO document type/transaction type in ECS scenario, which field should be changed? Should it be ET_ITEM- BE_DOC_TYPE?
Regards,
Srivatsan

Srivatsan,
To create new transaction type:
Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Define Transaction Types
To create new number range:
Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Number Ranges --> SRM Server Number Ranges --> Define Number Range for Local Purchase Orders
You can define to create automatic PO when a SC was created in: Supplier Relationship Management --> SRM Server --> Sourcing --> Define Sourcing for Product Categories
Rgs,
Pedro Marques

Extended Classic Scenarios Basic Queries

Similar Messages

Maybe you are looking for