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

Similar Messages

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

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

How to get the inbound idoc for the newly created inbound Idoc FM

Hi,
I have created a new function module to process the Inbound idoc. I need to have a idoc to check my function module, whether it is working fine or not. How I can get the data. Do I need to have the idoc from the partner ? Please help me ASAP.
Thanks,
sreenivas.

Hi Sreenivas,
Go to WE19 and get any of the your present idoc with the idoc type
then go to BD20...execute the same idoc...and there you can create the IDoc, and process the same with the Inbound function module tab..( give the FM you are using as the process code.)
from there you can do the debugging aswell of that FM
Thanks

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.

Delay in the Inbound Idoc Posting Process

Dear Friends,
We have an scenario in the Inbound Idoc Posting Process, when we process the Idocs through the standard Inbound Program - RBDAPP01, we face the delay of 3hrs to 12 hrs, approx.
When we try to re-process the same through the manual process, we could successfully post the Idocs, immediately.
When the same happens, through the background job - the delay is happening.
As we see, there is no problem with the program - RBDAPP01, but can't able to trace the delay in the process.
Any suggestions / advises are welcome.
Thanks in advance.

Hi Prasanna,
The update will happen only if a value already exists with the same unit of measure in the system. If the quantity is left blank in the system and if you are trying to update, the update might not happen. Even if the value is Zero in the system, provide the same unit of measure as the data used in the BAPI.
Regards,
Yogesh

How to write processing code for the Inbound IDOC to the R/3 ??

i m having a file -> XI-->R/3 scenario,
IDOC is being sent from XI to R/3,
can u guide to me to write a processing code for the Inbound IDOC to the R/3,
since i m new to ABAP and ALE technology, can we provide me any blog for doing that.......or guide me....

Hi Sudeep
Simple File to Idoc scenarion blog
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
Also see the blog
<a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> by Ravikumar.
Configuration of IDOC adapter
http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/frameset.htm
Regards
Santhosh
*Reward points if useful*

Where to put break point when debugging the inbound IDOC processing

Hi, Dear Experts,
If IDOC has error and want to debug, which program or function module to put break point when debugging the inbound IDOC processing
Thank you so much!
Helen

It depends on if you have the custom FM or standard FM...Is it MM invoice or FI invoice? ... You can find out your FM by going to partner profile (WE20) for your sender partner and partner function.. Drill down to your partner and the message type and find the inbound process code.. Double clicking on the process code will help you find the FM...
If you don't have access to WE20, You can also put BP into any of the IDOC_INPUT_INVOIC* FM and see if it is getting triggered (assuming your IDOC is standard FM)...

Find the Inbound IDOC

Hi Experts,
I have a requirement to get the Inbound IDOC for particular PO. I have used the following method:
http://forums.sdn.sap.com/thread.jspa?threadID=1082790
That means using tables:
A) SRRELROLES
B) IDOCREL
This is working for most of the cases except if the inbound IDOC is amended by the sender ( ex:- requested quantity changed ).
1. If inbound IDOC received without any changes, it will be there in SRRELROLES as roletype = 'INBELEG'.
2. If inbound IDOC received with changes it is not there in SRRELROLES.
Could you please help me to resolve this issue?
Thanks,
Chaminda

Hi,
Thanks for your help.
anyway, finally i had to use the time consuming way as there is no any other way.
1. Get all the ORDRSP Idocs from EDIDC based on the selected date range
select docnum status
      into table lt_edidc
      from edidc
     where credat in p_date1 and
           mestyp = 'ORDRSP'.
    if sy-subrc eq 0.
      sort lt_edidc.
2. Get all segment data records for the control records
      select mandt docnum counter segnum segnam psgnum hlevel dtint2 sdata
        from edid4
        into table lt_edid4
         for all entries in lt_edidc
       where docnum = lt_edidc-docnum and
             segnam = 'E1EDK02'.
3. to imporve the performance, i have used BINARY SEARCH when search back the IDOC from PO.
Thanks,
Chaminda
Edited by: chamindakrat on Feb 17, 2012 12:07 AM

Some Data Missing in the inbound Idoc received from Gentran

Hi,
We are receing one custom message type with the basic type ORDER05 in SAP from Gentran. When we checked the destination file generated in Gentran, its showing data for all the segments. However in SAP when we checked the corresponding idoc we find the segment E1EDP05 is missing. The Gentran team says they are placing the destination file in the unix server of SAP. However we dont find these files in the SAP Unix server. Could anybody advise what could be the problem and where we need to check further ?

Gentran will never be able to create an IDOC within SAP. Here is what happens:
> Gentran creates a flatfile/XML which is in the IDOC format (the one which you can see in WE60).
> Gentran then places this flat file/XML in a folder on Application server. This can be UNIX, Windows NT, etc..
> Gentran then triggers the Startrfc.exe which will trigger EDI_DATA_INCOMING function module.
> This FM will parse the data, check it for consistency of the defined standards, then write the control record into EDIDC and corresponding data records into EDID4 and updates the relevant statuses (i.e. 01 - added, etc). It'll then look into the partner profile setup, look for process code and moves the status to 64 and calls the inbound FM which will post the application document.
In you case, you need to find out what file is coming in and where E1EDP05 has missed. The data will only be sent by Gentran. The inbound function modules will never update IDOC data records (unless there is a customization). The status records are updated.
If E1EDP05 is not mapped and sent by Gentran and you still used to see it, then there should have been a customization in place to add values to IDOC segment fields. Try to get the final file that is mapped from either X12/EDIFACT and then see if E1EDP05 segment is present in there. If it is present then upload the same file into AL11 using CG3Z and call EDI_DATA_INCOMING or WE19 to process it. Once processed, you'll can observe if E1EDP05 is being created or not.

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

Message type is not populating in the Inbound idoc control record

Hi,
I have created an Inbound Idoc function module and have done the necessary Idoc settings. But, while testing in WE19, I observed that control record is not getting populated with message type and it is dumping.
The settings which I have done in WEDI as follows:
1. Created Idoc segments with necessary fields and released
2. Created Idoc type for the segment type
3. Created message type
4. Assigned message type to basic type
5. In the inbound processing settings,
filled the ALE attributes with the Idoc function module name and input value '0'
6. Assigned FM to basic type and message type
7. Created process code and assigned the process code to message type
Please let me know, the reason for the message type not populating in the control record. Useful answers will be surely rewarded.
Best Regards,
Mallika

Hi,
Maintain partner profile (Transaction code WE20) for the message type you defined in WE81 and put your process code in partner profile and check your logical system settings also in transaction SALE.
Thanks
Rahul

Validation the Inbound Idoc Cremas05

Hi ,
I have a requirement for inbound IDoc, my scenario is like this , we have to process the ADRMAS03 idoc first. This idoc will contain vendor number in OBJ_ID field .After that we have to process CREMAS05 idoc, at the same time we have to validate the vendor 's existence (which is in OBJ_ID field in ADRMAS03 idoc) . If vendor does not exists we don't want to process the CREMAS05 .
How to check whether the vendor is already exits when we process the CREMAS05 ?
In which table, the vendor number will store when processing the ADRMAS03 ?

Hello ,
It is an SAP Standard Interface created through BDBG. I would suggest you to create a similar interface using BDBG.
1. First create an empty BAPI( Copy of BAPI_GOODSMVT_CREATE) say ZBAPI_GOODSMVT_CREATE. Note the remove the logic of your Z BAPI.
2. Got to SWO1, create a deleagtion of BUS2017 called ZBUS2017 and a new Z API Method ZCREATEFROMDATA forr Z BAPI
Release and Activate.
3. Now go to BDBG and create an BAPI -ALE Interface.
You can write the custom logic and validation in your Z BAPI - ZBAPI_GOODSMVT_CREATE and finally call the standard BAPI BAPI_GOODSMVT_CREATE in it to post goods movement.
Advantage : 1. one less enhancement for SPAU, next upgrade.
2. Interface is generated automatically , only you need to take care of your custom code in Z BAPI.

Cost center not checked during the inbound idoc FIDCCP2

Hi all,
Could you please give any input on this strange issue.
I am testing inbound Idoc FIDCCP2 (GLVOR = 'HRP1' ) with tcode WE19 and when I fill cost center with value 'ZZZZZ' the system post the FI document and deosn't check the cost center like in FB01.
With FB01 I have a error message "Coste center 'ZZZZ 'does not exist on 21.08.2014" and cannot post the document.
Thanks.
Farouk.

Try OSS note 114814.
Regards
Waza

How top filter the inbound idoc?

Hi all,
I need to filter the Idoc like only some data to some particular organization.
Only some purchase organization i need to process.
How to filter it?
Regards,
Rohith.

HI rohit,
if you need to mapp the values from "originalvalue" to > "new_value" ... then you could use the ALE IDoc Segment Conversion Rules
1. Tcode: BD62 - Create a new Rule
2. Tcode: BD79 - change the values for that rule
3. Tcode: BD55 - assign the rule to a partner
Regards,
Gordon

RCVPOR is missing the Inbound IDoc

Similar Messages

Maybe you are looking for