Configuration Port in Inbound IDoc?

Hi~
There is a scenario "File to IDoc".
The flow of the scenario is legacy file system -> XI -> R/3.
Then,
Is it correct to configure only in XI using IDX1 & IDX2?
If it isn't correct, then should I configure in R/3 using WE20 & WE21, too?

Hi,
>In R/3
1. RFC Destination pointing to XI. (SM59)
2. Create Port using RFC Destination in WE21.
3. Partner Profile in WE20.
perfect on R3. The only difference will be that the Partner Profile now will have an Outbound Idoc as R3 is sending the Idoc. In the case of Idoc to file, the partner profile will have an inbound entry in it.
SLD 0f XI
1. Create tech System for the r3 system -> this will be a webasABAP
2. Create business system for the CLient of the r3 system --> webasABAP and make sure that tyhe logical system name is correct.
Use this business system as the sender system.
Partner Profiles are always done on the SAP R3 system.
Regards
Bhavesh

Similar Messages

Error in Testing Inbound Idoc PORDCR102

Hi,
I am creating purchase order using message type PORDCR1.
I have done the partner profile entry and Process code is 'BAPI'.
while testing the Inbound Idoc PORDCR102 using WE19.
I am passing the Control Record and the data record Information.
But when I am executing it in forground it is giving me Dump and IDOC remains in status 62.
Error is :-
Access via 'NULL' object reference not possible.
Error analysis
 An exception occurred that is explained in detail below.
 The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
 caught in
 procedure "PROCESS_COMPONENTS" "(FORM)", nor was it propagated by a RAISIN
 clause.
 Since the caller of the procedure could not have anticipated that the
 exception would occur, the current program is terminated.
 The reason for the exception is:
 You attempted to use a 'NULL' object reference (points to 'nothing')
 access a component (variable: "L_ITEM").
 An object reference must point to an object (an instance of a class)
 before it can be used to access components.
 Either the reference was never set or it was set to 'NULL' using the
 CLEAR statement.
I verified the data by creating the Purchase order using BAPI_PO_CREATE1, purchase order is successfully created.
Do Anyone have done a similar testing for message type PORDCR1, please give me your suggestions.
Thanks
Monika.

Hi Shankar,
check whther u r using the correct function module for correct message type.
anyway check the following configurations for an inbound idoc.
1>we81
2>we31
3>we30
4>bd51
5>we57
6>we42
7>we20
Regards,
Nagaraj

Sales order configuration data to the IDoc

Hi Experts,
I need to make sure that always in the outbound IDoc (ORDERS05) the segment E1CUVAL contains VALUE_TXT element for every VALUE element.
can you please tell where can I find the code that is in which user exit, to change it for checking E1CUVAL segment.
the configuration values are coming from the Sales order.
Thanks in advance.
MK
Edited by: mk.xi on May 2, 2008 10:48 AM

Hi Advait,
I think you can populate configuration data for inbound IDoc ORDERS05.
In user exits of IDOC_INPUT_ORDERS, you can search table VBAP for given material (will be posted) and find VBAP-CUOBJ (not initial). Then call function module VC_I_GET_CONFIGURATION to find all available configuration/characteristics data for above matarial.
From here, you can populate segment E1CUREF, E1CUCFG and C1CUVAL.
data: i_configuration like conf_out occurs 0 with header line.
data: l_instance like inob-cuobj.
clear: i_configuration.
refresh: i_configuration.
select single *
from vbap
if sy-subrc = 0.
l_instance = vbap-cuobj.
endif.
call function 'VC_I_GET_CONFIGURATION'
exporting
 instance = l_instance
tables
 configuration = i_configuration
exceptions
 instance_not_found = 1
 internal_error = 2
 no_class_allocation = 3
 instance_not_valid = 4
 others = 5.
loop at i_configuration.
endloop.
Hope this will give you an idea.
Regards,
Ferry Lianto
Note: Please award point for helpful answer.

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.

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

Inbound Idoc Configuration

Hi All,
I am new to Idoc, i wish to know what all steps are required for the configuration of the Inbound and the Outbound Idoc,
if some one can provide me some helpfull links and the steps for the same. that will be highly helpfull.
Regards,
Himanshu

Hello Himanshu,
Here you can find all relevant information for IDOC processing, see all the related topics in the Menu list:
http://help.sap.com/saphelp_utilities472/helpdata/EN/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
Hope this helps.
Regards
Olivia
Edited by: Olivia Walsh on Nov 29, 2010 12:42 PM

Inbound IDOC for sales orders not posting the configuration data

Hi all,
I am facing a problem in posting the inbound IDOC (message type ORDERS). The configuration data maintained in the parent segment E1CUCFG and in the segment E1CUVAL is not getting posted though i am passing the data in these segments which is 100% correct.
Can any one solve this problem

Hi Ravi,
Please check the two segments are active. You can do that in BD53.
In BD53 enter message type, and make the segments active.
If segments are active, it appears in white colour.
After this post the IDoc and check with segments.
If its useful, award points pls..
Regards,
Bharadwaj

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

Configuring to receive a iDoc in R/3 sent by XI

XI send a idoc( inbound - ORDERS05 ) to R/3, but occurs an ALE error, what's the basic settings that must to be done in R/3 to send iDoc(inbound) from XI to R/3 ?
Is it necessary to configure a port to XI in IDX1 in R/3 ?

Hi Regis,
U have to configure Port using IDX1 in XI where an RFC destination is to be mentioned which holds the recevier logon details...
And in the receiver maintain the partner profile(Inbound parameters needed to be handled...(WE30))
Regards,
Sridhar

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

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

Inbound IDoc ORDERS05

HI,
I have to design an Inbound IDoc for create an Sales Order from a plain file
The Idoc I use is ORDERS05
Can anybody help me with some easy example???
I have some problem when I tried to match the fields in the segments of the Idoc and the fields in the transaction VA01....

Hi,
Please check this links for inbound IDOC ORDERS05 data mapping.
http://www.erpgenie.com/sapgenie/docs/sapedi/ordersin.xls
http://www.erpgenie.com/sapgenie/docs/sapedi/ordedi.xls
http://www.erpgenie.com/sapgenie/docs/sapedi/ordi1.doc
If the above links do not work for you, then please try to use WE19 (IDoc testing tool) for data mapping and simulate the inbound sales order. You can also use this tool for testing purposes as well.
Once done, then you can try to process your inbound IDoc file using standard program RSEINB00 to read the file and generate IDoc(s). Please ensure all your ALE and IDoc configuration are done such as distrribution model (BD64), partner profile (WE20), IDoc Port Processing (WE21) and so on.
Hope this will help to start with.
Regards,
Ferry Lianto

How to configure, push and test Idoc from XI to R/3

Assuming mapping between imported Idoc and some file structure is fine ,I have to configure XI and R/3 for pushing Idocs from Xi to r/3. I have to make sure they talk.
-I have done this long time ago for pushing Idocs from R/3 to XI but I wonder if it is same procedure or it is different ?
-Can someone tell me - how to configure both for this purpose partner profiles , logical systems etc ?
-And also after configurations , how I can check if Idocs is received from Xi and the entire process is successful?
-does it make difference the type of Idocs during the configurations?
-Are the test for success same for all type Idocs?
Thanks all !
Jon

Here are the steps:
===========================
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
Additional References
Ale Configuration for pushing Idocs form SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

INBOUND IDOC issue

Hi,
I'm facing the following problem:
A program reads a file from a directory in the unix server itself and populates an IDoc. No BDC is involved.The file contains all the data required to populate the IDoc like control record, data records etc. But when the IDoc is posted, it fails giving the message " Receiver port in the control record is invalid ". But when I try to reprocess the IDoc through WE19 without changing anything, I'm able to process it successfully by giving the Inbound Function Module corresponding to the process code.This is not happening in the case of Standard Inbound. I'm using a file port with ALE services but not EDI.All the other configurations are maintained.
Please suggest a solution.
Thanks,
Raj.

Hi Rajgopal,
for an inbound idoc no need for port configuration.Please see whether u have done all the configurations correctly.Also if this is inbound that means u r updating to SAP , so already data will be available in control record and data record.So please check the sender information and the receiver information.check the port the sender using.
For a custom function module,custom message type,custom basictype,the below configurations r generally done.
1>we81
2>we31
3>we30
4>bd51
5>we57
6>we42
7>we20
In we20 u have give u r zmessagetype in the inbound parameters and also u r custom process code.
Regards,
Nagaraj

Port Settings for IDoc Adapter

Hi All,
Our scenario is like this ERP -> XI -> File. ERP sends IDoc to XI. I have a couple of questions.
1. In the control part of an IDoc, there's a sender partner number and sender port. What are they used for? As I understand, the partner and port represent the destination of the IDoc instead of the source. Why is there sender port and partner?
2. We need to maintain port using IDX1. Should I set the name of the port to be the same as the sender port of the IDoc?
3. I didn't configure the scenario and the IDoc sender adapter. If the ERP system sends IDoc to XI, can I find it in t-code IDX5?
Best Regards
Jerome

Hi Jerome,
1. Sender Partner and Port : The control record should have sender port and partner number. This will be used by the receiver system (i.e., XI system). Because, receiver system should know from which system this IDoc is coming using Sender Partner number. This partner number should be same as Logical system name in Sender Business system which is configured in SLD.
The sender port should be SAP<Sys-id of sender system>
and sender partner number should be <sys-id of sender>CLNT<client number of sender>
2. The port created in IDX1 will be used for importing IDoc's metadata in XI system from R/3. IDoc metadata is needed by IDoc adapter to convert incoming IDoc to IDoc-XML format.
It is mandatory to have same name for Port in IDX1 and sender port of the IDoc's control record.
3. I think the IDoc wont be listed in IDX5 if scenario and IDoc adapter are not configured. IDX5 displays inbound and outbound IDocs in the IDoc adapter.
Regards,
Uma

Configuration Port in Inbound IDoc?

Similar Messages

Maybe you are looking for