Sales Message Control

Dear all,
i wanna know how can i add message control for sales in system messages "OVAH" or should i do it in another place??
Thanks

Dear Mostafa,
Transaction SE91 is used to create message-class. You may define message and message number in the class.
For Message control, relevant transactions are:
WE81 - Create Logical Message Type
WE82 - Assign Message type for Idocs
WE20 - Partner Profile
WE21 - Port Definition
WE30 - Develop Idoc type
WE31 - Development Idoc Segment
BD21 - Generate Idocs from Change Pointers
BD50 - Activate Change Pointers for Message type
BD64 - Maintanence of Distribution Model (Determine the Distribution of Idocs)
NACE - Condition for Output Control
Message type: ORDERS
Idoc type: ORDERS05
Also, refer [SAP Help - Message Control|http://help.sap.com/saphelp_46c/helpdata/en/c8/19878343b111d1896f0000e8322d00/frameset.htm]
Best Regards,
Amit
Note: A few relevant threads for reference:
message control
message control

Similar Messages

  • How to send IDoc(Sales Order Confirmation) without Message control

    Hi,
    I need to send Sales Order confirmation,Delivery and Invoice through ALE (IDoc's). I am asked not to use MESSAGE CONTROL or CUSTOM IDoc to send confimation.
    I dont need to send a instant confirmation but i can do it at a specified time intervals.
    Do we have any other possiblity other than the both?
    Can you please give the steps to do, if possible?
    Thank you in advance,
    Gangolu.

    Hi
    This link may be useful
    Re: Re-open EDI - ORDCHG for outbound sales order

  • 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

  • Message Control in sales order

    Could some one help me to change the message control from Info to Error for Application area V1 (sales order)
    Thanks

    Hi
    This has to be done thro development only
    Only some messages of message class V4 can be done in t code OVAH
    Go to SE91
    1.Input the message class V1
    2..Input the message no say  061 in no and execute
    3.select the message no and click on where used list (ctrlshiftF3)
    4.select the box programming and deselect all others
    5. Then a list of programs where this error message is used will appear
    6.Double click description on the right side of your screen
    7.Here you can see the codings written for this message 061 which can be changed to warning to error
    Note
    The best way to do it is with ABAPer only
    Not recommended to change the standard settings
    Regards
    Raja

  • 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

  • EDI without message control

    I am getting  Invoice list in EDI form. I need to get that data into R/3
    with out using Message Control. How to do that ?

    Hi,
      Refer
    Re: Re-open EDI - ORDCHG for outbound sales order
    Regards

  • Help needed in Message Control - very urgent

    Hi Experts,
    I have one requirement where in the customer wants to stop creation of IDOC which posts Invoice using message control and message control status should be changed to RED color and also the message should be populated in the processing log saying 'IDOC processing failed, External customer numbers not maintained'.
    Could you please let me know any user exits or customer exits available for this purpose.
    I have searched all the possibilities.
    I have chanked the program RSNAST00 which picks up the data from table NAST and looks into table TNAPR to get the processing porgram for th selected output and also this program checks the partner profile and gets the process code which creates an inoice IDOC. I searched for user exits and customer exits to popolate the required messages and stop IDOC creation.
    I am an ABAPER and i know i need to write code to do validation, but could not find the exact place where to write? I any ABAPERS looking at this post, please reply me.
    Can anyone please advise me how to go about solving this issue?
    Thanks
    Srinath

    Hi,
       I am sending the requirement.
      Please send me the solution.
    Requirements:
    1.     EDI Invoice requires populating bottle UPC number not case UPC in IDOC and also populates customer PO number when invoice billing type is a credit.  These changes need to be reflected on EDI invoice (Idoc INVOIC02).
    Investigation:
    Requirement 1. EDI invoices are populating segment E1EDP19 qualifier 003 based on the unit of measure in the line item.  If shipment unit is CSE then it populates CSE upc, if shipment unit is EA then it populates Bottle UPC. 
    a.     It was found that the UPC populated on the EDI invoice was being read from material master – Additional data tab.  (Field SMEINH-EAN11).  For the EDI invoice, the customers expect the bottle UPC on this column.
    Requirement 2.  Need to always populate Segment E1EDK02 Qualifier 001 (customer PO) on the INVOIC02 idoc.  Standard SAP populates this information only when the billing type is F2 (regular invoice) and if the customer PO was entered in the Sales Order.
                                a) Premier requires this information to be populated in the idoc if the billing type is G2, RE, L2 also.
    Solution:
    Requirement 1.
           IDOC_OUTPUT_INVOIC function module needs to be changed to always populate the UPC number for the bottle UPC in segment E1EDP19 qualifier 003, field IDTNR.  This number is found on the material master – Basic data 1 view.  Field name is MARA-EAN11.   Please see screenshot of where in the material master to find the bottle UPC. 
         a. This change applies to all billing types (F2, G2, L2, RE etc).
           Requirement 2.
                 Change IDOC_OUTPUT_INVOIC function module to always populate customer PO information in Segment E1EDK02 qualifier 001, field BELNR.
    If billing type is equal to G2, L2, RE and VBRK-XBLNR not equal blanks then make BELNR = VBRK-XBLNR.
    Segment:  E1EDK02
                                  Field:  QUAL = 001
                                  Field:  BELNR = VBRK-XBLNR
    Please help me how to move a step ahead.
    Waiting for your immediate response.
    Thanks,
    Chandra.

  • Posting EDI Order confirmation without message control

    Hi,
    I would like to post a EDI sales order confirmation without message control through z program.
    Please let me know how to do this???
    thanks in advance
    Mukund

    Hi
    This link may be useful
    Re: Re-open EDI - ORDCHG for outbound sales order

  • Message control vs with out message control

    tell me the differenece between message control and without message control.

    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.

  • Regarding Message control

    hai guru's i am an abaper and i want to know what i s message control and how is it actually implemented i mean what is the output type , condition tables , condtion records and acess sequence and all , atleast basic functionality
    thanx in advance
    regards
    afzal

    I can explain you in brief.
    Output Type is used for outputting of documents in SAP.
    Output type is what is maintained in PO under messages tab. E.g. NEU is the standard Output type for a PO. When we define an output type in SPRO, we also assign a Progrom and a Layout to this Output type also called Message Type.
    ABAPer design the program and the Layout and Functional consultants assign these to the appropriate Output Type.
    Output Type can be for PO, RFQ, Contracts, Scheduling Agreements. Each can be defined in SPRO.
    Condition Tables are table which contain Condition records. Condition Tables, Condition Records and access sequence are used for price determination in Purchainng / Sales documents.
    you define say 2 condition tables with 1-2 fields and then define an access sequence and assign the above defined condition tables in order 1 and 2. then system will first search for the first set of condition table if it finds a condition record then it stops the search otherwise it serches for 2nd condition tabel for condition record. This is the purpose of access sequence.
    hope I have explained somewhat.

  • 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

  • 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

  • Error in setting up message control in WE21...

    Hello Experts,
    I am currently setting up the partner profiles of my new IDoc in
    transaction WE21(Partner profiles). Under the message control tab, I
    chose 'EF' under 'Application', 'NEU' under "Message type' and entered
    my process code under the 'Process code' column. But an error is bening generated
    saying that the 'Parameters for message control already used'.
    So how do I create a unique message type for my process code/IDoc? My Idoc is for
    purchase orders and will be trigerred upon release of PO.
    Hope you can help me guys. Thank you and take care!

    Message type NEU is already being used in the standard system. You have to create a message type of your own (use transaction NACE to do so).
    Regards,
    John.

  • PO outbound message control - Condition record / PO IDOC outbound user exit

    Guys,
    I have a system with PO outbound message control sending PO idocs to a unique plant that is set up as a customer in the partner profile. I am using a custom message type and RSEOUT00 to send my idocs with custom message type to this plant. This interface works fine. Now my requirement has changed. I need to send PO's to varying plants (depending on the plant in PO item- all items on my POs belong to same plant).
    I noticed that i cannot create condition tables with PO type and Plant combination. (SAP Note 457497 .Q-34).
    So I have decided to populate all my PO idocs with a generic receiving partner number '9999' and planning to change this somewhere in a user exit. I found an user exit which looks helpful.
    EXIT_SAPLEINM_001 .  FM
    MM06E001 - Enhancement.
    But somehow this exit is not triggered in during PO creation ME21N or change Me22N/Me22.
    Is this because I am using a custom message type instead of standard message type ? (I still use the process codes Me10/Me11). Would this matter ? When should this user exit trigger (during creation of idocs in status 30 or when i run RSEOUT00 to sweep these idocs in status 30 to status 03) ? Any tips will be useful.
    THanks.
    Edited by: Shareen Hegde on Jul 21, 2008 10:13 PM

    I found a OSS note -Note 457497 (Q&A # 34), which talks about the same . This was my assumption too. I was just confused because I saw plant(WERKS) in the field catalag of the access sequence.
    I don't know what header field I can use to map the plant (I agree its a good idea to do this). But I have decided to do it another way. I will change the receiving partner on the control record depending on the plant in an user exit
    -  EXIT_SAPLEINM_001.
    Thanks for your answer , Mahesh.

  • Need create a new control key, which message control is "error mode", then PR or PO

    Hi All,
    Can please help me I got an issue in QM ,
    Issue Description :-  Current QM control key for supplier validation date is “0001”, the message mode is only warning. PR or PO still can be created forcibly. Need create a new control key, which message control is “error mode”, then PR or PO cannot be created successfully.
    I thing should add some additional logic using BADI or USER-EXIT.
    can please help me how to find BADI or USER-EXIT if you know the appropriate BADI please let me know.
    Regards,
    Nani

    Hi,
    I tried that way I entered message control as Defect even purchase requisition is created how can I restricted purchase request ion.
    Regards,
    Nani.   

Maybe you are looking for