Organization Structure Extended Classic

Hi,
Can you please help me with the following Questions
The below link says that one can use local porg and Local Pgrp in Extended classic. In this case when a PO is replicated to backend, system determined the back end porg for replicated PO based on Location or plant
http://help.sap.com/saphelp_srm30/helpdata/en/0a/baf73a93ad9179e10000000a114084/content.htm
a) My question is a plant can have several  Purchasing Organizations assigned to it in back end ? In this case which one of them will be determined..
b) Also, if an SRM system is connected to multiple ECC. And similar categories are procured in all the ECC systems. We will have duplicate product categories after replication pointing to their individual ecc systems.
Now if we are to do Shopping carts using catalogues and since each catalogue item can have only one product category pointing to one of the systems.; this will result in duplication of catalogue items with each item for each system even though physically the item is same.
To avoid the above, If we decide to use local product categories and some how map them to one back end product category based on company code during creation of PO, it would help us simplify the process. Would it be Possible to do?
The purpose of the above question is. We want to use extended classic with plants and company codes mapped to back ends.
Entire Purchasing structure including Purchasing Organizations and purchasing groups will made local to SRM. The product categories are alos local product categories in SRM.
When i make the Shopping cart for example which is complete,
1. There should be some way to determine back end system. We are planning to use BBP_DETERMINE_LOGSYS. In this we will determine back end system using plant
2.  Then the next question is what willl be the Purchasing org in replicated PO, Your clarification to "a" above will answer this question
3. the next thing is what will be the purchasing group in the replicated PO. We are planning to use BBP_PGRP_FIND to do this
4. The next thing is what will be the Product category in replicated to back end. Your clarification to "b" willl answer the question.
c. Finally because of this design, will we have issues with contracts etc......
Edited by: kiransap25 on Aug 3, 2010 8:35 PM

Hi Kiran,
Regarding your 1st question:
a) As it can happen in backend for plant associated with sevarl P orgs, but in SRM it is one to one and  I think you can have a custome table in EBP for that one to one relationship through which you can decide the backend Pur Org in backend based on the plant.
b) Not very clear with the question, But the Product categories are based on the Backend and so is the catalogs which you assigned as in the users attributes which is get validated with the co code and backend system (based on the user attribute).
IS

Similar Messages

  • Local Purchasing Organization in extended classic scenario SRM 4.0

    Hi all,
    I have tried to make settings for updating vendor master records. I used the following path in IMG.
    SAP Implementation Guide > SRM Server > Technical Basic Settings > Settings for Vendor Synchronisation > Define Settings for Each Backend System
    There i wanted to make the entries for: Order, LogSystem, Flag in NoBEPchOrg and Local Purchasing Org. For the Local Purchasing Org. field i could not select any entries.
    My question now is how can I check if there is any local purchasing organization maintained. In the EBP Organizational Structure I have set the flag for the purchasing organization and have entered in the "corresponds to" the number of my purchasing organization from the backend and i have selected the SRM-System in the next field.
    Best regards,
    Bernd

    In the organization structure, under function tab leave the corresponds to field blank

  • Organization structure in extended classic scenario

    Hi All
    I  am trying to configure extended classic scenario on SAP SRM 7.0.  I have made the following settings for the same:
    1. In SPRO->SRM Server-> Technical Basic Settings -> Define backend system from product category, I have specified target system as SRM system and not ECD system
    2. In SPRO->SRM Server->Cross Application Basic Settings-> Activate Extended Classic Scenario, I have selected all the options including "Back end purchasing group responsible"
    I have a few doubts.
    1. In organization Structure (PPOMA_BBP) Comapny code is corresponding to company code in back end but do I have to create local purchasing organization and local purchasing group i.e. in Functions-> Corresponds  I'll have to leave blank. plz suggest
    2. Also is IPC configuration mandatory for extended classic scenario
    Plz give your suggestion on above mentioned issue
    Regards
    Pawan Keshwani
    Edited by: pawankeshwani on Mar 18, 2011 8:33 AM

    Hi Pawan,
    No you should mention Purch Org & Purch Grp also wrt your backend (ECC).
    IPC need not be configured separately from SRM 5.0 onwards. To ascertain if IPC is working fine just run the report : RSVMCRT_HEALTH_CHECK. You should see 4 success messages. Else get in touch with Basis to enable Virtual Machine Container (VMC)
    Regards,
    Nikhil

  • How to extend the validity of already limited organization structure

    Dear experts,
    I have limited a purchasing group in the organization structure to a date in the past. The purchasing group is no longer appearing in the organization structure. Now, how I can extend the validity of the organization structure to a future date ?
    Thanks and regards,
    Ranjan
    Ranjan Sutradhar

    Hi Ranjan,
    Kindly go to T-code BP....input the BP number or name of your Purchasing group and change the date under 'Address valid from' and 'Address valid to' date.
    Regards,
    Nikhil

  • 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 .
      BR!
       Alex!
    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->main.do
    then give the client no of yr ROS client
    the RFC user user ID from EBP to ROS
    it's password
    sap-sessioncmd=open
    sap-language=sy-langu
    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).
    BR
    Dinesh

  • Conversion of classic to extended classic

    hi,
    i wanted to convert from classic to extended classic scenario.so what can i do to that?already activated simplified pricing.now how can i activate the ipc pricing?do i need to implement any BADI for po pricing conditions and for organization structure maintenance.kindly help me to solve my issue?
    thanks,
    chakri

    Hello,
    Check the following URL. It provides some information about pricing and IPC:
    http://help.sap.com/saphelp_srm40/helpdata/en/72/f40f3c98ddaa4ce10000000a11402f/frameset.htm
    Additionally, 637562 can be helpful.
    Kind regards,
    Ricardo

  • URGENT: CLASSIC & EXTENDED CLASSIC

    hi gurus,
                can anyone tell me the difference between classic and extended classic scenarious in SRM? when will we use them for client requirement?
    what is the difference between R/3 enterprise structure and SRM organizational plan?
    what is meant by SAP SCM?
    if i  implement the extended classic then willl it possible in classic?how and why
    what r the followon documents will support for each scenarious?please be detail.
    what is the transactioncode for VENDORMAPPING?
    CCM,SUS,SOURCING,SSP,PDP,SERVICEPROCUREMENT are depending on which scenarios i.e classic or extended classic for each business scenarious?
    please send solutions immediatly to my id <i>[email protected]</i>
    warm regards
    rakhi

    Let me see if I can satisfy you :
    - The major difference between classic and Ex. classic is the system where the leading PO is created. In classic it's r/3 while in ECS it's SRM.
    The usage depends on the customer requirement and convinience.
    - R/3 ent structure and SRM org are mutually exclusive. But you take ref of r/3 ent structure in SRM org structure at many points.
    - SCM is collabration of many SAP components like APO, ICH. It's basically group of SAP solutions to map the tptal functionality of supply chain.
    - You can control ECS scenario with BADI depending on yr business objects.
    - Follow on documents are same for both PO or contract , GRN/Confirmation, Invoice
    - already tolD BBPGETVD for downloading vendors from R/3 and BBPUPVD for synchronisation
    - CCM is component for catalog can work in both classic or ECS
      SUS is component for suppliers can work in both classic or ECS
      sourcing is functionality for purchasers can work in both classic or ECS
      SSP is business scenario for self service can work in both classic or ECS
      PDP is BS for plan driven procurement can work in both classic or ECS
      service procurement is for service and work in same way
      these components or business scenarios are mapped as per customer requirements and hence the leading PO location has flexibility.
    BR
    Dinesh
    (Reward if helps)

  • Regarding the organization Structure

    Hi All,
    Can any one help me the basic organization structure for Extended Classic scenario.
    How to assign the extended attributes to that particular user.
    In my frontend if i select any of the product's then it is giving me dump saying that Template is not found.
    Points to be awarded.
    Thanks & Regards
    Girish

    Hi Raju.
    I don't think it sounds like problems with the org structure? It sounds more like the web-templates are missing or incomplete. You can check these via SE80.
    But otherwise post some more info from the dump etc.
    BR
    Dennis

  • Activate extended classic scenario

    Hello, when I try to activate extended classic scenario to create contracts in SRM and then transfer them to R/3 I have these options:
    Extended local PO
    BE Purch Grps Resp.
    Back-end check reqd
    Back-end errors, show as error msg
    Which options may I have to select?
    Thanks in advance

    Hi,
    I think Rosa's requirement is to create a manual and local contract in SRM.  Indeed you mentioned an excellent  BADi, but my understanding is this badi gets called from the sourcing application.  I am not sure whether this gets called from the SRM local contract.  This is the help documentation I am pasting here.  It would be wonderful if this works.  See the highlighted "importing parameters" part of the following pasted one.
    Thank you,
    DV
    Determine Target System of Contract
    Use
    With method CONTRACT_LOGSYS_DETERMINE, you can control the target system determination for contracts.
    In the standard, the Sourcing application and SAP Bidding Engine create contracts locally in SAP Enterprise Buyer . With this method, you can create a contract in the backend system instead.
    Requirements
    You are using a backend system with Release 4.6B or higher.
    You have created the logical system in activity Define Logical System
    Parameters
    Importing
    The BAdI takes this data from requirements in SAP Bidding Engine (bid) or from requirements in the Sourcing application.
    IT_HEADER
    Header structures
    IT_ITEMS
    Item structures
    IT_PARTNER
    Business partner data such as vendor or location
    IT_ORG
    Organizational data
    Changing
    In the method you can overwrite the following field:
    CV_LOGSYS
    Name of the system in which a contract is to be created.
    If this field remains empty or contains the name of the local system, then the contract is created locally.
    If this field contains the name of a backend system, then the contract is created there.
    Notes
    When coding the method, use the delivered sample coding as a guide.
    See also
    BAdI Determine Backend System / Company Code

  • Conversion of classic scenario into extended classic

    hai,
    i have configured classic scenario.now i wanted to convert classic into extended classic.what are all the things i need to do?do i need to close all of my shopping carts?do i need to implement any badi?what are all the modifications i have to do in organization structure and attributes?do i run any reports for extended classic scenario?could any one help me to find out the solution.
    thanks and regards
    chakradhar

    Hello Chakradhar,
    These pointers will help.
    A. Activate the extended classic scenario
    SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Cross-Application Basic Settings  Activate Extended Classic Scenario
    B. Activate IPC pricing
    C. BAdIs relevant for the pricing are activated correctly  BBP_PRICEDATA_READ; PRODUCT_UPDATE2
    D. SRM-SRM server-Technical basic settings-Define backend system for product categeries- SRM system as target system
    E. Number Ranges
    Check your business requirements, one of the good idea will be to switch the extended classic scenario only for a particular set of categories need ECS. you can have both scenarios,with deciding factor as product category.
    Thanks
    Ashutosh

  • Good news - find purchasing group in Extended classic

    Hello All,
    This is not a question. Just FYI.
    From SRM50 SP5, you do not need to program the BADI to find purchasing group in Extended Classic. Please cheek the note 944918 ECS: Find back end purchasing group as a responsible.
    Regards,
    Masa

    Hi,
       The link in my  previous reply refers to the use of BADI for changing the purchasing group in the SC to the correct value which is maintained in the SRM org Structure after the requirements are transferred  from R/3 to SRM.
      However in case of ECS(Extended classic scenario),w/o using the BADI you can ensure that the system always searches for a back-end purchasing group when determining the responsible purchasing group, that is, a purchasing group for which a relationship to a purchasing group was defined in the back-end system in the SRM organization management,details of which are given in the note 944918
    BR,
    Disha.
    <b>Pls reward points for useful answers.</b>

  • IR_IND indicator in purchase order - Extended Classic

    Hi All,
    We have a scenario where we purchase free item from vendors. We reset IR_IND in SRM PO then replicate into backend where IR receipt is reset and Free item is set. We have implemented badi BBP_DOC_CHANGE_BADI and BBP_ESC_PO_OUT to do so but POs always in held status and fail to replicate into backend. Our abaper found the changes in BADI has been overwritten by standard code - system will overwrite it with vendor data. Also we found relevant note 1260486 that stated this is truth - our badi changes will not be kept.
    For this case, can anyone help/advice how can we purchase free item in extended classic scenario? thank you.
    regards,
    glen

    Hello,
       Not sure if I follow exactly the comments about being overwritten from the partner data, but we do this successfully in an implementation of BADI BBP_ECS_PO_OUT_BADI.  In particular in our case we set the GR/IR flags based on a couple of criteria like the document type and amount; I don't recall all the technical details of the structure elements in the subsequent BAPI calls to create or change the PO (BAPI_PO_CREATE1 and BAPI_PO_CHANGE) regarding the free goods flag (UMSON) in the ECC PO, but FYI it is mutually exclusive to try and set the IR flag on a free goods item, the BAPI ignores it if IR is set as I remember.
    Hope this helps a little
    Cheers
    MC

  • Problem in Extended Classic Scenario related to PO

    hi,
    we are using Extended classic scenario in our client. User has created a SC .when we are going to create a PO system is showing an error Purchase Group B01 does not exist.
    This Purchase group is not created in R3 or neither replicated to SRM.and it is not assigned in the Org structure.
    Kindly Let me know from where the purchase Group might be Picked apart from the org Structure.
    regards
    subhash

    Hi
    Can you check your SC how this Purchase group picked form your basic data ?
    since this purchase group is existing in srm thats why it picked while create sc right?
    regards
    Muthu

  • Classic Scenanio and Extended Classic Scenario

    Hi all,
    I would implement on the same system 2 different scenario:
    1. Classic Scenario for self service procurement
    2. Extended Classic Scenario for the following business scenario:
        a. PR from ECC is transfered into Sourcing Cockpit with Plan Driven Scenario
        b. buyer convert the SC created in Sourcing Cockpit into a GOA or a PO that are transfered to ECC.
    Can coexist this different scenario?
    Can I address this different scenario only with organizational differences?
    Thanks
    Bye
    Marco

    Hi Marco,
    I see 2 quick ways to realise your requirement.
    The first is to create an attribute in t77omattr for a position and maintain that attribute in the organisational model. This attribute could just be filled with an X for example.
    Then you have to implement BADI BBP_EXTLOCALPO_BADI and retrieve the attribute you created with FM BBP_READ_ATTRIBUTES (use sy-uname to retrieve the attribute for the current user).
    The 2nd is to create a Z-table with the user-ids that you want to use the local (or ECS) scenario. Then again in BADI BBP_EXTLOCALPO_BADI  you have to write the logic to retrieve and compare this.
    Keep in mind that these are user-based distinctions and not based on scenario.

  • 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 I’m 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.

Maybe you are looking for