Transport binding consuming CICS WS

I have been trying for more than a week to consume a WebService from an IBM CICS Transaction Server. I have tried with .NET, AXIS, and XML Spy. They all work.
I have editted the proxy generated (standalone and deployable) in order to more or less match the tags that are sent by the other programs/frameworks.
However, it seems, atleast from what I can gather, the transportation binding might be at fault. Does anyone have any idea where to get information about how to implement a transportation binding change and/or documentation on how to modify this from the proxy.
Thanks in advance

Hi Krishna,
In WS Navigator, you will have an option to change the invocation parameters. Change it to other options and try out. It should work. Have faced this problem long back in 7.2 SP2 and solved it that way. To solve it permanently you may need to do a upgrade.
Best regards,
Bala

Similar Messages

PI - Invalid transport binding settingsjava.lang.NumberFormatException ?

Hi Experts,
    I have developed an InBound ABAP Proxy to be called as Web-service from some outside application e.g JAVA etc.
    some of the data fileds which is used in this proxy is having a defination of XSD DECIMAL.
   Whenever i am calling this Proxy in ABAP environment. SPROXY---> Test Proxy it is working fine without any error.
But when i goto NWDS--> WSNavigator it gives me the following error.
Invalid transport binding settingsjava.lang.NumberFormatException.
and it ask for HTTP Authentication. after submitting the userid / password it goes ahead & give the desired result.
But when we are calling this Web-Service from JAVA Environment it gives the above mentioned error.
What could be the reason. Pl. suggest!!!!!!!!!
Regards,
Umesh

Hi,
could you please provide some more info for some clear understanding.
As per i could understand: you have a JAVA application acting as a consumer application and you have developed a ABAP proxy acting as a provider application.Now you have some issues with decimal datatype in provider proxy side.
could you please say where from you have created the inbound interface ..is it created in ESR(IR) of PI or in CE or you have got it as a external definition from somewhere else.
If PI then, is it PI7.1?
cheers,
Abhishek.

Error when using Variable Transport Binding in Sender Mail Adapter

Hi,
I am using the Sender Mail Adapter to receive an email, convert the attached tab delimited text file into xml and map it to an IDOC.
I am using PayloadSwapBean and MessageTransformBean in order to do this, and this all works perfectly.
I am now trying to access the Adapter Specific Message Attributes to retrieve the SHeaderFROM attribute from the message and map it to a field in the idoc.
However when I check the "Variable Transport Binding" option in the Advanced tab of the mail adapter, the message no longer goes through to SXMB_MONI and I get the following error in the Java logs.
Transmitting the message to endpoint http://sapserver:53500/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during parsing of SOAP header.
Any ideas why this is happening?
Thanks,
Brad

Hi Luciana,
Honestly, I cant really remember how or if it was resolved and I was just helping out on the issue, but another consultant continued with it, so unfortunately I cant be any help on this.
Good luck!
Cheers,
Brad

Mail sender adapter with Variable Transport Binding doesn't work

Hi,
we have PI/700 SP7.
An external partner sends an email with one attachment (a simple csv file).
I take "PayloadSwapBean" (with swap.keyName = payload-name) to get the attachment.
Both, the Adapter-Specific Message Attributes indicator and the Variable Transport Binding indicator are set.
I set the mail package format indicator too.
What I need is the sender, receiver and subject of the mail plus the attachment.
Unfortunately it is not possible to read in the email with this configuration - I get an error.
If I unset the Variable Transport Binding indicator - I get the email but without "sender, receiver and subject" in "SHeaderFROM, SHeaderTO, SHeaderSubject". The "mail package" is overwritten by the attachment.
Is it a problem of the namespace "http://sap.com/xi/XI/System/Mail"?
Do I have to define this namespace or do I have to import a content (SAP BASE 700, SP7 is imported)?
Please help...
Regards
Wolfgang

Hi Wolfgang,
I hope it is not due to the namespace.
This might help you.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9e6c7911-0d01-0010-1aa3-8e1bb1551f05
Need some Guide regarding Configuration of Sender Mail Adapters....
Regards
Agasthuri Doss
Message was edited by: Agasthuri Doss Baladandapani

SOAP Use Adapter-Specific Message Properties and Variable Transport Binding

Hi Friends,
   I am new to use to Soap Adapter. Please help me out bellow doubts.
   1.When you use Use Adapter-Specific Message Properties and Variable Transport Binding .
   2. Where exactly we r using below parameters.
Remote User : (technical name: SRemoteUser )
Remote Host : (technical name: SRemoteHost )
SOAP Action (technical name: SHeaderSOAPACTION )
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:
Variable Header : (technical name: XHeaderName1 )
Variable Header : (technical name: XHeaderName2 )
Variable Header : (technical name: XHeaderName3 )
Thanks&Regards
G.Bhanuprakash

Hi,
   1.When you use Use Adapter-Specific Message Properties and Variable Transport Binding .
SAP Help says both are needed to be checked when you want to process adapter attributes
Configuring the Receiver SOAP Adapter - SAP NetWeaver Exchange Infrastructure - SAP Library
These attributes can be get/set using dynamic configuration and their technical names are what you have pasted:
Remote User : (technical name: SRemoteUser )
Remote Host : (technical name: SRemoteHost )
SOAP Action (technical name: SHeaderSOAPACTION )
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:
Variable Header : (technical name: XHeaderName1 )
Variable Header : (technical name: XHeaderName2 )
Variable Header : (technical name: XHeaderName3 )
Remote User - the username used to send a message to the adapter engine using SOAP
Remote Host - hostname which the remote user used
SOAP Action - SOAP Action of the XI webservice (sender) / SOAP Action of the receiver webservice
Variable Headers are additional key-value pairs in the HTTP Header that could be accessed in the XI Header using dynamic configuration. The limit is only three though.
Regards,
Mark

Variable Transport Binding - Soap Sender

Hello all,
I'm trying to retrieve a parameter from the HTTP header of a SOAP request.
I have created a SOAP sender communication channel, checked "Set Adapter-Specific Message Attributes" and "Variable Transport Binding", and entered the name of the parameter in Variable Header (XHeaderName1).
When I send the SOAP request, DynamicConfiguration exists with all standard parameters, but there is no XHeaderName1...
If I try the same with sender HTTP adapter, it works fine.
In the other way, if the dynamic configuration parameter XHeaderName1 already exists, and I try to add it in a HTTP header parameter in a receiver SOAP CC, that works.
Does somebody know why this doesn't work in the sender one?
Thanks,
Greg
PS: I'm using PI7.0 SP14

Hello,
I can see in dynamic configuration, with the namespace http://sap.com/xi/XI/System/SOAP, the standard HTTP parameters like SServerHost, SRemoteUser, etc...
But if I add a HTTP header parameter in the SOAP request, and I try to retrieve it with the SOAP sender CC, the parameter is not added in the dynamic configuration. If the name of the added HTTP header parameter is "TestParam", I put "TestParam" in the XHeaderName1 field of the sender CC, but the value is not added in the dynamic configuration. This is my problem.
Thanks,
Greg

Transport Binding in ABAP Consumer Proxy

Hello Gurus,
I am trying to call a webservice using ABAP Proxy in Netweaver SPS 15.
We donot have XI in our landscape.
This is a siebel web service ( on our intranet ) and the url to call is
http://abc12345.abc.com:80/eai/wsprj?SWEExtSource=WebService&SWEExtCmd=Execute&Username=TEST_USR&Password=TEST_USR
I tried to create a logical port ( Transaction LPCONFIG ) and put this whole URL and it works fine.
But abc12345 will be different on QA & PRD systems so I have to change in DEV and transport it which is not optimal solution.
I tried creating an HTTP Destination and put this into LPCONFIG with a URL suffix of
"eai/wsprj?SWEExtSource=WebService&SWEExtCmd=Execute" and it fails with Soap Error.
Is the special character "?" or "&" causing the issue??
I also tried to create a logical port in Soamanager using manual config and put "eai/wsprj?SWEExtSource=WebService&SWEExtCmd=Execute" in URL access path and it results in Soap error at runtime.
I tried WSDL based configuration with URL also but cannot even save the port as it gives error is HTTP destination creation. I also tried WSDL based configuration with local file. It creates the port but ignores the "?SWEExtSource=WebService&SWEExtCmd=Execute" part of URL which again gives saop error at runtime.
Any pointers on where I am going wrong. I want to be able to change these runtime parameters in QA/PRD either using HTTP destination with LPCONFIG or by creating a logical port using soamanager.
Thank You
Sanjay

i can't open your URL link.Can you send WSDL.I think there is some error in URL or in WSDL.When you create
logical port in LPCONFIG you can give URL directly just putting ?WSDL at th end of URL and When you click operation tab you will find SOAP Action Name .Provide same in SOAP Action.
Regards
Snehasish
Edited by: Snehasish Das on Nov 23, 2008 12:33 PM

Change webservice client transport/binding

I am migrating web service client generated by clientgen from 7.0 to 8.1. 7.0 client uses weblogic.webservice.binding.soap.HttpClientBinding which works directly with sockets and is fine for me. But 8.1 uses weblogic.webservice.binding.http11.Http11ClientBinding which works with java.net.HttpUrlConnection that requires proxy being set in java system property which is system wide and I cannot use that. HttpClientBinding uses system wide setting as well but it is webservice client specific at least.
So I want use HttpClientBinding in 8.1 as well. I am able to change it by calling
BindingFactory.getInstance().register("http11", weblogic.webservice.binding.soap.HttpClientBinding.class);
but this is again system wide setting which I am afraid of because of influencing other WS clients not using proxy. Is it possible to do it somehow in per client basis?
Injecting custom Binding info with getTransport returning "http" or in some other way.
Alternatively any way allowing me to set proxy on per WS client is solution for me

Hi Dahran,
SCC7 is for post import.
first you have to import the transports generated during the export into your client.
STMS. Go to your import queue and choose in the menu
Extras ->Other requests add
Fill in the transport number of one of the generated transports during the export. (something like <SID>KX0000x)
<b>After</b> the import you have to perform the SCC7

Usage of Variable Transport Binding(Receiver SOAP adapter) in multimapping

Hi All,
Mentioned below is the flow of the scenario that I am facing issues with:
ECC -> PI (A) -> PI (B) - Receivers(1,2,3..n)
I am working on PI(A).
An Idoc containing multiple Plants is triggered which is mapped to an XML in PI(A).
Depending on the number of Plants in the Idocs, that many XMLs are created in PI(A) using multimapping.
These XMLs are then sent to PI(B) which would route it to different receivers.
But PI(A) should send the party name to PI(B) for routing.
For this I am using dynamic configuration. If there are 'N' party names based on 'N' plants, always the last part name is being sent to PI(B).
Is it possible to send all the party names associated with each XML(/plant) without overriding?
As mentioned in the below table, an Idoc is triggered with 3 Plants. 3 XMLs are generated each for a different party. But only the last party i.e. C is being sent to PI(B) using dynamic configuration overriding A and B.
Plant
Party Name
Output
1
A
2
B
3
C
C
Please help me to resolve this issue.
Regards,
Vishal

Hello,
DC is not supported in multimapping.
But, where exactly u want to send the party name? In the xml file u want that party name to be there?
If yes, then there are 2 options either use AM as shown below or u can use variable substitution (search SDN u will find quite a few blogs/wiki on the same)
A new approach: Multi-mapping Dynamic Configuration using a generic custom module
Thanks
Amit Srivastava

Variable Transport binding - SOAP Sender Adapter

Hi All
have a scenarion where Sender System is sending Custom SOAP Header as below into P through SOAP Sender ChannelI.
And the requirement is to access the values coming in Header fields, example within Message Mapping need to Map Headername1 value to Outgoing structure.
<soapenv:Header>
     <Header1>S1</Header1>
     <Header2>S2</Header2>
     <Header3>S3</Header3>
</soapenv:Header>
   <soapenv:Body>
     u2026..
   </soapenv:Body>
Have checked the Paramter KEEP Headers in SOAP Adapter and in Adapter Specific Message Attributes have defined the following
Variable Header (XHeaderName1) = Header1
Variable Header (XHeaderName2) = Header2
Variable Header (XHeaderName1) = Header3
Now need to know what should be mentioned in the UDF in the Message Mapping for accessing Dynamic Configuration. Will these headers mentioned will be a part of Dynamic Configuration or not ?
Using the below UDF and its failing in Message Mapping - kindly suggest the corect way of achieving the same
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/SOAP", "XHeaderName1");
String value = conf.get(key1);
return value ;
Appreciate response in this regard
//Swetank

Hi Abhishek
Its failing at runtime at Message Mapping stage. The real problem is that I can't see the Header1 in my Dynamic Configuration header - it has all the other fields like SServerHost, SRemoteUser, but not my Header1 (S1) field. Thus either the UDF is wrong or any configuration in SOAP Sender Channel needs to be adjusted.
Further I am not sure whether Custom SOAP Header fields can be a part of Dynamic Configuration or they only show fields which are part of HTTP header.
//Swetank

Consuming a Webservice on WAS 6.40

Hello,
i try to consume a Webservice created with the Webservice Creation Wizard. I have configured the logical port and i created the client proxy. But when i run the test program with the crated proxy i retrieve the following error:
(id=SOAP:111): Unallowed RFC-XML Tag (SOAP_EINVALDOC)
In the RFC-Trace the following log is displayed:
INFO 16:34:40: SOAP Transport binding CL_SOAP_HTTP_TPBND_ROOT <
XRFC> ->IF_SOAP_TRANSPORT_BINDING~RECEIVE() Try to receive message <
XRFC> <
XRFC> INFO 16:34:49: SOAP HTTP Binding CL_SOAP_HTTP_TPBND_ROOT->HANDLE <
XRFC> STATUSCODE() Received return code 500 ( Internal Server Error ) <
XRFC> <
XRFC> ERROR 16:34:49: SOAP Message CL_SOAP_MESSAGE->IF_SOAP_MESSAGE <
XRFC> PART~INITFOR_DESERIALIZE() A SOAP Runtime Core Exception <
XRFC> occurred in method XP_READ_TAG of class CL_SOAP_XP at position id <
XRFC> 1 with internal error id 111 and error text Unallowed RFC-XML Tag <
XRFC> (SOAP_EINVALDOC) (fault location is 1 ).
What's wrong here? Someone can help me?
Thanks for your help!

Hi Adriano,
Here is the link I think you're looking for:
http://help.sap.com/saphelp_nw04/helpdata/en/4f/2e6a52c3cdc44d83169b181a9c62ba/frameset.htm
Hope it helps.
Thanks,
Marty

Consuming a Web Service via SSL with Basic Authentication

Hello,
I have a simple web service (returns a parameter value) and want to consume it. Therefore I have generated a proxy for its in Netweaver Studio SP13.
When I set up the web service to be accessed via HTTP and Basic Authentication (Username/Password), everything is fine. When I set up the web service to communicate via HTTPS, I get the following error message in my client:
java.rmi.RemoteException: Service call exception; nested exception is:
     java.lang.NullPointerException
     at priv.senw04.wsproxy.multisec_ssl.SSLBindingStub.pingText(SSLBindingStub.java:87)
     at priv.senw04.wsproxy.multisec_ssl.SSLBindingStub.pingText(SSLBindingStub.java:96)
     at priv.se.wsclient.MultiSecSSL.main(MultiSecSSL.java:38)
Caused by: java.lang.NullPointerException
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.disconnect(HTTPSocket.java:625)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.closeSession(HTTPTransport.java:396)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1312)
     at priv.senw04.wsproxy.multisec_ssl.SSLBindingStub.pingText(SSLBindingStub.java:80)
     ... 2 more
Testing the web service with WebServiceNavigator and/or by using a generated WebDynpro Client results in the following error:
000D604C66BE004E0000001300000AFC00040922E0160632 : An error occurred during processing the timestamp. The error was: com.sap.security.core.ws.wss.NoSecurityHeaderException No wsse:Security header has been defined for role soap:finalActor. Please verify the policy configuration..
But my main focus is on the client implementation based on a proxy. Here comes the client's code:
public class MultiSecSSL {
    public static void main(String[] args) {
        try {
            MultiSecuritySSLAuthImpl serviceInterface = new MultiSecuritySSLAuthImpl();
            SSLBindingStub service = (SSLBindingStub)serviceInterface.getLogicalPort(MultiSecuritySSLAuthViDocument.class);
            SecurityProtocol protocol = (SecurityProtocol) service._getGlobalProtocols().getProtocol("SecurityProtocol");
            AuthenticationContext auth = protocol.getAuthenticationContext();
            auth.setIgnoreSSLServerCertificate(true);
            auth.setUsername("cfpcompany");
            auth.setPassword("demo");
            String ret = service.pingText("Called service MultiSecurity via SSL");
            System.out.println(ret);
        } catch (Exception e) {
             e.printStackTrace(System.out);
Here comes the logical port information of the generated proxy:
<?xml version="1.0" encoding="UTF-8"?>
<LogicalPorts Name='MultiSecuritySSLAuth' InterfaceName='priv.senw04.wsproxy.multisec_ssl.MultiSecuritySSLAuth'>
<LogicalPort Name='SSLPort_Document' Endpoint='https://192.168.129.76:50001/MultiSecuritySSLAuth/SSL?style=document' BindingName='SSLBinding' BindingUri='urn:MultiSecuritySSLAuthWsd/SSL/document' BindingImplementation='SOAP 1.1 HTTP Binding with Attachments' StubName='priv.senw04.wsproxy.multisec_ssl.SSLBindingStub' Default='true' InterfaceName='priv.senw04.wsproxy.multisec_ssl.MultiSecuritySSLAuthViDocument' Original='true' Valid='true'>
    <globalFeatures>
      <Feature Name='http://www.sap.com/webas/630/soap/features/headers/' Provider='SoapHeadersProtocol' Original='false'>
      </Feature>
      <Feature Name='http://www.sap.com/webas/630/soap/features/session/' Provider='SessionProtocol' Original='false'>
        <Property Name='SessionMethod' Value='httpCookies'>
        </Property>
      </Feature>
      <Feature Name='http://www.sap.com/webas/630/soap/features/authentication' Provider='SecurityProtocol' Original='true'>
        <Property Name='AuthenticationLevel' Value='None'>
        </Property>
        <Property Name='AuthenticationMechanism' Value='HTTP'>
        </Property>
        <Property Name='AuthenticationMethod' Value='BasicAuth'>
        </Property>
        <Property Name='SupportsSSO2Authentication' Value='false'>
        </Property>
      </Feature>
      <Feature Name='http://www.sap.com/webas/630/soap/features/transportguarantee' Original='true'>
        <Property Name='Level' Value='No'>
        </Property>
        <Property Name='TLSType' Value='SSL'>
        </Property>
      </Feature>
    </globalFeatures>
    <localFeatures>
      <Operation Name='pingText'>
        <Feature Name='http://www.sap.com/webas/630/soap/features/wss' Original='true'>
          <Property Name='RequestPolicy' Value='Signature'>
          </Property>
          <Property Name='ResponsePolicy' Value='None'>
          </Property>
        </Feature>
        <Feature Name='http://sap.com/webservices/authorization' Original='true'>
        </Feature>
      </Operation>
    </localFeatures>
</LogicalPort>
</LogicalPorts>
To me, this looks consistent. Any idea, what is misconfigured on my machine ?

Hi Martin,
that is exactly, what I did.
- Change Web Service Configuration in IDE
- Build and Deploy the Service to my local Server
- Check Service in Visual Administrator
- Deleted and Regenerated the Standalone Proxy
- Deleted and Recreated the link between CLient and Proxy Project in IDE
- Started Client
Here comes the section of the ws-deployment-descriptor.xml of the service. For me, it matches, what the proxy generated.
<webservice>
    <guid>ed8363_10876a54b6d__7fe9_192_168_129_76_1135862193037</guid>
    <ejb-name-temp>MultiSecWSBean</ejb-name-temp>
    <webservice-name>
      <namespaceURI>urn:MultiSecuritySSLAuthWsd</namespaceURI>
      <localName>MultiSecuritySSLAuth</localName>
    </webservice-name>
    <webservice-internal-name>MultiSecuritySSLAuth</webservice-internal-name>
    <standard-namespaceURI>urn:MultiSecuritySSLAuthWsd</standard-namespaceURI>
    <ws-configuration>
      <configuration-name>SSL</configuration-name>
      <ejb-name>MultiSecWSBean</ejb-name>
      <service-endpoint-name>
        <namespaceURI>urn:MultiSecuritySSLAuthWsd</namespaceURI>
        <localName>SSLPort</localName>
      </service-endpoint-name>
      <wsdl-porttype-name>
        <namespaceURI>urn:MultiSecuritySSLAuthWsd</namespaceURI>
        <localName>MultiSecuritySSLAuthVi</localName>
      </wsdl-porttype-name>
      <webservice-definition-ref>
        <package>com.technidata.cfp.i3rdparty.cfpxml</package>
        <name>MultiSecuritySSLAuthWsd.wsdef</name>
      </webservice-definition-ref>
      <service-endpoint-vi-ref>
        <package>com.technidata.cfp.i3rdparty.cfpxml</package>
        <name>MultiSecuritySSLAuthVi.videf</name>
      </service-endpoint-vi-ref>
      <transport-binding name="SOAPHTTP_TransportBinding">
        <wsdl-binding-name>
          <namespaceURI>urn:MultiSecuritySSLAuthWsd</namespaceURI>
          <localName>SSLBinding</localName>
        </wsdl-binding-name>
      </transport-binding>
      <transport-address>/MultiSecuritySSLAuth/SSL</transport-address>
      <global-features>
        <feature name="http://www.sap.com/webas/630/soap/features/transportguarantee" protocol="SecurityProtocol">
          <property name="TLSType" value="SSL"/>
        </feature>
        <feature name="http://www.sap.com/webas/630/soap/features/authorization" protocol="SecurityProtocol"/>
        <feature name="http://www.sap.com/webas/630/soap/features/authentication" protocol="SecurityProtocol">
          <property name="AuthenticationMethod" value="BasicAuth"/>
          <property name="AuthenticationMechanism" value="HTTP"/>
          <property name="SupportsSSO2Authentication" value="false"/>
        </feature>
      </global-features>
      <operation-configuration uniqueViName="pingText(java.lang.String)">
        <transport-binding-configuration>
          <input>
            <property name="soapAction" value=""/>
            <property name="encodingStyle" value="http://schemas.xmlsoap.org/soap/encoding/"/>
          </input>
          <output>
            <property name="encodingStyle" value="http://schemas.xmlsoap.org/soap/encoding/"/>
          </output>
        </transport-binding-configuration>
        <feature name="http://www.sap.com/webas/630/soap/features/wss" protocol="SecurityProtocol">
          <property name="RequestPolicy" value="None"/>
          <property name="ResponsePolicy" value="None"/>
        </feature>
        <feature name="http://sap.com/webservices/authorization" protocol="SecurityProtocol">
          <property name="security-roles">
            <property name="role1" value="use_multisec_service"/>
          </property>
        </feature>
      </operation-configuration>
    </ws-configuration>
</webservice>
Regards,
Stefan

What is difference between transport protocol and message protocol

what is difference between transport protocol and message protocol
please give definition and small explanation

Hi,
Transport protocol gives information about outside of message details, kind of system, security details.
A transport protocol is a network protocol that has the capability of transferring some payload from one node to another, thus providing some level of transparency from the underlying network.
Transport protocols are used as a mechanism to move payloads around a network. Typically, a payload will have a transport binding associated with it. For example, SOAP (acting as a payload) has a predetermined binding for HTTP (a transport protocol).
Some common transport protocols include: HTTP, HTTP-R, SMTP and BEEP.
Message protocol gives you an idea of message type XI payload
http://help.sap.com/saphelp_nw04/helpdata/en/b6/0b733cb7d61952e10000000a11405a/content.htm

SAP PI: Using Variable Header Binding in Receiver Mail Adapter

Hello,
I try to use Variable Header Bindings in the Receiver Mail Adapter. Therefore I wrote the following User-Defined-Function in a mapping:
Java Function Start -
DynamicConfiguration conf = (DynamicConfiguration) container
    .getTransformationParameters()
    .get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create(
    "http://sap.com/xi/XI/System/Mail",
    "XHeaderName1");
DynamicConfigurationKey key2 = DynamicConfigurationKey.create(
    "http://sap.com/xi/XI/System/Mail",
    "XHeaderName2");
DynamicConfigurationKey key3 = DynamicConfigurationKey.create(
    "http://sap.com/xi/XI/System/Mail",
    "XHeaderName3");
conf.put(key1, new String("Test1"));
conf.put(key2, new String("Test2"));
conf.put(key3, new String("Test3"));
Java Function End -
As expected I see the Attributes and Parameters in the Dynamic Configuration in the SAP XI Monitor:
Dynamic Configuration Informattion Start -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/Mail" name="XHeaderName3">Test3</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/Mail" name="XHeaderName2">Test2</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/Mail" name="XHeaderName1">Test1</SAP:Record>
</SAP:DynamicConfiguration>
Dynamic Configuration Informattion End -
Now I configure my Receiver eMail Communication Channel and set the Variable Header Fields as follows:
   Adapter Specific Attributes: Checked
   Variable Transport Binding: Checked
   Variable Header (XHeaderName1): TSender
   Variable Header (XHeaderName2): TReceiver
   Variable Header (XHeaderName3): TOther
With this configuration I would have expected three new Header fields in the Header of the eMail, the reicever gets. But they are not there.
When I set standard attributes like THeaderTO, THeaderSubject a.s.o this works fine and the values are also set accordingly. Where it the mistake here?
The PI version we are working with is PI 7.0 SP10.
Your help will be highly appreciated.
Thank you,
Steffen

Hi Luciana,
Honestly, I cant really remember how or if it was resolved and I was just helping out on the issue, but another consultant continued with it, so unfortunately I cant be any help on this.
Good luck!
Cheers,
Brad

Purchase order :Stock transport orders: IDOC

Hi
I want send an IDOC to a external non-SAP system as soon as the delivery and picking is done. The non-SAP system would have to trigger a goods issue with reference to a picking number as soon as the goods are issued on the non-SAP system.
Is there a message type for picking and goods issue?

Example:
Plant 'Y' has one Storage Location 'C'.
Plant 'Y' is the MRP Area (SAP ECC) / Planning Location (SAP SCM APO)
Plant 'X' has two Storage Locations 'A' & 'B'.
Plant 'X' is the MRP Area (SAP ECC) / Planning Location (SAP SCM APO)
Initially in Week 01 an APO Deployment generated Purchase Requisition (Distribution Receipt (Confirmed)) exists to order 100 EA from Plant 'Y' into Plant 'X'.
Afterwards for the same Week 01 also a Stock Transport Order is manually being raised & executed in SAP ECC in order to transport 7 EA from Plant 'X' / Storage Location 'B' into Plant 'X' / Storage Location 'A'.
This Stock Transport Order consumes 7 EA of the APO Deployment Purchase Requsitions reducing it to 93 EA (= 100 EA - 7 EA).
This Stock Transport Order of 7 EA within Plant 'X' shouldn't it have had a net zero effect on the requirements situation of Plant 'X', and thus should not have caused any change rg what Plant 'X' requires from Plant 'Y'?
Edited by: SNC User ID on Feb 16, 2012 10:42 AM

Transport binding consuming CICS WS

Similar Messages

Maybe you are looking for