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

Similar Messages

PO not generated at backend in classic scenario

Hi,
I am working with SRM 5.0 in classic scenario.
1) I have defined No. ranges for SC and follow-on documents in SPRO. No. range PO is defined for backend (classic) POs. (Checkbox -External is not marked)
PO - From 3005000000 to 3008000000
2) I have assigned this no. range PO to document type 'EC' (Pur Order) as external no. range
3) No. range PO is also defined at R/3 backend for Purchase Orders (checkbox 'External' not marked)
PO - From 3004000000 to 3009999999
4) This no. range is assigned to doc. type EC as Internal no. range in R/3 backend
Now, when I am creating a SC in SRM and ordering it, it is causing an error in creation.
I see the following description in Admin login:
Shopping cart 6500005899 (PO 3005000532): BAPI 001 No instance of object type PurchaseOrder has been created. External reference:
PO no. 3005000532 is picked from no. range PO defined in SRM.
But, in SC screen, I do not see any follow-on documents.
When I check BBP_PD, I find following data:
BE_OBJECT_TYPE    -> BUS2012         -> Follow on Document Object Type in backend system
BE_OBJECT_ID      -> 3005000535       -> Follow on Document Object ID in backend
(However, this no. belongs to no. range PO defined in SRM. At the backend, the PO no. range starts from 3004000000 to 3009999999)
BE_INFO_REC    -> 5300002566
Also, I can see two lines highlighted in Red under Stats:
                       Status                            Description                 Inactive
HEADER          I1015                         Awaiting Approval                X
0000000001      I1111                    Item in Transfer Process           X
My doubt is that ,
a) Why system is picking PO# from SRM no. range (3005000535) and showing it as backend object ID?
b) When system is able to fetch the Info record information from backend, why the PO is not getting generated at the backend?
Why there is an error in transmission of PO?
Please help.
thanks

plz see Peter instructions in this thread
SC: Error in transmission BAPI 001
regards
Muthu

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

Central Contract Management in case of Classic Scenario

Hi,
At our current implementation, requirement is to implement both Service procurement(with hierarchy) and Central Conract Management. I was exploring the possibility of utilizing Central Contract Management with Classic scenario.
Will the Central Contracts created in this fashion be available in Sourcing Cockpit for the buyer to select against Purchase Requisitions? Will the Central Contract be visible at all in SRM in this case ?
Please respond only with reference to Classic scenario.
Thanks,
Abhilash

Yes the Central Contract will be available in the Sourcing Cockpit, both local and classic scenario's. Yes the Central Contracts will be available for the creation of Purchase Requisitions in R/3 and to assign SOS in R/3.
Do know that for SRM 7.0 PI is required for setting up Central Contracts. This is promised to change with the release of EHP1 for SRM (due june 2010).
Kind regards,
Tim

Number of document created in th backend in the classic scenario?

Dear Experts,
Could you please tell me the number of document and its details created in the ECC backend in the below cases?
1. Case 1:
Define backend objects:Purchase requistion created if no stock available.
Is it correct that the system will create two documents here? The first document will be Purchase Requisition
( from the classic scenario) and then a purchase order has to be triggered manually from the PR?
2. Case 2:
Define backend objects: Purchase Order if data complete, otherwise Purchase requisition.
Here, if all the data are complete and the system directly creates Purchase Order in the ECC backend system. From the shopping cart in SRM, one can see only ECC backend purchase order, no purchase requistion. If i check the Purchase Order in ECC backend system, I donot see any purchase requistion with reference to the Purchase Order.
Could you please help here? What are the number of documents created here? It is one or two (both purchase requisition and Purchase Order).
Is it not a violation of standard classic scenario if only one document is created?
Thanks and regards,
Ranjan

Hi,
In other words in the shopping cart is approved
1) If the source is assigned -It will create a P.O in the backend (Classic)
2) If the source is NOT assigned -It will create a P.R in the backend (Classic) .. you have to assign a source
Regards
G.Ganesh Kumar

SRM 5.0 Switching over from EC to Classic scenario

Hello Folks,
We are working in SRM 5.0 Extended classic scenario and the current need is to swipe from EC to the Classic scenario.
I thought it would be a click (uncheck Activation of the EC) and go. But to my surprise, system repeatedly is failing to transmit the Shopping cart into the back-end ECC 6.0 system.
Well...working into Vanilla SAP, my notion is there will be no need to activate any BAdis. Hence no BAdi implementation can be seen active in my system.
Please advice.
Thanks in anticipation.

Hi Marcin,
Thank you so much.
I awarded points for your help.
one quick issue, I am facing problem in posting invoice without reference to the PO. Error message was, "No logical system for FI is maintained. Inform system admin".
It sounds strange as I do have ECC as a solo back-end system. Second, I suppose I did best in assigning the logical system to ACS and SYS (PPOMA_BBP). Can you share your insight.
PS : I know it should be altogether a new thread. Be rest assured I will do all my best to reward your assistance !
Thanks.
Reg,

Extended Classic Scenario - SHC: Buffer table not up to date

Hello all,
I'm working in SRM_SERVER 550, SAPKIBKT11, and having issues using BACKEND PURCHASING ORGANISATIONS and the Extended Classic Scenario.
According to SAP note 944918 the following indicator should not be required to be set:
Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario --> extended classic scenario active.
I did set the Backend Purch. Grps Responsible indicator, and I did create organizational units specifically for the backend purch. grps.
We need to set the main part of all SHCs to ECS, but when I do set the indicator in customizing to "extended classic scenario = active", I get a dump in my web environment: 'buffer table not up to date'.
What is causing this failure in my SHC?
I tried to implement BAdI "BBP_EXTLOCALPO_BADI" (method DETERMINE_EXTPO) like described below here: without the line bbp_extpo_gl-bbpexpo = 'X'., I can continue and create the SHCs. Problem is though: all SHCs will get marked as Classic Scenario. So, to make sure the SHCs will always get marked as ECS, I have added this line in the BAdI. Unfortunately this immediately results in the 'buffer table not up to date' error in the SHC itself, as soon as I try to open the details of the new item.
Hope you help me out here?? It doesn't seem to be related to the BAdI, but somehow the system doesn't allow me to mark SHC items as ECS.
Thanks & Regards,
Berend Oosterhoff
SRM Consultant Accenture Technology Solutions - The Netherlands.
BAdI BBP_EXTLOCALPO_BADI:
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
data definition----------------------------------------------------*
DATA:    wa_mattype     TYPE BAPIMATDOA,
           wa_char18      TYPE MATNR,
           attrib_tab     TYPE TABLE OF bbp_attributes,
           wa_attrib_tab TYPE bbp_attributes,
           wa_value       TYPE om_attrval,
           wa_product_id TYPE comt_product_id.
    bbp_extpo_gl-bbpexpo = 'X'.
from here I did the specific selection for the SC, but that's not relevant here.

Hi Prashant,
Thanks for your quick reply!
Note 1085700 is about Short Dumps when creating or changing a contract. I am trying to create a Shopping Cart, without a reference to a contract. BAdI BBP_DOC_CHANGE_BADI is not active in our system.
Any other thoughts?
Regards,
Berend

Purchase Order Response in Classic Scenario

Hi Experts,
Implementation Scenario- CLASSIC
SRM Server - 5.0
Question-
1) Within Classic Scenario, is it possible for to create Purchase Order Response in SRM for a PO which is already created in backend? This PO is generated by a shopping cart in SRM.
Best Regards,
Amit

Hi Amit,
You can create POR for a PO which is already created in backend, no matter if its created with reference to SC in SRM. This POR would be done by the supplier in SUS scenario.
It possible in both, classic and ECS scenario's.
Regards,
Prashant

Inforecord price for SRM originated orders - CLASSIC scenario

Hi! Few months' back, I have posted some questions re the behaviour of the price on the PO when orders are generated out of SRM in a classic scenarioI have just completed testing and ended up with the following results:
1. If I create a shopping cart with material number for direct consumption and have a vendor defaulted from vendor list, the price reflected in the PO is from the inforecord. So, effectively, I could have $1000 on my shopping cart but PO showing $950 as this is the value in the inforecord. The $1000 comes from the material condition record in SRM (extracted via EBP_GET_BACKEND_PRICES).
2. If I create a shopping cart with material number for STOCK and have a vendor defaulted from vendor list, the price reflected in the PO is that maintained on the shopping cart. Is this behaviour correct? Note that in this case, the master PO is in SRM even in a classic scenario and I wonder whether it is because of this that the pricing behaviour is different.
Other observation: For stock purchase, I know that if I have multiple vendors (from vendor list and some from inforecords) and if I picked one of the vendors, the price will be adopted at the point of shopping cart so that the user has a 'confirmed' view of the price and there should be no discrepancies of prices between the shopping cart and the PO.
Can someone please shed some lights as to what should the standard behaviour be?
Cheers!
SF

hello SF
rule :- shopping cart price is a material price and it comes from your report and prices are stored in COMMPR01 .( EBP_GET_BACKEND_PRICES BY this report).
really the prices are picked from source of suooly like infor record , vendor list or contract while creating the purchase order.
i create a shopping cart for 100 USD since material price is 100 usd but PO created for 75 USD.
since contract material price is 75 usd.
With regards to using report EBP_GET_BACKEND_PRICES to upload the
prices from the backend system into EBP. Please refer to the online
documentation of this report:
'Under "Price reference per product", you can specify if the average
value of all valuation groups/plants is to be calculated or if the
valuation price from the first valuation group/plant is to be used. If
the average value is to be calculated, choose "Average of all prices".
If you wish to use the first valuation price, choose "Use first price".
The standard setting calls for the "Average of all prices" to be
calculated.'
This is how this report works. If you want to take another price you
have to change the coding according your requirements.
You will need to debug into the backend through
RFC-Call for backend-table MBEW
CALL FUNCTION 'RFC_READ_TABLE' DESTINATION iv_rfcdest
in FORM read_mbew and see the select statement that reads this table.
The report is taking exactly one price out of the data
package extracted out of R/3. If this could also be a moving average
price is more a question which kind of data is extracted out of of R/3
and how the R/3 config looks like - and if this moving average is in thelist.

Extended classic scenario - no backend PO created

I try to activate the extended classic scenario. It's not activated in customizing, tried to do it only with BADI implementation for special material groups. We are able to create POs in SRM but transfer to backend doesn't work.
I get following error messages in application monitor as backend application errors:
No instance of object type PurchaseOrder has been created. External reference:
PO header data still faulty
Document number 100000093 not within defined inter val
What's going wrong here?
Hubert

Hello,
Check if you have set up the customizing as below:
Extended classic scenario:
a) at SRM side:
- To assign the transaction type to the extended classic scenario you have to maintain the transaction type name (= the R/3 PO document type) to the attribute DP_PROC_TY (in contradiction to BSA in classic scenario) in PPOMA_BBP of the responsible Purchazing group.
- Create a number range for a local PO.
- Assign the local PO number range as a internal numer range to the transaction type.
b) at R/3 side:
- Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range (trx. OMH6 Number Range for Purchasing Documents)
- Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range for POs as "NoRge Ext" (field V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)
- Make sure that the SRM and R/3 number ranges match are exactly the same.
Kind regards,
Ricardo

Configuration steps for Extended Classic Scenario

Hi All,
Could you please let me know what are the configuration steps required for extended classic scenario.
Thanks in advance

Hi,
Important Settings that Determine the Extended Classic Scenario
The following settings are required for the extended classic scenario:
u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
This is for your additional information.
Hope this helps.
Regards,
Vikas

Status I1113 missing in SC in Extended classic scenario using TA BBP_POC

Hi all,
I am using SRM in extended classic scenario (ECS) (SRM Server 5.5) SP09.
1. Scenario (without any problems)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
No problems at all using standard Sourcing Cockpit -> POs are replicated to R/3, status correctly transfered into Shopping Carts (Status I1113 after creating a PO out of SC).
2. Scenario (problems concerning Status I1113 in SC)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
Shopping carts are manually transfered into a local PO by using standard transaction BBP_POC (create PO) -> function "Add shopping cart item" within item data
Local PO is created without any problem, sucessfully replicated to R/3 and if I start the Monitor for shopping carts I get all the detailed information (follow on documents) -> PO number etc.
Problem: If I use TA BBP_POC and add these shopping carts to PO positions, the status I1113 is not written to SC after executing BBP_GET_STATUS_2 and CLEAN_REQREQ_UP .
The SC remains in Status I1106 (Shopping Cart ordered) / I1129 (approved)
I cant find any entries in table BBP_DOCUMENT_TAB and the shopping carts have been removed from SoCo after creating a PO out of it...
Does anybody uses Transaction BBP_POC in ECS and adds Shopping Carts to POs?
Any Idea why the status for these SCs is just I1106 "Shopping Cart ordered" but status I1113 "Follow-on Document Created" is missing/not updated?
Best regards,
Andreas

Hi
Please go through the SAP OSS Notes below ->
Note 1053433 Extended classic: Incorrect status shown in check status
Note 730239 Check status: Missing Backend reference
Note 819094 shopping cart monitor:Update status after resubmit shop.cart
Note 825761 Report program for shopp. cart status update after resubmit
Note 768164 Multiple SCs via SoCo are processed incorrectly
Note 729967 Shoppng cart:Status I1111,no follow-on docs->analysis report
Note 728536 Shopping cart: Follow-on docs => analysis-/correction report
Note 704941 EBP 3.0: Status error in SC extractor
Note 486246 Incorrect shopping carts offered for confirmation
Do let me know.
Regards
- Atul

Limit items on extended classic scenario.

Hi everybody.
We are working in SRM 4.0 with extended classic scenario.
We are testing limit items (not service items), but I can not understand the limit item functionality.
In SC, we can assign contracts form limit items. But when we create PO from the SC, there is not any relationship between PO and contract. Moreover when I create a PO (limit item) from null, I can not assign any contract (field is not available).
In the other hand, in SC (limit item), I can select Follow-Up Actions as Confirmation and Invoice or Invoice. If I select Confirmation and Invoice, when I create a PO, ECC return me a message error, because in ECC, good receives are not allowed for PO with limit item category.
So, I have some questions:
1. Can I use limit items in PO with contract reference?
2. If yes, how can I do it? If not, what is the tab contracts functionality in SC with limit items?
3. What is the functionality to allow confirmations in SC with limit items?
4. Is there any documentation about limit item functionality?
Thanks and regards.
Raúl Moncada.

Hello,
As far as I know, this is a technical limitation. A work around would affect other functionalities.
Note 1358679 corrected such issue.
Regards,
Ricardo

Classic scenario & Extended classic scenario

Hi Experts ,
I am new to SRM , Is it possible to combine both classic scenario & Extended classic scenario . if it possible , then how to achieve this .
Regards
Vel.

Hi Vel
I suggest that instead of checking the possibility of implementing any combined scenario's like how you have asked ( Classic+Extended classic scenario).
You need to map the Business requirement and how the Business teams wanted to handle the PO ,GR etc and accordingly you have to plan for implementation scenario. You can' customise the standard SRM delivered options for these scenario . I t is advisable to either go for Classic or Extended classic.   But combination of Classic & stand alone scenario is possible.
for your ready reference i have given below capabilities of all scenarios, which you may already know..
Key implementation scenarios
u2022     Classic
o     Implement EBP and one or more ERP system . All shopping carts refer to MM process in your ERP backend, your   ERP is the leading system. GR (Confirmations and invoices can be entered in Enterprise Buyer or ERP back end system
u2022     Extended classic
o     Purchase order is created locally within EBP system , if the data in the shopping cart is insufficient to generate a complete purchase order. The data is supplemented manually within the enterprise buyer system EB is the leading system , GR,IV can be done in both EBP and ERP system.
u2022     Decoupled
o     Combination of classic and standalone scenario ,some items are locally handled, some items are transferred to the ERP back end system
o     We are able to send PO from both the system.
u2022     Standalone
o     Your SC items create local procurement only, this means all the follow on doc like GR,IV will be done at EB system only.
o     Only commitment & invoice posting will be done at ERP backend
You can get the final Business requirement and plan.
Regards
Narahari

Extended Classic Scenario not creating backend PO

Hi All
We are just starting with SRM (Using SRM 5.0 SRM Server 5.5) and trying to decide to use Classic or Extended Classic.
I can get the Classic working were an approved SC creates a backend PO without any problem. However when I switch on Extended Classic the backend PO is not created from an apporved SC.
In RZ20 my error is Shopping cart 1000000080 (PReq. ): BBP_BD 002 Buffer table not up to date and Table BBP_DOCUMENT_TAB is empty
In config I activated the extended classic scenario as well as activating the backend purchasing groups as responsible. Under sourcing I also defined for the relevant product categories as "1 - Sourcing Never Carried out"
Am I missing something obvious??
Many thanks for any help.
Daniel

Hi Daniel,
In reference to the info. you have provided, it looks like you have not switched to Extended Classic Scenario properly.
Once you say you are on ECS, the P.O should get created in SRM and the copy of it should get replicated to R/3.
As you said you have flagged both the check boxes in SPRO for ECS activation, try activating sourcing also.
SPRO > IMG > SRM > SRM Server > Sourcing > Choose one Product category for which you want to create shopping cart and set the setting as " Sourcing Always carried out".
Check whether the approved shopping cart is coming to Sourcing cockpit or not.And from there try to create a P.O by assigning vendor.
Also ensure that no BADI is activated which converts ECS to Classic scenario for the Product category you have choosen.
If this cycle woks then definitely what you require will also work.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Reference to SC in classic Scenario

Similar Messages

Maybe you are looking for