Extended Classic Scenario - Can Purchase Requsition be created in R/3?

Hi SRM Gurus,
In Extended Classic Scenario, Is it possible to have Purchase Req to be created in the backend?
Technically whether it is possible or not? Functionally, there is no such need, I agree.
Thanks & Regards,
Ramkumar

Hi
Please confirm what sceanrio in SRM are you planning for ?
I have not tried this. In Extended Classic Scenario, using BADI " BBP_TARGET_OBJTYPE" -> I guess, it's possible, but not sure. Try it out.
Purchase Order (PO) will be created in the R/3 system using the BADI - BBP_TARGET_OBJTYPE. Please read the standard documentation of this BADI, before implementing the same.
Regards
- Atul

Similar Messages

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

Extended classic scenario clarification

Hello
I have a question in case of a extended classic scenario.
Shopping cart is created by a employee and approved by a manager. But still no vendor exists in the shopping cart after approval. Now how the PO is created in SRM.
Note sourcing is activated, strategic and operational purchasers exits. How the process is implemented. Will the purchasers get informed via work items? Will they get shopping cart work items or incomplete PO work items.
Could any of you please give clarity on this.
Thanks in advance.

Hi
Once the shopping cart is created, based on sourcing config and also based on Purchase group responsibility the respective shopping cart flows in to the 'sourcing cockpit'(SOCO). Buyers/Purchasers will see all the open shopping carts and in SOCO there are multiple options available for purchasers to do. Such as creation of PO by just adding the vendor and right price/ creation of Bid or Auction or contract/ group the similiar requirements into one requirement create PO etc.
If the follow on document is chosen to be a PO or Contract then the shopping cart will go out of the SOCO once the PO/contract created. If at all the SC is considered for Bid/Auction process then the SC remains in SOCO till the Bid/Acution process is completed. Hope this helps
You can also look at SAP application help for SRM sourcing
http://help.sap.com/saphelp_srm702/helpdata/EN/d8/33ec56f17f4404806072749f7e764f/frameset.htm
Rgds/Kiran

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.

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.

GOA + Local Contract distribution to R/3 in Extended Classic Scenario

Dear SRM Gurus,
System Information: SRM Server 5.5 EBP5.5
Technical Scenario: Extended Classic Scenario.
Q1) We have created a Global Outline Agreement in EBP. We want this to be distributed to R/3.
But when we click on distribute, it does not get distriduted to R/3 ??? Is there any IDOC to be maintained----wich one ??
Please guide me as to how can we go ahead with this.
Best Regards,
ANIL RAJPAL.

Hi Anil,
The IDOC to be maintained is: BLAREL
For detail information you can visit the links.
http://help.sap.com/saphelp_srm50/helpdata/en/00/f5c93f4d903b1ce10000000a114084/content.htm
https://websmp104.sap-ag.de/~sapidb/011000358700002529571998/blarel02_d.htm
Also you can have look at notes:
643823
953269
671764
641919
Pls let me what all configuration you have done for GOA functionality so that I can suggest you something specific.
Best Regards,
Amit
Do reward the points if ans is helpful!!!

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

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

Error while creating Manual Service PO in Extended Classic Scenario

Hi Experts,
Extended Classic scenario (SRM 7.0 with ECC 6.0) While Creating Manual Service PO in SRM i am getting the below mentioned error messages. Can any one suggest what could be the problem.
Error Msgs:
1. Backend Error:In case of account assignment, please enter acc. assignment data for item
2. Backend Error:Purchase order still contains faulty items
Regards,
Mohan

Hi,
Yes i given all CC and GL information properly in Purchase Order Document for Service.. Still finding the error for Service PO alone.
Pl do the needful
Regards,
Mohan

Purchase Order Creation, Extended Classic Scenario

Can someone please explain the different databse tables affected during the creation of a Purchase Order.
Also, is there a transaction with which we can create PO in Extended classic scenario?

hi,
below are the tables effected while creation of PO:
CRMD_ORDERADM_H
CRMD_ORDERADM_I
BBP_PDIGP
BBP_PDBEI
BBP_PDISB
BBP_PDISS
BBP_PDSDLN
BBP_PDACC
BBP_PDTAX
BBP_PDATT
BBP_PDORG
BBP_PDWGT
BBP_PDDYN
BBP_PDEXR
PRCD_ITEM
PRCD_COND
PRCD_COND
BBP_PDDEP
CRMD_PARTNER
as far as your second question is concerned normally we will be creating a PO in SRM/EBP in web browser and it will replicate to the backend ERP.
regards
IGA

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

Extended Classic Scenario not creating backend PO

Hi All
We are just starting with SRM (Using SRM 5.0 SRM Server 5.5) and trying to decide to use Classic or Extended Classic.
I can get the Classic working were an approved SC creates a backend PO without any problem. However when I switch on Extended Classic the backend PO is not created from an apporved SC.
In RZ20 my error is Shopping cart 1000000080 (PReq. ): BBP_BD 002 Buffer table not up to date and Table BBP_DOCUMENT_TAB is empty
In config I activated the extended classic scenario as well as activating the backend purchasing groups as responsible. Under sourcing I also defined for the relevant product categories as "1 - Sourcing Never Carried out"
Am I missing something obvious??
Many thanks for any help.
Daniel

Hi Daniel,
In reference to the info. you have provided, it looks like you have not switched to Extended Classic Scenario properly.
Once you say you are on ECS, the P.O should get created in SRM and the copy of it should get replicated to R/3.
As you said you have flagged both the check boxes in SPRO for ECS activation, try activating sourcing also.
SPRO > IMG > SRM > SRM Server > Sourcing > Choose one Product category for which you want to create shopping cart and set the setting as " Sourcing Always carried out".
Check whether the approved shopping cart is coming to Sourcing cockpit or not.And from there try to create a P.O by assigning vendor.
Also ensure that no BADI is activated which converts ECS to Classic scenario for the Product category you have choosen.
If this cycle woks then definitely what you require will also work.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Extended Classic: Only local Purchase Order Creating

We are using SRM 7.0 SP5 extended classic scenario. The local purchase order is creating but the ERP PO is not creating. There are no errors in RZ20, ST22 or SLG1.
I can't even tell if it is trying to create a backend document. I set a break in the CREATE_DOCUMENT method where the BAP_PO_CREATE1 FM is called but the break never gets hit.

Azad,
Thanks for your answer. I did not realize that in exteneded classic the local PO is created first and that the backend po only gets created once PO has been sent out.
For anyone else having this problem this is what I found:
When I edit the local PO and order the PO after fixing an output problem, (PO is setup for no approval) , I was then able to see the backend errors appear on the PO infoming me of what when wrong when the sytem attempted to create the ERP PO.
Also, you can debug from program B46B_DPO_TRANSFER...set a break on line 393, just before the BBP_PO_INBOUND function module is called. Also that function module in the ERP system calls the BBP_PO_CREATE1 BAPI.
All this information has helped me answer my question....thanks for everyones help!
Edited by: Paul Trauth on Jan 27, 2010 5:24 PM

Can we use the Extended Classic Scenario with MM-SUS

HI, expert :
    In extended classic scenario ,the PO created in SRM system ,and then replicated into the MM system .You can't change it in MM system .
    So, in this situation ,I want to know the MM-SUS can be suitable or not ?The PO can transfer from ECC to SUS ?
   If I use the decoupled scenario ,which one I can select ?MM-SUS or EBP -sus ?
   BR !
Alex!

Hi Alex,
as noted by Bill, in MM-SUS is the extended classic not possible at all.
By default it's also not supported in the SRM-SUS. Please see the note 543544. If you would like to activate this, you need to pay a consulting fee for SAP:
"Please note that the full scenario can be enabled by a consulting solution, compare OSS note 700350."
Regards,
Peter

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

Extended Classic Scenario - Can Purchase Requsition be created in R/3?

Similar Messages

Maybe you are looking for