SRM 5.0 - Inactive versions of BOR Objects

[Susan R. Keohan]

Hi Mike,

Thanks for the reply, but at the point where SE80 (or SE37, or SE38) is complaining of an inactive 
object, the object (in this case, ZBUS2201) actually *is* active!  Activated thru SWo1 as is 
standard operating procedure.

So then why does the business object show up as inactive ?

Why does the code that shows up if you drill into the BO show the old version ('Hello...') not the 
new version ('Is there anybody out there?') which was generated ?

I suspect this is actually related to the way in which our SRM dev environment was built... this 
object was modified on one system, copied to another, then the Basis Team did some switching of 
system IDs or whatever kind of magic they do.  The custom BO did not exist in the prior version (EBP 
3.5) when the upgrade packs were applied.

I've filled out a customer message, so I assume we'll be having SAP log on to check this out someday.

Thanks again,
Sue

Mike Pokraka wrote:

> Hi Sue,
> You will usually have an 'inactive' and an 'active' version of your code -
> and yes I've seen the same as Kjetil on a system for the same reason.
> 
> Go into SE38 and create a prog:
> REPORT  ZMPTEST.
> write 'Hello...'.
> 
> Generate and execute. Now, make some change:
> REPORT  ZMPTEST.
> write 'Is there anybody out there?'.
> 
> at this point do NOT generate, just click the 'test' icon - you will see
> the result of the second 'version'.
> 
> Save and exit to front screen of SE38, execute (do NOT generate) - it'll
> complain about inactive versions - hit continue. Result: 'Hello...'. Click
> display prog and test again... you get the picture.
> 
> As long as you haven't activated everything fully there will be different
> versions from different viewpoints, something which confuses me as well so
> I usually activate everything when there's any doubt (commenting out any
> dodgy code and adding TODO's if necessary).
> 
> Hope that helps,
> Mike
> 
> Susan R. Keohan wrote:
> 
>>Hello all,
>>
>>SRM 5.0, SRM Server 5.50, SP SAPKIBKT03, Basis 7.0, SAPKB70006.
>>I know, I usually come up with the whacked out questions on Friday, so
>>excuse me for posting such an
>>oddball question so early in the week.  And for the record, this is not a
>>case of EBKAC, I have
>>watched while someone replicates this error.
>>
>>Scenario:
>>1)  You have made changes to a function module interface that a customer
>>business object (say,
>>ZBUS2201) calls, so you need to correct the errors. You edit this business
>>object. Save and generate
>>the object.
>>2) From SE80, if you check Inactive Objects, ZBUS2201 shows up.  Why ?
>>3) From SE80, drill into the business object.  Generate the Business
>>Object.  It has an error (from
>>the earlier code).  Select Goto>Next Error.
>>4) The code listed is not the code you edited and saved and generated in
>>Step 1.  Why ?
>>5) Hit the pencil to go into Change mode.  The live version (created in
>>Step 1) is now available for
>>editing.
>>
>>So I am assuming there is some hidden form of version management going on
>>- that needs tweaking.
>>Our Basis team cleared the buffers which brought no joy, and then bounced
>>the system, which also
>>brought no joy.
>>
>>Clearly I need to fill out an OSS message, but wanted to check with my
>>fellow WFers to see if any of
>>you have also encountered this issue.
>>
>>Cheers,
>>Sue
>>
>>--
>>Susan R. Keohan
>>SAP Workflow Developer
>>MIT Lincoln Laboratory
>>244 Wood Street
>>LI-200
>>Lexington, MA. 02420
>>781-981-3561
>>keohan at ll.mit.edu
>>
>>
>>
>>
>>
>>
>>
>>_______________________________________________
>>SAP-WUG mailing list
>>SAP-WUG at mit.edu
>>http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
> 
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 

-- 
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu