hjjeong
7e7c6a0ac0
영업관리 구매요청서관리·품의서관리 신규 2메뉴 (wace_plm 1:1)
backend
- services/salesPurchaseRequestService.ts: listPurchaseRequestReg(DOC_TYPE='PURCHASE_REG') + listPurchaseRegProposal(DOC_TYPE='PURCHASE_REG_PROPOSAL')
· 구매요청서 상태 CASE: PURCHASE_REG_PROPOSAL 자식 존재 시 '품의서생성' → '확정'/'작성중' (wace 매퍼 1:1)
· 품의서 결재상태: amaranth_approval(target_type='PROPOSAL') LEFT JOIN 우선순위
· sales_request_part 누락 → MBOM_DETAIL+PART_MNG fallback (구매관리 패턴 동일)
- routes/salesPurchaseRequestRoutes.ts + app.ts: /api/sales/purchase-request, /api/sales/purchase-proposal
frontend
- lib/api/salesPurchaseRequest.ts
- sales/purchase-request/page.tsx — 14컬럼, 구매요청서작성/품의서생성 액션 (placeholder 토스트)
- sales/purchase-proposal/page.tsx — 10컬럼, 결재상신 액션 (placeholder 토스트)
- PageHeader+CompactFilterBar+SmartSelect+DataGrid logicstudio 6종 패턴 일관 적용
구매관리>품의서관리 vs 영업관리>품의서관리 차이
- 구매관리: DOC_TYPE in ('PROPOSAL', 'PURCHASE_REG_PROPOSAL'(결재완료만)) → 발주서 생성 풀
- 영업관리: DOC_TYPE='PURCHASE_REG_PROPOSAL' 전용 → 결재상신 화면 (결재완료 시 구매관리로 자동 노출)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-15 10:04:37 +09:00
..
2025-10-01 16:15:53 +09:00
2026-05-15 10:04:37 +09:00
2025-11-28 11:52:23 +09:00
2025-12-09 10:18:07 +09:00
2025-10-01 16:15:53 +09:00
2026-04-23 14:03:45 +09:00
2026-03-13 15:02:06 +09:00
2026-03-11 15:53:01 +09:00
2026-04-28 13:59:34 +09:00
2026-03-12 18:47:42 +09:00
2026-05-07 16:58:02 +09:00
2026-03-17 17:37:40 +09:00
2025-12-09 12:13:30 +09:00
2025-09-26 13:52:32 +09:00
2026-05-13 14:04:50 +09:00
2026-03-18 14:42:47 +09:00
2025-11-03 14:31:21 +09:00
2026-02-25 11:45:28 +09:00
2026-03-16 10:45:00 +09:00
2026-04-24 15:00:42 +09:00
2026-02-27 14:25:53 +09:00
2026-04-09 15:12:36 +09:00
2026-04-09 15:12:36 +09:00
2025-09-03 18:23:23 +09:00
2026-03-12 18:47:42 +09:00
2025-12-11 11:17:52 +09:00
2026-03-11 12:42:25 +09:00
2025-09-02 09:37:51 +09:00
2025-09-26 13:11:34 +09:00
2026-03-04 20:51:00 +09:00
2026-03-04 20:51:00 +09:00
2026-03-04 20:51:00 +09:00