BMW JIS5000 sequence process
Purpose
This page describes the BMW JIS5000 sequence process in Automotive. It focuses on the steps that differ from a normal sales process: base setup, PAB order creation, EDI configuration, release of JIS messages, sequence control, and sequence-based loading-unit assignment.
1. Prepare the base setup
BMW uses a GLT number on the master label. The highest already used number must be maintained in Automotive Setup. If the field is not visible, it must be added through personalization.
In addition, BMW JIS works with dummy loading units so that the BMW-defined sequence can be represented correctly. For that reason, the packaging-instruction code BMW must be maintained on the master loading units.
| Setup point | Required maintenance |
|---|---|
| Highest GLT number | current running value for the master label |
| Packaging instruction code BMW | maintain only on master loading units |
2. Create the automotive sales order correctly
For BMW JIS, a standard automotive order is not enough. These fields must be set deliberately:
| Field | Required value |
|---|---|
| Order subtype | PAB |
| Call-off type | Delivery and FAB/PAB |
This combination is the basis for making production-synchronous call-offs, sequences, and shipments fit together later.
3. Configure the EDI baseline for BMW JIS
Even if inbound JIS messages can later be imported manually or automatically, the EDI structure must exist first.
Use this sequence:
- Open EDI message types and run Create standard messages.
- Maintain the EDI partner settings on the customer card.
- In the partner line, fill at least these values:
| Field | Value |
|---|---|
| Active | Yes |
| Direction | Outbound |
| Message type code | VDA4913 |
| Message location | project-specific path or outbound channel |
| Guide | BMW JIS |
- In EDI Setup, run Create EDI standard data. If you use file-based transmission, use the variant with file path.
4. Review and release JIS messages
Imported JIS messages appear in the Prod.-Sync. Call-Off Overview. There they can not only be viewed, but also released. Only released records are available for follow-up processes.
Before release, check:
- are the sequence details complete,
- is the message linked to the correct order,
- are there any unresolved EDI or master-data issues,
- is it clear which time range should be processed in the next sequence run.
5. Use sequence control
After the sequences were reviewed and released, they must be connected to their related shipments. Use Sequence Control for that step.
The usual sequence is:
- Open sequence control.
- Select status Preparation and the required time range.
- Mark the displayed sequences.
- Change the status to Open.
- Then create the shipment through New and Create goods issue.
The status change is not just formal. Only open sequences can move into the operational goods issue.
6. Goods issue and loading-unit assignment in sequence order
In the goods issue, open Loading Unit Assignment through Automotive. Then run Loading Unit Assignment in Sequence Order.
This creates the loading-unit assignment in the correct sequence order. Afterwards the assignment must be confirmed through Register. Only then should the delivery note be printed.
Control steps
| Point in time | What to check |
|---|---|
| Before the first test | GLT number and BMW packaging instruction maintained |
| When creating the order | order subtype PAB and call-off type Delivery and FAB/PAB set correctly |
| Before releasing the JIS message | sequence reference, order, and EDI status are plausible |
| Before goods issue | sequence status is really open |
| Before printing the delivery note | loading-unit assignment in sequence order is registered |
Typical error patterns
| Situation | Possible cause | Check |
|---|---|---|
| Sequence process does not start cleanly | PAB or call-off type is wrong on the order | inspect the order header |
| JIS records are available but do not continue | release in the Prod.-Sync. overview is missing | check the release status |
| Shipment order is wrong | loading-unit assignment in sequence order was not run or not registered | inspect loading-unit assignment in goods issue |
| EDI does not start technically | partner line or standard data is incomplete | inspect EDI message types, partner, and setup |
Result
- You can separate the BMW JIS process clearly from a normal sales flow.
- You know where PAB order, EDI, sequence control, and loading-unit assignment depend on each other.
- You avoid common failures caused by wrong order type, missing release, or incorrect sequence assignment.
Links