Is direct po possible in classic scenario?

hi ,
i am using classic scenario.so whenever i created a sc it creates a indirect po in the back end system.but i wanted to create a direct po in the backend system with out picking up the account assignment tab.so what can i do to get direct po in the back end system in classic scenario.
thanks
chakri

Hi Chakra
it is verypossible by development . remove accounting assignment . do some trick with BADI. we can not break sap but can over ride..
good functional consultant is a person not who knows standard . but he should know how to satisfy the customer by over riding the sap standard.
put some new threads you will get answer..
i am not deserved to get u r pts...
try to clear account assignment with badi..bbp_CREATE_BE_PO_NEW
sorry for my hasty standard answer,....
muthu

Similar Messages

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

Is plan driven procurement possible in classic scenario

hai ,
is classic scenario possible in plan driven procurement? if possible anyone give me the steps required to do it.
thanks and best regards,
n.chakradhar

Hi there,
See the link to help
http://help.sap.com/saphelp_srm50/helpdata/en/18/8897267ef5eb44beb7fc578e95845e/frameset.htm
=====
Technical Scenarios
You can carry out procurement of external requirements in conjunction with the following technical scenarios of Enterprise Buyer:
·        Standalone scenario
·        Classic scenario
·        Extended classic scenario
=====
Regards,
Matthew

BBPSC18 - Request for external staff - Classic Scenario in SRM 5.0 possible

Hello Community,
one of my customers wants to use "Reqest for External Staff". As far as I remember, in SRM 5.0 it is only possible in "Standalone Scenario".
Is this assumption correct? So not possible in Classic Scenario?
How about "Extended Classic"? Probably not possible either, right?
Thanks for any help or input!
Cheers, Julian

Hi Rahul,
thanks for your answer!
Actually I am only looking into the part "Request for External Staff" - "Acceppt Bid" - "Create PO (Classic in ERP)".
I have seen that this part works in SRM 7.01.
But currently we are not planning to upgrade. We are still on 5.0.
I tested the abovementioned process in our DEV-System. I behaves fine, no error messages. But when I want to create the PO out of the "Check Status" (yes, in SRM 5.0 this was possible), the system pretends to create a PO but it never gets created. So I just wonder if I missed some customizing, or if this also only works in Standalone or if there maybe is a smart technical workaround (some custom coding etc...).
Cheers, Julian

SUS-MM integration in Classic Scenario for SRM

Hello All,
We are using SAP SRM in classic Scenario.
We also plan to integrate SUS with MM .
Looks like in the Classic Scenario with SRM , only the Direct material procurement is possible
using MM- SUS.
How would the SUS-MM integration work for Indirect PO's.
Our Process is as follows:
1) Shopping cart created in SRM for Indirect material & approved ( with cost assignment)
2) Classic PO created in backend & sent to SUS
After this step is it possible that the Vendor create the GR in SUS and it is sent to ECC for Approva through PI l??
Thanks
Kedar

KedarG wrote:
> Is it possible in Classic Scenario, to send the SUS confirmation to SRM instead and from there to ECC
NO. dont think of a situation like that. if it is classic scenario except SC every thing will in ECC. how do you think confirmation creation can be possible in SRM when PO is not present in SRM!!
> Can you provide some details on ECC workflows. I didn't find any thing on this. Does ECC even support workflows as SRM?
>
SRM is a kiddo infront of ECC, so workflows definitely are present in ECC(not BRFs but event driven wfs).
any ways, your solution would be a custom solution, implement MB_DOCUMENT_BADI, to trigger a custom WF from custom event. this can be used for notification and stuff. but it wont stop the execution, so, dig on it how to stop the GR post till the workflow is not over.
and invoice anyways has workflows which you can use

PO type in classic scenario

Dear SAP gurus,
We're planning to use classic scenario in SRM 7 EHP 2 with backend ECC 6 EHP 5. In my previous project, i'm using extended classic, where after accepting RFx response, I can click simulate and create PO, and I can choose the PO type that I want to use (we have 5 PO types that we configure BOTH in SRM and ECC, as in extended classic, the leading PO is in SRM, I have setup internal number in SRM and external number in ECC).
In classic, can we also have the same feature where we can choose the PO type? Because as I recall, the determination of object in backend is in a setting where we can only define ONE number range for PO only. Is it possible during classic scenario I can choose which PO type that I want to create in ECC?
Appreciate your help on this.
Best regards,
John

Hi,
While creating PO from RFX, no pop up window will be opened to select the PO document type in Classic Scenario. Please have a look at the Knowledge base document no 1580116- "Classic scenario: Transaction types in Step 3 of the Sourcing Cockpit ".
SAP note 1323983 allows this modification. This is a modification note and is not available in standard.
Thanks,
Anshu

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.

Pcard integration in Classic Scenario

Hi All
I learnt that it is possible to use pCard in Classic Scenario if a few customizations are made.
These customizations include adding a few custom fields in the shopping cart & ECC PO for Pcard Company, Pcard Number
and Validity date.
However once these customizations are done, would the reconciliation in SRM work as in ECS, or further code changes will be required?
Thanks
Kedar

KedarG wrote:
> Is it possible in Classic Scenario, to send the SUS confirmation to SRM instead and from there to ECC
NO. dont think of a situation like that. if it is classic scenario except SC every thing will in ECC. how do you think confirmation creation can be possible in SRM when PO is not present in SRM!!
> Can you provide some details on ECC workflows. I didn't find any thing on this. Does ECC even support workflows as SRM?
>
SRM is a kiddo infront of ECC, so workflows definitely are present in ECC(not BRFs but event driven wfs).
any ways, your solution would be a custom solution, implement MB_DOCUMENT_BADI, to trigger a custom WF from custom event. this can be used for notification and stuff. but it wont stop the execution, so, dig on it how to stop the GR post till the workflow is not over.
and invoice anyways has workflows which you can use

Plan-Driven in classic scenario

Hi there.
We are working with classic scenario in SRM 5.5
We are customizing plan-driven procurement (only MRP without PS and PM modules)
Is it possible the next flow?
For ECC system
1. MRP creates purchase requisition
2. We pass the purchase requisition from ECC to SRM as SC
For SRM system.
3. We create bid invitation and bids from the SC
4. We create a PO in classic scenario (in ECC)
We try to do it, but when the SC is created in SRM, always appears as extended scenario.
Moreover we have deactivated the extended scenario.
Is it possible to run Plan-Driven in classic scenario or it is mandatory extended scenario?
Thanks and regards.
Raúl.

Hi,
The document flow you mentioned is possible with classic scenario.(The SPRO setting "activate Extended Classic " is not checked).
You can have all PR's transferred form R/3 to SRM and create Bid invitations from the SC's created in SRM in Sourcing Application.
BR,
Disha.

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

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 ?

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

Z Partner in classic scenario - Is possible to transfer ?

Hi Gurus,
I`m working in classic scenario.
SRM 5.0 / SRM Server 5.5 / R/3 4.7
I need your help about Partner Functions in PO.
I have a Z partner created in R/3 that is mandatory in one type of PO (in header) - the partner type is ZE. I need to replicate this Z partner in SRM.
I tried to create a new type of partner in customizing - Define Partner Functions, with Func. Type - 0012 - Vendor, but the system didn`t allow.
Because this, I used one line with Func. Type - 501 (Customer Partner Type:Org) and include my Z partner in field Abbrev.
Like this:
Function: 00000701
Func. Type: 0501
Usage: B2B
Description: Embarcador
Abbrev.: ZE
After this, I created one new type of Partner Schema and linked this new Schema in one type of Bid Invitation (BUS2200) and one type Purchase Order (BUS2201) - the same type of PO that ZE partner is mandatory in R/3.
In test in ITS, the system shows me the field to include the new partner, but when I try to create PO, the system can`t to transfer this new partner from Bidding SRM to PO R/3 and shows me the error message: the ZE Partner is mandatory in this type of PO (I know that this message is from R/3).
Please, somebody knows if is possible to create new partner and transfer it from SRM to R/3 in classic scenario ?
Thanks very much.
Best regards,
Cris
Edited by: Cristina Alkmin da Costa on Jun 30, 2008 3:53 PM

Hi. Patrner functions are generally different in SRM.
Do you want to be able to select from a list of values in SRM and get the value passed to the backend or do you want a fixed value, or can you look the value up from somewhere?
If you want to fix it or look it up you can simply use the BBP_CREATE_BE_PO_NEW BADI to pass the value.
If you want to select from a list of values, I think the only way is to create a custom field, see note 672960, then you can build a custom search help to find the lookup values you require.
Once you have looked them up, you can pass it to the backend using BBP_CREATE_BE_PO_NEW.
Regards,
Dave.

Is B/E ECC SoS in Local SRM PO in Classic Scenario Possible ( SRM7.0) ?

Hi Experts,
We are configuring SRM7.0 with ECC6 ( Ehp4) having Classic Scenario .
Our Ultimate Aim is - To maintain SoS in ONE system only (i.e. ECC) & use the same SoS in both ECC & SRM system, for all documents ( ECC PR, ECC PO, RM S/C, Local SRM POu2026etc )
In Classic Scenario, B/E ECC SoS ( Supplier Contract & Pur. Info Record) are proposing in S/C ( Indirect Mat.) , but these B/E SoS NOT proposing while creating u201CLocal SRM POu201D which is by default Ext. Classic.
We are exploring new CCTR functionality ....but seems complicated and requiered PI...
1.By doing any enhancement , can we pull B/E ECC Contract and Pur. Info Record as a SoS while creating u201CLocal SRM POu201D ?, If it is possible , then we are ready to do any enhnacement and I'll be most happy
2. Which BADi is used while creating Local SRM PO ?
Can anyone suggest/confirm please.
Thanks
NAP

Hello,
In classic scenario, only backend contracts can be used as SOS.
In extended classic, local contracts can be adopted as SOS.
If you are using classic scenario, you should distribute local contracts to ECC. Then, while creating a shopping cart in classic scenario, ECC contracts (which have been distributed) will be considered as SOS.
Regards,
Ricardo

Classic Scenario Possibility

Hi Friends,
I am a first times for Classic Scenario implementation.
Can the below scenario is a Possibility in SRM
1. SC creation
2. SOCO
3. RFX and Vendor Response
4. Central contract in SRM and distributed to MM
5. Release orders (PO) in MM with ref to Central COntract
I have few Questions:
1. What is the BSA attribute will be there in Classic
2. Can we create initiate sourcing from SC in CLassic or every time we create SC, it will create PR in ECC.
3. Can central contract be created locally in SRM and distributed in ECC (similar to Extended Classic)
Appreciate any help in this regard
IS

I am not sure as I have to test this in system but i found this some where which needs to be checked.
Section 3: Default Transaction Types
If there are multiple transaction types determined, then the default entry in the transaction type dropdown box is set to 'space'. If there is only one entry found for the user then this will be displayed as the default entry in the dropdown box. Here is the code section where it happens: /SAPSRM/CL_CH_WD_DOM_SOCO_GAF3, /SAPSRM/IF_CLL_MAPPER~REFRESH:

Is direct po possible in classic scenario?

Similar Messages

Maybe you are looking for