TAS Oil Scenario

TAS Oil Scenario.

Terminal Automation system, can be used to record correct Loaded or discharged quantities or any change in the shipment at the Loading or Discharge location. Mainly there are two scenarios where TAS is widely used. Pick Up and Shipment.

Pick Up: A pick up scenario is described as a trade condition where the customer picks up the goods from the vendors location. In such scenarios, the goods issue is done at the vendor’s location itself and there are no further ownership on the goods. In R/3, such a scenario is captured by performing a Goods Issue (GI) at the delivery level itself. IDOCS of type OILLDD or Oil Loading are used to simulate such scenarios.

A TAS IDoc can be attached in pick up scenario at a Sales contract/ Sales Order level. The Execution of such an IDOC would create the further Documents being Sales Order – Outbound Delivery/ Outbound delivery as the case may be dependent on at what level the IDOC was attached.

Attaching IDOC at Sales Contract Level.:

One can trigger TAS at the sales contract level to automate the subsequent document processing being an Order and an Outbound Delivery. A Load Id of type 0001 (Calloff (rush Order) and Delivery with Control Structure Type ‘A’ should be attached to the line item in the contract. The system would then create an IDOC of Type OILLDD with Action ’01 (create Pick up Load). Function IDOC_INPUT_OILLDD is executed to interpret to IDOC and create subsequent documents. Action Flag would differ depending at what level the Load Id has been attached.

Function module OIK_SD_CALLOFF_DELIVERY_CREATE is called to create the Order and Delivery for the Sales Contract.

Shipment: A shipmen scenario Is where the vendor ships the goods to the customers location and performs a GI at the customer location. TAS does not extend beyond a companies network, therefore it is not a practice to capture the delivery details at GI at the customer’s location. TAS is used in a Shipment scenario to capture the actual Loading details at the vendor location.

A Load ID of Type B0001 with control structure type ‘B’is attached at the shipment creation level for a vehicle being used in the shipment. This detail is transmitted to the Loading Plant through IDoc of type OILLDD using Action Flag 15. The TAS system captures the actual loading parameters for the shipment and sends the IDoc back to R/3. When the IDoc is executed at the R/3, the shipment captures the actual loading parameters and is changed to status Completely Loaded.

Delivery Confirmation Using TAS for STO:

Since TAS does not capture information from any customer’s location, TAS is not used to capture delivery confirmation details for an outbound delivery. However TAS has the capacity to perform a GR at the same vendor location for a Stock Transport Order. Procedure followed is the same using Load ID of Control Structure type D or E.

IS-OIL-TAS

Load ID Validity Date Assignment in Sales Contract:

Sales contracts are created with reference to another contract. If the contracts are TAS relevant, then the load Id would be automatically copied to the TAS Screen. This can be done by setting automatic Load ID assignment for the control structure type in the TAS customization and also can be assigned through USER Exits. Customers normally follow the method of implementing the user exit EXIT_SAPLOIK7_130 or EXIT_SAPLOIK7_110 to assign the load id.When the load id is assigned, the validity of the load id is copied from the contract. In case the period of the contract is changed, then the validity of the Load Id should be manually checked for correctness or done through a user exit if no manual intervention is expected. There is a check in the LOIK9F01 Form adjust_validation_period to check for the start date and end date of the load id. The load id details are stored in the gt_xoik01 table. This table is filled through the user exits or on the click of TAS button if automatic load id assignment is active. In case there is no ALA done, then the global table is filled when we assign a load id manually. Once the load Id is assigned (in any form), the first dates are copied as the load Id validity dates. Any further manipulation to the contract start or end date should be a date between the first given date range. Otherwise the date (start or end date) which lies outside the first date range would not be copied to the TAS Screen for load id validity. The system gives a warning/ information message that the dates have been changed. The user needs to change the dates manually or, this should be handled through an exit as the case may be suitable or the business.

Change log in shipment does not appear.

Some fields in the shipment might not appear in the shipment change log. This could be because of the change log field not set for the domain in the table for that particular field. The chage log should be set at the domain level in the table and once this is checked, the log would show the entry if changed.