Communication Channel IDOC tipy and SENDER

Hi experts!
We have an XI SP14.
I have read that it is not needed a communication channel to send Idocs from R/3 to XI but, if we try to set this communication channel, we are not able to select the "Sender" option in the comm. channel. We have never used this kind of comm. channel to send Idocs from R/3 to XI so, I wonder why we are having this problem.
Do you know if this is a problem with the XI version or is it customizable?
If it is customizable, do you know where is this set up?
Thanks in advance!

The configuration data for all the adapter can be found in IR under
SAP Basis 6.40 - >http://sap.com/xi/XI/System - > adapter objects -> adapter metadata.
Select idoc and you can see the configuration for inbound idoc adapter but there is no outbound configuration provided by SAP. you can check for reference the RFC adapter for both inbound/outbound configuration. If you want to configure a sender idoc adapter then you will have to create all the necessary configuration in line with what is needed for an sender idoc and then upload this metadata. Its not going to be as simple as enabling the sender button you will have to create all the remaining input fields for sender idoc channel.
Cheer's

Similar Messages

If message failed at communication channel, then need to send idoc to R/3

Hi folks,
i got a requirment like .....If message failed at communication channel, then need to send idoc to R/3.
can anybody suggest the possible solution.

HI
If you use a catching a MAIL - PI ALERT and based on that alert if u creating an IDOC then it is good if u really supress the alert immediately once the ALERT comes but if u really check and supress the ALERT fine Otherwise a CONTINOUS IDOCs will get created at SAP system.
Also there might be some natural generic reasons for communication channel fails
a) somtimes if the target FTP is down
b) if there is some issue with FILE ENOUGH
c) If File adpater is placing same file already exists or with already Opened by some target application
d) Dynamica file naming issue. (technical issue)
WHy cant u do scenario in the below steps without keeping BPM, CATCHING ALERTS which doesnt give exact QUARANTEE
Do one thing make a technical design in such a way into 1 flow or 2 flows in worst case
In INTERFACE MAPPING-->
a) Insert your current Normal Graphical mapping
b) Javamapping:- This code will take the first mapping output as Input through Stream Transformation and create a same FILE through JAVA FTP Comments at specified Cleint Location. I recommend in order to avoid direct interraction of writing a file at client FTP better always write at your Local PI NFS Application outbound directory which doesnt require host name and user and pwd. Even if it requires you can do a RFC lookup and maintain a host, Port, User ID, pwd, Directory, FIle naming pattern in that table or else simply DO VALUE MAPPIING and pass it through XML INPUT from FIrst mapping as additional fields
c) WITH IN THE SAME JAVAMAPPING: -
   If it successfully writes a file - wRite a TRACE log ("FILE NAME+ Sucecssfully written+ File Bytes")
   Then create an simple small XML OUTPUT and PASS that JAVA MAPPING OUTPUT To 3rd Grahical Mapping as Input it might be less than 5KB.
Note: - Remember that this output XML should be ina Multmapping SPLIT MERGET FORMAT with 1 FIELD or required INFO
as KEY FIELD INFO using DOM FACTORY
d) GRAPHICAL MAPPING: -
SOURCE IS JAVAMAPPING OUTPUT and TARGET HAS 2 messages
                       Message 1) SAME INPUT SMALL XML OUTPUT COMING FROM JAVA MAPPING OUTPUT
                       Message 2) IDOC TY{E STRUCTURE
Keep a Condition based on KEY VALUE Coming from source field execute either 1 Message1 or Message 2
In this way you can complete in a single Flow.
Later you can deifnee a simple flow to PICK and DROP from SOURCE file Writing through javamapping to client location Or else
WRITE A small OS SCRIPT and CALL in Receiver FILE COMMUNICATION at OS Command so that while writing a LOG file it will move the file from Source FTP to CLient FTP location.
Regards
Amar Srinivas Eli

Sender communication channel for HTTP and IDOC

Why the sender communication channel is not necessary for HTTP and IDOC

Hi,
Because they lie on ABAP stack ie on Integration Engine...so that they can process directly but other adapter lies on Adapter engine.
Regards
Hemant

Compare two Idoc's and send to te recievers as per the Condition.

Hi,
Scenario: Sender are a Idoc's and Receiver is Mail and File.
Sum the value of field1 of IDOC1 loop and compare with the field 2 of IDOC2. If the Condition satisfy send the data to file and mail reciever else send to only mail reciever.
I tried using a BPM. Steps used in BPM are as follow:
Step: 1
Fork -- with two branches.
Branch 1:loop1-- reciever1 -- container
Branch 2:reciever2
Step2:
Switch with two branches: Check the compare condition of the two Idoc
Branch 1:
Fork with two branches with send step with mail and file recievers
branch 2: Only mail reciever.
However if the condition is true or false the information is send mail to reciever.
I tried with the above steps, but failed.
Any changes required, please let me know.
Regards,
Manoj

sumit,
I recieve N number of IDOC1. I need Sum the value of field1 of IDOC1 loop and compare with the field 2 of IDOC2.
I tried using a BPM . Steps used in BPM are as follow:
Step: 1
Fork -- with two branches.
Branch 1:loop1-- reciever1 -- container
Branch 2:reciever2
Step2: Transfomation with Mapping program, source and Target message
Step3:
Switch with two branches: Check the compare condition of the two Idoc
Branch 1:
Fork with two branches with send step with mail and file recievers
branch 2: Only mail reciever.
When i checked with workflow i observe that that the message is not moving out of transformation step.But the message mapping is succesfully tested
Thanks,
Manoj

Which communication channel is reliable and best?

Hi,
we do have the scenario peoplesoft-XI-xRPM integration.
In this scenario Inbound is the IDOC for xRPM.we have planned outbound for peoplesoft as JMS/HTTP/SOAP.In the above 3 cases which is reliable and most affordable?The main scenario is peoplesoft sends data in a file to peoplsoft integration broker.Here we are binding a link between peoplsoft IB and XI IB.For this we had 3 communication protocals.can any body suggest which one is reliable and best one?
Thanx in advance.

but even if XI doesn't have standard adapter for the peoplesoft you can always install another one:
How To Install and Configure External Drivers for JDBC & JMS
https://websmp101.sap-ag.de/~sapdownload/011000358700003994312004E/HowTo_ConfigExtAdapters.pdf
Regards,
michal

Creating IDoc XML and sending to XI

There is a mechanism to create IDoc XML within SAP ERP through the use of
Change Pointers in concert with a port of type XML File (WE21). This is well
documented in this document.
http://www.erpgenie.com/sap/sapedi/Conversion%20of%20IDOCs%20to%20XML%20format.pdf
My question is whether the IDoc XML can be generated using Change Pointers and
the resulting IDoc XML be sent to XI through a RFC Adapter.
Please don't suggest using an IDoc Adapter. I already know how to do that.
Thanks
Vamsi

Hello Vamsi,
2) You need use Sender File Adapter for this.Not by RFC Adapter
1)yes, you can generate IDOC-XML using Change pointer
for better understanding...
Re: Change pointers trouble
CHANGE POINTER SAPAPO/C5
Re: Change pointer issue!!
If you want to know the basic concepts of Change pointers...Search SDN..you will find lot of info regardin this...
******************Reward points,if found useful

Time out at communication channel type SOAP and RFC(synchronous interface)

Hello Experts.
I have a some interfaces here that have a Sender SOAP channel and Receiver RFC channe. We have problens with Timeout with soap channel and expiration with RFC time channel. I need a way to keep de connection alive in these interfaces, someome can indicate a way to do it?
Thanks a lot.

The error that ocurred is that one:
SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.MessageExpiredException: Message 4f451ed1-db17-11e0-ab5d-00001e05f032(INBOUND) expired: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.MessageExpiredException: Message 4f451ed1-db17-11e0-ab5d-00001e05f032(INBOUND) expired
The RFC inbouc channel expired.
Thanks.

Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

Hello All,
One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
Is the (IDoc) Communication Channel from Sending system to XI required to configured?
Many thanks in advanced!
Jochen

Hi Jochen,
for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
Thanks,
Rajeev Gupta

AE: multiple Communication Channel instances and message re-sending

Hi All,
My scenario is as follows:
We are running the adapter engine on a server cluster. In the RWB, I have multiple instances of the Communication Channels, for theit various cluster nodes.
My question is:
I have a message in the RWB, which is in System Error state in the AE. If I resend this message from the RWB, does it get queued for the same communication channel instance (as last time, when it failed), or can it get assigned to a new instance?
Hope my question is clear.
Regards,
Puloma.

Hi,
I realized that, a message will always be handled by the same instance of the Communication Channel.
But Exception is when an instance is down. In this case the dispatcher will immediately schedule this message for another instance.
In our scenario, all the instances of the Communication Channel were down, and all the messages were in System Error state, with the error: "Channel not initialized."
In this case, if the message is resent, will it go to the same instance, or to a different instance?
Regards,
Puloma.

JMS Sender Communication Channel problem

Hi XI gurus!!
I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
In defaultTrace.XX.trc I see the following information and errors:
#1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
#1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#com.tibco.tibjms.TibjmsQueueSession@3a5f233#
{GenericConnectionProfileImpl
{Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
JmsMessageSelector=,
ConnectionFactoryConstructor=null,
ConnectionFactoryFactoryInvocation=null,
ConnectionFactoryInvocations=[],
DestinationConstructor=
{ConstructorInvocation
{className=null,
invokeParams=[]
DestinationInvocations=[],
MessageInvocations=[],
DestinationName=null,
User=,
Password=,
isJmsSessionTransacted=true,
InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
LookupConnectionFactory=QueueConnectionFactory,
LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
SerializedConnectionFactoryPath=null,
SerializedDestinationPath=null,
Flags=0000000000000000000000000000000000000000000000000000100000000010
#1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
#1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
#1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
Thanks

HI,
As per the trace details given please consider few of the below options....
What do u see in adapter monitoring tool for JMS adapter?
http://hostname:5XX00/mdt/amtServlet
Did you follow the document on correlation of JMS messages?
In communication channel You have to set
Correlation ID -> XI conversationID
XI message ID->GUID
XI Conversation ID -> JMS correlation ID.
Now in the custom J2EE application you should set
jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
This thread deals with the issue..
JMS Queue monitoring
Check if the JMS Sender adapter EOIO is with serialized messages
Thanks
Swarup

Stop and Start Communication Channels

Hi All,
I am finding some peculiar entries in my application log which has made my scenario go awry.
I have an AS2 to Proxy scenario. I am receiving the AS2 message successfully and i have to send a synchronous signed MDN back to the sender. I have done the necessary configurations for this and all certificates are loaded and verified.
The strange part is, once i receive the AS2 message and convert it to XML using content conversion, the communication channel is stopped and again restarted. This messages i could find in application log Log entries. This makes the MDN Asynchronous as the existing HTTPS connection with AS2 sender is lost and so the MDN is not delivered as ASYNC MDN method is not set up.
I need to know what are the system processes that can start and stop a communication channel. I am sure i have not set up any availability time planning for these comm channels and also, they are scheduled manually!
Thanks,
Rashmi.

Hi Debashish,
I am using Advantco AS2 Adapter, and they say it is one of the system processes and not anything with their AS2 Adapter.
Thats why this question. Are there any system processes that can start/stop a communication channel? Atleast I have not come across anything like that.
Thanks for your reply,
Rashmi.

Communication Channel and JMS

Hello Experts,
I am a newbie to SAP Xi so my question may sound a bit odd: please advise me.
I would like to send a JMS after the end and successful completion of a Communication Channel.
This Communication Channel is doing sync of an external DB with the SAP DB.
I have setup a free JMS server from Sun (version 4.3). My environment is full Windows 64bits.
I know I need to setup the proper JMS drivers in SAP Xi to allow the use of the JMS module adaptor,
but I'm unsure of the steps I need to follow to change the behavior of my communication channel.
Please suggests Experts.
Thanks and Regards,
Saule 73

Thanks a lot for this documentation!
it has proven very usefull for the implementation of a JMS object inside Xi.
This is definitely a step forward...
But I am still missing an element in the puzzle :
Once I have:
_ a configured JMS server (Sun 4.3),
_ the JMS object (sender) defined in SAP,
_ a communication ready to be used,
If I want the communication channel to trigger the sending of the JMS, must I :
_ write down a Entreprise JavaBean module to do the trick (to be included into the communication channel)
OR
is there another way to ask the Communication channel to do it (preferably not involving to much development)?
Thanks experts,
Saule73

How to get IDoc Metadata and Structure without connection to sender

Hello folks!
Is there any chance to receive and process an IDoc with PI without having loaded the IDoc
Metadata with a direct connection from the sending SAP System? Can't this be done by hand?
Or is it not possible to bypass the IDoc Adapter and send the Idoc via an RFC?
Thanks in advance
Gunnar

Hi!
The idea behind the question is the following:
Usually any NONE-SAP RFC-Server of an Integration Tool can receive IDocs just by
beein registered at the sending system. The way you get the metadata into the
receiving Integration tool is an complete different story an can be done by
manually or by doneload the metadata from the DDIC just one time by hand.
But with PI you need to connect to the sending SAP System directly
with idx1 and by importing the structure out of the Integration Builder, right?

Monitoring and sending alerts for IDocs

Hi ,
I have Idoc scenarios both outbound and inbound.
My requirement is that whenever an Idoc goes into error state an alert should be sent to a specified person automatically.
Please also let me know ways to reprocess Inbound and outbound Idocs.
Thanks

Hi,
Your question is mainly for ECC, than for PI...
but you can acheive it, for instance, by creating an abap program which checks the IDoc status, and send an email to a list of persons you determined for instance in a Ztable for each idoc (message type + idoc type + idoc extension). You can scheduled this program by creating a SAP job (tcode SM36).
Another way could be to add an abap enhancement in each idoc process (inbound / outbound) to check the status of this idoc and send an email. But...
Personally, I prefer the 1st solution, as the program is scheduled, you can group several idoc errors and send only one email (!). Keep in mind this case: among 1000 inbound idocs, 750 are in error, because of a bad or a missing data in the source system... What 's the result with the 2nd solution?... it's a spam of 750 emails to the emailbox of your employees (!!!. Not sure they will appreciate...
To retreat Idoc, you can use tcode BD87. Do not give this tcode to all employees, but only to some key users, to avoid that an employee retreat several idocs which are not in its scope (because he/she did not a godd selection in the selection screen) and which should be not be retreat now (exm due to a fiscel year).
regards
Mickael

IDOC Acknowledgement and Header Mapping

Dear all,
I've got the following scenario:
SAP 4.6C is sending many different IDOCs to XI 3.0 (SP14).
On XI side there are several integration processes, business systems and business services receiving the IDOCs.
I want to create IDOC acknowledgements and send them back to SAP system.
For one integration process I was able to successfully create and send back an acknowledgement by following the steps described in the very good blog:
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Now I want that every integration process/business system/business service is sending back an acknowledgement with the <b>same</b> logical system name (meaning "this acknowledgement is coming from XI").
As it is not possible to enter the same logical system name for more than one process I created a receiver agreement with:
Sender Service = the integration process
Receiver Service = the SAP 4.6C business system
Receiver Interface = ALEAUD.ALEAUD01
Receiver Communication Channel = IDOC receiver channel called "Ack_IDOC_Receiver", existing in SAP 4.6C business system and pointing to this system
Additionally I created a header mapping in this receiver agreement where I set the Sender Service to the business system of the XI system.
Unfortunately the tests showed to me that obviously the header mapping (maybe even the whole receiver agreement) is being ignored completely as no Acknowledgement IDOC will be created. Instead I get the error message "Unable to convert sender service to an ALE logical system".
I also played around a bit with the options "Apply Control Record Values from Payload" and "Pass Sender value from Payload" but this didn't make any difference.
Why is the header mapping not replacing the sender service in the acknowledgement message?
Best regards,
Tobias

Tobias,
we have the same Problem.
we´re sending with Receiving Partner "12345" and the IDoc in the target System is filled with the standard SAP Value maybe the one configured in the SDL.
We have configured our IDOC_REceiver with a mark on "Apply Control Record Value from payload".
If you have a look at the SAP Helpfile you will find out that some header fields are not be changeable and get the value from sap.
like IDOC-Number, Receiving Partner and maybe the sender service ???
Regards,
Gordon

Communication Channel IDOC tipy and SENDER

Similar Messages

Maybe you are looking for