Revert outbound_mng INSERT to source_table/source_id only

DB has no sales_order_id/shipment_plan_id/item_info_id columns
(mhkim original work shipped without migration DDL), so the re-applied
INSERT would error at runtime. Roll back to jskim-side column list
to keep outbound registration working; getProductionResults endpoint
restoration is unaffected.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
kmh
2026-05-22 09:52:39 +09:00
parent ba1f8af47b
commit a86a191a22

View File

@@ -144,7 +144,7 @@ export async function create(req: AuthenticatedRequest, res: Response) {
outbound_qty, unit_price, total_amount,
lot_number, warehouse_code, location_code,
outbound_status, manager_id, memo,
source_table, source_id, sales_order_id, shipment_plan_id, item_info_id,
source_table, source_id,
destination_code, delivery_destination, delivery_address,
created_date, created_by, writer, status
) VALUES (
@@ -154,9 +154,9 @@ export async function create(req: AuthenticatedRequest, res: Response) {
$13, $14, $15,
$16, $17, $18,
$19, $20, $21,
$22, $23, $24, $25, $26,
$27, $28, $29,
NOW(), $30, $30, '출고'
$22, $23,
$24, $25, $26,
NOW(), $27, $27, '출고'
) RETURNING *`,
[
companyCode,
@@ -180,11 +180,8 @@ export async function create(req: AuthenticatedRequest, res: Response) {
item.outbound_status || "대기",
manager_id || item.manager_id || null,
memo || item.memo || null,
item.source_type || item.source_table || null,
item.source_table || null,
item.source_id || null,
item.sales_order_id || null,
item.shipment_plan_id || null,
item.item_info_id || null,
item.destination_code || null,
item.delivery_destination || null,
item.delivery_address || null,