Re: Prefix not mapped

Hi Lars,

most of the namespaces are already part of the B1i namespace list, you don't need to define them explicitly at the inbound again.

The already embedded namespaces are automatically created. E.g. after creation of an new xform you can see them directly added into the xsl file as attributes of xsl:stylesheet.

=> In your step inbound definition you only need to add those which are not explicitly listed in xsl:stylesheet.

In the inbound step definition, please be aware that the namespaces must not be defined twice using different prefixes (for all scenario steps):

• Don't use different prefixes for the same url in different scenario step inbound definitions.
• Don't use different urls for the same prefix in different scenario step inbound definitions.

E.g. the following namespace is used in the sap.B1Mobile scenario: xmlns:b1mb="http://tempuri.org/"

• You must neither define the following in another scenario step  xmlns:tem="http://tempuri.org/" (same url but different prefix) nor xmlns:b1mb="http://tempuri.com/" (same prefix but different url).
• You need to reuse xmlns:b1mb="http://tempuri.org/"for all other scenario steps.

Best regards

Bastian

P.S.: In a xslt mapping you can also avoid explicit namepace usage by applying the following construct:

/*[local-name()=&apos;<name_of_your_element>&apos;],

e.g. select="/*[local-name()=&apos;Msg&apos;]/..." instead ofselect="/vpf:Msg/..."