Extended Classic and Invoicing Plans

Hi All,
We want to use the extended classic scenario for SRM but need to use invoice plan functionality in ECC to make scheduled payments.
Does anyone have an idea has to how we can accomadte this?
I've thought of adding a custom field which can indicate an invoice plan is needed and then changing the scenario to classic for that particular order but the user would then require access to ECC to amend the PO.
Is there anyway of adding the invoice plan data in SRM and then passing it to ECC?
Cheers
Chris

Hi. Do you want to use periodic or partial invoice plans?
If it was periodic you could put custom fields in the cart for start and end date and period type (monthly, weekly etc) and hide them when appropriate using the BBP_UI_CONTROL_BADI.
Then you could use a BADI or user exit in ECC / R/3 on PO create to read the fields from SRM and poulate automatically.
Instead of a new field to indicate that it is an invoice plan why not configure a new account assignment category in SRM to indicate that it needs an invoice plan? Just copy what you use now but call it "Invoice plan". Probably a bit easier than a custom field for this, especially if you are using custom fields for the actual invoice plan info. A custom field would work fins too though.
If you want to use partial invoice plans you would probably have to write a whole new transaction in SRM to allow you to pick up a list of POs from the backend and then have a new screen where you specify the partial dates and values.
When you save in the nwe transaction it could call a function in R/3 that populates the partial dates.
Regards,
Dave.

Similar Messages

  • Manually blocking SRM Extended Classic PO invoices

    Hi All,
    I understand that in tcode MRBR, when we select the radio button:  Manual Payment Block, we can see those invoices blocked at the Header Level.  (tcode MIR4, Payment tab, Pmnt Block field)
    It seems that only those invoices blocked at the time of invoice data entry (MIRO) are displayed.  But many times, we need to manually block the invoice AFTER it has already been entered and those are not displaying in MRBR.
    We are using SRM Extended Classic Config (if that matters) and are on ECC 6.0 SP10.  To block the invoice after the invoice has already been posted, we need to use tcode FBL1N to find the coordinating FI doc # and block it in that transaction code.  When we do that, it does show the block on the coordinating MM invoice number when viewing in MIR4, but it doesn't show in MRBR.  In other words, table BSEG shows the block, but table rbkp_blocked does not.
    Is there another way to manually block at the header level AFTER the invoice has been entered??  (so that it shows on the MRBR report).  Or is this a possible error with SAP's FI/MM integration?
    I thought I'd post my question here first before submitting an OSS message.
    I'd appreciate any guidance on this,
    Cindy

    Decided to just create custom reports to view blocked invoices either in FI or MM.

  • Invoice plan and ERS

    Guys,
    What is the difference between ERS and Invoicing plan?
    Are they both same? In that case, why is the settlement done on Tcode MRRL for ERS and MRIS for Invoice plan....?
    Please clarify my doubt.
    Happy holidays,
    Nureya

    Hi ,
    Please go through this below points difference between invoice plan (MRIS) and ERS (MRRL)  in invoice verification process.
    Use of Invoice plan in SAP MM ( Logisitic Invoice Verification )
    Through the use of Invoicing Plan for leasing agreements and such like, you aims to considerably reduce the manual data entry effort in the purchasing and invoice verification (A/P) department. 
    The invoicing plan enables you to schedule the desired dates for the creation of invoices relating to the planned procurement of materials or services independently of the actual receipt of the goods or actual performance of the services. It lists the dates on which you wish to create and then pay the invoices. 
    You can have the system create the invoices automatically on the basis of the data in the purchase order, thereby triggering payment of the vendor. It is also possible to enter the invoice for an invoicing plan manually. It is recommended that the invoice shall be created via Logistics Invoice Verification ---> Automatic Settlement --->Invoicing Plan Settlement. This 
    transaction can also run in the background. 
    Following are necessary customizings and preconditions for using the Invoicing Plan functionality in SAP - 
    1) You must maintain the 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. 
    4) The Logistics Invoice Verification must be used. 
    5) 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. 
    Furthermore, 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. The Goods Receipt indicator may only be set in combination with the Goods Receipt Non-Valuated indicator. The Invoice indicator must be set. 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. 
    Please go throuth this SAP help linkl
    [Help.SAP.COM|http://help.sap.com/saphelp_46c/helpdata/en/75/ee0d3355c811d189900000e8322d00/content.htm]
    ERS
    [ERS|http://help.sap.com/saphelp_srm30/helpdata/en/fb/8dec38574c2661e10000000a114084/content.htm]
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20c57f75-d26f-2910-c3aa-dee124530121?quicklink=index&overridelayout=true
    Prerequistic settings for ERS:
    1. Vendor master purchasing data  ( Flagged as GR-Based Inv Verification: Indicator specifying that provision has been made for goods-receipt-based invoice verification for a purchase order item or invoice item.
    Auto Eval GR Settlement Delivery: specifies that evaluated receipt settlement or the automatic generation of the invoices are allowed in relation to materials supplied or services performed
    Auto Eval GR Settlement Return: Specifies that automatic evaluated receipt settlement of return items is allowed.
    2. Check in Info record to Ensure that No ERS indicator is not checked in the info record for the vendor, Material + Vendor + Plant + Purchase organization.
    3. In PO ( Tax code maintain and Ticked GR based IV and ERS indicator )
    4. Settled the invoice using MRRL
    Difference between ERS and Invoice plan are :
    " ERS is the automatic invoice payment settlement to our supplier like EDI payment.
    Once we received the GR quantity system automatically settled the payment using ERS t.code MRRL.
    " There are two types of invoice plan ( Partial and Periodic invoice plan ) - is used to settled the Rental , period based payment etc using MRIS.
    With Thanks,
    Thiru

  • Difference between Classic Scenario and Extended Classic Scenario

    Hi Expers,
    I need your help again........:-)
    I just want to know what is the differne between classic and Extended Classic Scenario.
    Points will be rewarded
    Thank you
    sam

    Hi Sam,
    (explaination frm a previous thread)
    Difference between scenarios
    WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
    With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
    If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
    Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
    In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).
    Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
    Please check this too:
    http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
    BR,
    Disha.

  • Reverting to classic scenario in SRM7.1, from PPS and extended classic

    Hello  Experts,
    Recently we have moved  from SRM7 to SRM 7.01, in which we can have PPS without Extended classic scenario.
    As business wants classic scenario, How can we make the system as classic , in which PPS and extended classic is activated.
    any badi is available for this? Please help.
    Regards,
    Raju

    Raju,
    Basically you have few points to keep in mind. (yes you need to activate the SPRO config for extended classic, apart from this).
    1. switch between extended classic and classic is actually defined by the backend logical system of the document. if thats SRM itself then it follows the path of extended classic or if it is ECC then it follows classic.
    because its basically creating a follow on document and that explains the scenario.
    2. it also depends on what object are you expecting to be created. from a SC many documents can be created.
    a. PO in SRM
    b. PO in ECC
    c. PR in ECC
    d. Reservation in ECC
    - so, if you can define at any point that where is your document to be created and what is to be created you can control the flow.
    Now to do this. if you have few options.
    Option1:
    1. set the object types(2) for product categories (config, backend document type).
    2. implement BBP_EXTLOCALPO_BADI  to switch off extended classic
    Options 2:
    1. in doc change badi, change the backend destination to ECC
    2. in Badi BBP_TARGET_OBJTYPE pass the object type you want your follow on document to be.
    hope this explains

  • Can we use both Stand alone and Extended classic in one SRM system

    Hi All,
    Our client is now using Stand alone SRM system with back-end R/3 FI-CO system. Now they want to go Extended classic scenario for few product categories.
             Would it be possible to use both in one SRM system? If possible could you please provide what are the sequential steps to do this?
                 Thanks in advance.
    Regards,
    Ram

    Hi Ramesh,
    How did you end up solving your problem, as i have the same scenario.  Did you use this BADI (
    SRM Server->Business Add-Ins->Control Extended Classic Scenario->Activate Extended Classic Scenario)?  Based on my reading, it seems this BADI is relevant to switch between extended classic and classic scenarios. 
    From what i understand, we can control the standalone scenario via the define backend system configuration (SAP SRM -> SRM Server -> Technical Basic Settings -> Define Backend System for Product Category).  In my scenario, I have one set of product categories, so i will likely need to implement this BADI (BBP_DETERMINE_LOGSYS, method:   DETERMINE_LOGSYS - SAP SRM -> SRM Server -> Business Add-Ins ->Shopping Carts and Requirement Items -> Determine Backend System / Company Code) in order to determine the correct backend system based on company/plant for example. 
    Did you then leave the extended classic scenario activated (IMG --> Supplier Relationship Management -> SRM Server-> Cross-Application Basic Settings->
    Activate Extended Classic Scenario)? 
    Or how did you achieve both standalone and extended classic using one SRM server?
    cheers,
    AD

  • SRM standalone and extended classic

    Hi Experts,
    Configuration: ECC 6.0  (with Ehp4 installed - (not activated)
                           SRM 7.0
    Just want to seek confirmation of my understanding re: SRM implementation scenarios. Is it possible to have a extended classic and standalone setup using the same SRM server with same client? Both will have the same product categories. These will be for two separate entities/companies.
    Thanks in advance.
    Regards.

    Hi Mike,
    How did you end up solving your problem, as i have the same scenario.  Did you use this BADI (
    SRM Server->Business Add-Ins->Control Extended Classic Scenario->Activate Extended Classic Scenario)?  Based on my reading, it seems this BADI is relevant to switch between extended classic and classic scenarios. 
    From what i understand, we can control the standalone scenario via the define backend system configuration (SAP SRM -> SRM Server -> Technical Basic Settings -> Define Backend System for Product Category).  In your scenario, you have one set of product categories, just like mine, so i assume you had to implement this BADI (BBP_DETERMINE_LOGSYS, method:   DETERMINE_LOGSYS - SAP SRM -> SRM Server -> Business Add-Ins ->Shopping Carts and Requirement Items -> Determine Backend System / Company Code) in order to determine the correct backend system based on company/plant for example. 
    Did you then leave the extended classic scenario activated *
    MG --> Supplier Relationship Management -> SRM Server-> Cross-Application Basic Settings->
    Activate Extended Classic Scenario)? 
    Or how did you achieve both standalone and extended classic using one SRM server?
    cheers,
    AD

  • 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

  • Why extended Classic is implemented

    Hi Everybody,
    I was working in SAP SRM for past 3 years and only Support Experience. Yesterday attended an interview and he asked me why your client has implemented Extended Classic why not Classic Scenario?
    I know it depends to client-to-client.
    Can any one let me know the list of points need to be discussed to support this question. My answer was not impressive.
    Sree

    Hi Sree,
    You are right here it depends on the client whether to configure the system for extended classic and classic scenario.
    The extended classic scenario suits customer who wants to
    their purchasing department to save time and money by using the streamlined purchasing functionality of SAP SRM
    use the full sourcing capabilities offered by SAP SRM, yet who also want to be able to confirm and invoice direct materials
    the flexibility of being able to pre-enter confirmations and invoices
    Where the classic scenario suits the customer who wants:
    wide user group, for example employees not necessarily working in the purchasing department, to be able to enter their requirements quickly and easily. SAP SRM’s functionality and ease of navigation allow this, as it requires only minimal training
    their purchasing department to operate solely with the functionality offered by the backend system(s)
    For whom a transfer of purchasing activities to SAP SRM is not viable in SAP SRM
    You can use both the classic and extended classic capabilities by configuring the product categories
    Please let me know if the above answer is helpful.
    Best Regards,
    Ankit Jain

  • Extended Classic Scenario

    Referring to note 963000, we are about to install SRM 5.0 as AddOn to
    Ecc ERP 2005. In SRM we would like to implement the "Exteded Classic
    Scenario", meaning the procurement process will take place locally in
    EBP and a copy of data is replicated to the beckend system (ECC).
    Is the "Exteded Classic Scenario" compatible with the "SRM as add-on"
    installation? Note 963000 sais "The following scenarios are released
    within SRM AddOn: ... Self service procurement (classic deplyment)":
    does that mean that only the "Classic scenario" (meaning only Shopping
    cart on EBP, the rest of the purchasing process on backend) is
    available?

    HEllo,
    Only self-service scenario is supported. Means classic, extended classic and standalone.
    HTH
    Gordan
    Message was edited by: Gordan Flego
    Message was edited by: Gordan Flego

  • Sourcing in Classic/Extended Classic

    Hi Gurus,
    Can any one guide me through the difference in sourcing in Extended classic and classic scenarios.
    I am concern about the process while converting the SC in to PO.
    What is the difference in that Process.
    IS

    Hi
    Check the below links
    Extd classic:   http://help.sap.com/saphelp_srm70/helpdata/en/e0/f6be5157a24340bf7b1279854a52e1/frameset.htm
    Classic:  http://help.sap.com/saphelp_srm70/helpdata/en/d3/c9ca09052e47cd996279d765991177/frameset.htm
    Regards
    Kiran

  • HR520 Shift and workforce planning

    Hi
    Can anyone  send me
    HR520 Shift and workforce planning
    My details are there in my business card

    I do know that workforce does work with both classic and epma planning applications.
    It has been a while since I have been on a pure workforce application though I didn't think it actually added metadata to the dimensions.
    Cheers
    John
    http://john-goodwin.blogspot.com/

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

  • 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

  • Partner functions OA and IP missing for Vendor in Extended classic PO

    As part of current Classic scenario, we have maintained OA (Ordering Address) and PI (Invoicing Party) for a vendor in R/3. We have also maintained different ordering addresses for multiple plants in the Vendor master: Partner functions screen --> Alternative data.
    I would like to acheive the same functionality in Extended Classic scenario. We have replicated the vendors from R/3 to SRM. After activating Extended Classic scenario, we see only VN as the partner function in R/3 PO.
    Q1. How can we enable OA and PI partner functions in R/3 PO (Extended Classic) ?
    Q2. How can we enable different ordering addresses for multiple plants in R/3 PO (Extended Classic) ?

    Hi
    Which SRM Server are you using ?
    <b>You need to maintain Partner Functions in the SRM Server - SPRO Transaction - Configuration Settings.</b>
    <u>Here is the Path from SPRO Transaction -></u>
    <b>Supplier Relationship Management -> SRM Server -> Cros Application Basic-Settings -> Define Partner Functions</b>
    <u>Maintain Similar entries as mentioned below.</u>
    Function      Function     Type    Usage     Description                           Abbreviation  
    00000016     0013     B2B     Requester               RQ
    00000017     0007     B2B     Contact Person               CP
    00000018     0011     B2B     Bidder                    BI
    00000019     0012     B2B     Vendor                    VD
    00000020     0002     B2B     Goods Recipient               GR
    00000025     0014     B2B     Portal Provider               PP
    00000026     0008     B2B     Responsible Employee          RE
    00000027     0017     B2B     Ship-To Address               DP
    00000028     0003     B2B     Invoice Recipient               IR
    00000029     0015     B2B     Invoicing Party               IP
    00000030     0018     B2B     Ship-From Address          SP
    00000034     0002     B2B     Plant                    PLNT
    00000038     0001     B2B     Sold-to Party               ORDR
    00000039     0026     B2B     Preferred Vendor               PRVD
    00000051     0019     B2B     Purch. Org. Auth. For Release     AREL
    00000074     0025     B2B     Service Agent               SERV
    00000075     0031     B2B     Location     LOCA
    00000097     0034     B2B     Invoicing Party Employee          IPEm
    <u><b>Hope this will definitely help.</b></u>
    <u>More details -></u>
    <b>For 1), see these links below -></b>
    Partner function missing in backend PO
    Re: Error in transmission while PO cration
    "Multiple" partner data at PO header
    Partner functions in plan driven MM-SUS
    Re: Partner function not found
    Number range for business partner
    Re: Problem with BP. Assignment: Business partner person to user not unique
    Error in creation of Employee for Business Partner
    Re: enter exactly one partner of type vendor
    Re: Business partner as Vendor and Invoicing Party
    Partner functions in EBP for extended Classic Scenario
    Classic Scenario PO has multiple OA Partner Functions for Vendor
    <u>For 2), see the pointers -></u>
    <u><i>There is an article written by Jason Didday at www.saptips.com entitled "mySAP SRM and SAP R/3 Partner Functions: Supporting OAs, VNs and IPs" that you may find useful.</i></u>
    <u>In SRM, there is no standard relation betwwen plant and vendor master data.
    You can use BBP_GET_VMDATA_CF BADI to add backend data in SRM while using BBPGETVD and BBPUPDVD transactions.</u>
    Replication of Ordering Address from R/3 to SRM
    Re: Adding Partner Function to R/3 PO from SRM in Classic using BADI
    Partner function Payee in SRM
    Adding Partner Function to R/3 PO from SRM in Classic using BADI
    Do let me know.
    Regards
    - Atul

Maybe you are looking for

  • Macs can't find Epson Workforce 840 on network.

    I have an Epson Workforce 840 connected to my home network via the printer's internal wifi.  Home network is served by Apple Airport Extreme.  The network serves a mac mini and two macbook airs, all running OSX Mavericks. Since the upgrade to Maveric

  • CC Image wipe starts with ghost/negative image from previous image

    I have several images wiping onto a screen side by side, one after the other. However after the first image appears, the ghost of that image appears as I start each following wipe. This happens continually throughout all subsequent images. Here's an

  • Damaged iTunes Library causing problems

    My iTunes library is damaged after shut down and iTunes has restarted empty. I have tried to reimport all my music files but the same thing has happened again (three times). This has also affected my dock, passwords etc - I am afraid this may be part

  • How to Edit Scheduling Paramenters in Meetinplace 6

    Hello All, Have Meeting Palce 60.639.0 and want to adjust the "Max Adv Days to schedule from 90 to 180 in Meeting Time, but I am not able to make any changes? am logged in as an administrator, but cannot changes the values or save as those buttons ar

  • Is it illegal for iTunes to access all my passwords(FB,TW,etc)

    I have made a backup to my Iphone5(encrypted), i did not put a password to it, but when i try to Restore from that backup, it asked me a password, i searched on web and i find that this password was the one from my Facebook account(it is not stored i