Skip to main content

SoD — Process

The Process screen is the catalog of business processes used by every other SoD setting. One line per (Application, Process). Each row carries a numeric identifier and a friendly name — for example P2P (Procure to Pay), O2C (Order to Cash), R2R (Record to Report).

It is the top of the SoD hierarchy: Activities attach to a process, Risks are defined inside a process, the Matrix groups risk-bearing activity pairs by process.

At a glance​

Nomasx-1 · Settings · SoD · ProcessAPPPROCESS IDPROCESS NAME12 — JDE ProductionP2PProcure to Pay12 — JDE ProductionO2COrder to Cash

Goal of the view​

  • Declare the processes that will host the SoD activities and risks.
  • Use stable identifiers — Process ID is referenced by the Activities, Risks, Matrix and Objects tables. Renumbering breaks references.
  • One process per major business area — keep the catalog short so it stays readable. Most companies live with five to eight.

Columns​

ColumnSourceWhat it tells you
Application IDPROCESS_APPS_ID — application.Application the catalog applies to.
Process IDPROCESS_ID — short identifier.Reference used by every dependent SoD setting.
Process NamePROCESS_NAME — friendly label.Human-readable name.

Audit columns (PROCESS_AUDIT_USER, PROCESS_AUDIT_DATE) are kept on the row.

Edit dialog​

Click Add to declare a new process, or double-click a row to edit. The dialog is a single form.

Edit SoD processApplication12 — JDE Production ▾Process IDP2PNameProcure to PayCancelSave
FieldWhat to enter
ApplicationDrop-down of declared applications. The process belongs to this application.
Process IDShort identifier (e.g. P2P, O2C, R2R). Referenced by Activities, Risks, Matrix and Objects.
NameFriendly label for the process. Surfaces on every SoD report.

Tips & best practices​

  • Per-application catalog. If two applications carry the same SoD perimeter, declare the process in each — Nomasx-1 does not share rows across applications.
  • Match the auditor's vocabulary. Use the labels (P2P, O2C, R2R, HR, IT) the audit team already uses in their walkthroughs.
  • Keep the list stable across audit cycles — comparing the SoD figures quarter over quarter only works if the process IDs don't change.