Data elements in Idoc segments

Hi Experts,
Is there a way to get the list of Idoc segments in which a particular data element is used.
Regards,
Sridevi

Hi Sridevi,
Please check table EDSAPPL where you have segment type and data element. If you need to check in which idoc type these segments are residing then you can check table IDOCSYN. Hope this helps.
BR,
Atanu

Similar Messages

Data elements for IDoc Segments to non-SAP system

Hi,
I need to create IDocs for transferring data to non-SAP system. When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system? Because there are many fields where the field attributes of SAP system do not match the corresponding fields of receiving non-SAP system.
Thanks in advance!!
Regards,
Sriram

Hi Sriram,
When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system
Is it custom segments .
Regards,
Madhu.

How to change data element of IDOC segment

HI Experts,
I have copied a segment E1ISU_MEASUREMENT_MEA to ZE1ISU_MEASUREMENT_MEA.
Now i want to change data element of one of the field of the segment.
Please guide me how i can do it?
is there any disadvantages of doing this?
can we do it easily?
please give me step by step instructions if possible .
thanks in advance
Anit

Hi,
When you want to modify the segment details of a particular IDoc, you could do the same by editing the segment details via t-code, WE19. Once you edit, click on, Outbound or Standard Inbound if your IDoc is Outbound or Inbound respectively. A new IDoc will get generated. The generated IDoc will be in "yellow" status, ready to be picked up by a batch job if there exists one. Else you need to manually process the IDoc via the respective program.
~ Bineah

Chanding the content in an IDOC segment at runtime

Hi Experts,
I have funny issue with modification of the data in an IDOC segment. Below is the description of the issue:
     I am using the IDoc type FIDCC2.FIDCCP02. I have to populate the value for field 'KTOSL' of the
     segment E1FISEG. I wrote the logic in user exit EXIT_SAPLF050_006. It is getting triggered and the
     logic is updating the values in the IDOC_DATA internal table properly.
     When the IDoc is generated, I observed that the value for this field is not updated in IDoc Segment.
Could you please suggest where I went wrong.
Ramana

Hi Neha,
Thank you for the responce.
We need not to fill all the 21 fields before the field KTOSL. Because I was using the work area to modify the internal table based on the index.
One thing I can conclude is that we cannot change the values in the standard segments of a stanrd Idoc type. By the time you enter in the processing Functinal Module, the Idoc number would have been generated. So the modification we carry out are just updating the internal table which of no effect. The right way is that find the place where the values getting updated to the data base and change values as required. These changed values can be founf in the data base but not in the IDoc generated.
Neha one more query for the clarification,could you ever delt with the down payment requests through IDocs. If so please share the details.
Ramana

IDOC Creation - structure has no data elements

Hello,
I've encounted the following situation when creating a new custom idoc:
The structure in the data dictionary does not have any components (Data elements) associated with each field. (i.e if you view the structure using se11). This is causing problems when trying to build ALE conversion rules using BD79 as you cannot tell which field is which for conversions with muliple conditions.
Does anyone know how to get data elements against the fields in the dictionary structure. Standard SAP idocs appear to have them - see E1MARCM.
(we are using version 4.7)
Any help would be appreciated,
Thanks!

Anita,
I am assuming that although you are creating a custom idoc you are referring to standard strucutre already existing for your segment.
I am not very clear here, how did you create the segment. Can you clarify on the same?
regards,
Ravi

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

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..
Re: 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

Adding data element to segment in we31 in ECC 6.0

hi all,
I have added field name ( data element ) to segment in we31 in 4.6 C by going Edit u2013> cancel release, then F6 to goto change mode to add our field.
Now I have to add the same field ( data element ) to segment While adding it is giving system error as " Error while resetting the release of segment ZE1XXXXXX_01"
Kindly let me know what to do ?
Thanks in advance

Problem solved with the help of my collegue.
It is just using "Segment --> Add version".
As the old version is already released so we can
"Edit --> Cancel release".
Thanks,

Error while using '*'in the NTE (EDI 850) Segment where '*' is also used as Data Element

Hi All,
I am facing below mentioned error while using '*'in the NTE (EDI 850) Segment where '*' is also used as Data Element
Error: 1 (Field level error)
SegmentID: NTE
Position in TS: 70
Data Element ID: NTE02
Position in Segment: 2
Data Value:
3: Too many data elements
For Eg: NTE*GEN*My Text *goes here
Here, NTE02 should be My Text *goes here. So, how can I use "*" here without changing anything in the EDI message?
Can it be done?
Thanks.

Sorry, no.
X12 does not support an escape character so whatever is used for delimiters become reserved characters.
If you want to allow '*' in the data, you will have to chooser a different Element delimiter. The receiver should read the from this from the ISA Segment so it's supposed to be dynamic but that's not always the case in practice.

Need to change the lenth of data element WRBTR in Idoc FIDCCP01.

Hi All,
In my program i am doing a amount calculation and storing it in variable of data type BSIS-WRBTR. The same i am passing to a Idoc segment FIDCCP01 which alos uses the same data type. WRBTR has alenth of (13,2).
My calculation are crossing the desired limit of this data type. So i would like to change the Data elemet WRBTR used in IDOC segment.
Can any one guide me in how to do this.
Thanks,
Ravi Kasnale.

Hi mr Bhagath.
the only options where i can get the IDOC Number is as shown in the below attached screen s .
Varma
iam not sure of where i can get the IDOC number and implement the code,the only area where i could get the IDOC number is at the higlited square block where i explained that i can get but i am not able to write any code there as SAP is not allowing me .
hope to get the best answer from you.
regards.
Varma

How to use '*' as data Element in the NTE(Edi 850) Segment

Hi All,
I am facing a field level error while using '*' in EDI 850 (NTE segment). '*' is also used as Data Element.
For Eg: NTE*GEN*My Text *goes here
Here, NTE02 should be My Text *goes here. So, how can I use "*" here without changing anything in the EDI message?
I have asked this question before
http://social.msdn.microsoft.com/Forums/en-US/1668e8d8-ee99-4d79-961b-8d26f3a496f8/error-while-using-in-the-nte-edi-850-segment-where-is-also-used-as-data-element?forum=biztalkediandas2
The answer in the above forum was to ask client modify the EDI message.
Previously, our client was using a different technology (other than BizTalk) which was working fine with this format. So, they are insisting on this format only.
Thanks,

Sorry, the answer is the same.
It doesn't matter what EDI platform either side is using, the '*' in the field content conflicts with the '*' that is the element delimiter. That is invalid EDI, there is no way around that short of writing a custom EDI parser.
It's not clear if you're sending or receiving this message. But again, it's really doesn't matter.
1. Change the Element Delimiter to something other than '*'. < or > are not uncommon.
2. If you are receiving the EDI, create a custom Pipeline Component that "handles" NTE02 either by replacing the '*' with a substitute char or deleting it.
3. If you are receiving, you could add extra elements to NTE to accommodate extra fields (since that's how the parser will see them). Then you can join them again in a Map.

IDOC segment Data updation problem

I have done the Idoc extention for ORDERS05.I have written a code to insert data for my z segments in IDOC_INPUT_ORDERS.But when I run the program its not updating data to z segements as well as other segments
What may be the problem..
READ TABLE dedidd INTO wa_edidd WITH KEY segnam = c-e1edka1
                                                  sdata(3) = 'AG'.
        IF sy-subrc = 0.
          CLEAR w-index.
          w-index = sy-tabix.
          wa_e1edka1 = wa_edidd-sdata.
          CLEAR : wa_e1edka1-parvw,
                  wa_e1edka1-partn.
          wa_e1edka1-parvw = w-parvw.
          wa_e1edka1-partn = w-inpnr_ag.
          wa_edidd-sdata = wa_e1edka1.
          MODIFY dedidd FROM wa_edidd INDEX w-index TRANSPORTING sdata.
ENDIF.
Thanks
Umesh

Hi,
Use Comparing fields addition in MODIFY Statement...
MODIFY ........ COMPARING <key fields>
Hope this would help you.
Regards
Narin Nandivada.

IDOC Segments data?

Hi,
Can anyone tell in which tables is the IDOC segments data is stored?
Rgds,
Kanwar

Hi,
IDoc segment data is stored in strcuture like EDIDD.
Suppose you have created IDoc,then the function module export parameter for Idoc data is IDOC_data(defined as IDOC_DATA STRUCTURE EDIDD).
then you can access data as below.
LOOP AT IDOC_DATA.
    CASE IDOC_DATA-SEGNAM.
      WHEN 'E1EDP01'.
        MOVE IDOC_DATA-SDATA TO E1EDP01.
***Here e1edp01 structure will give you details of ***individual field.
    ENDCASE.
ENDLOOP.
Similarly you can access data for all segments.
Thanks.
Mark points if helpful.

How to edit inbound idoc with data errors in multiple segments and reproces

Hi friends,
i have a requirement for error handling of inbound sales order(ORDERS04) without using WORKFLOW and WE19.
i have seen some function modules like edic_* ..
but my doubt is how to edit the error data(how can i identify the particular error fileds in the segments)and how to reprocess the same idoc.
Please help me...
Thanks in advance

Hi Narasimh,
Please find the following steps to edit IDOC segment after you find the error using WE02.
The example codes can be found in website
http://www.sapgenie.com/sapedi/idoc_abap.htm
STEP 1 - Open document to edit
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
       EXPORTING
            document_number               = t_docnum
       IMPORTING
            idoc_control                  = itab_edidc
       TABLES
            idoc_data                     = itab_edidd
       EXCEPTIONS
            document_foreign_lock         = 1
            document_not_exist            = 2
            document_not_open             = 3
            status_is_unable_for_changing = 4
            OTHERS                        = 5.
STEP 2 - Loop at itab_edidd and change data
LOOP AT itab_edidd WHERE segnam = 'E1EDKA1'.
e1edka1 = itab_edidd-sdata.
IF e1edka1-parvw = 'LF'.
    e1edka1-partn = t_eikto.
    itab_edidd-sdata = e1edka1.
    MODIFY itab_edidd.
    EXIT.
ENDIF.
ENDLOOP.
STEP 3 - Change data segments
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
           TABLES
                idoc_changed_data_range = itab_edidd
           EXCEPTIONS
                idoc_not_open           = 1
                data_record_not_exist   = 2
                 OTHERS                  = 3.
STEP 3a - Change control record
CALL FUNCTION 'EDI_CHANGE_CONTROL_RECORD'
       EXPORTING
            idoc_changed_control         = itab_edidc
       EXCEPTIONS
            idoc_not_open                = 1
            direction_change_not_allowed = 2
            OTHERS                       = 3.
STEP 4 - Close Idoc
Update IDoc status
CLEAR t_itab_edids40.
t_itab_edids40-docnum      = t_docnum.
t_itab_edids40-status      = '51'.
t_itab_edids40-repid       = sy-repid.
t_itab_edids40-tabnam      = 'EDI_DS'.
t_itab_edids40-mandt       = sy-mandt.
t_itab_edids40-stamqu      = 'SAP'.
t_itab_edids40-stamid      = 'B1'.
t_itab_edids40-stamno      = '999'.
t_itab_edids40-stapa1      = 'Sold to changed to '.
t_itab_edids40-stapa2      = t_new_kunnr.
t_itab_edids40-logdat      = sy-datum.
t_itab_edids40-logtim      = sy-uzeit.
APPEND t_itab_edids40.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
       EXPORTING
            document_number = t_docnum
            do_commit        = 'X'
            do_update        = 'X'
            write_all_status = 'X'
       TABLES
            status_records   = t_itab_edids40
       EXCEPTIONS
            idoc_not_open    = 1
            db_error         = 2
            OTHERS           = 3.
Hope this will help.
Regards,
Ferry Lianto

After data transfered (ALE/IDoc), the data in one of the segment IS GARBAGE

Hi Experts,
I have posted data through ALE/IDoc. I am checking the posted data. in one of the segment the address, street name, name.....etc are looks like "±±¾©»ÝµÂºÀÊË¿Æ¼¼·¢Õ¹ÓÐÏÞ¹«Ë¾"...these are garbage charecters. If I set it ot "Traditionally Chinese" in options, it is showing in regular native language. My aim is to bring this address (ADRMAS) in native language even after the data is posted. Where can I change the settings, do I need to deal with the complex custom code??
Please help me in this.
Thanks
Nilesh

To Look the the code page options (SM59), I dont have authorization here.
The main problem is, there are so many IDocs are generating each time I send the vendor data (BD14).
Why this many are generating? is it per target system? is so, is it going through the filter data?
Please explain steps........I would be really appreciate for quick response.
Thanks
Nilesh

Data Element of MSGFN field in IDOC (DEBMAS)

May I know which data element the field MSGFN belongs to. I couldn't find the corresponding in the table KNA1 for example.
Please help

Hi
MSGFN belongs to no structure.
It defines what to do with each segment.
Look at WE60 with DEBMAS* you may see the possible values or WE31 with whatever segment.
eg: E1KNVPM-MSGFN = '003' would mean delete the partner function related in this segment.
Hope this helps.
Alain

Data elements in Idoc segments

Similar Messages

Maybe you are looking for