Doubt on Idoc adapter parameters

Hi ,
      I need one more clarification on Idoc adapter parameters :
1.while configuring for IDOC adapter in communication channel , we have an option
called "APPLY CONTROL RECORD VALUES FROM PAYLOAD" doubt arises here
what actually this mean,and if this check box is ticked what values will be taken from payload and where will be they applied?
                       Plz clarify answers will be definetely rewarded.
                                                                                Regards,
                                                                                Vinod.

Hi vinod reddy ,
If u want to add values to the control record , u have to select the APPLY CONTROL RECORD VALUES FROM PAYLOAD checkbox in the communication channel. When a new communication channel of type IDoc is created, the flag is set by default. If the flag is not set, the
settings comply with XI 2.0
This following websites clearly clarifies u'r doubt with detailed description with fields :
Fields of the IDoc Control Record
http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
Configuring the Receiver IDoc Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/content.htm
How to.......Sample IDoc XI Scenarios
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
cheers!
gyanaraj
****Pls reward points if u find this helpful

Similar Messages

Doubt about IDOC Adapter

Hi all,
i'm using idoc adapter for generating IDOCS from R/3, and my scenario is: IDOC->XI->File. this is working fine, in R/3 i've got partner profiles for diferent vendors(suppliers) and they are configured for create idoc message in R/3 and all this message are caught by XI from my scenario and generate the corresponding text file.
but now suppose that I need another scenario because i need to send purchase orders by mail instead file to some of my vendors in R/3. the scenario would be IDOC->XI->Mail.
for both cases i would use ORDERS05.
i can't undertand how XI knows wich scenario have to use, if there's nothing from R/3 that tells XI which scenario should be used.
thanks, Fabian.

Thanks for responses, I know what should i use to do what i wanted. but i've tried to make a condition in the receiver determination and it's giving me an error saying that 'No receiver could be determined'.
i've searched in other threads and i have seen that utilizes xpath to make conditions
what i have done is add a condition in Configured Receivers as '/p1:ZORDERS2/IDOC/EDI_DC40/RCVPRN = 0000010598'
because depending on the partner, i want to use either one or other adapter (file or mail)
do i have misedd something?

Doubt Regarding IDoc Adapter

Dear Gurus,
In IDoc to XML conversion scenarios, we never use Sender Communication Channel because the IDoc adapter sits on the ABAP stack and the conversion is done by the IDoc adaper in the Integration Server.
Then why in case of the reverse scenario , i.e. XML to IDoc conversion we use Receiver Communication channel and the IDoc adapeter explicitly? Why can't that IDoc Adpater that sits on the ABAP stack convert the xml file into IDoc format?

Hi Shweta,
the reason for this is:
The adapter at the inbound channel is located before the Integration Server pipeline and calls this pipeline. The adapter at the outbound channel, however, is called by the pipeline, and can therefore be regarded as part of the pipeline.
The connected systems transfer or receive IDocs through their IDoc RFC interface.
if you check this link:
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
and read the Integration section and try to understand the pipeline flow, as the names are not understandable(viz. receiver determintaion, mapping etc.) in the diagram.
you will get the clarity after reading this..
Sachin

Doubt on Idoc Adapter

Hi
I was going thru the help.sap for IDoc adapter.
Implementation Considerations
Only use the IDoc adapter to integrate SAP systems with the Integration Server if a scenario of this kind suits your requirements.
in
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
what does it really mean. I understand where the idoc adapter is placed and y no sender agreement is req. But this phrase in help.sap is confusing.
Can i take all ur help in understanding this?
thkx
Prabhu

Hi,
IDOC scenarios are used when you have to transfer business data TO or From SAP R/3 . Itz is still the most preferable solution. But if you want ackowledgements to be sent back for ex: a business data back can it be acheived through idoc >? No. That where rfc comes into picture. Itz only effective during assynchronous communication.
I suppose it was in this conext of application of a idoc adapter that was illistrated.
correct me if itz wrong
<b>Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*</b>

Doubt in Sender IDoc Adapter

Hi Gurus
I have doubts regarding the sender IDoc adapter.The sender IDoc adapter is present by default and we do not create manually. the qos of this is EO by default.
How can we change the QOS of the sender IDoc adapter? do we have to maitain any settings on the R/3 side, please explain??
thanking you

Dear Abhinav,
Check my comments in this forum thread:
[IDOC Serialization|Re: IDOC Serialization in PI]
Regards
Praveen K

Receiver AAE IDoc adapter

Hi All,
I have a doubt regarding receiver AAE Idoc adapter. There are three options available in java IDoc adapter namely Default, Manual and From NWA. In Default option, we just need to configure a RFC Destination in NWA but in From NWA option, we need to configure RFC Destination as well as Resource Adapter(JCA Connection Factory). So, I just want to know what is the benefits of using From NWA option over Deafult and what is purpose of configuring Resource Adapter in NWA?

Hi,
see the below link.
http://help.sap.com/saphelp_nw73/helpdata/en/bc/0341dd385945d49eb809c084cf3dea/content.htm
as per this link i should check the checkbox.
Configuring Acknowledgements for a Sender IDoc Adapter (AAE) Locate this document in the navigation structure
Procedure
    Choose the sender communication channel on which you want to enable acknowledgement settings.
    Choose the Parameters tab and then, choose the Ack Settings tab.
    On the Acknowledgement Parameters area, enter the following settings:
        System Ack Ok Requested
        Choose this option to receive XI system acks.
        System Ack Error Requested
        Choose this option to receive XI system error acks.
        Application Ack Ok Requested
        Choose this option to receive XI application acks.
        Application Ack Error Requested
        Choose this option to receive XI application error acks.
        ALEAUD Special Handling Needed
        Choose this option to enable the sender Java IDoc adapter to apply special handling to the incoming ALEAUD message. The adapter replaces the IDoc number of the ALEAUD message with the original IDoc number.
        Initially, the receiver Java IDoc adapter generates a unique IDoc number, which replaces the original IDoc number of the outbound message. This IDoc unique number is referred by the ALEAUD message. However, the ALEAUD message is not converted to an XI Ack message in this case.

IDoc Adapter - ATTRIBUTE_BE_NOT_SUPP Async processing

Hello,
I'm trying to establish IDoc communication. Here is the scenario that I need:
<XML Data> --- <SOAP> --> PI Server ( Map XML to IDoc XML) --- <IDoc> --> SAP Retail System
I have the following components set up:
1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
2. Sender Agreement
3. Map from InXML to OutIDoc. OutIDoc - Message Interface - Inbound Asynchronous
4. Receiver Determination
5. Interface Determination
6. Receiver Agreement
7. Receiver IDoc Communication Channel
8. Business Service for all this
No Integration Scenario.
If I replace item 7 to the FTP for example, everything works just perfect - I send XML it gets Mapped to IDoc and in my FTP I have the IDoc file.
Now, I've asked SAP support specialist to establish communication from PI Server to Retail using IDoc. He send me parameters, which I used for IDoc Communication Channel:
RFC Destination: NX7CLNT800
Port: A000000022
SAP Release: 3 - this is I put myself
But when I run the whole system again, I'm getting the error:
IDOC_ADAPTER ATTRIBUTE_BE_NOT_SUPP - "Only asynchronous processing supported for IDoc adapter outbound processg"
This is very confusing because both my message interfaces are Asynchronous.
Can anyone tell me what I'm doing wrong and why I'm getting this error.
Thanks.

8. Business Service for all this
Should it not be Business System for IDOC.....for SOAP it will be Business Service
1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
Check what is the QoS that is specified in the SOAP Channel.....if it is Best Effort then it will be a cause of the error......change it to Exactly Once (EO).
Regards,
Abhishek.
Edited by: abhishek salvi on Dec 4, 2009 10:29 AM

PI 7.1 Ehp1 IDOC adapter message packaging - package options on sender side

Hi guys,
I am trying to use the new IDOC adapter PI7.1 Ehp1 functionality for packaging the IDOCs in single PI message, instead of using Collect pattern in BPM. I have configured IDOC sender comm. channel with Sender Agreement as well. So far, so good, but I am wondering if the packaging done on PI side should be the same as the packaging parameters on sender side...
What I mean? Do I have to set the Pack. Size (we20) to be the same as the one on PI, and do I have to use "Collect IDocs" as
Output mode (also found in we20) .. I guess "Yes".. Actually what I got also is that I have to schedule RSEOUT00 if I am using the option to Collect IDOCs, right ? Can execution of RSEOUT00 be "plugged" somehow to be executed after bd21(Creation of IDocs from change pointers) execution ..?
If you have any personal experience on this - please share it with me
Thanks & Best Regards,
Lalo

I am wondering if the packaging done on PI side should be the same as the packaging parameters on sender side
Do not have to be same.
Think of this way: there are two containers carrying water: A for ECC and B for PI (specified in communication channel), you are defining the size of the containers.
If Size of A > B, then, One full A will need more than one B to handle, means multiple PI messages will be created.
if Size of A < B, One PI message is enough to handle incoming package.
For sure in partner profile of ECC, you will need to enable IDOC packaging and specify the size (container A).
Regards
Liang
Edited by: Liang Ji on Jun 8, 2010 3:30 PM

IDOC ADAPTER as sender settings

Hi ,
We trying a basic scenario where R/3 is a sender system
R/3 >IDOC ADAPTER>XI-->(File/sap system)
S57CLNT800
Configuration done at Sender R/3 system
1) RFC DEST for XI
2) trfc Port for above rfc dest
3)Partner profile for Logical system EXICLNT100(this is ls for XI server)
   outbound parameters (Message type Orders)
Configuration done at XI
1)RFC dest for Sender R/3
2) port by idx1 for RFC dest created above
in Integratoion directory
Assign buusiness systm...for technical system Sender SAP system
Whats next?
Is there any settings to be done in XI to setup partner proile and inbound parameters as Orders.
When i am trying that then it is throwing error saying orders message type not present in table edmsg
Casn some one explain me what settings to be done in (WE20)Integration repository also?
Please help me in this matter coz i am stuck like dope with no hope....with this for many days.
Please let me know if any more details you need.
Thanks a lot
Deepti Patil

Hi Michal
I am amzed to see your so fast reply.
Ya i have read the weblog by Ravikumar Allampallam which had helped me to configure
My SAP system as receiver and which went successfully.
But now since i am trying the scenario where SAP system should send the idoc
and lets say receiver system can be FILE or Again some SAP system but through XI.
So as i told earlier
I have made a technical system as system as ABAP (S57)
business system assigned to it.
When i assign this business system to a configuration scenario in Integration directory,
in adapter specific identifiers i can see
logical system as my sender system
R/3 system ID S57
Client 800
Integration server is set as integration server in sxmb_adm
Now i have queries as
1) any data mapping necessary in Integration repository (by importing IDOC)
    IN Integration directory will there be only one communication channel as
    receiver for my receiving system?
2) In Sender system when i simulate the IDOC that time who will be my recipient(we19)
   I am very new to idoc also so if you can help me in this.
3) if now if i am posting IDoC from SAP system, where in XI we can check whether IDOC is arrived or not/
4) if you have any standard document for all this.
5) i am following SAP HELP IDOC processing with IDOC ADAPTER
Thanks a lot again!!
Deepti patil

Reciever idoc adapter Determination error

Hi,
I have scenario File-XI-R/3.I am using Idoc adapter to send data to R/3.
I am getting Reciever determination error.I have done all the steps according to the below weblog.
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
When I test my steps in configuration with test tool it is succesfull but give me error at runtime.
Below is error description.
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Plz help me out if any one has some idea abt it.
Thanx
Rekha

Hi Rekha,
The End Point Type for your scenario should be an IDoc Adapter with parameters from your RFC destination in SM59.
The most common reason for this error is:
1. An error in configuration of sender adapter/proxy: wrong sender business system or namespace or interface name. Look, all this information you must put manually so be carefull on typos (one wrong or ommited letter and you can spend hours looking what is wrong). Copy (from Repository) and paste procedure is strongly recommended.
2. An error in Directory (Endpoint Configuration). Be careful to specified the correct host and port!!!
Hope this helps.
Regards
Suraj

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

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

REG: Error in IDoc adapter outbound processing

Hi All,
      I had a couple of doubts regarding these IDoc's.
1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
"IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
Can any one help me to Solve my Problem
2) How to find out whether the IDoc is of synchronous or Asynchronous mode
    and how to handle the synchronous type of IDoc's
Thanks in advance.
with Regards,
Kalyan Dannapaneni.

Hi Kalyan,
IDOCs are only Aynchronous (EO or EOIO).
If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
Best regards,
Silvia

IDOC adapter message limitation Status 64

Hello,
we have implemented an IDOC R/3->XI->R3 scenario.
Sometimes it happens, that the sending system generates a hugh number of idocs.
In this case, the IDOCs are posted to the receiving R/3 system, but stay on status 64 which says,
"...to few dialog processes...."
So the receiving SAP system has to few processes to start the processing of the idocs.
But we can no enhance the amount of the processes.
Is it possible, to limit the calls of the IDOC adapter
or to schedule the idocs, or to make a package?
This should be done on XI!!!!
I have read the QUEUE option, but we are working on 4.6BASIS, so this did not solve the problem.
best regards
Werner

Werner-
This situation can be handled using some variations to your suggestion of handling it in XI.
1) In the Partner profile of the target R3 system, use the option 'trigger by background program' in the inbound parameters. This way, the IDOCs will be created in the database, syntax checked and will be set to status '64' but with a different message (mostly No filters....). At this point, we are not even trying to post the IDOC to the application, which takes the most processing time.
2) Then in your traget SAP system, schedule program RBDAPP01. There are various options available to restrict your selections. By scheduling this program to run in regular intervals, you can process IDOCs which are in status 64, there by re-processing them if some failed during the last run because of lack of processes.
Some additional information on performance improvment:
RBDAPP01 is an interesting program, because it allows you to parallel process the IDOCs plus process them in packets. That is, instead of processing IDOCs one by one, you can make the program to use all the available free processes to process the IDOCs in parallel. This will greatly reduce your processing time.
If you see, this program has a tab called 'Parallel Proc' (assuming you are logged on in English). You can activate the check box 'Parallel Proc. Active' and choose a 'Server Group'.
Now, before using this option, you need to understand that this program will occupy all free DIALOG processes. Which means no process will be available for users to log on (even admins) while the program is busy posting IDOCS. However, this limitation can be overcome by fixing a system parameter on the server group which will limit the number of processes to be used by this program. For e.g., in one of my implementations, we set up the profile parameter in such a way that out of 13 dialog processes available, the program will always leave 5 processes free thereby occupying only seven free processes max.
This setting was done by the basis team and probably you or your basis team already know about it. If not, let me know, I will try to find it out from our guys here.
Hope the above explaination help. For more information check note 399271 and other related notes for RBDAPP01 PARALLEL PROCESSING.
KK

IDoc Adapter throws error

We are trying to send data to SAPR/3 47 IDES using IDoc Adapter.
the data is sent to XI from SQL database thro JDBC adapter and then to R/3 thro IDoc adapter.
All this is in Asynchronous mode and at no point we chose synchronous (IDoc adapter does not suppost Asynchronous process right).
But we are getting the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>B7685EB2-42F1-554B-80CC-6ADFC86C7975</SAP:MessageId>
<SAP:RefToMessageId>35A42550-81F9-11D9-AFC7-00C09F450580</SAP:RefToMessageId>
<SAP:TimeSent>2005-02-18T22:05:33Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>S70_812</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">DEBMAS.DEBMAS04</SAP:Interface>
</SAP:Sender>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_BE_NOT_SUPP</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Only asynchronous processing supported for IDoc adapter outbound processing</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
We are not sure where from this synchronous is being picked?
Please advise.
Thanks,
Bhaskar and Anil

In the Processing Parameters section of the JDBC adapter, make sure you have Exactly Once (Asynchronous) selected.

Doubt on Idoc adapter parameters

Similar Messages

Maybe you are looking for