Problem with HR inbound IDoc

Hi,
I have a problem with processing inbound IDocs from an external payroll system to infotype 0008. The process is quite simple; salary changes from the payroll system is recorded to the corresponding employee's infotype 0008. When testing I noticed that that the new record is recorded as is. For example if there is already an existing record with the validity dates 01.01.2010 - 31.12.9999 and the new record in the IDoc is 01.01.2011 - 31.12.9999, the new record is written as is. I would expect the system to delimit the old record correctly - similar to what would happen if you maintain records online. There is no error checking or any kind of processing done by the system.
I did some debugging and found out that the function module linked to process code HRMD writes the information directly to the database. If this is a standard way of doing this, it is really unusual.
Has anybody else encountered this? Any pointers?
Thanks.
Edited by: Theo Droste on Jan 20, 2011 11:56 AM

Hi
This is correct, the ale programme writes the data directly to the database, I have faced this isssue on occassion. I once raised an oss message on this as well, and sap confirms this is what happens. If it is a sap to sap ale, it somehow seems to work, - this could be because the outgoing idocs are created by sap itself but if it is a non sap to sap ale the onus is on us to ensure that the external system sends the correct data to sap in the way we intend it to be displayed.
that is how it has been in my experience. It is unusual, but apparently not impossible. Please let us know if you find out anything different.

Similar Messages

With out inbound Idoc can we post the data using we19

Hi,
with out inbound idoc can we post the data using we 19.........
for testing any idoc type particular to inbound FM is posting application data..in TABLES.....
Regards,
Raghunadh.

HI Raghunadh Babu
The main purpose of given WE19 Transaction by SAP... To generate test IDoc and check whether the data is posting according to business requirement....
Answer for your question.....Yes U can generate IDoc...
Enjoy playing with we19...
RR

Problem with extension of idoc in XI

Hello All,
I've extended an Idoc in R/3 with new segment.
That new idoc extension i've mentained in t/code IDX2
Also, i've imported the new extended idoc in XI in IR.
Next i've done the related mapoping for the new segment in IR.
In ID, do i need to change the old idoc name with new extension idoc which i'm using in the Receiver Agreement
After doing all these above modifications..i've receving the below mentioned error message
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Pls. let me know how i need to proceed further.
Thanks in advance!!!
Regards
Prasad

Hello Prasad,
Go through these discussions....
<IDOC_ADAPTER> ATTRIBUTE_IDOC_METADATA
Re: ERROR: "IDOC_ADAPTER" / "ATTRIBUTE_IDOC_METADATA"
File2IDoc Adapter Error
Hope the above links are very helpful to you..
Thanks,
Satya Kumar

Problems with processing outbound IDocs in background processes

Hello everybody,
I have a question for working with ABAP-PSS Ports.
The behvaiour is that I want to send master data, for example customers, to a function module. This function module works like an converter which process and writes the files in the filesystem.
Following situation:
- I have defined a partner System with different message types, for example DEBMAS and everthing what is necessary to replicate data to partner systems.
- I have defined also a Port like ABAP-PPS Port for calling my own function module.
- If I runs the program I process only 50 Idocs per process because otherwise i can happen that there are to many look entries in the system and the job crashs. (For example all customers are around 50000 Idocs).
Now my problem is that the worker for processing idocs starts each process in the foreground and in parallel.
But this is very strange! Because then all dialog processes are reserved and the system will be very slow!
How can I configure the Port or what have I to implement in my fucntion module to start processing in background (this is the very important point) and maybe allow the program only to use one or two process at the same time?
I have found on the function module EDI_DOCUMENT_CLOSE_PROCESS which I the parameter "Background". What thas this mean? I have set B for this but it has no effect!
Regards
Christian

I know that for inbound interface it is possible to define if in foreground or background and if parallel processing is allowed.
Who knows how I can do this also for outbond?

Problems with PORDCR101/2 IDOC Type

Hi All,
I am new to SDN so not sure of the protocol so please bear with me.
I am trying to use IDOC type PORDCR101 to create purchase orders.
In the segment E1BPMEPOHEADER I have mapped the the DOC_TYPE to NB (with the corresponding E1BPMEPOHEADERX set to X)
But I am still getting a strange error message
Document type ZU not allowed with doc. category F (Please check input)
ZU is a bespoke requestion that exists in the system, but nowhere is this mapped. The standard NB Purchase order type exists in the system.
If anybody can shed some light, I can provide the complete mapping if this is useful.
thanks
Shashi

Hi G.Ganesh Kumar,
The partner profile in WE20 the Partner Type is set correctly, the inbound parameters have message type PORDCR1 set correctly with the BAPI process code.
I have no problem generating the idoc, I get the error 51 with the above description when the idoc tries to post.
Shashi

Problem with non-updated idocs

Hi,
we have a problem after upgrading from 3.5 to 7.0. Lots of extractors end
in an error-message concerning non-updated idocs. Every day several
extractors have this problem. This are not always the same extractors. As
a result we must repair many extractions manually.
I know the procedure of how to repair, but I want te know how I can prevent
extractors from running into this problem in the first place.
Any suggestions?
This is the problem-message that we get...
Non-updated Idocs found in Source System
Diagnosis
IDocs were found in the ALE inbox for Source System that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs
manually using the Wizard or by selecting the IDocs with incorrect
status and processing them manually.

It has been happening on our env as well (BI 7.0 SP 12), time to time one load or the other gets into this problem and it waits yellow for few hrs before turning red.
I can correct the IDOC and move on or run the load again it works fine.. but the process chain gets held up not going to the next stage for hrs..
any resolution on your problem..
thanks
Mayil

Problem with creation of IDOC Segment Type

Hi,
I tried to create IDOC Segment Type Z1LFA1 but error
prompted "Structure Z1LFA1 already exist.".
I tried deleting it at se11 but prompted
"You cannot edit object R3TR TABL Z1LFA1 with the
standard editor"
and at sm30-TADIR, but prompted
with "Cannot delete object directory entry, object exists."
How will go about this??
Please help!
Thanks!

hi,
yup, tried doing that on we31 but the segment does not exist yet.
we're currently upgrading from 4.6 to ecc, I think the structure
was tranferred to our ecc client but the idoc segment and idoc type were not. I'll just have to transport it then.
Thanks!

Problem with an Receiver Idoc adapter

Hi.
We have just went from XI 3.0 to PI.7.10.
The Receiver idoc adapter is set up in the same way as it was in XI.
The problem is when two different interfaces runs at the same time I got data into the DC40-record which not belongs too this idoc but from an another interface/idoc.
The idocs are different messagetypes.
In this case the field MESCOD which belongs to one of the idocs also appered in the idoc where the field MESCOD not should be used.
Any idea whats wrong ?
/Per-Arne

Thanks.
Checked sxmb_moni as you said.
In the OutboundBinding-node I can see the right idocadapter is used
where 'Apply Control Record Values from Payload' is enabled.
<SAP:ChannelName>IDOC_INBOUND_U01_110</SAP:ChannelName>
In the IdocOutbound-node I can see the message code 'EXT' which should'nt be there.
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>001</SAP:MANDT>
<SAP:DOCREL>710</SAP:DOCREL>
<SAP:DOCNUM>0000000000033474</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>OILLDD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>OILLDD</SAP:MESTYP>
<SAP:MESCOD>EXT</SAP:MESCOD>
Too be more specific about the interface.:
I got one file in from a file adapter and out of that file I produce two idocs into R3 whit
two different idocs-adapters.
I think you are right about that the configuration may be mixed up.
Any idea of what I can do?
It may be an PI 7.10 bug ?
Shall I delete all config objects and so set config up from scrach again ?
/Per-Arne

Problem with import of IDOC fromSAP 3.1i to PI 7.0

Hi ,
I have an IDOC as ZXYZ.ORDERS01 in SAP R/3 3.1i System, I am unable to import the IDOC in PI7.0
Let me know the process to import that idoc.
( I am Doing IDOC to File and file to IDOC Scenario )
Regards,
Edited by: TomShey on Sep 22, 2010 6:27 PM

Hi,
We also had same problem of unable to import IDOC structures automatically from SAP 3.1I to XI/PI, as the support of this feature as mentioned by SAP starts from version >= 4.0.
Please find the prerequisite as mentioned in help.sap.com
Prerequisites
The SAP system from which you want to import the RFCs or IDocs must contain function modules for calling metadata. You can import RFCs and IDocs from SAP Release 4.0 and higher. The table below gives an overview of the required support packages:
(http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm)
So as per my experience, I could identify three options after indepth investigation.
1. Recreate the IDOC structures in another SAP system which is of latest version >= 4.0 may be IDES, and then import the structure in IR for further developments. This is the option we are using for our developments now.
2. Get WSDL of the IDOC structure by creating manually the structure using XML Enterprise edition using the complete syntax or xpath and import as external definitions and use it in mapping.
3. Re-create the IDOC structure in XI system itself and try to use it.
Let me know if this helped you.
Regards,
Bindu

Problem with SAPServerHost - Receiver Idoc

Good afternoon!
I am using the component SAP.Net Connector to receive IDOC's from the SAP, for this I created a Windows Service and in the OnStart event I create the SAPServerHost object that will go to talk with the SAP (through the transaction sm59, for example).
It happens that some times the SAP does not obtain to see this object, thus being does not obtain to send the IDOC's for windows service.
Thank you.
Danilo Santos de Oliveira

The SAPServerHost itself doesn't register at the SAP gateway. The actual SAPServer-inherited instances do so. You create them and attach them to the SAPServerHost. The host can control the state of the servers that it hosts, e.g. it can stop, pause and continue them.

Problem with Context in IDoc

Hi Experts,
I have the following source fields:
1 <Recordset>
      <Record>
         <LineIdentifier>ITEM</LineIdentifier>
         <Data>D1<Data>
      </Record>
      <Record>
         <LineIdentifier>ITEM</LineIdentifier>
         <Data>D2</Data>
      </Record>
2 <Recordset>
      <Record>
         <LineIdentifier>ITEM</LineIdentifier>
         <Data>D3<Data>
      </Record>
Target : 2 Idocs to be created!
For each recordset, an IDoc needs to be created. For Idoc 1, there should be 2 segment of E1EDP01 to be created(coz 2 ITEM) and Idoc 2, there should be 1 segment of E1EDP01).
I have done it as follows:
Check if LineIdentifier (context is recordset) = ITEM then map Record to UDF createItemrecord as follows
for(int i =0; i < record.length; i++)
     result.addValue(record<i>);
Then map it to RemoveContext and SplitByValue. The result is Idoc 1 has 1 segment of E1EDP01 (Value D1) and IDoc 2 has 1 segment of E1EDP01 (value D2).
The expected result is => Idoc1 -> E1EDP01(D1) and E1EDP01(D2) and Idoc 2 -> E1EDP01(D1) and E1EDP01(D3)
Please explain how this can be achieve.
thanks a lot.
Rewards guaranteed!!!
Regards,
Tush
Edited by: Tush Mangad on Aug 14, 2008 8:53 AM

I have found that XSL mapping does this quite well
An example to create Sales Order IDocs
Note that square brackets in the generate statement have been interpreted by this editor as a strikethrough
Input file
<?xml version="1.0" encoding="UTF-8"?>
<input>
     <row>
          <ordernum>ORD1</ordernum>
          <orderitem>ITEM1</orderitem>
          <data>ABC</data>
     </row>
     <row>
          <ordernum>ORD1</ordernum>
          <orderitem>ITEM2</orderitem>
          <data>DEF</data>
     </row>
     <row>
          <ordernum>ORD2</ordernum>
          <orderitem>ITEM1</orderitem>
          <data>GHI</data>
     </row>
</input>
XSL
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
     <xsl:output method="xml" indent="yes"/>
     
     <xsl:template match="/">
          <CRMXIF_ORDER_SAVE_M01>
               <xsl:apply-templates select="//input"/>
               
          </CRMXIF_ORDER_SAVE_M01>
     </xsl:template>
     
     <xsl:template match="input">
          <xsl:variable name="sales_order" select="//row"/>
          <xsl:for-each select="$sales_order">
               <xsl:if test="generate-id(.)=generate-id($sales_order[ordernum=current()/ordernum])">
                    
                    <xsl:if test="position()!=1">
                         <xsl:text disable-output-escaping="yes"><</xsl:text>/E101CRMXIF_BUSTRANS<xsl:text disable-output-escaping="yes">></xsl:text>
                         <xsl:text disable-output-escaping="yes"><</xsl:text>/IDOC<xsl:text disable-output-escaping="yes">></xsl:text>
                    </xsl:if>
                    <xsl:text disable-output-escaping="yes"><</xsl:text>IDOC BEGIN=<xsl:text disable-output-escaping="yes">"</xsl:text>1<xsl:text disable-output-escaping="yes">"></xsl:text>
                    <EDI_DC40 SEGMENT="1">
                         <TABNAM>EDI_DC40</TABNAM>
                         <MANDT>010</MANDT>
                         <DOCREL>620</DOCREL>
                         <STATUS>30</STATUS>
                         <DIRECT>1</DIRECT>
                         <OUTMOD>2</OUTMOD>
                         <IDOCTYP>CRMXIF_ORDER_SAVE_M01</IDOCTYP>
                         <MESTYP>CRMXIF_ORDER_SAVE_M</MESTYP>
                         <SNDPRT>LS</SNDPRT>
                         <RCVPRT>LS</RCVPRT>
                    </EDI_DC40>
                    <xsl:text disable-output-escaping="yes"><</xsl:text>E101CRMXIF_BUSTRANS SEGMENT=<xsl:text disable-output-escaping="yes">"</xsl:text>1<xsl:text disable-output-escaping="yes">"></xsl:text>
                    
                    <xsl:call-template name="bustrans_Template">
                         <xsl:with-param name="bustrans" select="current()"/>
                    </xsl:call-template>
                    
                    <xsl:call-template name="bustransItem_Template">
                         <xsl:with-param name="bustransItem" select="current()"/>
                    </xsl:call-template>
               </xsl:if>
               
               
               
               <xsl:if test="generate-id(.)!=generate-id($sales_order[ordernum=current()/ordernum])">
                    <xsl:call-template name="bustransItem_Template">
                         <xsl:with-param name="bustransItem" select="current()"/>
                    </xsl:call-template>
               </xsl:if>
               
               <xsl:if test="position()=last()">
                    <xsl:text disable-output-escaping="yes"><</xsl:text>/E101CRMXIF_BUSTRANS<xsl:text disable-output-escaping="yes">></xsl:text>
                    <xsl:text disable-output-escaping="yes"><</xsl:text>/IDOC<xsl:text disable-output-escaping="yes">></xsl:text>
               </xsl:if>
          </xsl:for-each>
     </xsl:template>
     
     <xsl:template name="bustrans_Template">
          <xsl:param name="bustrans"/>
          <APPL_SNAME>CRMXIF_BUSTRANS</APPL_SNAME>
          
          <E101CRMXIF_SALES_X SEGMENT="1">
               <APPL_SNAME>CRMXIF_SALES_X</APPL_SNAME>
               <DATAX>X</DATAX>
               <E101CRMXIF_SALES SEGMENT="1">
                    <APPL_SNAME>CRMXIF_SALES</APPL_SNAME>
                    
                    <PO_NUMBER_SOLD>
                         <xsl:value-of select="ordernum"/>
                    </PO_NUMBER_SOLD>
               </E101CRMXIF_SALES>
          </E101CRMXIF_SALES_X>
     </xsl:template>
     
     <xsl:template name="bustransItem_Template">
          <xsl:param name="bustransItem"/>
          
          <E101CRMXIF_BUSTRANS_ITEM SEGMENT="1">
               <APPL_SNAME>CRMXIF_BUSTRANS_ITEM</APPL_SNAME>
               <OBJECT_TASK>I</OBJECT_TASK>
               
               <ITEM_NUMBER>
                    <xsl:value-of select="orderitem"/>
               </ITEM_NUMBER>
               
               <PRODUCT_ID>
                    <xsl:value-of select="data"/>
               </PRODUCT_ID>
          </E101CRMXIF_BUSTRANS_ITEM>
     </xsl:template>
</xsl:stylesheet>
Result
<?xml version="1.0" encoding="UTF-8"?>
<CRMXIF_ORDER_SAVE_M01 xmlns:fo="http://www.w3.org/1999/XSL/Format">
     <IDOC BEGIN="1">
          <EDI_DC40 SEGMENT="1">
               <TABNAM>EDI_DC40</TABNAM>
               <MANDT>010</MANDT>
               <DOCREL>620</DOCREL>
               <STATUS>30</STATUS>
               <DIRECT>1</DIRECT>
               <OUTMOD>2</OUTMOD>
               <IDOCTYP>CRMXIF_ORDER_SAVE_M01</IDOCTYP>
               <MESTYP>CRMXIF_ORDER_SAVE_M</MESTYP>
               <SNDPRT>LS</SNDPRT>
               <RCVPRT>LS</RCVPRT>
          </EDI_DC40>
          <E101CRMXIF_BUSTRANS SEGMENT="1">
               <APPL_SNAME>CRMXIF_BUSTRANS</APPL_SNAME>
               <E101CRMXIF_SALES_X SEGMENT="1">
                    <APPL_SNAME>CRMXIF_SALES_X</APPL_SNAME>
                    <DATAX>X</DATAX>
                    <E101CRMXIF_SALES SEGMENT="1">
                         <APPL_SNAME>CRMXIF_SALES</APPL_SNAME>
                         <PO_NUMBER_SOLD>ORD1</PO_NUMBER_SOLD>
                    </E101CRMXIF_SALES>
               </E101CRMXIF_SALES_X>
               <E101CRMXIF_BUSTRANS_ITEM SEGMENT="1">
                    <APPL_SNAME>CRMXIF_BUSTRANS_ITEM</APPL_SNAME>
                    <OBJECT_TASK>I</OBJECT_TASK>
                    <ITEM_NUMBER>ITEM1</ITEM_NUMBER>
                    <PRODUCT_ID>ABC</PRODUCT_ID>
               </E101CRMXIF_BUSTRANS_ITEM>
               <E101CRMXIF_BUSTRANS_ITEM SEGMENT="1">
                    <APPL_SNAME>CRMXIF_BUSTRANS_ITEM</APPL_SNAME>
                    <OBJECT_TASK>I</OBJECT_TASK>
                    <ITEM_NUMBER>ITEM2</ITEM_NUMBER>
                    <PRODUCT_ID>DEF</PRODUCT_ID>
               </E101CRMXIF_BUSTRANS_ITEM>
          </E101CRMXIF_BUSTRANS>
     </IDOC>
     <IDOC BEGIN="1">
          <EDI_DC40 SEGMENT="1">
               <TABNAM>EDI_DC40</TABNAM>
               <MANDT>010</MANDT>
               <DOCREL>620</DOCREL>
               <STATUS>30</STATUS>
               <DIRECT>1</DIRECT>
               <OUTMOD>2</OUTMOD>
               <IDOCTYP>CRMXIF_ORDER_SAVE_M01</IDOCTYP>
               <MESTYP>CRMXIF_ORDER_SAVE_M</MESTYP>
               <SNDPRT>LS</SNDPRT>
               <RCVPRT>LS</RCVPRT>
          </EDI_DC40>
          <E101CRMXIF_BUSTRANS SEGMENT="1">
               <APPL_SNAME>CRMXIF_BUSTRANS</APPL_SNAME>
               <E101CRMXIF_SALES_X SEGMENT="1">
                    <APPL_SNAME>CRMXIF_SALES_X</APPL_SNAME>
                    <DATAX>X</DATAX>
                    <E101CRMXIF_SALES SEGMENT="1">
                         <APPL_SNAME>CRMXIF_SALES</APPL_SNAME>
                         <PO_NUMBER_SOLD>ORD2</PO_NUMBER_SOLD>
                    </E101CRMXIF_SALES>
               </E101CRMXIF_SALES_X>
               <E101CRMXIF_BUSTRANS_ITEM SEGMENT="1">
                    <APPL_SNAME>CRMXIF_BUSTRANS_ITEM</APPL_SNAME>
                    <OBJECT_TASK>I</OBJECT_TASK>
                    <ITEM_NUMBER>ITEM1</ITEM_NUMBER>
                    <PRODUCT_ID>GHI</PRODUCT_ID>
               </E101CRMXIF_BUSTRANS_ITEM>
          </E101CRMXIF_BUSTRANS>
     </IDOC>
</CRMXIF_ORDER_SAVE_M01>

Problem with automatic outbound IDoc creation

Hi all!!!
I want to configure an IDoc to be created when an Installation (IBASE) is saved.
To do this, I use the IDoc type CRMXIF_IBASE_SAVE01, assign a message type, link with the FM APPL_IDOC_INPUTM to create the IDoc, create a partner profile, create the process code and set on the message type.
After this, when I create an Installation, Must not the IDoc be created?
Is the process correct or lack some step?
Thanks and regards,
Manuel.

And, on the partner profile, I can´t set the process code on the outbound parameter because the field doesn´t appear.
I think this could be the error.

Problem with File to IDOC scenario

Hello,
I try to implement our first scenario to IDOC.
In TOC SXMB_MONI I have to errors
1. <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
2. <SAP:Stack>Unable to convert sender service aaa_Sender_Service to an ALE logical system</SAP:Stack>
Any idea how I can solve this problems?
Elad

HI,
I think u have not done the configuration at the R3 end....
Just go through the below step by step process of FILE to IDOC. and check whether u have done the same configuration for ur scenario....I dont know what all configuration u have done....
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Thnx
Chirag

Problem with Posting Sender IDOC

Hi,
I am Integrating SAP R/3 with a web browser Using SAP XI
Sender     : SAP R/3     -
> IDOC Adapter
Receiver   : Web Browser----->Soap Adapter
In SAP R/3 I am doing for " PM Module"
for Transaction IE02 ( Change Equipment),
This Transaction is Used to change any details of that Equipment.
I Identified the Standard IDOC which is created by using BAPI
"EQUIPMENT_CHANGE.EQUIPMENT_CHANGE01"
I configured ALE at Sender and configured Soap Adapter at receiver side.
<b>My Query is,</b>
Now I want to Post the IDOC , For the Above IDOC How should i send.
( For Example for Matrerial MATMAS for Posting IDOC it has transaction BD12)
But for Posting My IDOC wat will be the transaction and How should I post it.
Points will be awarded for the answer.
My Email ID is : [email protected]
Regards,
Jayasimha Jangam

Hi Jayasimha,
You should do the following configurations to post an IDoc from R/3 to XI.
Once check wheather these configurations are done.
<b>SAP XI</b>
1) RFC Destination (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.
2) Create Port (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 SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
<b>SAP R/3</b>
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

IDX2 Communication Error - Problem with only 1 IDoc Type

Trying to import metadata via IDX2. All IDoc types have imported succesfully, except DELVRY03.
I get a message saying "Communication Error" Message #: IDOC_METADATA407.
I have tried DELVRY01 and it imports fine. But, DELVRY02 and DELVRY03 both give the "Communication Error" messages.
Any ideas why this one particular type will not import? Settings/logon have not changed.
Thanks

FYI, Update... I think I may be on to something here...
All checks in WE30 return okay.
I debugged the IDX2 program, error is occuring in the 'IDOCTYPE_READ_COMPLETE' function call. It is returning with message: 'Structure of segment E1EDD10 is unknown'. Did search on this in OSS and found note #491264 -- Output of IDoc DELVRY02/DELVRY03 does not work
Symptom
You want to display IDoc DELVRYnn (nn = 02,03), SHPMNTnn (nn = 03,04,05), or PLNSHPnn (nn = 01) via the IDoc documentation transactions. The sys
Comment: This relates only to the display of the IDOC structure. The IDocs work for the data exchange.
Still working through the note to see if this will fix the issue, but I just tried to import in SHPMNT03 and I get the same error.
Thanks.

Problem with HR inbound IDoc

Similar Messages

Maybe you are looking for