Released vs. implemented Methods/Objects

[Mark Huffman]

David, Carsten and Kishore,
 
Thanks for your advice on the matter.
 
The full saga was that substantial development work had been done in a
new, customized business object as a $TMP object. When the business
object itself was added to a transport by changing the development
class, the program of the business object was not automatically
included.
 
Instead, the transport (which had already been sent to QA) had its'
status reset. The object-program's development class had to be manually
changed as well, thus adding it to the transport and then the whole
thing re-released.
 
So both the business object and its' program were transported from the
DEV to QA box successfully,even though the business object and methods
only had status of "Implemented". The only problem I noticed is that the
business object was not automatically generated in QA, which caused
spurious binding errors the first time the workflow started, and I had
to manually generated the object from display mode.
 
So I am still a little mystified as to when I should change the status
from implemented to released. Maybe at the end of this first testing
phase?
 
David Weston wrote:
>
> Hi Mark
>
> In my experience those objects that are not released are classed as
> local and thus cannot be transported until released.
>
> Regards
> Dave
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
> Mark Huffman
> Sent: Wednesday, May 31, 2000 1:38 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Released vs. implemented Methods/Objects
>
> What is the purpose of changing the status of a method or an entire
> business object to released vs. implemented? Can anyone point me to
> documentation on the matter? I have access to the 4.6 online doco and a
> reasonably long search did not turn up anything.
>
> Are there any transport limitations on objects or object-methods that
> simply have the status of implemented?