How to handle package in custom model development

[Former Member]

Hi all

I explain my doubts.

I am developing a large set of transactions custom to create a sort of model for installation. These developments have been made on a first server (I'll call it EC1). I create all development in a package and then I carried the package onto another develop system (I'll call it EC2). There is no connection between EC1 and EC2; transport has been made via server filesystem.

First problem: when I carried the CR, the system does not allow me to change package contents (report and so on) because the system of objects does not match with current system. Actually it's right because on my developments I see that owner is the user that I used for create reports on EC1 (that does not exists on EC2) and the system is EC1 .

Searching on forums I read that with SE03 I have to manually change owner and system of objects. And this will solve my problem. And actually did it.

My doubt is: I am writing something that in future will be installed on several server. This is not a "one-shot" custom development. The package should be transported on many other customer's development system where each time I will probably make changes on report (depending from customer's needs).

It seems on each machine I will have  to use SE03 to change owner and system before doing changes.

I don't think that I am doing correctly. Also because SE03 is very boring because I have to manually select one by one element to change (about 700 line to select manually) and then for each element is shown a popup where Owner and System can be changed (about 700 popup!). The question is:

Can someone please explain me how should I behave for create a report that will be carried onto several development system (where change will be done before going on quality server and so on .. ) ?

[ThomasZloch]

You should have one central box where your developments originate. In the target systems, you don't have to change the original system, you changes could also be done using the modification assistant.

You could also look into creating enhancement spots for the parts that need to be adjusted for each customer, study available information for the enhancement concept.

Are you using your own /ABCD/ type namespace? This is could also be beneficial to avoid name conflicts.

Finally, in order to mass change the original system and owner in SE03 for several objects, type in MASS as function code after you have marked a block of entries in the tree view, and see what happens

Thomas

[Former Member]

Let me start with a GREAT THANK YOU for mass hint... when I saw the popup I was fainting from happiness!

For what about

You should have one central box where your developments originate. 

The problem I have is that in theory I shall have "more" central box as develop server: you mean that each customer develop server I will install should be installed as successive node of my develop server?

And can you please explain this concept :

Are you using your own /ABCD/ type namespace?

For 5 years I wrote program always in 'server chain' dev->test->prod. What I always do is create in my Zpackage my Ztable with my Zdatatype used in my Zreport called from my Ztransaction. I don't think Z is your meaning of namespace..

Thanks for your help!

Regards

Gabriele

[ThomasZloch]

You're welcome, I was surprised too when I read about this MASS feature some time ago, as it is not contained in the menu.

Maybe I understood wrong, but it sounds like you are developing an application that should be installed in various, separate customers' landscapes. Normally, at least as I know it, these are installed by delivering a control and data file containing a transport request that can be added to the import queues of the customer's systems and then imported into each box. The origin where the transport request is created is your own development box.

In order to avoid naming conflicts of Z-objects, it can make sense to register your own namespace with SAP. These have the form e.g. /GABRIELE/, so a data element could be called /GABRIELE/BLDAT, and there will never be a conflict as you might face when you call it ZBLDAT.

Read more about it here:

http://help.sap.com/saphelp_nw70/helpdata/en/57/38dec24eb711d182bf0000e829fbfe/frameset.htm

Thomas

[Former Member]

Thank you very much. You have been clear and kind.

[former_member213851]

Hi Gabriele,

Instead of modifying the Owner on each system EC ,EC2 , you may develope a Z report in which you will give a file with List of Objects and Type from Selection screen and the Owner name and Tranport Req No ( Used for importing changes from one system to other) .

Now GUI_UPLOAD will transfer ths Excel file contents to Internal table say ITAB,  which you have to use for direct database update on table E070 and E071 to change Oener of objects with the help of Transpoer Request (TRKORR) which is primary key .

Eg: gt_data  will have excel sheet  has contents

LOOP AT gt_data INTO wa_data.

*--Certain checks to determine Transport No from object and then Owner of that object is changed to

*--owner from selection screen

   E070-AS4USER = wa_data-AS4USER.
    MODIFY E070 FROME070.
    COMMIT WORK.

ENDLOOP.

Best Regards,

Sachin