Setting automatically message type MAHN in POs.

Hi,
how can I set automatically the message type in POs so that clicking on "Messages" button
will show message type MAHN ?
Yours faithfully

you can only have MAHN as message type if you run ME91F and your PO fulfills the criteria to be reminded.

Similar Messages

  • To SET -UP message type 5 External Send to the purchase order approver

    Hi All
    Please help me to To SET -UP message type 5 External Send to the purchase order approver
    Susan

    Susan,
    This to me sounds like a release strategy setup using workflow. Could you please set up Release strategies initially and and then the workflow part couldd  be handled by a workflow personnel.
    Else, Setup teh message type with medium 7, and partner function MP, put the user name in the partner field. Go to communication method, choose the recipient type and fiull other required parameters and you should be set.
    Edited by: Pavan Kumar on Apr 6, 2010 12:27 PM

  • Payment release required; payment block set automatically Message no. F5707

    Hello Friends,
    I am trying to post vendor down payment with T.CODE F-48 but is am getting this Error " Payment release required; payment block set automatically, Message no. F5707"
    Will any budy please make me clear with this issue ....
    Have a nice day...
    Regards
    Amresh...

    HI g.amresh,
    Please check with the Payment Requiest F-47.  Are you using this function then check Receipt box in F-48.  I think that would be the reason. 
    Regards

  • Configuration setting for Message type to take OA print out put

    Hi All,
    Please let us know how to configure setting for Message type  for OA in SD to take print or to get print preview.
    Pls let me know .
    Regards,
    Nagaraj S

    hhv

  • Output Message Type MAHN not getting picked up in PO

    Hello Experts
       I have configured customized output type ZMAH (similar to MAHN) for reminder process. When I am creating PO this output type is not getting picked up automatically. If I am maintaining it manually I am able to send message for ME9F (Purchase Order) and ME91F (Reminder) successfully. Upon deremination analysis I am getting this message 502 " Output ignored (requirement 103 not fulfilled) ". Reminder are getting picked up from Purchase Value Key to PO.
    Any help is appreciated.
    Thanks
    Ankit

    Hello Tej
      I have maintained output device but same result.
    Here I am listing all parameters that I have used for configuration can anyone please take a look and let me know if I am missing anything
    Steps for new Message Type for PO Reminder (ZMAH)
    1.     Defined new Table 026 Purchasing Output Determination: Document Type
                                                        (ii) 027 Purchasing Output Determination: Purch. Org./Vendor for EDI
    2.     Defined new access sequence Z515 Access Sequence for Archiving.
    Following are parameters to the Access Sequence
    Access Sequence Number = 1
    Table = 026
    Description = Purchasing Output Determination: Document Type
    Requirement = 103
    Exclusive = Yes (box checked)
    Access Sequence Number = 2
    Table = 027
    Description = Purchasing Output Determination: Purch. Org./Vendor for EDI
    Requirement = 103
    Exclusive = Yes (box checked)
    3.     Maintain Output Type ZMAH for PO
    General Data
    Access Sequence = Z515
    Access to condition (Checked)
    Multiple Issuing (Checked)
    Change Output
    Program = SAPFM06P
    FORM Routine = ENTRY_NEU
    Replacement of Text Symbol
    Program = SAPMM06E
    FORM Routine = TEXT_SYMBOL_REPLACE
    Default Values
    Dispatch Time = Send Immediately (when saving application)
    Transmission Medium = External Send
    Communication Strategy = 0001 (E-mail Document)
    Processing Routines
    Transmission Medium = 5 (External Send)
    Program = SAPFM06P
    Form Routine = ENTRY_NEU
    Form = MEDRUCK
    Partner Roles
    Medium = External Send
    Funct = VN
    Name = Vendor
    4.     Fine-Tuned Control: Purchase Order
    Oprat. = 3
    CType = ZMAH
    Name = Output for Reminder
    Short Text = Urging letter (expediter)/reminder
    Update Print Related Data = Yes (checked)
    5.     Maintain Message Determination Schema: Purchase Order
    Procedure RMBEF1 (Purchase Order)
    Step = 101
    Cntr = 3
    CTyp = ZMAH
    Description = Output for Reminder
    Requirement = 103
    6.     Assign Schema to Purchase Order
    Procedure RMBEF1
    7.     Define Partner Roles for Purchase Order
    Out. = ZMAH
    Med = 5 (External Send)
    Funct = VN
    Name = Output for Reminder
    Name = Vendor
    8.     Test Condition Maintained in MN04 (Master Data)
    Purch. Org. = 0001
    Vendor = 101281
    Partner Funct = VN
    Medium = 5 (External Send)
    Date/Time = 4 Send immediately (when saving application)
    Output Device = LP01
    Cover Page Text = Reminder PO number &EKKO-EBELN&
    Also I have configured Purchasing Value Key, reminders are coming to PO correctly.
    Thanks
    Ankit

  • Message type NEU in POs

    Hi,
    how can I set SAP so that it will create automatically two message type NEU one in italian and the other one in english ?
    Regards

    Dear SAPBUG,
    You have to create 2 message type:
    Example:
    YNEU and ZNEU if you want to determine 2 message type at 1 time.
    Then try to add it in transaction MN04 and the respective output device.
    BR,
    Ian

  • MM Message type MAHN

    Dear friends
    Does anyone knows explain how could I use the "Eletronic Follow up"  from SAP.
    Which steps should I use to configure and use message MAHN to send warning to vendor , from PO fields.
    Best regards,
    Ale

    Hi,
    Please read this link. It will explain what you need:
    http://help.sap.com/saphelp_470/helpdata/en/b7/286992ebc611d1b6400000e8a738dc/frameset.htm
    Please bear in mind that you ALWAYS have to print out your PO first. Otherwise no reminder output.
    Please make sure you have maintained your reminder days on the material master (purchase value key) or in the info record or in the PO.
    Days with minus: letters are send before the goods receive dates (-2) will send letter 2 days befor GR date in PO
    Days with plus: reminder is send (3) 3 days after the planned GR date.
    Totally three reminders can be send. After the last reminder, and still not be delivered? Send your company worst nightmare to the vendor (helped in our case!).
    Printing in batch possible.
    Manual printing ME91F (transaction code).
    Best Regards,
    Eric.

  • Output message type not triggered for few POs

    ---PRs got created manually. then PRs converted into POs through background job (me59n).
    ( 25 PRs got created manually with same vendor and pur.org combination then all PRs converted into POs through ME59N. In that 20 PRs had message type automatically but remaining POs haven't got the message type )
    Condition record exists with vendor/pur.org combination.
    and all IMG settings are correct.
    medium is 8 (special function).
    and not able to replicate the issue in quality systems.
    Please Advise.
    Thanks in advance.

    PRs will not get any message type, POs will get a message record.
    How is the situation now?
    Did  you get 20 POs only, or do you have 25 POs where just 20 have a message record?
    In the first case  convert the PR manually to a PO manually and see if you get a message record. You should not enter anything manually, it is supposed to work without entering anything manually because it was meant for auto PO. In case you have to enter anything manually, then this might be an indicator why auto PO could not work.
    if the latter case, then compare a PO with and without message record on the fields that should match with your condition record.
    Do you expect the same message type for all POs, are they all in the same purchasing organisation?
    Read and check what is mentioned in KBA 1829682 - Output type is not determined in Purchase order

  • Change message type property of message in Orchestration

    Can we change the message type property of message  in Orchestration ?
    I tried to change the message type property of message  in Orchestration(in expression shape) as follows:
    MessageName(BTS.MessageType)="20";
    But admin console showed the error that it is read only property.
    How we can change it ?
    Prakash

    No you can't change the message type context property. If you have some process which is depend on message type value, then construct a new message whose targetnamespace and rootelement matches to the value which you want to set. With something like..
    create a completely new schema with the fields/ data structure same as the one where you want to change the message type
    Set the newly created schema's target namespace and rootelement to the one which you want to change. For example if you want to change the message type values as
    http://samenamespace#sampleRootElement, then set the target namespace of the newly created schema as "http://samenamespace" and its root element
    as "sampleRootElement"
    Then construct this new message from old message using message assignment shape or transformation using map. This way the newly contricted message will have the message type value as want you want to change. This is the only way.
    Moreover you can't set the message type value as "20" as you have shown, its targetNamespace#rootelement of the schema, not any custom value. If you have any process which depends on this custom value assign this value to a custom context property
    using property schema.
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • MESSAGE TYPE DEFAULT FOR PURCHASE ORDER

    Dear All,
    I want to set default message type ZNEU for all purchase order. I try this with T-CODE MN04 AND MN05 but it is not working.
    SO HOW I MAKE MESSAGE TYPE DEFAULT FOR PURCHASE ORDER
    Regards,
    Pankaj

    Hi,
    Miantain the all the conditions records in t.code : MN04. after that check for the "Define Partner Roles for Purchase Orde" what did you mentioned for new or change as per that,
    Check you had fine tune the output (message) type in following path:
    SPROMMPurchasingMessageOutput controlMessage tyoesDefine message type for Purchase Order--Fine-Tuned Control: Purchase Order
    Select the check box coresponding to your output(message) type ZNEU to have print output for this message type .......
    Now try creating PO & u will have default message type ZNEU......
    Hope this will help you.......
    BR,
    Patil

  • IDOC Message type from XI

    Hi,
    I'm sending idoc type ORDERS05 from XI. Previously, I had set up message type ORDERS for this IDOC in the partner profile. But then I changed message type to ORDRSP, and process code ORDR for inbound idocs. I've also set message type ORDRSP for IDOC type ORDERS05 in WE82 message type - idoc type linking.
    But for some reason, the IDoc is looking for message type ORDERS and not taking message type ORDERSP, and it is erroring in SAP, when I view the status of the IDoc it says that EDI Profile ORDERS Message type was not found.
    So my question is - is this message type for an idoc type to be used passed somewhere from XI, do I have to make a change in XI side, or SAP side.

    Hi,
    I did all these changes, in the IDOC mapping in XI and also selected the option to select control record from payload in the idoc adapter. The messge in SXMB_MONI, I can see that EDI_DC40 has mestyp ORDRSP, but when I see SAP we02 IDOC transaction, it says that message type is ORDERS. Don't know why this is still happening? Any other option needs to be checked guys?
    Regards,
    Vijay
    Message was edited by: vijay srikanth

  • Output message type determination through MIGO

    hello experts,
    I am doing MIGO for goods reciept, it is creating material document and triggering output type attached to it (ZLCO).
    Same thing when i am doing through an excel sheet (this excel application is calling a Z function module thats one looks is calling Standard BAPI BAPI_GOODSMVT_CREATE), this is creating material document but not trigger output type.
    Output ZLCO is not created upon VGR thru Excel Upload.
    What part of code should i provide to my Z function module so that it also trigger the Output type.
    Thanks,
    Sumit

    PRs will not get any message type, POs will get a message record.
    How is the situation now?
    Did  you get 20 POs only, or do you have 25 POs where just 20 have a message record?
    In the first case  convert the PR manually to a PO manually and see if you get a message record. You should not enter anything manually, it is supposed to work without entering anything manually because it was meant for auto PO. In case you have to enter anything manually, then this might be an indicator why auto PO could not work.
    if the latter case, then compare a PO with and without message record on the fields that should match with your condition record.
    Do you expect the same message type for all POs, are they all in the same purchasing organisation?
    Read and check what is mentioned in KBA 1829682 - Output type is not determined in Purchase order

  • Automatic Appearing of Message type if any changes occur wrto PO

    Hi All,
    I have created  a print out Message type and assigned to some PO Doc type, if we go and see in the creation message type the new created msg type is appearing.
    My question is,
    I want this msg type need to be appear automatically once the Po is created(Ie., after if we go and see in ME22N it should appear) or if we done any changes it should come automatically.
    Can anyone help me on this.
    Pls..
    Thanks & Regards,
    Nagaraj S

    Hi,
    Check if your message type has the operation "2" (Change) on the "Fine-Tuned Control: Purchase Order" customizing.
    Custom path: Materials Management -> Purchasing -> Messages -> Output Control -> Message Types -> Define Message Types for Purchase Order. Choose "Fine-Tuned Control: Purchase Order". (mu version: ECC600)
    Alex Almeida

  • Automatic trigger of message type WE01 in VL32N transaction

    Hello,
    My requirment is to populate the message type WE01 in VL32N transaction.
    Please let me know the steps
    Regards,
    HK

    Hi,
    You have to maintain the CONDITION RECORDS for the WE01 output type
    Goto the Transaction code  NACE and click on the APPLICATION ME and click on the OUTPUT types in the MENU BAR
    select the OUTPUT type WE01 and assign the SMARTFORMS & PRINT PROGRAMS to the output
    Now assign this outpt to the OUTPUT determination procedure and
    Maintain the condition records for the OUTPUT
    Once you maintain the CONDITION RECORDS , then automatically it will be triggered to the INBOUND DELIVERY, in VL032N
    Please check them and let us know if you need any frther details
    regards,
    santosh

  • How to set error message for 541 Movement type

    Dear gurus,
                I want to know that is it possible to set error message through any configuration? My requirement is that when we create issue document using m.t 541 it will not allow me to process that document without releasing PO document.so for that i want to set error message.
    <removed by moderator>
    Message was edited by: Jürgen L

    Hi,
       The subcontracting goods issue can be done even without PO reference. If your organization is strictly following the goods issue against PO only and you want to restrict the goods issue if the PO is not released, then you may check the below option. Please note that the below option is available in standard only from EHP 4 or above.
    1. Refer the KBA: 1915825 - Transfer Posting reference to a Purchase Order in MIGO and activate the PO reference option in MIGO - Transfer posting.
    2. Restrict the use of 541 movement in MB1B - Go to OMJJ and enter movement type as 541. Now go to "allowed transactions" folder and remove MB1B. Now the user cant use 541 in MB1B.
    3. Maintain the field - Purchase order as mandatory field for the movement type 541 in OMJJ.
    4. Train the users to use MIGO - Transfer Posting - Purchase order option for goods issue with 541 movement.
    5. If the PO is not released, system wont allow to use the PO in MIGO - Transfer Postings.
    6. If the user is selecting Transfer Posting - Other, system wont check the PO and hence it will allow to post the goods issue even if PO is not released. You may take organizational measures to restrict the usage or you may check for authorization concept - Refer the note: 773003 - MIGO: No authorization object for action/reference document
       If you are below EHP 4, there is no standard functionality available for the requirement as of my knowledge. If so, you may go for development to restrict the same.
    Regards,
    AKPT

Maybe you are looking for