Just in sequence


Abruf vom Lieferplan (LAB oder FAB).
You can distinguish between forecast delivery schedule (LAB) and JIT delivery schedule (FAB) by the value in the E1EDP10-SCREL field; 03 stands for LAB and 02 for FAB.

Lieferabrufe – LAB, wiki
Feinabruf – FAB, wiki

VDA 4905: Lieferabrufe (DELINS, DELFOR) – Call off
VDA 4905/2: Call off – Delivery Instruction (Odette Message DELINS)
VDA 4915: Feinabrufe (DELJIT) – Detailed Call Off (JIT)
VDA 4916: Produktionssynchrone Abrufe / JIT / JIS – Call Off Just-in-sequence.

The messages for scheduling agreement delivery schedules in the standard system:
– LPH1 for LAB – monats- oder wochengenau;
– LPJ1 for FAB – tagesgenau.

Scheduling agreement release

ABAP: Apply JIT action

Applying JIT action similar to background actions in JITM and JITOM can be done using ABAP:

Standard & user-defined actions modules

Where JIT-actions are defined and where the code to carrying them out?

There is function pool JIT04.
Include LJIT01CON keeps constants of the standard actions:

and the FM JIT04_SET_ACTION_INTERN keeps the code:

User-defined actions for JIT inbound are under Enhancement JIT04_01 (transaction SMOD):

So components of JIT04_01 are FM exits EXIT_SAPLJIT04_001, EXIT_SAPLJIT04_002 and EXIT_SAPLJIT04_003. You can use for own code their includes ZXJIT0U01, ZXJIT0U04 and ZXJIT0U03 accordingly (variable action_iv keeps the current action).

Outbound actions


The very similar structure for JIT outbound.
There is function pool JITOUT04 with include LJITOUT01CON.

User-defined actions for JIT outbound can be implemented into BAdI interface IF_EX_JITO_ACTION (BAdI JITO_ACTION):

The shortcut transaction for it is S_KA5_12001363.