cancel
Showing results for 
Search instead for 
Did you mean: 

reg problem in Runtime Constants $SenderService

Former Member
0 Kudos

Hi

Have a problem , I am using ABAP XSLT Processor mapping (I have used message split for this particular scenario i.e. input is single file and output is multiple file)

Instead of hard coding the sender service i tried to use Runtime Constants $SenderService but this was not working .

For one to one scenrio it is working fine ,also in JAVA XSLT Processor it is working fine ....

can any one help on this

Ramamurthy

Accepted Solutions (0)

Answers (1)

Answers (1)

Shabarish_Nair
Active Contributor
0 Kudos

are you testing your XSL program in XI or outside ?

These runtime consants can be accessed only inside XI.

also,

<i>

If you want to access one of the constants in the XSLT program, you first have to declare the constant as a parameter, for example:

<xsl:param name="MessageId" /></i>

ref: more @

http://help.sap.com/saphelp_nw04/helpdata/en/73/f61eea1741453eb8f794e150067930/content.htm

Former Member
0 Kudos

Hi Shabarish,

I have tested this in XI only , I have also declared the param as

<xsl:param name="SenderService" />.

This is working fine

where us in one scenario I am using message split i.e. Input is single file and delivery is 3 files (used 3 different channels in the reciver) in this particular scenrio alone i am facing this issue.....

Shabarish_Nair
Active Contributor
0 Kudos

well the runtime constants cannot be accessed if it is a message split.

Former Member
0 Kudos

this was working fine in XSLT mapping JAVA proccessor.

Dont know why this is not working with XSLT mapping ABAP processor

rams