Automatic IDOC  generation !

How to automate an idoc generation when the credit memo is created !
Can any one tell me the approach  and the steps !

Hi,
You dont need to write a code in userexit, just check this IDOC type : GSVERF01.(TCODE: WE60 or WE30)
Thru this you can create an IDOC for Credit memo.
Thru message control option we can achieve that.
Read this.. it will help u.
Message Control
The objective of Message Control is the exchange of information between various partners and the launching of subsequent processing that is partner-independent. Message Control provides interfaces to make this possible.
You can use the Message Control interfaces to describe various data combinations along with the required processing. If one of these data combinations is found to be applicable during the processing of an application object, the appropriate processing is started (synchronously or asynchronously).
Message Control is a "service program" for other applications. It is initiated via ABAP function modules. Information about which programs carry out the subsequent processing is managed in tables . The conditions determining when programs are called are often very complex and also depend on the individual customer situation. Message Control offers the flexibility needed to represent these various situations .
Purpose
The output or follow up processing of partner-dependent messages is automated via Message Control. The application then calls the Message Control via the specified interfaces.
You can use these interfaces to describe various data combinations along with the required processing. If one of these data combinations appears during processing, the appropriate processing is started (synchronously or asynchronously). You can define processing with several different methods, for example as a workflow, print output or as an IDoc dispatch for EDI.
Implementation considerations
SD and MM applications always use Message Control for message output. You carry out Customizing of the Message Control in the application’s Customizing. The Message Control is also sometimes described here as "output control".
Integration
Message Control is a "service program" for other applications. It is initiated via ABAP function modules. An application that uses Message Control must
Call the Message Control
Transfer files which should be compared with the combinations defined in Customizing.
Provide a processed program, that is called from the Message Control, if the transferred data corresponds with the combinations defined in Customizing
Features
The condition technique in the R/3 System is used to formulate the data combinations required. If the current application data corresponds to the conditions defined in Customizing, message determination was successful and created a message default. If the application supports it, the proposal can be changed (processed).
As a result the message is processed immediately or at a defined time. The processing status of the message is stored in a status record. If the application supports it, a processing log is written as well.
Message Control scenarios:
1. The credit limit has been exceeded in a sales order, whereupon the block indicator is assigned. The Message Control should respond to the block indicator by printing out this customer’s account history.
2. A document is released and receives a corresponding status in its data record. The Message Control should thereupon issue a release message.
There are also applications which can "switch off" message determination and directly generate the message default.
Structure
Condition Components and Condition Records
The individual objects of the Message Control which are relevant in the message determination process and can be configured in Customizing or the application transaction are explained.
Message determination
This section describes how the condition component hierarchy is evaluated and how the condition tables are accessed. Different scenarios, which can be realized by special strategies when Customizing the condition component, are used as examples.
Message Default and Message Editing
The result of message determination is a message default that can be edited manually in the application, if this function is available in the application. If not, any messages found are forwarded directly for automatic processing.
Message processing
This explains how the message found can be processed.
Regards.

Similar Messages

  • F110 Idoc generation

    hi Folks,
    i want to generate an idoc PEXR2002 using transaction f110 ( automatic payment program)
    Does anybody have any idea on how to do it. your inputs are valuable.
    Regards,
    Padma

    hi Madhu,
    thanx for your input. I checked all the settings. they are in place.
    In the additional log I am getting following entries:
    06-06-2008 12:36:51              payments by EDI / IDoc generation
    06-06-2008 12:36:51 IDOcs were generated for the following entries
    06-06-2008 12:36:51   Company code 3001     House bank AMX  Payment method W
    06-06-2008 12:36:51
    06-06-2008 12:36:51 End of log
    06-06-2008 12:36:52 Step 002 started (program SAPFPAYM_SCHEDULE, variant &0000000000019, user ID SACHIN)
    06-06-2008 12:36:52 Step 003 started (program RFFOEDI1, variant &0000000000012, user ID SACHIN)
    06-06-2008 12:36:52 Program RFFOEDI1: No records selected
    06-06-2008 12:36:52 Job finished
    Regards,
    Padma

  • IDOC generation at time to transfer order creation.

    What are the config steps involved for idoc generation at the time of transfer order creation?
    please advise.
    Edited by: avi on Dec 25, 2008 5:31 AM

    Hello,
    TO creation with respect to Picking perspective:
    Lean WM --> output type WMTA can be used to create TO automatically can be created (you can go to NACE transaction and check the settings of WMTA)
    From MM WM perspective i think it is PUTAWAY concept, if Purchase order -->Inbound delivery will be created with ref. to inbound delivery TO (putaway) can be created.
    Link for IDoc maintenance:
    IMG>LE>WM>Interfaces>external systems-->configure wm
    link for Automatic TO creation:
    IMG>LE>WM>Interfaces>inventory management-->Activate Automatic TO creation
    Mahesh
    Edited by: Mahesh on Jan 2, 2009 11:19 PM

  • Reg: Idoc  generation

    Hi All,
    AS per my understanding for SPEC2K idoc generation, SAP generates two IDOCS. one of standard SAP message type and another is of SPEC2K type .
    <b>My requirement</b> : if the customer requested items are not available then both the SAP message IDOC and SPEC2K idocs should be generated.
    If the customer requested items are available then only SAP message type idoc should be triggered and <b>SPEC2K idoc should not be triggered</b>.
    Is there any settings by which I can achive this.
    Thanks in Advance.
    Vijay.

    Go through the following Steps
    Try with the follwoing steps
    Sending System(Outbound ALE Process)
    Tcode SALE „³ for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ¡V Create Model View
    Tcode BD82 ¡V Generate partner Profiles & Create Ports
    Tcode BD64 ¡V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE „³ for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ¡V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ¡V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 ¡V Send Material Data
    Tcode WE05 ¡V Idoc List for watching any Errors
    1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    1) System Name : ERP000
    Description : Sending System
    2) System Name : ERP800
    Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    Client : ERP 000
    City :
    Logical System
    Currency
    Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    3)
    Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    5) Goto Tcode BD64
    seelct the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    6)goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    7)goto Tcode : BD11 for Material Receiving
    Material : mat_001
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Thanks & regards
    Sreenivas
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC
    Thanks & Regards
    Abhay.
    rewards point

  • Outbound IDOC generation

    Hi Gurus,
                         There is a requirement for a customer to develop a custom program i.e.  IDOC generation for the Manual payments (F-53 ) raised (As similar to the F110 Automatic payments ).... We are calling MASTER_IDOC_DISTRIBUTION function Module from which IDOC is getting generated but the data which needs to be distubted to XML file through Port configuration is not happening .
    with the Automatic payments with same port configuration this is working fine.... so is that anythign we need to do in the custom program ...
    Thanks for your help in advance
    Thanks & Regards,
    Ramamurthy

    Hi Ramamurthy,
    I'm assuming that the IDoc gets generated, i.e. you can see it in WE02. If not then you're probably missing the entry in the distribution model (BD64), so the function module creates a master IDoc, but no communication IDocs.
    If you see the IDocs on the database, but they are not being sent, check if your custom program issues a COMMIT WORK. Alternatively you could also see if changing the partner profile from Send immediately to Send via background program and then sending the IDoc via RSEOUT00 makes a difference.
    Cheers, harald

  • Automatic PO generation while doing MIGO

    Hi,
    Please guide me the details configuration and data maintain steps to enable automatic po generation at the time of doing MIGO with the movement type .
    Thanks in Advance,
    Regards,
    Soumen

    Settins
    a) Define and asing standard purchasing Organization at the Enterprice structure configuration
    Note: You can use the same normal purchasing organization you use for procurement as a standard.
    b) Activate automatic PO indicator for movement type 101 in coustomizig
    materials management - inventory management - goods receipt - create purchase order automatically
    c) Define purchasig document type
    materiales management - purchasing - define default values for puchasing document type
    d) Infor record for the standard purchasing organization and the vendor mater record.
    Note: You can use the same normal purchasing organization you use for procurement as a standard.
    e)The material has to be valuated
    And when you use de MIGO use movement type 101 as an non ordered item.
    regards,
    MC

  • Problem in Automatic mail generation after shipment creation in vt01

    Hi All,
    In VT01 Automatic mail generation to  customer  whenver a new shipment is created & in from address user mail adderess is mentioned but in my requirements i have  to mention different mail id in user mail address.
    how can i do this?
    please give me ur suggestions.
    Thanx

    Hi...
    When user close the shipment ,then he gets a mail on his id automatically generated from sap system.
    he want this mail should come to the mail id of his colleague.
    Pls reply asap.
    Thanx
    Vj

  • Inbound Idoc Generation

    Hello All,
    We have a ALE concept to transfer data between clients. We have made the settings and the process was fine. But on some days Inbound Idoc is not getting generated with respect to the outbound Idoc, and after some times once again system comes to normal state and the idoc generation is fine. How ever we dont have any root cause for the failure of Idoc generation. Could someone let me know where i can chk the info and what all the parammetres needs to be checked.
    Note ; There are no issues in ALE ocnfig settings.

    Hi ,
    See the following code :
    Program To Generate IDoc
    *& Report  ZZ_Program_To_Create_Idoc                                        
    report  zz_program_to_create_idoc                     .
    tables: ekko,ekpo.
    selection-screen skip 3.
    selection-screen begin of block b1 with frame title titl.
    selection-screen skip.
    select-options s_ebeln for ekko-ebeln.
    selection-screen skip.
    selection-screen end of block b1.
    data: header_segment_name like edidd-segnam value 'Z1EKKO',
          item_segment_name like edidd-segnam value 'Z1EKPO',
          idoc_name like edidc-idoctp value 'Z19838IDOC1'.
    data: header_segment_data like z1ekko,
          item_segment_data like z1ekpo.
    data: control_record like edidc.
    data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
    data: i_communication like edidc occurs 0 with header line,
          i_data like edidd occurs 0 with header line.
    data: begin of i_ekko occurs 0,
          ebeln like ekko-ebeln,
          aedat like ekko-aedat,
          bukrs like ekko-bukrs,
          bsart like ekko-bsart,
          lifnr like ekko-lifnr,
          end of i_ekko.
    data: begin of i_ekpo occurs 0,
          ebelp like ekpo-ebelp,
          matnr like ekpo-matnr,
          menge like ekpo-menge,
          meins like ekpo-meins,
          netpr like ekpo-netpr,
          end of i_ekpo.
    start-of-selection.
    select  ebeln aedat bukrs bsart lifnr from ekko
              into table i_ekko where ebeln in s_ebeln.
    select ebelp
           matnr
           menge
           meins
           netpr
           from ekpo
           into table i_ekpo
           where ebeln in s_ebeln.
    control_record-mestyp = messagetyp.
    control_record-rcvprt = 'LS'.
    control_record-idoctp = idoc_name.
    control_record-rcvprn = '0MART800'.
    loop at i_ekko.
    header_segment_data-ebeln = i_ekko-ebeln.
    header_segment_data-aedat = i_ekko-aedat.
    header_segment_data-bukrs = i_ekko-bukrs.
    header_segment_data-bsart = i_ekko-bsart.
    header_segment_data-lifnr = i_ekko-lifnr.
    i_data-segnam = header_segment_name.
    i_data-sdata = header_segment_data.
    append i_data.
    select ebelp
           matnr
           menge
           meins
           netpr
           from ekpo
           into table i_ekpo
           where ebeln = i_ekko-ebeln.
    loop at i_ekpo.
    item_segment_data-ebelp = i_ekpo-ebelp.
    item_segment_data-matnr = i_ekpo-matnr.
    item_segment_data-menge = i_ekpo-menge.
    item_segment_data-meins = i_ekpo-meins.
    item_segment_data-netpr = i_ekpo-netpr.
    i_data-segnam = item_segment_name.
    i_data-sdata = item_segment_data.
    append i_data.
    endloop.
    clear i_ekpo.
    refresh i_ekpo.
    endloop.
    call function 'MASTER_IDOC_DISTRIBUTE'
      exporting
        master_idoc_control                  = control_record
      OBJ_TYPE                             = ''
      CHNUM                                = ''
      tables
        communication_idoc_control           = i_communication
        master_idoc_data                     = i_data
    exceptions
       error_in_idoc_control                = 1
       error_writing_idoc_status            = 2
       error_in_idoc_data                   = 3
       sending_logical_system_unknown       = 4
       others                               = 5
    if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
             with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    else.
      loop at i_communication.
        write: 'IDOC GENERATED', i_communication-docnum.
      endloop.
      commit work.
    endif.
    initialization.
    titl = 'ENTER THE PURCHASE ORDER NUMBER'.
    Reward points if helpful.
    Regards.
    Srikanta Gope.

  • How to automate the generation of SCB Indicator while raising Invoices?

    Hi Team,
    According to our client requirements we are using different SCB Indicators(for Foreign vendors) in order to segregate the payments for diff. services. Can we automate this SCB Indicator while raising the invoices ? Else is there any other way to achieve this requirement.
    We are using different sources to raise the invoices automatically like self billing process, other middleware i.e. from Non-SAP system etc.,
    If we are raising invoices manually via MIRO / FB60 then we are giving the suitable SCB indicator according to the relevant service. Can we automate the generation of SCB Indicator while raising the invoices automatically ?
    Please provide your valuable suggestions!
    Thanks & Regards,
    Lakshmi S

    Hi Vinod,
    Thanks alot for your help in this regard
    Requesting you to please clarify here which BADI is the relevant one.PFB the screenshot for your easy reference.Because we found nearly 4 BADIs related to this scenario.Please through some light here once.
    Thanks in Advance!
    Regards,
    Lakshmi S

  • Any BADI returning the 'IDOC Status'  during IDOC generation.

    Hello All,
    I need a BADI which is being called during any IDOC generation and which returns the 'IDOC Status' i.e. Pass/Fail etc.
    So far I am able to find BADIs like 'IDOC_DATA_MAPPER' or ''IDOC_DATA_INSERT'' but such BADIs only return the IDOC document number.. they do not return any information on IDOC Status (the field Status field remains blank).
    Can any one suggest some solution on this please.
    Regards
    Vikas Gupta

    Hi Erik,
    Thanks for your reply, though i was able to get the status from BADI IDOC_DATA_MAPPER itself (earlier there were some config issues...which were creating some problems) but thanks for letting me know about table EDIDS, it helped at places.
    Regards
    Vikas Gupta

  • LSMW error message during "Start Idoc generation"

    Hi ,
    I am getting error message "'/tmp/YS.lsmw.conv' File Has Not Been Accepted for Processing"
    during the step "Start Idoc generation" in transaction LSMW.
    Please help to solve this issue.
    Thanks & regards,
    Yogita

    Hi,
    I already have set port and partner function.
    As per the details of the error message, it says "
    System Response
    Clarify if the inbound file is a Unicode file.
    Procedure
    If it is not a Unicode file, change the port definition and then start inbound processing again.
    If it is a Unicode file, then the file must be generated with the 'EDI_DC40_U' indicator. This must be clarified with the creator of the file.
    I have added the check Unicode fomat while defining the port.
    Can you please help?
    Regards,
    Yogita

  • Idoc generation

    HI All,
    If I enter the necessary data in tcode ME21 for purchase order and click on save button, corresponding idoc is to be generated.
    This is my requirement.
    For this, I worked out and came to know that I have to configure the following steps:
    RFC destination, Ports Creation, Partner Profile configuration, Distribution control.
    Apart from these, any other configuration is to be done ??
    Plz suggest me in what order i have to do all these....
    rgds,
    anil.

    Hi satish kumar ,
    Go through the following links
    You will find important information about IDOC generation
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    ALE/ IDOC/ XML
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    Good Luck and reward me for the same
    Thanks
    Ashok.N

  • Automatic invoice generation for service contract

    Hello,
    I want to create the  automatic invoicce generation for service contract based on the order.
    whenever i raise service contract order system should create the invoice automatically.
    could please let me know the settings?

    Hi JP Reddy
    You can schedule VF04/VF06 for your requirement, such that VF06 will run every 15/30 minutes and will generate billing document for your contracts automatically.
    Else go for Z extension development which will assign as output type to your contract and once triggered it will create invoice.
    try and revert

  • C202 idoc generation

    Hello All,
    I have a requirement like this.
    For transaction C202, (Master recipe change), when I go to Materials->BOM and change material quantity,
    and save the document, an idoc should be created. We hve Idoc type, Message type and Object type copied from BOM001 as customized.
    How can I achieve this. In NACE, I hve done changes for application (p1) ->medium (A) and processing routine ALE_processing and program RSNASTED for output type ME01. 
    But idoc is not getting created when I change BOM quantity and SAVE the document.
    Am I missing something here? I am not linking the object type (BOR) anywhere. Is this an issue?
    Any help and detailed explanation step-by-step what to do to achieve idoc generation would be appreciated.
    Thanks
    Ricky

    Hi,
    For ur scenario u need to go for change pointers method only.U have other options like distributing master data and transactional data..But i don't think anything otherthan change pointers is useful.
    Regards,
    Nagaraj

  • Automatic number generation using the function module

    Hai Everyone,
    I have the doubt in automatic number generation.
    i find the function module. the function module is
    report 123.
    *DATA: RC         LIKE INRI-RETURNCODE,
         NUMBER(10) TYPE C.
       CALL FUNCTION 'NUMBER_GET_NEXT'
            EXPORTING OBJECT          = 'HUGO'
                        NR_RANGE_NR     = '01'
            IMPORTING RETURNCODE      = RC
                        NUMBER          = NUMBER.
      CASE RC.
        WHEN ' '.
         everything o.k.
        WHEN '1'.
         the assigned number lies in the critical area.
        WHEN '2'.
         this was the last number, next time the first number
          will be assigned
      ENDCASE.
      write:/ number.
      in that function module what i want to give the  Exporting Object  'HOGO'. where i want to define the number range. what is meant by 'HOGO'.
    If any one faced the same problem plz help me.
    Thanks and regards,
    P.Naganjana Reddy

    Hai Chandrasekhar,
    in that what i have to give. Plz help me in this.
    Subobject data element
    To-year flag
    Number length domain
    No interval rolling
    Number range transaction
    Warning %
    Main memory buffering
    Group table
    Subobject field in group table
    Fld  NoRangeElement
    Fields int./ext. no.range no.
    Fld. NoRangeNo
    Display element text
    Thasnks and regards,
    P.Naganjana reddy

Maybe you are looking for