Limit shopping carts in extended classic scenario

How can we implement limit shopping carts in extended classic scenario. Has anyone done it? Thanks in advance

Hi
Which SRM version are you using ? It's possible to implement limit items concept in ECS Scenario.
What exactly you are looking for ?
Please have a look to the following links as well.
http://help.sap.com/saphelp_srm50/helpdata/en/40/654d216f12754e9decdaf4d360bc1c/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/d1/77623c44696069e10000000a11405a/frameset.htm
Few SAP OSS Notes to refer in this case.
Note 712702 ECS shopping cart with several limits
Note 724261 Limit: Error during creation of local purchase order
Note 694442 Limit SC: Customer fields not transferred to backend PO
Note 690000 Limit SC: Customer fields not transferred in Backend PO
Note 699255 Internal note and vendor text for LimitPO and LimitPReq
Note 501977 Error with limit SC: "Unit measure has no ISO code"
Note 520514 Limit, BBP_PD148: No account assignment details were adopted
Note 514727 Limit: Contracts are not displayed in the status
Note 516444 Account assignment check in the shopping cart with limit
Note 515500 Limit:'Confirmation and invoice' indicator not transferred
Note 515695 Invoice entry for limit shopping carts not possible
Regards
- Atul

Similar Messages

Tax calculation for a shopping cart in extended classic

Dear experts,
Can any one kindly explain me the taxcalcuation process for shopping carts in extended classic scenarios.
For example if I create a shopping cart for 1000 INR, tax is at 15% VAT total value will come 1150 INR.
How this calculation is happening, please explain me the config settings in backend (ECC) if any required.
Thanks for your help,
Regards,
Krish

Hi
First of all you need to define the tax code inECC at FTXP and after you need to define the tax producre like mm pricing.
go to mm config to do the appropirate calcualtuion procedure.
Regards
satish

Display info records while creating a shopping cart in Extended Classic

Hi ,
i am working on Extended Classic Scenario in SRM 5.0.
I have created an info record in R/3 Backend.
when i create a shopping cart with the relavant information system is not showing up the required info record that is maintained in the R/3 system.
Please respond to this problem ASAP.
Thanks,
mahesh

Hi,
See the foll threads:
Assign the Info-record to SOS automatically.
Re: Contract preference over PIR in SOS in Classic Scenario
BR,
Disha.
Do reward points for useful answers.

Adding Custom Field to Shopping Cart and PO, Classic Scenario

We are running SRM 7.0 with ECC 6.0 as the backend and using the Classic scenario. I want to add a custom field to the shopping cart and have the data transfer over to a custom field (of the same name) on the purchase order to the ECC side. I have already added the field to the shopping cart and have the data saving successfully there on the SRM side. What I am having trouble with is getting the data from the custom field to go over to ECC on the purchase order.
I have extended the Shopping Cart and Purchase Order item structures through configuration on SRM. This has added the fields to the INCL_EEW_PD_ITEM_CSF_SC and INCL_EEW_PD_ITEM_CSF_PO structures, as described in note 672960 (do i need to extend the PO structure on SRM if using the Classic scenario?). I have also extended the CI_EKPODB and CI_EKPODBX structures on ECC as described in note 458591. So the placeholders are there.
I feel like there must be something I am missing. The OSS note 458591 suggests that just adding the fields to the needed structures will cause the data to transfer, but this does not appear to be the case.
I have an implementation of BBP_CREATE_BE_PO_NEW that I can use, but do not see where to add the data in the output parameters of that BADI. Is there a BADI I need to implement on the ECC side?
Any help in this issue would be greatly appreciated.

Dug around a little bit more and stumbled onto this article which solved it for me: [How to transfer custom fields from SRM to ECC|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20b36c12-685f-2c10-4fb4-ba2e0b969c27?quicklink=index&overridelayout=true]
In BADI BBP_CREATE_BE_PO_NEW I had to add some code to fill in the CS_PO1_DOCUMENT-EXTENSIONIN parameter table with the structure for the BAPI_TE_MEPOITEM structure on the ECC side. The tricky part is creating a string representation of that structure with the correct offset. And it isn't as easy as just counting up the number of characters in SE12. For example, looking at my BAPI_TE_MEPOITEM structure in SE12, my custom field appears to start on character 157, but in reality, I had to offset the writing of my value to character 143. I guess it depends on what types are in there.
But once that gets figured out, it works well. As long as the custom field is added correctly to the CI_EKPODB append structure (which is appended to BAPI_TE_MEPOITEM), the data gets tranferred over in the ExtensionIn table, and SAP automatically knows what to do with the data as long as you have everything in ExtensionIn aligned correctly.
Thanks for the help everyone!

SRM XI Content for Shopping Cart model (Extended Classic)

We've loaded the XI content for SRM (XI7_0_SRM_SERVER_7.xxxx) from the sap marketplace and reviewed the data types, messages, and interfaces. It appears there are no pre-built integration scenarios associated with a Shopping Cart model (Purchase Orders, Advance shipment notice, etc). Does a set of pre-built integration scenarios exist, or are these generally built manually? We are going to be pushing purchase orders from ECC to SUS in most of our scenarios. Thanks in advance.

Usually SAP provides the integration scenarios with template systems. But you can always create your own integration scenarios in your own SWC by making a dependency in SLD and using the Interfaces/Message Types and Datatypes in the SAP standard content.
VJ

Extended Classic Scenario causing a dump "Buffer Table not up to date'

Hi All,
I could create a Shopping Cart in the Classic Scenario.
After activating the Global settings together with the Back end groups responsible for the ECS, I have also a Badi in place for a certain Category id..I expected that for this category id if I create a shopping cart thro' the describe requirement it would create a Local PO and a replica would be generated in the Back end system.
But as and when I add the item to the Shopping Cart, I get an ABAP Dump indicating the buffer table not up to date and a program error "Uncaught exception" in the Program SALBBP_PDH.
I also tried searching SAP Notes,but to vain.Working on SRM 5.0 Release level 12 and ECC 6.0 as back end.
Any body who has faced this before, Pl give me the clues.
Thanks & Regards,
Nagarajan

Hi
it is basis consulatant responsiblity. you must take help from Basis .
Note 26171 - Possible entry values for command field ("OK-code")
Buffer commands:
WARNING: Resetting buffers can significantly change the performance of the
entire system for a long time. It should therefore only be used when there
is a good reason to do so. As of release 3.0B system administator
authorization is required (authorization object S_ADMI_FCD). The action is
noted in the system log.
/$SYNC- This resets all buffers of the application server
/$CUA - This resets the CUA buffers of the application server
/$TAB - This resets the table buffers of the application server
/$NAM - This resets the nametab buffers of the application server
/$DYNP - This resets the screen buffers of the application server
regards
Muthu

Classic / Extended Classic Scenario for Shopping Cart

Dear Friends,
We are working on two different business scenarios with same Product type, Product and Product Category where we would like to control Extended Classic Scenario.
1. Self Service procurement to be executed in Classic Scenario as the follow-on document (Purchase Requisition) should be created in backed ECC system.
2. Plan Driven Procurement cycle where External requirement is transferred from backend ECC to SRM keeping Extended Classic scenario active so that system creates Shopping cart in SRM.
So which condition should I use to control the Classic / Extended Classic Scenario in BADI BBP_EXTLOCALPO_BADI method DETERMINE_EXTPO.
Regards,
Sandeep Parab

Thanks Pierre,
My Sourcing requirement is working as desired with following code in BADI BBP_SRC_DETERMINE (method DETERMINE_SOURCING).
method IF_EX_BBP_SRC_DETERMINE~DETERMINE_SOURCING.
DATA: w_header TYPE BBP_PDS_SC_HEADER_D.
CALL FUNCTION 'BBP_PD_SC_GETDETAIL'
EXPORTING
    I_GUID = HEADER_BBP_GUID
IMPORTING
    E_HEADER = w_header .
IF sy-subrc = 0.
IF w_header-subtype = 'ER'.
    SOURCING = 'X'.
ELSE.
    SOURCING = ' '.
ENDIF.
ENDIF.
endmethod.
However Im not able to control the Classic and Extended Classic Scenario even after introducing field EXT_DEMID in structure BBPS_EXTPO_BADI in badi BBP_EXTLOCALPO_BADI and method DETERMINE_EXTPO.
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
IF ITEM_DATA-EXT_DEMID = ' '.
BBP_EXTPO_GL = ' '.   for classic
ELSE.
BBP_EXTPO_GL = 'X'.   for extended classic
ENDIF.
endmethod.
No idea y this is not working to my knowledge it should work
What do you think ? this this code and badi actiation im not able to perform SSP in classic mode and sourcing with extended classic mode.
Regards,
Sandeep Parab.

Payment term key with limit days in Extended Classic Scenario

Hello,
We have an SRM 4.0 implementation (SRM Server 5.0 with Support Package
9) using the Extended Classic Scenario.
When a shopping cart is created, it must be approved, and then a
purchase order is generated (first locally at SRM, and then is
replicated to the backend).
The problem is that the payment term key (field at header level EKKO-
ZTERM) of the backend purchase order is empty, only in cases when we use a payment term key which have several different values for the
field "limit days" (T052-ZTAGG in backend, BBP_PAYTERM-ZTAGG in SRM).
Example:
 ZTERM ZTAGG
 K180 09
 K180 19
 K180 31
If the payment term key selected has no several values for the field "limit
days" (one single entry), the payment term key arrives correctly at the backend purchase order.
Example:
 ZTERM ZTAGG
 E000 00
In SRM table BBP_PAYTERM we have upload the backend payment terms
(using report BBP_UPLOAD_PAYMENT_TERMS). In other threads it is said that you must copy the entries generated by the report with the logical system of the SRM system, but in extended classic scenario it seems to be not necessary.
We have already implemented note 846009, in order to use always the backend payment term, but the error didnt get resolved.
We have our vendor business partners mapped to the local and backend
purchasing organizations, but it is only necessary indicate the Payment term key for the Backend Purchasing Organization.
Regards

hi,
Pls see the foll notes:
Note 576349 - Terms of payment in the ECS
Note 541934 - Modification note: Copying base date from T052
Note 953999 - ECS: Terms of Payment values not in PO header
Note 940453 - Backend payment term data not updated in the extended PO
Note 945018 - Incoterms data not transferred to the back end
BR,
Disha.
Pls reward points for useful answers.

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

SC with Limit Item using Extended Classic Scenario?

Hello,
Can we implement SC with Limit Item using Extended Classic Scenario.
I mention that we replicate the Product Categories from R/3 backend.
We have tried to create a SC with Limit item, but the data on Quantity, Price and Tax is not picked up at PO level.
Regards,
Shaiek

Hi
Please try out this.
For the time-being,
Try de-activating all the custom BADI Implementations and check, what is happening, in the standard SRM system. How does it behave incase of limit item ?
Incase it works fine, without any Custom Implementation active in the system, I suspect there is something wrong in your current deactivated BADI Implementation.
Since i don't have access to your system , Please paste the code here.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Extended Classic Scenario - Free Items?

Does SAP support PO's in Extended Classic Scenario with a zero price (free items)?
My client is switching from classic to extended classic scenario and they require to be able to creaet PO's that have a zero price like they have in the classic scenario.
We are currently getting an error that we need a price with the IR flag, but I would expect the system to automatically unflag the IR flag for a free item?

Hi Jay,
Thanks for your response. There are two problems with your soluiton. First the shopping cart doesn't have the IR flag on it and can't be changed by the user and we have PO's created directly from SC's and go out to the vendor.
Second, In extended classic scenario it apprears that the system doesn't allow you to change the ir flag on the PO and make the cooresponding change in the ERP PO.

Switch from classic to Extended Classic Scenario- Impact

Hello,
We are proposing to switch from Classic to Extended Classic Scenario.
We are on SRM_SERVER 550,Sp7 and SAP 4.7 backend.
We want to know if this is technically feasible to switch and have less/no impact on existing transactional data and master data.
Main concerns are: Existing open Shopping carts and PO's.
We are also modifying the WF by including buyer completion WF.
Will the carts created in classic scenario and 'awaiting approval' work similarly in ECS?
Can we copy old carts (created in classic scenario) into new ones in ECS?
Are there any other issues like the ones above which people have come across?
Is there any standard SAP material/Consulting note available
which gives some guidelines for switching scenarios?
Regards,
Srivatsan

Hello,
You can switch from the classic to the extended classic scenario by making the global settings in the IMG.
But it would be better if you can decide if only a particular set of categories need ECS.
If you wish to have both the scenarios,the deciding factor is the product category.
You can also activate a BADI for the control of ECS despite the above Global settings.
Reward if answer is helpful,
Thanks & Regards,
Nagarajan

SRM: Extended Classic scenario: Request your help.

Hi Guru's,
We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
in our project the SRM box is : G3OSBSR102.
R/3 backend Box is : RCHSBR3142.
Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
1) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
2) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
Many Thanks,
Prasad NN.

Dear Prasad,
To work on Extended Classic Scenario, you just have to maintain the following configuration in SPRO:
>SAP Supplier Relationship Management
>SRM Server
>Cross-Application Basic Settings
>Activate Extended Classic Scenario
Check the flag "Extended Classic Scenario Active".
You dont have to manipulate "BE_LOG_SYSTEM" field to choose your scenario.
Regards
Thiago Salvador

SR_ Extended Classic Scenario : Request your help please

Hi Guru's,
We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
in our project the SRM box is : G3OSBSR102.
R/3 backend Box is : RCHSBR3142.
Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
1) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
2) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
Many Thanks,
Prasad NN.

Hi ,
Go to SPRO
There is a node - Activate Extended Classic scenario
Do the config.
Regards
G.Ganesh Kumar

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

Limit shopping carts in extended classic scenario

Similar Messages

Maybe you are looking for