answer_format stringclasses 2
values | category stringclasses 4
values | depth int64 1 6 | family stringclasses 12
values | instruction stringlengths 71 404 | kind stringclasses 1
value | month_end int64 203k 203k | month_start int64 203k 203k | region stringclasses 4
values | task_id stringlengths 24 37 |
|---|---|---|---|---|---|---|---|---|---|
exact integer | A | 5 | reorder_shortfall | Find the top-selling product id for region NA, category A, months 202601-202603. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,603 | 202,601 | NA | v3_depth5_reorder_shortfall_t0 |
exact integer | B | 5 | reorder_shortfall | Find the top-selling product id for region NA, category B, months 202604-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,606 | 202,604 | NA | v3_depth5_reorder_shortfall_t1 |
exact integer | C | 5 | reorder_shortfall | Find the top-selling product id for region EU, category C, months 202601-202604. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,604 | 202,601 | EU | v3_depth5_reorder_shortfall_t2 |
exact integer | D | 5 | reorder_shortfall | Find the top-selling product id for region EU, category D, months 202603-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,606 | 202,603 | EU | v3_depth5_reorder_shortfall_t3 |
exact integer | A | 5 | reorder_shortfall | Find the top-selling product id for region APAC, category A, months 202602-202605. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily dem... | ops | 202,605 | 202,602 | APAC | v3_depth5_reorder_shortfall_t4 |
exact integer | D | 5 | reorder_shortfall | Find the top-selling product id for region APAC, category D, months 202601-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily dem... | ops | 202,606 | 202,601 | APAC | v3_depth5_reorder_shortfall_t5 |
exact integer | B | 5 | reorder_shortfall | Find the top-selling product id for region LATAM, category B, months 202601-202604. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily de... | ops | 202,604 | 202,601 | LATAM | v3_depth5_reorder_shortfall_t6 |
exact integer | C | 5 | reorder_shortfall | Find the top-selling product id for region LATAM, category C, months 202603-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily de... | ops | 202,606 | 202,603 | LATAM | v3_depth5_reorder_shortfall_t7 |
exact integer | D | 5 | reorder_shortfall | Find the top-selling product id for region NA, category D, months 202602-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,606 | 202,602 | NA | v3_depth5_reorder_shortfall_t8 |
exact integer | A | 5 | reorder_shortfall | Find the top-selling product id for region EU, category A, months 202602-202605. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,605 | 202,602 | EU | v3_depth5_reorder_shortfall_t9 |
exact integer | B | 5 | reorder_shortfall | Find the top-selling product id for region APAC, category B, months 202604-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily dem... | ops | 202,606 | 202,604 | APAC | v3_depth5_reorder_shortfall_t10 |
exact integer | A | 5 | reorder_shortfall | Find the top-selling product id for region LATAM, category A, months 202601-202603. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily de... | ops | 202,603 | 202,601 | LATAM | v3_depth5_reorder_shortfall_t11 |
exact integer | C | 5 | reorder_shortfall | Find the top-selling product id for region NA, category C, months 202601-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,606 | 202,601 | NA | v3_depth5_reorder_shortfall_t12 |
exact integer | B | 5 | reorder_shortfall | Find the top-selling product id for region EU, category B, months 202601-202603. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,603 | 202,601 | EU | v3_depth5_reorder_shortfall_t13 |
exact integer | C | 5 | reorder_shortfall | Find the top-selling product id for region APAC, category C, months 202602-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily dem... | ops | 202,606 | 202,602 | APAC | v3_depth5_reorder_shortfall_t14 |
exact integer | D | 5 | reorder_shortfall | Find the top-selling product id for region LATAM, category D, months 202601-202605. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily de... | ops | 202,605 | 202,601 | LATAM | v3_depth5_reorder_shortfall_t15 |
exact integer | A | 5 | reorder_shortfall | Find the top-selling product id for region NA, category A, months 202604-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,606 | 202,604 | NA | v3_depth5_reorder_shortfall_t16 |
exact integer | D | 5 | reorder_shortfall | Find the top-selling product id for region EU, category D, months 202601-202602. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,602 | 202,601 | EU | v3_depth5_reorder_shortfall_t17 |
exact integer | A | 5 | reorder_shortfall | Find the top-selling product id for region APAC, category A, months 202603-202604. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily dem... | ops | 202,604 | 202,603 | APAC | v3_depth5_reorder_shortfall_t18 |
exact integer | B | 5 | reorder_shortfall | Find the top-selling product id for region LATAM, category B, months 202605-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily de... | ops | 202,606 | 202,605 | LATAM | v3_depth5_reorder_shortfall_t19 |
exact integer | C | 5 | reorder_shortfall | Find the top-selling product id for region NA, category C, months 202602-202604. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,604 | 202,602 | NA | v3_depth5_reorder_shortfall_t20 |
exact integer | B | 5 | reorder_shortfall | Find the top-selling product id for region EU, category B, months 202604-202606. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,606 | 202,604 | EU | v3_depth5_reorder_shortfall_t21 |
exact integer | D | 5 | reorder_shortfall | Find the top-selling product id for region APAC, category D, months 202603-202605. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily dem... | ops | 202,605 | 202,603 | APAC | v3_depth5_reorder_shortfall_t22 |
exact integer | C | 5 | reorder_shortfall | Find the top-selling product id for region LATAM, category C, months 202601-202602. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily de... | ops | 202,602 | 202,601 | LATAM | v3_depth5_reorder_shortfall_t23 |
exact integer | D | 5 | reorder_shortfall | Find the top-selling product id for region NA, category D, months 202601-202603. For that product, compute inventory position (on_hand - reserved + inbound), estimate daily demand as floor(units sold in the window / 4) with a minimum of 1, compute planning demand as (lead_time_days + 21 safety-stock days) * daily deman... | ops | 202,603 | 202,601 | NA | v3_depth5_reorder_shortfall_t24 |
exact integer | A | 5 | delayed_net_revenue | For region NA, category A, months 202601-202603: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,603 | 202,601 | NA | v3_depth5_delayed_net_revenue_t0 |
exact integer | B | 5 | delayed_net_revenue | For region NA, category B, months 202604-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,606 | 202,604 | NA | v3_depth5_delayed_net_revenue_t1 |
exact integer | C | 5 | delayed_net_revenue | For region EU, category C, months 202601-202604: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,604 | 202,601 | EU | v3_depth5_delayed_net_revenue_t2 |
exact integer | D | 5 | delayed_net_revenue | For region EU, category D, months 202603-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,606 | 202,603 | EU | v3_depth5_delayed_net_revenue_t3 |
exact integer | A | 5 | delayed_net_revenue | For region APAC, category A, months 202602-202605: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,605 | 202,602 | APAC | v3_depth5_delayed_net_revenue_t4 |
exact integer | D | 5 | delayed_net_revenue | For region APAC, category D, months 202601-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,606 | 202,601 | APAC | v3_depth5_delayed_net_revenue_t5 |
exact integer | B | 5 | delayed_net_revenue | For region LATAM, category B, months 202601-202604: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,604 | 202,601 | LATAM | v3_depth5_delayed_net_revenue_t6 |
exact integer | C | 5 | delayed_net_revenue | For region LATAM, category C, months 202603-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,606 | 202,603 | LATAM | v3_depth5_delayed_net_revenue_t7 |
exact integer | D | 5 | delayed_net_revenue | For region NA, category D, months 202602-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,606 | 202,602 | NA | v3_depth5_delayed_net_revenue_t8 |
exact integer | A | 5 | delayed_net_revenue | For region EU, category A, months 202602-202605: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,605 | 202,602 | EU | v3_depth5_delayed_net_revenue_t9 |
exact integer | B | 5 | delayed_net_revenue | For region APAC, category B, months 202604-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,606 | 202,604 | APAC | v3_depth5_delayed_net_revenue_t10 |
exact integer | A | 5 | delayed_net_revenue | For region LATAM, category A, months 202601-202603: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,603 | 202,601 | LATAM | v3_depth5_delayed_net_revenue_t11 |
exact integer | C | 5 | delayed_net_revenue | For region NA, category C, months 202601-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,606 | 202,601 | NA | v3_depth5_delayed_net_revenue_t12 |
exact integer | B | 5 | delayed_net_revenue | For region EU, category B, months 202601-202603: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,603 | 202,601 | EU | v3_depth5_delayed_net_revenue_t13 |
exact integer | C | 5 | delayed_net_revenue | For region APAC, category C, months 202602-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,606 | 202,602 | APAC | v3_depth5_delayed_net_revenue_t14 |
exact integer | D | 5 | delayed_net_revenue | For region LATAM, category D, months 202601-202605: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,605 | 202,601 | LATAM | v3_depth5_delayed_net_revenue_t15 |
exact integer | A | 5 | delayed_net_revenue | For region NA, category A, months 202604-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,606 | 202,604 | NA | v3_depth5_delayed_net_revenue_t16 |
exact integer | D | 5 | delayed_net_revenue | For region EU, category D, months 202601-202602: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,602 | 202,601 | EU | v3_depth5_delayed_net_revenue_t17 |
exact integer | A | 5 | delayed_net_revenue | For region APAC, category A, months 202603-202604: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,604 | 202,603 | APAC | v3_depth5_delayed_net_revenue_t18 |
exact integer | B | 5 | delayed_net_revenue | For region LATAM, category B, months 202605-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,606 | 202,605 | LATAM | v3_depth5_delayed_net_revenue_t19 |
exact integer | C | 5 | delayed_net_revenue | For region NA, category C, months 202602-202604: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,604 | 202,602 | NA | v3_depth5_delayed_net_revenue_t20 |
exact integer | B | 5 | delayed_net_revenue | For region EU, category B, months 202604-202606: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,606 | 202,604 | EU | v3_depth5_delayed_net_revenue_t21 |
exact integer | D | 5 | delayed_net_revenue | For region APAC, category D, months 202603-202605: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,605 | 202,603 | APAC | v3_depth5_delayed_net_revenue_t22 |
exact integer | C | 5 | delayed_net_revenue | For region LATAM, category C, months 202601-202602: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,602 | 202,601 | LATAM | v3_depth5_delayed_net_revenue_t23 |
exact integer | D | 5 | delayed_net_revenue | For region NA, category D, months 202601-202603: get the paid/refunded orders, keep only orders whose ship_days exceeded promised_days, compute net USD revenue after loyalty discounts and refunds for those delayed orders, and report the total. | ops | 202,603 | 202,601 | NA | v3_depth5_delayed_net_revenue_t24 |
exact integer | A | 6 | delay_sla_burden | For region NA, category A, months 202601-202603: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,603 | 202,601 | NA | v3_depth6_delay_sla_burden_t0 |
exact integer | B | 6 | delay_sla_burden | For region NA, category B, months 202604-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,606 | 202,604 | NA | v3_depth6_delay_sla_burden_t1 |
exact integer | C | 6 | delay_sla_burden | For region EU, category C, months 202601-202604: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,604 | 202,601 | EU | v3_depth6_delay_sla_burden_t2 |
exact integer | D | 6 | delay_sla_burden | For region EU, category D, months 202603-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,606 | 202,603 | EU | v3_depth6_delay_sla_burden_t3 |
exact integer | A | 6 | delay_sla_burden | For region APAC, category A, months 202602-202605: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,605 | 202,602 | APAC | v3_depth6_delay_sla_burden_t4 |
exact integer | D | 6 | delay_sla_burden | For region APAC, category D, months 202601-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,606 | 202,601 | APAC | v3_depth6_delay_sla_burden_t5 |
exact integer | B | 6 | delay_sla_burden | For region LATAM, category B, months 202601-202604: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,604 | 202,601 | LATAM | v3_depth6_delay_sla_burden_t6 |
exact integer | C | 6 | delay_sla_burden | For region LATAM, category C, months 202603-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,606 | 202,603 | LATAM | v3_depth6_delay_sla_burden_t7 |
exact integer | D | 6 | delay_sla_burden | For region NA, category D, months 202602-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,606 | 202,602 | NA | v3_depth6_delay_sla_burden_t8 |
exact integer | A | 6 | delay_sla_burden | For region EU, category A, months 202602-202605: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,605 | 202,602 | EU | v3_depth6_delay_sla_burden_t9 |
exact integer | B | 6 | delay_sla_burden | For region APAC, category B, months 202604-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,606 | 202,604 | APAC | v3_depth6_delay_sla_burden_t10 |
exact integer | A | 6 | delay_sla_burden | For region LATAM, category A, months 202601-202603: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,603 | 202,601 | LATAM | v3_depth6_delay_sla_burden_t11 |
exact integer | C | 6 | delay_sla_burden | For region NA, category C, months 202601-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,606 | 202,601 | NA | v3_depth6_delay_sla_burden_t12 |
exact integer | B | 6 | delay_sla_burden | For region EU, category B, months 202601-202603: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,603 | 202,601 | EU | v3_depth6_delay_sla_burden_t13 |
exact integer | C | 6 | delay_sla_burden | For region APAC, category C, months 202602-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,606 | 202,602 | APAC | v3_depth6_delay_sla_burden_t14 |
exact integer | D | 6 | delay_sla_burden | For region LATAM, category D, months 202601-202605: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,605 | 202,601 | LATAM | v3_depth6_delay_sla_burden_t15 |
exact integer | A | 6 | delay_sla_burden | For region NA, category A, months 202604-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,606 | 202,604 | NA | v3_depth6_delay_sla_burden_t16 |
exact integer | D | 6 | delay_sla_burden | For region EU, category D, months 202601-202602: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,602 | 202,601 | EU | v3_depth6_delay_sla_burden_t17 |
exact integer | A | 6 | delay_sla_burden | For region APAC, category A, months 202603-202604: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,604 | 202,603 | APAC | v3_depth6_delay_sla_burden_t18 |
exact integer | B | 6 | delay_sla_burden | For region LATAM, category B, months 202605-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,606 | 202,605 | LATAM | v3_depth6_delay_sla_burden_t19 |
exact integer | C | 6 | delay_sla_burden | For region NA, category C, months 202602-202604: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,604 | 202,602 | NA | v3_depth6_delay_sla_burden_t20 |
exact integer | B | 6 | delay_sla_burden | For region EU, category B, months 202604-202606: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,606 | 202,604 | EU | v3_depth6_delay_sla_burden_t21 |
exact integer | D | 6 | delay_sla_burden | For region APAC, category D, months 202603-202605: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,605 | 202,603 | APAC | v3_depth6_delay_sla_burden_t22 |
exact integer | C | 6 | delay_sla_burden | For region LATAM, category C, months 202601-202602: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,602 | 202,601 | LATAM | v3_depth6_delay_sla_burden_t23 |
exact integer | D | 6 | delay_sla_burden | For region NA, category D, months 202601-202603: get the orders, count delayed orders where ship_days exceeded promised_days, find high and critical support tickets for those orders, count tickets that breach a 24-hour first-response or 120-hour resolution SLA, and report delayed_order_count + breached_ticket_count. | ops | 202,603 | 202,601 | NA | v3_depth6_delay_sla_burden_t24 |
exact integer | A | 6 | breached_ticket_revenue | For region NA, category A, months 202601-202603: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,603 | 202,601 | NA | v3_depth6_breached_ticket_revenue_t0 |
exact integer | B | 6 | breached_ticket_revenue | For region NA, category B, months 202604-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,606 | 202,604 | NA | v3_depth6_breached_ticket_revenue_t1 |
exact integer | C | 6 | breached_ticket_revenue | For region EU, category C, months 202601-202604: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,604 | 202,601 | EU | v3_depth6_breached_ticket_revenue_t2 |
exact integer | D | 6 | breached_ticket_revenue | For region EU, category D, months 202603-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,606 | 202,603 | EU | v3_depth6_breached_ticket_revenue_t3 |
exact integer | A | 6 | breached_ticket_revenue | For region APAC, category A, months 202602-202605: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds f... | ops | 202,605 | 202,602 | APAC | v3_depth6_breached_ticket_revenue_t4 |
exact integer | D | 6 | breached_ticket_revenue | For region APAC, category D, months 202601-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds f... | ops | 202,606 | 202,601 | APAC | v3_depth6_breached_ticket_revenue_t5 |
exact integer | B | 6 | breached_ticket_revenue | For region LATAM, category B, months 202601-202604: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds ... | ops | 202,604 | 202,601 | LATAM | v3_depth6_breached_ticket_revenue_t6 |
exact integer | C | 6 | breached_ticket_revenue | For region LATAM, category C, months 202603-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds ... | ops | 202,606 | 202,603 | LATAM | v3_depth6_breached_ticket_revenue_t7 |
exact integer | D | 6 | breached_ticket_revenue | For region NA, category D, months 202602-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,606 | 202,602 | NA | v3_depth6_breached_ticket_revenue_t8 |
exact integer | A | 6 | breached_ticket_revenue | For region EU, category A, months 202602-202605: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,605 | 202,602 | EU | v3_depth6_breached_ticket_revenue_t9 |
exact integer | B | 6 | breached_ticket_revenue | For region APAC, category B, months 202604-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds f... | ops | 202,606 | 202,604 | APAC | v3_depth6_breached_ticket_revenue_t10 |
exact integer | A | 6 | breached_ticket_revenue | For region LATAM, category A, months 202601-202603: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds ... | ops | 202,603 | 202,601 | LATAM | v3_depth6_breached_ticket_revenue_t11 |
exact integer | C | 6 | breached_ticket_revenue | For region NA, category C, months 202601-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,606 | 202,601 | NA | v3_depth6_breached_ticket_revenue_t12 |
exact integer | B | 6 | breached_ticket_revenue | For region EU, category B, months 202601-202603: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,603 | 202,601 | EU | v3_depth6_breached_ticket_revenue_t13 |
exact integer | C | 6 | breached_ticket_revenue | For region APAC, category C, months 202602-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds f... | ops | 202,606 | 202,602 | APAC | v3_depth6_breached_ticket_revenue_t14 |
exact integer | D | 6 | breached_ticket_revenue | For region LATAM, category D, months 202601-202605: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds ... | ops | 202,605 | 202,601 | LATAM | v3_depth6_breached_ticket_revenue_t15 |
exact integer | A | 6 | breached_ticket_revenue | For region NA, category A, months 202604-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,606 | 202,604 | NA | v3_depth6_breached_ticket_revenue_t16 |
exact integer | D | 6 | breached_ticket_revenue | For region EU, category D, months 202601-202602: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,602 | 202,601 | EU | v3_depth6_breached_ticket_revenue_t17 |
exact integer | A | 6 | breached_ticket_revenue | For region APAC, category A, months 202603-202604: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds f... | ops | 202,604 | 202,603 | APAC | v3_depth6_breached_ticket_revenue_t18 |
exact integer | B | 6 | breached_ticket_revenue | For region LATAM, category B, months 202605-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds ... | ops | 202,606 | 202,605 | LATAM | v3_depth6_breached_ticket_revenue_t19 |
exact integer | C | 6 | breached_ticket_revenue | For region NA, category C, months 202602-202604: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,604 | 202,602 | NA | v3_depth6_breached_ticket_revenue_t20 |
exact integer | B | 6 | breached_ticket_revenue | For region EU, category B, months 202604-202606: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,606 | 202,604 | EU | v3_depth6_breached_ticket_revenue_t21 |
exact integer | D | 6 | breached_ticket_revenue | For region APAC, category D, months 202603-202605: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds f... | ops | 202,605 | 202,603 | APAC | v3_depth6_breached_ticket_revenue_t22 |
exact integer | C | 6 | breached_ticket_revenue | For region LATAM, category C, months 202601-202602: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds ... | ops | 202,602 | 202,601 | LATAM | v3_depth6_breached_ticket_revenue_t23 |
exact integer | D | 6 | breached_ticket_revenue | For region NA, category D, months 202601-202603: get the paid/refunded orders, find high and critical tickets for those orders, keep tickets that breach a 24-hour first-response or 120-hour resolution SLA, map those breached tickets back to their unique order ids, compute net USD revenue after discounts and refunds for... | ops | 202,603 | 202,601 | NA | v3_depth6_breached_ticket_revenue_t24 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.