JIT inbound from scratch proccess IMG

First of all we’ll create a plant, and then – sales organization:

SPRO > Enterprise structure > Definition > Define, copy, delete, check sales organization

img_56151a2c1b378

Checking SPRO – step by step:

Creating Reconciliation Account in General Ledger (FS00):

In OX19 please assign Control area to Control company (new entries).

Now we will create customer for JIT proccess, t-code XD01, on the tab page “Unloading points” enter an unloading point:

On the “Sales area data > Shipping” select the indicator Order combination.

On the tab page Partner Functions enter a Partner Description. If you want to enter other goods recipients, make an entry in the table.

XD02

Then you have created a JIS system partner profile (t-code WE20).

Next step – is to creating a couple of component group material (KMAT):


Read the rest of this article

JIT Humor

Receiving invoice via EDI: INCINV_CREATE

Basic types INCINV_CREATE01 / INCINV_CREATE02 – Incoming Invoice (IncomingInvoice) are available since EHP5.

Next MRM BAPI’es provides Invoice Verification:

  1. ALE_INCOMINGINVOICE_CREATE1
  2. BAPI_INCOMINGINVOICE_CANCEL – Invoice Verification: Reverse Invoice
  3. BAPI_INCOMINGINVOICE_CHANGE – Invoice Verification: Change Provisional Invoice
  4. BAPI_INCOMINGINVOICE_COMPLAIN – Invoice Verification: Display Letter of Complaint
  5. BAPI_INCOMINGINVOICE_CREATE – Invoice Verification: Post Invoice
  6. BAPI_INCOMINGINVOICE_CREATE1 – Invoice Verification: Hold/ Park/ Park As Complete/ Post Incoming Invo
  7. BAPI_INCOMINGINVOICE_DELETE – Invoice Verification: Delete Provisional Invoice
  8. BAPI_INCOMINGINVOICE_GETDETAIL – Invoice Verification: Display Incoming Invoice
  9. BAPI_INCOMINGINVOICE_GETLIST – Invoice Verification: List Incoming Invoices
  10. BAPI_INCOMINGINVOICE_PARK – Invoice Verification: Park Invoice
  11. BAPI_INCOMINGINVOICE_POST – Invoice Verification: Post Provisional Invoice
  12. BAPI_INCOMINGINVOICE_RELEASE – Invoice Verification: release invoice
  13. BAPI_INCOMINGINVOICE_SAVE – Invoice Verification: Flag Invoice for Background Processing

IncomingInvoice INCINV_CREATE IDoc will be passed to FM’s BAPI_IDOC_INPUT1 (Inbound BAPI IDoc: Individual Processing) or BAPI_IDOC_INPUTP (Packet Processing) which calls
IDOC_INPUT_INCINV_CREATE and subroutine CREATEFORMDATA1 (SAPLMRM_BAPI).

Sample IDoc INCINV_CREATE02 from quality system is listed below:

Own customer exit for JITL (JITPP)

Defining the production info describes principles of using the table JITPP (“JIT : Production Information”) – repetitive manufacturing (A), stock transfer (B) and customer exit (Z). Table field is JITPP-BAFLU.

The transaction for controlling this behaviour is JITL:

The last one (customer exit) is very typical customer-function call, which is calls from functional module JIT03_DO_BACKFLUSH (CALL CUSTOMER-FUNCTION ‘009’), so function EXIT_SAPLJIT03_009 transmits into include ZXJIT0U19 next structures:

JIT call main tables linking

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

Just in sequence

jis

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

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.

ISU_VDEW_APERAK

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

/SCTM/TMAPERAK1

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