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_member229755]

Hi Arun,

I would recommend checking the following:

1. Note the Time ToC was created

2. Note the time TOC was released.

2. Note the Time Active version of the function module was changed to Version 2.0 in the DEV system.

As per my knowledge, ChaRM creates the ToC and includes all the objects(active version) that are in the Original Transport.  We can also configure ChaRM to release the TOC perhaps.

Regards,

Prasath