Min coding/unit-testing time for 4-exit/2-BADI project ???

[Former Member]

Assume some customer project requiring the coding of 3 customer-exits, 1 customer subscreen, and 2 BAdI's. Assume insert/updates into three SAP tables as part of the back-end.

What is the minimum time for coding/unit-testing that such a project would be assigned in your shop, assuming total lines of code is < 1000. This does not include initial identification of the proper exits/BAdI's via SE18/SMOD.

Thanks for any opinions you care to share ...

djh

[RichHeilman]

I agree, it really depends on the skill set of the developer. Of course, even a seasoned developer could spend days trying to figure out how he wants to implement(as the saying goes, there is always 3 ways to accomplish the same thing in SAP) and to find the hooks where he can put his code.

I have been working on a project for about a month(the OE user exits) and I have gone thru multiple iterations of coding and testing, breaking, recoding, testing, breaking, etc. To the point that I actually scrapped the whole thing and went a different way. Usually this kind of thing is not considered when giving a time line or a estimated due date.

Fortunatly, I live in a world, where I can say, it will get done, when it gets done(of course there is some pressure, but I don't want to deliver junk) or with my famous words at my company........

<i>Can this be done?</i>

Yes, we can do anything with time and money.

<i>How long will it take?</i>

2 weeks.

Even if I think it is a 1/2 days work.

Regards,

Rich Heilman

[thomas_jung]

> <i>How long will it take?</i>

> 2 weeks.

> Even if I think it is a 1/2 days work.

Ah the famous <a href="http://www.urbandictionary.com/define.php?term=Scotty+Principle">Scotty Principle</a>. What ABAP programmer hasn't put that to good use.

[ChrisSolomon]

Through years of experience and much of that in consulting, I have been trained to provide only one answer....

IT DEPENDS.

😃

[suresh_datti]

>>What is the minimum time for coding/unit-testing ?

That could be purely relative.. I might take 3 days while Rich could knock it off in half-hour.. It really depends on the person who actually does it & how good/bad the Spec is..

leaving that aside, I would say a weeks' time is fair enough.. this is just for development.. more often than not, you will end up making changes with each Functional Unit Test.. In a 3 system landscape, you will have better data in QA & hence the real 'test' will be there.. you could be going back & forth between Dev and QA before signing off to Prod.

~Suresh