Questions about Extended classic scenario

Hi gurus,
I'm working in SRM 5.0, ECS, backend ECC 6.0 (only one backend).
Everytime a SC is being approved a SRM PO has be created. Then a copy of this PO  has to be created in ECC with document Type ATT and the same number of the SRM PO.
I have two questions
First of all I need to know the settings to make in 'Define objects in backend system' (for every purchasing Group and every Category ID, I need to create always PO in backend).
P.Gr   Category ID  Source System      Internal proc.                              External proc.
        *                 TRDCLNT011         Always external procurement        PO if item data complete, otherwise P.Req.
Is this correct?
Secondly I need to understand the logic for number range definition
SRM Activities
1 - Define number range for Shopping Cart
I Need to create a SC number range
01 1000000000 - 1999999999
and then associate this range (01) to SHC transaction type ('Int.n' field)
2 - Define a number range for local PO
LO 7000000000 - 7999999999
and then associate this range (LO) to ECPO transaction type ('Int.n' field)
3- Create a new transaction type 'ATT' (backend PO)
4 - Define a number range for backend PO
PO 7000000000 - 7999999999
and then associate this range (PO) to ATT transaction type ('Int.n' field)
ECC Activities
1 - Define a number range for document type ATT
XX 7000000000 - 7999999999
and then associate this range (XX) to ATT Document  type 'External
Is this correct?
I'd really appreciate your help
Points will be rewarded
Thaks in advance
Best regards

Hi. It all sounds about right.
I don't think the define backend docs does a great deal in ECS, you always get a PO with extended classic. If you ever want anything but a PO, a reservation for example, you have to not use extended classic for those items.
The number ranges look OK, although I think you only need 1 number range for the backend/local POs, it should all go in line on its own. It's been a while since I got an ECS system going so it is hard to remember.
The thing to do is try it in a test system and see what happens.
If anything goes wrong let us know on SDN what error messages you get and we should be able to help.

Similar Messages

  • Question on Purchasing documents in extended classic scenario

    Hi friends
    How to create local purchasing documents i.e po,confirmations,invoice, in extended classic scenario
    Please let me know the path
    venkat reddy

    Hi Venkat,
    The user interface and the process is same for local documents. However the result of document posting (either backend or local) depends on the setting in SPRO --> SRM --> Technical basic Settings --> Define backend system for product category.
    Here you can define the target system as the system of document posting. If the terget system specified here is your SRM system, then it will create local documents in SRM.
    Do reward points for helpful answers

  • Use the MM-SUS in Extended Classic Scenario

    HI,my experts :
        The standard function doesn't support the MM-SUS in Extended Classic Scenario .Now I may have two questions about it .
      1、  I have one ECC system .I need handle the invice in the ECC system .In other word ,the invoice rcreated in the SUS should transfer to the MM system .But in EBP-SUS ,the invoice is transfered to the SRM system .What can I do now ?
      2、 If  I  want to use the decoupled scenario ,some POs are create in EBP ,and others are created in MM .Now ,which sus I should select ? EBP-SUS  or MM-SUS?
       Or some detail document about it .
    Edited by: Alex on May 25, 2010 9:17 AM

    Khan has explained most of the things.
    The external web service I meant is actually OPI catalog which you need to maintain.
    The same has to be entered in the attribute CAT of the EBP purchaser.
    To maintain the call structure of this catalog
    Get the URL from SE80->BSP appln->ros_prescreen->controller->
    then give the client no of yr ROS client
    the RFC user user ID from EBP to ROS
    it's password
    the operational purchaser role in EBP (sap_EC_BBP_OP_PURCHASER) should be linked with
    the same in ROS via role menu->business partner->screen supplier->right click->change details
    ->sap-client=ROS client no
    The administrator & op purchaser should be present in ROS org structure also
    & should have same userID & password as EBP
    you have to define the vendor root, the root of the purchasing organization and the currency in
    table BBP_MARKETP_INFO in the SRM System (Enterprise Buyer client).

  • Extended classic scenario triggered on company code

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

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

  • Pricing conditions in extended classic scenario

    Hello friends,
    I have a question about pricing conditions. There is a condition in R/3 where the price can be redetermined based on the G/R date. Is it to do something similiar in SRM. I mean redetermine the price at the time of confirmation.
    Thanks any help will be appreciated.

    Hello Chakradhar,
    IPC is required for extended classic scenario. Reach out to your basis practitioner, he should be able to perform this.
    Helpful links
    Re: IPC Configuration in Functional perspective.
    Re: IPC Configuration
    Hope this helps.

  • 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.

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

  • POR transferred into MM(Backend) system in Extended Classic Scenario

    I am working on standard EBP-SUS Extended Classic Scenario. We have SRM Server 7.0 SP9 
    As we are successfully send PO from EBP to SUS.
    Issue : On working to Purchase Order Response,i am getting POR sent by SUS to EBP but we are not getting it replicated to MM.
    Our Concerns about is it need extra configuration required or need to have apply some note to getting replicated POR in MM from EBP or have to configure some XI Scenario to replicate POR from SRM EBP to MM.
    As we know that Extended Classic Scenario supports till Purchase Order Response still we are not getting Purchase Order Response in MM.
    Please tell us, Provided Solution will  be really appreaciated.
    Pawan Keshwani

    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
    <b>Note 940453 - Backend payment term data not updated in the extended PO
    Note 945018 - Incoterms data not transferred to the back end</b>
    Pls reward points for useful answers.

  • 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.
    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?

  • Extended classic scenario to Classic scenarioc in SRM.??

    someone pls tell me how to change from Extended classic scenario to Classic scenarion while creating in shopping cart...?
    I am using BADI "BBP_EXTLOCALPO_BADI" change to classic scenarion from extending classic..but i got confused about source code..So i request any one can help me for suitable source code..

    Do you mean to say that you have set up Extended Classic Scenario but you want to change it to Classic Scenario?... If this is the case, remove the activation in COnfiguration for Extended classic scenario and deactivate BADIs you ve implemented for Extended Classic
    Do you want to change it to Classic only for the Document user is creating.--> Read the indicator or data from SC and decide whether the document has to be in Classic or Extended classic SCenario.... The BADI will either have Extended classic = X or NOT.... so there is no parameter for classic Scen... Depending on your requirements, implement the ext. classic badi to SET it or NOT set it...
    Virender SIngh

  • Extended Classic Scenario  - how does the integration work ?

    Apologies for asking a basic question, but we are looking at requirements for integrating SRM with R/3 using the extended classic scenario and I need to understand how the integration actually works ?  How is the data transferred between the 2 systems ?  Does it use BADI's, idocs etc ?
    Many thanks,

    Hi Olaf,
    I just wanted to give some precision on what you said (in the thread How to "see" PO in EBP ? also)
    The Extended classic scenario only refers to the local PO creation replicated in R/3.
    In this scenario, in the R/3 PO only the data not managed/sent from the SRM are available for modification (which depends on the SRM version you use)
    The "PR transfer from R/3" is called "Plan driven procurement", and in this scenario only RFC is used, the qRFC are only used for BDocs of the CRM Middleware.

  • 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?

    below are the tables effected while creation of PO:
    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.

  • PO status Held in extended classic scenario

    Hello SRM gurus,
             I am very new to SRM with MM background. I have a question which i think you guys might have come across earlier.
    We are using version 5.5 extended classic scenario, replicated all the vendors and materials from R/3 to SRM, did all the basic configuration needed, we are able to see those vendors and materials in SRM also. here is the issue. we are trying to add an item to the shopping cart which in turn creates a PO in SRM so that it automatically replicates in R/3. But the PO status in SRM is Held and we found out that vendor is not assigned to the PO which is very clear why the PO has been held. So what could be reason the vendor is not getting assigned to the PO though we have the inforecord and source list(checked the fix indicator also)for the same material and vendor in R/3 ?
    I'm sure many of u would have come across this issue. please help me out.

    Hi Satya
          Thanks for your quick response.
    1) We are using Workflow without approval process
    2) I checked BBP_NUM_SUSPO in SRM server. There is nothing in there. Is this the correct number range for PO? I checked OMH6 in R/3. please tell me how to sync it.
       When we try to post it after editing the PO with vendor number, we are getting Waiting for approval error though we have activated Without workflow approval process. let me know why is it showing that error?
    We have another strange issue which is, We have assigned a material say M01 to a P01, POrg1 and vendor V01 and have info record and source list, but we don't see this Pur.grp when we create the shopping cart and it defaults to some other pur.grp say AP01 which we deleted long back. can you tell me where it is picking up the deleted ones?

  • SUS-MM vs SUS-EBP (Extended CLassic Scenario)

    We have an extended classic scenario already up and running between ERP->EBP system without XI usage.
    Now it is necessary to configure SUS integration for ASN creation purpose. As I can see SAP has 2 standard configuration guides: one for SUS-MM and another one for SUS-EBP, but they are not fully relevant for ECS.
    Could anybody tell me please from what system EBP or ERP it is better to send PO to SUS system when we are using extended classic scenario? And what are advantages/disadvantages of this?
    Thanks and Regards,

    Hi Dinesh!
    Thank you for your answer! It is clear that leading PO is in EBP, but why I can't use ORDERS and ORDCHG IDOCs to transfer PO and PO chnages to SUS?
    One other question: do you know whether Configuration Guide for ECS exsits (like SUS-MM and SUS-EBP documents)?
    Edited by: Siarhei Tsikhanenka on Apr 4, 2008 9:56 AM

  • Tolerances in SRM extended classic scenario

    Hi all,
    I have a question regarding tolerances in extended classic scenario and I hope that somebody could help me.
    We use extended classic scenario. The tolerance group is attached to TOG attribute in PPOMA_BBP, tolerance key is DQ.
    We also tried to use tolerance key CF, but it seems as if CF is not applicable for GR?
    However, whenever we try to confirm more than PO quantity, we get an error message. “PO Ordered quantity exceeded by 1 EA“
    It seems so that SRM has a ‘double’ tolerance check
    • one in SRM against defined tolerance (via attribute TOG)
    • one in R/3 against the PO tolerance
    Now my question: Is this the expected behaviour or a bug? We do not want to maintain two tolerances. And furthermore most of the time we have PO’s without a material master. Are there any possibilities to skip the PO tolerance check?
    Thanks for your help,
    Edited by: Martina A. on Jan 15, 2008 1:13 PM

    Depending on the SRM version you are using, Please go through the links, which will definitely help ->
    Condition Type SRM - ECC
    Tolerance in SRM and ECC (BE R/3)
    Re: SC Budget check without SAP Fund Mgmt
    TOG parameter and tolerance checks better understanding
    Setting EKPO-UNTTO with BAPI_PO_Create
    Re: SRM: many confirmation for PO
    Please maintain the "TOG" attribute in PPOMABBP transaction in SRM.._
    Do let me know.
    - Atul

  • Extended classic scenario clarification

    I have a question in case of a extended classic scenario.
    Shopping cart is created by a employee and approved by a manager. But still no vendor exists in the shopping cart after approval. Now how the PO is created in SRM.
    Note sourcing is activated, strategic and operational purchasers exits. How the process is implemented. Will the purchasers get informed via work items? Will they get shopping cart work items or incomplete PO work items.
    Could any of you please give clarity on this.
    Thanks in advance.

    Once the shopping cart is created, based on sourcing config and also based on Purchase group responsibility the respective shopping cart flows in to the 'sourcing cockpit'(SOCO). Buyers/Purchasers will see all the open shopping carts and in SOCO there are multiple options available for purchasers to do. Such as creation of PO by just adding the vendor and right price/  creation of Bid or Auction or contract/   group the similiar requirements into one requirement create PO etc.
    If the follow on document is chosen to be a PO or Contract then the shopping cart will go out of the SOCO once the PO/contract created. If at all the SC is considered for Bid/Auction process then the SC remains in SOCO till the Bid/Acution process is completed. Hope this helps
    You can also look at SAP application help for SRM sourcing

Maybe you are looking for

  • How to use one PSE with multiple URLs?

    I need to hit my DMZ SAP Web Dispatcher with multiple unique URLs.  I am starting off using and  DNS will resolve both the Web Dispatcher Host.  Following Tobias Winterhalter's Blog: Name-based virtual hosts and one

  • How to display presentation variable in a column

    Hi all....I have to display presentation variable in a column... I tried placing @{variable_name} in column formula.. But it is displaying a value 0 ..where the variable carries a date value. Any suggestions?

  • My ipod will not scroll up or down or left or right how do i set this up or how do i fix it

    my ipod will not scroll up or down or left or right how do i set this up or fix it

  • Update Vendors using Idoc.

    Hi all, We have two different SAP systems (call it system A and system B). The vendor data is created and updated in system A and CREMAS idoc is generated to pass the data to system B. The problem come since the system B have some fields as display (

  • Cahnges Alternate Document type

    Hi Friends, I have maintained an alternate document type ZMMF in OR10 Sales Order. In Sales order it is showing both options i.e. ZMMF and OR10. But when I am going to change this, system is prompting an error as below: Changes to sales document type