Difference in Inside-out and Outside-In development approaches

[Former Member]

Hi,

Can you please tell me difference between Inside-out and Outside-In development approaches. I heard it with respect to adapters and proxies.

[Former Member]

check this out http://help.sap.com/saphelp_nw04/helpdata/en/ce/1d753cab14a909e10000000a11405a/frameset.htm

regards

Pratibha

[Former Member]

Hi Rupesh...

<b>Nice question as a Project Management point of view..</b>

We can go for Interface development in 2 ways..:

1. Create Interface objects in XI and replicate that thing in both sides for further development..

Adv :: You are not dependent on others for XI development....Like in case of Proxies.

Disadvantage : Skill in proxy required..

2. Create RFC/IDoc in end systems and import those in XI for development..

Advantage : People are usually familiar/comfortable with adapter oriented approach rather then adapter less..

Disadvantage : you can't start your work before the end systems have completed their task..Once they have completed then only you can import the RFC/IDoc and proceed..

About deciding the approach : It depends upon teams strength/situation ...Like in one of the project i have worked Project needs to be done by a Consortium of 3 teams from different companies..One for handling legacy one for R3 one for XI..

So we went for Approach 1 as we don't want our work to be dependent on others..

Hope i am clear..

Regards,

[vikas_agarwal]

Hi,

When we uses the interfaces provided by RFC/ BAPI and Idoc then it is called as Inside out approach

And when we creates our own interfaces by creating data types and message types then it is called as Outside-In Approach.

Thanks

[vikas_agarwal]

Hi,

http://help.sap.com/saphelp_nw70/helpdata/en/84/e8763c997fda50e10000000a11405a/frameset.htm

Thanks