Files
wace_rps/frontend/lib/api
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
..
2026-03-04 20:51:00 +09:00
2025-12-10 15:59:04 +09:00
2025-12-10 15:59:04 +09:00
2025-12-10 15:59:04 +09:00
2025-09-24 10:04:25 +09:00
2025-12-23 09:31:18 +09:00
2025-10-02 17:14:08 +09:00
2025-09-26 17:11:18 +09:00
2025-10-02 17:28:52 +09:00
2025-10-20 17:50:27 +09:00
2025-09-29 13:29:03 +09:00
2025-09-10 18:36:28 +09:00
2025-11-28 11:34:48 +09:00
2026-03-12 09:00:52 +09:00
2026-01-14 10:20:27 +09:00
2026-03-04 21:09:55 +09:00
2025-10-27 11:11:08 +09:00
2025-12-17 12:01:16 +09:00
2025-12-08 16:18:44 +09:00
2025-10-20 09:53:31 +09:00