Invoicing Plan functionality in Extended Classic scenario

Hi,
For PO's are created in SRM-Extended Classic scenario, kindly let me know on how to maitain Invoicing plans.
Thanks,
KB

Hi. You could use ERS.
Let's say you wanted an invoice plan to pay every month for 12 months, you could create a cart on an ERS vendor and order quantity 12, unit months.
Then every month the user could do a goods receipt for 1 month.
That would trigger an ERS invoice, just like an invoice plan would.
The only problem with this is that you are relying on the user to do the goods receipt.
Regards,
Dave.

Similar Messages

  • Invoice Plan on ERP extended classic PO?

    We are using ECS.  The ERP PO is display only as standard.  Can I still add an invoicing plan in the ERP system to this display only purchase order?

    Hi Paul
    Please refer to these details regarding Invoice Plans in SAP
    1) Maintain settings in Customizing for purchasing (for example, invoicing plan type, date categories, date descriptions, and date sequence proposals). The related path is IMG ---> Material Management ---> Purchasing ---> Purchase Order ---> Invoicing Plan ...... 
    2) The Purchasing document with FO Document Type (Framework Order) must be used. This document type requires that a validity period be entered in the PO header. This specification is adopted in the invoicing plan, provided that this has been predefined in Customizing for the relevant invoicing plan type. 
    3) The purchase order item must have an account assignment and Logistics Invoice Verification must be used. 
    4) The vendor must have agreed to use the automatic invoice creation facility (since we will use automatic settlement to create the invoice). In this case, the 'AutoEvalGRSetmtDel.' indicator must be flagged in the vendor master record. 
    5) Once Purchase Order is created with order type FO, ensure that the indicators for GR/IR control have been set correctly on the item detail screen.
    6) The Goods Receipt indicator may only be set in combination with the Goods Receipt Non-Valuated indicator. The Invoice indicator must be set.
    7) For the automatic creation of invoices, the ERS (Evaluated Receipt Settlement) indicator must be also set. A further prerequisite for automatic settlement is that a tax code must be entered in the purchase order.
    Regards
    Virender Singh

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

  • 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

  • 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

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

  • Cost distribution in Extended classic scenario

    Hi All,
    We are in SRM 4.0 using extended classic scenario.
    When we create a purchase order with cost distribution, it gets copied to backend system. But the partial invoice field in backend PO is always having the value "Distribution in sequence".
    In configuration for account assignment category, it has been defaulted to "Distribute proportionately".
    When we checked with SAP they told that for SRM POs it will always be distribute in sequence. It has to be distributed while posting MIRO. This value is hardcoded in SRM PO transfer program. It is very strange and moreover this is a essential functionality which needs to be in SRM.
    Any one using extended classic scenario, could you please tell me how you are handling multiple account assignments?
    Please help me.
    Thanks,
    Arun

    Friends,
    If you are using cost distributions in extended classic scenario, then could you please check and let me know the value that you are getting in the "Partial Invoice" field in Account assignment tab of backend PO.
    Please help.
    Thanks,
    Arun

  • 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

  • Extended Classic Scenario PPOMA_Purchasing Org and Group

    Hi gurus,
    We are working with SRM 5.5 and we are having problems with the assignments for the Purchasing organization and Purchasing groups in the PPOMA.
    In the documentation it says we should have one box for the R3 Purchasing Organization (flagged and referred to the backend POrg) and one for the Local Purchasing Organization (flagged but NOT referred to the backend POrg). The same for the Purchasing Groups, the one under R3 POrg will be flagged and referred to the PGroup in R3 and the one under the Local POrg will have the flag but it will not be referred to the backend PGroup.
    Afterwards, in the attributes for the Local POrg and Local PGroup, with the attributes PURCH_ORGX and PURCH_GRPX the local and the R3 POrg and PGroup will be assigned each other.
    The purchasers will be located in the Local PGroup. The R3 POrg and PGroup will never have users assigned.
    The problem is that all the workflow is only working if the "Local" POrg and Group have the backend purchasing organization and purch group assigned in the Function Tab. This means that the 2 boxes for R3 are no longer necessary. In the documentation it says that this version of SRM needs both boxes for the POrgs and the 2 boxes for the PGroups. We have flagged the Extended Classic Scenario.
    Any help on this? It's because of the version?
    Many thanks and regards,
    I will give Points!

    Hi Ana
    PURCH_GRP     Purchasing group     Number of an organizational unit that is indicated as local purchasing group in the organizational plan.
    This attribute is simulated. You define an organizational unit as company on the Function tab.
    PURCH_GRPX     R/3 purchasing group     Number of an organizational unit that is indicated as the R/3 purchasing group in the organizational plan. The value contains the ID and the associated backend system of a backend purchasing group.
    This attribute is simulated. You define the ID and the associated system on the Function tab.
    PURCH_ORG      Purchasing organization     Number of an organizational unit that is indicated as local purchasing organization in the organizational plan.
    This attribute is simulated. You define an organizational unit as purchasing organization on the Function tab.
    PURCH_ORGX     R/3 purchasing organization     Number of an organizational unit that is indicated as the R/3 purchasing organization in the organizational plan.
    This attribute is simulated. You define the ID and the associated system on the Function tab.
    can you elaborate more?
    in ECS also we can map the backend purchase organisation/ purchase group for purchasing activity.
    there might be a resposibilty tab for the backend purchase group might be mapped the responsible purchaser list (dept).plz check it up
    regards
    Muthu
    regards
    Muthu

  • Extended Classic Scenario - Can Purchase Requsition be created in R/3?

    Hi SRM Gurus,
    In Extended Classic Scenario, Is it possible to have Purchase Req to be created in the backend?
    Technically whether it is possible or not? Functionally, there is no such need, I agree.
    Thanks & Regards,
    Ramkumar

    Hi
    Please confirm what sceanrio in SRM are you planning for ?
    I have not tried this. In Extended Classic Scenario, using BADI " BBP_TARGET_OBJTYPE"    -> I guess, it's possible, but not sure. Try it out. 
    Purchase Order (PO) will be created in the R/3 system using the BADI -  BBP_TARGET_OBJTYPE. Please read the standard documentation of this BADI, before implementing the same.
    Regards
    - Atul

  • 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

  • Why Extended Classic Scenario

    Hello
    I understand the difference between Extended Classic and Classic Scenario with the follow on document creation. But, I need to understand the business benifits of implementing Extended Classic Scenario as opposed to Classic Scenario in SRM. In what business scenario do one suggest Extended Classic.
    Appreciate every answer
    Thanks
    Vijay

    Hi Vijay,
    The most important thing to consider when choosing the implementation scenario is to consider which system will support the different steps of the procurement process.
    In case of the classic scenario, after creation of the request (shopping cart) in SRM, the remaining process steps will be handled / supported  in the back-end system (ECC). Goods receipt can be executed in both systems.  This would be a good choice if the organization has already an operational back-end system and the users from the purchasing department are already familiar (and happy) with all the MM functionality.  SRM will only function as a support tool for administrating the purchasing needs of the end-users in the organization.
    In case of the extended-classic implementation scenario the complete purchasing process will be supported in the SRM system (most organizations prefer to use the back-end system for invoice verification). Thus requesters, purchasers, goods recipients etc. all will use the SRM system to support their respective activities.  This would be the preferred scenario in case both MM (ECC) and SRM are new to the organisation and will be implemented together.
    SRM offers the different users a nicer user interface as opposed to the R/3 screens. Also the (strategic) sourcing capabilities of SRM can only be used  when implementing the extended classic scenario. Same for the Suplier Enablement business scenariou2019s. Most are only supported when extended classic is active.
    So depending on the intentions of the organization a choice can be made. SRM only as a tool for administrating the decentralized request from the end users in the organization: Classic scenario will suffice. SRM as a tool to support the complete purchasing process, from sourcing till  evaluation - Extended classic will be the correct choice.
    Regards,
    Skander

  • Classic scenario & Extended classic scenario

    Hi Experts ,
    I am new to SRM ,  Is it possible to combine both classic scenario & Extended classic scenario . if it possible , then how to achieve this .
    Regards
    Vel.

    Hi Vel
    I suggest that instead of checking the possibility of implementing any combined scenario's like how you have asked ( Classic+Extended classic scenario).
    You need to map the Business requirement and how the Business teams wanted to handle the PO ,GR etc and accordingly you have to plan for implementation scenario. You can' customise the standard SRM delivered options for these scenario . I t is advisable to either go for Classic or Extended classic.   But combination of Classic & stand alone scenario is possible.
    for your ready reference i have given below capabilities of all scenarios, which you may already know..
    Key implementation scenarios
    u2022     Classic
    o     Implement EBP and one or more ERP system . All shopping carts refer to MM process in your ERP backend, your   ERP is the leading system. GR (Confirmations and invoices can be entered in Enterprise Buyer or ERP back end system
    u2022     Extended classic
    o     Purchase order is created locally within EBP system , if the data in the shopping cart is insufficient to generate a complete purchase order. The data is supplemented manually within the enterprise buyer system EB is the leading system , GR,IV can be done in both EBP and ERP system.
    u2022     Decoupled
    o     Combination of  classic and standalone scenario ,some items are locally handled, some items are transferred to the ERP back end system
    o     We are able to send PO from both the system.
    u2022     Standalone
    o     Your SC items create local procurement only, this means all the follow on doc like GR,IV will be done at EB system only.
    o     Only commitment & invoice posting will be done at ERP backend
    You can get the final Business requirement and plan.
    Regards
    Narahari

  • PO attachment transfer to ECC - Extended classic scenario

    Hi all,
    We are on SRM 5.0 ECS.As standard,can the SRM PO attachments be transferred to  ECC PO?Is this possible in  ECS?If so,what are the steps?

    HI Alexander,
    The purchase order in the Extended Classic Scenario is transferred to the backend system with different Function Modules. The
    attachment transfer logic was only implemented in the Classic Scenario.
    One reason for this decision was, that the leading Purchase Order in the extended classic scenario is the local one, and in the local purchase order the attachments are available.
    At the moment it is not planned to support the attachment transfer in the Extended Classic Scenario. The transfer of attachments to backend PO is developed only for Classic Scenario.
    I am sorry that this is not the result that you wanted. This also explains why in the ECS PO transfer BADI BBP_ECS_PO_OUT_BADI does not have the parameters for attachments where as the Classic PO transfer
    BADI does (BBP_CREATE_BE_PO_NEW).
    We have some notes related to SC and POR reporting issues when transferring attachments to ECC side, but ther are related to Classic scenario:
    1400088: SC attachments transferred to ECC PR are lost on EHP upgrade
    1413792 Attachment deleted after changing purchase order
    I hope this information help you to understand this issue,
    Kind Regards,
    Rafael Rhoden

  • 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

Maybe you are looking for