No manual triggering of Message Type

Hi Gurus,
What are the settings required if i want the message type can never be triggered manually.
Please what can i do to to achieve this.
Points will be rewarded.
Thanks
Rohit

Hi
Check out these notes
[208271|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=208271]
[172403|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=172403]
[189661|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=189661]
[798476|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=798476]
i dont think.. its gonna solve the issue... but.. check out , if u find it helpful...
- Pithan
Edited by: Pithan Pithan on Apr 28, 2009 3:35 PM

Similar Messages

  • Updates rules activation triggers dump message type X

    Hi,
    In an existing update rule, I am trying to add a field (key figure=> characteristic (source)
    after I activated the update rules a shot dump is triggered
    "Message type X"
    message class RSAA
    Number 108
    trigger location
    %_T005N1
    Module Name Instantiate
    called function :
    RSAU_GET_CUBE_TIME
    I have already done some consistency test about the infocube in RSRV, but don't dind a clue for the moment.
    any help would be grateful
    John

    Hi
    Try to run standard program RSAU_UPDR_REACTIVATE_ALL.
    Thanks
    lokeshM

  • Output message type triggering for all

    Hi,
    I want the output messages to be triggered for particular Vendor and doc type with ALE config.
    Now the config is such tht whenever the PO is created for doc type, the output type gets triggered for ALE partner .
    So need guidance.
    Thanks

    hi,
    Please check whether the access sequence attached to your Condition type has a condition table with Document type and vendor field, if not then you can add one or create a new Access sequence and attach it to you condition type.
    Next you maintain the Condition Records for the doc type and vendor combination, and the system shall trigger the message type automatically.

  • Message type EDI is not triggering for outbound deliveries

    Hello,
    When ever the shipment status is completed message type EDI is triggered for the outbound delivery.
    However, in spite of the shipment completion the DESADV EDI message is not created in the outbound delivery.
    So, i request you to help me in this issue.
    Regards,
    Anil

    Hi,
    1st please check the partner porfile for whom it is sent ( Eg -- Ship to party) using T.code WE20 in partner type ku, look for the customer for whom it is sent.
    Check for the message type wheter it is add in outbound parameteres.
    Finally check the varaint of shipment whether the required output is maintained in the shipment varaint and also make sure that condition record is maintained for the output.
    You find some solution with this.
    Regards
    vk

  • Message type is not triggered in SAP when PO copied from eSHOP

    Hi,
    We are creating PO in eShop and sending to SAP.
    POs are correctly getting copied from eShop to SAP.No issues.
    We have set condition record for Message type to trigger in SAP for those POs as EDI Medium.
    No message is getting triggering in SAP.
    Whether it is standard one ? or any further enhancement required ? If so please suggest the BAPI.
    Thanks

    Hi Dhina
    What is the application eSHOP?.
    for example
    In SAP SRM - Technical scenario - Extended Classic.
    Purchase orders were created in SRM -EBP and replica of Purchase Orders were replicated to ECC system. In the above scenario messages are created in SRM not ECC.
    The PO messages are out puted to vendor from SRM itself.
    So please clarify what is meant by eShop. so others can help you further  ..
    Muthu

  • 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

  • IDOC message type LOIPLO not triggering

    Hi Friends
    Our client want to send firmed planned orders to External system through outbound IDOC LOIPLO
    So we are using MF50 to firm the planned orders.
    The idoc message type LOIPLO is not triggering.
    How to trigger IDOC message type   LOIPLO . What are the settings we have to do.
    Regards,
    Srihari.M

    dear friend,
    Message Type :  LOIPLO
    Basic Type :        LOIPLO01
    You need not create any custom IDOC type as we are having a standard IDOC type available within SAP, but you need to write a custom function module to read the data from the IDOC segments and then call the below BAPI to post the Planned Order.
    Check the input parameters of BAPI and gothrough the documentation of the Basic Type in WE60 transactions, whether all the necessary input parameters of the BAPI are covered in the standard IDOC type, if not then we need to customize the standard basic type to meet the requirements.
    Bapi which needs to be used is BAPI_PLANNEDORDER_CREATE
    good luck!

  • Issue with Message Type Triggering during Inbound Delivery Creation

    Hi Experts,
    Hi Experts, 
    Currently we are facing issue with message type triggering during inbound delivery creation:
    In NACE transaction for Inbound delivery we have 3 custom output types:
    Pricing Procedure Used is standard one -> E10001
    Z140  Inbound Delivery Create  (This should get triggered when IB delivery is created)
    Z141  Inbound Delivery Change (This should get triggered when IB Delivery is changed)
    Z142  Inbound Delivery Delete(This should get triggered when IB Delivery is deleted).
    At present if i check delivery in  VL33 -> Extras -> Delivery Output
    Both  Z140 and Z141 are being triggered during IB delivery creation. While it should be only Z140.
    Could you please suggest that are we missing any configuration in SPRO or we need to create any custom routine (requirement) to handle this?
    Thanks

    Hi,
    There is no fine-tuned control for inbound delivery messages as for Purchase order. Hence I guess to meet your above requirement, you have to go for a custom solution similar to the PO fine tune control settings.
    Thanks,

  • Same message type and two different IDOCS need to be triggered

    Hi,
    I have two idocs with same message type,the partner profile is same.
    Please tell if there is any way to handle this situation without changing the message type.
    Please do the needful.
    Thanks,
    Nivedita

    Hi
    We can have same message type for different idoc types.
    ex:MATMAS.MATMAS01
        MATMAS.MATMAS02
        MATMAS.MATMAS03
    In the above example MATMAS is the same message type for different idoc types.
    Thanks

  • Message type :FIDCC2/ IDOCFIDCCP02 - Triggering outbound IDOC

    I have to send the FI accounting document of certain customer groups to the third party system .
    Can anyone pls let me know how to trigger the outbound IDOC for the message type FIDCC2 after the FI document is created.
    I have configured BD64 but can not find which program to trigger to generate the outbound IDOC with the FI data.
    Thanks,
    Prashanth

    Hi Anji,
    Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
    But I have to send Outbound Idoc for a Schedule Agreement.
    Whether the same  Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
    Please Advice.
    Regards,
    Anbalagan

  • Error in ALE service 29 Could not determine recipients for message type MAT

    Hi Experts,
    While transferring the material using ALE am getting  error 29 ie   'Error in ALE service'  and message is 'Could not determine recipients for message type MATFET'.
    Also i ve recieved the materials with the proper status al the end am getting the above error.
    Kindly help me out.
    Thanks in advance.

    Hi ,
    Status 29 means " partner profile not found " . Please check if the recieving partner is configured properly  in WE20 in sender system.
    Also make sure that the Port and RFC definations are also completed. If the IDoc is manually triggered then please make sure that control record parameters of the idoc are properly filled - if we miss the details ( like wrong port given , wrong basic type for message type - or extended message type ) then also the idoc will fail in status 29 even though the partner profile is properly configured .
    Since your idoc is getting generated i think no issues with BD64 since already interested recipeints were populated in control record of idoc.
    Regards
    Vikas Chaudhary

  • Incorrect message type in IDOC for Purchase order change

    Hi Gurus.
    Please advise on below.
    We have several purchase orders that are configured to trigger IDOC upon change. But accidentally, someone has deactiveted the automatic proposal of EDI message type for these Purchase orders which resulted to not transmitting purchase order change documents automatically.
    As a workaround, we have proposed to create EDI message manually during Purchase order change. But upon checking in tcode WE09, message type is ORDERS which is PO create instead if ORDCHG for purchase order change.
    Please kindly advice on why it is behaving like this for purchase orders with EDI message previously deactivated.
    Thanks in advance.
    Acel.
    To simulate.
    Create PO. go to messages, select EDI message then deactivate permanently. Save PO. Release PO if needed. Change PO. go to messages, EDI is not automatically proposed. create EDI message mamanually. Save PO. Release PO id needed. check tcode WE09, for PO create, no IDOC since it was deactivated permanently. For PO change, IDOC was triggered but with incorrect message type ORDERS instead of ORDCHG.

    Hi Acel,
    You will need to check the settings in transaction WE20 - You will be using a Partner Profile to determine the outbound message, either for each vendor or a generic one.
    on the outbound parameters, you will need to ensure that ORDCHG is set up as a message type. If not, add it, ensuring that you use the message ORDCHG, the basic type (or extension) that you are using, usually ORDERS05 and make sure that in message control, you have process code ME02 set up. This should enable the correct message type to be determined.
    Regards,
    Rob

  • 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

  • Message type MBGMCR: posting of GR for a text po

    Hi
    Goods issues are posted by using this message type MBGMCR in R/3 system. Idocs are coming from SRM system.
    We are getting an error message for an idoc of this message type MBGMCR : "No stock posting possible for this material, The material belongs to a material type whose stocks are not managed on a quantity basis".
    I checked the data segment & found that this is a text PO (PO without material reference).
    My question is that can we post GR of a text PO by using this message type MBGMCR.
    Regards
    sapmm

    have you tried posting it manually with MIGO, just for testing purposes?
    MIGO or MB11 usually allow to post a goods receipt even for text items, with some preconditions, like GR indicator is active.
    Usually, when  the receipt is based on the PO, such message should not come, because a text PO has an account assignment K, which means the costs are posted to cost center and no stock is created.
    And IDocs for movements do in general the same as a manual posting, using the same program routines for posting.
    This M7097 is usually coming if you have no account assignment in the PO, which means you want post to stock, but stock management is not active for the material type.

  • Message interface with two types of message types

    Hi experts,
    I am having problem that a proxy cannot be generated because  of the (mixed) types of the message types that the interface is using.
    The first message type is defined in the repository and another is defined as an external definition, imported in from an outside source.
    Here is the SAP message I received when I tried to generate the proxy for this interface.
    +++++++++++++++++++++++++++++++++++++++++++++
    Interface uses external and internal message definitions
    Message no. SPRX122
    Diagnosis
    In a message interface you can use messages from different sources:
    1. Message types and fault message types edited in the Integration Repository
    2. Messages imported into the Integration Repository (external definitions, RFC, IDoc)
    In the current message interface, message types from different sources have been used.
    Since messages from these different sources must be handled differently during proxy generation, such a mixture of messages within a message interface is not possible.
    System Response
    The interface cannot be generated.
    Procedure
    Change the interface definition accordingly in the Integration Repository.
    ++++++++++++++++++++++++++++++++++++++++++
    The imported xsd is quite large and also contain many large includes. I don't have the option of creating the message type manually.
    Any suggestions?
    Thank you,
    -michelle

    Hi all,
    I tried several things and the problem is still not resolved. This is what I learned.
    First of all, I believed the SAP message about mixing of internal and external message is misleading or even wrong. I tried with both message types being external but I still get the same message that the interface has one internal and the other external message type.
    Secondly, since Arvind suggested that I might have used an xml element that is not currently supported by ABAP proxy, I then change to another definition with the most simplest elements. I then attached this other definition to the interface and tried generating the proxy again. I still get the same system message that I am using mixing of message types in one interface.
    My conclusion is XI still is not capable of generating ABAP proxy from external definition.
    Does anyone have any comments/suggestion/experience on this issue?
    Best regards,
    -michelle

Maybe you are looking for