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

Similar Messages

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

    Hi!
    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,
    Siarhei

    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)?
    BR,
    SIarhei
    Edited by: Siarhei Tsikhanenka on Apr 4, 2008 9:56 AM

  • Changing the Global Control of Extended Classic Scenario

    Hi,
    We are implementing a duplicate scenario, where for a certain product category we will use classic scenario (Only contracts on SRM) and for the others ext. classic scenario (contracts,requisitions and PO's on SRM). I activated the ext classic scenario by flaging it on the customizing. I also read in the documentation that we have to use BBP_EXTLOCALPO_BADI in order to determine which category will be handled in which scenario.
    Did anybody had experience on this and provide the important points while implementing such a scenario?
    Thank you in advance,
    If you need to forward details, [email protected]
    Message was edited by:
            Gaia K.

    Hi,
    Well that quite simple
    As you have done it just activate ECS scenario and activate the badi to change to classic scenario with you custom rules (product category...).
    As soon as you get the ECS scenario configured, evrything will be ok for classic scenario.
    Kind regards,
    Yann

  • ASN in Extended Classic Scenario with SUS

    Hi SRMer?
    Is it possible to create an ASN in SUS with Extended Classic Scenario (ECS)?
    OSS note 543544 mention that the scenario is limited for document types Purchase Order, Purchase Order Response and Change Order. Confirmations and invoices are not possible. There is no indication on ASNs.
    Any help will be appreciated.
    Regards.

    Hi
    Please go through these links ->
    SUS-MM Confirmation without ASN
    Re: Details on ASN
    The specified item was not found.
    SUS  ASN - mandatory field
    ASN Confirmation not created,
    Clarifications on EBP-SUS and MM-SUS Scenario
    Re: SUS-MM scenario with "POR (order ack.)" and ASN for free text
    Creating custom field in ASN screen of SRM SUS
    SUS Invoice
    Regards
    - Atul

  • PO error - extended classic scenario

    Hi Guys,
    I'm using SRM 5.0 with extended classic scenario...
    During creation of the purchase order locally (in SRM) I got the "error in process" status.
    My means of T-code RZ20 I got the following info to ithis error:
    context:B2B Procurement
    object name:Purchase Order
    short name: Backend application errors
    status: Active
    Alert text: PO 700..1: Call of a method or kernel Method that has not been implemented
    using Transaction BBP_PD I got the following status:
    Status: I1080
    Description: in transfer to execution system
    Do you have any idea what should I do in order to resolve this outstanding issue?
    many thanks in advance for your help.
    regards,
    Piotrek

    Hi
    Go to transaction - <b>SPAM</b> to get all the required Patch levels and other required system version details.
    <b>Meanwhile, try the following SAP OSS Notes as well -></b>
    <u>Note 508972 - Error during transfer of extended purchase orders
    Note 881650 - Duplicate transfer/output of the purchase order
    PO status in " error In Process ".
    Error in Transfer Process (Urgent )
    FOLLOW ON DOCUMENT NOT CREATED ( ERROR IN PROCESS)</u>
    Hope this will help.
    Regards
    - Atul

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

    Hi
    <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.
    Regards
    - Atul

  • 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

  • Extended classic scenario in SRM 7.1

    Hi colleagues,
    we want top use SRM 7.1 with extended classic scenario and we want to create POs in SRM and reflect them in ERP backend. The question is it possible somehow to change those POs aftewards (e.q. add confirmations, transportation costs, etc...) in ERP? Or is there any way to trasnfer POs in hold status from SRM to ERP and then change them in ERP?
    Thanks and regards, Anton

    Hi Anton,
    PO is created a in SRM as local and a copy( copy does not contain the entire PO info, only the useful for the backend) is being sent to R3.
    DO NOT try to search a workaround for modification in the backend..sooner or later you will be incurring in incosisnten data and misalignmentes.
    SRM is the PO golden source.
    Thanks and Regards,
    Abraham

  • 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

  • ECS- Extended Classic Scenario - Customer expectation

    Hello All
    What are the customer expectations from Extended classic scenario other than SAP Standard functionality
    Muthu

    For example
    1.business wants to send a PO via EDI . it may be achieved by enhancement
    2. PO message not be created in SRM and message creates in ECC and sent it to supplier from ECC not SRM
    3.data synchronisation on transaction data across SRM and ECC
    4. local contract with Vendor list.
    etc.
    Muthu

  • Can we use the Extended Classic Scenario with MM-SUS

    HI, expert :
        In extended classic scenario ,the PO created in SRM system ,and then replicated into the MM system .You  can't change it  in MM system .
        So, in this situation ,I want to know the MM-SUS can be  suitable or not ?The PO can transfer from ECC  to SUS ?
       If I use the decoupled  scenario  ,which one I can select ?MM-SUS or EBP -sus ?
       BR !
      Alex!

    Hi Alex,
    as noted by Bill, in MM-SUS is the extended classic not possible at all.
    By default it's also not supported in the SRM-SUS. Please see the note 543544. If you would like to activate this, you need to pay a consulting fee for SAP:
    "Please note that the full scenario can be enabled by a consulting solution, compare OSS note 700350."                                  
    Regards,
    Peter

  • MM-SUS for the extended classic scenario

    Hi,
    I have done SUS-MM for the classic scenario.
    Did anyone implement SUS-MM  for the extended classic scenario ?
    Did you face any problem or will it be same as 'classic' scenario ?
    Please help
    Thanks
    Pranav

    There shouldn't be any problem especially when the scenarios are concerned. Since the PO's moves from MM-SUS.
    Regards, IA

  • Are you using the Extended Classic Scenario ?

    Hello everybody,
    Is somebody using the Extended Classic Scenario - SRM 4.0 ?
    If yes, could you describe briefly the config steps that you follow ?    
    I have received and followed some advices here and I have checked all the official documents without success..   =(     Until now, for some reason the EBP tries to create the PO in the backend =(
    Thanks for your help guys !
    Regards from Mexico.
    Diego

    Hi Diego,
    If you activated the Extended scenario, the system cannot try to create directly a PO in the backend, it first has to create it localy.
    If you are sure that:
    -You activated the Extended scenario in SPRO (and not in the BADI)
    -The system tries to create directly the PO in R/3 (as you say in your post)
    Then there are only 2 solutions:
    1- You have activated the scenario BADI, and tell the system to work in classic scenario
    2- You have a bug in your SRM (which I doubt, cause I implemented this scenario on EBP 3.5, EBP 4.0 and SRM Server 5.0, and I never had this kind of problem).
    Regards.
    Vadim

  • SUS / no goods receipt doc to backend  in extended classic scenario?

    Hello
        have you any find  a solution for problem
        in SRM/SUS and goods receipt in extended classic scenario. Gr remains  only in SRM not going to backend...
    Brg Harri
    Message was edited by: Harri Harkonen
    Message was edited by: Harri Harkonen

    Hi Christophe,
    We also have this issue. Goods Receipt from SUS is created in SRM but is not posted in backend (we have implemented extended classic scenario).
    I tried to use the BBP_DOC_SAVE_BADI to created an idoc which posts the material document in backend system (using fm IDOC_GR_CREATE).
    The goods receipt is posted in backend this way.
    Unfortunately we are not able to cancel or make a return delivery on this GR.
    I am very interest in your FM. Could you please share this, or tell me what changes you made to the GR in SRM.
    Thanks in advance.
    Rgds,
    Martijn

  • Extended Classic Scenario Pricing issue, can I over come by using SRM-MDM?.

    Hi SRM GURU'S,
    I am using  ECC 6.0, SRM 5.5, SUS, LAC, cFolders and SRM-MDM with Extended Classic Scenario.
    My Question is : In case of Extended classic scenario, there is issue with Pricing and conditions. Is there any possibility to overcome this issue by using SRM-MDM. Or do I have to go for IPC. My client has not brought IPC. I have to cover Pricing with the above components.
    Anyone suggest me, how to proceed.  Thanks in Advance. Awaiting for quick response.
    Thanks & Regards,
    John.

    Hi Masa,
    We can maintain Price and conditions as a record in CCM for Particular Material or Vendor. When you add that record to shopping cart it will update. I mean, If the provision is available in MDM, I don't want to use the Two components for same functionality.
    If I use IPC, Is there separate license for that. What else need to be updated to use IPC (Patches etc).
    If you have IPC configuration material, could you please share with me? How to bridge the SRM Conditions and ECC Conditions?
    Please clearly give me details.  I really appreciate you.
    Regards,
    John.

Maybe you are looking for

  • S10-2 sees sd card but cannot read,format

    I've already reloaded  the drivers from the website here and tried different SD cards, mostly 2 gig and less. Windows Explorer sees the sd card as drive E: but when I access it, the system tells me the disk is not formatted, ( even though it was on a

  • SAP Installation advice and guidence

    Hi, How to install multiple server on one PC For example: I need to install 3 to 4 server on single system 1) ECC6 2) SRM 5.0 and 3) MDM 5.5 (SRM MDM 2.0) on one PC My PC specification is as below 1) HDD 1 TB 2) RAM 4 GB I have installed SRM already,

  • New to SAP Netweaver...Please guide....

    Hi all I have recently joined this network. So, not sure wether this is right place to post such a question. I am a fresher in IT field. My level of knowledge is limited to core java and JSP, servlets. Now I am a member of project team which is worki

  • Not able to use Alert Configuration/Alert Inbox in the Runtime Workbench

    Hi Experts,                   I have installed PI 7.1 on my system. I'm not able to use the Alert Configuration/Alert Inbox in the Runtime WorkBench. It is asking for a logon and the logon which i used for ABAP & Java Stack is not working. e.g., For

  • TS3274 My ipad shows 4 updates for the apps but the ipad doesn't update

    IPad has 4 updates to do and the unit does not update.