topic Re: Transportable Objects in Application Development and Automation Discussions

Transportable Objects

Former Member — Tue, 10 Oct 2006 22:25:32 GMT

How do I know if the Object I'm modifying is a candidate for transport to QA invironment?. Is there any thumb rule?.

Also I did configured ALE/IDOC ( Standard idoc ) to send Idoc to another system. Do I have to transport anything or I have to do it manually in QA?. Appreciate any reponses. Thanks

Re: Transportable Objects

Former Member — Tue, 10 Oct 2006 22:35:44 GMT

Hi ,

Wht i know is when u finish moification and try to save it , it will ask for u to transport r not......i dont think if there is a thumb rule...

Sony

Message was edited by: sony

Re: Transportable Objects

Former Member — Tue, 10 Oct 2006 23:00:08 GMT

Hi Ram,

When an object is saved AND the object has been assigned a PACKAGE name (not a temporary object) the SAP system will ask you to add it to a transport request or at that moment you can create a new transport request.

IDoc's created will be transported. Standard IDoc's are available in the other SAP system (if it's release is the same or higher).

As for ALE, any changes made to it are not transported, nor is there a question for transport.

However, you have a wonderfull transaction BD64 for creating distribution models. Here so-called partner pairs are created and you can maintain several parts for the communication and distribution.

Once you have created a model (always two partners are involved) you can then distribute the model to the partner systems or you can create a transport for them.

In the target systems you then can generate the partner profiles (transaction WE20) automatically (also from within transaction BD64).

Regards,

Rob.

Re: Transportable Objects

Former Member — Tue, 10 Oct 2006 23:20:00 GMT

<i>Once you have created a model (always two partners are involved) you can then distribute the model to the partner systems or you can create a transport for them.</i>

ROb,

Would you explain the above statement please. Any landscape has for example Dev->QA->Prod and within each environment, there will be several partners and we can distribute the model among partner systems. Why do anyone create transport for model distribution. May be I couldn't quite understood your point. Would you please eloborate for me? Thx

Re: Transportable Objects

Former Member — Tue, 17 Oct 2006 20:58:41 GMT

Hi Ram,

Within transaction BD64 (Display/Maintain Distribution Model) you can create your own defined distribution models.

Each model has two PARTNERS (In fact these are logical destinations (transaction BD97) related to from physical RFC destinations (transaction SM59)).

If you do not wish to use BD97, you can also use directly the SM59 destinations, but the names must then always match.

Within a PARTNER you can define BAPI's (either the sending partner or the receiving partner) or you can define a message type (Most often this is an IDoc).

Furthermore below the BAPI and/or IDoc you can add filter rules (thus allowing for only specific messages or data getting through between the partners).

On the system, where your modelviews are originated, ALL partners must be defined. On the target systems only those partners used on that specific system.

Once your model has been completed, you can choose to DISTRIBUTE it to the target systems. These systems are always reached via the RFC destination (Menu: Edit --> Model --> Distribute).

Once distribution is completed, on the target system you then can generate your partner details automatically (the results can be viewed via transaction WE20).

Generation also takes place in BD64 (Menu: Environment --> Generate Partner Profiles).

And then you are finished and the communication can take off.

SAP has several automated scripts to do this (partly) for you. For example, take a look in customizing (Transaction SPRO). Within the IMG follow the path:

SAP Implementation Guide --> Cross-Application Components --> Predefined ALE Business Processes --> Cross-Application Business Processes --> Central User Administration

Within this path you will see all required activities to set up "Central User Administration".

PS. This was on our own CRM system.

Hope this gives you some insight in Modelviews.

Regards,

Rob