:):(Creation of RFX or LAC in a Classic Scenario:):(

Hi Guys,
I was wondering if you guys could come up with some nice suggestions on how i should go ahead and process my requirements.
We are implementing a SRM 4.0 (classic scenario) system. I am aware that all shopping carts in SRM are created and transferred to the backend as a PO/PR according to our customization and nothing goes to the sourcing cockpit when a vendor is not assigned in a classic scenario.
Implementation of a classic scenario restricts one to create a Bid or a Live Auction from the sourcing cockpit. Can all the SRM GURUS suggest me in what way one could push the requirements to the bidding engine or to the Live Auction Cockpit in a CLASSIC SCENARIO.
I hope i would get great responses.
Thanks
Sunny

Hello Sunny,
there has never been such limitations.
Classic scenario is supported by Sourcing Cockpit & Bidding Engine in SRM 4.0, at the condition that a classic SC is created in SRM.
In sourcing customizing, you can decide to send all SC without source of supply to the Sourcing Cockpit.
You can even decide to initiate directly an RFX, without using the Sourcing Cockpit.
At the end of the negociation (RFX --> Bids --> Auctions --> Bids), the awarded bid can be transformed into a backend PO or a backend Contrat.
Rgds
Christophe

Similar Messages

Doubts in creation of PO for service PR in classic scenario

Hi everyone,
I'm working with SRM 5.5 in a classic scenario.
I have the following process:
1. A PR for services is created in ECC (Item Category "D")
2. The PR is transferred to SRM as SC
3. A bid invitation is created in sourcing cockpit
4. A bid is accepted
5. A PO is created.
In the 5th step the PO is created locally in SRM. Is this the standard behavior?? Why is not created in R/3?
Thanks,
Ivá

Hi Ivan,
For scenario details pls refer below links:
http://help.sap.com/saphelp_srm50/helpdata/en/d9/cbd33b8dca2c43e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/frameset.htm
What message do you get when you create a PO from Bid?
Are you able to execute the scenario for materials?
Regards,
Prashant

Creation of Inbound delivery mandatory for ASN process in classic scenario?

Dear Experts,
We are going for classic scenario for our green field SRM implementation process. Our client is not using ASN process in their existing MM process. However, they are now looking for an oppurtunity to enable Suppliers to trigger ASN using SUS. In such case, is creation of inbound delivery from Buyer side a mandatory process?
Is the below the process correct?
PO -> ASN (Supplier using SUS) -> Inbound delivery (Optional) -> Goods Receipt (Mandatory) -> Invoicing.
Here, I understand that Goods receipt can be verified against the PO or via Inbound delivery to PO. ASN will inform the store keeper in advance about impending goods receipt and smoothen the confirmation process.
Could you please comment on the above process? Could you please suggest the best practices followed here?
Thanks and regards,
Ranjan
Ranjan Sutradhar

Hey Ranjan!,
You are on track.
The process flow you have shown is true. ASN is available as a standard as part of the MM-SUS process. It makes the buyer aware of any delays in delivery or to make arrangements on shipping docks to receive goods on a said date etc.
Regards,
Nikhil

Creation of PO in Classic scenario.

Hi
i am using classic scenario.my problem is i have created shopping cart&approved.after approving this PR had been generated.
ok. now i want to create PO,GR &Invoice with PR.but i could not create with PR.
so please suggest me How to create PO, GR, Invoice with PR in Back end?
OR
Are these created automatically without PR in Backend?
could any one suggest the process.
BR
sss

Hi
This control settings available in SRM
SPRO
cross apllication settings..
Define Objects for Backend System
check this settings for your material group w.r.t external procurement.
is it PO creation or PR generate settings?
Is your Shopping cart has a valid source of supply.
if your cart is incomplete , PR only created, so check it up.
br
muthu

PO Creation Process in Classic Scenario

Hi
I want to understand the exact PO creation process in a classic scenario. Once the buyer clicks on 'Create Purchase Order' in the SOCO, what are the series of steps that are triggered till the PO number gets displayed in the SOCO screen?
I assume that the shopping cart has all required data and ready for PO creation.
With Regards
Sathya

Hi,
The shopping cart is created and approved in SAP Enterprise Buyer. The remainder of the procurement process takes place in the backend ERP system(s) and all other follow-on documents, such the purchase order, goods receipt/service entry sheet and invoice, are located there. With SAP Supplier Self-Services, you have partial supplier involvement for the operational procurement business scenarios when buying materials. There is no support for services.
Shopping Cart
SAP Enterprise Buyer
Approval
SAP Enterprise Buyer
Purchase Order
Backend system
Goods Receipt
Backend system (can be pre-entered in SAP Enterprise Buyer)
Invoice
Backend system (can be pre-entered in SAP Enterprise Buyer)
Please award the points if it helps.
BR,
Vijay Mittal

Contract Creation in SRM 7.0 classic scenario

Hi All,
We are using SRM 7.0 Classic scenario with ECC 6.0 EHP 4 and CLM 2. We are creating contracts in SAP CLM and pushing into as Global outline agreement.
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
What are the mandatory fields required to transfer the CLM contracts contracts to ECC outline agreement - I know ,Vendor, Purchase org, Pur grp, company code are required - is product catagory is also a mandatory field.
Rgds/Pawan

Hi Pawan,
Please find the answered for your questions:
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
Mitesh: Yes we can very well create in Classic Scenario as well in SRM 7.0.SC can be pushed to SOCO based on the Prod Category configuration in SPRO.From SOCO PO, Contract and RFX can be created for SC.
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
Mitesh: I dont think we can use ECC outline agreement as source of supply in SRM while creating SC.Contract replication in SRM 7.0 with EHP 4 ECC is eSOA based and ONLY Outbound to SRM (inbound to ECC).Contract cannot be replicated from ECC to SRM.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
+Mitesh: Standard intergeration of CLM/ESO to SRM 7.0 is very much there in roadmap for future releases of SRM/ESO.+
+As of now there is a consulting solution available to integerate ECC and ESO/CLM.+
+This logic can be leveraged to integrate ESO/CLM to SMR 7.0 (or lower version) requiring Developement effort from SRM functional,SRM technical,PI, Basis,ESO and java consultants.+
+Such contracts can be forced to be used as Source of Supply or alternatively replicated to ECC Via standard repliation scenario.+
Hope this helps.
Regards,
Mitesh

SRM PO creation classic scenario

Hi,
I have some requirements & need direction
Scenario#1
Classic scenario: SC created for multiple lines with multiple product categories. This fetches corrosponding P Groups based on the config. When PO is created it creates multiple POs based on P Groups. We need to create single PO out of this SC by passing a dummy P Grp while PO creation
Scenario 2 #
Same example but all the product categories are same so there will be one P Grp passed on while PO creation. However, we need to pass a dummy P Grp while PO creation. Ideally in this scenario system would have created single PO but we need to pass this dummy P Grp. In short any PO generated out of SRM will have same P Grp. We dont want to touch current config & need development
Scenario 3#
SC -PO scenario. SOurced SCs. Once SC is approved, it will create PO as a standard functionality. However, we want to hold Po creation & subsequently run a batch job which will collect all SC approved during some period say 3 Hrs & group them based on vendor & plant & create POs accordingly.
Example:
Sourced SCs
SC-1 with vendor 123456 created for qty 100
SC-2 with vendor 999999 created for qty 200
SC-3 with vendor 123456 created for qty 100
We need to create 2 POs grouping first & third in one & create another PO for SC-2
Please advise
arjman

Dear Poster,
As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
Best Regards,
SDN SRM Moderation Team

Purchase Order Creation, Extended Classic Scenario

Can someone please explain the different databse tables affected during the creation of a Purchase Order.
Also, is there a transaction with which we can create PO in Extended classic scenario?

hi,
below are the tables effected while creation of PO:
CRMD_ORDERADM_H
CRMD_ORDERADM_I
BBP_PDIGP
BBP_PDBEI
BBP_PDISB
BBP_PDISS
BBP_PDSDLN
BBP_PDACC
BBP_PDTAX
BBP_PDATT
BBP_PDORG
BBP_PDWGT
BBP_PDDYN
BBP_PDEXR
PRCD_ITEM
PRCD_COND
PRCD_COND
BBP_PDDEP
CRMD_PARTNER
as far as your second question is concerned normally we will be creating a PO in SRM/EBP in web browser and it will replicate to the backend ERP.
regards
IGA

How to know which BAPi is being used for creation of PO in classic scenario

Hello Experts,
We are in SRM 7.0 classic scenario.
How can we know which BAPI is being used in the calssic scenario i.e. How can we know if we are usind BAPI_PO_CREATE or BAPI_PO_CREATE1 for creation of PO?
Any pointers will be highly appreciated.
Thank you in advance,
Thanks & Regards,
RKS

Hi RKS
yesterday BLOG by our SUMMER WANG helps every SRM consultant to debug the PO error
/people/summer.wang/blog/2010/05/11/trouble-shooting-of-srm-po-transfer-error
Good work Summer wang !!
Muthu

PO creation problem with classic scenario

Hi All,
We are in SRM 7.0 nad have mapped extended classic scenario. Now we want to map the Classic scenario only for a specific company code. So, my question is can we map the classic scenario on company code specific.
I tried maintianing the document type & number ranges in R/3. Maintained the number ranges & transaction type in SRM.
Also implemented BADI BBP_EXTLOCALPO_BADI.
But after creating the SC the status is "Approved" but no PO getting created in ECC. On observing RZ20 there is an system error for the number ranges.
Please let me know if I am missing some steps.
Thanks in advance.
Regards,
Abey.

HI,
Make sure the PO number range in ERP is same in SRM. Also have the external checkbox checked for PO number range in ERP.
Also have the same transaction type in SRM and ERP. Where the ERP transaction type should have external number range as the above mentioned profile.
Regards
Sam

Extended Classic Scenario, BADI for PO creation in R/3

Hi,
We are using the extended classic scenario. When the PO gets replicated from SRM to R/3, right now the field CATALOGID is not being transmitted to the backend R/3 system.
1) What BADI should I implement (and the method) to transmit the CATALOGID to R/3?
2) After implementing the BADI, do I also have to change the BAPI?
3) Is the BAPI used to transfer data from SRM to R/3, BAPI_PO_CREATE?
Thanks and Regards,
Peter

Hi Peter,
1-You can use BBP_ECS_PO_OUT_BADI for ECS scenario.
Since the R3 PO does not have field for catalog id, the EKKO- BEDNR (Tracking Number) field can been used for example to store this information. In this BADI all the items are identified and their tracking number field is populated with a catalogue id value.
2-If you use the tracking number field, no use of R/3 BADI is required.
3-BAPI_PO_CREATE1
Please check my answers in this post :
catalogid field not going in R3 backend
Kind regards
Yann
Message was edited by: Yann Bouillut
Message was edited by: Yann Bouillut

Shopping Cart and PO creation - Classic Scenario

Hi,
SRM 5.0 - Classic Scenario
User U-1 is under the company code C-1
Shopping Cart SC-1 has been created successfully for the Product Category PC-1
Product Category PC-1 has been assigned to Purchasing Org. POrg-1
Question 1)
But back-end POrg-1 has NOT been assigned to Company Code C-1. What will happen to this SC-1 ? Will the PO be created ?
Question 2)
Next....Vendor V-1 has been assigned as Source for the Shopping Cart SC-1.But Vendor V-1 has NOT been extended to the Purchasing Org POrg-1. But it has been extended to the POrg-2.
Will the above SC-1 will be converted as PO ?
Please help. Currently I am doing blueprint. I don't have the system to do the above test.
With regards,
Pranav

Hi Pranav,
Here are answers to your questions;
Question 1)
But back-end POrg-1 has NOT been assigned to Company Code C-1. What will happen to this SC-1 ? Will the PO be created ?

Sundeep: No, This PO will be in "Error in Transmission" with a backend application error for a PO. Same as trying to create it directly in ECC, it will error
Question 2)
Next....Vendor V-1 has been assigned as Source for the Shopping Cart SC-1.But Vendor V-1 has NOT been extended to the Purchasing Org POrg-1. But it has been extended to the POrg-2.
Will the above SC-1 will be converted as PO ?
Sundeep: No, it is same as trying to create a PO in ECC directly, it will not allow you to create it. Also this scenario is not practical, as in reality, when you replicate vendors from a backend, it will replicate all Porgs that the vendor is created with, hence this scenario concern is ruled out !
Thanks,
Sundeep

Creation PO in classic scenario in backend

Hi,
I'm in classic scenario with plan driven. I'm using SRM 5.5
I'm using bid engine and i'd like to create a PO in backend directly from a bid.
What do I need to get it?
thanks in advance
Best Regards

Hi
As per this SAP OSS Note 762223... you can try this out..
I guess this OSS Note, will be applicable to SRM 550
Releases
Software
Component Release From
Release To
Release And
subsequent
SRM_SERVER 500 500 500
SRM_SERVER 550 550 550
BBPCRM 4.0 400 400
You can try this out.. Hope this will help.
Regards
- Atul

Classic scenario service PO replication

Scenario:-
Classic Scenario
No PI(Process Integration)
No PDP (Plant Driven Procurement) process
Today we created new Service purchase requisition (which is never adopted for PO creation) which contains only one item(10), under this line item (10) five service Numbers…as 20000000(Line-10),20000021(Line-20),20000025(Line-30),20000033(Line-40),20000058(Line-50)
then
Our process:-
Purchase Requisition(Service) Transferred from ECC to SRM - >Purchase Requisition Converted in to shopping cart in SRM> Shopping Cart goes to sourcing -> buyer
creates RFx by adopting the Shopping Cart -> RFx is sent to bidder -> bidder will respond >RFx Response number will be created in SRM>Buyer will compare the RFx responses -> Buyer will click on the RFX response number of L1 vendor>in the RFX response screen when he will click on the “CREATE Purchase Order”
Issue:- why in Service PO items are splitted in to item-10,item-20,item-30,item-40 which is not same like in Service PR
Hope if above issue will solved below error message wont appear
Error Message:-
Materials of requisition 2100000654 item 00010 alr. ordered in full
Message no. 06076
Please Find the attached screen shot
Thanks
Madhu

Can you please elaborate more on this .
from what I understand you want the SC item to not split into different PO generally it spits based on different shipping address maintained . You can also check this in BADI ZBBP_GROUP_LOC_PO
Below is a sample code I found from one of the earlier threads as below :
http://scn.sap.com/message/2772557#2772557
http://scn.sap.com/message/3155145#3155145
http://scn.sap.com/message/2877448#2877448
http://scn.sap.com/message/2371974#2371974
https://scn.sap.com/thread/2026160
https://scn.sap.com/thread/54153
METHOD if_ex_bbp_group_loc_po~group_po. 
*------------------------------------------------------------------------------* 
* Exit Grouping of Items for Local Purchase Orders 
** Parameters 
*ITEM_DATA TYPE BBP_INT_ITEM_GROUP Item Data for Shopping Basket Item 
*It contains the most important item details of the shopping cart and 
*additionally in the field REFNUMBER a reference number for further 
*processing purposes 
*------------------------------------------------------------------------------* 
* Method used to group item before PO creation 
* How it work ? 
* 1/ Select extra colons from table ZPO_SPLIT_CRITER 
* 2/ Getting Compoents from existing type BBP_INT_ITEM_GROUP 
* 3/ For each line recalcul Refnumber 
********************************************************************** 
* Declarations 
********************************************************************** 
*--------------------------------------------------------------------* 
* Variable 
*--------------------------------------------------------------------* 
DATA: lt_zpo_split_criter TYPE TABLE OF zpo_split_criter 
 , ls_zpo_split_criter TYPE zpo_split_criter 
 , lo_struct TYPE REF TO cl_abap_structdescr 
 , lt_field_list TYPE ddfields 
 , ls_field_list TYPE dfies 
 . 
 
DATA: 
 lt_item_data TYPE bbp_int_item_group 
, ls_item_data TYPE bbp_int_item_groups 
, ls_back_data TYPE bbp_int_item_groups 
, ls_modi_data TYPE bbp_int_item_groups 
, l_fname TYPE fieldname 
, l_refnumber TYPE refnumber 
, l_tabix TYPE sytabix 
, l_not_empty TYPE c 
, l_act_not_empty TYPE c 
. 
*--------------------------------------------------------------------* 
* Field symbols 
*--------------------------------------------------------------------* 
FIELD-SYMBOLS: <lfs_refnumber> TYPE bbp_int_item_groups-refnumber 
 , <lfs_act_refnumber> TYPE bbp_int_item_groups-refnumber 
 , <lfs_field_value> TYPE ANY 
 , <lfs_act_field_value> TYPE ANY 
 . 
*--------------------------------------------------------------------* 
* Constants 
*--------------------------------------------------------------------* 
* CONSTANTS: 
* . 
********************************************************************** 
* Process 
********************************************************************** 
* 1/ Select extra colons from table ZPO_SPLIT_CRITER 
SELECT * FROM zpo_split_criter INTO TABLE lt_zpo_split_criter 
 WHERE split EQ 'X'. 
CHECK NOT lt_zpo_split_criter[] IS INITIAL. 
DELETE lt_zpo_split_criter WHERE fieldname = 'REFNUMBER'. 
 
* 2/ Getting Compoents from existing type 
lo_struct ?= cl_abap_typedescr=>describe_by_name( 'bbp_int_item_groups' ). 
CALL METHOD lo_struct->get_ddic_field_list 
 EXPORTING 
 p_langu = sy-langu 
 p_including_substructres = abap_true 
 RECEIVING 
 p_field_list = lt_field_list 
 EXCEPTIONS 
 not_found = 1 
 no_ddic_type = 2 
 OTHERS = 3. 
IF sy-subrc <> 0. 
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO 
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. 
ENDIF. 
 
LOOP AT lt_zpo_split_criter INTO ls_zpo_split_criter. 
* Verify if field exist in table 
 READ TABLE lt_field_list 
 TRANSPORTING NO FIELDS 
 WITH KEY fieldname = ls_zpo_split_criter-fieldname. 
 CHECK sy-subrc EQ 0. 
 
* Copy table in internal 
 lt_item_data[] = item_data[]. 
 
* Sort table by REFNUMBER and fieldname 
 SORT lt_item_data 
 BY refnumber (ls_zpo_split_criter-fieldname) 
 ASCENDING. 
 
* Clear internal value. 
 CLEAR: l_refnumber 
 . 
 
 CONCATENATE 'LS_ITEM_DATA-' ls_zpo_split_criter-fieldname 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_act_field_value>. 
 CHECK sy-subrc = 0. 
 CONCATENATE 'LS_BACK_DATA-' ls_zpo_split_criter-fieldname 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_field_value>. 
 CHECK sy-subrc = 0. 
 CONCATENATE 'LS_ITEM_DATA-' 'REFNUMBER' 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_act_refnumber>. 
 CHECK sy-subrc = 0. 
 CONCATENATE 'LS_BACK_DATA-' 'REFNUMBER' 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_refnumber>. 
 CHECK sy-subrc = 0. 
 
 CLEAR: <lfs_refnumber> 
 , <lfs_field_value> 
 . 
 
* For each reccord in table, calculate new REFNUMBER 
 LOOP AT lt_item_data INTO ls_item_data. 
 MOVE sy-tabix TO l_tabix. 
 IF <lfs_act_field_value> IS INITIAL. 
 MOVE ' ' TO l_act_not_empty. 
 ENDIF. 
 
 IF ls_zpo_split_criter-as_not_blank IS INITIAL. 
* Case of each value on field create a new refnumber 
 IF <lfs_field_value> NE <lfs_act_field_value> OR 
 <lfs_refnumber> NE <lfs_act_refnumber> . 
 l_refnumber = l_refnumber + 1. 
 MOVE <lfs_act_field_value> TO <lfs_field_value>. 
 MOVE <lfs_act_refnumber> TO <lfs_refnumber>. 
 ENDIF. 
 ELSE. 
 IF l_not_empty NE l_act_not_empty OR 
 <lfs_refnumber> NE <lfs_act_refnumber> . 
 l_refnumber = l_refnumber + 1. 
 MOVE l_act_not_empty TO l_not_empty. 
 MOVE <lfs_act_refnumber> TO <lfs_refnumber>. 
 ENDIF. 
 
 ENDIF. 
 ls_modi_data = ls_item_data. 
 ls_modi_data-refnumber = l_refnumber. 
 
 MODIFY item_data FROM ls_modi_data INDEX l_tabix 
 TRANSPORTING refnumber. 
 ENDLOOP. 
ENDLOOP. 
 
ENDMETHOD.
 
 
 
It works with the table ZPO_SPLIT_CRITER as bellow: 
CLIENT MANDT 
FIELDNAME FIELDNAME 
SPLIT BOOLE_D 
AS_NOT_BLANK BOOLE_D 
 
If you need more information, contact me directly. 
Regards, 
 
David BOUTIER 
Consultant technique Sap Netweaver - KALYDIA 
8, rue Pasquier - 75008 Paris

External requirement handling in SRM using classic scenario

Hi Experts,
We have a requirement in Classic scenario:
PRs for MRO / indirect materials generated in PM / PS of ERP will be transferred to SRM using WF interface for approval process.
Upon final approval in SRM, Follow-on document PO should be created in the back end.
The SC in SRM should have the status u201CApprovedu201D & u2018Follow-on Documentu2019 created.
My question is SRM standard will create a PO as follow-on doc after the SC is approved in SRM. How to control this creation of PO in SRM & only approval message should be transferred to back end ERP.
Pls provide any suggestions or inputs on technical settings / adjustments to be carried out.
Note that we cannot use PDP scenario as SRM will be used only for SC approval process.
Tks.

Thanks Muthu for the reply.
The doc flow in the link above shows that after SC is approved, it will be available in sourcing cockpit for further processing (i.e. RFX, PO etc) in SRM. Our requirement should not be allowed to create PO in SRM and it should be allowed only in back end ECC.
SRM is used to centralize the approval process where multiple back end systems are connected. (How ever, in future follow-on docs are also created in SRM).
Current Target steps:
1. Create PR from PM/PS in ECC (PR status will be "In release").
2. Transfer PR to SRM and SC will be created (SC status will be "In approval").
3. SC will be Approved / or Rejected in SRM. (PR status will be updated to Approved / or Rejected in ECC).
4. If approved, follow-on doc PO (manual or automatic) will be created in ECC. (SC status will be updated to EX: "PO cretaed")
When the SC is in the process of approval, user in ECC may add new items or make changes to PR from PM/PS. After these changes, the current approval WF for SC in SRM should be cancelled and new SC is created and so on...
Sophisticated message synchronization is required between ECC & SRM.
Is it possible to acheave the above solution (create PO only in back end system) using the steps mentioned in doc "5082a622-7310-2c10-1a9b-ef31dd69a770.pdf" with some modifications.
Forgot to mention the following system details:
ERP - ECC with EhP4
SRM - SRM 7.0
Thanks,

:):(Creation of RFX or LAC in a Classic Scenario:):(

Similar Messages

Maybe you are looking for