JIT call main tables linking

May 5, 2014

Inbound:

Table JITMA (JIT Material Data)

JIT Material	Customer	Material	Sales.Doc	Item	Base UoM
110063	DNFG	720000000034	30000001	10	PC
100900	DNFG	720000000098	30000002	10	PC
200014	DNFG	720000000011	30000003	10	PC

Table JITIT (Components Group)

Components group	Call number	CG type	Call control	External status	Internal processing status
80111117	55000828	D051	0005	280	4000
80111118	55000828	D052	0009	280	4000
80111119	55000828	D053	0009	280	4000

Table JITHD (Call header)

Call number	Customer	Customer external JIT call number	Sequence No.	Call type	Add.Info 1
55000828	DNFG	15000RASA37124	1882	S	NB

Table JITCO (Call components)

Components group	JIT Material	Qty
80111117	110063	1
80111118	100900	1
80111119	200014	1

Outbound:
Inbound and outbound JIT-calls linked together (in case of) using field JITOIT-POSID.

Table JITOHD (Call header outbound)

Call key	Call type	External call number	Sequence No.
404565	D (sum) / S (seq)	0000404565

Table JITOIT (Components Group JIT Outbound)

Call key	Components group No.	Internal Processing Status
404565	5000808746	0040
404565	5000808747	0040

Table JITOCO (Call components)

Components group No.	Control cycle number	Quantity
5000808746	88273	1
5000808746	119793	2
5000808747	133513	1

Table PKHD (Control cycle)

Control cycle number	Material
88273	72110063
119793	72100900
133513	72200014

Customer, JIT, JIT-call
1 comment

Just in sequence

January 22, 2014

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

bedarfssynchrone Produktion, JIS, JIT, Reihenfolgesynchronität
1 comment

ABAP: Apply JIT action

October 14, 2013

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

call function 'JIT04_SET_ACTION'
      exporting
        action_iv            = 'ZSHP'
        commit_iv            = 'A'
        ext_trigger_iv       = 'O'
        just_status_upd_iv   = 'X'
      tables
        jc_hd_it             = lt_hd2
        jc_it_it             = lt_jitit
      exceptions
        action_not_performed = 1
        wrong_parameters     = 2
        others               = 3.
    if sy-subrc <> 0.
      leave program. " abort
      message '' type 'I' display like 'I'.
    endif.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

call function 'JIT04_SET_ACTION'

exporting

action_iv = 'ZSHP'

commit_iv = 'A'

ext_trigger_iv = 'O'

just_status_upd_iv = 'X'

tables

jc_hd_it = lt_hd2

jc_it_it = lt_jitit

exceptions

action_not_performed = 1

wrong_parameters = 2

others = 3.

if sy-subrc <> 0.

leave program. " abort

message '' type 'I' display like 'I'.

endif.

ABAP, JIT
Comments Off

Standard & user-defined actions modules

August 19, 2013

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

– standard

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

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.

BAdI, IS-A-JIT, JIS, JIT, User Exit
1 comment

ISU_VDEW_APERAK

December 18, 2012

ISU_APERAK Messages from EDIFACT Category APERAK
ISU_VDEW_APERAK APERAK (German Electricity Associaiton 1.0, D.99A)

Uncategorized
No comments

/SCTM/TMAPERAK1

December 18, 2012

Anwendungsfehler und Bestätigungsnachricht
Application Error and Acknowledgement Message

/SCTM/E1OCBUNB1 Interchange header
SYNTAX_ID CHAR04
SYNTAX_VER_NO NUM1
SENDER_ID CHAR35
SND_ID_QUALI CHAR04
RECIPIENT_ID CHAR35
REC_ID_QUALI CHAR04
DATE_PREPARATION NUM6
TIME_PREPARATION NUM4
IC_CONTROL_REF CHAR14

/SCTM/E1OCBUNH1 Message Header
MESS_REF_NO CHAR14
MESS_TYPE_ID CHAR6
MESS_TYPE_VERNO CHAR03
MESS_TYPE_RELNO CHAR03
CONTROL_AGENCY CHAR03

/SCTM/E1OCBBGM1 Beginning of Message
DOC_NAME_CODE CHAR03
DOCUMENT_NAME CHAR35
DOCUMENT_NUMBER CHAR35
MESS_FUNC_CODE CHAR03
RESPONSE_TYPE_CODE CHAR03

/SCTM/E1OCBDTM1 Date/Time/Period
DTM_FC_QUALIF CHAR3
DTM_PERIOD_VALUE CHAR35
DTM_FORMAT_CODE CHAR3

/SCTM/E1OCBFTX1 Free text
SEG_ID CHAR3
TEXT_SUB_CODE_QUALIF CHAR3
FREE_TEXT_VALUE_1 CHAR512

/SCTM/E1OCBRFF1 Reference
REF_FUNC_CODE CHAR3
REFERENCE_ID CHAR30

/SCTM/E1OCBNAD1 Name and Address
PARTY_FUNC_CODE CHAR3
PARTY_IDENTIFIER CHAR35
CODE_LIST_ID_CODE CHAR3
RESP_AGENCY_CODE CHAR3
PARTY_NAME_1 CHAR35
STREET_POBOX_1 CHAR35
STREET_POBOX_2 CHAR35
STREET_POBOX_3 CHAR35

/SCTM/E1OCBUNT1 Message Trailer
NUMBER_MESSAGE_SEG NUM6
MESSAGE_REF_NO CHAR14

/SCTM/E1OCBUNZ1 Interchange trailer
IC_CONTROL_COUNT NUM6
IC_CONTROL_REF CHAR14

APERAK, EDI, IDoc, TMAPERAK1
No comments

Filling JITIT-VBELN_VL

September 25, 2012

Linking JIT calls to delivery (e.g. after DELE action) are done in table JITIT, field VBELN_VL.
Functional modules are JIT02_UPDATE_PG_STATUS_DELIV and JIT01_MODIFY_JITIT_STAT_DELI.

JIS, Shipping
No comments