Fabric Reporting Database Data Dictionary

Page 1

Fabric Reporting Database Data Dictionary

Page 2

Table of Contents 1 Introduction .................................................................................................................................................................................................................................................... 4 3 Data mapping .................................................................................................................................................................................................................................................. 4

3.1 Table: application_error_detail ...................................................................................................................................................................................................................... 5 3.2 Table: application_events ........................................................................................................................................................................................................................ 10 3.3 Table: application_service_detail ............................................................................................................................................................................................................ 14 3.4 Table: application_form_detail ............................................................................................................................................................................................................... 18 3.5 Table: middleware_requests .................................................................................................................................................................................................................... 21 3.6 Table: middleware_sessions .................................................................................................................................................................................................................... 26

3.7. Table: middleware_sub_requests ............................................................................................................................................................................................................... 30 3.8. Table: api_requests ..................................................................................................................................................................................................................................... 35 3.9. Table: api_sub_requests ............................................................................................................................................................................................................................. 40 4 Custom Metrics ................................................................................................................................................................................................................................................ 45

4.1 Table: custom_metrics_master ................................................................................................................................................................................................................ 45 4.2 Table: crpt_metric .................................................................................................................................................................................................................................... 49 4.3 Table: crpt_owner .................................................................................................................................................................................................................................... 50 4.4 Table: crpt_master_info ........................................................................................................................................................................................................................... 51

5 Invalid Messages .............................................................................................................................................................................................................................................. 52 5.1 Table: invalid_messages .......................................................................................................................................................................................................................... 52

6 License Info ........................................................................................................................................................................................................................................................ 53 6.1 Table: licenseinfo ..................................................................................................................................................................................................................................... 53

7 Utility Tables ...................................................................................................................................................................................................................................................... 54 7.1 Table: dw_keys_session .......................................................................................................................................................................................................................... 54 7.2 Table: dw_keys_request .......................................................................................................................................................................................................................... 54 7.3 Table: geolocations_ip4 ........................................................................................................................................................................................................................... 55 7.4 Table: dim_date ....................................................................................................................................................................................................................................... 56 7.5 Table: jrs_fusionmap_usa ........................................................................................................................................................................................................................ 57 7.6 Table: jrs_fusionmap_world .................................................................................................................................................................................................................... 58 7.7 Table: metrics_application_log ............................................................................................................................................................................................................... 58 7.8 Table: metrics_configuration ................................................................................................................................................................................................................... 59 7.9 Table: tmp_calendar ................................................................................................................................................................................................................................ 59

Page 3

Page 4

1 Introduction The purpose of this document to provide information about the application analytics data being collected, processed, and loaded into Kony’s analytics data warehouse. The document will provide data mapping for the data but will not describe the nature of individual reports.

3 Data mapping The following tables describe the individual fields present in each record type. The following columns are contained in the field mapping tables:

o Column Name – actual target column name in the data warehouse o Business Name – Verbose name of the column o Description – Technical description of the field intent or contents o Required – If yes, the respective column must be present in the input o Data type – SQL data type or field length o Source – Data origination or collection point:

o Application Generated – value is measured and sent from the application on the device o Dispatcher – Internally generated value o MaxMind DB – Value is provided by the dispatcher via the MaxMind Geo-IP database o Queue Message ID – The message ID assigned as it the message was inserted into the collection queue

Page 5

3.1 Table: application_error_detail Description: This table stores data for all error type application events such as error, exception and crash. This table has more granular data available for error events than the application_events table, wherein the metadata values are split into columns for ease of use for error specific reports.

Column name Business name

Description Required Data type

Bid Batch ID Unique batch identifier created by Kony Analytics when batch of messages is processed.

YES VARCHAR2(255)

Mid Message ID Unique message identifier created when a message is dropped into a queue. (Null for on-prem)

VARCHAR2(255)

kaid Kony Account ID

This is a value generated by Kony to represent the customer’s Kony Account.

YES

VARCHAR2(255) eid Environmen

t ID This is a value generated by Kony to uniquely identify this cloud environment within the customer’s account.

YES

VARCHAR2(255) aid Application

ID A unique identification given to the application by the developer.

YES VARCHAR2(255)

ts Timestamp A String representation of the server date and time when the request was received including timezone and must be in the format of "yyyy-mm-dd HH:MM:SS". A day is defined as 12:01am to 12:00am UTC time

YES

TIMESTAMP(6) evttype Event Type Type of the event generated like FormLoad, Form Exit,

Button click, Service calls, Gestures, Orientation, Custom Event

YES

VARCHAR2(100) aname Application

Name A friendly name for the application given by the developer.

YES

VARCHAR2(255) atype Application

Type The atype can be [native, mixedmode, hybrid, spa, mobileweb] – Could be new values in the future.

YES

VARCHAR2(255) plat

Platform The operating system version such as 5.1.2. It is some string value from the OS. This will be blank in the case of atype=SPA or MobileWeb

YES

VARCHAR2(255)

Page 6

chnl Channel The application channel - [mobile, tablet, desktop] – Could be new values in the future.

YES

VARCHAR2(255) formid Form ID Identifier of the form where the event occurred in app

VARCHAR2(255) widgetid Widget ID ID of the widget where applicable. Applicable for button

clicks, some gestures

VARCHAR2(255) sid Session ID A unique ID for this session. All requests to the server

executed within the same session will have the same Session ID

YES

VARCHAR2(255) evtsubtype Event

Subtype Additional Data about the event. Ex: For service call it is name of service, for gesture it has left to right swipe, tap etc. For custom events, the developer can set the evtSubType to any string value.

VARCHAR2(255)

flowtag Flow Tag Optional parameter that can be set by developer via an API call to identify a flow. Helps in easy identification for data analysis.

VARCHAR2(255) session_key Session Key Surrogate session key YES

NUMBER(20) request_key Request Key Surrogate request key

NUMBER(20) errcode Error Code Error code if the evttype is error and Exception code if

evttype is exception

VARCHAR2(50) errmsg Error

Message Error message if the evttype is error and Exception message if evttype is exception

VARCHAR2(255)

errfile Error File Error file if the evttype is error and Exception file if evttype is exception

VARCHAR2(255)

errmethod Error Method

Error method if the evttype is error and Exception method if evttype is exception

VARCHAR2(255)

errline Error Line Error line if the evttype is error and Exception line if evttype is exception

NUMBER(10)

errstacktrace Error Stack Trace

The stack trace of the error for debugging purpose. CLOB

errstacktrace_var

Error Stack Trace

The stack trace of the error for debugging purpose. VARACHAR2(4000)

errtype Error Type Error type VARCHAR2(255)

Page 7

iserror iserror true if the evttype is error/crash and false if evttype is exception

NUMBER(3)

errcustommsg Error Custom Message

This field inserts only if the evttype is crash CLOB

errcustommsg_var

Error Custom Message

This field inserts only if the evttype is crash varchar(4000)

errcrashreport Error Crash Report

This field inserts only if the evttype is crash CLOB

errcrashreport_var

Error Crash Report

This field inserts only if the evttype is crash varchar(4000)

sessionid Session ID If the evttype is crasha nd metadata contains sessionid field, SID will be replaced with this sessionid

VARCHAR2(255)

did Device ID Unique identifier for a device as exposed by the underlying SDKs. For SPA, DesktopWeb, MobileWeb it will be empty.

VARCHAR2(255) dm Device

Model The device model such as iPhone 5. This is a string that comes from the device and could be anything. This will be blank in the case of atype=SPA or MobileWeb

VARCHAR2(255) ua User-Agent The User-Agent of the client browser. This will be only

populated for atype=SPA or MobileWeb

VARCHAR2(255) os OS Version The operating system version such as 5.1.2. It is some

string value from the OS. This will be blank in the case of atype=SPA or MobileWeb

VARCHAR2 (255)

aver Application Version

Client application version VARCHAR2(255)

kuid Kony User ID

This string typically represents a User ID, but customers could potentially supply a very long string.

VARCHAR2(255) sdktype SDK Type The type of the Fabric SDK used at the client. Ex:iOS,

Android. This field is not applicable for Kony Studio based applications.

VARCHAR2(50) sdkversion SDK Version The version of the Fabric SDK used at the client. Ex: 1.0.

This field is not applicable for Kony Studio based applications.

VARCHAR2(50)

Page 8

pluginverplat Plugin Version - Platform

plugin version of the platform plugin used in the binary. For iOS app, it would be the iOS plugin version, for android applications the android plugin version and so on. Applicable only for event type crash.

VARCHAR2(255) pluginveride Plugin

Version - IDE plugin version of the IDE plugins used while the client binary was built. Applicable only for event type crash.

VARCHAR2(2048) mfbaseid Fabric Base

Application ID

This is applicable if the client application is pointing to a Fabric application in the backend to retrieve data for service requests, instead of traditional Kony Integration Server service definition per application. This is a GUID generated by Fabric server when application is first defined. This is same across different servers if the application is published to different servers.

VARCHAR2(255) mfaname Fabric

Application Name

This is applicable if the client application is pointing to a Fabric application in the backend to retrieve data for service requests, instead of traditional Kony Integration Server service definition per application. This is a name provided by developer in Fabric server when application is first defined. This is same across different servers if the application is published to different servers.

VARCHAR2(255) mfaid Fabric

Application ID

This is applicable if the client application is pointing to a Fabric application in the backend to retrieve data for service requests, instead of traditional Kony Integration Server service definition per application. This is a GUID generated by Fabric server when application is published to a cloud. This is different in different servers if the application is published to different servers.

VARCHAR2(255)

diskmemfree

Disk memory free

To be used to indicate free memory in the internal disk in MB

FLOAT(126)

diskmemtot

Disk memory total

To be used to indicate total memory in the internal disk in MB.

FLOAT(126)

Page 9

sdmemfree

Sd memory free

To be used to indicate free memory available in SD card in MB.

FLOAT(126)

sdmemtot

Sd memory total

To be used to indicate total memory available in SD card in MB.

FLOAT(126)

chargelevel

Battery charge level

To be used to indicate battery level during time of crash. This will be a number indicator % available of battery.

FLOAT(126)

ramused

Memory usage

To be used to indicate the memory used when app crashes.

FLOAT(126)

cpu

CPU usage To be used to indicate the % of CPU being used at time of crash.

FLOAT(126)

networktype

Network type

To be used to indicate the type of network during time of crash. Valid values – “mobilenetwork”, “wifi”

VARCHAR2(50)

sessiontype Session Type Type of session, interactive/non-interactive

VARCHAR2(50)

Page 10

3.2 Table: application_events Description: This table stores application events data for Kony Integration Server based applications.




YES VARCHAR2 (255)

mid Message ID Unique message identifier created when a message is dropped into a queue. (Null for on-prem)

VARCHAR2 (255)



YES VARCHAR2 (255)

eid Environment ID

This is a value generated by Kony to uniquely identify this cloud environment within the customer’s account.

YES VARCHAR2 (255)

aid Application ID A unique identification given to the application by the developer.

YES VARCHAR2 (255)


YES Timestamp(6)

evttype Event Type Type of the event generated like FormLoad, Form Exit, Button click, Service calls, Gestures, Orientation, Custom Event

YES VARCHAR2 (100)

formid Form ID Identifier of the form where the event occurred in app

VARCHAR2 (255)

widgetid Widget ID ID of the widget where applicable. Applicable for button clicks, some gestures

VARCHAR2 (255)

sid Session ID A unique ID for this session. All requests to the server executed within the same session will have the same Session ID

YES VARCHAR2 (255)

Page 11

evtsubtype Event Subtype Additional Data about the event. Ex: For service call it is name of service, for gesture it has left to right swipe, tap etc. For custom events, the developer can set the evtSubType to any string value.

VARCHAR2 (255)


VARCHAR2 (255)

session_key Session Key Surrogate session key YES NUMBER(20)

request_key Request Key Surrogate request key NUMBER(20)

Metadata_var Metadata If the metadata is json object and evttype is error/crash/exception and service response, they will be processed by the analytics backend and stored separately for easier reporting and access.

VARCHAR2 (4000)

metadata Metadata If the metadata is json object and evttype is error/crash/exception and service response, they will be processed by the analytics backend and stored separately for easier reporting and access.

CLOB

awsid AWSID AWS ID – Internal account tracking number. (Null for on-prem)

VARCHAR2 (255)

ebid Beanstalk ID This will be a unique ID that correlates to the AWS ID for the beanstalk. (Null for on-prem)

VARCHAR2 (255)

rid RequestID RequestID - A unique ID generated for this request VARCHAR2 (255) did Device ID Unique identifier for a device as exposed by the

underlying SDKs. For SPA, DesktopWeb, MobileWeb it will be empty.

VARCHAR2 (255)

aname Application Name

A friendly name for the application given by the developer.

YES VARCHAR2 (255)

atype Application Type

The atype can be [native, mixedmode, hybrid, spa, mobileweb] – Could be new values in the future.

YES VARCHAR2 (255)


YES VARCHAR2 (255)

plat Platform Platform - [ios, android, blackberry, windows, j2me] – Could be new values in the future

YES VARCHAR2 (255)

Page 12

rip Remote IP The remote IP address from the HTTP header. Should be the public facing IP address of the client. Need to find if that is still available in the HTTP header somewhere once the request hits a server.

VARCHAR2 (255)

dm Device Model The device model such as iPhone 5. This is a string that comes from the device and could be anything. This will be blank in the case of atype=SPA or MobileWeb

VARCHAR2 (255)

os OS Version The operating system version such as 5.1.2. It is some string value from the OS. This will be blank in the case of atype=SPA or MobileWeb

VARCHAR2 (255)

ua User-Agent The User-Agent of the client browser. This will be only populated for atype=SPA or MobileWeb

VARCHAR2 (255)

stype Session Type Identifies if the user's application [b2c, b2e] came from a licensed B2E source such as MAM

YES VARCHAR2 (255)


Application version of client VARCHAR2 (255)

kuid Kony User ID This string typically represents a User ID, but customers could potentially supply a very long string.

VARCHAR2 (255)

country Country code Please see "GeoIP City Edition CSV Database Fields" section at http://dev.maxmind.com/geoip/legacy/csv/

VARCHAR2 (2)

region Region code VARCHAR2 (10)

city City name VARCHAR2 (255)

zip Postal code VARCHAR2 (32)

lat Latitude NUMBER(8,5)

lon Longitude NUMBER(8,5)

dmacd Metro code NUMBER

areacd Area code VARCHAR2 (3)

Page 13

sdktype SDK Type The type of the Fabric SDK used at the client. Ex:iOS, Android. This field is not applicable for Kony Studio based applications.

VARCHAR2 (50)

sdkversion SDK Version The version of the Fabric SDK used at the client. Ex: 1.0. This field is not applicable for Kony Studio based applications.

VARCHAR2 (50)

mfbaseid Fabric Base Application ID


VARCHAR2 (255)

mfaname Fabric Application Name


VARCHAR2 (255)

mfaid Fabric Application ID


VARCHAR2 (255)


VARCHAR2(50)

Page 14

3.3 Table: application_service_detail Description: This table stores data for service response event type in more granular detail than application_events table for ease of use for reports using only application service response info.



bid Batch ID Unique batch identifier created by Kony Analytics when batch of messages is processed.

YES VARCHAR2 (255)


VARCHAR2 (255)



YES VARCHAR2 (255)

eid Environment ID


YES VARCHAR2 (255)


YES VARCHAR2 (255)


YES Timestamp(6)


YES VARCHAR2 (100)



YES VARCHAR2 (255)

atype App Type The atype can be [native, mixedmode, hybrid, spa, mobileweb] – Could be new values in the future.

YES VARCHAR2 (255)

plat Platform The operating system version such as 5.1.2. It is some string value from the OS. This will be blank in the case of atype=SPA or MobileWeb

YES VARCHAR2 (255)

Page 15


YES VARCHAR2 (255)


VARCHAR2 (255)


VARCHAR2 (255)


YES VARCHAR2 (255)


VARCHAR2 (255)


VARCHAR2 (255)

session_key Session Key Surrogate session key YES NUMBER(20) request_key Request Key Surrogate request key NUMBER(20) opstatus Operation

Status The opstatus value is zero if network call is successful and non-zero if the network call fails. Kony Integration Server documentation would have reference as to what each value of opstatus implies.

YES VARCHAR2 (50)

httpcode HTTP Response Code

If successful we would mostly 2xx values otherwise there will be different codes depending on the network error.

YES NUMBER(10)

resptime response time Response time of the service call. YES NUMBER(10) did Device ID Unique identifier for a device as exposed by the


VARCHAR2 (255)


VARCHAR2 (255)


VARCHAR2 (255)

Page 16


VARCHAR2 (255)


version of the client application. VARCHAR2 (255)


VARCHAR2 (255)


VARCHAR2 (50)


VARCHAR2 (50)



VARCHAR2 (255)



VARCHAR2 (255)



VARCHAR2 (255)


VARCHAR2 (50)

Page 17

Page 18

3.4 Table: application_form_detail Description: This table stores data for form exit, App load, App transission event type in more granular detail than application_events table for ease of use for reports using only.




YES VARCHAR2(255)


VARCHAR2(255)



YES VARCHAR2(255)

eid Environment ID


YES VARCHAR2(255)


YES VARCHAR2(255)


YES Timestamp(6)


YES VARCHAR2(100)



YES VARCHAR2(255)

atype App Type The atype can be [native, mixedmode, hybrid, spa, mobileweb] – Could be new values in the future.

YES VARCHAR2(255)


YES VARCHAR2(255)

Page 19


YES VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(255)


YES VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(255)

session_key Session Key Surrogate session key YES NUMBER(20) request_key Request Key Surrogate request key NUMBER(20) did Device ID Unique identifier for a device as exposed by the


VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(255)


VARCHAR2 (255)


version of the client application. VARCHAR2(255)


- VARCHAR2(255)

Page 20


VARCHAR2(50)


VARCHAR2(50)



VARCHAR2(255)



VARCHAR2(255)



VARCHAR2(255)

formdur Form duration Time spent by user in application form in milliseconds NUMBER(10)

foredur Fore Ground Duration

Time spent in fore-ground in milliseconds.

NUMBER(10)

loaddur Load Duration Application load time in milliseconds.

NUMBER(10)


NUMBER(10)

Page 21

3.5 Table: middleware_requests Description: Stores information about service call requests from the application client to Kony Integration Server




YES NUMBER(20)


VARCHAR2(255 )



YES VARCHAR2(255 )

eid Environment ID


YES VARCHAR2(255 )


VARCHAR2(255 )


VARCHAR2(255 )

did

Device ID Unique identifier for a device as exposed by the underlying SDKs. For SPA, DesktopWeb, MobileWeb it will be empty.

VARCHAR2(255 )


YES VARCHAR2(255 )



YES VARCHAR2(255 )

rid RequestID RequestID - A unique ID generated for this request YES VARCHAR2(255 )

Sid Session ID

A unique ID for this session. All requests to the server executed within the same session will have the same Session ID YES

VARCHAR2(255)


YES VARCHAR2(255)

Page 22


The atype can be [native, mixedmode, hybrid, spa, mobileweb] – Could be new values in the future

YES VARCHAR2(255)


YES VARCHAR2(255)

idur idur Internal Duration - A numeric value in milliseconds - time to process a request minus the time it takes for backend systems to respond

YES NUMBER

tdur tdur Total Duration - A numeric value in milliseconds. Roral duration to process request, including backend systems respond duration.

YES NUMBER

rip Remote IP The remote IP from the HTTP header. Should be the public facing IP of the client. Need to find if that is still available in the HTTP header somewhere once the request hits a server.

VARCHAR2(255 )


YES TIMESTAMP(6)


VARCHAR2(255)


VARCHAR2(255)

ua User Agent The User-Agent of the client browser. This will be only populated for atype=SPA or MobileWeb

VARCHAR2(255)

svcid ServiceID Service ID - A unique ID of the service the client called. YES VARCHAR2(255 )

fid Form ID

Form ID - A unique ID of the mobile web or SPA web page the user accessed. This is only populated for atype=SPA or MobileWeb

VARCHAR2(255 )


YES VARCHAR2(255 )

Page 23

aver Applicatio Version

Version of the application

VARCHAR(255)

session_key Session Key Surrogate session key YES NUMBER(20) request_key Request Key Surrogate request key YES NUMBER(20)


VARCHAR2(255 )


VARCHAR2(2) region Region code VARCHAR2(10) city City name VARCHAR2(255

) zip Postal code VARCHAR2(32) lat Latitude NUMBER(8,5) lon Longitude NUMBER(8,5) dmacd Metro code NUMBER areacd Area code VARCHAR2(3) predur PreProcessor

Duration Time taken to execute custom pre-processor logic YES NUMBER

exdur External Duration

Time taken to execute all outbound calls to external systems

YES NUMBER

prsdur Parse Duration

Time taken to execute parsing logic on response including XPath on XML or HTML on web scraping

YES NUMBER

postdur PostProcessor Duration

Time taken to execute custom post-processor logic YES NUMBER


VARCHAR2(50)


VARCHAR2(50)

opstatus Operation Status

The opstatus value is zero if network call is successful and non-zero if the network call fails. Kony Integration Server documentation would have reference as to what each value of opstatus implies.

NUMBER(10)



NUMBER(10)

Page 24

errmsg Error Message Error message. This field is filled if the service request failed at the server side.

VARCHAR2(4000)

errstack_var Error Stack Trace

The stack trace of the error for debugging purpose. This field is filled if the service request failed at the server side.

VARCHAR2(4000)

errstack Error Stack Trace


CLOB



VARCHAR2(255 )



VARCHAR2(255)



VARCHAR2(255 )

svcgroup Service Group Service Group

VARCHAR2(255 )

rver

Integration service version header

Requested integration services version - version requested by SDK in header of http request.

VARCHAR2(50 )

svcver Service Version Integration service version

VARCHAR2(50 )

Page 25

reqmapdur Request Map Duration

Object mapping duration (request) integer - time in milliseconds NUMBER

respmapdur Response Map Duration

Object mapping duration (response) integer - time in milliseconds NUMBER

oname Object Name Object name for which mapping is done VARCHAR2(255 )

omethod Object Method http verb for the object (PUT, POST..)

VARCHAR2(50 )

svctype Service Type valid values are Integration, Orchestration, Object VARCHAR2(100 )

contype Connector Type Connector Type

VARCHAR2(100 )

xmode XMode

To differentiate online call vs offline call. Default value is online, for sync calls from offline objects it should be offline

VARCHAR2(100 )

sessiontype Session Type Type of session, interactive/non-interactive VARCHAR2(50)

trecords Total Records Total number of records downloaded/uploaded during sync service call NUMBER

reqtype Request Type Type of request from the device VARCHAR2(50 )

reqbytes Request Bytes Transaction request data in bytes NUMBER

respbytes Response Bytes Transaction response data in bytes NUMBER

reqprsdur

Request Data Processing Duration

Time taken to parse the data and convert to JSON for a request NUMBER

respprsdur

Response Data Processing Duration

Time taken to parse the data and convert to JSON for a response NUMBER

incnfdur

Interceptor Conflict Duration

Time taken to execute built-in interceptor logic for conflicts in milliseconds NUMBER

cnfcnt Conflict Count Number of conflicts occured during sync service call NUMBER

Page 26

Iserror Is Error True if any error occurs during sync service call, otherwise false

VARCHAR2(10 )

3.6 Table: middleware_sessions

Page 27

Description: This table stores info about application sessions for Kony Integration Server based applications. An application session is created whenever application is launched, or when application is used after 30 minutes of idle time.




YES VARCHAR2(255)


VARCHAR2(255)



YES VARCHAR2(255)

eid Environment ID


YES VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(255)


YES VARCHAR2(255)



YES VARCHAR2(255)

Sid Session ID A unique ID for this session. All requests to the server executed within the same session will have the same Session ID

YES VARCHAR2(255)


YES VARCHAR2(255)


The atype can be [native, mixedmode, hybrid, spa, mobileweb] – Could be new values in the future

YES VARCHAR2(255)


YES VARCHAR2(255)

Page 28

tdur tdur Total Duration - A numeric value in milliseconds. Total duration to process request, including backend systems respond duration.

YES NUMBER

rip Remote IP The remote IP address from the HTTP header. Should be the public facing IP address of the client. Need to find if that is still available in the HTTP header somewhere once the request hits a server.

VARCHAR2(255)


YES TIMESTAMP(6)


VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(255)


YES VARCHAR2(255)


Version of the application VARCHAR2(255)

session_key Session Key Surrogate session key YES NUMBER(20)


VARCHAR2(255 )

Country Country code Please see "GeoIP City Edition CSV Database Fields" section at http://dev.maxmind.com/geoip/legacy/csv/

VARCHAR2(2) Region Region code VARCHAR2(10)

City City name VARCHAR2(255)

Zip Postal code VARCHAR2(32)

Lat Latitude NUMBER(8,5)

Lon Longitude NUMBER(8,5)

dmacd Metro code NUMBER

areacd Area code VARCHAR2(3)

Page 29


VARCHAR2(50)


VARCHAR2(50)



NUMBER(10)



NUMBER(10)

errmsg Error Message

This field is filled if the service request failed at the server side.

VARCHAR2(4000)



CLOB



VARCHAR2(4000)

Mfbaseid Fabric Base Application ID


VARCHAR2(255)



VARCHAR2(255)

Page 30



VARCHAR2(255)

svcgroup Service Group

Service Group VARCHAR2(255)

svcver Service Version

Integration service version

VARCHAR2(50)

rver Integration service version header

Requested integration services version - version requested by SDK in header of http request.

VARCHAR2(50)


3.7. Table: middleware_sub_requests

Column name Bussiness Name Description Required Data Type

bid Batch ID Unique batch identifier created by Kony Analytics

when batch of messages is processed. YES VARCHAR2(255)

mid Message ID Unique message identifier created when a message is

dropped into a queue. (Null for on-prem) VARCHAR2(255)

kaid Kony Account ID This is a value generated by Kony to represent the

customer’s Kony Account. YES VARCHAR2(255)

eid Environment ID This is a value generated by Kony to uniquely identify

this cloud environment within the customer’s account. YES VARCHAR2(255)

awsid AWSID AWS ID – Internal account tracking number. (Null for

on-prem) VARCHAR2(255)

Page 31

ebid Beanstalk ID This will be a unique ID that correlates to the AWS ID

for the beanstalk. (Null for on-prem) VARCHAR2(255)

did

Device ID Unique identifier for a device as exposed by the underlying SDKs. For SPA, DesktopWeb, MobileWeb it will be empty. VARCHAR2(255)

aid Application ID A unique identification given to the application by the

developer. YES VARCHAR2(255)

aname Application Name A friendly name for the application given by the

developer. YES VARCHAR2(255) rid Request ID A unique ID to identify the request YES VARCHAR2(255)

sid

Session ID A unique ID for this session. All requests to the server executed within the same session will have the same Session ID YES VARCHAR2(255)

chnl Channel The application channel - [mobile, tablet, desktop] –

Could be new values in the future. YES VARCHAR2(255)

atype Application Type The atype can be [native, mixedmode, hybrid, spa,

mobileweb] – Could be new values in the future YES VARCHAR2(255)

plat Platform Platform - [ios, android, blackberry, windows, j2me] –

Could be new values in the future YES VARCHAR2(255)

idur Internal Duration

A numeric value in milliseconds - time to process a request minus the time it takes for backend systems to respond YES NUMBER

tdur Total Duration -

A numeric value in milliseconds. Total duration to process request, including backend systems respond duration. YES NUMBER

rip Remote IP

The remote IP from the HTTP header. Should be the public facing IP of the client. Need to find if that is still available in the HTTP header somewhere once the request hits a server. VARCHAR2(255)

ts TimeStamp

A String representation of the server date and time when the request was received including timezone and must be in the format of "yyyy-mm-dd HH:MM:SS". A day is defined as 12:01am to 12:00am UTC time YES TIMESTAMP(6)

dm Device Model

The device model such as iPhone 5. This is a string that comes from the device and could be anything. This will be blank in the case of atype=SPA or MobileWeb VARCHAR2(255)

Page 32

os Operating System

The operating system version such as 5.1.2. It is some string value from the OS. This will be blank in the case of atype=SPA or MobileWeb VARCHAR2(255)

ua User Agent The User-Agent of the client browser. This will be only populated for atype=SPA or MobileWeb VARCHAR2(255)

svcid Service ID Service ID - A unique ID of the service the client called. YES VARCHAR2(255)

psvcid Parent Service ID Service ID of the parent service that invoked the child service YES VARCHAR2(255)

fid Form ID

Form ID - A unique ID of the mobile web or SPA web page the user accessed. This is only populated for atype=SPA or MobileWeb VARCHAR2(255)

stype Session Type Identifies if the user's application [b2c, b2e] came from a licensed B2E source such as MAM YES VARCHAR2(255)


Application version of the client VARCHAR2(255)

kuid Kony User ID This string typically represents a User ID, but customers could potentially supply a very long string. VARCHAR2(255)

country COUNTRY Please see "GeoIP City Edition CSV Database Fields" section at http://dev.maxmind.com/geoip/legacy/csv/ VARCHAR2(2)

region REGION VARCHAR2(10) city CITY VARCHAR2(255) zip ZIP VARCHAR2(32) lat Latitude NUMBER(8,5) lon Longitude NUMBER(8,5) dmacd NUMBER areacd Area Code VARCHAR2(3) predur Pre Duration Time taken to execute custom pre-processor logic YES NUMBER

exdur External Duration Time taken to execute all outbound calls to external systems YES NUMBER

prsdur Parse Duration Time taken to execute parsing logic on response including XPath on XML or HTML on web scraping YES NUMBER

postdur Post Processor Duration


sdktype SDK Type

The type of the Fabric SDK used at the client. Ex:iOS, Android. This field is not applicable for Kony Studio based applications. VARCHAR2(50)

Page 33

sdkversion SDK Version

The version of the Fabric SDK used at the client. Ex: 1.0. This field is not applicable for Kony Studio based applications. VARCHAR2(50)

opstatus Op-Status

The opstatus value is zero if network call is successful and non-zero if the network call fails. Kony Integration Server documentation would have reference as to what each value of opstatus implies. NUMBER(10)

httpcode Http Code

If successful we would mostly 2xx values otherwise there will be different codes depending on the network error. NUMBER(10)

errmsg Error Message This field is filled if the service request failed at the server side. VARCHAR2(4000)

errstack_var Error Stack Var

The stack trace of the error for debugging purpose. This field is filled if the service request failed at the server side. VARCHAR2(4000)

errstack Error Stack

The stack trace of the error for debugging purpose. This field is filled if the service request failed at the server side. CLOB

mfbaseid

Fabric Base Application ID

This is applicable if the client application is pointing to a Fabric application in the backend to retrieve data for service requests, instead of traditional Kony Integration Server service definition per application. This is a GUID generated by Fabric server when application is first defined. This is same across different servers if the application is published to different servers. VARCHAR2(255)

mfaid

Fabric Application ID

This is applicable if the client application is pointing to a Fabric application in the backend to retrieve data for service requests, instead of traditional Kony Integration Server service definition per application. This is a name provided by developer in Fabric server when application is first defined. This is same across different servers if the application is published to different servers. VARCHAR2(255)

mfaname

Fabric Application Name

This is applicable if the client application is pointing to a Fabric application in the backend to retrieve data for service requests, instead of traditional Kony VARCHAR2(255)

Page 34

Integration Server service definition per application. This is a GUID generated by Fabric server when application is published to a cloud. This is different in different servers if the application is published to different servers.

svcgroup Service Group Service Group VARCHAR2(255)

psvcgroup Parent Service Group

Service Group of the parent service that invoked the actual service VARCHAR2(255)

rver

Integration Service Version Header

Requested integration services version - version requested by SDK in header of http request. VARCHAR2(50)

svcver Service Version Integration service version VARCHAR2(50)





oname Object Name Object name for which mapping is done VARCHAR2(255) omethod Object Method http verb for the object (PUT, POST..) VARCHAR2(50) svctype Service Type valid values are Integration, Orchestration, Object VARCHAR2(100) contype Connector Type Connector Type VARCHAR2(100)

xmode XMode

To differentiate online call vs offline call. Default value is online, for sync calls from offline objects it should be offline VARCHAR2(100)



reqtype Request Type Type of request from the device VARCHAR2(50) reqbytes Request Bytes Transaction request data in bytes NUMBER respbytes Response Bytes Transaction response data in bytes NUMBER

reqprsdur



respprsdur



Page 35

incnfdur Interceptor Conflict Duration



iserror Is Error True if any error occurs during sync service call, otherwise false VARCHAR2(10)


3.8. Table: api_requests




YES NUMBER(20)


VARCHAR2(255)



YES VARCHAR2(255)

eid Environment ID


YES VARCHAR2(255)

Page 36


VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(255)



VARCHAR2(255)

rid RequestID RequestID - A unique ID generated for this request YES VARCHAR2(255)

request_key Request Key Surrogate request key YES NUMBER(20) idur idur Internal Duration - A numeric value in milliseconds - time

to process a request minus the time it takes for backend systems to respond

YES NUMBER


YES NUMBER


VARCHAR2(255)


YES TIMESTAMP(6)

svcid ServiceID Service ID - A unique ID of the service the client called. YES VARCHAR2(255)


YES VARCHAR2(255)



) zip Postal code VARCHAR2(32) lat Latitude NUMBER(8,5) lon Longitude NUMBER(8,5)

Page 37

dmacd Metro code NUMBER areacd Area code VARCHAR2(3) predur PreProcessor




YES NUMBER



YES NUMBER




YES VARCHAR2(50)


VARCHAR2(50)



NUMBER



NUMBER


VARCHAR2(4000)



VARCHAR2(4000)



CLOB

Page 38



VARCHAR2(255)



VARCHAR2(255)



VARCHAR2(255)


VARCHAR2(255)

rver








oname Object Name Object name for which mapping is done VARCHAR2(255)

omethod Object Method http verb for the object (PUT, POST..) VARCHAR2(50)

Page 39

svctype Service Type valid values are Integration, Orchestration, Object VARCHAR2(100)


VARCHAR2(100)


reqtype Request Type Type of request from the device VARCHAR2(50)



reqprsdur



respprsdur



incnfdur





Page 40

3.9. Table: api_sub_requests




YES NUMBER(20)


VARCHAR2(255)



YES VARCHAR2(255)

eid Environment ID


YES VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(255)



VARCHAR2(255)

rid RequestID RequestID - A unique ID generated for this request YES VARCHAR2(255)

idur idur Internal Duration - A numeric value in milliseconds - time to process a request minus the time it takes for backend systems to respond

YES NUMBER


YES NUMBER


VARCHAR2(255)

Page 41


YES TIMESTAMP(6)

svcid ServiceID Service ID - A unique ID of the service the client called. YES VARCHAR2(255)

psvcid Parent ServiceID

Service ID - A unique ID of the service the client called. YES VARCHAR2(255)


YES VARCHAR2(255)



) zip Postal code VARCHAR2(32) lat Latitude NUMBER(8,5) lon Longitude NUMBER(8,5) dmacd Metro code NUMBER areacd Area code VARCHAR2(3) predur PreProcessor




YES NUMBER



YES NUMBER




YES VARCHAR2(50)


VARCHAR2(50)

Page 42



NUMBER



NUMBER


VARCHAR2(4000)



VARCHAR2(4000)



CLOB



VARCHAR2(255)



VARCHAR2(255)



VARCHAR2(255)

Page 43


VARCHAR2(255)

psvcgroup Parent Service Group

Service Group of the parent service that invoked the actual service

VARCHAR2(255)

rver








oname Object Name Object name for which mapping is done VARCHAR2(255)

omethod Object Method http verb for the object (PUT, POST..) VARCHAR2(50)

svctype Service Type valid values are Integration, Orchestration, Object VARCHAR2(100)


VARCHAR2(100)


reqtype Request Type Type of request from the device VARCHAR2(50)



reqprsdur



respprsdur



Page 44

incnfdur






Page 45

4 Custom Metrics For custom_metrics_master data, which key is mapped to each sequential data type section (s1, s2, l1, I2) will vary for each app. The fields are assigned in the order in which the fields were originally created in the Fabric console. As an example, the first integer data type be l1 and the second integer defined would be I2. Thus, second string value defined as s2 and so on. The custom metrics keys in custom metrics tab is sorted, so exact order of creation can’t be found later from console but can be manually found from crpt_metric table, or from custom reports builder by hovering over the field name while building report.

4.1 Table: custom_metrics_master Description: This table stores custom metrics data sent by Kony Integration Server applications, either from the client or server pre or post processors.




YES VARCHAR2(255)


VARCHAR2(255)



YES VARCHAR2(255)

eid Environment ID


YES VARCHAR2(255)


YES VARCHAR2(255)

request_key Request Key Surrogate request key YES NUMBER(20)

s1 .. s50 metric Metrics of data type string VARCHAR2(255)

l1 .. l25 metric Metrics of data type integer NUMBER

d1 .. d25 metric Metrics of data type double FLOAT(126) b1 .. b25 metric Metrics of data type boolean CHAR(1) t1 .. t25 metric Metrics of data type timestamp TIMESTAMP(6) dt1 .. dt25 metric Metrics of data type date DATE

Page 46



VARCHAR2(255)



VARCHAR2(255)



VARCHAR2(255)


true if the evttype is error/crash and false if evttype is exception

VARCHAR2(255)


YES TIMESTAMP(6)

session_key Session Key Surrogate session key

NUMBER(20) chnl Channel The application channel - [mobile, tablet, desktop] –

Could be new values in the future.

VARCHAR2(255)


The atype can be [native, mixedmode, hybrid, spa, mobileweb] – Could be new values in the future.

VARCHAR2(255)


VARCHAR2(255)

rip Remote IP The remote IP address from the HTTP header. Should be the public facing IP address of the client. Need to find if

VARCHAR2(255)

Page 47

that is still available in the HTTP header somewhere once the request hits a server.


VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(255)


Client application version

VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(255)


VARCHAR2(2)

region Region code

VARCHAR2(10)

city City name

VARCHAR2(255)

zip Postal code

VARCHAR2(32) lat Latitude

NUMBER(8,5)

lon Longitude

NUMBER(8,5)

dmacd Metro code

NUMBER

areacd Area code

VARCHAR2(3)


VARCHAR2(50)


VARCHAR2(50)

rid RequestID RequestID - A unique ID generated for this request

VARCHAR2(255)

Page 48

sid SessionID A unique ID for this session. All requests to the server executed within the same session will have the same Session ID

VARCHAR2(255)

svcid ServiceID Service ID - A unique ID of the service the client called.

VARCHAR2(255)

Page 49

4.2 Table: crpt_metric



owner_id Owner ID This value indicates the owner_id that maps to the crpt_owner table

YES NUMEBR(20)

name Name Name of the metrics created from the console YES VARCHAR2(255)

mtype Measure Type Measure /dimension that we are selecting while creating the metric.

YES VARCHAR2(255)

dtype Data Type Data type of the metric we are creating. YES VARCHAR2(255)

aggr_func Aggregation Function

Aggregation Function . Sample values : sum/average/highest/count/lowest .. etc

VARCHAR2(255)

is_deleted Is Deleted Sample values 0/1. 1– Indicates metrics got soft deleted. 0 – Indicates metrics exists.

CHAR(1)

dw_column_name DW Column Name

Sample Values: L1 – l25/S1- S50 etc. These fields get mapped to the custom_metrics_master table.

YES VARCHAR2(255)

created_by Created By Audit columns VARCHAR2(255)

created_date Created Date DATE

updated_by Updated By VARCHAR2(255)

updated_date Updated Date DATE

Page 50

4.3 Table: crpt_owner





YES VARCHAR2(255)

eid Environment ID


YES VARCHAR2(255)


YES VARCHAR2(255)

dw_table_name DW Table Name

Custom Metrics Master table name YES VARCHAR2(255)

jrs_domain Jasper Domain Name of the jrs domain VARCHAR2(255)

created_by Created By Audit columns VARCHAR2(255)

created_date Created Date DATE



Page 51

4.4 Table: crpt_master_info

Column name Business name Description Required Data type

datatype Data Type

This column represents the data types supported for creating the different custom metrics. EX: String/Long/Double/Date/TimeStamp/Boolean YES VARCHAR2(20)

col_prefix Column Prefix

This Column represents the data type prefix letters used during custom metric creation. EX: s/l/d/dt/t/b YES VARCHAR2(20)

col_count Column Count

The max number of custom metrics that can be created for different data types. EX: 25/50 YES NUMBER

col_metadata Column Metadata

This column represents the data type supported for different columns. EX: varchar(255)/bigint/float etc YES VARCHAR2(255)

jas_datatype Jasper Data Type This column represents the jasper supported data types. VARCHAR2(255)

created_by Created By VARCHAR2(255)

created_date Created Date Audit Columns DATE



Page 52

5 Invalid Messages

5.1 Table: invalid_messages




YES VARCHAR2(255)

msg_body Message Body Complete payload that got failed during processing. YES VARCHAR2(4000)

msg_type Message Type Indicate the table name for which message processing got failed.

YES VARCHAR2(255)

rsn Reason Reason for which message failed during processing. YES VARCHAR2(1000)

insert_date Insert Date Insertion Date YES TIMESTAMP(6)

Page 53

6 License Info

6.1 Table: licenseinfo



licensetype License Type Type of the license we are fetching. EX: SessionsData/NamedUsers/Devices etc

YES VARCHAR2(20)

insertdate Insert Date Insertion date YES DATE

effectivedate Effective Date Effective date YES DATE

lastyear Last Year Count of the total number of sessions logged in last year. NUMBER

yeartodate Year to Date Count of the total number of sessions logged from present year starting date to current date.

NUMBER

lastquarter Last Quarter Count of the total number of sessions logged in last quarter.

NUMBER

quartertodate Quarter to Date

Count of the total number of sessions logged from present quarter starting date to current date.

NUMBER

lastmonth Last Month Count of the total number of sessions logged in last month.

NUMBER

error Error This column stores the error data if any while fetching the data.

CLOB

modifieddate Modified Date Audit Column TIMESTAMP(6)

Page 54

7 Utility Tables This data need not be imported if imported to a BI or reporting engine. This is more for generating data for the tables mentioned in previous sections

7.1 Table: dw_keys_session


session_key Session Key Unique Surrogate session key generated from sid and hash_code YES NUMBER(20)

sid Session ID

A unique ID for every session. All requests to the server executed within the same session will have the same Session ID YES RAW(255)

hash_code Hash Code Hash code generated by combining sid and eid parameters YES RAW(255) insert_date Insert Date Insertion date of the row into the table YES TIMESTAMP(6) created_by Created By Audit Columns VARCHAR2(255) created_date Created Date DATE updated_by Updated By VARCHAR2(255) updated_date Updated Date DATE

7.2 Table: dw_keys_request


request_key Request Key Unique Surrogate request key generated from rid, eid and time stamp. YES NUMBER(20)

rid Request ID A unique ID generated for this request YES VARCHAR2(255)

eid Environment ID This is a value generated by Kony to uniquely identify this cloud environment within the customer’s account YES VARCHAR2(255)

ts Time Stamp

A String representation of the server date and time when the request was received including timezone and must be in the format of "yyyy-mm-dd HH:MM:SS". A day is defined as 12:01am to 12:00am UTC time YES TIMESTAMP(6)

insert_date Insert Date Insertion date of the row into table. YES TIMESTAMP(6)

Page 55

created_by Created By Audit Columns VARCHAR2(255) created_date Created Date DATE updated_by Updated By VARCHAR2(255) updated_date Updated Date DATE

7.3 Table: geolocations_ip4


startipnum Start IP Number Start IP number for a particular range of IP’s. EX: 1.22.45.0 VARCHAR2(15)

endipnum End IP Number End IP number for a particular range of IP’s. EX: 1.22.45.255 VARCHAR2(15)

startipint Start IP Integer Integer representation of the startipnum column YES NUMBER endipint End IP Integer Integer representation of the endipnum column YES NUMBER country Country The country code for this location in the file's locale. VARCHAR2(2) region Region The region code for this location in the file's locale. VARCHAR2(10) city City The city name for this location in the file's locale. VARCHAR2(255)

postalcode Postal Code

A postal code close to the user's location. We return the first 3 characters for Canadian postal codes. We return the first 2-4 characters (outward code) for postal codes in the United Kingdom. VARCHAR2(32)

latitude Latitude The approximate latitude of the postal code, city, subdivision or country associated with the IP address NUMBER(8,5)

longitude Longitude The approximate longitude of the postal code, city, subdivision or country associated with the IP address. NUMBER(8,5)

dmacode Metro Code

The metro code associated with the location. These are only available for networks in the US. MaxMind provides the same metro codes as used by Google Marketing Platform. VARCHAR2(3)

areacode Area Code The area code for this location in the file's locale. VARCHAR2(3) created_by Created By VARCHAR2(255)

Page 56

created_date Created Date Audit Columns DATE updated_by Updated By VARCHAR2(255) updated_date Updated Date DATE continentcode Continent Code The continent code for this location in the file's locale. VARCHAR2(10) continentname Continent Name The continent name for this location in the file's locale. VARCHAR2(255) countryname Country Name The country name for this location in the file's locale. VARCHAR2(255) regionname Region Name The region name for this location in the file's locale. VARCHAR2(255)

timezone Time Zone

The time zone associated with location, as specified by the IANA Time Zone Database, e.g., “America/New_York”. VARCHAR2(255)

isineuropeanunion Is in European Union

This is 1 if the country associated with the location is a member state of the European Union. It is 0 otherwise. CHAR(1)

ipspatial IP Spatial The physical location and shape of geometric objects. Here we use to represent the IP in a 2D plane SDO_GEOMETRY

7.4 Table: dim_date


date_key Date Key This column represents the date as key in the below format. EX: 20100101(YYYYMMDD) YES NUMBER(10)

dt Date

This column represents the date in complete format including timestamp. EX: 2010-01-01 00:00:00 (YYYY-MM-DD HH:mm:SS) YES DATE

year_number Year Number This column gives the year number specified in date_key column EX: 2010 YES NUMBER(10)

quarter_number Quarter Number

This column represents which quarter the date present in date_key column. EX: 1 YES NUMBER(10)

quarter_name Quarter Name This column represents the quarter name. EX: Quarter 1 YES VARCHAR2(10)

Page 57

month_number Month Number

This column represents the month number present in the date_key column. EX: 1 YES NUMBER(10)

month_name Month Name This column represents the month name. EX: January YES VARCHAR2(10)

month_short_name Month Short Name

This column represents the month name in short form. EX: Jan YES VARCHAR2(3)

week_of_year Week of the Year

This column represents which week in the year the date_key belongs to. EX:1 YES NUMBER(10)

week_of_month Week of the Month

This column represents which week in the month the date_key belongs to. EX:1 YES NUMBER(10)

month_full_weeks Month Full Weeks

This column represents how many weeks present in the month. EX:4 YES NUMBER(10)

full_week_flag Full Week Flag This column represents the date_key is full week or not. EX:1 YES NUMBER(10)

day_of_week_number Day of Week Number This column represents the day of the week number EX: 1 YES NUMBER(10)

day_of_week_short_name Day of Week Short Name This column represents the week short name. EX: MON YES VARCHAR2(3)

day_of_week_name Day of Week Name This column represents the week name. EX: Monday YES VARCHAR2(10)

day_number Day Number This column represents the day in the date_key column EX: 1 YES NUMBER(10)

7.5 Table: jrs_fusionmap_usa


geoname_state Geoname State Geographical name of each state in US VARCHAR2(2)

chartentityid Chartentity Id

Predefined unique internal IDs to reference each entity i.e each state name VARCHAR2(2)

shortname Short Name This column represents the short name of all the states present in US VARCHAR2(2) longname Long Name This column represents the long name of all the states present in US VARCHAR2(20)

Page 58

7.6 Table: jrs_fusionmap_world


geoname_country Geoname Country Geographical name of all the counties VARCHAR2(2)

chartentityid Chartentity Id Predefined unique internal IDs to reference each entity i.e each country VARCHAR2(3)

shortname Short Name This column represents the short name of all the countries. VARCHAR2(2)

longname Long Name This column represents the long name of all the countries. VARCHAR2(50)

7.7 Table: metrics_application_log


service_name Service Name This column represents the service name for which we are going to log the messages. VARCHAR2(255)

log_level Log Level This column represents the log level we are defining for the project. VARCHAR2(255)

event_date Event Date This column represents the event date VARCHAR2(255)

request_id Request Id This column represents the request id for which we are logging the log. VARCHAR2(255)

Page 59

thread_name Thread Name This column tell the thread name for which we are logging the log. VARCHAR2(255)

additonal_info Additonal Info Any additional info is been logged into this column. VARCHAR2(255) log_message Log Message This column represents the actual log message. VARCHAR2(4000) exception_trace Exception Trace The complete stack trace is been logged into this column CLOB

7.8 Table: metrics_configuration


name Name

This column contains some key where we can change the values so that we have some behavior changes in the code.For Example: Giving the log level to the metrics code by default as INFO and we can change to DEBUG if required from here.

YES VARCHAR2(50)

value Value Value for the above specified key YES VARCHAR2(255) created_date Created Date Created Date DATE updated_date Updated Date Updated Date DATE

7.9 Table: tmp_calendar


dt Date This column contains date YES DATE

Documents

Fabric Reporting Database Data Dictionary