Reservation in Classic scenario

Hi Experts,
How does the reservation fucntionality work in classic scenario.
We do not want the application to create a reservationeven if there is stock in the backend. The system should always send the item to sourcing cockpit.
Is there a configuration by which we can restrict Reservation.
Regards,
Jith

Hi Dave,
Many thanks for your inputs. We have already set Always carry out sourcing. But it still does an availability check and tries to create a reservation.
Now we do not want to create reservation at all. We always want to send the item to the sorcing cockpit and create a PO or contract after sourcing.
If we use the BBP_TARGET_OBJECTS BADI we can set the object to resevation and the sourcing indicator is set.
But standard behaviour shoud be not to do a availability check and create reservation, once we set Always carry out sourcing. Is this a bug or are missing any config. (BTW we are on classic scenario).
Regards, Jith

Similar Messages

Reservation with Extended classic scenario

Hi ;o)
I'm working at a costumer were we have extended classic scenario. We want to be able to make reservations in the backend if the item is on stock, and we have seen in a solution matrix from SAP that this should be possible.
The configuration for reservations should be done according to the guides - but no reservations is created when ordering a stock material.
I was searching on the developer network, and came across a topic, where it was stated that reservations could only be made with classic scenario (or using a BAdI where you switch the extended on and off depending on product category). Do any of you know if this is really a fact?
Thanks in advance
Maria Hvenegaard, Denmark

Hi
Read this first.
You can use BBP_CREATE_RES_BACK BADI using Se18 Transaction.
This BADI You can find in SPRO -> Supplier Rel. Mngmt. -> SRM Server -> Business Add-Ins -> Follow-on document generation -> Reservation in Backend System
If you want to create reservation, you have first to switch from ECS to classic scenario through BBP_EXTLOCALPO_BADI then you have to implement BBP_TARGET_OBJTYPE badi to determine the criteria to create a reservation in your backend.
We need to maintian the customising setings in SPRO Transaction.
Define objects in Back end systems. Maintain the document type EC or ECPO for Purchase Orders and not for creating reservations. Maintain number ranges (RS) and align the same to R/3 or backend systems. In setting up the org plan in the PPOMA_BBP Transaction, the attribute for resevation - Attribute BWA should be maintained too, if reservations are to be created in the backend system.
Movement Type Accounting Object
201 Cost Center
221 WBS-Element
231 Sales Order
241 Asset
Example :
logicalsystemname\201
Maintain the following Settings in the IMG using SPRO Transaction.
1.For internal Procurement > 1.Always Reservation for Material types Subjected to inv Mgmt
2.For External Procurement >1.Always purchase Requisition.
Note -> The plant that you use to create the shopping cart might not be extended to handle inventory management. Select a right plant which is extended to inventory management and you will see a reservation being created.
Be aware that:
- with the classic scenario you can create PR, PO and/or Reservations in R/3, but there is no local purchasing document (except the SC), so all functions around the local PO will not be possible.
- with the extended classic scenario, you can only create PO in the backend, but a local PO exists in SRM.
Concerning GR, it is possible to make it in SRM for both scenario
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Classic Scenario - Reservation Movement Type

Hi All!
We are in a Classic Scenario environment and the requirement is for a certain type of material to create Reservations in the backend with a different Movement Type. Lets say we have three types of Stock Materials: two of these will create reservations with the Movement type 201 defined as default at the root level but I want the third type to create reservations with movement type 301 Transfer posting.
I have assigned this value (301) for the movement type attribute for a particular user and set it up as default but it didnt work, the reservation was still created with 201.
Is there any way I can achieve this? Will I need to use the BBP_DOC_CHANGE_BADI implementation?
Any idea will be much appreciated (and rewarded of course )
Many thanks
Elisabeta

Yes, I have successfully implemented this by using BAdI BBP_CREATE_RES_BACK as Dave suggested. I only wanted to change the movement type for a specific plant so Iu2019ve done something like this
method IF_EX_BBP_CREATE_RES_BACK~FILL_RES_INTERFACE.
data zl_res_items type bapiresbc.
if res_header-plant = u2018my_plantu2019
move '301' to res_header-move_type.
Endif.
maintain receiving plant & storage location
move res_header-plant to res_header-move_plant.
now this is the receiving plant which I am taking it from SRM
I have put in the functional specification accepted by the user the fact
that in SRM when they create the shopping cart they have to specify in the
location the storage location which is the destination
move zl_res_items-store_loc to res_header-move_stloc. move_stloc is
the destination
Then Iu2019ve changed the res_items-plant & res_items-store_loc to be the supplying location which in our case it will always be 0001. If your supplying
Location can be different then you will have to code some logic in here when you loop at res_items.
Also I have made the Plant attribute maintainable so that the users can maintain their own default destination plant if they want.
I hope this helps.
Good luck
Elisabeta

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

SRM 7 PPS Classic Scenario with Plan Driven Procurement?

Hello experts, I want to know if the combination of SRM 7 PPS Classic Scenario with Plan Driven Procurement is possible? or if there any limitation to consider? Our client needs to create purchase requisition in ERP -> send this purchase requisitions to SRM (as shopping carts) create bids - > quotations - > create contract from accepted quotations and then from the contract we need to create purchase order but this one must be created in ERP (classic scenario) Someone has experimented the same situation? Best regards and thanks for your Help.
Liam

Hi Lima ,
Classic scenario wont support PPS .
        - Stand alone and classic scenario not supported
        - Shopping cart renamed to Purchase Requisition
        - Shopping cart generate (pre)commitment in funds management
        - Contract can create Funds Reservation (Earmarked Funds) in Funds Management as a Guarantee
        - Goods Receipt and Invoice created in ERP
        - Mixed PO: PO with lines that works like contract lines, a PO can be created from these lines
        - PO created from contracts or mixed-PO is named call-off PO. Only is a new name, is a "normal" SRM      PO
        - Goods receipt possible in SRM only in "easy" cases
Thanks & Regards
Pradeep Kumar Dondeti

Extended classic scenario triggered on company code

Good morning,
I have a system with SRM 5.0. I would like to have both classic and extended classic scenario, I know that it is possible to activate extended classic only for a product category with BADI BBP_EXTLOCALPO_BADI , but my question is: Is it possible to activate it for a company code? If yes, is it with the same BADI ?
Thanks in advance
Charlotte

Hi
Before talking about de-activating ECS or not in this BADI, this scenario must first be activated.
This is done via the customizing point "Activate ECS": just flag the check-box, and all you classic items (i.e. those for which a backend has been determined) become extended classic.
Here is the SRM - IMG path:
SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
You can then fine-tune the scenario by using the BADI BBP_EXTLOCALPO_BADI.
Note- The BADI BBP_EXTLOCAL_PO_BADI can be used to activate the classic scenario based on the proguct categories .
You can choose to have the 3 scenarios working on the same SRM system depending on product category (standard) or any other business rule through the BADI BBP_EXTLOCALPO_BADI. The BADI is mandatory if you want the Classic and the Extended Classic to work together
Exactly, this BADI allow you to implement your own business rule for backend determination in a multiple Backends environment (Standard customizing is only based on Product categories)
As soon as you use BADI BBP_EXTLOCALPO_BADI , you don't have to use the ECS scenario activation customizing point (the rule is overwritten with the BADI result). The BADI BBP_DETERMINE_LOGSYS will only help in your case, if you have several Backend where to create PO documents.
PS: be aware that in ECS scenario you will no longer be able to create PR or reservations in R/3.
Other related links ->
Classic Scenanio and Extended Classic Scenario
Extended Classic vs Standalone
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Classic / Extended Classic Scenario for Shopping Cart
Re: Classic Scenanio and Extended Classic Scenario
Re: Switching from Classic to Extended Classic
Re: Calssic or Extended Classic Scenario - BBP_EXTLOCALPO_BADI
Change from ECS to Classic Scenario
Re: Changing the Global Control of Extended Classic Scenario
Re: Technical Scenario Switch: From Standalone To Extended Classic
Do let me know.
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.

Reverting to classic scenario in SRM7.1, from PPS and extended classic

Hello Experts,
Recently we have moved from SRM7 to SRM 7.01, in which we can have PPS without Extended classic scenario.
As business wants classic scenario, How can we make the system as classic , in which PPS and extended classic is activated.
any badi is available for this? Please help.
Regards,
Raju

Raju,
Basically you have few points to keep in mind. (yes you need to activate the SPRO config for extended classic, apart from this).
1. switch between extended classic and classic is actually defined by the backend logical system of the document. if thats SRM itself then it follows the path of extended classic or if it is ECC then it follows classic.
because its basically creating a follow on document and that explains the scenario.
2. it also depends on what object are you expecting to be created. from a SC many documents can be created.
a. PO in SRM
b. PO in ECC
c. PR in ECC
d. Reservation in ECC
- so, if you can define at any point that where is your document to be created and what is to be created you can control the flow.
Now to do this. if you have few options.
Option1:
1. set the object types(2) for product categories (config, backend document type).
2. implement BBP_EXTLOCALPO_BADI to switch off extended classic
Options 2:
1. in doc change badi, change the backend destination to ECC
2. in Badi BBP_TARGET_OBJTYPE pass the object type you want your follow on document to be.
hope this explains

Switching over from Extended Classic to Classic Scenario

Dear Experts,
If I need to switch back completely from Extended classic to Classic scenario do I need to activate any BADI?
Else I can just deactivate extended classic in SPRO.
Give your comments.
Regards,
B.N.Karthikeyan.

Hi Karthick,
Extended to classic
1. in SPRO - SRM Server - Cross application basic settings - Activate extended classic scenario
-- deactivate the check box.
2 . Cross application settings -- Define objects in backend system ( reservation, PR, PO )
Need to maintain this settings.. like for the sc which document should create in backend like PR/RES/PO.
3.In classic scenario no need to maintain IPC settings.. which require in Extended classic
4. Important thing is you should take care of number ranges..
Thanks
prasad.s

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

SRM PPS using classic scenario

Hi SRM Experts,
I am exploring the possibility of implementing PPS in SRM 7 using the classic scenario.
Please let me know if it is possible and how can it be achieved.
Earlier threads mention that PPS is only available using extended classic.
Thanks.
Regards,
Amish

Hi Amish ,
PSS scenario is not supported for classic scenario ,
changes in procurement process of SRM 7.0
        - Stand alone and classic scenario not supported
        - Shopping cart renamed to Purchase Requisition
        - Shopping cart generate (pre)commitment in funds management
        - Contract can create Funds Reservation (Earmarked Funds) in Funds Management as a Guarantee
        - Goods Receipt and Invoice created in ERP
        - Mixed PO: PO with lines that works like contract lines, a PO can be created from these lines
        - PO created from contracts or mixed-PO is named call-off PO. Only is a new name, is a "normal" SRM      PO
        - Goods receipt possible in SRM only in "easy" cases
Thanks& Regards
Pradeep Kumar Dondeti

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

Classic scenario

Hi experts
I would like to know how is the configuration for system generates PO in Backend after aproving shopping cart, in (CLASSIC SCENARIO) the number ranges interval in SRM and R/3 should be internal or external?
Thanks
Nilson

Hi,
In classical scenario,you can
On approval, the system creates the follow-on document in a particular backend system based on the information you entered in Customizing for SRM Server. Depending on availability of the item or service you require, and on the settings you have entered in Customizing, this follow-on document may be a:
Purchase order Purchase requisition Reservation
It's in SPRO-SRM -Cross Application Basic settings-Define Objects in Backend System(Purch reqs, Reservations...........................)
for detail see the link
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/srm/technical+scenarios&
There is an icon for link,which will give you details of setting possible in different scenario.
For mumber range config please refer the foll threads:
Re: Number range config
Defining the number range
Re: Extended Classic - Purchase Order Number Ranges
Re: PO Creation with external PO number
Re: Different number ranges for shopping carts
BR,
Disha.
Pls reward points for useful answers.

Classic Scenario -Backend settings

Hi,
In the classic scenario the following is done in SRM
1. In the PPOMA_BBP - we are defining the Attribute : BSA - as EC
2. How this is linking with the Backend in SAP R/3.
We have created the Logical system-in SM59 and RFC are assigned to SRM and SAP R/3.
Backend SAP R/3
1. Number Ranges for P.O defined?
In SAP R/3 -SPRO -Define Document types -We can see the Type EC
How is the linking is achieved in SRM and Backend in classic scenario,.
Can you explain in details what are the setting done in SRM and SAP R/3 to achieve the Classic scenario
Regards
G.Ganesh Kumar

Hi,
Some of the basic settings around document types in SRM for the classic scenario which you have to define are the following :
In R/3 system:
1. define number range for the POs , PREQs and Reservations which will be created in R/3 system,
2. create document types for PO, PREQs and Reservations and assign to them the number of the number ranges created in step 1 - this is the doc type which you have to assign to BSA attribute
In SRM system:
1. define SRM transaction types
2. Define shopping cart number range, as well as the number range of the follow on documents created in R/3 system
3. Define number range for local confirmations of services and goods receipts
Regards,
Desislava

Some questions about classic scenario

Hi all:
      For classic scenario,I found the SC with indirect material procurement could created a corresponding Reservation or PR in R/3,But for direct material procurement, the SC could not have any courresponding document created in R/3. Does it right.

Hi,
This scenario relies strongly on the Enterprise Resource Planning (ERP) backend system(s), since all materials management documents, such as purchase orders, goods receipts, service entry sheets, and invoices are located there. Enterprise Buyer and one or more backend systems (SAP or Non-SAP) are implemented. All materials management is mapped in the ERP system. All materials management documents (such as purchase orders, goods receipts, service entry sheets and invoices) exist in the backend system.
SAP Enterprise Buyer is used to create the shopping cart and obtain approval if required. The goods receipt and invoice can also be entered here. SAP Enterprise Buyer communicates this information to the backend system where the active documents are created.
This scenario suits customers:
     Who want a wide user group, for example employees not necessarily working in the purchasing department, to be able to enter their requirements quickly and easily. SAP Enterprise Buyers functionality and ease of navigation allow this, as it requires only minimal training
     Who want their purchasing department to operate solely with the functionality offered by the backend system(s)
     For whom a transfer of purchasing activities to SAP Enterprise Buyer is not viable
If collective invoicing needs to be conducted, the classic scenario must be used.
Hope this helps u....
Reward points if useful...
Regards,
Sreenivas

Reservation in Classic scenario

Similar Messages

Maybe you are looking for