JIT outbound actions

The action is a part of call control. The action carries out a logistical or a technical function for a components group, for example the posting of a goods receipt. You can define in which internal processing status of the components group an action is permitted and which internal processing status the components group should obtain after the action is carried out. Actions can be triggered by:

  • the receipt of a JIT call by EDI
  • a user dialog in the system, for example in Outbound JIT Monitoring (transaction JITOM)

JITOM transaction:
jitom_transaction

Integration

    • You define the possible actions in Customizing for JIT Outbound. You can use the actions provided as standard or define your own actions.
    • If the actions you have defined yourself
        • simply cause a change in the internal processing status, you can enter them in Customizing in the table.
        • trigger a function, as well as changing the internal processing status, you can use a Business Add-In (BadI).
      • You define the possible actions in Customizing for JIT Outbound. Internal actions are not visible in Outbound JIT Monitoring.
      • In Customizing, you also determine whether an action is relevant to the inbound process, to the outbound process or to both processes. JIT calls relevant to the inbound process are only displayed in Monitoring Inbound. JIT calls relevant to the outbound process are only displayed in Monitoring Outbound.
      • For summarized JIT calls outbound, actions are only relevant to the outbound process and are therefore only displayed in the Monitoring Outbound.
      • For sequenced JIT calls, actions are relevant to the inbound and the outbound processes, that is, they can be displayed in the inbound and the outbound monitoring.
      • You can also interlink actions in Customizing. The system then carries out two or more actions together.

Features

The system provides the following actions as standard
(the code of actions kept in the functional modules):


Action

Function

Description
OAPP Add components group to JIT call outbound The system adds a components group to a summarized JIT call, that already exists in a summarized JIT call with the same material. Both components groups differ only in quantity and date.
JIT calls to which a components group can be added must:

  • contain the same material
  • not yet have been sent
  • be suitable with regard to timing

Should these conditions not be fulfilled, a new JIT call is created using the action OCRE.

OARC Archiving JIT Calls Outbound In archiving, the system selects only those JIT calls/components groups, whose internal processing status permits this action.
You can trigger archiving from transaction JITOA, however, not from Monitoring.
OCGR Reverse goods receipt The system cancels the material document. The status of the components group is set to the subsequent status you have defined. You can repost the goods receipt.
OCRE Create JIT calls outbound The system creates the call in the system and arranges it in the call structure. This action is triggered by a sequenced JIT call inbound for sequenced JIT calls outbound and manually using transaction PK23 for summarized JIT calls outbound.
This action only creates a new message record – no new IDoc is sent.
ODLC Send delivery confirmation for JIT calls outbound You send the delivery confirmation in transaction ODLC. This transaction triggers action ODLC.
After this action, the system sets the indicator showing that the delivery confirmation has been sent in the Outbound Monitoring.
ODLI Create delivery for summarized JIT call outbound (for stock transfer) The system creates a delivery, to which it adds the call components of the component groups selected.
This delivery is important for the creation of the transfer order which you need for an internal stock transfer within your plant.
OFIN Close components group outbound The system sets the status asclosed for this call outbound/components group.
OGRE Post goods receipt for JIT outbound The system posts the goods receipt for the JIT call outbound.
The goods receipt is posted cumulatively per material and supplier.
OMOD Modify JIT calls outbound The system changes the total call outbound.
This action only creates a new message record – no IDoc is sent at this stage.
OREO Delete JIT call outbound The system deletes the call from the database.
OREP Repeat send of outbound messages You use this action in emergencies, should any technical problems arise. The call is resent.
OSDD Send outbound message – process With this action, a message is sent for selected components groups if a message record exists for these components groups.
OSDP Send outbound call: create message You need this action for actionsOCRE and OMOD. In these two actions, action OSDP is carried out automatically by the system.
OSHP Process payment advice for outbound call. As soon as you have received the payment advice, the status of the sequenced JIT call is updated.

Delivery schedule/JIT delivery schedule integration

SEQJIT

If only forecast delivery schedules are sent from the customer scheduling agreement (no JIT delivery schedules) JIT delivery schedules can be generated from the JIT calls.
Using this method, you are given the option of (manually) comparing the planning (FDS) with the JIT calls.

JIT inbound actions (SeqJC, SumJC)

The action is a part of call control. It has a logistical or technical effect on a components group. This may be the printing of a components list or the creation of a delivery, for example. You can define the internal processing status of the components group for which an action is permitted and the internal processing status the components group is to receive once the action has been carried out. Actions can be triggered by:

  • An incoming JIT call by EDI and an external status change.
  • A user dialog in the system, such as a progress confirmation.

Integration

  • You define the possible actions in Customizing for JIT Inbound. You can use the standard actions provided or define your own actions. If the actions you have defined yourself:
    1. Simply cause a change in the internal processing status, you can enter them in Customizing in the table.
    2. Trigger a function as well as changing the internal processing status, you can use a customer exit.
  • You define the possible actions in Customizing for JIT Outbound. Internal actions can only be triggered when you receive a call by EDI or with internal system activities and not in a user dialog.
  • You can also interlink actions in Customizing. The system then carries out two or more actions together.

Features

The system provides the following actions as standard
(the code of actions kept in the functional modules):

Action Function Description
Actions for Creating and Changing
CREA Create JIT call The system creates the call in the system and arranges it in the call structure. This action is usually triggered by a forecast signal from the OEM.
MODI Change JIT call (total) The system changes the total call.
The action MODI is contained in action PIN. See also: Action PIN.
MODH Change call (call header and components group) With the external status change, for example, the system changes only the call header and the components groups.

Continue reading “JIT inbound actions (SeqJC, SumJC)”

JIT: How Component group type assignment is done in call components?

sap-blau

How the system will does the job:

The system carries out this function automatically, each time a JIT call is received. In this way it assigns each call component transmitted to a components group type. The components group type then takes on the internal control of the call components.

With sequenced JIT calls for assemblies, the system assigns several call components to the same components group type. With the other call types the call components and the components group type form a logical unit and the system therefore assigns a different components group type to each call component.

In the components group determination the system compares whether the characteristics of the call components match a components group type. As soon as it can assign a call component, it continues with the next one. In the profile for the components group determination you can define with which priority the system should consider the various characteristics. The system determines the relevant characteristics of the call components as follows:

JIT customer

The JIT customer is made up of the sold-to party and the partner description and can therefore be taken from the IDoc.

Unloading point and assembly location

The unloading point and, if necessary the assembly location, are also transmitted with the JIT call. The system can also take these characteristics of the call components from the IDoc.

Components group material

The JIT customer generally transmits the components group material with a call. You have several options for defining the components group material of the call component before the components group determination.

You can realize an individual components group material determination using a customer exit. This is particularly recommended for sequenced JIT calls for assemblies, due to the large number of variants.

If you use the process for discrete materials, you can transfer the material of the call components as a components group material.

If you use the process for discrete materials and exactly one components group material can be assigned to a call component, you can transfer the configurable material of the call component as a components group material. To do this you must have entered the configurable material in the material master of the call component in the tab page Basic data 2 in the field Cross plant conf.mat.

Production version

You can also assign the production version using a customer exit. The production version allows you to assign two otherwise equal call components to different components group types, to produce them on different production lines, for example.

There are also call types – please follow the below link:

Call Structure and Call Types

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):


Continue reading “JIT inbound from scratch proccess IMG”

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:

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

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).

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.