Skip to Content

Interface determination based on a custom field on payload


We added a custom field (a flag) to a standard enterprise service TransportationOrderRequest_Out hoping to use it for routing in PI, i.e. determine a unique interface / mapping if this flag has a certain value. However it turns out there is a constraint that only standard fields can be used for routing / interface determination. Is this true and if so could someone advise if there is a work around?

Best Regards,


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Sep 13, 2016 at 10:25 PM

    Hi KC,

    you can use the custom field for routing, but how you added the custom field in standard structure? You need to use the enhanced data type to add the custom field in PI and then use in ECC (if it is related to proxy).

    refer the below link for standard content enhancement

    XI/PI: Data type enhancements (standard Business Partner)



    Add a comment
    10|10000 characters needed characters exceeded

    • Praveen,

      The namespace on your screenshot looks like a custom one, could you please confirm? Our interface is in the standard namespace and we don't want to change it. In this case if we choose custom software component in receiver determination will it work if the interface triggered is in the standard namespace?

      Best Regards,


Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.