Skip to Content
avatar image
Former Member

out bound IDOC creation

Hi experts,

I am given a task to create an out bound IDOC which would be input to TIBCO, which must be triggered every time Good issue transaction is completed by either VT02N or VL02N transaction up pressing SAVE.

IDOC is to have fields from Customize tables apart from standard SAP tables, so was asked to create an own IDOC ( eg: Z--Idoc).

Please tell me how to create the idoc, and also the method to trigger it and how to populate the IDOC ( program etc).

Use full inputs would be promtly rewarded.

Regards,

Ram.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Oct 05, 2007 at 02:07 PM

    Hi

    Creation of Custom IDOc type and message Type

    First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.

    take the Basis help to create them.

    1.First create segments in WE31 Tcode with the required dataelements

    2.Create the Basic Idoc Type in WE30

    release the Segments and IDOC type.

    3.Create Message type in We81

    4.Assign the message type to IDOC type in WE82 T code

    5.Create the process code in We41 (for Outbound) WE42 (for Inbound)

    6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for Inbound) Outbound Fun module

    7.Create Workflow setting if needed ..

    8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0

    9.Define setting for fun module in BD51

    10.In BD51 Define the settings for Fun module..

    10.Assign the Processs Code to Fun mod`ule

    Outbound Interface

    PROCESS DIAGRAM for Outbound Interface

    1. Analyse Hierarchy Levels

    2. Create New segment

    3. Create New IDoc Type

    4. Create New Message Type

    5. Link Message with IDoc Type

    6. Create an entry in EDP13 via transactions WE20 and BD64

    7. Populate the Custom IDoc via ABAP Program

    7b Error Handling

    7c. Send Status Email

    8. Test the Population of the Custom IDoc

    Step 1 – Analyse Hierarchy Levels:

    Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.

    Navigate to transaction code WEDI

    Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.

    Step 2 – Create a new segment:

    via wedi : Development - IDOC Segments or Transaction code WE31.

    • Enter segment name and click on Create.

    ? The name of the segment type must start with Z1 , and have a maximum of eight characters.

    • Enter description and enter the relevant field names and data elements.

    ? The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.

    • Save the segment and enter Person Responsible and Processing Person .

    • Go to Edit and Set Release.

    • Repeat this procedure for each new Segment in the IDOC.

    Step 3 – Create a new IDOC Type

    via wedi Development - IDOC Types or Transaction WE30.

    • Enter segment name (starting with Z), click on Basic Type and then Create.

    • Create as new, enter Person Responsible and Processing Person and enter description.

    • On ‘Create Basic Type’ screen decide where segments should be inserted and go to Edit/Create Segment.

    • Complete relevant fields in the Maintain Attributes screen:

    • From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.

    • The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).

    • The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.

    • Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a ‘Child’.

    • When IDOC created return to initial screen. Go to Edit and Set Release.

    • Go to Transaction WE60 to view the IDoc Type you have created.

    Step 4 – Create new Message Type

    via wedi Development - Message Types or Transaction WE81.

    • Display/Change and click on New Entries

    • Create a new Message Type and Save.

    Step 5 – Link Message Type to IDOC Type

    via wedi Development - IDOC Type/Message or Transaction WE82.

    • Display/Change and then click on New Entries.

    • Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.

    Step 6 – Create an entry in EDP13 via transactions WE20 and BD64.

    The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.

    • WE20 – Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.

    • BD64 – Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to ‘Environment’ on Menu and click on Generate Partner Profiles and generate (not save) profile.

    Step 7 – Populate the custom IDOC via ABAP Program

    See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.

    • Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.

    • The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.

    - PERFORM populate_Control_structure USING c_mestyp

    c_SEGMENT_type1.

    • The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.

    - PERFORM transfer_Parent_data_to_seg.

    • The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.

    - PERFORM master_idoc_distribute.

    • NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.

    • The ALE Layer handles the sending of the IDOC to the receiving system.

    • Error Handling (see Step 7b).

    • Commit work.

    Project Specific

    Step 7b – Error Handling• Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.

    • Declare a structure of type ‘MCMAILOBJ’ for sending instructions.

    • Enter values for the internal table based on structure ‘MCMAILOBJ’

    • For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module ‘MC_SEND_MAIL’.

    • Enter values in the following parameters: -

    MS_MAIL_SENDMODE = ‘B’ (Batch Mode)

    MS_MAIL_TITLE = 'Mail Title'

    MS_MAIL_DESCRIPTION = ‘Error description’ (e.g. MATNR not given)

    MS_MAIL_RECEIVER = ‘Name of Receiver’ (To be determined)

    MS_MAIL_EXPRESS = ‘E’ (Express Delivery)

    MS_MAIL_DLINAME = Leave Blank

    MS_MAIL_LANGU = 'E' (Language)

    MS_MAIL_FUNKOBJ_NAME = Leave Blank

    TABLES

    MS_MAIL_CONT = I_MCMAILOBJ

    Note:

    It has to be determined separately for each interface how these errors and mail notifications are to be grouped – dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.

    When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)

    Step 7c – Send status mail

    • Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.

    • Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).

    • Use function Module ‘MC_SEND_MAIL’ to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.

    Step 8 – Test the population of the custom IDOC

    via wedi IDoc - Display IDoc or Transaction WE02.

    • Enter your message type and execute.

    • Status should be green, double click on one of the Idocs you have created to view its contents.

    • If a problem has occurred click on Status which will give you a description of the error.

    • Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.

    • Click on each individual segment and view the content to check that the correct data has been read.

    • If you have UNIX access by using AL11 you can view the file that you have created.

    Note:

    For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.

    Regards

    Anji

    Add comment
    10|10000 characters needed characters exceeded