CHARM TOC VERSION MANAGEMENT ISSUE

[#1]

HI Experts,

             We are using charm in our project for the last 6 months and everything working fine. But now we noticed one conflict as stated below in steps.

1.Developer developing a Function module and  saves it in task under the main transport.Lets say this version is version 1.0

2.Developer releases his task and asks basis to transport it to QAS.

3.Basis creates a TOC for the main transport.(TOC is created but not released.)

At this point of time another developer is editing the same Function module and lets say now the current active version for the FM is 2.0

4.Now basis is releasing the TOC.

5.Basis transport TOC to QAS.

But while checking in QAS version 2.0 has been transported instead of 1.0.the current version in QAS for the FM is 2.0.

How come version 2.0 has been transported even though the developer saved version 1.0 in his task and released only that task.

Is this a defect of Charm that it will take the version of the FM at the time of releasing the TOC.(While TOC released the developer was editing his FM and the version has changed to 2.0)

Kindly reply.

Regards,

Arun Raj.

[TomCenens]

Hi Arun

Sounds like "works as designed" really .

Upon release, the transport takes the currently active version so if the developer created the task for 1.0 but in the meantime build 2.0 and 2.0 is active and the TOC is not yet released, it will take 2.0 upon release since it takes the currently active version.

A transport has in essence a reference to an object and takes the active version upon release. So if you want to have 1.0 transported first, the TOC has to be released before 2.0 is put active so they can test 1.0 in acceptance, if you use CHARM and put the change document back to "in development" because the test was not "ok" in acceptance, you get a new TOC if you then go from "in development" to "to be tested" again while the original transport request is still unreleased.

Best regards

Tom