In JIT whenever the master data is changed[ JIT customer data , JIT Material data , JIT component group data ] the changes are updated in the database and not in the shared buffer. Hence the reorganization of the buffers needs to be triggered manually through the transaction JITR ( report :- RJITMREO01)
Options in JITR
1)Recreate basic data in shared buffer
The first option refreshes the shared buffers.
JIT customer data – Data in Table JITCU is present in the buffer table JITSB (CU)
JIT material data – Data in Table JITMA is present in the buffer table JITSB (MA)
JIT part group – Data in Table JITPG is present in the buffer table JITSB(PG)
2)Reorganize JIT material master data
This option is mainly use to remove the unwanted data in the table JITMA. It can also use to to find the scheduling agreements with a reason for rejection and then delete them from JTIMA. But inorder to list out for deletion these scheduling agreements has to fulfill two criteria
1) Scheduling Agreements will have “reason for Rejection” set( which is set in this case)
2) No entry corresponding to the scheduling agreement exist in JITCO table
If there exist JIT calls corresponding to the agreement , the system would not allow us to delete those from JITMA , using JITR. In order for that we need to create a New scheduling agreement and map the existing JIT calls to the new one .This can be done by using the third option of JITR
Option 3: Transfer from new scheduling agreements into existing JIT calls
1.Create a scheduling agreement.
2.Create a JIT call with reference to this Scheduling agreement
3.Change the scheduling agreement and set a #reason for rejection#.
4.Execute JITR with option 3.
5.Create a new scheduling agreement with the same customer,customer
material and unloading point.
6.Now execute JITR with option 3.
7.Execute #Start Transfer#
After this the JIT call is mapped to the new scheduling agreement.
At code level these two criteria checking are happening in the
function module JIT03_GET_MATERIAL_FOR_REORG
Line 48 (1)* only material where ABGRU isn’t initial
ABGRU:- Reason for rejection
DELETE jitma_sb_lt WHERE abgru IS initial. <<<<<<<<
SELECT DISTINCT matid FROM jitco INTO TABLE matid_lt
LOOP AT jitma_sb_lt INTO jitma_sb_ls.
READ TABLE matid_lt INTO matid_ls
WITH TABLE KEY mat_l = jitma_sb_ls-matid.
IF sy-subrc EQ 0.
DELETE TABLE jitma_sb_lt FROM jitma_sb_ls.<<<<<<<<
ENDIF. ” IF sy-subrc NE i1_gc.
In the release DI 46C2, the option of refreshing the buffers is permitted on a single application server However, from the release DIMP 471 onwards, refreshing on multiple/all application servers is allowed.