Regarding direct material procurement in Classic scenario.

Question

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]

Answer 1

Hi
<b>Why not go for the BADI -> BBP_TARGET_OBJTYPE</b>
Or
<u>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.</u>
<b>Here is the Path ->
IMG -> Supplier Relationship Mnagement -> SRM Server -> Cross-Application Basic settings -> Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)</b>
<b>Define Objects in Backend System (Purch. Reqs, Reservations,</b>
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