Idoc adapter configuration

while idoc adapter configuration we uncheck the option " apply control record values from payload" why and when it will be usefull?

Hi Sudhakar,
When you want to map control record values from the Target payload .....
Then you choose the option apply control record from payload.
Follow the link below to understand the concept better....
(Configuring the Receiver IDoc Adapter --> Fields of the IDoc Control Record)
http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/frameset.htm
Regards,
Sushil.

Similar Messages

IDoc Adapter configuration for very high volumes

Hi PI Expert,
I'd like to have some tips about Idoc Adapter configuration in case of very very hudge volumes in "file to Idoc scenario" (adressing ECC) : How to optimize Idoc transmission time PI -> ECC ?
=> parallelization PI -> ECC by using differents comm channel IDocs with differents RFC destinations ?.
=> some other technical parameters in adapter IDoc
=> ...
Thanks a lot
Best regard.
Etienne

Hi,
for sure idoc bundling will greatly increase performance: https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2762. [original link is broken] [original link is broken] [original link is broken]
If you are in 7.1 you can also leverage message packaging: http://help.sap.com/saphelp_nwpi71/helpdata/en/46/79e8e13872275ae10000000a11466f/frameset.htm
Regards,
Sergio

Idoc Adapter Configuration Issues

Dear Collegues,
I have given up almost all hope on configuring my Idoc adapter as I have an error message that I am not sure of how to fix; I have read just about everything I can get my hands on....any help would be so much appreciated:
Scenario: Demonstrate a simple 'proof of concept' to send MATMAS from R3 ->XI -> R3
Sending system: [R3 4.6b] CL0510
Rec'g system: [R3 4.6b] EL0510
XI system 3.0: NXL220
Current error message in outbound RFC layer of CLO:
No service for system SAPCL0, client 510 in Integration Directory
Per the documentation I have done the following:
- RFC connections are all complete
- Port and Partner Profiles complete
- ALE model from sender for MATMAS
- IDX1 in nxl for ports
- IDX2 - matmas metadata
- Integration Builder [config]:
 *Technical and Biz systems set up
 *CL0510 is set up as 'services w/o party' and there is
 a generated idoc channel.
 *The Adapter Specific Identifier is the CL0510 log
 syst.
 *Receiver Determination is created w/
 idoc_inbound_asychronous as interface; not sure
 what "namespace" is so I threw the word Idoc in there
 *Interface Determination is created w/ above
 parameters except the receiver party and service have
 asterisks in them I can't seem to remove
 *Sender and Rec'r Agreements set up [again what goes
 in that namespace field?]
I think that identifies all of the configuration I have attempted to enter. I have been only able to read documentation and weblogs as XI training won't be happening for me and my collegues until another several weeks.
Thanks so much,
Jennifer Edmondson
Intel Corp, AZ

Hi Jennifer,
for the inbound to XI, e.g. CL0510 you don't have a sender agreement since when you setup up the WE21 trfc Port on CL0510 it points to the XI system as a regular type T SM59 connection. On the connection you can enable the TRACE flag and see in the trace what payload got sent and any errors. I had a problem with that as my user / password to the XI machine was wrong.
The other part I'm missing from your message is, did you do all the Repository stuff beforehand, e.g. import the IDOCs for each Software Components(defined in the SLD, Tech and Buiz System), then when you use the dropdown in the Directory the Namespaces will default as the urn:sap-com:document:sap:idoc:message. Again once you have done the repository there is no need to write namespaces by hand at all. Do not put an IDOC into a Message Interface, may be into an action if you like to put a scenario into the IR (not necessary).
On the Receiving IDOC Adapter you will specify all the RFC stuff for the EL0510 system and this one goes into an receiver agreement.
I'm sending MATMAS from R/3 to XI to File Adapter or SOAP and no issues at all.
On CLN510 in BD87 does the IDOC has a status of send? Does it look ok?
I hope this helps. I can make some screenshots of my config if that helps. Send me an e-mail to [email protected]
Cheers
Stefan

XI 2.0 - IDOC Adapter configuration

Hi,
I currently have an integration scenario whereby an external system sends IDOC-XML to our integration server which then forwards this via an IDOC adapter to an R/3 620 system.
When I send the XML to one client I keep getting the following message :-
<SAP:Context />
<SAP:Code p1="Requested parameter does not exist" p2="RQ1CLNT302" p3="" p4="">IDOC_ADAPTER.RECEIVER_BSI_INCORRECT</SAP:Code>
<SAP:Text language="EN">Unable to convert partner to IDoc receiver partner</SAP:Text>
After my initial investigation I believed that the above error was due to the client within the SLD had been set-up without a logical system name and the receiving business system had been set-up without an ALE name. In order to resolve this I deleted and re-created the client and the business system within the SLD. Having done all this the error still occurs.
Does anyone know what causes this problem?
The systems involved have been set-up in the SLD as follows :-
a) Sending system PKMS_SAPTEST Alename: PKMS_TEST
b) Receiving system RQ1CLNT302 Alename RQ1CLNT302
I have checked the ports in IDX1 and the partner profile in the receiving system but still cannot work out what is causing this problem.
I know I am missing something really obvious as these messages work when I send them to other clients but I am at a loss to explain the difference
Regards
Ian

Hi All,
I have now resolved this problem and thought I should spend some time sharing this with you.
I decided to look at the code that was issuing the error which was calling a function module called SAI_LOGICAL_SYSTEM_GET to return the logical system for my business system. When I ran the function module in test mode it returned a blank logical system. The logical system is stores in table sailcrbsc. I re-ran the function module with the bypass buffer field set to 'X' - now when the function module is called it returns the correct logical system.
Anyone out there have any more info on this? How should I have re-built this table?
Regards
Ian

XI - 3.0 Adapter configuration

Hi,
can any one tell me how to confirm that XI adapters ( default ones wotever comes along with NW-XI) have been installed successfully?
Reg,
Venkat

Hi,
For IDOC ADAPTER
follow the steps:
1 Scenario
This guide deals with all the configurations required to create an IDoc adapter in Exchange Infrastructure
3.0 to send an IDoc from XI to the SAP backend system.
Unlike other types of adapters, the IDoc adapter has dependencies on the XI 3.0 ABAP configurations and
the backend SAP system configurations. Those configurations information will have to be either created
first or retrieved in order to complete the IDoc adapter configuration.
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
     The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
     The Client must be the client number of the backend SAP system.
     Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
     Double-click on the business system in the Integration Directory.
     Switch to Edit mode.
     Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
     The RFC Destination is from step 3.1.
     The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
2) For File and RFC follow this blog:
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Regards
Hemant
Awar points if find helpful

IDoc Adapter - Logical System - File to IDOC configuration

I have a scenario reading a File ->XI->IDoc in R/3. I'm looking to have the control record parameter for SNDPRN reflect the Environment dealt with. I unchecked the 'Apply Control Record Values from Payload' & 'Take Sender from Payload' boxes but the problem I'm getting is that the system is reading from the business service (IDoc Adapter - Logical System) and feed it in the Partner Profile in the IDOC. This means that I should all the time redefine 3 this Logical System in config before transporting my scenario from DEV/QA/PRD. Any idea how I can avoid this kind of 'hardcode' ?
Thanks

Hi,
Why u r using three different LS can't u use only one LS and send all the IDOCs to same LS. That will ease ur task.
Do let me know why u r going for three different LS.
In the file r u getting any data which will help u to identify that this file is for which LS. IF that is the scenario then u can use the value mapping and based on the value which is coming in file u can map it to the IDOc filed which u have mentioned and in the configuration it will take the respective configuration.
Thnx
Chirag

How to configure Sender IDOC adapter

Hi could someone pls guide me on the steps that i need to take to configure IDOC sender adapter..
Are the steps for Sender and Receiver IDOC adapter same other than the fact that sender idoc adapter doesn't need a sender communication channel.
Regards,
Ashish

hi Goyal,
Just check out this link.
How to Configure IDOC
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Regards
Sachin

Can we go with ALE configuration instead of receiver idoc adapter at target

Hi Experts,
Could you please provide me some idea when why don't we go with ALE configuration to exchange IDOC from PI to Target system instead of configuring receiver IDOC adapter at target side.

Hi Raj
Point 1:
When we send IDoc from SAP system to PI ,it used ALE connections nothing but using RFC destination and Port it establishes the connection IDoc will reach PI ABAP Stack.
Point 2:
When we send IDoc to ECC using PI IDoc adapter it uses the same mechanism(RFC destination/Port),but the only purpose of IDoc comm8unication channel is to call RFCDEstination and Port created in PI.
i.e: There is no difference in communication(Point 1 and Point 2) both uses TRFC calls.
Regards,
Raj

Configuration Problem on IDOC Adapter

Hi,
I am trying to configure the IDOC Adapter and am badly stuck.
On the sender system: I have configured
-RFC destination, ports and partner profile.
- I have also configured the SLD as per documentation
On the Integration Server:
-RFC Destination, Port maintanence(IDX1.
- Imported Metadata (IDX2)
My IDOC is getting created and is being sent properly, I can see that in WE02
But I cannot see it in Integration Server using transaction IDX5.
Please help.
Regards
Ramesh

Ramesh,
Try to refresh the cache
in Xi using transaction SXI_CACHE > delta Cache refresh.
Then go to Integration Server and Environment Cache Notifications.
Status should be green once you refresh the cache.
This may look a bit silly, but it worked for us.
(We used to get errors with SXI_CACHE in XI3 Service pack 9. Then we followed the steps of Checking Instalaltion part 1 as in XI3 install guide. Once we repeated these steps . SXI_CACHE worked and everything was fine).
To find what exacly is happening, try to send the IDoc from one R/3 to anotehr thro Xi.
The other R/3 will tell you the errors even if it does not show up in SXMB_MONI.
Hope this helps.
Thanks,
BG
Message was edited by: Bhaskar Ghandikota

Configuration Of Receiver Idoc Adapter

Hi Experts,
for an interface,I need to desighn a receiver idoc adapter.Plese guide Me
regarding following matters:
1. how to configure receiver idoc adapter ?
2. how to get the control record for the receiving idoc?
3. what are the configuration we have to make?
4. receiving idoc's data i want to update in my SAP database,How to achieve that?(Any program I have to write?what i need to mention in there?)
Eagerly looking for valuable suggestions.
Regards,
Rasmiraj
Edited by: rasmiraj tripathy on Aug 29, 2011 1:32 PM

Hi RashmiRaj,
Configuration Scenario
1. Create the RFC Destination in SM59.
2.Create Port in IDX1.
3.Create Logical System in BD54
4.Create A Scenario
5. Select a Business System in Service with out Party
6.Create a Receiver Communication Channel.
7. Create a new Business Service
8. Create a new Communication Channel
9. Mention the logical Name in the Service->Adapter Specific Parameters of both the File Sender Service as well as the business system.
10. create sender agreement
11. Create Receiver Determination
12. Create Interface Determination
13. Create Receiver Agreement
Also check the link [File to IDOC|http://www.****************/Tutorials/XI/FileToIDoc/FiletoIDocScenario.htm]
and http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660?quicklink=index&overridelayout=true
Thanks and Regards,
Naveen
Edited by: chichilin on Aug 29, 2011 5:40 PM

Configurations for Receiver IDoc adapter??

Hi,
I have a File-to-Idoc scenario. In the Reciever Idoc adapter configuraiton, we have to provide: 1) RFC destination and 2)Port. Where do we define the RFC destination and Port? Do we have to do any any configuration in R/3 in we20 and we21?
Any help is greatly appreciated.
Thanks,
Karma

1) RFC destination and 2)Port. Where do we define the RFC destination and Port?
>>These are defined on XI server in IDX1 tcode.
>>Port is SAP<XXX>, <XXX> = SID of R/3 receiver system
>>RFC destination is the one u mention in this port definition.
>>First define the RFC destination in SM59 of XI Server.
>>U need not do anything in IDX2.
Do we have to do any any configuration in R/3 in we20 and we21?
Yes.
In WE20 of R/3, u have define the partner profile for XI server with the IDoc as inbound parameter.
In WE21 port for connecting to XI server. Here also u have to mention the RFC destination, which has to be defined in SM59.
Good luck.
-Naveen.

Is Dynamic Configuration possible with IDOC adapter.

Hi,
I have SOAP to IDOC scenario. I have many SAP receivers and are determined at runtime in a Java map.
Can i use Dynamic Configuration for IDOC adapter?
Thanks
Shakthi

Hi Sivasakthi,
Why do you need Dynamic Configuration in receiver IDOC?
Regards,
Sanjeev.

SP14 Multi-mapping - error in receiver idoc adapter

Hi,
I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
When testing the setup 'real life' the message fails. The error message in the monitor says:
- 
- <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_WRONG_INTF</SAP:Code>
<SAP:P1>InterfaceCollection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
If trying to send multiple XML records, i get the following error:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
Also the Idoc is also being used as Inbound interface - so no mistakes here either.
I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
Best regards,
Daniel

Hi Daniel,
I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
CO_TXT_MMF_ENGINETYPE
Messages in multi message format can be sent to one adapter engine only
However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
I hope that helped you a little further - if you find out more I'd be happy to learn about it.
regards,
Peter

File name naming convention in File Adapter configuration in ID

Hi All ,
I have a query related to xml filename created in IDOC-XI-FILE scenario based on value of one of IDOC field .
The scenario is like this :
I have to send one xml file per store for material master . In this case how can I define my file name with store name in File adapter configuration in ID .
Naming convention should be
<storename>_date_masterdataname.xmlwhere store name is one of field of IDOC .
Plz help me .
Thanks in Advance
Regards
Prabhat Ranjan

Hi Prabhat,
take a look at this weblog:
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii
you have to specify variable substitution
(in the file adapter)
and give the path to the store name (in the variable sustitution table)
you file name schema (from the file communication channel can look like this)
%storename%_date_masterdataname.xml
Regards,
michal
Message was edited by: Michal Krawczyk

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

Idoc adapter configuration

Similar Messages

Maybe you are looking for