Reservation with Extended classic scenario

Hi ;o)
I'm working at a costumer were we have extended classic scenario. We want to be able to make reservations in the backend if the item is on stock, and we have seen in a solution matrix from SAP that this should be possible.
The configuration for reservations should be done according to the guides - but no reservations is created when ordering a stock material.
I was searching on the developer network, and came across a topic, where it was stated that reservations could only be made with classic scenario (or using a BAdI where you switch the extended on and off depending on product category). Do any of you know if this is really a fact?
Thanks in advance
Maria Hvenegaard, Denmark

Hi
Read this first.
<u>You can use BBP_CREATE_RES_BACK BADI using Se18 Transaction.
This BADI You can find in SPRO -> Supplier Rel. Mngmt. -> SRM Server -> Business Add-Ins -> Follow-on document generation -> Reservation in Backend System</u>
<u>If you want to create reservation, you have first to switch from ECS to classic scenario through BBP_EXTLOCALPO_BADI then you have to implement BBP_TARGET_OBJTYPE badi to determine the criteria to create a reservation in your backend.</u>
<u>We need to maintian the customising setings in SPRO Transaction.
Define objects in Back end systems. Maintain the document type EC or ECPO for Purchase Orders and not for creating reservations. Maintain number ranges (RS) and align the same to R/3 or backend systems. In setting up the org plan in the PPOMA_BBP Transaction, the attribute for resevation - Attribute BWA should be maintained too, if reservations are to be created in the backend system.
Movement Type Accounting Object
201 Cost Center
221 WBS-Element
231 Sales Order
241 Asset
Example :
logicalsystemname\201</u>
<u><b>Maintain the following Settings in the IMG using SPRO Transaction.</b>
1.For internal Procurement > 1.Always Reservation for Material types Subjected to inv Mgmt
2.For External Procurement >1.Always purchase Requisition.
Note -> The plant that you use to create the shopping cart might not be extended to handle inventory management. Select a right plant which is extended to inventory management and you will see a reservation being created.</u>
Be aware that:
- with the classic scenario you can create PR, PO and/or Reservations in R/3, but there is no local purchasing document (except the SC), so all functions around the local PO will not be possible.
- with the extended classic scenario, you can only create PO in the backend, but a local PO exists in SRM.
Concerning GR, it is possible to make it in SRM for both scenario
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Similar Messages

  • SRM 7 : Vendor record replication in backend with Extended Classic Scenario

    Hello,
    We are implementing SRM 7 with Extended Classic Scenario and Supplier Self-registration.
    Can you explain what is to be configured to get the new vendors replicated to the backend?
    Thanks in advance.

    Hi,
    It is possible to transfer suppliers to ERP system, if you use 'Supplier registration with ERP' scenario. After registration and acceptance, newly registered suppliers would appear on supplier monitor from where you can transfer them to backend system.
    Check the below link for more details:
    http://help.sap.com/saphelp_srm50/helpdata/en/cf/35074152aff323e10000000a155106/frameset.htm
    Regards,
    Sanjeev

  • 'BAPI_POEC_CREATE' function doesn't work with extended classic scenario

    Hi everybody.
    Antecedents:
    We are working in an extended classic scenario.
    When we create a Purchase Order via ITS in SRM, the system works ok, the PO is replicated in the ERP system.
    But when we execute “BAPI_POEC_CREATE” function module in order to create a PO in SRM, no message are available in the application monitor, but the PO is not replicated in the ERP system.
    Both exampled were created with exactly same data (partners, items, categories, accounts, …)
    Moreover when we modify the second PO created via ITS, the systems doesn’t show any error message, we can order our PO again without error, but the PO isn’t replicate in the ERP system.
    1. We executed “BAPI_POEC_GETDETAIL” function module, and there is only a difference between POs, E_PO_STATUS table.
    PO created by transaction has 8 entries:
           I1009 X
           I1015 X
           I1021
           I1038
           I1039 X
           I1043
           I1080 X
           I1180
    And PO created by BAPI has 5 entries:
           I1015 X
           I1021
           I1038
           I1043
           I1180
    2. We run “BBP_PD” transaction, and there is only a difference.
    PO created by transaction mode shows:
    - Message: W BBP_PD 830 Default values have been taken from Vendor PRUEBA10/purchasing organization Área Global Compras (org. compras)
    And PO created by BAPI
    - Message: No Messages
    Could anyone help me with the problem?
    Thanks in advance.
    Raúl.

    Hi Raúl,
    this is exact, BAPI_POEC_CREATE is designed to create local PO.
    If you want to replicate it to R/3, then you have to change it to an ECS PO.
    In BADI BBP_DOC_CHANGE_BADI, called at the real beginning of BBP_PD_PO_CREATE, you will have to change some data to enable the ECS scenario:
    - change header subtype to EP
    - change header log system to SRM (keep FI LS as is)
    - determine a backend purch group & org
    - complete BE fields (be_object_id, be_object_type, don't change be_log_system because it will be determined during the transfer, be_pur_org and be_pur_group will also be determined during the transfer)
    - ... and maybe other R/3 relevant fields
    Compare both PO one by one, and adapt the gaps.
    Rgds
    Christophe
    PS: please reward points for helpfull answers

  • 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

  • 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

  • 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

  • ASN for extended classic scenario

    Hello all,
    we have SRM with extended classic scenario (EBP-MM),
    is it possible to use ASN (shipping notification) functionality in our system ?
    Kind regards,
    Arthur

    Hi
    ASN can be created by the vendor in SUS system for that XI mapping is required. ASn can be created in SUS by any vendor users. I guess it's not possible with ECS.
    Please check the SAP Consulting Note 1026638 GR Output Integration with MM-SUS Scenario for R/3 <= 47
    You need to have functional background for this:
    To create an ASN against PO or SA release:
    1. you need to compulsarily put how much qty you are sending against the reqd. qty(shown by PO / SA )
    2. dispatch vehicle no. (optional)
    3. road challan no. (optional)
    4. one more optional entry ( sorry I forgot)
    Useful related pointers ->
    Re: how does the GR get into SUS---MM-SUS Sceanario
    ASN in Extended Classic Scenario with SUS
    SUS ASN & Invoice
    The specified item was not found.
    Do let me know.
    Regards
    - Atul

  • Use of Purchase info records in SRM SC in Extended Classic scenario

    Hi All,
    We have implemented SRM 7.13 with Extended classic scenario. If we have Purchase info record in SAP ECC for the material, it gets populated in SRM SC in Source of supply Tab but the price of Purchase info record does not get updated in the SC line item.
    Can anyone let me know which configurations is required to fetch the Purchase info record price or we need to have a customization to achieve this.
    Thanks,
    Ankur

    HI Ankur
    when you say the price did not get updated did you check the sequence which is used for price determination ?
    1. User entry
    2. Contracts
    3.  Info record
    If still you think it is an issue please check the report  EBP_GET_BACKEND_PRICES and let me know if your problem gets fixed?
    Regards
    Vinita

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

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

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

  • 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

  • Payment term key with limit days in Extended Classic Scenario

    Hello,
    We have an SRM 4.0 implementation (SRM Server 5.0 with Support Package
    9) using the Extended Classic Scenario.
    When a shopping cart is created, it must be approved, and then a
    purchase order is generated (first locally at SRM, and then is
    replicated to the backend).
    The problem is that the payment term key (field at header level EKKO-
    ZTERM) of the backend purchase order is empty, only in cases when we use a payment term key which have several different values for the
    field "limit days" (T052-ZTAGG in backend, BBP_PAYTERM-ZTAGG in SRM).
    Example:
         ZTERM     ZTAGG
          K180           09
          K180           19
          K180           31
    If the payment term key selected has no several values for the field "limit
    days" (one single entry), the payment term key arrives correctly at the backend purchase order.
    Example:
         ZTERM     ZTAGG
          E000           00
    In SRM table BBP_PAYTERM we have upload the backend payment terms
    (using report BBP_UPLOAD_PAYMENT_TERMS). In other threads it is said that you must copy the entries generated by the report with the logical system of the SRM system, but in extended classic scenario it seems to be not necessary.
    We have already implemented note 846009, in order to use always the backend payment term, but the error didn’t get resolved.
    We have our vendor business partners mapped to the local and backend
    purchasing organizations, but it is only necessary indicate the Payment term key for the Backend Purchasing Organization.
    Regards

    hi,
    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>
    BR,
    Disha.
    Pls reward points for useful answers.

  • SC with Limit Item using Extended Classic Scenario?

    Hello,
    Can we implement SC with Limit Item using Extended Classic Scenario.
    I mention that we replicate the Product Categories from R/3 backend.
    We have tried to create a SC with Limit item, but the data on Quantity, Price and Tax is not picked up at PO level.
    Regards,
    Shaiek

    Hi
    Please try out this.
    For the time-being,
    Try de-activating all the custom BADI Implementations and check, what is happening, in the standard SRM system. How does it behave incase of limit item ?
    Incase it works fine, without any Custom Implementation active in the system, I suspect there is something wrong in your current deactivated BADI Implementation.
    Since i don't have access to your system , Please paste the code here.
    Hope this will help.
    Please reward suitable points.
    Regards
    - Atul

  • 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

  • Classic and extended classic scenario with one EBP

    Hello Guys
    If I have a one EBP and multiple ERP back ends. For one backend, I need to have classic and other to have extended classic scenario. How this can be fulfilled. Is it possible, if so please provide the configuration setup.
    Thanks in advance.

    Hello,
    In BADI BBP_EXTLOCALPO_BADI  method DETERMINE_EXTPO.
    you can try this.
    Structure Declaration
      DATA: ls_item_data TYPE bbps_extpo_badi.
    Moving item data to a structure
      MOVE-CORRESPONDING item_data TO ls_item_data.
    SELECT SINGLE LOGSYS FROM comm_product
                                     INTO lv_logsys
                                     WHERE PRODUCT_GUID =  ls_item_data-PRODUCT .
    If  lv_logsys = 'XXXCLNT010' "backend system
          Cancelling the enhanced classical scenario
            bbp_extpo_gl-bbpexpo  = space.
    ELSE IF lv_logsys = 'YYYCLNT010'  "backend system
          Cancelling the enhanced classical scenario
            bbp_extpo_gl-bbpexpo  = ' X'.
    ENDIF.
    Regards,
    Neelima

Maybe you are looking for