Codes, UDFs & Notes
Notebooks (MEMOTYPE / TASKMEMO / WBSMEMO) — Not Schedule Logic
Notebooks are text on a topic; not steps, UDFs, or schedule logic
What a planner means
A notebook is text on a topic (scope, change, safety, “why this lag”). It does not date the activity, hold a relationship, or change float.
XER tables (Oracle)
MEMOTYPE — the topic dictionary:
| Column | Oracle label |
|---|---|
memo_type_id | Unique ID |
memo_type | Notebook Topic |
seq_num | Sort Order |
eps_flag | Available for EPS |
proj_flag | Available for Projects |
wbs_flag | Available for WBS |
task_flag | Available for Activity |
TASKMEMO — activity notebook body: memo_id, memo_type_id, task_id, proj_id, task_memo (Notebook Description).
WBSMEMO — EPS / project / WBS notebook: wbs_memo_id, memo_type_id, wbs_id, proj_id, wbs_memo.
One activity can have several TASKMEMO rows (one per topic). The topic flags say where that topic is allowed, not that a row exists.
What it is not
- Not an activity step (
TASKPROC). - Not a UDF (
UDFVALUE). - Not the activity name or notebook-as-WBS.
- Not a constraint or Expected Finish.
Microsoft Project
Project has a single Notes field on the task (and resource/assignment notes). No topic dictionary, no EPS/WBS/activity flags.
Do not explode TASKMEMO into subtasks or WBS bands, or concatenate every topic into Activity Name. A Viewer can show notebooks as text. A converter may map one topic into MSP Notes; that is a product choice, not an identity. Do not invent an MSPDI NotebookTopic table.