Manage direct procurement in classic scenario

Hi Experts,
We are on SRM 701
Classic Scenario
can anyone let me know how we can manage direct procurement in classic scenario?
i want to kept goods in storage location and i cant do that because of account assignment tap in SC and as i know account assignment is mandatory to create a Sc
Regards
Elham

Hello Elham,
As suggested Account Assignment should always be used and one cannot skip it for creating the Shopping Cart. If you are having Classic Scenario then your PO would be in backend system directly which you can manage through dummy account assignment as guided you in your previous post. Just get in touch with your Finance Team and ask them to make a Dummy Profit Center/Cost Center which you can use while creating SC for your local Storage
Thanks
Gaurav Gautam

Similar Messages

Direct Procurement in Classic Scenario

Hi Experts,
We are on SRM 7 Ehp1, ECC 6 Ehp4.
Classic Scenario.
1. I have read in the forums , that in Classic Scenario, direct procurement is possible but the system behaves like Extended Classic and creates a Local PO. Just want to confirm this and if yes , does this happen as a standard or do we need to implement any BADI or anything to achieve this.
2. Also , in Classic Scenario, PDP scenario , can we transfer stock items(Direct Materials) PR's into SRM system or are there any limitations.
Thanks
Aditya

Hi Aditya,
You are right. Classic system behaves as extended classic for Direct procurement scenario. Your PO will be created in SRM itself and a copy of this will be sent to ECC. This happens as a standard and no BADIs need to be implemented for this.
Also in your classic system, you can transfer stock PRs into SRM. These will be available as shopping carts in the sourcing cockpit.
Regards,
Nikhil

Plan Driven Procurement in Classic scenario

Dear SAP gurus,
We are in SRM 7 EHP 1 with backend ECC 6 EHP 5. We are considering to use classic scenario, but we want to make sure that all the components are working fine. We have a scenario where MRP will be used in backend thus crearting a PR. We know that we can then push the PR to become SC in SRM then it can be processed there.
However seein note 505030 point 15, it seems that you cannot procure direct material using classic scenario. I assume that if using classic scenario, the PR of stock materials just wont go to SRM. However in other places I read that actually stock material works for classic scenario, but the PO will automatically switch to extended classic.
So which one is correct? Is:
1. For PDP and in classic environment, PR stock material NOT able to go to SRM, OR
2. For PDP and in classic environment, PR stock material can go to SRM, but when it is converted to PO it switch to extended classic.
Best regards,
John

Hi John,
The second option works in SRM.
Direct procurement in classic scenario works as if the system were extended classic. Thus your PO will be created in SRM and a copy of it will be replicated to ECC.
Regards,
Nikhil

Direct procurement in Classic

Experts,
Need your help once again.
I have implemented direct procurement in Classic scenario (SRM 7/ECC 6.0) and after reading on this forum, I realised that Direct procurement in classic, functions as extended classic because a local PO is created in SRM and this is replicated to ECC. So far this is working for me.
Now I want to make changes to this PO. It is not allowing me to edit PO in ECC which is right because PO was created in SRM and copied to ECC. But strangely, I am unable to edit PO in SRM also?
Is this correct behaviour?
Please suggest.
Best Regards,
John

Hi John,
For direct procurement, it will have nothing to do with CS or ECS.
SRM will create the local PO for direct material and transfer the PO into ERP. And you could not change the PO in ERP.
Regards,
Guoyu

Self service procurement and plan driven procurement in classic scenario

hai friends,
i have configured self service procurement and now i am configuring plan driven procurement in classic scenario.my doubt is suppose a shopping cart is created and placed in a sourcing application of the professional buyer.And assume he accomplished sourcing activity and created purchase order .Now purchase order is created locally or in the backed.i am using classic scenario ,now can u tell where the purchase order is located? if i want to place that particular purchase order in SRM it self what will i do? thanks in advance.

Hi Chandra
before going to select Business scenario (self service, plan driven..etc), you must freeze the technical scenario. Depends upon your technical scenario, your PO will be created .
Where PO is created it is called leading system. It is SAP standard.
If you were selected Classic- Po created in R/3.- R/3 is a leading system .
if you were select ECS- > PO will created in SRM and Copy also will be created in R/3 system. In EBP only you can edit the PO not in r/3. here SRM is a Leading system.
regards
Muthu

Regarding direct material procurement in Classic scenario.

Hello SRM Gurus ,
We are implementing SRM5.0 classic scenario, (SSP with CCM).
As per standard , Shopping cart for a direct material (Requisition for
stock) will create a follow-on document in SRM only (controlled extended
classic scenario).
Client's requirement is that it should create a back-end PR in R/3 system.
Reason being, the client needs to have only one indenting system and one
procurement system.
which BAPI in R/3 for PR/PO has to be used to create PRs or Pos from SRM. Similarly, RFC which FMs have to be used to update status in SRM.
How to bypass the standard replication mechanism.
Please help me..
Thanks and regards,
Mani
mail id : [email protected]

Hi
Why not go for the BADI -> BBP_TARGET_OBJTYPE
Or
Alternatively using SPRO settings, you can change the standard behaviour of the system based on various attrbutes e.g., for a Particular Product, Item category, etc.
Here is the Path ->
IMG -> Supplier Relationship Mnagement -> SRM Server -> Cross-Application Basic settings -> Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)
Define Objects in Backend System (Purch. Reqs, Reservations,
You perform this step only if you create your Materials Management documents in a backend system.
You specify the documents that are to be created in the backend system for a requirement coverage request.
The following documents can be created:
Purchase requisition
Purchase order
Reservation
You enter a product category (such as office supplies, or hardware) and/or an organizational unit. The organizational unit contains the purchasing group that is responsible for procuring products in this category.
You can enter the product category generically, such as Office*.
Note
The backend system is determined using the product category in the requirement coverage request item. The item also contains the organizatinal unit.
You can use the Business Add-In BBP_TARGET_OBJTYPE if you wish to implement a different logic for creating documents in the backend system.
Example
If purchasing group 01 wants to procure materials from the category Raw Materials, a reservation is to be created every time.
If materials in the category PC are to be procured, a purchase requisition is to be created every time.
Activities
1. Enter the organizational unit and/or the category.
2. Enter a source system.
3. Choose the procurement type.
Reservation if stock is available, otherwise external procurement
The system creates a reservation if the material is subject to inventory management and sufficient stock quantity is available in the warehouse on the requested date.
Always reservation for materials subject to inventory management
The system creates a reservation if the material is subject to inventory management, irrespective of whether stock is available.
Always external procurement
The system does not create a reservation, but always procures the item externally. In this case, you specify the type of external procurement.
The following options are significant if the system cannot create a reservation (for example, if there is no stock available or for a non-stock item) or the system must not create a reservation (choose Always external procurement).
Purchase order if item data complete, otherwise purchase requisition
The system always tries to create a purchase order. If the item data is incomplete (for example, the vendor or price is not known), the system creates a purchase requisition from the item.
Always purchase requisition
The system always creates a purchase requisition.
Always local purchase order
The system always creates a local purchase order.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Central Contract Management in case of Classic Scenario

Hi,
At our current implementation, requirement is to implement both Service procurement(with hierarchy) and Central Conract Management. I was exploring the possibility of utilizing Central Contract Management with Classic scenario.
Will the Central Contracts created in this fashion be available in Sourcing Cockpit for the buyer to select against Purchase Requisitions? Will the Central Contract be visible at all in SRM in this case ?
Please respond only with reference to Classic scenario.
Thanks,
Abhilash

Yes the Central Contract will be available in the Sourcing Cockpit, both local and classic scenario's. Yes the Central Contracts will be available for the creation of Purchase Requisitions in R/3 and to assign SOS in R/3.
Do know that for SRM 7.0 PI is required for setting up Central Contracts. This is promised to change with the release of EHP1 for SRM (due june 2010).
Kind regards,
Tim

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

Stock Procurement by Classic Scenario

Hi,
We are using SRM Server 5.5 as an add-on component to ECC 6.0. Only Classic deployment is in our scope.
Can anybody clarify me if we can procure Stock Material by Classic deployment of SRM?
While creating SC, when I click on 'Order as Direct Material' system is unable to determine the Purchasing Group and Org. So its unable to get replicated into R/3.
Thanks
Debashish

Hi Jagdish,
SAP told us that standard Classic scenario can't handle Stock procurement. For stock proc we need to have the extended classic scenario. In Extended classic we have Plan-driven procurement and we can do it there. Once again for stock procurement we need to define Local Purch grp and purch org and we need to have POs in SRM. POs in SRM is possible for Extended Classic scenario and this is not a part of Classic scenario.
SAP said that if we want to create Stock SC in SRM then we have to go for development.
Can anybody in this forum please confirm that in Classic Scenario we can't create a Stock SC (Without development)?
If you refer to OSS note 963000, it says that in ADD-ON SRM , only classic scenario is supported. If this is the case why I can see the 'Order as Direct Material' button.
Can anybody help me here??
Thanks
Debashish

PDP with classic scenario

Hello,
I am working with SRM 7.0 and ECC 6.0.
1) I would like to know how do you transfer PR to SRM in classic scenario? Is it the same as for extended classic scenario (using program BBP_EXTREQ_TRANSFER)?
2) How do you create PO in backend for direct procurement in classic scenario ? I was reading different threads and I found that I need to apply a BADI to clear the account information. Is this correct?
Thanks in advance!
Martí

Hi Martin,
As mentioned by SAM, you can transfer the requirements from ECC system to SRM system using newly introduced BAdi 'ME_REQ_Sourcing_cust'. BBP_EXTREQ_TRANSFER' is no longer used. However, your backend ECC system has to be on ECC 6.0 enhancement pack 4. otherwise, you still need to use the prog you have mentioned.
Yes, you can still use classic scenario for direct procurement by claring the accounting info in SRM. there are already number of threads for the custom solution.
Regards,
Ranjan

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

Doubts in PO's after a Bid invitation in Classic Scenario

Hello everyone,
I am working in SRM 5.0 in a classic scenario. I have a doubt, I do de following:
1. Create a PR in R/3
2. Replicate the PR in SRM as SC
3. Create a Bid invitation form the SC
4. Accept a Bid
5. Create a PO
In the 5th step, the PO is created in both system (SRM and R/3). Is this correct?
I though that only the PO is created in R/3.
Thanks
Ivá

Hi Ivan,
Pls see this thread which discusses abt the workaorunds for your requirement to create the PO in R/3 backend instead of locally in SRM.
Re: Regarding direct material procurement in Classic scenario.
BR,
Disha.
Do reward points for useful answers.

How can we know in classic scenario, whether confirmation has been done in

Hi ,
In Self service procurement with classic scenario:
I believe that we can do confirmation in EBP or in R/3.
How can we know in classic scenario after confirmation, whether confirmation has been done in EBP or in R/3.
Also please give an idea is there any configuration difference for confirmation need to do in EBP.
thanks
RESHMA

Hello Reshma,
>
Reshmab wrote:
> How can we know in classic scenario after confirmation, whether confirmation has been done in EBP or in R/3.
> (...)
Using Web GUI (ITS or Portal), if you look at the SC history (or PO history) in table mode, if column where you find SC number as no value for confirmation (confirmation with SRM number range), this means PO was confirmed directly in R/3 with a Goods Receipt.
Using SAP GUI, if confirmation was done in SRM purchasing document exists in CRMD_ORDERADM_H for PROCESS_TYPE = 'CONF',
>
Reshmab wrote:
> Also please give an idea is there any configuration difference for confirmation need to do in EBP.
> (...)
There is no specific customizing to allow SRM confirmation: just give correct role to users in order access to confirmation transactions (authorization object BBP_PD_CNF ). Check with roles EMPLOYEE* or PURCHASER*.
Regards.
Laurent.

Question to those who do Direct Procurement in EBP

Hello,
I just have a simple question to those who have confgured and process Direct Procurement in EBP....
 If you click the 'Order as Direct' button, can you click it again to revert back? If
 not, what is your process to revert back? If you can, have you have any
 problems or dumps that an OSS note cured?
Thank you in advance and points award accordingly.
Regards, Dean.

Hi
To disable this button, you need to create an Active Implementation of 'BBP_DP_PROD_CHK_BADI' using SE18 transaction. (Read SAP documentation first)
yes, this can be deactivated via BADI BBP_DP_PROD_CHK_BADI.
In method PRODUCT_CHECK, just clear EV_DP_FLAG.
Related links ->
Re: How to hide 'Order as Direct' button?
Direct material
Re: Question regarding direct material
Re: Regarding direct material procurement in Classic scenario.
Re: how to hide, turnoff, disable a button, checkbox on Shopping Cart
Assigning R/3 products to a Product category in SRM
Related SAP OSS Notes ->
Note 654892 Incorrect subtype of items in extended scenario
Note 544184 Direct material procurement with content integrator
Regards
- Atul

Difference between Classic Scenario and Extended Classic Scenario

Hi Expers,
I need your help again........:-)
I just want to know what is the differne between classic and Extended Classic Scenario.
Points will be rewarded
Thank you
sam

Hi Sam,
(explaination frm a previous thread)
Difference between scenarios
WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).
Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
Please check this too:
http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
BR,
Disha.

Manage direct procurement in classic scenario

Similar Messages

Maybe you are looking for