Changing existing classical scenarios in ID to ICo post PI upgrade

Dear Members,
Installed a test PI 7.11 system and restored primary PI DEV system backup on to the test PI system and then the test PI 7.11 system was upgraded to PO 7.4 dual stack system. Done with the post up-gradation activities and the test PO 7.4 system was up and running.
Now, all the ID config objects in the upgraded test PO 7.4 system remained as classical scenarios with sender agreement, receiver determination, interface determination & receiver agreement etc.,
Need a clarification here i.e., how to change the existing classical scenarios to ICo objects in the upgraded PO 7.4 test system..? Do we need to delete the existing sender agreement, receiver determination, interface determination, receiver agreement objects and manually build ICo objects for the respective scenarios (or) do we have any other alternative.
I suppose that the Content Migration Tool doesn't suffice my requirement, as the new PO 7.4 system is not a parallel system built against the existing
PI 7.11 system. I directly performed the upgrade activity on the test system and not on a parallel built system.
In this case, can someone advice how to change the existing classical scenarios to ICo objects i.e., manually (or) do we have any other alternative.
Br,
Saiganesh

Hello Martin,
Finally got it. In the migration tool, configured source system also with the same details as the target system and then the migration of classical to ICO was fine.
Closing the thread.
Br,
Saiganesh.

Similar Messages

  • Change from ECS to Classic Scenario

    Dear SRM Gurus,
    System: SRM Server 5.5
    We had activated Extended Classic and made baseline configuration, and tested some scenario.
    We now plan to change to classic scenario. So we removed tick from " Activate Extended Classic Scenario ".
    Problem: When am trying to create a LEADING PO in R/3 in Classic Scenario,through Shopping cart for a material for which no stock exist, system is creating LOCAL PO in EBP, and am not able to change the PO in R/3.
    Is there any NOTE to be applied to change to classic scenario? as we made configuration for ECS.
    Pls guide.
    Best Regards,
    Dinesh

    Hi Anil,
    I have gone through the postings made by you, Yann and others.
    Let me put forward my observations from what you have posted.
    1. Is the P.R / P.O getting created in the back end?
    You said you could not edit the P.O in back end.
    2. Is the shopping cart going to sourcing **** pit or directly creating a P.O in the front end (EBP)?
    If the shopping cart is going to sourcing then you can create a P.O in SRM but you can not edit the same in SRM and can be only editable in the back end R/3.
    If this is the case then in SPRO > IMG > SRM > SRM Server > Sourcing > check whether the " sourcing always carried out" is mentioned under sourcing tab for that product category. In this case the shopping cart always go to sourcing / purchaser's work list.
    If you change the setting to " Sourcing never carried out" then the shopping cart will create either a P.R / P.O in the back end based on the completeness of the data.
    Please let me know about these settings and incase any clarification is needed.
    Award points for suitable answers.
    Rgds,
    Teja

  • 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

  • SAP eSourcing with SRM Extended Classic Scenario

    Hi Team,
    We are using ECC 6.0 with eSourcing. Currently we use SRM 5.0 with Classic Scenario.
    Now we are planning an upgrade from SRM 5.5 to SRM 7.0 and want to do the Extended Classic Scenario. This will help us to do additional functionalities of SRM.
    eSourcing can be used for Strategic RFx and CLM functionalities.
    SRM can be used for SC, Operational Sourcing and PO. We can also use the SRM-SUS Scenario for PO confirmation and Invoices.
    Have any one used eSourcing with SRM Extended Classic? In that case, please provide some light into how to use all these application to better streamline the overall Source to Procure strategy.
    Also, do you think Classic is the way to go or Extended Classic is better? Any documents or pictures are greatly appreciated.
    Thanks
    Jogy

    Hi
    SAP provide standard integration b/w ECC and Esourcing/ CLM (PR (both inbound and outbound). However in case you decide to go with extended classic scenario,you might need e Sourcing/ CLM integration with SRM (since PO would be created in SRM) which is not provided out of the box by SAP. However custom interface (based on flat file transfer) can be built b/w SAP SRM and e Sourcing.
    MM-SUS scenario is not much different from EBP-SUS scenario in terms of functionality.
    Regards
    Mudit Saini

  • Account assignment not updated in SRM's shopping cart when changes are made in ERP's PO - Classic Scenario

    Hello!
    A customer has classic scenario and creates shopping carts using only cost center as account assignments in SRM.
    When the PO is created in ERP's backend, sometimes a purchaser changes the account assignment to Asset("A").
    The account assignment changed in ERP is not reflecting in the shopping cart and the result is that the requester can not make a goods receipt in SRM because the account assignment does not match the PO.
    Does anybody knows what shall be done so the account assignment in SRM is updated according to ERP?
    Shall I use BBP_DOC_CHANGE_BADI?
    Thanks in advance!
    Best regards,
    Karin

    Hi Karin,
    As Mithun rightly said, the changes made to the PO will not be reflected in the SC not just in Classic but in Extended Classic Scenario as well.
    We create a Confirmation against a PO and not against SC, so it is not necessary that the SC needs to be updated.
    Is the system allowing the creation of the Confirmation or is the error coming up when the confirmation is being posted on the backend system?
    Can you check the SLG1 in SRM for the error that it is triggering when the PO is changed?
    Regards

  • PO Change in Extended Classic Scenario

    Hi SRM Experts,
    Our client is using ECC 5 and SRM 3 (BBPCRM 4.0) and using classing scenario successfully.
    Now we have started using extended classic scenario for limited suppliers.
    Now the client requirement is to change the PO after approval.As you know that in ECC the PO can be displayed only.
    And the PO already directly submitted to the supplier.
    Is it possible to change the PO after submitting to supplier ?
    They are looking for some changes in text/shipping address etc.
    Appreciate all your suggestions.
    Thanks and Regards,
    Pradeep

    Thanks Masa for your quick reply.
    Could you please tell me that,we are using work flow for SC approval and when the Shopping Cart created the WF also starts and finally the SC get final approval the PO will push to supplier directly and the same will be replicated in ECC (display only).
    So after activating the version control will it still allow the user to change the SC/PO after completing the approval ?
    If so do we need to make any changes in our WF ?
    Thanks and Regards,
    Pradeep

  • Classic scenario: Update shopping cart with changes in backend PO?

    The Shopper would like to have visibility in their shopping cart (SRM 5.0, classic scenario) of changes made to the follow-on PO created in ECC6. Is it possible for the cart to be updated with changes made to the backend document, or would the customisation for this type of request be too complex?
    Any advice would be appreciated, thanks!

    Hi,
    Yes this report is reading the PO quantity and value and the history tab for follow-on documents such as GR or invoice.
    Thus the SC history is updated.
    Kind regards,
    Yann
    Message was edited by:
            Yann Bouillut

  • Deltas in changing Classic scenarios to Extended Classic Scenario

    Hi All,
       Currently my client has Classic scenario partially implemented and work in progress. Now a idea of changing to ECS is proposed because in the first place Classic/ECS for Pre-Encumberance is not  standard SAP 5.0 unless applying OSS which is not been proven successful so far.
    So I would like to know what Config be required to change Classic to ECS other than Material master product category determination and activation of ECS flag, and old POs to convert inorder to do Conf in SRM. Please advise soon as I need to suggest the board soon.
    Regards
    Rao

    Hi,
    Re: Switching over from Extended Classic to Classic Scenario
    Could be helpful.
    Thanks
    prasad.s

  • Classic Scenario change Material Group on PR

    In a classic scenario can the material group be changed on PR created from approved SC.
    We are unable to change it in our enviornment. Please confirm if it is standard SAP behaviour .
    Thanks.

    Hi Kumar,
    You can definitely change the PR in ECC system if you are in Classic scenario.
    Yes, even the material group can be changed in PR.
    In classic scenario the Follow on documents of shopping cart either PR or P.O depending on the setting in the configuration can be changed in ECC system as they are the leading documents.
    Check in case some exits or field controls have been put in place in your ECC system which would disable the ability to change some of the fields in PR.
    Hope this makes you more clear.
    Let us know in case of any further clarifications.
    Regards,
    Teja

  • Configuration changes of  "Classic to Standalone scenario"  in EBP system

    Hi,
    Could you guide me in configuration changes of "<b>Classic to Standalone Scenario</b>" in EBP system...
    Will I get any documentation on this..?
    Thank you...
    Best Regards,
    Thiru

    Hi Thiru,
    to change from Classic to Standalone Scenario, you have to change customizing point "Define backend for product category".
    If your set target system = SRM logical system, then follow on doc will be created localy in SRM -> standalone scenario.
    Rgds
    Christophe
    PS: please reward points for helpfull answers

  • Change of GR and Invoice in Classic Scenario

    Hi All,
    The classic scenario is chosen.
    The End user creates a SC -> PO is created -> GR is created -> invoice is created in backend system.
    The Account discovers that there is a difference between Invoice and PO - this will be handled in a workflow, where the end-user will receive a message saying please check this GR for deviance. There is found a deviance and now the end-user wants to correct the GR but the end-user doesn't have ECC access.
    Can the correction be done in SRM?
    Kind regards,
    Line

    Hi Line,
    Classic scenario enable to create, modify and delete GR in SRM or ECC.
    Kind regards,
    Yann

  • PO is not generated for completed SC in SRM.70 classic scenario.

    Hi,
    I am working on SRM 7.0 - Classic scenario.
    When a shopping cart is complete in terms of price, vendor (assigned) and other required data, item stays in transfer process. even we are adding items from catalog.
    If a SC is incomplete a PR document is created in backend without a problem but when a complete SC is oredered, the status of shopping cart remains item in transfer process. I can see in table BBP_PDBEI, backend object type (BE_OBJECT_TYPE) is correctly selected as BUS2012 and the document number of PO is also correctly selected.
    This is the case even for the SC ordered using catalog materials.
    I have checked following configuration and it seems to be ok.
    1. 'Define objects in backend system's
    2. Number ranges definition in SRM and ECC
    3. Document type attribute -BSA in PPOMA_BBP
    Configuraiton wise everything seems to be, I tried to manually transfer the SC using FM BBP_REQREQ_TRANSFER but it does not change the status of SC it remains I1111
    RZ20 does not show any error for the SC with status I1111.
    Is there any sepcial FM to push the SC in SRM 7.0?
    Any help/tips would be highly appreciated. Thanks in advance.
    Thanks,
    Ravi

    learnt that PO number has generated in SRM and the same PO number not exist in ECC.
    check SM58 , rz20 log or Application monitor for the shopping cart.
    or monitor shopping cart click the icon follow on document and errror message must throw in 1 minutes.
    let us see .
    1. what is the settings in define backend OBJECTS
    2. check all basic data in the shopping cart - especially org data
    3. run bbp_check_consistancy report for your id?
    4. every user has the same issue?
    SEE THE RICHARDO technique
    http://wiki.sdn.sap.com/wiki/display/SRM/ShoppingCartStatusI1111-+Resubmit
    Muthu
    Report BBP_ALERT_SB_NOTTRANSFERED is available to change the status of the shopping cart item from I1111 to 'Error in transmission' (I1112) and later on, it is possible to retransfer this shopping cart from Application Monitor/Monitor Shopping Cart transactions.
    1480994  How to process a shopping cart with status I1111
    Edited by: Muthuraman Govindasamy on Jul 16, 2010 11:31 PM

  • Extended Classic Scenario - PO Update issue

    Hello experts.
    We are working with SRM 5 in the extended classic scenario and we have a serious problem in a productive environment for the following case.
    (01) We create a purchase requisition (PR) in R/3 with several items;
    (02) We send PR to the SRM generating a shopping cart;
    (03) The buyer creates a PO for all items from the shopping cart;
    (04) The PO is transmitted to R/3;
    (05) For some cases buyer changes the PO wich is sent back (updated) to R/3;
    So far so good. The problem happens when some item in the request already has GR or Invoice. In those cases when the PO is updated on SRM, its transmission to R/3 does not occur, generating an error log that can be seen in transaction RZ20 of SRM.
    I understand that if any GR or Invoice exists for the item it can no longer be modified, but is it expected that no other item can also be modified from SRM? What is the expected behavior for this case?
    Moreover, even if the GR and Invoice have been canceled, we are still unable to update the PO in R/3 from SRM. Is this a expected behavior? It was our understanding that the PO should be updated if all incoming documents (GR, Invoice, SES ..) were completely canceled.
    We appreciate any help on this matter.
    Thanks and Regards,
    Evandro Miasato

    Hi, Masa,
    Thank you for your advice,
    I set the method U:Print Using Berkeley Protocol, after that
    in  trx. SP01 I have the Error Status on Composite Document -
    Status Incorrect (Reason Unknown).
    Best regards,
    Guzal.

  • Extended classic scenario local PO

    Hi All ,
    Need some inputs on the extended classic scenario local PO.
    There is couple of functionality which we need to do for the PO. I mean when the PO gets created automatically after shopping cart completely approved
    We can change the same PO from the process purchase order also.
    But if I want to map couple of the fields, when PO is getting created automatically how can do that one. And I donu2019t want map these fields when the PO is from the getting changed process purchase order also.
    I am using the BADI, BBP_DOC_CHANGE_BADI (PO_CHANGE Method) to map these fields.
    The thing is here , this BADI will call even for the automatic PO creation and also for changing the PO .
    Currently when I noticed PO gets created automatically by the user id u201CWF_BATCH u201C , So I am using the same the logic like .
    If sy-uname = WF_BATCH
    Do the mapping part
    Endif,
    But I donu2019t think so; this logic will work all the times.
    Please can anyone give me some pointer for the same, it will be really helpful for me .
    Seeking your help on this
    Thank you,

    Hi Latha,
    This is a bit tricky one. Yes you are vry correct, the logic is not that fool proof, as the PO can be subjected to so many changes back & forth; even approvals can be done after a change is completed etc.
    The other alternative is to go ahead the document version. You can use the function module BBP_PD_PO_GETDETAIL and the table E_VERSION will contain all the versions of the PO. This should differentiate the change & initial PO verions.
    Hope you can build your logic based on this; this is a better logic on par with the existing one.
    Regards
    Kathirvel

  • Currency issue in Local PO in SRM ( SRM 4.0, Ext. Classic scenario)

    Hello SRM community,
           There is contract exist at a Product category level which is created in currency Euro & can be used by both local as well as well global purchasing org. for subsequent PO releases( Call off).
    We are using extended classic scenario, SRM 4.0. before explaining the scenario, here is what we have maintain for a vendor in BBPMAININT
    Let say..
    Vendor(Business Partner)             Purchasing org.                     Currency
    100168                                         Global Purchasing org.     Euro
    100168               Local Purchasing Org                SEK
    Now there are two scenarios in this
    Scenario No.1
    When Strategic purchaser directly creates any purchase order release for Local purchasing org. with reference to above created contract
    & if he chooses Euro as a currency, system throws a warning message as "Currency Euro in Purchase order is different then the PO currency SEK of vendor.
    but still he manage to order the PO Euro.
    Scenario No.2
    If strategic purchaser creates shopping cart for local purchasing org. where S/C currency is Euro & assign above contract as a source of supply.
    Local PO gets created but the system swaps the currency in PO automatically to SEK which is nothing but the currency available for Vendor/Pur. Org combination
    in BBPMAININT.
    Why there is this difference in behaviour.
    I mean, when you directly creates a PO release wrt contract, system allows you to select currency other then the one maintain in BBPMAININT for Vendor/PUr.Org combination however if you try to create a SC for Local pur. org  with contract as a valid source of supply then system overrides the SC currency with the currency maintain in the BBPMAININT for  Vendor/PUr.Org combination
    We would like to know if there is any way possible by which we can maintain SC currency in PO & should not allow system to
    swap it with what is being maintain in Vendor/Pur.Org combination in BBPMAININT.-
    is there any Badi available where we can change this behaviour..& if poosible a way of approach to do it through Badi....
    Any help is well appreciated with full rewards to valuable suggesation.
    Regards
    Bharat Morajkar

    Hi Bharat,
    You can use the BADI <b>BBP_DOC_CHANGE_BADI</b> to make changes to the document, after user entry and before saving the document to the database.
    BBP_SC_CHANGE method can be used for changing shopping carts.
    Hope this works in your case. Try it and let me know.
    Rgds,
    Teja

Maybe you are looking for