Advanced Scenarios

While Manufacturing Batch Size is designed to enforce a consistent and structured batch production model, real-world manufacturing environments often require flexibility to handle exceptional situations.

This section describes how the system behaves in non-standard scenarios and how batch control logic adapts when typical constraints—such as fixed quantities, single-lot production, or strict BOM alignment - are challenged.

Producing Quantities That Do Not Match Batch Size

In standard operation, production is executed in full batches. However, demand may not always be perfectly aligned with the defined batch size.

When a required quantity exceeds the batch size, the system automatically splits production (when accepting the warning message) into multiple batch production orders, each representing one complete batch.

When the demand is not an exact multiple of the batch size, the system rounds up the required quantity to ensure that all production orders still correspond to full batches. This ensures consistency in execution, even if it results in overproduction relative to the original demand.

This behavior preserves the integrity of the batch model, ensuring that partial batches are avoided.

Restrictions on Manual Adjustments in Production Orders

Batch-controlled production orders introduce strict limitations on manual changes.

In these scenarios:

• Production order quantities cannot be edited
• Component lines cannot be freely added or removed
• Changes to the Production BOM structure trigger warnings

These restrictions are intentional and ensure that production remains aligned with the predefined batch configuration. If deviations are required, they must be handled outside the batch-controlled flow.

This scenario is particularly relevant when users attempt to adapt production orders to unexpected operational conditions, such as material shortages or urgent changes in demand.

Lot Assignment Conflicts During Production

A key principle in Manufacturing Batch Size is that each batch must correspond to a single, unique lot.

During production posting:

• Only one lot can be assigned to a batch production order
• The same lot must be used consistently across all output transactions
• Attempting to use a different lot will result in an error
• A lot cannot be reused across different batch production orders

These constraints ensure strong traceability but may require operational adjustments when production interruptions or corrections occur.

This scenario typically arises when:

• Output is posted in multiple steps
• Users attempt to correct or reprocess production entries
• There is confusion in lot assignment across teams

Working Without Proper Lot Configuration

Batch-controlled production relies heavily on item tracking configuration.

If the system is not properly configured - for example, if Create Lot No. Info. on Posting is not enabled - batch-specific controls on lot information cannot be fully enforced. In such cases, the system falls back to standard behavior, reducing traceability and control over batch lots.

This scenario highlights the dependency between batch logic and underlying item tracking configuration.

Partial Reclassification and Lot Splitting

After production, users may need to move or adjust inventory in ways that conflict with batch structure.

When attempting to:

• Split a batch lot into smaller quantities
• Change lot numbers for part of a quantity
• Move only a portion of a batch to another location

The system will trigger warnings and require user confirmation before proceeding.

If the operation continues:

• The batch structure may be partially broken
• The system may remove or adjust the batch designation on affected lots

This ensures flexibility while still making the user aware of the impact on traceability.

Batch Size Behavior in Planning Components

Although full production planning is not part of the app, batch logic extends into component requirement calculations.

Advanced scenarios may arise when:

• Demand does not match batch size
• Planning data includes complex requirements

In these cases:

• Quantities are calculated based on batch formulas
• Results are rounded up to match full batch requirements
• Scrap values are excluded from calculations
• Manual adjustments to planning lines are restricted

This ensures that even indirect processes, such as planning evaluation, remain consistent with batch production logic.