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.

Similar Messages

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.

Idoc segment for updating Sales order item dates

Hi All,
I would ike to update the sales order item dates (loading date, Goods Issuance date etc) from an IDOC.
please let me know the Idoc segment and fields that need to be filled in?
Thanks in advance.
Regards,
Zeeshan.

Hi,
Here are some details of the segments in the idocs -
SEGNAM Segment Name E1EDL20
VBELN Sales and Distribution Documen 180001539
SEGNAM Segment Name E1EDL18
QUALF IDOC Qualifier: Control (Deliv PIC : Picking with flow records (inbound)
SEGNAM Segment Name E1EDL18
QUALF IDOC Qualifier: Control (Deliv PGI : Post delivery goods issue (inbound)
SEGNAM Segment Name E1EDT13
QUALF IDOC Qualifier: Date (Delivery 010 : Picking
NTANF Constraint for activity start 20090808
ISDD Actual start: Execution (date) 20090808
SEGNAM Segment Name E1EDL24
POSNR Item number of the SD document 10
MATNR Material Number 1112
WERKS Plant SG01
KDMAT Material belonging to the cust 1112
LFIMG Actual quantity delivered (in 55
VRKME Sales unit EA
POSEX External item number 10
ORMNG Original Quantity of Delivery 55
SEGNAM Segment Name E1EDL41
QUALI Qualifier for Reference Data o 001 : Purchase order data of customer
BSTNR Customer purchase order number 4500004668
BSTDT Customer purchase order date 10
POSEX Item Number of the Underlying 10
SEGNAM Segment Name E1EDL37
Regards,
Shamma

How SAP handles Child Idoc segment data insertion automatically

Hello,
We have some Infotypes with extra segments and IDocs are getting created with Parent and child segments.
To fill the data into the parent/child segments, we are currently using User-Exits.
Is there any settings/config in table level(e.g. T777D etc), or any other way, so that SAP handles the data filling into parent/child segments automatically.
Thanks.

No I dont want to change the value in WE19.... In runtime I am changing the value of schedule Line quantity and the same is getting update in SDSA also but when a new idoc is getting created that value is not getting reflected in that Idoc segment field.
Kindly suggest.

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

RE: How to change Idoc segment data

Hi folks,
I have a requirement where in I have a Inbound DELIN Idoc in the SAP system. When I am reprocessing the same Idoc through WE19 by changing the delivery schedule and then changing the E1EDP16-WMENG value in runtime while debugging, the same is getting updated in correponding SDSA but when the new Idoc is getting triggered, only previous old Idoc value is getting reflected.
Kindly suggest!!!!
Vishal.

No I dont want to change the value in WE19.... In runtime I am changing the value of schedule Line quantity and the same is getting update in SDSA also but when a new idoc is getting created that value is not getting reflected in that Idoc segment field.
Kindly suggest.

How to change the IDOC segment data

How to change the segment data for all IDOCs at one shot J.
For exmple E1EDK02-QUALF - 004
                   E1EDK02-RGID - 100000008 (Inquiry No)
               to
       E1EDK02-QUALF - 004
                   E1EDK02-RGID - 200000005 (Quotation)
Any hints, tips.Appreciate your help and more rewards.
Regards,
Cris

Hi,
You can change the IDOC values using the transaction WE09
Give the IDOC number..
Press F8..
Expand the tree..
Double click on the segment..
Then in the menu..DATA RECORD -> DISPLAY/CHANGE..
It will go in change mode..Change the IDOC value..
Thanks,
Naren

Report to display IDoc segments data?

Hi all,
I have an idoc. That has segements. Each segments has fields. I need those fields data individually in each segement. Is there any reports that displays fields data of each segement and all the idoc data.
regards
helpful answeres are surely rewarded

We can see the Data of the fields in a segment in all the Idocs ( an Idoc type) you have selected.
1) Go to transaction "WE02".
2) Enter 'Basic type' of Idoc you are looking for and execute
3) Click on the last button (List Specific Segment, Shift+ F1) on the application tool bar
4) enter the Segment you are looking for and press enter.
5) It will display the Report with the Data of all the fields of the segment of all the Idocs selected.
Thanks
Shekar

Data updation problem?

Hi All,
I have two buttons, submit and save. in submit i am calling FM through service call to get data. data is coming correctly.
In save i am trying to save any changed data. but changed data is not saving, i checked through debug in table showing changed data, but in database it is not updating.
code i am using in SAVE button.
DATA lo_nd_it_vttk TYPE REF TO if_wd_context_node.
DATA lo_el_it_vttk TYPE REF TO if_wd_context_element.
DATA ls_it_vttk TYPE wd_this->Element_it_vttk.
DATA lt_it_vttk TYPE wd_this->Elements_it_vttk.
Data lt_it_vttk type STANDARD TABLE OF if_main=>Element_it_vttk.
DATA lt_it_vttk TYPE STANDARD TABLE OF vttk.
DATA wa_vttk TYPE vttk.
navigate from <CONTEXT> to <IT_VTTK> via lead selection
lo_nd_it_vttk = wd_context->path_get_node( path = `ZSHIPMENT_CHANGE.CHANGING.IT_VTTK` ).
get element via lead selection
lo_el_it_vttk = lo_nd_it_vttk->get_element( ).
get all declared attributes
lo_el_it_vttk->get_static_attributes(
    IMPORTING
      static_attributes = ls_it_vttk ).
******Changing DATA ************
WA_VTTK-EXTI1 = LS_IT_VTTK-EXTI1.
    WA_VTTK-DTDIS = LS_IT_VTTK-DTDIS.
    WA_VTTK-UZDIS = LS_IT_VTTK-UZDIS.
    WA_VTTK-DPREG = LS_IT_VTTK-DPREG.
    WA_VTTK-UPREG = LS_IT_VTTK-UPREG.
append WA_VTTK to lt_it_vttk .
MODIFIED DATA IS COMING TO lt_it_vttk TABLE. BUT NOT UPDATING DB
lock the table
CALL FUNCTION 'ENQUEUE_E_TABLE'
    EXPORTING
      MODE_RSTABLE   = 'E'
      TABNAME        = 'VTTK'
    EXCEPTIONS
      FOREIGN_LOCK   = 1
      SYSTEM_FAILURE = 2
      OTHERS         = 3.
MODIFY VTTK from table lt_it_vttk.
if sy-subrc is initial.
    COMMIT WORK .
else.
    ROLLBACK work.
endif.
CALL FUNCTION 'DEQUEUE_E_TABLE'
    EXPORTING
      MODE_RSTABLE = 'E'
      TABNAME      = 'VTTK' .
In this i am missing anything? Please Help.
Thanks,
Madan.

I guess the problem is here.
******Changing DATA ************
WA_VTTK-EXTI1 = LS_IT_VTTK-EXTI1.
WA_VTTK-DTDIS = LS_IT_VTTK-DTDIS.
WA_VTTK-UZDIS = LS_IT_VTTK-UZDIS.
WA_VTTK-DPREG = LS_IT_VTTK-DPREG.
WA_VTTK-UPREG = LS_IT_VTTK-UPREG.
you are not passing any key fields value here.
i guess you need to pass the value of
WA_VTTK-TKNUM field also.
SO ADD
WA-VTTK-TKNUM = LS_IT_VTTK-TKNUM.
Thanks
sarbjeet singh

IDoc meta data load problem in IDX2

I have been trying to load meta deta for some idocs and am getting message 'Basic type <idoc_type> is unknown'. Interesting to note is that I could load ECMMAS01 idoc type but other idoc types like MATMAS01 ..04, ORDERS01 ...04, DOCUMENT_LOAD01 ... and many others that I tried, I got the same message. The config has been done in IDX1 and IDX2 (that's how I got the ECMMAS01 in).
There is an OSS note '0000751839 IDoc Adapter: Basic type 'XYZ' is unknown. ' It seems we are already on that patch level. Can't verify if the note has been really applied or not for authorization issues for now. The note also mentions about a workaround to set the category level to '0' (i.e. blank) in the Integration server configuration. But that doesn't seem to help either.
Anyone else had this problem and resolved it?
Harshad

Problem stands resolved. I realized that the RFC destination in XI for the R/3 system had a problem. What still is not answered is how come I was able to import ECMMAS01?!?! One explanation could be that the RFC connection was ok then. Don't know, but I am happy that it works now.

Large data update Problem

I have a temprary table with 5 million rows (A)
which needs to be appended with 90 million row table (B).
60% of the rows of the 5mil rows already exist in the big table
i need to update/merge the table A data with table B
Oracle version is 8.1.7
Please advice which method is the fastest

hi raghu,
this is the portal content management forum. please post your database related question in the following forum:
General Database Discussions
this is the appropriate place to post database related questions.
thanks,
christian

Add leading zeroes in the IDOC segment data

Hi,
How to populate the Document number and EAN code in the segment with leading zeroes because I have checked that all fields in the segment are of charcter type.
I want to know can this be handled by customizing or coding but how?
Thanks
Prince

Hi,
You can use :
   call function 'CONVERSION_EXIT_ALPHA_INPUT'
    exportiong
      input = c1
    importing
      output = c1.
Regards,
Subramanian

IChart Date updation problem in version 12.1

Hi,
I have created a Line iChart for a TagQuery in which I am passing the Tags ,start date, end date and server (simulator) through the following script
                                          var chart = document.iChart;
          var qryObj = chart.getQueryObject();
          qryObj.setServer("simulator");
          qryObj.setStartDate("01/14/2011 07:00:00");
          qryObj.setEndDate("01/14/2011 07:01:00");
          qryObj.setDuration(60);
          chart.refresh();
I am getting the Line Chart but it is always displaying the StartDate as system current date and EndDate as StartDate +60 min (in setDuration) but I need Line Chart for the date's which I am passing through the script
Thank you for the answers in advance..

Use: updateChart(true) instead of refresh()
Your query is time based, so it will 'refresh' the chart to the most recent duration.
http://help.sap.com/saphelp_mii122/helpdata/EN/44/b305d64c7914e6e10000000a114e5d/frameset.htm

Can we chnge segment data of IDOC while processing using EXITS ?

Hi All,
We have requirement that we have to do validations while processing of IDOC i.e. using User EXIT.
i can access the data and can do validations final i can update the tables data coming from user exit , but I'm not able to update the Segment field data.
here we can directly update the database , but i'm not able change the IDOC segment values .
for example
   FOR cond_a IDOC
THE USER EXIT==>EXIT_SAPLVKOI_002
FUNCTION EXIT_SAPLVKOI_002.
""Lokale Schnittstelle:
*"       IMPORTING
*"             VALUE(IDOC_CONTROL) LIKE EDIDC STRUCTURE EDIDC
*"             VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"       TABLES
*"              IDOC_DATA STRUCTURE EDIDD
*"       EXCEPTIONS
*"              APPLICATION_ERROR
i can acess the segement values using IDOC_DATA and validations are done .
but how can i update this segmnent values that must apper in IDOCS again .if we see in we05.
Regards
Nandan.

Hi Nadan ,
Yes we can change segment data of an Idoc in the Exits.
Below is the code to change the Idoc segment data .
Here I took E1EDK04 as example I read the data from E1EDK04 and I change the segment data
READ TABLE t_idoc_data INTO is_edidd
WITH KEY segnam = c_segnam_e1edk04. "#EC *
IF sy-subrc EQ 0.
MOVE: is_edidd-sdata TO is_e1edk04.
ENDIF.
IF l_betrg = c_betrg.
is_e1edk04-mwskz = C_TAX20.
is_e1edk04-txjcd = c_txjcd.
ELSEIF l_betrg = c_betrg1.
is_e1edk04-mwskz = C_TAX21.
is_e1edk04-txjcd = wa_ekpo-txjcd.
ENDIF.
LOOP AT t_idoc_data
WHERE docnum = i_idoc_contrl-docnum.
CASE t_idoc_data-segnam .
WHEN c_segnam_e1edk04.
MOVE is_e1edk04 TO is_edidd-sdata.
MODIFY t_idoc_data FROM is_edidd.
ENDCASE.
ENDLOOP.
Please let me know if u have any Queries .
Rgds
Sree m

Trigger a process(IDOC) when Data in Z-table updated

Hi All,
I am working on an interface and the outbound IDOC from R/3 to XI needs to be triggered when a particular field value in a Z*table changes.
So far I am able to trigger the IDOC from the calling Z*prog which updates this table, but I need some exit, PAI etc which will get triggered only when the data in table is updated.
Current Flow chart:
Z-prog starts--->Updates a Z-table--->if sy-subrc=0--->I create an IDOC from the Z-prog itself
What I need:
Z-table is updated--->check if particular filed value changed--->Trigger IDOC
Is it possible to do this.
Many thanks
Shirin

Hi Balu,
I am triggering my IDOCS from the Z*program itself.
The trigger point is when I have successfully updated the table (sy-subrc = 0).
Then I have used the code below to populate my IDOC. I have also maintained a distribution model, so that is the reason I pass only the idoc type in edidc segment and do not pass any port , receiver etc.
Hope you find the code useful.
Regards
Shirin
Reward points if this was helpful.
*Local Data Declaration
DATA: wa_msg_header TYPE zca_msg_header,
         wa_edidc      TYPE edidc,
         wa_edidd      TYPE edidd,
         i_edidc       TYPE edidc OCCURS 0,
         i_edidd       TYPE edidd OCCURS 0,
         wa_trailer    TYPE zca_gs_trailer,
         wa_count(10) TYPE n,
         wa_allocation_response TYPE zca_allocation_response.
*Populate IDOC segments
* 1. Save the message type and the basic IDoc type* in the control segment
MOVE 'ZMT_ALLOCATION_RESPONSE' TO wa_edidc-mestyp.
MOVE 'ZGS_ALLOCATION_RESPONSE' TO wa_edidc-idoctp.
* 2. Populate the Genius specific Message Header 'ZCA_MSG_HEADER'
wa_msg_header-source        = 'SOURCE_SYST'.
wa_msg_header-destination   = 'DESTINATION-LS.
wa_msg_header-message_id    = ''. "Populate this in XI
wa_msg_header-date_time     = ''. "populate this in xi.
wa_msg_header-message_typ   = 'I'.
wa_msg_header-status        = 'S'.
MOVE 'ZCA_MSG_HEADER' TO wa_edidd-segnam.
MOVE wa_msg_header    TO wa_edidd-sdata.
APPEND wa_edidd       TO i_edidd.
CLEAR wa_edidd.
* 3 Populate the ALOCATION_RESPONSE segment
CONCATENATE 'EXAM'
               sy-datum
               sy-uzeit
               INTO
               wa_allocation_response-uid.
* wa_allocation_response-uid                 = i_set_number .
wa_allocation_response-set_number          = i_set_number .
wa_allocation_response-trigger             = '1' .              "Always default to Allocation Change   .
wa_allocation_response-next_a_exam         = i_next_a_exam .
wa_allocation_response-miles_to_a          = i_miles_to_a .
wa_allocation_response-next_b_exam         = i_next_b_exam .
wa_allocation_response-miles_to_b          = i_miles_to_b.
wa_allocation_response-next_major_exam     = i_next_maj_exam .
wa_allocation_response-miles_to_major_exam = i_miles_to_maj_exam .
MOVE 'ZCA_ALLOCATION_RESPONSE' TO wa_edidd-segnam.
MOVE   wa_allocation_response   TO wa_edidd-sdata.
APPEND wa_edidd                 TO i_edidd.
CLEAR wa_edidd.
*4 Populate the Trailer record 'ZCA_TRAILER'
wa_trailer-data_marker = 'T'.
wa_trailer-checksum     = wa_count.
MOVE 'ZCA_TRAILER' TO wa_edidd-segnam.
MOVE wa_trailer       TO wa_edidd-sdata.
APPEND wa_edidd       TO i_edidd.
CLEAR wa_edidd.
* Check for distribution model and create the IDOC
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      master_idoc_control            = wa_edidc
    TABLES
      communication_idoc_control     = i_edidc
      master_idoc_data               = i_edidd
    EXCEPTIONS
      error_in_idoc_control          = 1
      error_writing_idoc_status      = 2
      error_in_idoc_data             = 3
      sending_logical_system_unknown = 4
      OTHERS                         = 5.
* No need for error handling here as the IDOC will be created and ststus record will
* mention the latest ststus including any error message.

IDOC segment Data updation problem

Similar Messages

Maybe you are looking for