Documents / Cookbook on how to configure Extended Classic Scenario?

We currently have the Classic scenario and are thinking of changing to exteded classic becuase we want to use the sourcing cockpit in SRM 7.0.  Does anyone have any good documentation on how to configured Extended Classic?

Hi Sivakumar,
If you mean how to archive PO in MM side, please refer to the following info:
====
In ECC system, if you want to archive a MM PO, please use transaction
SARA->archive object MM_EKKO.
456129 FAQ: Archiving in purchasing
401318 Archiving: Additional information
====
If you want to delete this ECC PO, please use BAPI_PO_CHANGE and
refer to the following test data:
Parameters:    PURCHASEORDER      =  XXXXXXXXX
Parameters:    POITEM
PO_ITEM                        = 00010
DELETE_IND                     = X
Parameters:    POITEMX
PO_ITEM                        = 00010
PO_ITEMX                       = X
DELETE_IND                     = X
You also need to run BAPI_TRANSACTION_COMMIT after BAPI_PO_CHANGE for updating the change.
Regards,
Ivy

Similar Messages

  • Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

    We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
    Please provide some help in solving this issue.

    Hello,
    This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC).  And accepting the SES in ML81N will generate GR posting.
    For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
    So basically, for service items you create confirmation and for materials you create ASN.
    Regards,
    Prasanna

  • 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 close extended classic PO in ECC...

    Hi Friends...
    We are in SRM 7.02 and ECC 6.05 in Extended Classic Scenario. One PO had been created for 1 Quantity 3 years ago. There was no GR/IR document posted against that PO. Now that PO had been archieved from SRM. But still PO is available in ECC with open quantity and also its appearing in the open PO report. Now requester wanted, the PO to be closed in ECC and shouldnot appear in the open PO list.
    How to handle this situation.. How to close the extended classic PO in ECC at this scenario. As PO not available in SRM, we can not do anything from SRM side.
    Your inputs are appreciated....
    Regards
    Sivakumar Kandasamy

    Hi Sivakumar,
    If you mean how to archive PO in MM side, please refer to the following info:
    ====
    In ECC system, if you want to archive a MM PO, please use transaction
    SARA->archive object MM_EKKO.
    456129 FAQ: Archiving in purchasing
    401318 Archiving: Additional information
    ====
    If you want to delete this ECC PO, please use BAPI_PO_CHANGE and
    refer to the following test data:
    Parameters:    PURCHASEORDER      =  XXXXXXXXX
    Parameters:    POITEM
    PO_ITEM                        = 00010
    DELETE_IND                     = X
    Parameters:    POITEMX
    PO_ITEM                        = 00010
    PO_ITEMX                       = X
    DELETE_IND                     = X
    You also need to run BAPI_TRANSACTION_COMMIT after BAPI_PO_CHANGE for updating the change.
    Regards,
    Ivy

  • How to configure extended withholding tax to get correct 1099MISC

    hi sap guru's
    How to configure extended withholding tax to get correct 1099MISC
      any body help me configuration  and generating 1099misc form.
    raju
    [email protected]

    Hi,
    Pls. check your email. I just sent documents on configuration and reporting for 1099MISC.
    Hope this helps.
    Regards,
    Chirag

  • 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
    regards
    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.
    Regards,
    Prashant
    Do reward points for helpful answers

  • In an extended classic scenario, how can we make few purchase orders to sta

    Hi All,
    In an extended classic scenario, how can we make few purchase orders to stay local (i.e. without copying it to the back end). The decision criteria to stay local is information other than product category, i.e. using pcard and the cart value.
    Thanks
    Murali

    Murali,
    As I said usually this integration is done using ALE - IDOCs. You can find the all the configuration do be done here.
    http://www.sappro.com/downloads/OneClientDistribution.pdf
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    In this the filtering can be done at two levels.
    1. Data Filtering
    2. Segment Filtering
    Data Filtering:
    Data filtering can be done in dustribution model where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
    Look at BD64 where you can do the config for data filtering.
    Regards,
    Ravi
    Note : Please mark the helpful answers

  • How differentiate POs classic scenario and POs extended classic scenario?

    Hi Gurus,
    Is possible determine that some POs are generated in SRM system and send to R3 (Extended classic scenario) and other POs only to send from SRM to R3 system (classic scenario) in the same system?
    How we can differentiate which POs should be sent to R3 (classic scenario) and which not? Is possible use type of document for example? Could you explain me if exists standard process?
    The objective is determining the following: Is necessary differentiating POs created in SRM of importation and  should be sent to R3 system (classic scenario), and in case of local POs (not importation) is necessary extended classic scenario.
    I have understood that there is a scenario that includes the Classic and Extended Classic, I think is called Decoupled scenario.
    Thanks for your help!!

    Hello,
    Yes this is possible.
    You can do it automatically based on the product category. You must define the back-end system you wish to use for each product category by making the relevant settings in Customizing for SAP SRM under SRM Server --> Technical Basic Settings --> Define Backend System for Product Category
    Check the online documentation here: http://help.sap.com/saphelp_srm701/helpdata/en/f3/6f505050404ce99151722a79a2c089/frameset.htm
    You can also use Business Add-In BBP_EXTLOCALPO_BADI to overwrite settings made in Activate Extended Classic Scenario and implement more rues for the scenario determination, e.g. based on the purchasing organization for manually created PO's.
    First you set you system to Activate Extended Classic Scenario : SPRO --> SAP Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
    Then you set exceptions in the BAdI.
    Regards
    Franck

  • Extended Classic Scenario  - how does the integration work ?

    Hi,
    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,
    fiona

    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.
    Regards.
    Vadim

  • 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

  • How is PR created in Extended Classic Scenario

    Hai friends
    How is PR created  in Extended classic Scenario
    Please let me know
    Regards
    Krishna

    Hi krishna,
                  Shopping cart in SRM is equal to PR in R/3.If it is Classic scenario we can customise to create PR in backend for the shopping cart in EBP , but in ECS directly PO will be created against the shopping cart in EBP and it will replicate to R/3 system.
    Regards,
    Baparao.

  • Sharing attachment documents (e.g. for P.O.) in extended classic scenario

    Dear SAP SRM gurus
    in the SAP SRM extended classic scenarios (rel. 7.0) attachments of Purchase Order can be viewed also in the backend SAP ECC 6.0  as per SAP Notes n. 1582690 and 1057932 . But I am not sure if attachments are phiysically transmitted from SAP SRM to ECC or only document url is passed even though, as per SAP note n.1357551 it seems that only url is passed.
    My customer wants to know if there is the possibility of not replicating them.
    Any suggestions will be appreciated.
    Many thanks in advance
    Best regards
    Gianluigi Brenna
    Edited by: GIANLUIGI BRENNA on Jul 29, 2011 2:56 PM
    Edited by: GIANLUIGI BRENNA on Jul 29, 2011 3:08 PM

    Hello,
    In extended classic scenario the attachments arent transferred to ECC as the source document is in SRM. The document in ECC is only a copy and it cant be modified also.
    If we have to transfer attachments, then probably implicit enhancements to standard logic might be needed.
    Regards,
    Prasanna

  • Multiple PO document types/transaction types in Extended Classic scenario

    Hi All,
    We are on SRM_SERVER 550, Extended Classic Scenario.
    We have a requirement where we need to create multiple PO document types (based on certain criteria).
    I have noticed that in standard, there are only 2 transaction types provided for SRM PO - ECPO and ECDP.
    We need more document types and these should be triggerred automatically after SC is approved.
    I understand that we need to maintain all the PO transaction types in SRM, number ranges in SRM then maintain the same transaction types as PO document types in R/3 and same number ranges in R/3.
    I also understand that the change for document type needs to be done in BBP_DOC_CHANGE_BADI.
    I have 2 specific questions:
    1. We need to maintain attribute BSA for the users. Here we need to mention the document type and source system. What should be the source system mained in attribute BSA for ECS? Should it be the SRM system or R/3 system?
    2. In BBP_DOC_CHANGE_BADI to change the PO document type/transaction type in ECS scenario, which field should be changed? Should it be ET_ITEM- BE_DOC_TYPE?
    Regards,
    Srivatsan

    Srivatsan,
    To create new transaction type:
    Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Define Transaction Types
    To create new number range:
    Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Number Ranges --> SRM Server Number Ranges --> Define Number Range for Local Purchase Orders
    You can define to create automatic PO when a SC was created in: Supplier Relationship Management --> SRM Server --> Sourcing --> Define Sourcing for Product Categories
    Rgs,
    Pedro Marques

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

    Hi
    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
    OR
    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...
    Regards
    Virender SIngh

  • Convert classic in extended classic scenario

    hai,
    i wanted to convert classis scenario into extended classic scenario.what are all the steps that i needed to be follow.does it require any implementation of badi?how the po will be sent to the r3 in display mode?
    could anyone give the solution
    Edited by: chakradhar  nannapaneni on May 11, 2009 12:45 PM

    Hi,
    1.     Activate the extended classic scenario
    When the extended classic scenario is set, SRM generates a local purchase order for each item in the shopping cart. All follow-on documents are created in the backend system as well as locally in the SRM
    2.     Activate IPC pricing
    Since SRM 3.5 IPC (Internet Pricing Configurator) pricing is mandatory for extended classic implementations.
    In the classic scenario you can replace the IPC by the simplified pricing
    IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Cross-Application Basic Settings  Activate Extended Classic Scenario
    IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Business Add-ins for SRM Pricing
    Check whether the BAdIs relevant for the pricing are activated correctly and filled with the correct coding:
    BAdI                                     I            PC Pricing (Extended)          Simplified Pricing (Classic)
    BAdI: BBP_PRICEDATA_READ
    Implementation:. BBP_PRODUCT_PRICE                     Not active         Active
    *BAdI: PRODUCT_UPDATE2
    Implementation. IPC_UPD_PROD_BUFFER2     Active         Not active
    Regards,
    Abraham

Maybe you are looking for

  • How can I create a search filter on my muse project?

    How can I create a search filter on my muse project like the 'sort by' function of this website? http://trufcreative.com/work By that I mean be able to narrow down the content displayed on a single page (preferably with an animation) without having t

  • My website works in IE but not firefox

    this is my web page: http://www.andrew-leonard.co.uk/Mallorca/mallorca%20ferns.htm It usess css to define layers and javascript to show and hide the layers. It uses a dhtml menu system by Milonic to execute the javascript This is part of the code for

  • InDesign Server as a reporting service

    Hi, Im looking for help/guidelines regarding InDesign. I'm a software architect working on a line-of-business application that will eventually require printing about 5 hundred thousand personalized report (of about 20 pages each) over a couple of day

  • Tolerance days related to discount

    As to note 1033219, the number of tolerance days is subtracted from the document's due date. It would be good to be able to have such functionality also for discounts which are not affected by the existing behaviour.

  • Anyone else having crash problems with mountain lion and parallels 8.0?

    Anyone else having crash problems running Mountain Lion and Parallels 8.0 ?