Skip to Content
author's profile photo Former Member
Former Member

Idoc Segment data

HI All,

I need to pass a constant value for the fields in segments between 2 systems,where can i do that,there a transaction code wher we can do,plz let me know,all useful answers are rewarded

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

7 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jul 11, 2007 at 07:17 AM

    Displaying IDoc Type or Segment Documentation

    Prerequisites

    The following section assumes that you wish to display a specific IDoc type. To display the documentation for an individual segment, choose Documentation ® IDoc segments from the initial screen of the IDoc interface and continue with step 3 in the section. However, the segment documentation only supports HTML and tree display formats.

    To display the documentation for a general IDoc type (IDoc record types), read the procedure in the following section - Displaying the General Structure (Record Types) of an IDoc You can display this documentation in all the formats specified below, apart from DTD.

    If you wish to send the documentation as an IDoc, you must define the IDoc type SYIDOC01 with the message type SYIDOC for your partner in outbound processing. For more information see: Partner Profiles in the Standard Dialog

    Procedure

    To gain an overview of all the IDoc types supplied by SAP (basic types), choose in the Initial Node of the IDoc Interface and then the F4 Help for your object basic type.

    A list of the basic types supplied with your release version is displayed, together with a brief description.

    Choose the required IDoc type.

    Choose Goto ® User settings and specify the required view. It means: IDoc type attribute

    Basic type or extension, release, version of record types: Also see important terms

    Segment attributes

    Frequency of use, necessity, qualified segment

    Segment field attributes

    Length (in bytes), data element, from which the field documentation is read.

    Segment documentation

    Defining text for the segment in general

    Segment field documentation

    Defining text for the individual segment fields = documentation of the associated data elements

    Field values

    For example fixed values which are attached to a domain or check tables from which the possible values are read.

    The further settings affect default values for different output formats (HTML, C-header and so on).

    Return to the initial screen and choose (display tree) for a quick overview of the system.

    The individual segments and their fields are displayed in a tree structure which corresponds to the parent-child segment hierarchy.

    You can select within the tree structure which parameters are to be output for individual objects (for example, a particular segment field). You can switch the corresponding icon on or off by clicking on it. For an explanation of the icons, select .

    You can select additional formats from the initial screen.

    for the IDoc format. Specify the corresponding partner (partner number and partner type).

    for the HTML format. Three files are generated: One for the frame, one for the index and one for the actual documentation. Their names end correspondingly with _f, _i and _d. An HTML browser loads the frame file and places the index and documentation files in the corresponding parts of the frame. If you have made the settings in the IDoc Administration User Parameters, the browser is started automatically.

    for the C-header

    for the parser

    Documentation ® Generate DTD for the DTD format

    The C-header and HTML formats contain the information "released since release...". In fact, this applies only from Release 4.0A onwards. In releases between 3.0D and 4.0A, this information specifies the release for which the IDoc type was created (which was usually where the IDoc type was also released). This information was not implemented in releases prior to 3.0D.

    Reward point if useful.

    Thanks.

    Abhay.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 11, 2007 at 07:19 AM

    Also check tcode we31.

    regards...

    abhay.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 11, 2007 at 07:19 AM

    Hi,

    I think it will be possible by SM59.

    Other wise check in WE30/31.

    <b>Reward points</b>

    Regards

    Message was edited by:

    skk

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 11, 2007 at 07:26 AM

    Hi Bharan kumar,

    You can pass values using <b>ALE/IDOC</b>, if it is two sap system then do the configuration of ale and pass the values through idoc. create the idoc and msgtype and transfer to the other system.

    Or try to get the values from the segment to the excel file and then integrate two system using third party software and then use bapi to upload data to other system.

    U can check the steps of configuring the ale and idoc below as sample :

    Go through the following Procedure & Links

    ALE IDOC

    Sending System(Outbound ALE Process)

    Tcode SALE ? for

    a) Define Logical System

    b) Assign Client to Logical System

    Tcode SM59-RFC Destination

    Tcode BD64 ? Create Model View

    Tcode BD82 ? Generate partner Profiles & Create Ports

    Tcode BD64 ? Distribute the Model view

    Message Type MATMAS

    Tcode BD10 ? Send Material Data

    Tcode WE05 ? Idoc List for watching any Errors

    Receiving System(Inbound ALE )

    Tcode SALE ? for

    a) Define Logical System

    b) Assign Client to Logical System

    Tcode SM59-RFC Destination

    Tcode BD64 ? Check for Model view whether it has distributed or not

    Tcode BD82 -- Generate partner Profiles & Create Ports

    Tcode BD11 Getting Material Data

    Tcode WE05 ? Idoc List for inbound status codes

    ALE IDOC Steps

    Sending System(Outbound ALE Process)

    Tcode SALE ?3 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 ?3 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

    Here Master Idoc set for Messge type MATMAS-->press Enter

    1 Communication Idoc generated for Message Type

    this is your IDOC

    Change Pointers

    I know how to change the description of a material using ALE Change Pointers.

    I will give the following few steps

    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

    ALE/IDOC Status Codes/Messages

    -


    01 Error --> Idoc Added

    30 Error --> Idoc ready for dispatch(ALE Service)

    then goto SE38 --> Execute the Program RBDMIDOC

    29 Error --> ALE Service Layer

    then goto SE38 --> Execute the Program RSEOUT00

    03 Error --> Data Passed to Port ok

    then goto SE38 --> Execute the Program RBDMOIND

    12 Error --> Dispatch ok

    Inbound Status Codes

    50 Error --> It will go for ALE Service Layer

    56 Error --> Idoc with Errors added

    51 Error --> Application Document not posted

    65 Error --> Error in ALE Service Layer

    for 51 or 56 Errors do the following steps

    goto WE19 > give the IDOC Number and Execute >

    Press on Inbound function Module

    for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error

    <b>Reward pts if found usefull:)</b>

    Regards

    Sathish

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 11, 2007 at 07:16 AM

    Hi Baharan,

    Use T.Code WE30.

    reward point if useful.

    regards...

    ABhay.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 11, 2007 at 07:17 AM

    Hi Bharan

    Can u explain a little bit more what your requirement is???

    Regards

    Pavan

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 11, 2007 at 07:29 AM

    Hi

    Data Creation in Idoc

    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an

    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.

    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.

    IDoc is a intermediate document to exchange data between two SAP Systems.

    *IDocs are structured ASCII files (or a virtual equivalent).

    *Electronic Interchange Document

    *They are the file format used by SAP R/3 to exchange data with foreign systems.

    *Data Is transmitted in ASCII format, i.e. human readable form

    *IDocs exchange messages

    *IDocs are used like classical interface files

    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.

    WE30 - you can create a IDOC type.

    An IDOC with data, will have to be triggered by the application that is trying to send out the data.

    FOr testing you can use WE19.

    How to create idoc?

    *WE30 - you can create a IDOC type

    For more information in details on the same along with the examples can be viewed on:

    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404

    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm

    http://www.sappoint.com/presentation.html

    http://www.allsaplinks.com/idoc_search.html

    http://www.sapgenie.com/sapedi/idoc_abap.htm

    http://www.erpgenie.com/sapedi/idoc_abap.htm

    To Create Idoc we need to follow these steps:

    Create Segment ( WE31)

    Create Idoc Type ( WE30 )

    Create Message Type ( WE81 )

    Assign Idoc Type to Message Type ( WE82 )

    Creating a Segment

    Go to transaction code WE31

    Enter the name for your segment type and click on the Create icon

    Type the short text

    Enter the variable names and data elements

    Save it and go back

    Go to Edit -> Set Release

    Follow steps to create more number of segments

    Create IDOC Type

    Go to transaction code WE30

    Enter the Object Name, select Basic type and click Create icon

    Select the create new option and enter a description for your basic IDOC type and press enter

    Select the IDOC Name and click Create icon

    The system prompts us to enter a segment type and its attributes

    Choose the appropriate values and press Enter

    The system transfers the name of the segment type to the IDOC editor.

    Follow these steps to add more number of segments to Parent or as Parent-child relation

    Save it and go back

    Go to Edit -> Set release

    Create Message Type

    Go to transaction code WE81

    Change the details from Display mode to Change mode

    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter

    Click New Entries to create new Message Type

    Fill details

    Save it and go back

    Assign Message Type to IDoc Type

    Go to transaction code WE82

    Change the details from Display mode to Change mode

    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.

    Click New Entries to create new Message Type.

    Fill details

    Save it and go back

    Check these out..

    how-to-create-idoc

    Check below link. It will give the step by step procedure for IDOC creation.

    http://www.supinfo-projects.com/cn/2005/idocs_en/2/

    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

    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs

    go trough these links.

    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

    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...

    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.

    2.IDOCs are independent of the sending and receiving systems.

    3.IDOCs are independent of the direction of data exchange.

    The two available process for IDOCs are

    Outbound Process

    Inbound Process

    AND There are basically two types of IDOCs.

    Basic IDOCs

    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.

    Extended IDOCs

    Extending the functionality by adding more segments to existing Basic IDOCs.

    To Create Idoc we need to follow these steps:

    Create Segment ( WE31)

    Create Idoc Type ( WE30)

    Create Message Type ( WE81)

    Assign Idoc Type to Message Type ( WE82)

    imp links

    http://www.allsaplinks.com/idoc_sample.html

    http://www.sapgenie.com/sapedi/idoc_abap.htm

    www.sappoint.com

    --here u can find the ppts and basic seetings for ALE

    http://sappoint.com/presentation.html

    www.sapgenie.com

    http://www.sapgenie.com/ale/index.htm

    Check these links.

    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

    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs

    Please check this PDF documents for ALE and IDoc.

    http://www.sappoint.com/abap/ale.pdf

    http://www.sappoint.com/abap/ale2.pdf

    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf

    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf

    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf

    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf

    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf

    Check below link. It will give the step by step procedure for IDOC creation.

    http://www.supinfo-projects.com/cn/2005/idocs_en/2/

    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

    Reward all helpfull answers

    Regards

    Pavan

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.