Lesson 4 of 5
BJ5 as the reference process
9 min
Listen to this lesson
SAP Best Practices describes standard business processes as scope items, each with a process flow diagram, a test script and the configuration needed to run it. For plan-to-produce in discrete manufacturing, the reference is BJ5, Make-to-Stock Production for Discrete Manufacturing. Using it as the baseline gives Contoso a shared vocabulary with SAP, with partners and with its own key users.
Finding and reading BJ5
Scope items live in SAP Signavio Process Navigator (part of SAP for Me). Search for BJ5, pick your product (SAP S/4HANA Cloud Private Edition or on-premise) and release, and open the process flow. The documents vary by release, so always pick the version that matches the system you are testing, and read the test script alongside the flow.
Process flows are drawn in swim lanes, one per role. A step in one lane hands over to the next. Optional steps are marked, and boxes at the edges name the scope items that feed in or follow. Read the lanes first, then the hand-offs, then the edges.
What BJ5 contains
In the published flows, BJ5 plans a finished product and a subassembly. The planner creates PIRs, runs MRP, checks the stock/requirements situation and converts planned orders into production orders for both levels. The supervisor releases the orders. Warehouse and operators stage materials, confirm operations and post goods receipts for the subassembly and then the final assembly. Some steps are optional, such as a capacity check or reviewing a scrap report.
Components the plant buys are not procured inside BJ5. That happens in J45, Procurement of Direct Materials, which the flow shows as an upstream scope item. The cost side at period end is also outside BJ5, in the period-end closing scope items for the plant, or in event-based production costing where that is in scope.
- PlanPIRs and MRPDemand for the finished product; MRP plans both levels and the purchased parts
- BuyJ45 in parallelPurchase requisitions for components become POs and goods receipts
- Make subassemblyOrder, release, confirm, receiveThe subassembly is produced and put into stock first
- Make final assemblyOrder, release, confirm, receiveFinal assembly consumes the subassembly and purchased parts
- ClosePeriod-end closingWIP, variances and settlement for the plant
Mapping Contoso to BJ5
| BJ5 element | Contoso equivalent |
|---|---|
| Finished product | CMC-ALT-100 alternator, plant 1710 |
| Purchased component (via J45) | CMC-RTR-200 rotor from Lakeside Components |
| Subassembly | Contoso has none in the current BOM; the stator is wound inside the alternator routing |
| Storage | Rotors received into 171S and moved to line-side 171L (movement 311); components staged from 171L at ASSY-10; finished goods received into 171B, then put away into 171A (EWM) for sale |
| Period end | Plant 1710 order settlement in company code 1710 |
A fit-gap view: BJ5 elements and how Contoso uses them.
Mapping like this is where fit-to-standard starts. Where Contoso matches BJ5, it can reuse the scope item test script as a starting point for its own test cases. Where it differs (no subassembly order, a custom confirmation screen, a different costing approach), the difference is a deliberate design decision that needs its own test.
What would you do?
A consultant proposes skipping BJ5 and writing Contoso's production test cases from scratch, because "the scope item uses demo data." What is the best response?
- BJ5 is SAP Best Practices' make-to-stock production process for discrete manufacturing.
- Find it in SAP Signavio Process Navigator; pick the release that matches your system.
- Read the flow by lanes (roles), hand-offs and edges (J45 upstream, period-end closing downstream).
- Map your products and deviations to BJ5 and reuse its test script as a baseline.
Check your understanding · not graded
Lesson check
1. Which scope item is shown upstream of BJ5 for buying components?
2. Where do you find the current BJ5 process flow for your release?
3. How are BJ5 process flow diagrams organized?
4. Contoso has no subassembly orders. How should that be handled against BJ5?