CHARM TOC VERSION MANAGEMENT ISSUE

[Former Member]

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.

[Miguel_Arino]

Hello,

this is standard function of ChaRM.

Every time you have a new version, the ToC is created again, and only the latest version is imported.

If you want to avoid this issue, you should look into using DGP. Or perhaps not allow the devs to do the transports, for closer control.

Best regards,

Miguel

[Former Member]

Hi miguel, If possible I would like to consult you about a question that I raised concerning the ToC in ChaRM . When ToC is done , it may be due to delay in impact of changes in the QA system? When I refer to that delay , I mean several hours to several days. Thank you very much. regards.- Mario Agustín Micheltorena.-

[Miguel_Arino]

Hello,

Could you please rephrase your question? I cannot understand the question.

Best regards,

Miguel