MDP Group
TR / DE
Blog

How to Parameterize Decision Rules in SAP TM with BRF+

SAP Transportation Management (TM) handles complex logistics scenarios where countless decisions need to be made: 
  • Which sales orders should be consolidated into a Freight Unit (FU)? 
  • Which carrier should be chosen? 
  • What type of tendering process should apply? 
  • Which surcharges or discounts should be added? 
  • When should deliveries be split? 
Managing all these decisions purely through ABAP developments is possible, but it is not sustainable. Every small change would require IT involvement, slowing down the business. This is where BRF+ (Business Rule Framework Plus) becomes essential. BRF+ allows business rules to be modeled parametrically. It gives flexibility, reduces dependency on IT, and brings agility to transportation processes. 

Why BRF+ Matters

From a consulting perspective, BRF+ brings several advantages: 
  • Flexibility: Rules can be changed without new developments. 
  • Business empowerment: Analysts and process owners can update rules directly. 
  • Centralized logic: All business rules are managed in one framework instead of scattered BAdI implementations. 
  • Performance: The BRF+ engine is optimized for high-volume data. 
  • Testing: Rules can be simulated before being activated in production. 

Usage Areas of BRF+ in SAP TM

BRF+ is embedded in almost every major decision-making area of TM. Let’s walk through the main use cases with examples.  

  1. Freight Unit Building (FUBR)

FU creation is one of the most fundamental TM processes. BRF+ rules determine how orders are consolidated or split. 
  • Consolidation rules: 
  • Same customer + same destination + same delivery date → one FU. 
  • Same product group → one FU. 
  • Split rules: 
  • Volume > 20 m³ → split FU. 
  • Weight > 10 tons → split into two. 
  • Pallet count > 33 → create additional FU. 
  • Product-based rules: 
  • Glass → max 500 kg per FU. 
  • Chemicals → max 1 ton. 
  • Electronics → max 100 items per FU. 
Example: “If Product Type = Glass and Quantity > 500 kg → create a new FU.”  

  1. Carrier Selection

Carrier selection is often the most critical decision in transportation. With BRF+, it becomes multi-dimensional: 
  • Cost + KPI combination: Choose based on both freight cost and on-time delivery rate. 
  • Business share: Ensure Carrier X does not receive more than 30% of the total volume. 
  • Seasonal/Climate rules: In winter months, only carriers with snow-chain certified trucks. 
  • Customer-specific rules: Some customers require only contracted carriers. 
Example: “If Destination = Norway and Month = December–March → only winter-certified carriers are eligible.”  

  1. Tendering

Tendering logic is fully configurable with BRF+: 
  • Tender type: 
  • Express shipments → Direct Tender (auto award). 
  • Standard shipments → Peer-to-peer. 
  • Low-value shipments → Broadcast. 
  • Response times: 
  • Express → 30 minutes. 
  • Standard → 2 hours. 
  • International → 6 hours. 
  • Fallback logic: 
  • If the first carrier rejects → go to the second. 
  • If no response → trigger broadcast tender. 
  • Region-specific behavior: 
  • Europe → Peer-to-peer. 
  • Domestic (Turkey) → Direct Tender. 
Example: “If Loading Location = Port and Service Level = Express → Direct Tender with 30 min response time.”  

  1. Charge Management

Charge and cost calculation is another area heavily supported by BRF+: 
  • Surcharges: 
  • Weekend delivery → +10%. 
  • ADR (dangerous goods) → +200 €. 
  • Airport handling fee → +50 €. 
  • Discounts: 
  • Carrier X → 5% discount. 
  • Customer Y → 10% discount for specific routes. 
  • Mode-based logic: 
  • Road → per km. 
  • Air → per kg. 
  • Ocean → per container. 
  • Time-based rules: 
  • Night delivery → +15%. 
  • Public holiday → +20%. 
Example: “If Mode = Ocean and Cargo = Reefer → apply €100 surcharge per container.”  

  1. Compliance and Constraints

BRF+ also supports compliance and regulatory checks: 
  • Dangerous goods (ADR/DG): Certain classes can only be handled by DG-certified carriers. 
  • Country-specific rules: 
  • Germany → extra customs documents required. 
  • USA → export license mandatory. 
  • Customer-specific constraints: 
  • Customer A → only contracted carriers allowed. 
  • Customer B → ADR transport not permitted. 
Example: “If Destination Country = DE and ADR Class = 3 → block carriers without DG certificate.”  

  1. Integration Scenarios

BRF+ is not limited to TM itself but also controls ERP and EWM integration: 
  • Delivery split rules: Decide when ERP deliveries are split in TM. 
  • Event management: Trigger alerts if expected events don’t occur. 
  • Pre-settlement checks: If price deviation > 5%, require approval. 
  • EDI/IDoc filtering: Decide which messages should be sent. 
Example: “If Settlement Amount > €10,000 → trigger additional workflow approval.”  

  1. Planning Scenarios

Planning is another area where BRF+ brings flexibility: 
  • Optimizer parameters: Prioritize cost vs. service time dynamically. 
  • Constraint handling: Consider vehicle capacity, driver hours, or legal restrictions. 
  • Prioritization: VIP customer orders always planned first. 
  • Load planning: Certain product types only allowed in specific vehicle types. 
Example: “If Customer = VIP → prioritize order in the earliest planning slot.” 

Case Study: Automotive Industry Carrier Selection 

A European automotive manufacturer was using SAP TM for spare parts distribution. Initially, carriers were selected purely based on cost. However, delays increased and customer complaints followed. 
  • Problem: Changing KPI weightings required ABAP development each time. 
  • Solution: A BRF+ decision table was created: 
  • Premium service → KPI 70%, Cost 30% 
  • Standard service → Cost 80%, KPI 20% 
  • Result: Business users could adjust weights themselves. Within 3 months, customer satisfaction improved by 15%. 
This case shows how BRF+ can directly influence business outcomes, not just IT efficiency. 

Technical Framework

  • Decision Tables: Most common; IF/ELSE rules modeled in tables. 
  • Expressions: Formula, case, lookup for more complex rules. 
  • Data Access Definition (DAD): Data provider layer for BRF+ (e.g., FU volume, carrier KPI). 
  • Simulation: Run rules before activation. 
  • Integration: Rules can be called from BOPF determinations or BAdI implementations. 

Consulting Best Practices

  1. Start simple: Begin with decision tables before adding complex formulas. 
  2. Central documentation: Prevent “rule spaghetti” by managing rules in one place. 
  3. Involve business users: Teach analysts to maintain decision tables. 
  4. Always test: Use simulation before moving rules to production. 
  5. Monitor performance: Overly complex tables can slow down processing. 
Conclusion BRF+ is the decision engine of SAP TM. It plays a role in FU creation, carrier selection, tendering, charge management, compliance, integration, and planning. When implemented correctly: 
  • Business agility improves, 
  • IT workload decreases, 
  • Regulatory compliance and customer satisfaction both increase. 
For SAP TM consultants, BRF+ should not be seen merely as a configuration tool but as a strategic flexibility layerthat ensures long-term sustainability of transportation processes. 

Similar
Blog

What is SAP Leonardo?

Everything You Need to Know About SAP's Leonardo PlatformSAP Leonardo is an innovation platform offered by SAP that can work with blockchain, IoT,...

What is SAP Application Interface Framework (AIF)?

SAP Application Interface Framework (AIF) is an SAP add-on that facilitates integrations of business users and enables their monitoring. It enables...

The Role of Cloud Connector in CPI

What is Cloud Connector?Cloud Connector is an application that creates a secure connection with SAP ‘cloud’ in order to ensure that systems in...

The Role of Warehousing in Supply Chain Management

The aim of supply chain management is to continue the flow of goods and services from the point of origin to the point of consumption in an...

ABAP Clean Code: The Key to Better Software Development

Clean code refers to software that is readable, understandable, maintainable, and testable. Embracing clean code principles in ABAP ensures that...

Understanding IDoc in SAP: Overview, Structure, and Types

SAP’s robust enterprise resource planning (ERP) solutions streamline business operations across various industries. At the heart of SAP’s data...

Embedded SAP EWM Client BASIS Implementation

SAP EWM Client Basis Implementation The first step is client basis implementation for the SAP EWM. Therefore, I am explaining shortly step by step...

What is the e-Accounting Slip?

In the pandemic period we live in due to the coronavirus, we have seen again that most of the accounting transactions can be carried out from home,...

What are the 5 Basic Principles of Continuous Improvement?

Continuous improvement is an effective methodology that focuses on the continuous improvement of processes, products or services through small and...

Your mail has been sent successfully. You will be contacted as soon as possible.

Your message could not be delivered! Please try again later.