Receiver port missing in inbound idoc

Hi All,
I am posting idocs from XI to R/3. All the ALE settings have been done correctly. Idocs were being posted to R/3 successfully, however suddenly the idocs started failing in R/3 with error: EDI: Partner profile inbound not available
When i checked the control record for the errored idocs i found that the receiver port is missing. I am not sure why this is happening as in the idoc adapter we have provided this and also the idocs were being posted successfully with the same setting.
Pls help to find the root cause for this problem.
Further what would be the best way to reprocess these failed idocs? The number is huge around - 30,000 hence manual processing through we19 is not possible. Also BD87 cannot be used as i need to edit the idoc to add the receiver port information before reprocessing.
Kindly suggest. Any help in this regards would be welcome.
Thanks
Anand Chavan

hi
Go thru the below blogs
check the partner profile settings
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/frameset.htm
Idocu2019s not posted in the receiver SAP Systemsu2026.
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
Troubleshooting File-to-IDOC Scenario in XI.
Troubleshooting File-to-IDOC Scenario in XI.
reward points if helpfull
regards
kummari

Similar Messages

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

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

Message variant is missing in INBOUND IDOC.

hi,
Any one can help on this issue?
The sender has confirmed that message variant was filled in outgoing file.
However, When we received this Inbound IDOC, the message variant is blank.
I still am confused by two questions:
1. The function module which insert record into table EDIDC and EDIDD, is same as the function module which post this IDOC to sap module(normally we maintained it in WE57)
2. We normally need to maintained in WE57, but also need create one processing code, what is relationship between WE57 and processing code(WE42)

Hi,
Message Type/Message Variant needs to be maintained in WE20 ( Partner Profiles). In case of inbound IDOC ( receiving the data other systems) Data processing/posting will happens via function module. the function module will attach to the process code.
Process Code : The IDoc interface uses the process code to find the business process which controls the conversion of the IDoc into the SAP document.
The Process code will assign to the function module in WE42, the same function module will assign to the Message type and Idoc type in WE57
In a short summary, The Function module required to post the Idoc/update the data in SAP. However the Function module should process specific to the Message type and Idoc type only. It means the settings is required to identrify the correct function module to process the Inbound Idocs.
Whenever there is a problem with ALE setting the message 64 will trigger, it means the IDOC is ready to transfer to the application ( process through FM ).
Thanks,
Kiran.

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

** Inbound IDoc - One field is missing but it is displayed in SXI_MONITOR

Hi Friends,
We have developed IDoc to IDoc scenario. Source IDoc is sent from 3rd party system. Target is an Z IDoc (Replica of VEHCLE01 IDoc).
When we test the source IDoc XML from RWB, the message processed successfully in SXI_MONITOR and target IDoc is also created in backend SAP system. But, the problem is that, in target payload there are 5 fields. But, in the physical idoc created in SAP system has only 4 fields. The last field is missing.
Since it is inbound IDoc, I deleted the IDoc meta data in IDX2 txn, and reimported again the Z IDoc. But, again the same problem is coming. i.e one field is missing in inbound IDoc. But, in the receiver payload, that field is there with value.
Kindly clarify, friends.
Kind Regards,
Jegathees P.

HI,
If that field is missing for first time in R3 means(ie Receiver system, Idoc posting in we02) , then
XI side:
1. u have check whether that field is existing in Target Interface,Target Message in Interface Mapping
2. Make sure that u have mapped that field in Message Mapping.
R3 (receiver side)
1. Plz check we30 , whether that field is there for that ZIdoc structure
2. Take the same Idoc which got posted , test in we19 whether that Idoc getting posted with that field or not?
check whether ur Idoc structure is activated in XI
Thanks
Praba

AEDTM + UNAME not filled via HRMD_A inbound idoc

Sorry if this is the wrong forum but I couldn't find any forum related to IDocs.
I have an inbound idoc:
message type: HRMD_A
basic type: ZHRMD_A0701
Processing the idoc is working, however, AEDTM and UNAME isn't filled (the fileds are empty). I would assume that those fields are filled automatically with sy-datum and sy-uname. I did some debugging and found the corresponding INSERT:
IDOC_INPUT_HRMD
- IDOC_PROCESS_HRMD
- RH_IDOC_OBJECTS_SAVE
    - inbound_objects_block
      - RH_CREATE_INFTY_PA_PB
        - SAVE_PA_PB_INFTY
          - insert_pa_pb_objects
            INSERT (dbname) FROM <f_prel_db>.
AEDTM and UNAME are emtpy in <f_prel_db>. Any idea why? Is this a known issue?

HR inbound idocs actually do not override change date / time (aedtm, uname) with date/ user id of the user who processes the inbound idoc. These info should automatically be populated in the oubound idocs as is from sending SAP system.
I guess the reason being is this is meant to replicate data (with all original info from sending system) to receiving system. If you notice in the receiving system, when HR inbound idocs are processed, change pointers are not recorded.
Therefore, if the inbound idcocs are not senf from SAP, these info would need to be populated when outbound idocs are created. Otherwise, you may have to look at inbound user-exit to see if these fields can be populated in the idocs segments.

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.

"Receiver port not valid in control record"...idoc error

Hi,
The new materials are sent to SAP via a text file which is placed in the application server which EDI uses to populate the Idoc segments and creates the material master.
Recently we upgraded from SAP 4.6 C to ERP 5.0.
After upgrading we are getting a message as Port(HPLED) invalid in control record.
I get an error message as "receiver port HPLED not valid in control record"...
It is not able to find the receiver port & hence cannot create the MM.
We checked all the config and compared with Test and production and we could not find any noticable change.
Did anyone come across any infor on this?
Your valubale reply is really very important for me.
Pls reply.
Regards,
Pri

Hey Ramesh,
I've already done the WE57 setting.
You see the WE57 setting is always done on the reciever side and not on the sender side (There is no harm but it is not what SAP recomends) The Linking on the sender side is done in the Partner Profile, where we give the extension name.
For the reciever this Partner profile setting of extension is not there therefore we need to go to WE57 and do it.
I've done all the config and have tried all the things in both the systems but somehow nothing is working.
That is why I asked that in my Inbound FM which is IDOC_INPUT_HRMD do I need to popluate one of it Parameters or fields where I mention the Extension name and all.
Yesterday however I found an SAP NOTE (105148) which tells me that my naming convention of the Extension is wrong. I have made ZHRMD_A07 extending standard IDOC tupe HRMD_A07, actually it should be ZRMD_A07. Again this is speculative I need to try this out. But I do know that SAP has various checks which checks all the naming convention and all. I'll try this out and hopefully it might work.
In the meantime any other suggestions are most invited. I am using Message type HRMD_A and using IDOC type HRM_A07
Regards
Abhishek Sahi

Essential Transfer Parameters Missing in record during Inbound IDOC process

Dear Gurus
We are creating a Inbound delivery in one system, we have made all the custom settings for IDOC processing for inbound and outbound idoc in both the systems. Upon the execution of inbound delivery, the system
During the Inound delivery processing, the outbound IDOC is successfully distributed. However in the receving system, the IDOC is not posted and it throws the below erroe\r
Essential transfer parameters are missing in record: 0180000055 000010 / Mess number 561 and message type E
We are using Outbound IDOC mess type DESADV basic type DELVRY01 process code DELV with FM IDOC_OUT PUT_DELVRY
In the receiving system message type DESADV , process code DELS, and FM IDOC_INPUT_DESADV1
What is that which is going wrong.
Please help me out
Thanks

Hello
To create inbound delivery from outbound delivery, use following setting -
Outbound idoc -
idoc type - DESADV01
message type - DESADV
Process code - SD05
FM - IDOC_OUTPUT_DESADV01
Inbound iDOC -
Message Type - DESADV
Process Code - DESA
FM - IDOC_INPUT_DESADV
Idoc Type - DESADV01

Creating Delivery based on the Inbound IDOC received.

Hi all,
I have a requirement where in, Outbound Delivery for Sales order is to be created based on the inbound IDOC received from a third party. The standard idoc type DELIVERY03, requires the Delivery Number for updating the order but it cannot create a delivery number.
Can any one suggest which IDOC type can be used for this or if there is any alternative solution?

Hi,
You can use FM IDOC_INBOUND_WRITE_TO_DB to create an inbound IDoc.
CALL FUNCTION 'IDOC_INBOUND_WRITE_TO_DB'
    EXPORTING
      PI_STATUS_MESSAGE       = I_EDIDS
    IMPORTING
      PE_IDOC_NUMBER          = DOCNUM
      PE_STATE_OF_PROCESSING = STPROC
      PE_INBOUND_PROCESS_DATA = I_TEDE2
    TABLES
      T_DATA_RECORDS          = I_EDIDD
    CHANGING
      PC_CONTROL_RECORD       = I_EDIDC
    EXCEPTIONS
      IDOC_NOT_SAVED          = 1
      OTHERS                  = 2.
Check the following link:
http://www.sapbrain.com/TUTORIALS/TECHNICAL/IDOC_tutorial.html
<b>Reward points</b>
Regards

IDOC ( WS-- XI -- R/3) Receiver Port

Hello i am having issues with IDOC post on R/3 via XI. The issue is with receiver port. I am populating values of Message variant and message function in Mapping and nothing else were populated.
As per SAP documentation RCVPOR variable will be populated from receiver adapter whether "Apply control record from payload is checked or not".
This value RCVPOR is being populated control record of idoc when "Apply control record from payload" is unchecked . when its checked its not . please comment

Hi Bujji,
did you see the RCVPOR in your payload?? if yes then select all the three check boxes in adapter refers to payload.
basically there are two ways to send Receiver and Sender details to R/3, one is from payload and the other is from configuration.
if you check the "Apply Control record from payload"
along with this you shd check "Take Sender from payload" and "Take Reciever from payload". then it should work.
if you uncheck Apply control record from payload then it will take these details from SLD. Make sure that these are given there.
Regards,
Sukarna

Inbound IDoc: Field BVTYP is missing

Hi,
I am new to IDoc I need help with a scenario. We have an interface wherein AP documents are transported to SAP. When we are viewing these IDocs in SAP field BVTYP (Partner Bank Type) is missing
Thanks in advance

Hi,
Are you dealing with inbound or outbound IDoc for sales order?
I am a bit confused ... you mentioned the IDoc successfully posted (inbound IDoc?) however outsource EDI team reported that field ZEILE is missing (outbound IDoc?)
Regards,
Ferry Lianto

Inbound IDOC missing

Hi ,
We are testing idocs between two clients of a system ABD, between ABDCLNT100 and ABDCLNT200.
The sender is client ABDCLNT200 and receiver is client ABDCLNT100. The outbound process was successful in client 200 but we cannot see the inbound idocs in the receiving client 100. The status of the outbound IDOC in client 200 is 03.
Could anyone please let me know all the checks I need to do in client 100 to find out why the IDOC is not posted or why we cannot even see the inbound idoc in 100.
Thanks
Swetha

Hello
sm58 in the sender to see if there are any rfc errors.
sm59 to ensure that the rfc connections between the two clients are working.
bd64 to make sure that the definition of the distribution model is correct.
Regards
Greg Kern

Segment E1IDBW1 is missing for the inbound idoc type PAYEXT

Hello,
the above segment is missing in the inbound idoc - basic type pexr2002.
I have checked in TC-we30 and its available there.
but still the idoc is getting generated without this segment.
can someone suggest.
thanks
Arun

Hi All,
I have a similar query to that of Penny. We are able to get the standard IDOC to generate with segment E1IDBW1. It contains the standard fields INPWEEMP, INPWTXT1, INPWTXT2. However, we have a requirement to manipulate the standard contents of these fields. We wanted to use user exit EXIT_SAPLIEDP_002 to do this.
I have maintained user exit EXIT_SAPLIEDP_002 but when we enter this on creation of the IDOC the segment E1IDBW1 does not seem to be available in table EDIDD_TABLE for manipulation. Can you advise please if (1) you were able to get E1IDBW1 available to edit in exit EXIT_SAPLIEDP_002 and (2) were you able to manipulate the contents of INPWTXT1, INPWTXT2 etc?
We have done the following steps:
- BTE 2441 is available on our release
- house bank has been setup as an In House Cash Center which allows E1IDBW1 to be generated
- entry has been maintained in table FEDICUS with Message Type = PAYEXT, BasicType = PEXR2002, Extension = Blank, Seg Type = E1IDBW1
- code maintained in ZXF08U04
The system enters ZXF08U04 but E1IDBW1 is not available there for manipulation.
Can you advise what we might be missing please?
Thanks and regards
Mike

Receiver port missing in inbound idoc

Similar Messages

Maybe you are looking for