shad0w/pelagia-portal
1
0
Fork 0
Code Issues 11 Pull requests 2 Projects Releases 2 Packages Wiki Activity Actions

docs(schema): note suggestedAdvancePayment is the reuse point for issue #91
All checks were successful
PR checks / checks (pull_request) Successful in 43s
Details
PR checks / integration (pull_request) Successful in 32s
Details

Browse source 
The structured payment-request lane (#91) should extend this column for the
ADVANCE/PART 'exact sum due', not add a parallel field.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Hardik 2026-06-24 01:45:56 +05:30
parent 99c928213b
commit 455d268925
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
App/prisma/schema.prisma
View file

@ -517,6 +517,11 @@ model PurchaseOrder {
// resolved amount is stored here. Null on legacy/pre-feature POs ⇒ no explicit // resolved amount is stored here. Null on legacy/pre-feature POs ⇒ no explicit
// advance, so Accounts defaults to the full remaining balance. Set once at // advance, so Accounts defaults to the full remaining balance. Set once at
// approval and not edited afterwards (issue #92). // approval and not edited afterwards (issue #92).
//
// NOTE (issue #91): this IS the "exact sum due for payment" for an ADVANCE/PART
// request. When the structured payment-request lane (payment-term enum +
// separate approval) is built, reuse this column for the requested amount
// rather than adding a parallel "exact sum" field.
suggestedAdvancePayment Decimal? @db.Decimal(12, 2) suggestedAdvancePayment Decimal? @db.Decimal(12, 2)
piQuotationNo String? piQuotationNo String?
piQuotationDate DateTime? piQuotationDate DateTime?