Oracle Retail Knowledge Base

Start Here

4 min read

Context

Welcome to the Oracle Retail knowledge base: a vault of implementation runbooks and troubleshooting notes for the stack: MFCS, RDT, AIF DATA, AIF APPS, Insights, LPO, IPO, MFP and AP.

This note explains how the vault works. Read it once before writing anything.

New here?

Open this vault as a folder in Obsidian (Open folder as vault). All the settings, templates and folder structure ship with the repo, so your setup matches everyone else’s. First time? Follow How to set up Obsidian to get configured.

1 - Information flow

Every note travels through the numbered folders in one direction. The number is the order, counting down.

02-Sketch  →  01-ToBeReviewed  →  00-Knowledge
 (writing)      (peer review)       (trusted)
FolderWhat lives hereWho moves it out
02-SketchNotes under development. Incomplete, unverified, changing. Obsidian creates every new note here automatically.The author, once the note is complete
01-ToBeReviewedNotes the author considers finished, waiting for a second pair of eyes.The reviewer, never the author
00-KnowledgeReviewed, authoritative notes. Treat these as correct.Nobody. This is the final state
99-imagesEvery image attached to any note, at any stage. Obsidian saves pastes here automatically.n/a

The rules

  1. Start in 02-Sketch. Never create a note directly in 00-Knowledge.
  2. Use the template. Every note starts from Templates/Template_note.md (see How to format in Obsidian for how to insert it).
  3. When the note is ready, move it to 01-ToBeReviewed. Drag it in the file explorer. Obsidian repairs any links automatically.
  4. A different, authorized person reviews it. You do not review your own note. The reviewer fills in Reviewed by and Reviewed on in the frontmatter.
  5. The reviewer moves it to 00-Knowledge. If it is not ready, the reviewer moves it back to 02-Sketch and says why.
  6. Images always go to 99-images, whatever stage the note is in. Just paste into the note. Obsidian files them for you.
  7. Editing a note that is already in 00-Knowledge? If the change is small (a typo, a new SQL line), edit in place. If you are reworking it, move it back to 01-ToBeReviewed so it gets reviewed again.

What a good note looks like

  • Frontmatter filled in: Created by, Created on, Client, and the tags for the products it touches.
  • Opens with ## Context: one short paragraph on why someone would run this procedure.
  • If the note has more than one subtopic, add a > [!tip] Quick access box right after the Context, with one [[#section|Section]] link per heading so readers can jump. See How to format in Obsidian for the pattern.
  • Then the procedure, in numbered steps.
  • UI navigation written as a breadcrumb: POM > TOP LEFT MENU > Tasks > Batch Monitoring
  • End with a footer, separated from the body by a --- rule: a ### Related section (one link per line) and, if the note cites external docs, a ### Reference section after it. Do not put a “Related:” line in the middle of the note. A link that reads as part of a sentence, such as “switch back with Batch setup - Incremental mode”, stays where it is.

Reference example: Batch setup - Full mode.

The SQL in these notes is documentation, not a script

Runbooks here contain update statements against Oracle config tables. Read them, adapt them, run them deliberately against the right environment. Never copy-paste a whole note into a session.

Obsidian syntax

New to Obsidian, or need a formatting refresher? How to format in Obsidian has the shortcuts, text formatting, links, and callout syntax. This page keeps only the vault’s own conventions below.

2 - Conventions

Tags

The tag vocabulary is fixed. Use only these, and only the ones that actually apply:

  • Products: #MFCS #RDT #AIF_DATA #AIF_APPS #INSIGHTS #LPO #IPO #MFP #AP
  • Interaction: #POM — add to any procedure carried out through POM (Process Orchestration Manager), on top of the product tags.

Tags live in the frontmatter tags: list (no # there). You can also drop #TAG inline in the body when you mention a product in passing.

Do not invent new tags. The value of the vocabulary is that #AIF_DATA finds everything about AIF DATA. Open the Tags pane on the right sidebar to browse.

Frontmatter

Every note carries this block, and Obsidian shows it as editable properties at the top:

---
Created by: Felipe Silva
Created on: 2026-07-20
Client: P&C
Reviewed by:
Reviewed on:
tags:
  - AIF_DATA
---

Dates are always YYYY-MM-DD. Reviewed by / Reviewed on stay empty until someone actually reviews the note.

Client records which implementation a note describes. Use the short form, such as P&C. Leave it empty for notes that describe a product behaviour rather than one client’s configuration. Anything with a client filled in should be assumed to contain values specific to that engagement, so never copy them into another environment without checking each one.

Graph View

Backlinks