# FIX-aviator-capability-on-BO-UI_688988251
## Introduction

When the deploy status of Aviator capability is not done, the enable requset has been sent, it will cause the BO UI is not correct display. It is all OK except the BO UI. We will prevent the issue in our code in Release 24.4.

This document explains how to correct the data in this issue tenant.

![](attachments/688988251/688988250.png)

### Steps

1. Login in the issue tenant with the tenant admin, switch to https://<ESM\_FQDN>/sap/rest-client?TENANTID=804874389
2. Send the **GET** request with URL **common-settings/setting/OT\_AI\_CONFIG.**
3. You will get the result as bellow:
	{
	"OT\_AI\_CONFIG": "{\\"llmEndpoint\\":\\"[....\\",\\"tenantId\\":\\"XXXXXXX\\"}"](https://1zwpwwuoe7.execute-api.eu-central-1.amazonaws.com/eu30-prod/%22,/%22llmApikey/%22:/%22tenant_int_804874389_llm_api_gateway_apikey_secret_key/%22,/%22cognitoEndPoint/%22:/%22https://eu30-aviator.auth.eu-central-1.amazoncognito.com/oauth2/token/%22,/%22cognitoClientId/%22:/%227pdkdfvp7ho40g3circmraju3o/%22,/%22cognitoClientSecret/%22:/%22tenant_int_804874389_llm_cognito_client_secret_key/%22,/%22tenantId/%22:/%222daf7c41ee5c497db7bedeed6d5e0b25/%22%7D%22 "https://1zwpwwuoe7.execute-api.eu-central-1.amazonaws.com/eu30-prod/%22,/%22llmapikey/%22:/%22tenant_int_804874389_llm_api_gateway_apikey_secret_key/%22,/%22cognitoendpoint/%22:/%22https://eu30-aviator.auth.eu-central-1.amazoncognito.com/oauth2/token/%22,/%22cognitoclientid/%22:/%227pdkdfvp7ho40g3circmraju3o/%22,/%22cognitoclientsecret/%22:/%22tenant_int_804874389_llm_cognito_client_secret_key/%22,/%22tenantid/%22:/%222daf7c41ee5c497db7bedeed6d5e0b25/%22%7d%22")
	}
	The tenantId will be used in the steps 7.
4. Go to the SMAX bastion server, then execute the command to login in the itom-bo-ats-deployment-xxx-xxx

kubectl exec -it itom-bo-ats-deployment-xxxxxx -c itom-bo-ats -n <NS> bash

1. 1. Get the dba password by "get\_secret itom\_itsma\_dba\_password\_secret\_key"
		2. Login in to the pg in bo-ats db with psql.
		3. execute the sql as bellow:
		1. Get 1 record with no **llmTenantId** in **properties** and **status=0**: **SELECT \* FROM "bo\_db\_user".tenant\_capability WHERE tenant\_id = <TENANT\_ID> AND type = 6;**
				2. Update the LLM capability status to DONE: **UPDATE "bo\_db\_user".tenant\_capability SET status = 2 WHERE tenant\_id = <TENANT\_ID> AND type = 6;**
				3. Update set the LLM capability tenant id: **UPDATE "bo\_db\_user".tenant\_capability SET properties = jsonb\_set(properties, '{llmTenantId}', '"<LLM\_TENANT\_ID in step 3>"') WHERE tenant\_id = <TENANT\_ID> AND type = 6;**
				4. Double check the **llmTenantId** in **properties** and **status=2**: **SELECT \* FROM "bo\_db\_user".tenant\_capability WHERE tenant\_id = <TENANT\_ID> AND type = 6;**

#### Check in the BO UI

Login to the BO UI with suite-admin, you can see the data is back to normal.

## Attachments:

[image2024-7-16\_16-21-2.png](attachments/688988251/688988250.png) (image/png)