Inbound Idoc port ???

Hi All,
I am working on proxy to IDoc_AAE scenario. Can anybody tell me from where inbound Idoc will take port?? I have imported inbound parameters in respective partner profile, but not sure from where this idoc is picking port value. Kindly suggest.
Thanks & Regards,
Rashmi Joshi

Hello,
If you already know the port no , you can do that by filling the EDIDC Segment of the Idoc .
Else the Idoc will be sent via the RFC destination configured in the rcver idoc channel
and during the TRFC call system will check for the existing partner profile (the entries set up in we21).
hope this helps .
rgds
Kishore

Similar Messages

Inbound IDOC receiver port not getting filled in

Hi All,
I checked the WE20 configuration and it is fine. Just wanted to check if there is any other sap configuration which might be missing.
The IDOC is coming from a web server and they confirmed that they are filling the receiver port information while sending, but in the IDOC that we receive in SAP the receiver port is coming as blank.
Any pointers will be appreciated.
Thanks,
Anil

Hello Anil,
When they say they are filling receiver port that means they filling EDIDC-RCVPRT, please note with out receiver port you will not be able to receive the Idoc.
It means this value might be cleared somewhere in SAP. may be user exit or BADI or enhancement. what you can do is try to create inbound idocs by populating receiver port using WE19 and check whether the created idoc contains this value or not.By doing the you can get an idea where this value is disappered.

Port values for inbound IDoc processing

We're using GIS to send IDocs into SAP, and are switching over to using file-based rather than tRFC due to some file size issues.
Can someone clarify for me why EDI_DATA_INCOMING needs a file port for loading (makes sense to me), but the receiver port (RCVPOR) value in the IDoc control record has to be SAP<sid> for the IDoc to load properly? I would expect that having a receiver port equal to the file port that we're receiving files via would be correct.
Thanks,
James

Hi James,
Why does EDI_DATA_INCOMING need a file port for loading?
The file port is used to determine the file type of the input file whether is flat or XML file.
If the file type is XML, then FM EDI_DATA_INCOMING will call FM IDOC_XML_FROM_FILE to process inbound IDoc file. Otherwise, it will call FM IDOC_INBOUND_FROM_FILE for processing the IDoc input flat file.
Hope this will help.
Regards,
Ferry Lianto

Inbound Idoc with T-code: BORGR ( Inbound delivery create) EDI cannection

Dear all,
Kindly help me to create inbound delivery with BORGR transaction.
Here the we have to create the inbound delivery in the system with the help of vendor number and material without using Scheduling agreement number in BORGR
Please suggest the processing code and the function module required for the BORGR document posting.
I have done the following steps u2026but not able to post the dummy idoc through WE19 .
1.     Use standard message Type DESADV (T code: WE81).
2.     Use standard IDOC type DELVRY05 (T code: WE30).
3.     Assign message type to IDOC Type ( Tcode: WE82).Message Type:-DESADV, Basic Type:-DELVRY05,Release 700
4.     Use standard assignment of process code DELS with the message type DESADV ( Tcode: WE42)
5.     Inbound Function Module : IDOC_INPUT_DESADV1 ( T code : WE57)
6.     Define Port type File (Tcode: WE21) Port u2013 EDI_ASN Inbound Delivery.
7.      Define Partner Profile (Tcode: WE20) Inbound Parameters.
8.     Enhancement can be done in inbound IDOC as per the business requirement. Business has confirmed Field name wise Inbound IDOC data which will be received from vendor and all fields are available in the standard IDOC type DELVRY05.
Please help if anything more required for posting dummy idoc .
Thanks and regards,
koshti

Hi Dick,
just one additional hint as we had recently such problems :
It my happen that DESADV creates an inb.del <b>w/o</b> packing the HUs (idoc status is 'yellow' instead of 'red'). To avoid this OSS #912470 is the solution.
Kind Regards
Kay

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear:   g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'.   "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'.              "Direction
* Receiver
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
    g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'.             "Partner type
g_idoc_control_record-rcvpfc = ''.               "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'.             "Partner type
g_idoc_control_record-sndpfc = ''.               "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam               = 'E1BPACHE09'.
g_edidd-segnum               = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
    exporting
      pi_idoc_control_rec_40              = g_idoc_control_record
*     PI_DO_COMMIT                        = 'X'
*   IMPORTING
*     PE_IDOC_NUMBER                      =
*     PE_ERROR_PRIOR_TO_APPLICATION       =
    tables
      pt_idoc_data_records_40             = g_edidd
    exceptions
      idoc_not_saved                      = 1
      others                              = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
    in background task as separate unit
    tables
      idoc_control_rec_40 = g_idoc_control_record
      idoc_data_rec_40    = g_edidd.
commit work.
endif.
write: / 'Well done!'.

Stop Inbound IDOC's from being created

I want to stop inbound IDOC's for a particular partner (type LS) from being created in our R/3 system. Is there a way to do this? I am aware these can be stopped in the middleware, but this is not possible in our case. I am also aware that I can stop these IDOC's from being processed via the partner profile, however, there will be a huge number of useless IDOC's that will be created in our system and I want to avoid that.
Hence, I do not want the inbound IDOC's to be created in the first place even though they are transmitted to SAP. Is this possible?
Any inputs will be highly appreciated.
Thanks,
Raghu.

Hi Satwik,
Choose Idoc in WE02.
Get port name, Then in WE21 get RFC name.
Go to transaction SMQS - Here we can block this RFC instead of blocking the queue.
Thanks,
Anil

Inbound idoc

Hi,
here i am picking the file from APPS and also inbound IDOC creation.
just anyone check my code and give some suggestions in the areas of impovemet technically.
thanks
report znsd007.
*tables : zih001, zid001.
tables: zstbm_lots, zstbm_stages, zibmordertype.
data: t_zstbmlot like zstbm_lots occurs 0 with header line,
      t_zstbmstage like zstbm_stages occurs 0 with header line.
parameters :
   fromdir    like     rsmrgstr-path lower case default
'/apps/MQBridge/idocmsgs/',
   fromfile   like rsmrgstr-name lower case default '*.txt',
   todir      like rsmrgstr-path lower case default
'/apps/MQBridge/idoctemp/',
   tofile     like edi_path-pthnam lower case no-display,
   procdir    like rsmrgstr-path lower case default
'/apps/MQBridge/idocproc/',
   procfile   like edi_path-pthnam lower case no-display,
   toport     like edipo-port no-display.
constants: c_tst(7) value 'IBM_TST',
            c_bi(6) value 'IBM_BI',
            c_mrk(7) value 'IBM_MRK',
            c_sbt(7) value 'IBM_SBT'.
data: w_tst(1) type c,
      w_bi(1) type c,
      w_mrk(1) type c,
      w_sbt(1) type c,
      w_err(1) type c,
      w_processcd(20) type c.
data :
file_list     like     rsfillst occurs 100 with header line,
pattern     like     rsmrgstr-name,
tmpfile(128),
begin of in1 occurs 100,
dir(128),
file(128),
data(63000) occurs 0,
data(1063) occurs 0,
end of in1,
str(63000),
*str(1063),
str2 like str,
*outfile(63000) occurs 100 with header line,
*outfile(128),
crtl like edi_dc40,
*counter type i,
segment like edi_dd40-segnam,
segment_no(6) type n,
data like edi_dd40-sdata,
productid_ecid(25),
edidd40 like edi_dd40.
field-symbols : <fs2>,<fs>.
data:   messtab like bdcmsgcoll occurs 0 with header line.
start-of-selection.
break-point.
perform getfile_list tables file_list using fromdir fromfile.
delete file_list where type = 'directory'.
toport = 'FILE'.
loop at file_list.
    perform getfile tables in1 using file_list.
endloop.
sort in1 by dir file.
check not in1[] is initial.
loop at in1.
    at new file.
      concatenate todir '/' in1-file into tofile.
      replace '//' with '/' into tofile.
      condense tofile no-gaps.
      open dataset tofile for output in text mode encoding default.
      if sy-subrc ne 0.
        message e168(j4) with tofile.
      endif.
Copy the populated dataset to be saved into a processed directory
      concatenate procdir '/' in1-file into procfile.
      replace '//' with '/' into procfile.
      condense procfile no-gaps.
      open dataset procfile for output in text mode encoding default.
      if sy-subrc ne 0.
        message e168(j4) with procfile.
      endif.
      clear : edidd40, crtl.
      crtl-tabnam     = 'EDI_DC40'.
      crtl-mandt      = sy-mandt.
      crtl-docrel     = '620'.
      crtl-direct     = '02'.
      concatenate 'SAP' sy-sysid into crtl-rcvpor.
      crtl-rcvprt     = 'LS'.
      crtl-rcvprn     = 'SSD_PN0001'.
      crtl-mestyp     = 'ZCPAOC'.
      crtl-idoctyp    = 'ZCPAOC01'.
      crtl-sndpor     = 'SSD0000001'.
      crtl-sndprt     = 'LS'.
      crtl-sndprn     = 'SSD_PN0001'.
      transfer crtl to : procfile.
      clear segment_no.
    endat.
    refresh t_zstbmlot.
    refresh t_zstbmstage.
    loop at in1-data into str.
      clear edidd40.
      edidd40-mandt = sy-mandt.
      check not str is initial.
      search str for ','.
      if sy-subrc = 0.
        segment = str+0(sy-fdpos).
        sy-fdpos = sy-fdpos + 1.
        data = str+sy-fdpos.
        case segment.
          when 'ZSTBM_LOT'.
            clear t_zstbmlot.
            split data at ',' into t_zstbmlot-aufnr
                                   t_zstbmlot-ordertype
                                   t_zstbmlot-plant
                                   t_zstbmlot-productid
                                   t_zstbmlot-ec
                                   t_zstbmlot-lotlabel
                                   t_zstbmlot-other_lot_label1
                                   t_zstbmlot-orderqty
                                   t_zstbmlot-customercd
                                   t_zstbmlot-srcevendor
                                   t_zstbmlot-waferid
                                   t_zstbmlot-lotowner
                                   t_zstbmlot-lottype
                                   t_zstbmlot-prty
                                   t_zstbmlot-planstart
                                   t_zstbmlot-planfinish
                                   t_zstbmlot-linecodejc
                                   t_zstbmlot-qualitycod
                                   t_zstbmlot-poi
                                   t_zstbmlot-poi_text
                                   t_zstbmlot-cot
                                   t_zstbmlot-cot_text
                                   t_zstbmlot-lotprodtyp
                                   t_zstbmlot-productcd
                                   t_zstbmlot-familycd
                                   t_zstbmlot-lot_cmmnt
                                   t_zstbmlot-devassem
                                   t_zstbmlot-devassemtx
                                   t_zstbmlot-numdevices
                                   t_zstbmlot-date_of_mfg
                                   t_zstbmlot-pur_order
                                   t_zstbmlot-process_cd.
            append t_zstbmlot.
            edidd40-segnam = 'ZSTBM_LOT'.
            edidd40-hlevel = '2'.
            segment_no = segment_no + 1.
            edidd40-segnum = segment_no.
            edidd40-sdata = t_zstbmlot.
          when 'ZSTBM_STAGE'.
            clear t_zstbmstage.
           split data at ',' into t_zstbmstage-stage.
            move data to t_zstbmstage-stage.
            append t_zstbmstage.
            edidd40-segnam = 'ZSTBM_STAGE'.
            edidd40-hlevel = '3'.
            edidd40-psgnum = segment_no.
            edidd40-sdata = t_zstbmstage.
        endcase.
        transfer edidd40 to : procfile.
      endif.
    endloop.
    t_zstbmlot-date_of_mfg = t_zstbmlot-date_of_mfg(8).
Determine the order type here using t_zstbmstage and t_zstbmlot
and update order type int t_zstbmlot.
    clear w_tst. clear w_bi. clear w_mrk. clear w_sbt. clear w_err.
    clear w_processcd.
    loop at t_zstbmstage.
      if t_zstbmstage-stage = c_tst.
        w_tst = 'X'.
      elseif t_zstbmstage-stage = c_bi.
        w_bi = 'X'.
      elseif t_zstbmstage-stage = c_mrk.
        w_mrk = 'X'.
      elseif t_zstbmstage-stage = c_sbt.
        w_sbt = 'X'.
      endif.
    endloop.
    if t_zstbmlot-process_cd = 'SubStock Release' or
       t_zstbmlot-process_cd = 'SUBSTOCK RELEASE'.
      w_processcd = 'SUBSTOCK RELEASE'.
    endif.
    select single * from zibmordertype
           into zibmordertype where
           ibm_tst = w_tst and
           ibm_bi = w_bi and
           ibm_mrk = w_mrk and
           ibm_sbt = w_sbt and
           processcd = w_processcd.
    if sy-subrc = 0.
      t_zstbmlot-ordertype = zibmordertype-ordertype.
    else.
      write: 'Order type not determined for lot label:',
              t_zstbmlot-lotlabel.
    endif.
Put into zih001 to create idoc
    clear : edidd40, crtl.
    crtl-tabnam     = 'EDI_DC40'.
    crtl-mandt      = sy-mandt.
    crtl-docrel     = '620'.
    crtl-direct     = '02'.
    concatenate 'SAP' sy-sysid into crtl-rcvpor.
    crtl-rcvprt     = 'LS'.
    crtl-rcvprn     = 'SSD_PN0001'.
    crtl-mestyp     = 'ZCPAOC'.
    crtl-idoctyp    = 'ZCPAOC01'.
    crtl-sndpor     = 'SSD0000001'.
    crtl-sndprt     = 'LS'.
    crtl-sndprn     = 'SSD_PN0001'.
    transfer crtl to : tofile.
    clear : edidd40.
    edidd40-segnam = 'ZIH001'.
    edidd40-mandt = sy-mandt.
    edidd40-hlevel = 1.
    edidd40-sdata = t_zstbmlot.
    transfer edidd40 to : tofile.
    check not in1-data[] is initial.
    at end of file.
      close dataset : procfile, tofile.
      call function 'EDI_DATA_INCOMING'
        EXPORTING
          pathname = tofile
          port     = toport.
      check sy-subrc = 0.
    Remove file from idocmsgs directory after idoc processing
      clear tmpfile.
      concatenate in1-dir '/' in1-file into tmpfile.
      replace '//' with '/' into tmpfile.
      condense tmpfile no-gaps.
      delete dataset tmpfile.
    endat.
endloop.
form getfile_list tables intab1 structure rsfillst using inval1 inval2 .
call function 'SUBST_GET_FILE_LIST'
    exporting
      dirname            = inval1
      filenm             = ''
      pattern            = inval2
    tables
      file_list          = intab1
EXCEPTIONS
ACCESS_ERROR       = 1
OTHERS             = 2
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
endform.                    "getfile_list
*&      Form getfile
      text
     -->P_FIELD_LIST text
form getfile tables intab1 structure in1
              using    inval structure file_list.
data : xfile(128).
clear xfile.
concatenate inval-dirname '/' inval-name into xfile.
replace '//' with '/' into xfile.
open dataset xfile for input message messtab
                          in text mode encoding default.
check sy-subrc = 0.
clear : str, intab1. refresh intab1-data.
do.
replace ALL OCCURRENCES OF
        cl_abap_char_utilities=>horizontal_tab
                   in xfile with space.
replace all occurrences of '#' in xfile with space.
replace all occurrences of ':' in xfile with space.
replace all occurrences of '_' in xfile with space.
    read dataset xfile into str.
replace all occurrences of '#' in str with space.
replace all occurrences of ':' in str with space.
replace all occurrences of '_' in str with space.
    if sy-subrc <> 0.
      exit.
    endif.
    intab1-file = inval-name.
    intab1-dir = inval-dirname.
    append str to intab1-data.
enddo.
if not intab1-data[] is initial.
    append intab1.
endif.
close dataset xfile.
endform.                    " getfile
form showdata changing inval indat.
data : xxtab like sval occurs 100 with header line,
           ff0(100), ff1(30), ff2(30), yesno.
inval = indat.
do.
    assign component sy-index of structure inval to <fs>.
      Z1STB_HDR TO <FS>.
    if sy-subrc <> 0. exit. endif.
    describe field <fs> help-id ff0.
    split ff0 at '-' into ff1 ff2.
    clear xxtab.
    xxtab-tabname = ff1. xxtab-fieldname = ff2. xxtab-value = <fs>.
    append xxtab.
enddo.
call function 'POPUP_GET_VALUES_USER_HELP'
    EXPORTING
      popup_title     = 'Enter Order Information'
    TABLES
      fields          = xxtab
    EXCEPTIONS
      error_in_fields = 1
      others          = 2.
if sy-subrc <> 0 .
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
endform.                    "showdata

hi
i can see views are increasing inmy post. bu ti am not unable to see any when i enter. where are the views stored for this thread. now i am just clicking the reply to this thread.
please let me know where can i see th eviews.
thanks

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Testing of an inbound idoc.

hi experts,
i have to create an inbound interface for processing message order/ordchg.I have a .txt data file .how do i test my inbound interface so that the data in the text file is passed onto the inbound idoc?
Valuable help will be rewarded.
Regards,
Shrita.

Hi shrita sharma
1)Generating Idoc as a flat File on the outbound.
2)Uploading File as IDoc in the Inbound System
1) Send an outbound IDOC data(ORDERS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
Good Luck and Reward me for the same ..!!
Thanks
Ashok

SM58 - IDoc adapter inbound: IDoc data record table contains no entries

Trying to send Idocs from SAP ECC6.0 via PI 7.0 up until 2 days ago there was no problem.
Since yesterday, only one specific type of Idoc does not make it into XI (PI). In the Idoc monitor (WE02) the idocs that were created gives status 3 which is good. But all Idocs of that specific type (ZRESCR01) does not go to XI. I can only find them bakc in SM58 where it gives the following message:
IDoc adapter inbound: IDoc data record table contains no entries
I have checked SAP notes 1157385 and also 940313, none of them gives me any more insight into this error. I have also checked all the configuration in WE20, SM59, and in XI (repository and directory) and in XI IDX1, IDX2 but could not find anything that would cause this. I can also not think of anything that changed since 2 days ago.
Please point me in the right direction.

hi,
i think in sm 58 u can find entries only when there is some failure in login credential .
if there is change in IDoc structure than you have to reimport the idoc metadata defination at IDX2.otherwise not requird.
please check the logical system name pointing to the your requird target system....
please also verify thet your port should not be blocked.
pls find the link it may help
Monitoring the IDOC Adapter in XI/PI using IDX5
regards,
navneet

How to create Inbound Idoc from XML file-Need help urgently

Hi,
can any one tell how to create inbound Idoc from XML file.
we have xml file in application server Ex. /usr/INT/SMS/PAYTEXT.xml' we want to generate inbound idoc from this file.we are successfully able to generate outbound XML file from outbound Idoc by using the XML port. But not able to generate idoc from XML file by using we19 or we16.
Please let me know the process to trigger inbound Idoc with out using XI and any other components.
Thanks in advance
Dora Reddy

Hi .. Did either of you get a result on this?
My question is the same really .. I am testing with WE19 and it seems SAP cannot accept an XML inbound file as standard.
I see lots of mention of using a Function Module.
Am I correct in saying therefore that ABAP development is required to create a program to run the FM and process the idoc?
Or is there something tht can be done with Standard SAP?
Thanks
Lee

How to Test, Inbound idoc ,with out the Sender System, using a Text File

Hi Guru's .
we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
on the same client.
we wanted to test this idoc with text file from our local machine.
Can anyone give us detail steps.like how to create File layout
with Segment name,and values for the fields.how to pass this file to the system.
Thanks in advance.

Hi Aparna.
My requirement is to test the idoc with Inbound File.
Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
when i am trying to do this syst complaing about
Partner Profile not available, and some times
port not available. and some times with
'No further processing defined'.
but i maintained part profiles and port perfectly.
Can you help me in testing with test 'File' port.

RCVPOR is missing the Inbound IDoc

Hi all,
I am getting IDoc from the XI with the status code 56.
I found that receipt port is missing in the control record.
If I use sender partner type as LS, it is working fine. When I use the sender partner type as KU IDocs are not getting posted successfully, the port for the recipient information in the control record of the inbound IDoc is empty and all other filled are filled.
Any suggestions please
Thank you
Regards
Harsha

Dear Harsha,
can you explain how you solved the issue - I am experiencing exactly the same problem. I am receiving the same Message type from several other systems (not LI, but LS), and we are receiving other message types for the same partner. -> in all other cases the RCVPOR is filled correctly.
We are using webMethods and not XI, the RCVPOR is sent correctly by the middleware.
brg Karl

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

Inbound IDOC basic type HRMD_A07: Why no validation available?

I am using a standard inbound IDOC basic type HRMD_A07 to update employee master data (IT0000 & IT0001). However, i found out that this IDOC just directly updates to the infotypes without any validation. For example, i provide an invalid company code (BUKRS) and personnel area (WERKS), the IDOC still updates into database without any proper validation.
Filled the following fields in the IDOC segments:
E1PLOGI
plvar=01, otype=P, objid=00000001, opera=I
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0000, begda=20120101, endda=99991231
E1P0000
pernr=00000001, infty=0000, endda=99991231, begda=20120101, massn=01, massg=01, stat1=3, stat2=3
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0001, begda=20120101, endda=99991231
E1P0001
pernr=00000001, infty=0001, endda=99991231, begda=20120101, bukrs=XXXX, werks=XXXX, persg=1, persk=EC, abkrs=99, plans=00000111, otype=S
Please help me out in case I am missing something. Thanks.

Additional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel

Inbound Idoc port ???

Similar Messages

Maybe you are looking for