Skip to main content

SoD — Objects

The Objects screen attaches source-system programs to SoD activities. One line per (Application, Process, Activity, Row, Object). Each row says: running this object counts as performing this activity. An activity typically maps to several objects — interactive forms, batch programs, the same program with different versions.

This is the bridge between the abstract SoD model and the concrete programs the source system runs.

At a glance​

Nomasx-1 · Settings · SoD · ObjectsAPPPROCESSACTIVITYROWOBJECT IDDESCRIPTION12P2PVEND-CR1P0401Vendor Master Maintenance12P2PVEND-CR2P01012Address Book Vendor12P2PPAY-APV1P0413MManual Payment

Goal of the view​

  • Tell Nomasx-1 what counts as "doing" an activity. Each row pins an SoD activity to a concrete source-system object.
  • Multiple rows per activity is normal. Row numbers them — the engine considers any of them as evidence the activity was performed.
  • Source for Conflicts → Proven. Without an object mapping the activity has no observable footprint, so the proven analysis cannot work.

Columns​

ColumnSourceWhat it tells you
Application IDOBJECT_APPS_ID — application.The application.
Process IDOBJECT_PROCESS_ID — process.The SoD process.
Activity IDOBJECT_ACT_ID — activity.The activity the object backs.
Row IDOBJECT_ROW_ID — sequence.Stable identifier among the objects of the same activity.
Object IDOBJECT_ID — technical object.Program code (e.g. JDE P0401).
Object NameOBJECT_NAME — friendly label.Human-readable name of the program.

Edit dialog​

Click Add or double-click a row to open the form.

Edit SoD objectApplication12 — JDE Prod ▾ProcessP2P ▾ActivityVEND-CR ▾Row1Object IDP0401NameVendor MasterCancelSave
FieldWhat to enter
ApplicationDrop-down of declared applications.
ProcessDrop-down filtered to the chosen application's processes.
ActivityDrop-down filtered to the activities of the chosen process.
RowSequence number within the activity's object list. Auto-incremented; edit to reorder.
Object IDSource-system program code (e.g. JDE P0401).
NameFriendly name of the program.

Tips & best practices​

  • Map every program that touches the activity — the Proven view depends on a complete mapping. Missing rows produce false negatives on the conflict analysis.
  • Re-check the mapping after a source-system patch — new versions of a program (or a new alternative entry point) need to be added here.
  • Per-activity mappings should not overlap. The same object on two different activities makes the model ambiguous.