What is external classic scenario?

Gurus,
What is external classic scenario? Is this the other name for Plan driven procurement OR something else? Please clarify
Thanks,
Sid

Hi Siddarth,
This scenario is an extension of the classic scenario. Whereas in the classic scenario, goods and services are processed in the backend system, in the extended classic scenario, the procurement process takes place locally in SAP Enterprise Buyer and a copy of the data is replicated to the backend system. Communication between Enterprise Buyer and the backend system is via RFC. The purchase order is created locally in Enterprise Buyer.
If the data in the shopping cart is insufficient to generate a complete purchase order, you can supplement the data manually in SAP Enterprise Buyer before it is transferred to the backend system. The purchase order in SAP Enterprise Buyer is the leading purchase order. From SAP Enterprise Buyer Release 4.0 with an SAP backend system Release 4.6, the complete purchase order is replicated to the backend. It is a read-only copy and supplies the reference needed for the creation of goods receipts, service entry sheets, and invoices in the backend system. The plant is the criterion used for splitting shopping cart items into different purchase orders. This is because the purchasing organization is determined in the backend system based on he basis of the plant. Goods receipts (confirmations) and invoices can be pre-entered in Enterprise Buyer.
The following takes place in the Enterprise Buyer system:
Search for scource of supply, pricing, tax determination, commitments are updated in the backend system, account assignment and budget check are performed against the backend system.
Data for the Business Information Warehouse is updated partly from Enterprise Buyer and partly from the backend system: Purchase order data is updated from Enterprise Buyer, goods receipt and invoice data is updated from the backend system.
This scenario suits customers:
     Who want their purchasing department to save time and money by using the streamlined purchasing functionality of SAP Enterprise Buyer
     Who want to use the full sourcing capabilities SAP Enterprise Buyer offers, yet who also want to be able to confirm and invoice direct materials
     Who want the flexibility of being able to pre-enter confirmations and invoices in SAP Enterprise Buyer
The extended classic scenario does not support purchase orders based on limit shopping carts or procurement card functions, as these require the invoice to be local.
Hope this helps you.
Please Reward Points if useful..
Regards,
Sreenivas

Similar Messages

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

External requirements and Classical scenario

Hi experts
Is there some restriction concerning the use of external requirements in Classical scenario?
Is there some some sap note about it?
Thanks
Nilson

Hi Nilson,
Pls refer Note 505030 - Restrictions for the integration of external requirements.
Regards,
Prashant
Do reward points for helpful answers

External requirement handling in SRM using classic scenario

Hi Experts,
We have a requirement in Classic scenario:
PRs for MRO / indirect materials generated in PM / PS of ERP will be transferred to SRM using WF interface for approval process.
Upon final approval in SRM, Follow-on document PO should be created in the back end.
The SC in SRM should have the status u201CApprovedu201D & u2018Follow-on Documentu2019 created.
My question is SRM standard will create a PO as follow-on doc after the SC is approved in SRM. How to control this creation of PO in SRM & only approval message should be transferred to back end ERP.
Pls provide any suggestions or inputs on technical settings / adjustments to be carried out.
Note that we cannot use PDP scenario as SRM will be used only for SC approval process.
Tks.

Thanks Muthu for the reply.
The doc flow in the link above shows that after SC is approved, it will be available in sourcing cockpit for further processing (i.e. RFX, PO etc) in SRM. Our requirement should not be allowed to create PO in SRM and it should be allowed only in back end ECC.
SRM is used to centralize the approval process where multiple back end systems are connected. (How ever, in future follow-on docs are also created in SRM).
Current Target steps:
1. Create PR from PM/PS in ECC (PR status will be "In release").
2. Transfer PR to SRM and SC will be created (SC status will be "In approval").
3. SC will be Approved / or Rejected in SRM. (PR status will be updated to Approved / or Rejected in ECC).
4. If approved, follow-on doc PO (manual or automatic) will be created in ECC. (SC status will be updated to EX: "PO cretaed")
When the SC is in the process of approval, user in ECC may add new items or make changes to PR from PM/PS. After these changes, the current approval WF for SC in SRM should be cancelled and new SC is created and so on...
Sophisticated message synchronization is required between ECC & SRM.
Is it possible to acheave the above solution (create PO only in back end system) using the steps mentioned in doc "5082a622-7310-2c10-1a9b-ef31dd69a770.pdf" with some modifications.
Forgot to mention the following system details:
ERP - ECC with EhP4
SRM - SRM 7.0
Thanks,

Classic / Extended Classic Scenario for Shopping Cart

Dear Friends,
We are working on two different business scenarios with same Product type, Product and Product Category where we would like to control Extended Classic Scenario.
1. Self Service procurement to be executed in Classic Scenario as the follow-on document (Purchase Requisition) should be created in backed ECC system.
2. Plan Driven Procurement cycle where External requirement is transferred from backend ECC to SRM keeping Extended Classic scenario active so that system creates Shopping cart in SRM.
So which condition should I use to control the Classic / Extended Classic Scenario in BADI BBP_EXTLOCALPO_BADI method DETERMINE_EXTPO.
Regards,
Sandeep Parab

Thanks Pierre,
My Sourcing requirement is working as desired with following code in BADI BBP_SRC_DETERMINE (method DETERMINE_SOURCING).
method IF_EX_BBP_SRC_DETERMINE~DETERMINE_SOURCING.
DATA: w_header TYPE BBP_PDS_SC_HEADER_D.
CALL FUNCTION 'BBP_PD_SC_GETDETAIL'
EXPORTING
    I_GUID = HEADER_BBP_GUID
IMPORTING
    E_HEADER = w_header .
IF sy-subrc = 0.
IF w_header-subtype = 'ER'.
    SOURCING = 'X'.
ELSE.
    SOURCING = ' '.
ENDIF.
ENDIF.
endmethod.
However Im not able to control the Classic and Extended Classic Scenario even after introducing field EXT_DEMID in structure BBPS_EXTPO_BADI in badi BBP_EXTLOCALPO_BADI and method DETERMINE_EXTPO.
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
IF ITEM_DATA-EXT_DEMID = ' '.
BBP_EXTPO_GL = ' '.   for classic
ELSE.
BBP_EXTPO_GL = 'X'.   for extended classic
ENDIF.
endmethod.
No idea y this is not working to my knowledge it should work
What do you think ? this this code and badi actiation im not able to perform SSP in classic mode and sourcing with extended classic mode.
Regards,
Sandeep Parab.

Use the MM-SUS in Extended Classic Scenario

HI,my experts :
    The standard function doesn't support the MM-SUS in Extended Classic Scenario .Now I may have two questions about it .
1、 I have one ECC system .I need handle the invice in the ECC system .In other word ,the invoice rcreated in the SUS should transfer to the MM system .But in EBP-SUS ,the invoice is transfered to the SRM system .What can I do now ?
2、 If I want to use the decoupled scenario ,some POs are create in EBP ,and others are created in MM .Now ,which sus I should select ? EBP-SUS or MM-SUS?
   Or some detail document about it .
BR!
   Alex!
Edited by: Alex on May 25, 2010 9:17 AM

Khan has explained most of the things.
The external web service I meant is actually OPI catalog which you need to maintain.
The same has to be entered in the attribute CAT of the EBP purchaser.
To maintain the call structure of this catalog
Get the URL from SE80->BSP appln->ros_prescreen->controller->main.do
then give the client no of yr ROS client
the RFC user user ID from EBP to ROS
it's password
sap-sessioncmd=open
sap-language=sy-langu
the operational purchaser role in EBP (sap_EC_BBP_OP_PURCHASER) should be linked with
the same in ROS via role menu->business partner->screen supplier->right click->change details
->sap-client=ROS client no
The administrator & op purchaser should be present in ROS org structure also
& should have same userID & password as EBP
you have to define the vendor root, the root of the purchasing organization and the currency in
table BBP_MARKETP_INFO in the SRM System (Enterprise Buyer client).
BR
Dinesh

Classic Scenario : Purchase Order failing to get created

Hi,
We are using SRM 5.0 classic scenario. We are only using SRM for classic scenario only. while trying to create the backend purchase order i get the following error "       Interval of number range object REQREQ does not exist: SC no. PO "
I have defined the number ranges for PO
Define Number Ranges for Shopping Carts and Follow-on Document
EC     3000000000     3009999999     3000000019   internal
Define transaction type : BUS2201 doc type ECPO
Description          Purchase Order
Int. Number Range         EC
Ext. Number Range         02
Status Profile
BTrans.Category      BUS2201
Description          Purchase Order
Partner Determ.Proc.
Text Schema          PO
Event Schema
In R/3
I copied NB transaction type into ECPO
Defined external number ranges
Thanks
Lebo

Hi
As Jagadish said,
1. In SPRO what is the number range you defined for PO in "Define Num range per Backend System for Follow-on doc".
bp - 10000 19999
lp - 20000 29999
for eg bp -is backend purchase order no ranage
         lp - is local purchase order no ranage
2. Then make sure above number range is maintained in "Define Num range per Shopping Cart and Follow-on doc" and it should be Internal num range.
            bacclnt100(backend logical syatem)    bp pr rs
              bp -backend po no range
              pr - purchase requst
              rs -reservation
3. this for r/3 classic po i.e bp
Description Purchase Order
Int. Number Range : BP
Ext. Number Range
Status Profile
BTrans.Category BUS2201
Description Purchase Order
Partner Determ.Proc.
Text Schema PO
Event Schema
4. define number range for local purchase orders
Description Purchase Order
Int. Number Range LP
Ext. Number Range 03
Status Profile
BTrans.Category BUS2201
Description Purchase Order
Partner Determ.Proc.
Text Schema PO
Event Schema
adding to Jagadish
since you are in classic scenario
a) one po number ranage for backend PO
b) another po number ranage for local PO - Why this is required means if it is ordered a direct local PO will be created SRM rather than R/3 system. this PO document type also must be mapped in r/3.
c) backend PO number ranage configuaration you can map in backend as external.
regards
muthu
Edited by: Muthuraman Govindasamy on Jun 4, 2009 10:33 AM

Extended classic scenario - no backend PO created

I try to activate the extended classic scenario. It's not activated in customizing, tried to do it only with BADI implementation for special material groups. We are able to create POs in SRM but transfer to backend doesn't work.
I get following error messages in application monitor as backend application errors:
No instance of object type PurchaseOrder has been created. External reference:
PO header data still faulty
Document number 100000093 not within defined inter val
What's going wrong here?
Hubert

Hello,
Check if you have set up the customizing as below:
Extended classic scenario:
a) at SRM side:
- To assign the transaction type to the extended classic scenario you have to maintain the transaction type name (= the R/3 PO document type) to the attribute DP_PROC_TY (in contradiction to BSA in classic scenario) in PPOMA_BBP of the responsible Purchazing group.
- Create a number range for a local PO.
- Assign the local PO number range as a internal numer range to the transaction type.
b) at R/3 side:
- Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range (trx. OMH6 Number Range for Purchasing Documents)
- Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range for POs as "NoRge Ext" (field V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)
- Make sure that the SRM and R/3 number ranges match are exactly the same.
Kind regards,
Ricardo

How to choose diffetent PO types in R/3 from a SC in Classic Scenario

Hello everyone,
I am working with SRM 5.0 in a classic scenario and I have a problem. I create a SC, then it is sent to sourcing cockpit where I assign it a vendor to create a PO, but I can't choose what kind of PO I want to create.
In PPOMA_BB, the user has at least 2 different PO's in attribute BSA and attribute DP_PROC_TY. When I create a PO from a Bid invitation I can choose this kind of POs.
Do you know how to choose different POs type from SC??
Thanks,
Ivá

Hi,
For backend products,In standard you can not choose what PO you want. By default the backend document type 'EC' is chosen. In number ranges for SC followon documents the interval number 'PO' would correspond to backend EC document external interval number. This is the standard behaviour though you might have maintained BSA attribute with other values in addition to EC.
For local products you can choose the PO transaction type. After youclick on create purchase order, in the next screen you will get an option choose your transaction type, provided you have maintained these in PPOMA_BBP for BSA attribute.
Hope this clarifies.
Rgds,
RRK

Classic Scenario PO not creating, only PR

Hi,
I'm using SRM 5.0, in classic scenario to R/3 4.6C. My Shopping Carts to R/3 are complete, but is not creating a PO. It creates a PR. If i run, ME57, assign and process, PR is already assigned a Fixed vendor, and PO is created without any further data being added. (Vendor, price, etc)
I'm confident my number ranges and Doc Type settings are correct.
In SRM customising, my 'Define Objects in BE Sys, has vaild P.Group, Cat Id, R/3 Source sys, Always external and PO if item data complete'.
When I trace RFC, RSRFCTRC, it is calling BAPI_REQUISITION_CREATE. Not BAPI_PO_CREATE1. Vendor master, set to auto create PO, not using material masters. Mat group and Vendor replicated from R/3 to SRM. Tax is calculated in R/3.
Any help appreciated. Is there a FM in SRM to test why its not creating a PO?
regards Adam

Hi
Couple of reasons might be possible ->
1) Try de-activating all the Custom BADI Implementations using SE19 Transaction (name starting with Y or Z) in SRM System for the time being, and then try out again.
Seems to be some BADI - BBP_TARGET_OBJECTS
BBP_TARGET_OBJTYPE might be over-riding the back-end documents creation.
2) Incase above step, does not help, Try creating a PO or PR directly into R/3 system (using ME21N or ME51N Transactions with the Document typeused in SRM), with the same data that is passed in the RFC call (you traced earlier) then see, what is happening in that case ?
Do let me know.
Regards
- Atul

Reference to SC in classic Scenario

Dear SAP gurus,
We're planning to install SRM 7 EHP 2 with backend ECC 6 EHP 5. We plan to use classic scenario, as we know that now, classic scenario already support Sourcing Cockpit and creation of RFx/Auction referring to SC.
However we want to clarify somethings. As I know, the control for classic scenario can be set to 2 things:
a. If stock available create reservation,
b. If external, create PR if no source found.
So let's say that in classic scenario, I create SC with non-stock item. Once it is approved, does it create PR in backend? Or it is not creating PR in backend, rather it sticks in SRM and go to sourcing.
Then in sourcing, let's say I decide to create RFx, and as result, I create PO from RFx response. As it is in classic, the PO will be created directly in backend. In backend, what will be the value in PR field? Is it going to show the SC number? The PR number? (assuming that once approved, SC will create PR in backend as well) OR the PO will NOT have any reference to the SC at all?
Appreciate if someone can shed some light of system behaviour in this case.
Best regards,
John

Hi
So let's say that in classic scenario, I create SC with non-stock item. Once it is approved, does it create PR in backend? Or it is not creating PR in backend, rather it sticks in SRM and go to sourcing.
Ans: In classic scenario for a non stock item if the source is not there,after the SC is approved it will create PR
in the backend.
In Extended classic sceanario(ECS) if the Sc is not having source once the SC is approved it will go to Sourcing cockpit
(or) you can see in Purchaser worklist
Then in sourcing, let's say I decide to create RFx, and as result, I create PO from RFx response. As it is in classic, the PO will be created directly in backend.
Ans : In ECS if you creating Rfx to PO in the tracking tab you can see the SC.
In backend, what will be the value in PR field? Is it going to show the SC number? The PR number? (assuming that once approved, SC will create PR in backend as well) OR the PO will NOT have any reference to the SC at all?
This is not clear
G.Ganesh Kumar

Direct materials in classic scenario - any restriction in backend?

Dear SAP gurus,
I have read that when we use classic scenario, procurement for direct materials actually using extended classic. But as per SRM 7 EHP 2 the true classic PO (leading PO in ECC) now possible.
I just want to confirm is there any restriction in the backend side? E.g what is the minimum version of ECC that we should use for this scenario?
One more thing, I assume that in classic scenario we can have SC or external requirement goes to Sourcing Cockpit, and then we can proceed to create RFx or Auction from here rite? From here, I assume we can create PO from the response and it will create directly in ECC. is this correct?
Best regards,
John

Hi Ramki,
thanks for the confirmation. one more thing, can we setup different po type in classic scenario when we're creating po from rfx response? as i understand we can only setup one number range for po backend in srm config, so what should i do if i want to specify that user can chose the po type that they want to create in backend as a follow on from rfx response?
best regards,
john

Classic scenario: po is not created

hai ,
i am using classic scenario.In define backend objects configuration i made the following settings
product category purchasing group internal procurement external procurement
555 555 always external proc create po if data is complete
when i created shopping cart it always creates purchase requisition in the back end.i have checked in shopping cart.delivery date,price ,quantity,account section,and source of supply .everthing is fine but in the backend pr is created instead of purchase order .how can i find out the solution.can anyone suggest me regarding the above problem
thanks and regards
chakradhar

(1)there can be several reasons for creating PR instead of PO. Please see the FAQ note 1173815 for the possible reasons, and the guide for debugging under:
https://wiki.sdn.sap.com/wiki/display/SRM/Howtoanalyzethefollow-ondocumentdetermination
(From peter thread copied)
(2)BBP_TARGET_OBJECTS BADi active in your system?
(3) Do you have fixed source of supply in your sc ?
555 555 always external proc create po if data is complete ? what is this 555 555
do you given corrrect material group / purcase group correcly...
regards
muthu

Contracts in Classic Scenario

In Classic Scenario SRM 5.0 with ECC 6.0, how can I create an ECC Contract with a requirement from the Purchaser's Worklist ? Do I use the Global Outline Agreement? If so, what are the config steps ? Full points assured. Thx.
Raja

Hi You can create a GOA in SRM and distribute a contracts in Backend .
Basic configuration
(1) Define a transaction type GCTR
(2) No range internally in EBP and Externally in R/3,
(3) Idoc settings sending to r/3 like BLAORD, COND_A
(4) You must have a role to create a GOA as SAP_BBP_STAL_STRAT_PUR-
CHASER.
(5) You may need to map all condition type in SRM and R/3.
(6) Refer this notes 646903 - Global outline agreement: Tips and tricks
You can refer some related links...
http://help.sap.com/saphelp_srm50/helpdata/en/42/f93dfd975f3ee6e10000000a1553f7/frameset.htm
http://help.sap.com/saphelp_srm30/helpdata/en/7d/0a093f7c392e5ae10000000a114084/content.htm
Re: SRM GOA [BLAREL ]
regards
Muthu

SRM 7.0 Unable to create PO - Classic Scenario.

Hello,
We are able to successfully create the below scenario.
PR in ECC --> Get PR in SRM --> Start Collective processing -> Transfer to Central System (SC is created for the PR @ this time) --> Create RFx --> Rfx Response --> Create PO. (PO is created in ERP, Classic Scenario)
We are able to get the PR & we are able to create SC successfully and the PR/ SC is available in Sourcing cocpit.
Able to create RFx --> Rfx Response.
Now once the RFx Response is Accepted --> We go for creating PO.
Classic Scenario.
The error is due to pricing - debugged and checked as mentioned in my earlier message.
IPC pricing is switched off and the BADI for simple pricing is activated.
Error : " Message A BBP_PD 396 cannot be processed in plugin mode HTTP "
But this is due to pricing is what i guess.
Error is raised in FM "BBP_PDPRC_UPDATE".
Kindly Suggest.
Unable to Create PO
Regards.
Edited by: Purshothaman P on Jul 6, 2010 1:50 PM

Hi,
Please check and run the following reports (se38): BBP_CND_CUSTOMIZING_CHECK & RSVMCRT_HEALTH_CHECK and post back the results.
Note for BBP_CND_CUSTOMIZING_CHECK also run 'Simulation of Pricing with Manual Price' (scroll down after executing the report initially).
Also the badi information you activated tells us a lot. Although i take it that you executed and read everything that's included in the transaction information. The following sentence gives a prety doubtfull feeling for the CPPR scenario to work for your configuration:
SAP recommends using this BAdI only in exceptional cases and only after checking thoroughly if it is compatible with the Business Scenarios used.
Note: From what i've just read IPC has to be disabled, certain badi's etc. need to be disabled. And VMC (sap basis) has to be configured. Please view: [http://help.sap.com/SCENARIOS_BUS2008/helpdata/EN/9C/F90B7CB34A4889935D1733C6756D5B/content.htm]
Could you also please check and provide whether 'normal' SRM classic scenarios like: SC -> PO do run within your system. Also the error and information you have provided is very little.
Kind regards,
Tim

What is external classic scenario?

Similar Messages

Maybe you are looking for