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:
- 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 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. |
| MODG | Change call (components group) | The system only changes the components group of the call. |
| JIT2 | Change a call using transaction JIT2 | The system carries out this action if you have changed a call with the transaction Change JIT call (JIT2). |
| MODC | Change a JIT call component |
You use this action to change individual components of a JIT call. Only the component to be changed is sent and changed. This may be the case if your customer increases the quantity of a component. If the system cannot find the component in question then another component is added to the call similar to action INSC. |
| INSC | Add call component | You use this action to add a component to an existing JIT call. The system sends only the new individual call component and adds it to the JIT call. |
| DELC | Delete a call component | You use this action to delete a component from an existing JIT call. |
| DLET | Delete components group | The system deletes the components group, if it is no longer transmitted for a repeated call. If you do not define the action, the components group is retained in the call. |
| CGAP | Add components group (SumJC) | The system adds a components group to a summarized JIT call that already exists with the same identification in the summarized JIT call. Both components groups differ only in quantity and date. |
| Actions for Production and the Completion Message | ||
| PIN | Transfer to production |
The system transfers a components group to production. This action is usually triggered by an assembly signal from the OEM. If no call exists for this components group, the system creates a new call. If the components group type changes, the components group is deleted and a new one created. In this case, you must have maintained action DLET for the status change to initial in Customizing. Note that the action PIN contains the action MODI. |
| PCOM | Print component list | The system prints a list of call components, which you can enter in the production as an accompanying note. |
| PINP | Release for production and print component list | Interlinked action with sub-actions PIN and PCOM. |
| CGRP | Generate and assign grouping term | Assigns grouping information to a components group and to a grouping index. |
| POUT | Completion message from production | The system assigns the status to the components group, but does not carry out any goods movement. |
| PICK | Print pick list | The system prints a pick list, which you can display, for example, on a packing rack. |
| POUP | Create completion message, and print pick list | Interlinked action with sub-actions POUT and PICK. |
| Actions for the Backflush and Goods Movement | ||
| BFLU | Carry out backflush | The system carries out the repetitive manufacturing backflush or a stock transfer. |
| BFLP | Carry out backflush in the background | The system carries out the repetitive manufacturing backflush in the background. |
| BFDL | Create backflush and delivery | Interlinked action with sub-actions BFLU and DELI. |
| Actions for the Delivery | ||
| DELI | Create Delivery | The system creates a delivery, to which it adds the call components of the component groups selected. |
| DELU | Add components groups to the delivery | The system adds the components groups of an existing (open) delivery. |
| DELD | Remove components groups from the delivery | The system removes the components groups from the delivery. |
| DLSP | Send Delivery from External Service Provider to Manufacturer | The system sends a delivery from an external service provider to a manufacturer. |
| VL10 | Create SumJC delivery from VL10 | For summarized JIT calls, you can generate a delivery list. The system selects all calls for the delivery list, whose internal status permits this action (the action calls the sub-action DELS). |
| DELS | Create delivery from VL10 / without lock | Sub-action of action VL10 You can replace this action by one of your own, if you want to created your own delivery list. |
| GOIS | Post Goods Issue | You can use this action to post the goods issue for a JIT delivery. |
| GOCC | Reverse goods issue | You can use this action to reverse the goods issue for a JIT delivery. |
| Actions for closing the calls. | ||
| STAT | Update JIT calls in BW | The system only updates the calls/components groups in the Business Information Warehouse, whose internal processing status permits this action. |
| FINI | Close components group | The system sets the status as closedfor this call/components group. |
| ARCH | Release JIT calls for archiving | In archiving, the system selects only those JIT calls/components groups, whose internal processing status permits this action. |
| REOR | Reorganize JIT calls | The system deletes the call from the database. |
| Actions for special occurrences | ||
| CANC | Cancel components group | The system sets the components group to the internal processing statusCanceled. |
| SCRA | Reprint component list (scrap backflush) | The system prints the component list with highest priority, so that the components group can be reproduced immediately. |
| REPR | Reprint component list | The system prints the component list for a components group, if this has been damaged, for example, in production. |
| NIO | Missing parts message (status change) | With this action you can set a scrap components group to a park status, if you do not want to produce immediately. |
| WFLW | Trigger workflow event | The system triggers a workflow event. |
| Actions for internal calls and buffer store | ||
| WIN | Store components group | The system stores a components group from the issue storage location of the components group materials in the puffer storage location. |
| SWCG | Exchange components group (internal call) | The system exchanges the component groups of two calls. Using this action, you can deliver the JIT calls using buffer stores. |
| PSWC | Print components group exchange | You can carry out this action after exchanging the components groups. The system prints a list of the call components to be removed from storage, which you can forward to the employee in storage. |
| WOUT | Remove components group from storage | The system transfers a components group from the buffer storage location to the receiving storage location of the components group material. |
| CRHU | Create a handling unit from a components group | The system creates a handling unit from a components group before you store it in the buffer storage location. |
| DEHU | Pack and delete handling unit | The system unpacks a components group from the handling unit and deletes the HU, for example after you have removed it from the buffer storage location. |
| HUPP | Generate an HU in production | The system generates an HU from production. You can delete it using the action DEHU. |
| Actions for the Delivery Confirmation | ||
| MTCH | Set delivery confirmation to ‘matched’ | The system matches the quantities with the components group. |
| UDMT | Reset delivery confirmation match | The system resets the quantity match of the components group. |
October 3, 2016