JIT error handling

-
  • JIT call processing
    • JIT00 003 The external status change you requested is not planned
    • JIT00 359 Component group not found for 
  • 701236 - JIT: Performance problems
    • 352105 - Copy scheduling agreement (JIT) perform. doc. flow
    • 351986 - Perf. JITR transf. new sched. agreem.items to calls
    • 1227274 + 1696110 - RJITCOP001: Various errors in the copy scheduling agreement

JIT call processing

JIT00 359 Component group not found for

Function JIT03_FIND_PARTGROUP

JIT00 003 The external status change you requested is not planned

The action is carried out, no status change ( internet connection is broken )

  1. Find the JIT control setup
  2. Find source and target statuses
  3. Find the actions to change to the target status
  4. Analyze the action

701236 - JIT: Performance problems

1227274 + 1696110 - RJITCOP001: Various errors in the copy scheduling agreement
  • Neuer Lieferplan mit Daten aus altem Lieferplan
  • SDRQCR21: Recovery of Sales and Delivery Requirements 
  • RVV05IVB: Reorganization of SD Document Indices
  • RJITREOBAT: Transfer New Scheduling Agreement Items into Existing Calls (JITR)
  • RJITLAB001: Abgleich der JIT-Abrufe mit den LAB/FAB-Bedarfen, 
The components group type determination is independent of the document flow. Because it is generally executed through a customer exit, the runtime basically depends on how this customer exit is programmed. The call of the components group determination should be minimized, for this refer to note 651685

The ATP check requires a certain runtime in general.
If this runtime is not available, this ATP check must be deactivated. For this, use the following note

The document flow increases over time and the runtimes become correspondingly longer.One possibility of correcting the problem is to optimize the way the document flow is processed. This is done with the following notes.
Ultimately the only solution is to reduce the document flow table VBFA. In the JIT area, this is currently only possible by deleting an existing scheduling agreement by a new scheduling agreement. For this, the programs which are mentioned in the following notes can be used.

351986 - Perf. JITR transf. new sched. agreem.items to calls

Table JITCO was updated for an individual item, this procedure requires a long runtime, the update is executed at package level per <= 1000 records.
The function of transferring new scheduling agreement items into existing calls can also be planned via program RJITREOBAT as a JOB.

352105 - Copy scheduling agreement (JIT) perform. doc. flow

The data volume of the document flow for scheduling agreements, in particular, for sequenced JIT calls may cause considerable performance problems. Report RJITCOP001 was created in order to avoid this.
In this case, the existing scheduling agreement is copied in the first step, rejected in step 2 and the forecast delivery schedules (LAB/FAB) are transferred to the new scheduling agreement in step 3 (here a correction delivery is created for the cumulative quantities).

As the last action, the new scheduling delivery items are transferred into the existing
JIT call (status without a delivery note).

Comments

Post a Comment