Hi everyone,
in our organisation , we are migrating from R3 to ECC 6 and with this comes the new concept of packages... Also , we have put in place solution manager and are planning to use solar01 to document our solutions.
At this moment , our development objects are really structured in a few development classes but the structure is really flat and not too useful by any means.
We are planning to start using packages to structure our code differently. We we're thinking of maybe structuring packages in a similar fashion to the one in solution manager ... that being
Product , Scenario, process , task ... and giving the program an actually meaningful name like ZSALESDOCUMENTX rather than a coded name like Z7CGI1001 ...
I'm wondering how others have structured their programs and if you have links to guidelines and examples that could help us put together good guidelines in regards to this.
Also, does it make sense to follow the solution manager documentation structure... ? I'm not sure about that. It could help people find documentation for the program but then again, there could be technical problems in structuring the code this way (transports... etc).
Thanks.