Skip to content

DELETE /yms/scale/tickets/(?P\d+)

YMS > yms.scale

What it does

#^/yms/scale/tickets/(?P<id>\d+)$# accepts DELETE and is declared in app/systems/YMS/scale/api_routes.php:305 as a regex pattern.

The route handler delegates to scale_portal_post_handle(). That function is the owner of this behaviour; the route entry is only dispatch.

Call chain:

  1. → scale_portal_post_handle() — app/systems/OMS/inbound-order/scale_portal_post_helper.php:2
  2. ↳ scale_portal_generate_ticket_number() — app/systems/OMS/inbound-order/scale_portal_post_helper.php:435
  3. ↳ getClientId() — config/config.php:45

Who calls it

No literal caller path was found in frontend/, public/ or new-system/. The endpoint may be called through a constructed path, a helper wrapper, or only by an external client. Treat the route table and owner function as the authority.

Input

Where Key
path id
body ID
body ORDER_ID
body WEIGHT_PREFIX

Request bodies must not use TYPE, ACTION or USERNAME as contract fields.

Output

The response is produced by a shared helper, so the key set is not visible at the route. Read the owner function to confirm the shape before writing a client.

SQL executed

SELECT TICKET_NUMBER FROM T_LOAD

SELECT ID FROM T_SCALE_TICKET

INSERT INTO T_SCALE_TICKET (

SELECT TICKET_NUMBER FROM T_SCALE_TICKET WHERE CLIENT_ID = ? AND TICKET_NUMBER LIKE ? ORDER BY TICKET_NUMBER DESC LIMIT 1

Data

Tables reached from the owner function:

  • T_LOAD
  • T_SCALE_TICKET

Access

  • module-gated on yms.scale, so tenant module access applies