MASTER_IDOC_DISTRIBUTE inbound idocs?

I am trying to post an inbound IDOC that was created inside an ABAP program.
I have tried MASTER_IDOC_DISTRIBUTE and set the direction on the control record to '2' (inbound), however when i look at the idoc posted in WE02, its in the outbound section, not the inbound. Of course it's failing there because the partner is not set up (nor should it be) to process this idoc as outbound.

Hi, I think if you direcly call this FM (IDOC_INPUT_ORDERS), it can goes, even without the IDOC number. The IDOC number is for the EDI/ALE layer to differentiate the IDOCs, but it looks no usage in the Inbound FM inside, as these FM is only for inbound IDOC data into server.
Maybe there will be some consistency issue occur, but the inbound can be done, haven't tried it.
By the way, it looks you want to create a IDOC which has the same sender and receiver, it has some other way, you can reference in the following link:
http://www.sapgenie.com/ale/whitepaper.htm
In The 7.3 Topic it has been explained to configure this scenerio.
hope it will be helpful
Thanks a lot

Similar Messages

Collective inbound idocs into R/3 system using master_idoc_distribute FM

Hi All,
I want to process inbound idocs (4 idocs collectively) in R/3 using master_idoc_distribute function module. The idoc is coming into system as one idoc having 4 segments (each segment for each idoc and contains sub segments too). I want to call master_idoc_distribute for each idoc for sending it to external system. I am using a custom FM for calling the master_idoc_distribute and assigning it into process code inbound for processing the incoming idoc.
The FM is working for one idoc perfectly but throwing error for more than idocs coming in collectively. Any help is appreciated.
Thanks

use commit work saparately after each function module call

Creation of Inbound IDOC from a flat file.

Hi all,
I hav to create Purchse Order using inbound IDOC in which I hav to take data from a .xls or any flat file.
Can any one help me with this. i.e wat r the steps involed to do so.
Regards.
Rahul

Hello,
Why do u want to create a Idoc for creating PO from flat file - you can simply use BAPI. Ok if you want to create PO only using Idoc.
I think message type is ACC_PURCHASE_ORDER0.
I just made one sample program to you how to create a PO with Idoc method. Here i am doing for Material Master Creation. Let me know if want any clarification.
********Poorna********
TABLES : MARA, MAKT, EDP13.
DATA : I_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE,
      I_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
PARAMETERS : P_MATNR LIKE MARA-MATNR.
START-OF-SELECTION.
REFRESH I_EDIDC.
SELECT * FROM EDP13 WHERE MESTYP = 'ZMATMASTER'.
    MOVE-CORRESPONDING EDP13 TO I_EDIDC.
    I_EDIDC-IDOCTP = EDP13-IDOCTYP.
    APPEND I_EDIDC.
ENDSELECT.
READ TABLE I_EDIDC INDEX 1.
I_EDIDD-SEGNAM = 'ZMATMASTER'.
SELECT SINGLE * FROM MARA WHERE MATNR = P_MATNR.
SELECT SINGLE * FROM MAKT WHERE MATNR = P_MATNR
                              AND SPRAS = SY-LANGU.
I_EDIDD-SDATA+0(18) = MARA-MATNR.
I_EDIDD-SDATA+18(40) = MAKT-MAKTX.
I_EDIDD-SDATA+58(4) = MARA-MTART.
I_EDIDD-SDATA+62(1) = MARA-MBRSH.
I_EDIDD-SDATA+63(3) = MARA-MEINS.
APPEND I_EDIDD.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      master_idoc_control                  = I_EDIDC
   OBJ_TYPE                            = ''
   CHNUM                                = ''
    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
COMMIT WORK.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
       WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

INBOUND IDOC Creation

Hi ,
Trying to create an INBOUND IDOC for material.
Using the FM MASTER_IDOC_DISTRIBUTE . But the problem is that this is creating an idoc as an outbound .although I have set the parmeter for direction as inbound.
Could some please advise me which Fm should I use to create an IDOC as inbound ?
since I can see there are more FM like 'IDOC_WRITE_AND_START_INBOUND' and CCDL_MASTER_IDOC_CREATE and more.
Thanks and Regards,
Ankur

Hi,
The FM that you have specified here are the one which are used for saving the data from IDOC to SAP.
But in this scenarion I want to create an IDOC with inbound direction . to be more eleborative I will get incomplete information from External system in IDOC and based on this I neeed to create an Standard IDOC filling the more required information and then this Standard IDOC will be processed by Standard FM like the one you have specified here 'IDOC_INPUT_XXXX',
What i need is the FM for Creating this Standard IDOC as inbound.
hope this explain .
Thanks and Regards,
Ankur

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.

Send inbound IDOC as outbound(copy)

Hi,
We need to send the same inbound IDOC as outbound IDOC to the customer(they want to get a copy of it) How can we do this? We are getting inbound sales order IDOC's and the customer wants the copy of the same IDOC, not order acknowledgement. Is it possible?
Any inputs are greatly appreciated.
Sarita

I can think of following:
You create your own Process code, Function Module to update your data using Inbound IDOC and at the end generate outbound IDOC using same data and then distribute using MASTER_IDOC_DISTRIBUTE.

Inbound - IDoc problem

Hi Friends,
Can anybody help me . I am facing a problem in IDOC inbound processing.
My scenario in SALES PER RECEIPT - POS like this: I have to read XML (From PC) file and i have to post it.
I am using Idoc - WPUBON01. After reading XML file i used Function module to distribute - MASTER_IDOC_DSTRIBUTE.
In we02 i checked Idoc is generating but status showing 29.
So run the report RSEOUT00. But i am getting message like 'No idoc is selected for processing'.
Plz help me what i have to do. I created port also.
Regards,
P. Kumar.

Hi,
sarath has told valid point..don't use master_idoc_distribute,instead use the bapi
bapi_idoc_input1..
plz check the sample code how to do with inbound idoc,as u have got the data ,u just need to call the bapi and post it..
check the code and proceed..
FUNCTION zdtsint052f_gpoms_to_sap_gm.
""Local interface:
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
Purpose            :On recording the material consumption from       *
                    manufacturing tickets in GPOMS system, GPOMS     *
                    will report the data to the SAP system.Based     *
                    on this message, goods issue to the process order*
                    will be posted in SAP. This interface will       *
                    used for storage location managed materials      *
                    in SAP.                                          *
Program Logic      :Loop at the data records of IDOC and to get the *
                    Order number and SAP Movement type               *
                    If the Material document already exists for this *
                    Order number and Movement type then give error   *
                    else call standard FM 'BAPI_IDOC_INPUT1' to      *
                    Material Documents in SAP.                       *
Declaration of Constants                                             *
CONSTANTS :lc_item_create(25) TYPE c VALUE 'E1BP2017_GM_ITEM_CREATE',
             lc_mbgmcr(6)       TYPE c VALUE 'MBGMCR'.
Declaration of Variables                                             *
DATA : lv_index TYPE sytabix,
         lv_retcode type sy-subrc.
Declaration of Workareas                                             *
DATA: lwa_e1bp2017_gm_item_create TYPE e1bp2017_gm_item_create,
        lwa_data         TYPE edidd, " Work area for IDOC
        lwa_control      TYPE edidc. " Work Area for control rec
Read the control data information of idoc.
loop at idoc_contrl INTO lwa_control Where mestyp = lc_mbgmcr.
Extract the data from the segments.
    LOOP AT idoc_data INTO lwa_data
    WHERE docnum = lwa_control-docnum and
          segnam = lc_item_create.
*->> Set the tabix of the internal table
      lv_index = sy-tabix.
Move the Material Document Item Segment data
      MOVE lwa_data-sdata TO lwa_e1bp2017_gm_item_create.
Modify the material document item data internal table
      PERFORM sub_modify_idocdata changing lwa_e1bp2017_gm_item_create.
*->> set the changed values to the IDOC SDATA
      MOVE lwa_e1bp2017_gm_item_create TO lwa_data-sdata.
*->> Modify the table
      MODIFY idoc_data FROM lwa_data index lv_index.
Clear the Work areas
      CLEAR : lwa_data,
              lwa_e1bp2017_gm_item_create.
    ENDLOOP.                                     "LOOP AT t_idoc_data
Call the BAPI function module to create the
appropriate Material Document
    CALL FUNCTION 'BAPI_IDOC_INPUT1'
      EXPORTING
        input_method          = input_method
        mass_processing       = mass_processing
      IMPORTING
        workflow_result       = workflow_result
        application_variable = application_variable
        in_update_task        = in_update_task
        call_transaction_done = call_transaction_done
      TABLES
        idoc_contrl           = idoc_contrl
        idoc_data             = idoc_data
        idoc_status           = idoc_status
        return_variables      = return_variables
        serialization_info    = serialization_info
      EXCEPTIONS
        wrong_function_called = 1
        OTHERS                = 2.
    IF sy-subrc = 1.
      RAISE wrong_function_called.
    ENDIF.
endloop.
ENDFUNCTION.
***INCLUDE LZDTSINT052F_GPOMS_GMF01 .
*&      Form sub_modify_idocdata
Modify the material document item data internal table
FORM sub_modify_idocdata
CHANGING pwa_e1bp2017_gm_item_create TYPE e1bp2017_gm_item_create.
contant declaration
CONSTANTS: lc_261(3) TYPE c VALUE '261'.
DATA : lv_aplzl LIKE resb-aplzl,
         lv_aufpl LIKE resb-aufpl,
         lv_subrc LIKE sy-subrc,
         lv_charg LIKE resb-charg,
         lv_uom LIKE pwa_e1bp2017_gm_item_create-entry_uom.
CLEAR: pwa_e1bp2017_gm_item_create-reserv_no,
         pwa_e1bp2017_gm_item_create-res_item.
*->> Get SAP storage bin & Storage type from the Z table
SELECT lgtyp lgpla
    INTO (pwa_e1bp2017_gm_item_create-stge_type,
          pwa_e1bp2017_gm_item_create-stge_bin)
     UP TO 1 ROWS
    FROM zdtsint050_sttyp
     WHERE zstorage_typ = pwa_e1bp2017_gm_item_create-stge_type
      AND zstorage_bin = pwa_e1bp2017_gm_item_create-stge_bin.
ENDSELECT.
IF sy-subrc NE 0.
    CLEAR: pwa_e1bp2017_gm_item_create-stge_type,
           pwa_e1bp2017_gm_item_create-stge_bin.
ENDIF.
PERFORM get_oper CHANGING pwa_e1bp2017_gm_item_create.
Get the Reservation number and Reservation item number
basing on the idoc data.
SELECT rspos werks lgort
         INTO (pwa_e1bp2017_gm_item_create-res_item,
              pwa_e1bp2017_gm_item_create-plant,
                 pwa_e1bp2017_gm_item_create-stge_loc)
         FROM resb
         UP TO 1 ROWS
         WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no
         AND   matnr = pwa_e1bp2017_gm_item_create-material
         AND   charg = pwa_e1bp2017_gm_item_create-batch
         AND   aufnr = pwa_e1bp2017_gm_item_create-orderid
         AND   vornr = pwa_e1bp2017_gm_item_create-activity
         AND   bwart = lc_261.
ENDSELECT.
IF sy-subrc <> 0.
Start of insertion for R31K993797
    CLEAR lv_charg.
    SELECT rspos werks lgort
         INTO (pwa_e1bp2017_gm_item_create-res_item,
              pwa_e1bp2017_gm_item_create-plant,
                 pwa_e1bp2017_gm_item_create-stge_loc)
         FROM resb
         UP TO 1 ROWS
         WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no
         AND   matnr = pwa_e1bp2017_gm_item_create-material
         AND   charg = lv_charg
         AND   aufnr = pwa_e1bp2017_gm_item_create-orderid
         AND   vornr = pwa_e1bp2017_gm_item_create-activity
         AND   ( splkz = 'X' or
                 splkz = space )
         AND   bwart = lc_261.
    ENDSELECT.
    IF sy-subrc <> 0.
End of insertion for R31K993797
      SELECT SINGLE werks lgort
            INTO (pwa_e1bp2017_gm_item_create-plant,
                   pwa_e1bp2017_gm_item_create-stge_loc)
            FROM resb
            WHERE rsnum = pwa_e1bp2017_gm_item_create-reserv_no.
      CLEAR : pwa_e1bp2017_gm_item_create-reserv_no,
              pwa_e1bp2017_gm_item_create-res_item.
    ENDIF.
ENDIF.
get SAP UOM
SELECT SINGLE zsap_uom
                INTO lv_uom
                FROM zca_uom_conv
                WHERE zext_uom = pwa_e1bp2017_gm_item_create-entry_uom.
IF sy-subrc = 0.
    pwa_e1bp2017_gm_item_create-entry_uom = lv_uom.
ENDIF.
ENDFORM.                    " sub_modify_idocdata
*&      Form get_oper
     Get the operation
     <--P_PWA_E1BP2017_GM_ITEM_CREATE_RE Segment
FORM get_oper CHANGING p_pwa_e1bp2017_gm_item_create TYPE
               e1bp2017_gm_item_create.
DATA : l_aufpl LIKE afko-aufpl,
         l_aplzl LIKE afvc-aplzl.
REFRESH : i_op.
UNPACK p_pwa_e1bp2017_gm_item_create-orderid TO
         p_pwa_e1bp2017_gm_item_create-orderid.
Get the reservation and routing number for the order
SELECT SINGLE
         rsnum
         aufpl
         FROM afko
         INTO (p_pwa_e1bp2017_gm_item_create-reserv_no,
               l_aufpl)
         WHERE aufnr = p_pwa_e1bp2017_gm_item_create-orderid.
IF sy-subrc = 0.
    CALL FUNCTION 'CONVERSION_EXIT_NUMCV_INPUT'
      EXPORTING
        input = p_pwa_e1bp2017_gm_item_create-activity
      IMPORTING
        output = p_pwa_e1bp2017_gm_item_create-activity.
ENDIF.
ENDFORM.                    " get_oper
i have modifeid the incoming data,in ur case its not needed ,only first few lines until the bapi u have to see..if u have any query let me know..
Regards,
Nagaraj

How to create an inbound Idoc from an inbound IDoc in same client

How to create an inbound Idoc from an inbound IDoc in same client
Idoc will come from XI as an inbound idoc to SAP, now I have to read this inbound Idoc and split it into Several Inbound Idocs and now needs to be posted in the same client.
please let me know the procedure..
Thanks in advance,
Sagar

Hi Sagar,
Develop a cusom Z-Inbound function module, configure the Z-FM to trigger when idoc is recieved from XI. In your Z-Inbound function module split the idoc (Recieved from XI) into respective Idocs and Using MASTER_IDOC_DISTRIBUTE post the IDOCs into the same system.
Thanks & Regards

Need Code to generate Inbound Idocs

Hi friends
i have a flat file consists of delivery confirmation data
by using this i need to generate inbound idocs
i filled all the segments in idoc type /afs/delvry03 and message type whscon
can any one have the code to generate inbound idocs
please remember that here i am not using XI
thanks
Anil

Hi this is for Stand alone Programs, I hope it is useful to you.
Program Flow
The program logic contains the following blocks:
1. Provide a selection screen to allow a user to specify the various objects for which IDocs are to be generated.
2. Determine the key of the application document from the object specified in step 1.
3. Select application data from the database using the object key identified in step 2.
4. Populate control record information.
5. Populate an internal table of type EDIDD with data records for the various segments.
6. Call the ALE service layer (MASTER_IDOC_DISTRIBUTE) to create the IDocs in the database.
7. Commit work.
The program in Listing 32-2 generates the monthly report IDoc ZMREPT01, which illustrates a stand-alone outbound process.
Listing 32-2
REPORT ZARNEDI1 MESSAGE-ID ZE.
Parameters
object key (Social security number for the employee)
PARAMETERS: P_SSN LIKE ZEMPDETAIL-SSN.
message type
PARAMETERS: P_MESTYP LIKE EDMSG-MSGTYP OBLIGATORY.
destination system
PARAMETERS: P_LOGSYS LIKE TBDLST-LOGSYS.
Constants
DATA:
    segment names
        C_HEADER_SEGMENT           LIKE EDIDD-SEGNAM VALUE 'Z1EMHDR',
        C_WEEKLY_DETAILS_SEGMENT   LIKE EDIDD-SEGNAM VALUE 'Z1WKDET',
        C_CLIENT_DETAILS_SEGMENT   LIKE EDIDD-SEGNAM VALUE 'Z1CLDET',
        C_SUMMARY_SEGMENT          LIKE EDIDD-SEGNAM VALUE 'Z1SUMRY',
    idoc type
        C_MONTHLY_REPORT_IDOC_TYPE LIKE EDIDC-IDOCTP VALUE 'ZMREPT01'.
Data declarations
idoc control record
data: control_record_out like edidc.
employee header data
DATA: FS_EMPHDR_DATA LIKE Z1EMHDR.
employee weekly details data
DATA: FS_WEEKDET_DATA LIKE Z1WKDET.
client details data
DATA: FS_CLIENTDET_DATA LIKE Z1CLDET.
employee monthly summary data
DATA: FS_SUMMARY_DATA LIKE Z1SUMRY.
total hours and amount for the summary segment
DATA: TOTAL_HRS_MONTH TYPE I,
        TOTAL_AMT_MONTH TYPE I.
Database Tables
Application data tables
TABLES: ZEMPDETAIL, ZEMPWKDET.
Internal tables
DATA:
    weekly details - appplication data
        IT_WKDET LIKE ZEMPWKDET OCCURS 0 WITH HEADER LINE,
    data records
        INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE,
    communication idocs geneerated
        IT_COMM_IDOCS LIKE EDIDC OCCURS 0 WITH HEADER LINE.
Program logic
********************Select Application Data***************************
SELECT SINGLE * FROM ZEMPDETAIL WHERE SSN = P_SSN.
IF SY-SUBRC NE 0.
     MESSAGE E001 WITH P_SSN.
     EXIT.
ENDIF.
SELECT * FROM ZEMPWKDET INTO TABLE IT_WKDET WHERE SSN = P_SSN.
IF SY-SUBRC NE 0.
     MESSAGE E002 WITH P_SSN.
     EXIT.
ENDIF.
********************Build Control Record******************************
Fill control record information
CONTROL_RECORD_OUT-MESTYP = P_MESTYP.
control_record_out-idoctp = c_monthly_report_idoc_type.
control_record_out-rcvprt = 'LS'.
control_record_out-rcvprn = p_logsys.
********************Build Data Records********************************
*--Employee header--
fill the employee header information
FS_EMPHDR_DATA-LNAME = ZEMPDETAIL-LNAME.
FS_EMPHDR_DATA-FNAME = ZEMPDETAIL-FNAME.
FS_EMPHDR_DATA-SSN   = ZEMPDETAIL-SSN.
FS_EMPHDR_DATA-DOB   = ZEMPDETAIL-DOB.
fill the administrative section of the data record
INT_EDIDD-SEGNAM = C_HEADER_SEGMENT.
INT_EDIDD-SDATA = FS_EMPHDR_DATA.
append the employee header data record to the IDoc data
APPEND INT_EDIDD.
*--Employee weekly details--
LOOP AT IT_WKDET.
fill the weekly details for each week
    FS_WEEKDET_DATA-WEEKNO = IT_WKDET-WEEKNO.
    FS_WEEKDET_DATA-TOTHOURS = IT_WKDET-TOTHOURS.
    FS_WEEKDET_DATA-HRLYRATE = IT_WKDET-HRLYRATE.
add administrative information to the data record
    INT_EDIDD-SEGNAM = C_WEEKLY_DETAILS_SEGMENT.
    INT_EDIDD-SDATA = FS_WEEKDET_DATA.
append the data for the week to the IDoc data
    APPEND INT_EDIDD.
Client details of each week
    FS_CLIENTDET_DATA-CLSITE = IT_WKDET-CLSITE.
    FS_CLIENTDET_DATA-WORKDESC = IT_WKDET-WORKDESC.
add administrative information to the data record
    INT_EDIDD-SEGNAM = C_CLIENT_DETAILS_SEGMENT.
    INT_EDIDD-SDATA = FS_CLIENTDET_DATA.
append the client details for the week to the IDoc data
    APPEND INT_EDIDD.
ENDLOOP.
*--Employee monthly summary--
compute total hours and amount for the month
LOOP AT IT_WKDET.
    TOTAL_HRS_MONTH = TOTAL_HRS_MONTH + IT_WKDET-TOTHOURS.
    TOTAL_AMT_MONTH = TOTAL_AMT_MONTH + ( IT_WKDET-TOTHOURS *
                                          IT_WKDET-HRLYRATE ).
ENDLOOP.
fill the summary information
FS_SUMMARY_DATA-TOTHRS = TOTAL_HRS_MONTH.
FS_SUMMARY_DATA-TOTAMT = TOTAL_AMT_MONTH.
condense the summary record fields to remove spaces
CONDENSE FS_SUMMARY_DATA-TOTHRS.
CONDENSE FS_SUMMARY_DATA-TOTAMT.
add administrative information to the data record
INT_EDIDD-SEGNAM = C_SUMMARY_SEGMENT.
INT_EDIDD-SDATA = FS_SUMMARY_DATA.
append summary data to the IDoc data
APPEND INT_EDIDD.
*************Pass control to the ALE layer****************************
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
       EXPORTING
            master_idoc_control            = control_record_out
       TABLES
            COMMUNICATION_IDOC_CONTROL     = IT_COMM_IDOCS
            MASTER_IDOC_DATA               = INT_EDIDD
       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 NE 0.
     MESSAGE E003 WITH P_SSN.
ELSE.
     LOOP AT IT_COMM_IDOCS.
       WRITE: / 'IDoc generated', IT_COMM_IDOCS-DOCNUM.
     ENDLOOP.
     COMMIT WORK.
ENDIF.

Inbound IDOC extension

Hi,
iam working on an inbound IDOC TPSSHT01, i need to add an extrta field and segment , so i create an data element and Z segment and add the field in the segment
i have to copy the TPSSHT01 to a ZTPSSHT01 and do the IDoc extension ,
i have to copy the function module IDOC_INPUT_SHIPPL to Z_IDOC_INPUT_SHIPPL
Can any body let me know what are the steps that i have to follow to process the inbound idoc with the above requirment
Cheers,
Sai

Hi ,
      Follow this procedure .
In bound Idoc
Step 1: Create segment
a.     T.code WE31
b.     Enter a new segment type and press create button
c.     Give a short text
d.     Enter the field names say FIELD NAME : MATNR ;; DATA ELEMENT: CHAR(18)
e.     Save the segment   (zkrishseg)
Step 2: Create IDOC type
a.     T.code WE30
b.     Enter a new IDOC type name
c.     Choose the basic type and press the create button.
d.     Choose the create new option button and enter a description and press enter
e.     Place the cursor on the type name and then press create button.
f.     Enter the segment name created in step 1 and check the mandatory segment check box
g.     Enter minimum number and maximum number as 1 and press enter.
h.     Then save the IDOC type.   (zkrishtyp)
Step 3: Create message type
a.     T.code WE81
b.     Press change button.
c.     Press new entries button.
d.     Enter a message type and short text and press save button. (zkrishmsg)
Step 4: Assign message type to IDOC type.
a.     T.code WE82
b.     Press change button
c.     Press new entries button.
d.     Enter the created message type, IDOC type and version release (46B or 46C)
Step 5: Create a function module for inbound. (Z_IDOC_KRISH_INBOUND)
Step 5A: Create characteristics of inbound FM.
a.     T.code BD51
b.     Click New entries
c.     Enter the IDOC function module name and 1(individual type) in input t..
d.     Save it.
Step 6: Assignment of FM to log, message and type.
a.     T.code WE57
b.     Go for change mode and click new entries.
c.     In processing byenter FM name and enter F as type.
d.     Enter basic type (idoc type-zkrishtyp) and message type (zkrishmsg) in the respective text boxes.
e.     Choose the direction as 2 Inbound.
f.     Save the data.
Step 7. : Creation of inbound process code.
a.     T.code WE42
b.     Go to change mode and click create entries.
c.     Enter a new process code and description (zidockrish)
d.     Enter the FM name in the identification text box
e.     Choose processing with ALE service
f.     Choose processing by FM and click Save button
g.     In the next screen, select the FM name and click save button
Step 7a : Creation of inbound process code.
h.     T.code SM59
i.     Select R/3 connection and click create.
j.     Enter all system related things(for Eg. Connection type as 3, Target host as SAP04,
Description , and Logon details and save.
Step 8: Define a port
a.     T.code WE21
b.     Click on Transactional RFC and press the Create button
c.     Enter a port name and description. (ztestkrish)
d.     Choose the release type.
e.     Choose the RFC destination.
f.     To create RFC destinationgo to SPRO and search RFC destinationand create.
g.     Save the data.
Step 9. Define logical system
a.     T.code SALE
b.     Click down the sending and receiving systems
c.     Click down the logical systems
d.     Choose Define logical system.
e.     Go for new entries.
f.     Enter a new name and description and save it. (zkrishlog)
Step 10. Create partner profile
a.     T.code WE20
b.     Choose partner type LS and click create.
c.     Enter the logical system name in partner number
d.     Then Save . Here Type is US.
e.     click + icon(create inbound parameter) in the bottom. Note: Two table control subscreens will appear. One for inbound and the other for outbound. Click + icon in inbound area.
f.     Enter the message type, process code and save the data.
Step 11. Checking the Idoc
a.     T.code WE19,
b.     Choose radio Basic type , enter the type name(zkrishtyp) and press execute button.
c.     Click on EDIDC Number.
d.     Enter partner Number, Partner type, Port Number for sender and recipient ( data remains same here for sender and recipient)
e.     Enter Message type and press ENTER.
f.     Click on empty space corresponding to SEGMENT name and enter Paarameters like MATNR, WERKS and CHARG etc.
g.     Click standard inbound properties here and press enter see the result.
h.     T.code WE02
i.     Enter IDOC number press ENTER see the status.
Function Module in Inbound
     Import Parameters
     INPUT_METHOD           LIKE BDWFAP_PAR-INPU              Inbound method for the IDoc inb
MASS_PROCESSING     LIKE BDWFAP_PAR-MASS            Flag: Mass processing
Export Parameters
WORKFLOW_RESULT     LIKE      BDWF_PARAM-RESULT          Final value of method
APPLICATION_VARIABLELIKE      BDWF_PARAM-APPL_VAR Variable to be used by
IN_UPDATE_TASK      LIKE      BDWFAP_PAR-UPDATETASK       Flag: Application has
CALL_TRANSACTION_DONLIKE      BDWFAP_PAR-CALLTRANS        Flag: Application
tables
     IDOC_CONTRL         LIKE      EDIDC                       Control record (IDoc)
IDOC_DATA              LIKE      EDIDD                       Data record (IDoc)
IDOC_STATUS          LIKE      BDIDOCSTAT           ALE IDoc status (subset of al
RETURN_VARIABLES    LIKE      BDWFRETVAR    Assignment of IDoc or documen
SERIALIZATION_INFO LIKE      BDI_SER                Serialization objects for one
     Source code
FUNCTION ZASHOKMODULE.
""Local interface:
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
data: begin of w_data occurs 0.
       include structure edidd.
data: end of w_data.
data: wa_data like ZASH1.
data : i_data like standard table of wa_data initial size 0.
*tables : zhemal1.
data : begin of wa_zhemal1.
        include structure zhemal1.
data : end of wa_zhemal1.
data : i_ZHEMal1 like standard table of wa_ZHEMal1 initial size 0.
read table idoc_data with key SEGNAM = 'ZASH1'.
loop at IDOC_DATA into W_DATA where segnam = 'ZASH1'.
WA_DATA = W_DATA-SDATA.
wa_data = w_data-sdata.
append wa_data to i_data.
endloop.
MOVE IDOC_DATA-DOCNUM TO IDOC_STATUS-DOCNUM.
    IDOC_STATUS-MSGID = 'ZABC'.
    IDOC_STATUS-STATUS = 53.
    IDOC_STATUS-MSGTY = 'S'.
    IDOC_STATUS-MSGNO = '001'.
    APPEND IDOC_STATUS.
LOOP AT i_data into wa_data.
wa_ZHEMal1-VBELN = wa_data-VBELN.
wa_ZHEMal1-POSNR = wa_data-POSNR.
wa_ZHEMal1-MATNR = wa_data-MATNR.
wa_ZHEMal1-MATWA = wa_data-MATWA.
wa_ZHEMal1-MATKL = wa_data-MATKL.
append wa_ZHEMal1 to i_ZHEMal1.
insert ZHEMal1 from table i_ZHEMal1 accepting duplicate keys .
ENDLOOP.
ENDFUNCTION.
For Out bond Steps are
1.     Create segment
2.     Create Type
3.     Create Message Type
4.     Assign message Type to Idoc Type.
5.     Create Port
6.     Define Logical systems.
7.     Define Partner profile.
8.     Create a Report program.
Report program Out bond
REPORT ZASH1 .
              Outbound standalone idoc creation                      *
Program Name : Y_VENMAST_OUTBOUND_STANDALONE                         *
Description : Outbound standalone idoc creation for training        *
               to Unilever offshore team members                     *
Created by   : Satyam Computer Services Ltd.                         *
Created on   : 04.01.2002                                            *
                       Modification Log                              *
Developer           Date            Transport #   Details            *
Subramony         04.01.2002                                         *
Tables Declaration                                                   *
TABLES : zhemal1.
Internal table declaration                                           *
data : i_zhem1 Like standard table of zhem1 with header line.
data : control_record_out like edidc.
*data: p type p decimals 2,
     c(10) type c.
start-of-selection.
    p = '3.14'.
    c = p.
    overlay c with '0000000000000'.
write c.
DATA : BEGIN OF I_EDIDD OCCURS 0.
        INCLUDE STRUCTURE EDIDD.
DATA : END OF I_EDIDD.
DATA : BEGIN OF I_EDIDC OCCURS 0.
        INCLUDE STRUCTURE EDIDC.
DATA : END OF I_EDIDC.
DATA : BEGIN OF I_zhemal1 OCCURS 0,
            VBELN LIKE zhemal1-VBELN,
            POSNR LIKE zhemal1-POSNR,
            MATNR LIKE zhemal1-MATNR,
            MATWA LIKE zhemal1-MATWA,
            MATKL LIKE zhemal1-MATKL,
       END OF I_zhemal1.
SELECT-OPTIONS : S_vbeln FOR zhemal1-vbeln .
START-OF-SELECTION.
PERFORM F_GET_zhemal1.
END-OF-SELECTION.
Building Control record
CONTROL_RECORD_OUT-MESTYP = 'ZASH1'.
CONTROL_RECORD_OUT-IDOCTP = 'ZASH1'.
CONTROL_RECORD_OUT-RCVPRT = 'LS'.
CONTROL_RECORD_OUT-RCVPRN = 'ZASH1'.
CONTROL_RECORD_OUT-sndPRT = 'LS'.
CONTROL_RECORD_OUT-sndPRN = 'ZASH1'.
PERFORM F_PROCESS_OUTPUT.
*PERFORM F_FILL_EDIDD.
PERFORM F_CREATE_IDOC.
Form F_GET_Y1COTU110                                                *
FORM F_GET_zhemal1.
SELECT VBELN POSNR MATNR MATWA MATKL
         FROM ZHEMAL1
         INTO TABLE I_ZHEMAL1
         WHERE VBELN IN S_VBELN.
ENDFORM.                    " F_GET_zhemal1
Form f_process_output                                                *
FORM F_PROCESS_OUTPUT.
LOOP AT I_zhemal1.
I_zhem1-VBELN = I_zhemal1-VBELN.
I_zhem1-POSNR = I_zhemal1-POSNR.
I_zhem1-MATNR = I_zhemal1-MATNR.
I_zhem1-MATWA = I_zhemal1-MATWA.
I_zhem1-MATKL = I_zhemal1-MATKL.
i_edidd-segnam = 'ZASH1'.
    i_edidd-sdata = I_zhem1.
    append i_edidd.
    clear i_edidd.
ENDLOOP.
ENDFORM.                    " f_process_output
Form f_create_edidc                                                 *
FORM F_CREATE_IDOC.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
       EXPORTING
            MASTER_IDOC_CONTROL            = CONTROL_RECORD_OUT
       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.
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_EDIDC.
      WRITE :/ 'IDoc Generated :' , I_EDIDC-DOCNUM.
    ENDLOOP.
    COMMIT WORK.
ENDIF.
ENDFORM.                               " f_create_idoc
Please reward if useful.

Create Article Master through inbound IDoc (Normal Flow of Inbound IDOC)

Hi All,
I am new to Inboud IDoc.
I have a file on application server. In program (SE38), I read that file through "open data set"..." close data set.". now the file is in internal table. where should i pass that data (i mean in which structures). and what should i do to create an article in SAP System. I mean what should i write in program ? which Fn. module called ? etc..
My requirement is that using Inbound IDoc ARTMAS05 post the data from application server.
I am aware of all ALE configuration and all WE30, WE31, WE81, WE82.....
could anyone brief the basic steps of inbound IDOC ARTMAS05 and INFREC01.
please help me out.
valuable contribution is appreciated.
Thanks & Regards,

for this you need to write a program .
once you get the data form file to Internal table. then
pass your internal table data to idoc control and idoc dta
like pass all segemnts data then pass all segments data to this FM
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
      EXPORTING
        master_idoc_control            = wa_edidc
      TABLES
        communication_idoc_control     = gt_edidc
        master_idoc_data               = gt_edidd

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Creation of Sales Order and Service Contract from Inbound IDOC

Hi Experts,
My requirement is to create a Sales Order as well as a Service Contract from one Inbound IDOC. I am getting the Inbound IDOC from a third Party. The message type is ORDERS and Basic Type is ORDERS02. How ever i am using an extension type IDOC which carries all the required data for Sales Order and Service Contract. My requirement is like, to create a Sales Order first.
I have created a Z FM which is attached to the Process Code and subsequently to the message type. Inside the FM i an calling FM 'IDOC_INPUT_ORDERS' for creation of Sales Order. After that i am changing the IDOC data for the Document Type. I am changing the document type which is responsible for Contract Creation.
Then I am again calling the FM 'IDOC_INPUT_ORDERS' for creation of Contract with the help of IDOC data. But here the Contract is not getting created. It's getting failed during the Batch input session.
I need to solve this problem as soon as possible. Please help me. If there are any other options also please share.
Thanks in Advance.
Regards,
Priyabrata

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

Creation of Service Contract from Inbound IDOC

Hi Experts,
I am using Inbound IDOC type ORDERS02 with message type ORDERS for creation of Sales Order. Now my requirement is like to create a Service Contract from that Inbound IDOC. The IDOC type contains all the data require to create a Service Contract. The scenario is like, after creation of Sales Order it will check for the corresponding Service Contract exits or not by querying on a Z table which contains all those entries.
So my idea is to create a Z Program, in which it will check for the Service Contract and will create the same by reprocessing the same IDOC or by calling some Function Module. Please suggest how shall i proceed to create a Service Contract.
Is there any way to reprocess the IDOC or to collect the Data from the IDOC segments pass them to a FM which is responsible for creation of Inbound IDOC. Please suggest if this is feasible.
Thanks in Advance.
Regards,
Priyabrata.

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

How to read file from prsntn server in Inbound idoc FM.

Hi Experts,
I am new to idoc.
I have requirment that i need to read a file from presentation and application server and put in inbound idoc FM.Idoc will be processed in batch.
How can i put selection screen in FM and read the file?or how can i proceed with the solution?
Please help..
Umesh

Hi Umesh,
My understanding on your requirement is to read a file from pres. server and pass the data to an IDoc function module. Am I correct?
If this is the case then you can create a report which picks up the file from pres. server and then read data from the file and pass it to the parameters of the required function module.
Hope this helps.
Regards,
-Sandeep

MASTER_IDOC_DISTRIBUTE inbound idocs?

Similar Messages

Maybe you are looking for