TAOM → Jira and Confluence – layout template

Published on agosto 19, 2026 · by TAOMAI
Jira-Vorgangsansicht „Etiketten erstellen" mit Typ, Priorität und Beschreibung aus einem TAOM-Prozessschritt.

TAOM → Jira & Confluence · layout template

This is how a Jira issue and the automatically generated Confluence blueprint page can look, built from the TAOM structure. Every field is fed from TAOM attributes (object/TAOM ID as the stable key, process = epic, phase = story, step = task/sub-task). Demo content – this is about the layout.

Jira · issue view

Create labels

PROD-2345  In progress
Description

Demo description: in this step, labels for equipment, materials, shelf compartments and mobile storage bins are created, checked and attached.

  • Check master data and apply the label layout (WRICEF object)
  • Print the label, verify scannability and record it
  • Confirm the assignment to the object

Source: TAOM Process Studio · taken automatically from the process documentation.

Child issues
Functional specification (FS) Done PROD-2345-1
Design the label layout Done PROD-2345-3
Create test cases In progress PROD-2345-5
Open in Jira Update from TAOM
Details
Type Sub-task
Priority High
StatusIn progress
ResolutionUnresolved
TAOM-IDT01-P2M-L44LO-ETI
Epic-Link Production planning
ComponentSAP PP · EWM · TAOM Editor
LabelsWRICEFLabel
Fix-VersionR2026.1
SprintP2M Sprint 7
AssigneeAB Anna Example
ReporterTA TAOM Agent
Created from TAOM · last synchronised: today
Confluence · blueprint page (generated from TAOM)
P2M – Plan to Manufacture
  • 1 · Process overview
  • 2 · Production planning (L4)
  • 2.1 Run MRP
  • 2.2 Plan the production order
  • 2.3 Capacity levelling
  • 3 · WRICEF
  • 4 · Risks & measures
  • 5 · Test management
  • 6 · Change history

Production planning Approved

Level L4 · process (epic PROD-123) · generated from TAOM Process Studio
W Create Word file Open in Jira Edit
OwnerAB Anna Example
Due15.05.2026
Progress100 %
Last change24.05.2026 · M. Example
Version1.0
ℹ️
Generated automatically from TAOM Process Studio. Structure: process (epic) → phases (stories) → steps (tasks/sub-tasks). Object/TAOM IDs link every section to its Jira issue; the requirements (user stories/BLRs) are synchronised with Jira in both directions at runtime.
1 Process overview (L4)

This scope item covers production planning – from requirements planning (MRP) through production order planning to capacity levelling. It makes planning-relevant objects, materials and resources unambiguously documented, traceable and linked to the executing SAP systems.

Elaboration

The process plans secondary demand on time and in the right quantity and turns it into executable production orders. It covers checking material availability, levelling available capacity and releasing the orders to production. Read more …

Position in the process (BPMN)

MRP Createlabels 🔗 Show in BPMN
2 Process model (TAOM Process Studio / BPMN)

Linked model in gBPML, maintained in the TAOM Editor / TAOM Process Studio. open · from gBPML (column AE) — the model link is added automatically at the next sync.

3 Dependencies (required scope items)
Scope itemTitleRelationStatus
J45Material requirements planningrequiredActive
BJ8Production order processingdownstreamActive
3JPWarehouse management (EWM)requiredBeing introduced
4 Assumptions & KDDs
Assumption / KDDCommentLink
One label template group-wideGlobal template decision DEC-010DEC-010
MRP runs nightly in batchopen · from gBPML
5 Security & permissions

open · from gBPML role → SAP transaction per scope item is not fully mapped yet.

RoleRole descriptionTasks / transactionsAccess type
a production plannerPlans demand and production ordersMD01 · CO40 · MD04Create/change
a warehouse operativeLabelling & bin maintenance/SCWM/LS01 · MB1AExecute
6 Organisational structure & master data

6.1 Master data

  • Material · routing · bill of material
  • Work centre / resource
  • Storage bin & label layout
  • open · BP available (H)

6.2 Organisational structure

  • Plant · storage location · production version
  • MRP controller group
  • EWM warehouse number
7 Country rollout / legal entities

Scope availability per country (source: BP available):

DE ✓CZ ✓CN ✓IN ✓PL ✓CH ✓US ✓CZ Prot. ✓BR –FR ✓GB ✓HK ✓IT ✓NL ✓RU –SE ✓TR ✓
8 Value case
Value categoryValue leverMeasureTarget
EfficiencyFewer mislabelled objectsLabel error rate< 0,5 %
Lead timeFaster order releaseAvg. time MRP → releaseopen · from gBPML
9 Phases & steps (stories / tasks)
TAOM-IDStepTypeStatusJira
T01-P2M-L44LO-ETICreate labelsSub-taskIn progressPROD-2345
T01-P2M-L44LO-PLACreate planned orderTaskOpenPROD-2346
T01-P2M-L44LO-MRPRun MRPTaskDonePROD-2340
10 Requirements overview (user stories) · synchronised with Jira in both directions
Labels filled automatically from master data PROD-2401 In progress

As a warehouse operative I want labels to be filled automatically from the material master data so that I do not have to enter data twice.

Acceptance: scannability ≥ 99 %Func. Spec: FS_Etiketten_v1.0Tech. Spec: TS_Etiketten_v1.0Gap: noRelease: global template
Approvals: ☑ GPO · ☑ Global ERP Lead · ☐ RPE EMEA · ☐ SME
Reprint with a reason PROD-2402 Open

As a production planner I want to reprint labels with a documented reason so that changes stay auditable.

Gap: yes (enhancement)Func. spec: open · from gBPMLRelease: R2026.2
Approvals: ☐ GPO · ☐ Global ERP Lead · ☐ RPE Americas · ☐ RPE APAC
11 BLRs (business level requirements)
Approval process for safety-relevant labels PROD-3006 Open

As a quality manager I want a multi-stage approval process for safety-relevant labels so that regulatory requirements (ISO 9001) are met.

Gap type: workflowRelease: global template
Approvals: ☑ GPO · ☐ Global ERP Lead · ☐ SME
12 WRICEF objects
TypeTitleDescriptionStatusJira
F – FormLabel templateLabel layout & print maskDonePROD-3001
R – ReportLabel logRecord of printing & checkingIn progressPROD-3002
I – InterfaceLabel printing serviceInterface to the printing systemIn progressPROD-3003
E – EnhancementReprint with a reasonExtension for the reprint processOpenPROD-3005
13 SAP references (downloads)
DOC Test script / BPD (DE/EN) 4LO_S4HANA2020_BPD_DE/EN_XX.docx
HTM Process preview (BPMN view) Process_Overview_DE/EN_XX.htm
HTM FactSheet 4LO_S4HANA2020_DE/EN_XX.htm
PDF Set-up guide 4LO_S4HANA2020_Set-Up_EN_XX.pdf
ZIP Process diagram archive (BPMN source) Process_Overview_DE/EN_XX.zip
TAOM™ · Traniva AG · Object ID: T01-P2MPR-L2MRP-L44LO · OS-15 · MGT-09 · TOOL-12
Updated: 2026-08-01 · AUD-1784486253473 · Refs: OS-15, TOOL-12

Page details

Process IDP2M.04.01
LevelL4 · process
Epic (Jira)PROD-123
Phase (story)2.1 Run MRP
Object IDT01-P2MPR-L2MRP-L44LO
SystemsSAP ERPEWMLabel printer
ClassificationStandard
ComplianceISO 9001ISO 27001
AI generatedYes
ToolTAOM · TOOL-12

Documents & attachments

PDF
FS – functional specification
FS_Etiketten_v1.0.pdf · 24.05.2026
DOC
TS – technical specification
TS_Etiketten_v1.0.docx · 24.05.2026
PNG
Label layout (example)
Label_Design_Beispiele.png
XLS
Test cases
TC_Etiketten_v1.0.xlsx
Show all attachments

Quality & test

Test coverage
76 % (19 / 25 test cases)
DEFECTS 2 critical · 1 normal open

Risks

RISK-001 Wrong label on the objectHigh
RISK-002 Readability not guaranteedHigh
RISK-003 Printer unavailableMedium

Decisions

DEC-010 Standard label material20.04.26
DEC-011 QR code as the standard22.04.26

Change history

24.05.26M. Example · approvedv1.0
20.05.26A. Example · review completedv0.9
15.05.26L. Lerner · in progressv0.8
Show the full history
Open = To Do In progress = In Progress Done/approved = Done open · from gBPML = filled automatically at the next sync Icons: original Atlassian issue-type icons
TAOM → Jira & Confluence · layout template (demo content) · The “Create Word file” button produces the complete process document as .docx from the same TAOM data · Jira and Confluence are Atlassian products, SAP is a trademark of SAP SE · © 2026 TRANIVA AG

Insights

Leave a Reply

Your email address will not be published. Required fields are marked *