Sharing our success story implementing automated BOM release approval workflow using BOPF and Fiori in SAP PLM 2021. Previously, our engineering teams spent 5-8 days per BOM release managing manual approval routing and status tracking. We automated the entire workflow with BOPF workflow configuration for business logic and Fiori notification integration for real-time approver alerts. The result was a 60% reduction in cycle time - releases that took a week now complete in 2 days. Key to success was comprehensive audit logging that captures every approval action, comment, and status change for compliance. Implementation took 3 months but ROI was immediate. Engineers now focus on design work instead of chasing approvals. Happy to share technical details if others are implementing similar automation.
Let me provide comprehensive details on our automated BOM release implementation:
BOPF Workflow Configuration: We leveraged SAP’s Business Object Processing Framework (BOPF) to build the approval workflow engine. The key decision was to create a custom business object that wraps standard BOM objects rather than modifying BOM structure directly. This approach preserved existing BOM functionality while adding workflow orchestration.
The BOPF business object defines approval stages: Engineering Review → Design Verification → Manufacturing Feasibility → Final Release. Each stage has associated actions (approve, reject, request changes) and determinations (automatic routing logic based on BOM characteristics like part count or cost). We configured validations at each stage to ensure BOMs meet quality criteria before advancing.
Biggest technical challenge was handling BOM effectivity dates during workflow. A BOM in approval might have future effectivity that conflicts with production schedules. We built BOPF determinations that check effectivity against production plans and automatically flag conflicts for expedited review. This required custom ABAP logic within BOPF action implementations.
For exception handling, we implemented three escalation mechanisms:
- Time-based escalation: If approver doesn’t respond within 24 hours, workflow escalates to their manager
- Urgency override: Submitter can flag BOM as urgent, triggering parallel approval instead of sequential
- Manual intervention: Workflow administrators can force-advance BOMs in emergency situations, with full audit logging of the override
These exceptions maintain workflow flexibility while preserving audit compliance. Every exception triggers detailed logging explaining why normal process was bypassed.
Fiori Notification Integration: We use standard Fiori notification services - no custom mobile app development required. When BOPF workflow advances to a new stage, it calls notification API /IWNGW/IF_NOTIF_PROVIDER to create notifications for assigned approvers. Notifications appear in Fiori Launchpad notification center and push to mobile devices via SAP Fiori Mobile app.
Notifications include deep links that open the BOM directly in our custom Fiori approval app. Approvers can review BOM details, view attached documents, add comments, and approve/reject - all from mobile device. The approval app is built with SAPUI5 and consumes BOPF business object via OData service.
Critical implementation detail: We configured notification templates for each approval stage with different priority levels. Engineering Review notifications are low priority (informational), but Final Release notifications are high priority (requires immediate action). This prioritization helps approvers focus on time-sensitive decisions.
Audit Logging: Our audit logging captures comprehensive activity tracking for FDA compliance requirements:
- Every workflow state transition (who, when, from-state, to-state)
- All approval decisions with approver comments and justifications
- BOM attribute changes during workflow (tracked via BOPF change documents)
- Document views and downloads (integrated with document management audit trail)
- System-generated determinations and routing decisions
- Exception escalations and manual overrides with detailed reasoning
Logs write to custom database table with tamper-proof timestamps and digital signatures. We retain logs for 10 years per regulatory requirements. Audit reports can reconstruct complete approval history for any BOM, showing decision timeline and approver actions.
For FDA validation, we documented the BOPF workflow logic, tested all approval paths including exceptions, and validated audit log completeness. The validation documentation package includes workflow specifications, test protocols, and audit trail verification results.
Performance Measurement: We established baseline metrics by analyzing 6 months of manual approval data before automation: average cycle time was 5.8 days, with high variability (standard deviation 2.3 days). Post-automation metrics show average cycle time of 2.1 days with much lower variability (standard deviation 0.7 days). The consistency improvement is as valuable as the speed improvement.
We monitor ongoing performance through custom SAP Analytics Cloud dashboard that tracks:
- Average cycle time by BOM complexity (part count, document count)
- Approval stage bottlenecks (which stage takes longest)
- Exception frequency (how often escalations occur)
- Approver response times (identifies training needs)
The dashboard updates daily from BOPF workflow logs. When cycle time trends upward, we investigate root causes - usually training issues or changing business requirements that need workflow adjustment.
ROI and Business Impact: Implementation required 3 months with 2 ABAP developers, 1 Fiori developer, and 1 business analyst. Total investment approximately 2000 hours. Annual savings from cycle time reduction: engineers reclaim 800 hours previously spent on approval coordination, plus faster time-to-market for new products improves revenue by an estimated $2M annually.
Key success factors:
- Executive sponsorship - VP Engineering championed the project
- User involvement - engineers participated in workflow design
- Phased rollout - piloted with one product line before enterprise deployment
- Comprehensive training - 4-hour workshop for all engineers and approvers
- Continuous improvement - monthly review of metrics and workflow refinements
The automated workflow transformed our engineering culture. Teams now trust the system to route approvals correctly and provide real-time status visibility. The audit logging gives confidence to quality and compliance teams. Overall, this was one of our highest-ROI PLM automation projects.
Great questions. The BOPF integration was straightforward because we built the workflow on top of standard BOM objects, not custom structures. We didn’t modify existing BOM logic, just added workflow orchestration. For exceptions, we implemented escalation rules - if an approver doesn’t respond within 24 hours, the workflow automatically escalates to their manager with notification.
Can you elaborate on the Fiori notification integration? Are you using standard Fiori notification APIs or custom development? We’re planning similar automation and want to ensure notifications work across mobile and desktop without custom mobile app development.
The audit logging aspect is critical for us. What level of detail do you capture in audit logs? Do you log just approval decisions or also include pre-decision activities like BOM views and document downloads? For FDA validation, we need comprehensive activity tracking.
60% cycle time reduction is outstanding. How did you measure baseline performance before automation? And how are you tracking ongoing performance to ensure the improvement sustains? Curious about your metrics and monitoring approach.
Impressive results. How did you handle exception scenarios - like when an approver is unavailable or a BOM needs urgent release? Automated workflows can be rigid when business needs flexibility. Did you build in escalation paths or manual override capabilities?
This sounds exactly like what we need. What was the biggest technical challenge during implementation? We’re concerned about integrating BOPF with our existing BOM structures without breaking current processes.