Reminders / expediters to vendor

Hi All,
I would like to send delivery reminders to vendor automatically through email. I am doing the same in ME91F. Where in message i am taking as external send (5). When i generate message its saying message generated. But the same is not visible in SCOT. Please let me know where do i need to config about the message (reminder) to vendor and any other settings.
Rakesh

Any inputs,,

Similar Messages

  • Tables for following scheduling agreements and PR data

    Hi All ,
    Please can you tell me table names if I want the following information
    1. Scheduling Agreement Created By, Amended By, Modified Date, Plant
    2. Req Created by, Released by, Cost center, plant
    Thanks in advance
    Vinayak

    To view the fields listed in a table go to Tcode SE11 and enter the table name and execute
    EBAN  - Purchase Requisition 
    EBKN  - Purchase Requisition Account Assignment 
    Req Created by Table:EBAN Field ERNAM
    Released by- Table:EBAN Field FRGGR
    Cost center- Table:EBAN Field FISTL (Funds Center)
    plant-Table:EBAN Field WERKS
    For Scheduling Agreements following are the tables:
    EKEH    - Scheduling Agreement Release Documentation 
    EKEK    - Header Data for Scheduling Agreement Releases 
    EKET     - Scheduling Agreement Schedule Lines 
    EKETH   - Scheduling Agreement Schedules: History Tables
    You will find the following list of fields in these tables:
    MANDT                          Client
    EBELN                          Purchasing Document Number
    EBELP                          Item Number of Purchasing Document
    ETENR                          Delivery Schedule Line Counter
    EINDT                          Item Delivery Date
    SLFDT                          Statistics-Relevant Delivery Date
    LPEIN                          Category of Delivery Date
    MENGE                          Scheduled Quantity
    AMENG                          Previous Quantity (Delivery Schedule Lines
    WEMNG                          Quantity of Goods Received
    WAMNG                          Issued Quantity
    UZEIT                          Delivery Date Time-Spot
    BANFN                          Purchase Requisition Number
    BNFPO                          Item Number of Purchase Requisition
    ESTKZ                          Creation Indicator (Purchase Requisition/S
    QUNUM                          Number of Quota Arrangement
    QUPOS                          Quota Arrangement Item
    MAHNZ                          No. of Reminders/Expediters for Schedule L
    BEDAT                          Order date of schedule line
    RSNUM                          Number of Reservation/Dependent Requiremen
    SERNR                          BOM explosion number
    FIXKZ                          Schedule Line is "Fixed"
    GLMNG                          Quantity Delivered (Stock Transfer)
    DABMG                          Quantity Reduced (MRP)
    CHARG                          Batch Number
    LICHA                          Vendor Batch Number
    CHKOM                          Components
    VERID                          Production Version
    ABART                          Scheduling agreement release type
    MNG02                          Committed Quantity
    DAT01                          Committed Date
    ALTDT                          Previous delivery date
    AULWE                          Route Schedule
    MBDAT                          Material Staging/Availability Date
    MBUHR                          Material Staging Time (Local, Relating
    LDDAT                          Loading Date
    LDUHR                          Loading Time (Local Time Relating to a
    TDDAT                          Transportation Planning Date
    TDUHR                          Transp. Planning Time (Local, Relating
    WADAT                          Goods Issue Date
    WAUHR                          Time of Goods Issue (Local, Relating to
    ELDAT                          Goods Receipt End Date
    ELUHR                          Goods Receipt End Time (Local, Relating
    ANZSN                          Number of serial numbers
    NODISP                         Ind: Reserv. not applicable to MRP;Purc
    hope this helps!

  • Regarding The Message determination

    Hi
    is it necessary to assign form everytime to the standard output type?

    Hi
    You need to create condition record for the condition type Provided the below mentione setting are done
    Also check for the below points
    The message type denotes different kinds of message in the SAP System (for example, communications sent to vendors, such as purchase orders, order acknowledgments, reminders, expediters etc.).
    To define a message type, you must enter the following:
    Message type   Alphanumeric key of up to 4 characters, uniquely identifying a message type.
    Access sequence Key for the access sequence.
    Description
    Text describing the message type.
    Detail data (only the most important data is described):
    Transmission medium
    One-character numeric key determining the type of message processing (e.g. printout, transmission as fax or e-mail).
    Time-spot
    One-character numeric key defining the point in time at which message processing takes place (e.g. immediately a document is saved or with the next selection run).
    Partner role
    Partner role defining the recipient.
    Condition access
    Indicator allowing you to specify that the default value for the relevant message is to be determined using the condition technique.
    Access TNADR
    One-character, numeric key defining the conditions upon which the print parameters are determined (see the section "Adjust Forms")
    Note
    The values entered in the detail data for transmission medium, time-spot, and partner role are automatically adopted as default values when a message record of the relevant message type is created.
    Setting up fine-tuned control for each message type
    For each type of message you create, you must specify the operations for which it is to be used.
    For example: New (original) output, output of change notices, or output of urging messages (expediters).
    First choose "Perform function" and then "Purchasing document -> Purchase order -> Messages -> Fine-tuned control". You must do this for all purchasing documents

  • Expeditors in PO u2013 need to understand if we can stop after 1st 3 expeditors

    Dear Experts,
    For a PO, I have 1st, 2nd, 3rd   Expeditors as 1, 3 and 5 days respectively.
    Delivery date as per PO is 23.03.2011.  So, as expected, 1st, 2nd, 3rd expeditors were sent on 24/25/27th March Respectively.  So far its ok.
    Since, the GR is done on 17.04.2011, a total of  7 expediters have been sent (1 each for 1st, 2nd and 3rd and then afterwards, 1 expeditor per every 5 days).
    My question is, is this the standard behavior of SAP to send expeditor after every 5 days once the first 3 expeditors have been sent until GR is done?
    Where exactly is this configured in SAP? 
    Suppose if I want to send no reminders after 1st 3 reminders, can we achieve this?
    Please suggest me your valuable inputs
    Regards,
    Shetty

    Hi,
    At PO Item Level >>Delivery Tab >> Expeditors Days are mentioned for sending 1st three Expediators ,Below this field "No. Exped " Consist of the Number of Expeditors to be send for the particular line Item.
    Check these field for the value. The field Value should be blank , if only 3 Expeditors are to be sent.
    "Number of Reminders/Expediters :
    Number of reminders or urging messages issued to a vendor with respect to a certain item.
    In the SAP System, a distinction is sometimes made between reminders (issued prior to the due date) and urging messages (issued after the due date and also referred to as "expediters" or "follow-up" letters).
    Use :
    This field shows the total number of reminders and urging messages (expediters) for all schedule lines relating to this item.
    Regards
    Mascot.
    Edited by: Manish Kumar on May 2, 2011 1:07 PM

  • Quotation comparison for Landed Cost

    Dear Experts,
    Can anybody please explain how to enter Conditions in RFQ (TC-ME41). Our requirement is that, we want to ask the quotation to vendor for Discounts, Freight charges, Taxes.
    (all including final price)
    and also quotation maintenance (ME47) for those conditions.
    Price comparison (ME49) for landed cost (final price)
    Please explain the process.
    Thanks in Advance !!!!!!!!!!!!!!!!
    Vijay

    For Sch Agreement - Table EKET
    MANDT                          Client
    EBELN                          Purchasing Document Number
    EBELP                          Item Number of Purchasing Document
    ETENR                          Delivery Schedule Line Counter
    EINDT                          Item Delivery Date
    SLFDT                          Statistics-Relevant Delivery Date
    LPEIN                          Category of Delivery Date
    MENGE                          Scheduled Quantity
    AMENG                          Previous Quantity (Delivery Schedule Lines
    WEMNG                          Quantity of Goods Received
    WAMNG                          Issued Quantity
    UZEIT                          Delivery Date Time-Spot
    BANFN                          Purchase Requisition Number
    BNFPO                          Item Number of Purchase Requisition
    ESTKZ                          Creation Indicator (Purchase Requisition/S
    QUNUM                          Number of Quota Arrangement
    QUPOS                          Quota Arrangement Item
    MAHNZ                          No. of Reminders/Expediters for Schedule L
    BEDAT                          Order date of schedule line
    RSNUM                          Number of Reservation/Dependent Requiremen
    SERNR                          BOM explosion number
    FIXKZ                          Schedule Line is "Fixed"
    GLMNG                          Quantity Delivered (Stock Transfer)
    DABMG                          Quantity Reduced (MRP)
    For PR  - Table   CEBAN
    BANFN                          Purchase Requisition Number
    BNFPO                          Item Number of Purchase Requisition
    BSART                          Purchase Requisition Document Type
    BSTYP                          Purchasing Document Category
    BSAKZ                          Control indicator for purchasing document
    LOEKZ                          Deletion Indicator in Purchasing Document
    STATU                          Processing status of purchase requisition
    ESTKZ                          Creation Indicator (Purchase Requisition/S
    FRGKZ                          Release Indicator
    FRGZU                          Release status
    FRGST                          Release Strategy in Purchase Requisition
    EKGRP                          Purchasing Group
    ERNAM                          Name of Person who Created the Object
    ERDAT                          Changed On
    AFNAM                          Name of Requisitioner/Requester
    TXZ01                          Short Text
    MATNR                          Material Number
    EMATN                          Material Number Corresponding to Manufactu
    WERKS                          Plant
    LGORT                          Storage Location
    BEDNR                          Requirement Tracking Number
    MATKL                          Material Group
    You can check the table name & fields in SE84 also - ABAP Dictionary - Fields
    Rgds,
    Vikas

  • Tab " delivery" in po .use of reminder field

    Sir,
    In a po there is a delivery tab where we  set reminders 1,2,3
    how is this functioning with delivery date as well as how are the reminders send to vendors
    ply explain
    regards
    amey

    Hi Amey ,
    The standard o/p type used for dunning is MAHN.
    If you have already done customising for o/p type NEU in case of PO , the same customising applies to MAHN , only the o/p Form may Change.
    Maintain the condition records in MN04 and monitor the same in Transaction ME91F.
    Regards
    Ramesh Ch

  • Message determination

    Hi All,
    how will seach sequence work in PO prinout outs.   Like new prinout, change prinouts, reminders etc.  For eg; How will the system know the that it has to print a changed PO and reminders to the vendors.
    Also, will be there be any indicators to distinguish between new PO prinouts and changed PO printouts.
    Regards
    Ajay

    Hi,
    I wanted to know. If i have taken a prinout and issued to vendor.  Now i changed qty and price in PO.  Took another prinout.  will there be any indicator in PO to let the vendor know that the PO has been ammended. 
    regards
    ajay paliyan

  • 855 order acknowldegement

    Hi Gurus,
    can anybody please expalain me the differences between the tcodes ME2A, ME91F (ME91), ME92F (ME92). In what cases are these tcodes used. Please exaplin with an example. we are trying to implement the 855 EDI order acknwodlegement from the vendor process. I just wanted to understand these tcodes, what they do. For example the PO against which the order acknowledgement which is yet to be received, will it show up in ME2A, Let us say we put 7 days of monitoring time to receive the vendor acknowledgement, then will ME92 show the PO in the output only if we have passed past the 7 days mornitoring time. PLease exaplin in this fashion. Also when do we start to send the reminders to the vendor. Is it after the monitoring time has passed ? are any other  tcodes that we could leverage around order acknowledgement, confirmations etc.
    Thanks
    Anusha
    Edited by: anusha vemulapati on Mar 11, 2011 11:28 PM

    If you are looking for Order acknowledgement, which is ALE message ORDRSP and IDOC type ORDERS05. Corresponding EDI message is 855. In standard ALE process order acknowledgement can only happen at order level. So if there are multiple orders from same ship-to party multiple ORDRSP messages (ORDERS05 IDOCs) will be created.
    Since you want to send  acknowledgement for all orders recieved for one ship-to-party in a day, I am sure you will be thinking of processing them in a batch. If you need to send this information as IDOC then, you will need to create a custom IDOC because ORDERS05 has order number in the header segment and that can be only one. But if you are converting IDOC into EDI message then you can handle this in the program that is converting IDOC to EDI message.
    For generating ORDRSP messgae on creation of Sales Order you need to configure standard output type BA00.
    Cheers,
    Sanjeev

  • Job runs RM06ENMA (ME91F)  generates a reminder after 3rd reminder is sent

    Dear Experts,
    I schedule a job for RM06ENMA (ME91F) to send reminders/expeditors to vendors
    First 3 reminders are sent based on 1st/2n/3rd reminders from PO.
    My problem is, after 1st 3 reminders are sent, why there are more reminders sent?
    How can I stop this? Infact, a reminder is sent every 5 days after 1st 3 reminders.
    Pls help
    regards
    Shetty

    the batch job executes the program of transaction ME91F to generate a reminder.
    It checks the 3. level reminder days for any reminder above the 3rd level.
    as you have set the 5th day for the 3rd level reminder, SAP will generate the next reminder 5 days later e.g. on the 10th, then on the 15th , on the 20th etc. until your order is delivery completed

  • GR Reminder

    Hii sap,
    it is possible to have GR reminder by e-mail if PO still not yet GR after few month or week ?

    You can send Urging/Reminders letters to vendor via (ME91F)
    For that u need to satisfy certain prerequisites
    1. Message determination has to be configured for purchasing document
    2. Message records must have been created through master data maintenance (Purchasing menu).
    3. Purchasing document should have been created first and transmitted to the vendor first.
    4. Maintain purchasing value key in Purchasing view of the mateiral master (select purchasing value key with suitable reminder 1, reminder2, reminder 3)
    If you want to set different reminder level for your material, create new purchasging value key in IMG screen
    IMG->Materials management>Purchasing-->Material Master->Define purchasing value key
    Cretae new purchasing value key Enter Reminder 1, Reminder 2 and Reminder 3
    The days after which u want to send reminder to vendor if the material is not delivered according to the delivery date mentioned in PO

  • Printout of  reminders  to vendor

    Hi Gurus
    can any one pls tell tell  how to get all reminders list with respect to vendor after PO is issued with reference to purchasing valu key

    Hi,,
    You can send Remainders/Expediters  w.r.to Purchasing value key using --ME91f..
    here u can select the purchase documents and generate message and save.
    It will triger printout output.
    please reward  the points ,, if your question is answered.
    bye,,
    sudhakar

  • Reminders at vendor level

    Hello,
    I'm facing the following problem: one of my clients creates purchase orders on text, so no material code, no inforecord. But he wants to avoid to set the reminders in every PO. So the question is: is it possible to assign reminder-settings at vendor-level? if so, how?
    Or are there other possibilities: doc-type, account-assignment, ...?
    Kind regards,
    Renaat
    Edited by: Renaat Eeckhout on Feb 2, 2011 12:21 PM

    Hi Renaat,
    Another possibility in IMG for purchasing --> Material master --> Entry Aids for Items Without a Material Master. Here you can assign purchasing value keys (normally used in material master) to material groups.
    BR
    Raf

  • Reminders for PO and RFQs

    Hello Sapiens,
    Can anybody tell me the execution of reminders in purchasing value key?
    Theory is that we get reminders before or after or on the delivery date. but how can we see its execution?
    is it possible to see its execution on development or ides server?
    how me91A and me91f are connected to purchasing value key?
    Kindly explain in detail...
    thanks

    Hi
    See the following def
    Definition
        Number of days representing the time interval at which reminders or
        urging letters/messages (may also be termed "chasers", "hasteners" (UK)
        or "expediters" (USA)) are to be issued to the vendor.
    Use
        A negative number of days means that a reminder is to be issued to the
        vendor n days prior to a certain date (for example, the delivery date or
        the deadline for submission of quotations).
        A positive number of days means that a letter or message urging delivery
        or submission of a quotation etc. is to be issued n days after the due
        date.
    Procedure
         In the case of purchasing documents, the time intervals are defaulted
         from the purchasing info record or, if one does not exist, from the
         material master record.
    Dependencies
         The basis for the reminder intervals is the delivery date or deadline
         for submission of quotations etc.
         In the event of several reminder levels, the days must be set out in
         ascending order of time, without gaps.
    Example
         In the event of a delay in delivery, you can send messages urging the
         vendor to deliver ordered materials a total of three times, at interval
         of 10 days:
    In IMG Material management -
    purchasing -
    mat master-----purchasing value key
    assign the reminder
    maintain this in mat master
    in me91f generate message
    if useful rward point
    Reg
    S.Anbu

  • Auto Email to vendor for followup balance quantity deliver

    Hi All,
    Auto Email to vendor for followup balance quantity deliver,
    I have an requirement that Auto email to vendor for reminder with some fixed days (example : 10 days),
    Please suggest me any configurations for this and suggest me how to proceed on this..
    Thanks

    Hi,
    You can use Urging Reminders to supplier with output type MAHN.
    Here you set all the reminders to vendors based on days set up earlier then delivery date or 10 before delivery date 5 days before delivery date.
    Refer the below docs it may help you..
    Output message type MAHN Dunning - ERP SCM - SCN Wiki
    Reminders and Urging Letters (Expediters) - Purchasing (MM-PUR) - SAP Library

  • Automatic reminder to vendor

    hi friends..............
    my client wants to reminder automatically to vendor.
    can anyone suggest wat are the settings i have to do???
    i have give 3 reminder dates in purchase info record.
    plz help..................

    Hi,
    Please check below information. You can check more details on help.sap.com
    If you have specified reminder levels under the item details of a purchasing document, the system is able to generate reminders and urging letters (expediters) automatically.
    You can enter up to three reminder levels. For example, the reminder levels 10-20-30 mean that urging letters are issued 10, 20, and 30 days after the due date for submission of a quotation or for the delivery of ordered goods. (Note: in the SAP System the term "reminders" is often used to denote such messages issued before the due date, whereas the term "urging letter" or "expediter" commonly stands for a perhaps more strongly worded admonitory message issued after the due date. However, this distinction is not consistent, and may not apply outside the SAP environment. The corresponding term for "urging letter" in the FI component is "dunning letter", and relates to overdue payments.)
    A negative number means that a reminder is to be issued prior to the deadline for submission of quotations or the delivery date for ordered goods. For example, if you enter 5- as the reminder level, a reminder will be sent 5 days prior to the quotation submission date.
    Prerequisites
    u2022     The message determination facility has been set up in Customizing for Purchasing.
    You can also work with the standard settings. For further information, see Tips for Fast Message Determination Set-Up in the Implementation Guide (IMG).
    u2022     Message records must have been created through master data maintenance (Purchasing menu).
    u2022     The purchasing document involved must have previously been transmitted to the vendor.
    Activities
    You first generate messages for all purchasing documents for which reminders or urging letters need to be issued and then output these messages.
    Generating a Message
    1.     Choose <Purchasing document>  Messages  Urging/reminders.
    2.     Enter the selection criteria for the documents that should be checked with regard to the necessity of issuing reminders or urging letters.
    Enter a reference date. The system takes this date as the basis for calculating the periods after which reminders or expediters are due.
    Select the List untransmitted messages field to ensure that the list also includes those documents whose reminders and urging letters are in the message queue but have not yet been outputted.
    3.     Choose Program  Execute.
    You see the documents in respect of which due dates are approaching or have been exceeded.
    4.     Select the documents for which you want to generate reminders or urging letters. Then choose Edit  Generate messages.
    5.     Save your selections.
    Outputting Reminders or Urging Letters
    6.     To output the message, choose <Purchasing document> MessagesPrint/transmit.
    7.     Enter the same selection criteria as in step 2 and then execute the program.
    8.     Select the messages to be outputted (printed or transmitted) and then choose Edit  Output message.

Maybe you are looking for