Hierarchy
IS-OIL (Software Component) IS-OIL⤷
IS-OIL-DS-TAS (Application Component) Interface to Terminal Automation System⤷
OIK_I (Package) TAS (Terminal Automation System)
IMG Activity
| ID | SIMG_TD_TAS_0001 | Define functions and function groups |
| Transaction Code | S_SO5_65000269 | IMG activity: SIMG_TD_TAS_0001 |
| Created on | 19990913 | |
| Customizing Attributes | SIMG_TD_TAS_0001 | Define functions and function groups |
| Customizing Activity | SIMG_TD_TAS_0001 | Define functions and function groups |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_TD_TAS_0001 |
Description
Here function modules are defined and assigned to function groups. The following predefined function modules are available in the IS-Oil System:
OIK_SD_CALLOFF_CREATE
This function module creates calloffs based on loading data in the Idoc that is related to contract items. The relationship between the loading data and the contract items is determined by the Load ID. This function module does not create deliveries immediately.
The function module from the standard system, SD_DOCUMENT_COPY_ONE_STEP, is used by this function module to create calloffs in the same manner as in the standard SAP system.
OIK_SD_DELIVERY_CREATE
This function module creates deliveries based on loading data in the Idoc related to order items. The relationship between the loading data and other items is determined by the Load ID contained in the loading data. This function module does not create a goods issue immediately.
To create a goods issue, the delivery numbers are stored in table OIK03. The report ROIKPGIS reads each entry from this table and calls the transaction VL02 which posts the goods issue for the delivery. After goods issue has been posted, the entry for the delivery is deleted from table OIK03.
OIK_SD_CALLOFF_DELIVERY_CREATE
This function module creates calloffs based on loading data in the Idoc related to contract items. The relationship between the loading data and the contract items is determined by the Load ID which is part of the loading data. This function module immediately creates deliveries for the created calloffs.
The function module in the standard system, SD_DOCUMENT_COPY_ONE_STEP, is used by this function module to create calloffs and deliveries in the same manner as in the standard SAP system.
It is not possible to post the goods issue immediately. To create the goods issue, the delivery numbers are stored in table OIK03. The report ROIKPGIS reads each entry from this table and calls transaction VL02 to post the goods issue for a delivery. After goods issue has been posted, the entry for the concerned delivery is deleted from table OIK03.
OIK_TD_SHIPMENT_LOAD_CREATE
This function module replaces the loading transaction for a scheduled shipment. The action code in the Idoc determines if a load save (Action Code 11) or a load confirm (Action Code 15) is started.
The Load ID references a vehicle. Depending on the data in the data area E1OILT3 of the Idoc, the quantities are split across all documents with the same material on the vehicle, are split across all documents with the same material in a compartment, or are booked exactly against a document assigned to a compartment.
OIK_OILDD01_TASGRP2_FORWARD
This function module creates a copy of the loading Idoc and replaces the original Load ID with a value from one of the following fields in the Load ID master data record: LID Depot, 3rd Party Code, or 3rdDelNr. The Idoc is then sent to the ALE layer, and can be used as an inbound Idoc for another IS-Oil system.
OIK_IDOC_TASGRP2_CREATE
This function module enhances the Idoc with Load ID master data. The Idoc is then sent to the ALE layer.
OIK_CUSTOMER_FUNCTION_EXAMPLE
This function module is an example to show what must be considered when a customer function module is programmed. Detailed information can be found in the topic Example for Programming a User Function Module.
Activity
All function modules are in function group OIK2. The user can add self-defined modules. The function module OIK_CUSTOMER_FUNCTION_EXAMPLE is provided as an example of how new modules should be added.
After function modules have been defined, they can be assigned to function groups. SAP function modules can be used with user-defined function modules. Maintaining an identical interface ensures that inbound data is redistributed out of the function module.
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_TD_TAS_0001 | 0 | I400022111 | Interface to Terminal Automation System |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VC_OIKFUNC | C - View cluster | SM34 | OIK_000001 | TAS Load indicator - function and group maintenance |
History
| Last changed by/on | SAP | 20030617 |
| SAP Release Created in |
