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.

[Former Member]

Hi Varun,

As per my understanding, In Normal Change, when we modify any object and save in TR and pass it to test then ToC automatically created and available for import in QAS. But if second time you try to modify same object without releasing original TR, than system creates new tasks under same transport request and again if you pass it to test and new ToC gets created. If you import ToC through task list than newest version get imported through task list.

Hope this clarify your question.

Further please refer below link to understand ToC concept

Regards,

Piyush Jain