Print Out Donate, Loss, Sales

Business / Process Summary

The discussion covers configuring and completing multiple asset disposal / transfer document printouts in a system (likely an ERP workflow). The presenters focus on:

• Field requirements and which fields appear by disposal type
• Numbering/format rules and how document generation logic works
• How disposal documents connect to downstream operational steps such as delivery orders and approval/validation stages

---

Operational Workflow and Data Dependencies

The workflow described is essentially:

1. User selects disposal type: donate / sell / loss
2. System dynamically shows different required fields based on the selection
3. After fields are completed, the system:
   • Downloads the BAST (asset handover/acceptance document)
   • Uploads it into the disposal record
4. Workflow then proceeds through stages like:
   • submit → validate → approve → (panel/approval) → DO / delivery / finalization
   • The exact “DO / delivery” path depends on the order type

Noted Pain Point

A mismatch risk is highlighted:

• Some fields should be provided earlier (at the beginning of the form / selection)
• But the current process seems to require completing information after BAST download/upload
• This creates risk that the document output is generated with incomplete or misaligned data

---

Document Field Strategy (Dynamic Templates by Disposal Type)

Donation (donate)

Uses a default document structure, including:

• Default fields, such as:
  • date (today)
  • date/month/year
• Location-related details may be left blank initially

Requires user-entered identity details:

• First party details: name, position, address
• Second party details:
  • includes an application letter number
  • additional fields may be intended for manual completion later

Includes structured numbering/formatting, such as:

• serial / numbering system
• references including:
  • site code
  • Roman month
  • year
  • e-form numbers (some marked as “unknown” and needing follow-up)

---

Loss (loss / write-off without reward)

Has a similar baseline, but with loss-specific sections:

• Recipient / transfer-related sections are similar but differ in some numbering and fields
• Includes police/vehicle/security report fields, such as:
  • “security report number”
  • “number and date”
• Includes manager’s assessment fields
• Some elements are described as hardcoded (e.g., signatures layout)

---

Sell (asset sales)

Delivery is emphasized:

• The flow connects to delivery of goods and delivery order (DO)
• The system generates/attaches delivery order printouts into the sales/disposal process after approval stages

Sell item-level behavior includes:

• Asset code / item code (when applicable)
• Serial number may be absent for some cases (“explicitly not there”)
• Quantity and conditions are mapped from configurable unit/condition rules

---

Asset / Item Master Data Mapping (How Values Are Derived)

The presenters repeatedly describe mappings:

• Asset number / asset code
  • described as attached to an AMS module (confirmed with a person later)
• Quantity / amount
  • implies “amount = 1 unit” based on asset context
  • includes a question about whether procurement is inventory-based
• Asset value
  • if taken from inventory, then asset value = original value
• Acquisition year/date
  • derived from the acquisition date field

They also note:

• Some fields are “red” and require later confirmation (whether to include them)
• Some fields may be skipped (e.g., weight left empty)

---

Disposal Type → Required Field Selection Logic

UI logic is driven by disposal type:

• If user chooses lost
  • a company-area-specific option/field should appear and must be filled

Also noted:

• Asset vs inventory distinction:
  • warehouse inventory vs fixed assets
  • inventory triggers different selection types and may show different asset fields

---

Outbound vs Stock File / Inventory Movement Configuration

A configuration issue is discussed for delivery/sales:

• There are two possible modes:
  • outbound
  • stock file
• The presenters debate the expected behavior:
  • If it’s outbound other than “calls”, they expect outbound logic
• Testing/observations indicate:
  • when configured one way, output may return as “stock file” instead of “outbound”

They suggest the behavior may be:

• determined later via configuration, or
• hardcoded in code, depending on system design

---

Numbering, Formatting, and Hardcoding

Presenters emphasize that:

• Number format changes by disposal type and possibly by underlying disposal category
• Site codes and Roman month formatting are part of the template
• Some sections (e.g., signatures and print blocks) are hardcoded:
  • once data is filled, layout is automatic
• The number of printout/signature blocks differs by module:
  • they mention “four” print sections for disposal

---

Metrics / KPIs / Business Targets

No explicit KPIs or numeric business targets (revenue, CAC, LTV, churn, etc.) are mentioned.

The “metrics” discussed are operational/form-related, such as:

• serial numbering sequences
• ensuring field completeness before upload/approval steps

---

Actionable Recommendations (Implied)

• Confirm and standardize:
  • which fields are mandatory at form start for each disposal type (donate/sell/loss)
  • whether BAST download/upload timing should change so required fields exist before output generation
• Decide and implement:
  • whether uncertain “red” fields should be removed or kept in templates
  • whether optional fields like weight should be included or remain empty
• Validate integrations/configurations:
  • ensure correct selection between outbound vs stock file logic in the DO process so the system reads the expected data flow
• Assign data ownership:
  • use named internal experts (e.g., the person who “knows best” about asset codes linked to AMS)

---

Presenters / Sources Mentioned

• Mr. Faris (referred to repeatedly)
• Pak (name missing in subtitles)
• Mr. Eko (mentioned in outbound/stock file logic discussion)
• Banguncan (described as best source for asset code/asset numbering details)
• Bang Uri (asked about procurement/inventory acceptance process and asset unit rules)
• Mr. [name missing] (multiple references; names redacted by subtitle auto-generation)