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

Similar Messages

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

Info Record Not Appearing for all materials in classic scenario.

HI ALL,
 I am working on Classic Scenario and all the follow-on documents are getting created properly. But the problem is With SOS. Currently i am able to view the info record for only one of my material, I am also referring backend contracts through vendor list. The contracts are visible in SOS.
 Can somebody pls put a light as to why for other materials the info records is not displayed in SOS, is there a report which has to be run to get the info record into SRM from ECC. If not then how does the system bring these contracts and info record from ECC to SRM.
 I am working on SRM 5.0 and ECC 5.0.
THANKS AND REGARDS
Debu

Hi
Please read this as well.
You have created sources of supply. These could be:
-> Contract items in Enterprise Buyer
-> Vendor-specific prices
For this, you have created Product Linkages in the SRM System with vendor-specific prices via the SAP Menu Master Data -> Products -> Process Products.
-> Entries in the vendor list of Enterprise Buyer
In Customizing you have assigned product categories to which the system is to automatically group requirements and you have scheduled report BP_SC_TRANSFER_GROUPED to run periodically.
For more information, see the Supplier Relationship Management Implementation Guide (IMG): SRM Server -> Sourcing -> Define Interactive Sourcing for Product Categories.
Sourcing is completely integrated with the global availability check in SAP APO and executes a vendor search. You can activate third-party order processing in the check instructions by choosing how you want the system to start sourcing and which sourcing method you want to use for it. There are two different options here:
○ If you want the products to be delivered exclusively by external vendors, the system performs sourcing directly at the external vendors without evaluating internal locations. For this, SAP APO requires corresponding purchasing records, delivery plans and contracts that are transferred from SAP ECC.
○ If you only want to have products delivered by external vendors occasionally, that is to say, if you are unable to deliver the product from your own warehouse stock, choose an ATP profile in which both internal and external vendors are evaluated. In this case, the external vendor is treated like an internal location in SAP APO, and is integrated into location determination in the rule-based availability check.
You can also choose the vendor manually. If you have already specified a vendor as the source of supply in SAP CRM, SAP SCM does not carry out any further sourcing. In this case, SAP SCM merely checks the validity of this vendor and confirms the requirement in its full amount if the vendor is valid.
For more information, see SAP Library for SAP SCM at SAP Advanced Planning and Optimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> Advanced Availability Check Methods -> Third-Party Order Processing in the Global ATP -> Sourcing in Third-Party Order Processing.
Refer these links for more details ->
Assignment of Existing Sources of Supply
http://help.sap.com/saphelp_srm50/helpdata/en/25/40f23a53cd0e04e10000000a11402f/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/55/4af548688211d4977e0004ac962ee6/frameset.htm
http://help.sap.com/saphelp_crm50/helpdata/en/fa/84944279c0c66ae10000000a155106/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/18/db183d30805c59e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/63/36f2323326da4da25d9d0a06f550a0/frameset.htm
Processing Contracts
http://help.sap.com/saphelp_srm50/helpdata/en/43/0f234a9e242a8be10000000a1553f6/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/5a/4cc5376848616ae10000009b38f889/frameset.htm
See alsoSAP Note 519794 EBP: Replication of Materials exclusively for Purchasing
SAP Note 505030 (Restrictions for the integration of external requirements).
Regards
- Atul

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

Extended Classic Scenario does not create backend PO

We have SRM 5.0 SP 11 with ECC 6.0 backend (only one comp code, one plant and couple storage locations in the plant). I am configuring extended classic in there with the Org structure having Local Purchasing Org/ Local Purchasing Groups and the ECC Purchasing Org/ ECC Purchasing Groups.
It appears I am missing something; the system creates a Local PO just fine, however, dont see any signs of the system attempting to create a PO in the ECC system (no runtime errors or logs in either system).
In fact, my shopping cart does not show any value for Location (although the Org has the ECC location assigned to the user).
Any help is highly appreciated. Thx.
Raja

ECC 6.0 is ERP_2.0 and not R/3_4.70.
also check the resp org unit consistency with BBP_BP_OM_INTEGRATE
with the option all object types.
if I am not mistaken there are some FMs to push the copt again
like
BBP_PD_PO_transfer
(pl check the syntax... don't have system)
also check on "bachend prgp responcible" for yr ECS settings
also check the logic if you have implemented
BADI control ECS
BR
Dinesh

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

SUS for classic scenario

Hello All,
Is it not possible to set-up a SUS for classic scenario? if so, can some one tell me why?
We have a ECC- EBP classic scenario for direct procurement and plan to leverage the same EBP to set up a SUS . SUS will be on a different client and we would like to use EBP-SUS for indirect procurement.
Please advice. will award points for sensible answers
S

in the case of classic scenario --> following restrictions apply
1) since there is no local document created in SRM , it is not possible to send the purchase order document from SRM to SUS
2) document has to be send from R/3 , and it is possible there to order materials and not services....
3) services is not supported from R/3 to SUS.
hope this helps...

Collective Invoice Posting for Direct Materials

Hi ,
We have extended classic scenario with R/3 backend and we are posting Collective Invoices for multiple POs for direct materials ( order type ECDP).Invoices fail to transfer to backend.BD87 /WE02 log in R/3 indicates the following error -->Acct assgt 01 for order item 2200000070 00001 does not exist
Message no. M8140
Also ,if I try posting the invoices in R/3 using MIRO, there are no errors.
Thanks,
Gourang

Several notes show up for M8140.
316657, 615114, 506930 in the SRM area.
493604, 810917 for BAPIs may also be relevant.
334765 recommends creating a support message for further analysis.
Kind Regards, Suresh.

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

Classic scenario, where to create Contract and product category

Hello All,
We are using SRM4.0 ( Classic scenario) with non-sap backend system.
We need to attach contract in Shopping cart in SRM.
My questions are:
1. In which system ( EBP or non-sap backed), we need to create contract? and how to create it?
2. In which system( EBP or non-sap backend), we need to define product or product category? and how to create it?
Regards
Neelesh

Neelesh
When you replicate product categories from any backend system, they get created in SRM and update the value of logical system with the backend from which it replicated.
You can only create Product category in standalone. You can try to create the same for classic but maintain log syst value with the correct backend. This is not advisable.
PS : Reward points if helpful.
Regards
Jagadish

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

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

BAPI Required to post GR in EBP System( SRM4.0, Classic Scenario)

Hello All,
We have SRM4.0 with classic scenario with non-sap backend system.
We need to post GR in EBP system automatically.
could you please tell me the BAPI required for this?
Regards
Neelesh

Hi,
You can use function BBP_BC_CONF_CREATE of BAPI_CONFEC_CREATE.
Kind regards,
Yann

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 ?

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

Direct materials in classic scenario - any restriction in backend?

Similar Messages

Maybe you are looking for