Message control configuration

Hi all,
I want to configure the message control so that It could send Idocs as and when some changes take place in the relevant data fields (transactional data). How do i go about it? (Steps involved in configuration)
Thanks & Regards,
Ananda

Hi,
Either you can do it NACE transaction or you can do it in the SPRO configuration. For specific to use OMFE.
SPRO->Material mgmt->Purchasing->Messages->Output control
Regards,
Ravi
Note : Please mark the helpful answers

Similar Messages

  • Message Control Configuration for V1 application

    Hi,
    We are trying to generate ORDRSP output, but we get the  error saying "Maintain outgoing EDI-connection data for partner 1000.", while trying to generate ORDRSP output through transaction VA01, and then Extras->......
    Does any know why are we getting this error?
    Thanks.
    Karma

    Go to WE20 and create the partner 1000 type KU and maintain the outbound idoc properties.
    Regards
    Shravan

  • How to do configuration to create outbound idoc using message control

    The objective is to create outbound idoc based on some selection criteria using message control approach.The interface will be triggered when there is goods receipt via MIGO transaction.............Now based on the material document number from NAST table i am going to fetch data and do further processing inside the function module i am going to create.later idocs will be created via program RSNASTED.How we do the configuration to set up this whole operation?

    Please go thru:
    1) message control
    2) http://help.sap.com/saphelp_di46c2/helpdata/EN/c8/19878343b111d1896f0000e8322d00/content.htm
    Regards
    Shital

  • Output type not proposed in Message Control when PO is created

    Hi,
    DETAILS
    I have set up the system to send a IDOC when a PO is created. I have done the following settings in the system to send the IDOC using the message control functionality in the PO creation screen.
    1). Created a new output type ZNEU which is an exact copy of NEU output type provided by the SAP system.
    2). Assigned the new output type to the output determination procedure.
    3). Enabled the new output type ZNEU for ALE distribution.
    4). Maintained the condition records in the system for the output type ZNEU such that for the P org, endor and Docmuent type combination the output shall be proposed.
    5). Maintained a partner profile( Logical System ) and assigned the output type ZNEU to this partner profile.
    6). Created a Distribution model for Sender ~ Receiver for ORDERS message type.
    PROBLEM
    When i create a PO the new output type is not getting proposed by the system. I am not sure why it is not getting porposed in the message control.
    I tried to manually enter the ZNEU output type in the system to see if the system is accepting. I am getting an error
    Partner % does not exist for partner function LS
    Any idea what i am missing? Am i missing any configuration or am i doing something wrong?
    cheers

    The output is not being proposed automatically is becuase you are missing "Condition Records" for the output type ZNEU.
    Go to NACE.
    Select EF - Purchase Order
    Select "Condition Records"
    Select ZNEU and select condition records
    Now, system will bring the combinations of access sequence. Maintain appopriate record.
    This will enable you to get the output type automatically in the purchase order.
    Regards,
    Naimesh Patel

  • Creation of Custom IDoc with Message control for sales Order

    Hi all,
    I am trying to create custom Outbound IDoc with message control.
    I wrote the code in a function module and i want to register that function module. (as in inbound registration of function module as in BD51).I am not knowing if that registration is necessary for outbound Idoc, if so in which transacition?
    Please list me the steps to create a custom IDoc for Message control.
    Thanks in advance,
    Regards,
    John.

    Hi,
    You need to use FM : MASTER_IDOC_DISTRIBUTE to create outbound idoc.fill the data in the tables EDIDC,EDIDD and generate the IDOC.
    check this link:
    Re: Master_IDoc_Distribute
    and use transaction : WEDI for IDOC configurations.
    here you will have all the transactions(step by step) to set the outbound IDOC configurations.
    Regards
    Appana

  • Is it possible to use BAPI-ALE to send an idoc using the message control?

    Hi Guys
    Is it possible to use BAPi-ALE to send an IDOC using a message control?
    I have configured the system to send an IDOC when a outbound delivery is saved in the system.
    I have done the following.
    1). I am using the std BAPI-ALE interface provided by the object type LIKP.
    2). I am using the method SAVEREPLICA for which an interface already exists in BDBG transaction.
    3). I hace created a distribution model in BD64 and added the BAPI - LIKP and SAVEREPLICA
    4). Created a partner profile ( using the generate partner profile option in the BD64 transaction )
    QUESTION:
    1). How do i associate the custom OUTPUT type created for Delivery ?
    2). I tried to associate the custom output type in the Partner profile definition under the message control tab but i am not sure which Process code to be used? Since the partner profile was generated automatically from BD64 it has an entry for SHP_OBDLV_SAVE_REPLICA as a message type in the outbound parameters. and i am unable to find a process code for this Message type in WE41. So what process code should i use in the Message control tab against the custom output type?
    3). Do i need to leave the message control tab empty without making any entry? If yes then how would the system come to know that it needs to trigger this partner profile when the custom output type is proposed by the system?
    will award points for useful answers
    Edited by: Workflow  learner on May 29, 2008 8:49 PM

    "any way"
    Applications such as ScreenRecycler, http://www.screenrecycler.com/ScreenRecycler.html, can do it.

  • Message "Wrong partner type LS" in message control

    Hi All,
    I am trying to send PO's out to a middleware system. I have configured the middleware system as a LS (logical system) done all the config required for Message control.
    But when I enter Output type = NEU and Medium = A (ALE) and Partner Function = LS and partner name and save the PO, I get the error "Wrong Partner type LS" in the processing log for that message. The details description says "The message record of the message control contains a partner role with a partner type LS that cannot be used here. Only the 'KU' and 'LI' partner types are allowed.". But i need to send it to partner type LS.
    Am I missing anything. Please Advise.
    Thanks in advance

    Hi!
    'By default' purchase orders can be send to vendors or plants - the two parties in the document. This is linked to the two different partner types KU and LI. Only partners of this type of a purchase order can be used to send data.
    Check, if you can create a partner definition (WE20) for KU (hopefully you have less plants then vendors).
    You also need a partner determination for the document - only out of this partners automatically a message output can be assigned.
    Regards,
    Christian

  • ALE with Message Control

    Hi Guys,
    I have a small problem. I wish to trigger an IDoc to my Vendor as soon as a Purchase Order is created in my system. I am using Message Control for it.
    All the configuration for proposing the output type have been done and I am getting the desired output type shown in the "Messages" with correct recepient . But when the PO is saved and the Idoc is generated I find that the IDoc is sent to some other Logical System and not to the vendor.
    I have created the partner profile for the Vendor with the outbound parameters.
    Can anybody tell me what am I missing or could be wrong in my settings?
    Regards,
    Prakash Pandey

    Do you have a specific requirement?
    For  example, purchase order message control parameters will look like this,
    Message type - Orders
    application - EF
    Message type - NEU
    Process code ME10
    For purchase order change,
    Message type - ORDCHG
    application - EF
    Message type - NEU
    Process code ME11
    Change flag set

  • Is it possible to use the message control in R/3 to trigger a Proxy?

    Is it possible to use the message control in R/3 to trigger a Proxy? The message control mechanism has some advantages that I want to use E.g. repeat messages with RSNAST00, configuration instead of coding etc.. Does anyone uses SD Invoice message control mechanisms together with XI Proxies?
    Best regards,
    Matthias

    Hi,
    >>>configuration instead of coding etc
    currenly it is not possible to achive it without any coding
    >>>repeat messages with RSNAST00
    RSNAST00 is not used to repeat messages (idocs) but to send them
    try using standard IDOC in your sd invoice scenario
    if you don't want to do any coding
    Regards,
    michal

  • Ale/Idocs ..... what is the role of  message control

    Hi Guy s..
    Can Any one.. tell me..  Importance of message  control , Stand alone and  change pointer s in Ale  Idoc''' and where to use...

    Hi,
    Message Control:
    With Message Control is documents are output based on
    certain conditions. In ALE scenarios this is basically used for transfer transaction data (fulfilling configuration settings defined in message control) from one system to another system.
    Example: If you want to send purchase order IDocs from customer to vendor system using ALE. When saving of purchase order the IDocs should be triggered. Further the IDocs should only be sent when the purchasing document fulfils certain conditions - purchase document of a certain document type only needs to be sent. By output control we can configure the conditions and the timing (when the document should be triggered) and using ALE (as interfacing technology) we can send IDocs (containing application data fulfilling conditions) from one system to another system.
    For More Info on Message Control,
    /people/gajendra.bhakuni/blog/2007/03/13/message-control-output-control-for-ale
    Change Pointers:
    Change pointers are the mechanism through which you can send data to another SAP system or external system if there is a change happening to specific fields of master data.
    Change Pointer (Master Data Distribution)
    Purpose
    If you want to distribute master data changes with the SMD tool (Shared Master Data), changes to the master data objects are flagged for distribution by change pointers ( ® Master Data Distribution).
    The SMD tool is connected to the change document interface. If the master data changes are to be distributed, the application writes a change document. The contents of this are passed to the SMD tool. The tool writes change pointers, reads the application data and creates the master IDoc.
    The master IDoc is then passed to the ALE layer, which sends it to all interested systems.
    The change pointer tables (BDCP und BDCPS) should be as small as possible. Use as few change pointers as possible and delete change pointers which you no longer need.
    do the following steps for Change pointers ::
    1) Tcode BD61---> check the change pointers activated check box
    save and goback.
    2) Tcode BD50---> check the MATMAS check box save and comeback.
    3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
    4) Tcode BD52---> give message type : matmas press ok button.select all what ever you want and delete remaining fields.
    save & come back.
    5) 5) go to Tcode MM02 select one material and try to change the description and save it
    it will effects the target systems material desciption will also changes
    6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
    give Message type : MATMAS and Executte
    go through this link which ll give you detail about the change pointer
    http://www.angeli.biz/www5/cookbooks/workflow/workflow_30/docu.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
    http://help.sap.com/saphelp_470/helpdata/en/dc/eb683c00e8a646e10000000a11402f/frameset.htm
    Regards,
    Padmam.

  • Message control attributes for EDI 846, 947

    Hi experts,
        I need to configure partner profile for these EDI transactions: EDI 846 and EDI 947. What should be entered in these fields of message control tab:
    Application, Process code, Message type? Also what are the IDOC types for these?
    Thanks.
    Regards,
    Abhinav

    Go to WE20 and create the partner 1000 type KU and maintain the outbound idoc properties.
    Regards
    Shravan

  • Message control for outline contract BLAORD.BLAORD03

    Hi There,
    I am configuring outline contract idoc BLAORD.BLAORD03, I want to know what are the message control parameters for that?
    Application: -
    Message Type: -
    Process Code: -
    Thanks,
    Nishant

    Hi Nishant,
      Check the Tcode WE82 for Mesage type and Basic type of ur idoc,
      Check  the Tcode WE40 for Inbound process code
      check the Tcode WE41 for outbound process code.
    Messagetype is                 BLAORD
    InboundProcess code is      BLAO
    Function module name is     IDOC_INPUT_BLAORD
    for application try with          WT
    Thanks,
    Ram.

  • Outbound message control for sales order SISCSO.

    Hi...
    I am trying to generate IDoc for Sales order using message control. The IDoc of type SISCSO is getting generated as per the requirement.
    I want to calculate certain things before generating IDocs. I have done the following configurations:
    1. A function module 'ZIDOC_OUTPUT_SALES_ORD' is created with interface same as 'IDOC_OUTPUT_ORDRSP'. (Where i am planning to write a code)
    2. WE57 where Function module is assigned to SISCSO as outbound FM.
    No BD51 is done as it is only for inbound process.
    3. New process code ZSO is created through WE41, which is made message independent and FM created in step 1 is assigned to it.
    4. In WE20 , this process code is attached to V1 type of application under message control.
    Still, my FM is not getting called... I have checked it by applying Break point as well as raising exception in the FM. But still it's not working..
    Where am i going wrong??
    Can anybody suggest solution??
    Thanks,
    Audy.

    Hi,
    You need to use FM : MASTER_IDOC_DISTRIBUTE to create outbound idoc.fill the data in the tables EDIDC,EDIDD and generate the IDOC.
    check this link:
    Re: Master_IDoc_Distribute
    and use transaction : WEDI for IDOC configurations.
    here you will have all the transactions(step by step) to set the outbound IDOC configurations.
    Regards
    Appana

  • Change Investment Management message Control

    I am setting up Investment Management, and I would like to know if its possible to change message BQ151 to a warning.  this message stops you allocating more to an order than is available in the total budget.
    The reason for doing this, is that we want the option to have unbudgeted orders, so it is possible that an area may exceed its budget.
    I cannot find any message control options in Investment management, or where the change options are for application area BQ.
    Does anybody know where these message are configurable?
    Thanks
    Graham

    Hi,
    Technically, it's possible through OBMSG transaction. Though, you should consider the consequences...
    Regards,
    Eli

  • What is message control?

    Hi all,
    What is message control? esp in Idocs..... Any docs links on Message control?
    Thanks,
    Charles.

    hi,
    Message control
    Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
    In outbound programs(function module) that use message control the key of the
    application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
    message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
    The parameteers passed to the function module are
    IMPORTING PARAMETERS
    OBJECT LIKE NAST
    It contains documents key.
    CONTROL_RECORD_IN LIKE EDIDC
    It contains the partailly filled control record
    EXPORETING PARAMETER
    OBJECT_TYPE
    CONTROL_RECORD_OUT LIKE EDIDC
    TABLES
    INT_EDID LIKE EDIDD
    The internal table used to fill the data records in the same order as they exists in
    the IDOC.
    The important parameters that should be filled in the custom function module are
    CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
    ===========================================
    Message control and output type. In R/3, message control is a mechanism by which documents are output based on certain selection criteria, requirements, and sequences. Message control determines the type of document, its timing, number, and medium (print, fax, ALE, or EDI.). Outbound messages in SD (Sales and Distribution) and MM (Materials Management, Purchasing) are created and processed by message control records. The output records are stored in the NAST table.
    Message control uses the condition technique. The conditions for creating an output message are stored in condition tables that have selection fields picked from a catalog of application fields/tables. To determine if an application document qualifies for output, search strategies are used through access sequences, output procedures, and requirements. Once a message qualifies for output, message control modules use the parameters set in the condition type or output type to determine the timing of transmission and the medium of the message. The output type also specifies the program or module to be invoked to create the output.
    Message/output determinations are concepts applicable not only to EDI and ALE, but also to other output mediums.
    ~~Guduri

Maybe you are looking for

  • How to save plain text attachments

    I often get email with plain text attachments (e.g., source code). Mail tries to be smart and displays the attachments in the body of the mail. But I wold like to save them as usual. I can't even control-click on them Does anyone have an idea what I

  • How do i import camera raw files to photoshop elements 9 when it is saying it doesnt recognise files from card.

    how do i import raw files onto elements 9 when there is a message saying it doesnt recognise files

  • TS1208 question: conflicting dhcp range

    Hi out there Am after a basic language easy to follow instrution to resolve the above I have a TC as my main wifi router, with an extreme and express as part of the network.  I have the above message on my TC, and I have absolutely no idea how to res

  • Admin Approval

    1. How to assign a proxy group for AD approval process? Right now the access policy is set to 'with approval' and can be approved only by system admin and not the Ad admin group. Assuming the above will work in future.... 2. How to send an email noti

  • Importing text from Word file while keeping formatting

    I have text set up to convert to Goudy Oldstyle. When I try to import formatted text from a Word file, the italics don't translate to Goudy Oldstyle italic. It becomes Goudy Italic and then reads as a conflict. How would I be able to reformat just th