Sequencing processes

In the Administrative Functions area, you can manage some code lists that are used to configure and to control the sequencing processes in Transformation Services:

Just-In-Time (JIT) and Just-In-Sequence (JIS) performance optimizations

In sequencing processes like JIT or JIS, a large data volume must often be processed in a short time. This situation leads to specific performance requirements. Because JIT or JIS processes differ from the standard processes that use planning schedules and shipment schedules, specific performance optimizations are required. The actual requirements are specific for each JIT or JIS process. These are factors that influence a JIT or JIS process:

  • The trading partner
  • The number and kind of items per vehicle
  • The number of produced vehicles
  • The distance to the supplier, for example, on site versus long-range JIS

Especially important is to process the sequential impulse messages in time. The lead time for these messages depends on the specific production and shift model and can be lower than 1 hour.

To improve the overall performance of customer JIT or JIS installations, these features can be used in Transformation Services:

  • Transformation Services supports the mapping of large EDI messages including sequential forecast messages.

  • You can control the splitting of inbound VDA 4916 messages per vehicle, that is, per record type 662. Use the parameters Timeout (min) and Split per 662 Record (VDA 4916) in the code list MessageSplitter. By default, the splitting of the VDA 4916 messages per vehicle is activated.

    Note: If the message is split, the number of BODs that are created and must be processed is increased by a factor of up to ten. This also influences the message processing in the Release Management area.
  • If the message is not split, the resulting message can be huge (40 MB and more). Thus, it is required to cut the display length of the message. The result is shown on the Source Message and Target Message tabs in the detail view of the Manage Messages page. Otherwise, a time-out during the transmission of the data from the server to the client would happen.