Dear Bassem Sabbagh,

I have created a common JIRA for this issue. Kindly assign an AI DEV resource to investigate and resolve it.

Assigned to Ashutosh to define the WL ... WIP

Both Huawei and NSN ran csv-outputs attached with suggested names.
Note: I have only changed the existing importer connector nothing else.

Hi Sandya,

As discussed, the Importer ID and Importer Connector are still missing in almost all tables in the CSV output.

XML shared.

Hi Sandya,

Please check the attached excel sheet where I have mentioned the parsing connector name and need to check where it is parsing incorrect.

Sandhya to define the WL

WL is half day.

to be delivered in 14-10 the first half

It is done , but as discussed with indrasan he said that upload the csv after fix all the issue related to jira OT-84.

ticket to be assigned to Indrasan and CSVs to be shared with integration and to be loaded in SD

csv-output shared with integration and uploaded in staging db.

importor connector name is not mendatory for each csv , it is discussed with driss sir, and for addinfo or error alarm we are using the common code for each connector, there is error coming for others connector while i change the code for addinfo , we can fix it by change in each connnector seperatly.

Dear @Sandya Sharma,

Please find the validation remarks: (Green-Fixed, Blue-Ignore, without any colour-To be check)

I consider the latest one Importer Id=’20251016091426_2025-10-16-09.14.26’

Updated list (OT-83 (Nokia RAN) is attached for your reference.

to be fixed by 29-10

csv output shared with integration

Hi Sandya, could you please confirm if Integration has uploaded it? I am unable to find any email regarding this.

As confirmed this is included in the CSV output which is shared for OT-84.

Bassem Sabbagh in meantime please assign this to Jharna Thakur to fix for Huawei RAN.

Jharna to define the WL ... started on 4-11

Done with this, will share the CSV output with the resolution for OT-85.

CSVs are shared with integration

Hi @Sandya Sharma,

Please find latest validation feedback for Importer Connector for Nokia RAN:

Consider Importer ID: 20251107090325_2025-11-07-09.03.25

Still Importer Connector is not correct for below tables:

CSV-Output Table Name
NodeInterface
RadioAntenna
SubInterface
ElementCell5g
ElementCellRadioBandWidth
ElementTrx
LogicalInterface

Please check the updated data and confirm.

Hi @Sandya Sharma,

Please find below validation feedback for latest importer id: 20251111023300_2025-11-11-02.33.00

Still Importer Connector is not correct for below tables:

CSV-Output Table Name
NodeInterface
SubInterface
ElementCell5g
ElementTrx

WIP and to be fixed by 13-11

CSV output shared with integration.

1- Nokia RAN:

Connector name is parsing OK in all possible tables except below which can be ignored:
(II) Site
(III) Error alarm

2- Huawei RAN:

Connector name is parsing OK in all possible tables except below:
(II) Site
(III) Error alarm
(IV) Sub interface: Missing somewhere in table (To be check by Jharna Thakur

Hi Jharna Thakur please commit the code for connector name missing issue in Huawei RAN for table "Sub interface" as it is fixed now withing OT-45 CSV output.

Hi Jharna,

The issue was initially identified in the Sub Interface table, where the importer connector was missing. You had fixed this earlier. However, while validating the latest data on the server using the importer ID 20251231015405_2025-12-31-01.54.05 (shared by Basant on 31-12-2025), I noticed that the importer connector issue is now appearing in additional tables as well either it is missing or incorrect 'Huawei_M2000'.

The following tables are affected, even though they were previously fixed (except for Sub Interface):

1- BATCH_ELEMENT_CELL_RADIO_BAND_WIDTH
2- BATCH_ELEMENT_GSM_CELL_MAIO
3- BATCH_ELEMENT_TRX
4- BATCH_ELEMENT_TRX_ARFCN
5- BATCH_IP_DATA
6- BATCH_LOGICAL_INTERFACE
7- BATCH_NETWORK_ELEMENT_DUMP
8- BATCH_NODE_INTERFACE
9- BATCH_RADIO_ANTENNA
10- BATCH_SUB_INTERFACE
11- BATCH_VIRTUAL_INTERFACE

Kindly review and fix the importer connector issue for the above tables as well.

XML and CSVs are generated with no issues on local laptop of Jharna ... it could be integration issue ... L2 to generate again the XML and share it for validation ...

I have checked the staging database and the issues have now been resolved.
Previously, the Omantel connector was executed instead of the Ooredoo Huawei RAN connector, which caused the discrepancy. This has been corrected.

Now, issue has been fixed for both connector Nokia RAN (Already fixed earlier) & Huawei RAN (Now fixed):

Connector name is parsing OK in all possible tables except below which can be ignored:
(II) Site
(III) Error alarm

2- Huawei RAN:

Connector name is parsing OK in all possible tables except below:
(II) Site
(III) Error alarm