Classic Scenario in SRM 7.0

Hi,
I have a doubt. Please correct me if I am wrong:
- As per my knowledge, confirmation and invoice can be created either in SRM or ECC in SRM 5.0. However in the SRM 7.0
confirmation and invoice can not be created in SRM 7.0. It has to be create ECC.
- In plant drive procurement both confirmation and invoic has to create in ECC. It should not be create in SRM 7.0.
Thanks in advance.
BR,
Jennifer

Hi Jeniffer,
In SRM 7.0 also, you can continue to create confirmation and invoice in classic scenario against your shopping cart.
Plan driven procurement is not supported for direct materials in classic scenario. You have to use extended classic scenario i.e. in such cases PO, follow-up confirmation and invoicing can be done SRM as well.
Thanks and regards,
Ranjan

Similar Messages

SUS-MM integration in Classic Scenario for SRM

Hello All,
We are using SAP SRM in classic Scenario.
We also plan to integrate SUS with MM .
Looks like in the Classic Scenario with SRM , only the Direct material procurement is possible
using MM- SUS.
How would the SUS-MM integration work for Indirect PO's.
Our Process is as follows:
1) Shopping cart created in SRM for Indirect material & approved ( with cost assignment)
2) Classic PO created in backend & sent to SUS
After this step is it possible that the Vendor create the GR in SUS and it is sent to ECC for Approva through PI l??
Thanks
Kedar

KedarG wrote:
> Is it possible in Classic Scenario, to send the SUS confirmation to SRM instead and from there to ECC
NO. dont think of a situation like that. if it is classic scenario except SC every thing will in ECC. how do you think confirmation creation can be possible in SRM when PO is not present in SRM!!
> Can you provide some details on ECC workflows. I didn't find any thing on this. Does ECC even support workflows as SRM?
>
SRM is a kiddo infront of ECC, so workflows definitely are present in ECC(not BRFs but event driven wfs).
any ways, your solution would be a custom solution, implement MB_DOCUMENT_BADI, to trigger a custom WF from custom event. this can be used for notification and stuff. but it wont stop the execution, so, dig on it how to stop the GR post till the workflow is not over.
and invoice anyways has workflows which you can use

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

BBPSC18 - Request for external staff - Classic Scenario in SRM 5.0 possible

Hello Community,
one of my customers wants to use "Reqest for External Staff". As far as I remember, in SRM 5.0 it is only possible in "Standalone Scenario".
Is this assumption correct? So not possible in Classic Scenario?
How about "Extended Classic"? Probably not possible either, right?
Thanks for any help or input!
Cheers, Julian

Hi Rahul,
thanks for your answer!
Actually I am only looking into the part "Request for External Staff" - "Acceppt Bid" - "Create PO (Classic in ERP)".
I have seen that this part works in SRM 7.01.
But currently we are not planning to upgrade. We are still on 5.0.
I tested the abovementioned process in our DEV-System. I behaves fine, no error messages. But when I want to create the PO out of the "Check Status" (yes, in SRM 5.0 this was possible), the system pretends to create a PO but it never gets created. So I just wonder if I missed some customizing, or if this also only works in Standalone or if there maybe is a smart technical workaround (some custom coding etc...).
Cheers, Julian

Extended classic scenario in SRM 7.1

Hi colleagues,
we want top use SRM 7.1 with extended classic scenario and we want to create POs in SRM and reflect them in ERP backend. The question is it possible somehow to change those POs aftewards (e.q. add confirmations, transportation costs, etc...) in ERP? Or is there any way to trasnfer POs in hold status from SRM to ERP and then change them in ERP?
Thanks and regards, Anton

Hi Anton,
PO is created a in SRM as local and a copy( copy does not contain the entire PO info, only the useful for the backend) is being sent to R3.
DO NOT try to search a workaround for modification in the backend..sooner or later you will be incurring in incosisnten data and misalignmentes.
SRM is the PO golden source.
Thanks and Regards,
Abraham

Classic scenario using SRM SOCO

Dear Experts,
We use SRM7.0.
We want to use classic scenario u2013 creating backend PO and not SRM PO.
Can we use the SRM SOCO if we want to create backend PO ?
To clarify myself, can we implement this procurement process:
1. SRM SC
2. The SC will go to the SRM SOCO u2013 Sourcing cockpit
3. The purchaser will create backend PO from the SC items on the SOCO
Or in case we want backend PO, we must use ME57 on ECC system ?
Thanks and regards,
Lori

Hi Lori
It is possible to create a Purchase order in the backend from the SRM cockpit ( but it should not be order as Direct) by the Purchaser in the classic scenario.
Are you finding any difficulties ?
shopping cart create and ITS venture to cockpit upon sourcing configuration
add vendor and price in the shopping cart item or propose source of supply
and click PO creation and PO number will be generated from SRM system and PO will be avaiulable in ECC system .
BBP_CREATE_BE_PO_NEW - Purchase Order in Backend System
Using BusinessAdd-In BBP_CREATE_BE_PO_NEW you can change all the data thatis transferred to the backend system for generation of a purchase order. This includes, for example, the item data, the account assignment data, and texts.
All the shopping cart data is available as input parameters.
Ricardo / Lisa - please confirm the same when you read this thread and appreciate your comments here

P-card process available for SRM 5.0 extended classic scenario

Hello,
I didn't find the information, so I'm posting this message.
Is the p-card functionality available for the extended classic scenario in SRM 5.0 ?

Hi,
Use of Procurement Cards are supported in Extended calssic scenario from SRM 2007 ..onwards
HTH
Rajesh

SRM MM-SUS for Direct Material ( i.e. Ext Classic Scenario)

Hi Friends,
We are planning to have the Classic Scenario in SRM 7.0 with SUS. So it will be SUS-MM scenarion and it supports only for Classic Scenario,
But when there is a case of Direct Materials [ Manual or through PDP ( Ext Req) ], it is SAP by defaullt setting that , system determine Extended Classic Scenario.
Now , if SUS-MM supports only to Classic scenario ,then we can collaborate the Orders of Direct Material genereted through Ext Classic Scenario in SUS ?
Confused over these contrast . Can any one suggest that how to get both one in SUS-MM ?
Thank you in advance.

Hi Alex,
Thanks for reply.
It seems here is some confusion. PDP of Dircet Material is standard SRM secarion where we can soure the requieremnets generted in various SAP Module like PS, PM , SD, APO..etc. So We just hav eintenstion to source the requiermnet in Sourcing cockpit to create the PO .
Okay. For time being , forget the PDP of Direct Material.
Just take the Direct Material ( For which we mention inventory or we procure for stock) only.
By SAP standard / defualt setting , for Direct Material , local PO is generted ,althoug we have mentioned Classic Senrion setting for the same . And it is Extended Classic Scenarion. Right!
At another side , it is SAP standrad that SUS-MM senarion support for only CLASSIC SCENARIO.
Then , my conern is how we can send these Local orders for dircet Material to Supplier via SUS ? Wether it is not possible ?

PO output for Extended classic Scenario from the R/3 backend

Hi,
1) Does the PO output (ignoring the config maintained in SRM server 5.5 for the output) through R/3 backend is standard or it is mandatory to give local outputs from SRM only incase of Extended classic scenario?
Regards,
DV

Hi Anil,
We are working on extended classic scenario with SRM 5.0 & ECC6.0.
Please explain how we can take "PO output for Extended classic Scenario from the R/3 backend ".
Please send the related document to [email protected]
Thanks in advance
Ashutosh

Classic Scenario PO after Bidding of ECC Purchase Requisition - PR

Dear SRM experts
Is it possible to create bidding invitation for a ECC-MM-PR   and then create a Purchase Order for Winner Bid in Classic Scenario of SRM.
What configuration should be done for making Bid and then PO in SRM in classic scenario to process the MM PR.
Ahmed

Hello,
Transfer of ECC PReq for bidding & creation of ECC PO as follow on document is possible.
See the details - Business scenario - Plan driven procurement.
http://help.sap.com/saphelp_srm70/helpdata/EN/48/3003eb2c8a72d0e10000000a42189c/frameset.htm
Configuration need to be done on SRM as well as on R/3.
On ECC side:
a.Create a Profile: " V_T160PR"
   Profile + Syst Log of SRM
b. Create a Filter:"V_T160EX"
    Product Category + Purchasing Group + Profile
( PReq satisfying the Pcat & Pgrp combination will be transferred)
On SRM side:
You need to maintain a sperate Local Porg /Pgrp entry in the Org structure for trasnfer of PR's from R/3 to SRM.Under these Org/Grp ,you need to assign the RFC user and this user will be used to create the SC in SRM for the corresponding PR in R/3.
Then, you will run the program BBP_EXTREQ_TRANSFER in R/3 to transfer the PR to SRM sourcing cockpit. Using the requirement created in SRM, buyer can create a bid & as a further follow on document as Classic.
Hope this helps.
Thanks
Ashutosh

Status I1113 missing in SC in Extended classic scenario using TA BBP_POC

Hi all,
I am using SRM in extended classic scenario (ECS) (SRM Server 5.5) SP09.
1. Scenario (without any problems)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
No problems at all using standard Sourcing Cockpit -> POs are replicated to R/3, status correctly transfered into Shopping Carts (Status I1113 after creating a PO out of SC).
2. Scenario (problems concerning Status I1113 in SC)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
Shopping carts are manually transfered into a local PO by using standard transaction BBP_POC (create PO) -> function "Add shopping cart item" within item data
Local PO is created without any problem, sucessfully replicated to R/3 and if I start the Monitor for shopping carts I get all the detailed information (follow on documents) -> PO number etc.
Problem: If I use TA BBP_POC and add these shopping carts to PO positions, the status I1113 is not written to SC after executing BBP_GET_STATUS_2 and CLEAN_REQREQ_UP .
The SC remains in Status I1106 (Shopping Cart ordered) / I1129 (approved)
I cant find any entries in table BBP_DOCUMENT_TAB and the shopping carts have been removed from SoCo after creating a PO out of it...
Does anybody uses Transaction BBP_POC in ECS and adds Shopping Carts to POs?
Any Idea why the status for these SCs is just I1106 "Shopping Cart ordered" but status I1113 "Follow-on Document Created" is missing/not updated?
Best regards,
Andreas

Hi
<b>Please go through the SAP OSS Notes below -></b>
Note 1053433 Extended classic: Incorrect status shown in check status
Note 730239 Check status: Missing Backend reference
Note 819094 shopping cart monitor:Update status after resubmit shop.cart
Note 825761 Report program for shopp. cart status update after resubmit
Note 768164 Multiple SCs via SoCo are processed incorrectly
Note 729967 Shoppng cart:Status I1111,no follow-on docs->analysis report
Note 728536 Shopping cart: Follow-on docs => analysis-/correction report
Note 704941 EBP 3.0: Status error in SC extractor
Note 486246 Incorrect shopping carts offered for confirmation
<u>Do let me know.</u>
Regards
- Atul

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

Completion workflow in extended classic scenario

Hi gurus,
We use extended classic scenario with SRM Server 5.5.
In ppoma, each purch org and purch groups has the local and the backend. Vendors are replicated to backend purch org and then also to the local purch org.
I have seen that in classic scenario purchasers should be assigned to the local purch org. however, completion workflow only determine the agent (purchaser) if it is in the backend purch org.
The problem is that then this purchasers cannot manage any business partner.
How can I solve it?
I have seen other clients that the completion workflow determine the agents in the local purch org...
Many thanks!!!
Regards
Patrícia

Hi,
In the Extended classic scenario, local purchasing organisation and purchasing groups are required to create shopping carts and purchase orders. in this scenario, when
the vendors are replicated from the SAP back-end using BBPGETVD,BBPUPDVD program or vendor-synchronization programs, the vendor update in SRM is only for the R/3 purchasing organizations. because the local purchasing organisations are required in SRM for the Extended Classic or standalone scenario, these replicated vendors needs to be extended to the local purchasing organisations.
organizations can use Tx. BBP_UPDATE_PORG for extending the vendors to the local purchasing organiztion.
see OSS Note 390546 for more info.
Regards
vasanth

Sourcing in extended classic scenario

Hello, all
We are using the extended classic scenario in SRM 5.0.
In sourcing cockpit I have the following problem. In spro Supplier Relationship Management/SRM/Server/Sourcing/Define Sourcing for Product Categories I set Sourcing Always Carried Out. From a shopping cart the purchase order is created automatically as the data complete, but I'd like to sent shopping cart to the sourcing, where from a shopping cart create bid invitation or purchase order. How do it?
Please help,
Best regards,
Guzal

Hi Guzal,
As informed by Claudia, Incomplete mainly means no vendor assignment, no price etc.
If the vendor is assigned at the shopping cart level by means of a contract the shopping cart (details) is complete. Even in this case the SC should go to Sourcing cockpit in case of "Sourcing Always carried out" is chosen in the sourcing column.
In the above case the P.O gets directly created from SC only when the options
" Sourcing never carried out" & " Sourcing carried out for items w/o assigned source of supply" were chosen.
Hope you will be more clear on this issue. Any clarifications always welcome.
Rgds,
Teja

Why Extended Classic Scenario

Hello
I understand the difference between Extended Classic and Classic Scenario with the follow on document creation. But, I need to understand the business benifits of implementing Extended Classic Scenario as opposed to Classic Scenario in SRM. In what business scenario do one suggest Extended Classic.
Appreciate every answer
Thanks
Vijay

Hi Vijay,
The most important thing to consider when choosing the implementation scenario is to consider which system will support the different steps of the procurement process.
In case of the classic scenario, after creation of the request (shopping cart) in SRM, the remaining process steps will be handled / supported in the back-end system (ECC). Goods receipt can be executed in both systems. This would be a good choice if the organization has already an operational back-end system and the users from the purchasing department are already familiar (and happy) with all the MM functionality. SRM will only function as a support tool for administrating the purchasing needs of the end-users in the organization.
In case of the extended-classic implementation scenario the complete purchasing process will be supported in the SRM system (most organizations prefer to use the back-end system for invoice verification). Thus requesters, purchasers, goods recipients etc. all will use the SRM system to support their respective activities. This would be the preferred scenario in case both MM (ECC) and SRM are new to the organisation and will be implemented together.
SRM offers the different users a nicer user interface as opposed to the R/3 screens. Also the (strategic) sourcing capabilities of SRM can only be used when implementing the extended classic scenario. Same for the Suplier Enablement business scenariou2019s. Most are only supported when extended classic is active.
So depending on the intentions of the organization a choice can be made. SRM only as a tool for administrating the decentralized request from the end users in the organization: Classic scenario will suffice. SRM as a tool to support the complete purchasing process, from sourcing till evaluation - Extended classic will be the correct choice.
Regards,
Skander

Classic Scenario in SRM 7.0

Similar Messages

Maybe you are looking for