Skip to Content

Extending standard ESR proxy

Hi All,

we have a requirement to extended a standard ESR outbound interface with additional fields. We do NOT have SAP PI as our middle ware and hence have to go for "Data type enhancement" technique. I tried searching for some specific questions, but could not find an answer. Below are the questions: -

1. While doing data type enhancement, I have to create my own namespace which goes under standard "LOCAL" SWC. So, it is good practice to create namespace locally ?

2. If yes, I believe that I will have to manually maintain that first in every system ( QA, pre-prod and prod ) before I transport the data type enhancement under that namespace. Is this understanding correct ?

3. If answer to Q1 is NO, then what are the possible ways. At the moment, the SLD is out Solman Java system. Do we have to create the SWC + namespace there ? Will it possible to import it in S4 system once those are created in Solman?

3. Is there any specific naming convention that SAP proposes for creating own namespace. Could not find any documentation around it. Do share some link which mentions that OR kindly provide what was your thought process in choosing the name space.

Thanks & Regards

Srinivas Rao.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Mar 06 at 03:54 PM

    Hi Rao,

    I have written a step by step guide on how to implement Data Type Enhancements for standard proxy structures. Hopefully this will answer your questions! Check the blog post and leave a comment if you have further questions.



    Add comment
    10|10000 characters needed characters exceeded