Released vs. implemented Methods/Objects

[Kishore Thota]

Hi Mark,
 
Here is the SAP note on this topic.
 
Release status Modeled (symbol (Page) )
You cannot call modeled object types/components at runtime.
 
Release status Implemented
Implemented object types/components are either in the test phase or are
only used internally.
You can call and test them at runtime.
Implementation may not yet be stable.
 
Release status Released (symbol (Arrow) )
Released object types/components are released for use. You can call them at
 runtime.
 Any enhancements made by SAP to released object types and components are
upward-compatible.
 
Object types and components can only be released if they are in
delivery-relevant development classes.
 
Release status Obsolete (symbol (Red Triangle) )
Obsolete object types/components show that the functions are being
discontinued and replaced
with other functions that are incompatible.
 
Object types or components being discontinued and designated by SAP as
obsolete are still
supported in the change release and the next release.
The old functions and the new functions are available in parallel for this
period.
Incompatible changes are included by SAP in a central release publication.
 
 
 
 
 
 
Thanks,
Kishore Thota
Ph: (919) 543-1831
Tie Line: 8-441-1831
 
 
Mark Huffman <m.r.huffman at worldnet.att.net>@MITVMA.MIT.EDU> on 05/31/2000
01:37:50 AM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:  SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:
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?