PUNINAR JAYA OTM IMPLEMENTATION:

OTM business objects’ transfer to FTI and ETL set up

Scope:
This document covers the steps needed to transfer the OTM order releases, buy shipments, sell shipments, invoices
and bills to FTI database and schedule and ETL process needed for the transfer in the Puninar OTM implementation

Steps Involved:

In order to make all the business objects eligible for being transferred to the HDOWNER (database schema used for
FTI) schema from GLOGOWNER (database schema used for OTM) schema, the status representing readiness for
loading has to be set on the order release and buy and sell shipment objects. This is handled in the following way:

1. Order Release: The status OR_HD_LOAD_STATUS has to be set to OR_READY_TO_LOAD. There

are two sub categories for this action:
a. Newly created orders: For orders that are newly created in OTM, the automation agent
PL_ORDER_RELEASE_CREATED sets the internal status of the order release to
OR_READY_TO_LOAD. The following action handles this process:

b. For order releases created or last updated before the first ETL process is run: For such orders, the
OR_HD_LOAD_STATUS has to be manually updated using CSVs. For this, go to Business
Process Automation -> Data Import/Export -> CSV Export. Here, use the where condition:

STATUS_TYPE_GID LIKE '%OR_HD_LOAD_STATUS' and STATUS_VALUE_GID LIKE

'%OR_NOT_READY_TO_LOAD'

Extract all the records obtained and save them as a CSV. Then manually replace all
status_value_gids having value ‘OR_NOT_READY_TO_LOAD’ to ‘OR_READY_TO_LOAD’. After
this go to Business Process Automation -> Integration -> Integration Manager -> Upload an
XML/CSV Transmission.

Here, upload the modified CSV with IU transaction code. This will update all order releases’
 statuses with OR_READY_TO_LOAD status and these orders will be picked up during the next
scheduled ETL run for transfer to FTI.
2. Shipments: For buy shipments the ETL transfer is handled in the following manner:
a. Newly created Buy Shipments: The agent PL_BUY_SHIPMENT_CREATED sets the internal
status of the newly created buy shipment to SHIPMENT_READY_TO_LOAD making it eligible for
the ETL transfer.

b. Newly Created Sell Shipments: The agent SELL_SHIP_CREATED_ACTIONS sets the internal
status of a newly created Sell Shipment to SHIPMENT_READY_TO_LOAD, making it eligible for
being picked up by the next ETL process for transfer to HDOWNER schema. The following action
handles this:

c. For old and existing shipments which have not been updated or created after the first ETL
scheduled run, similar to the procedure used for order releases, a fresh CSV with all the shipments
that are not ready to be loaded to HDOWNER are queried using the where clause:

STATUS_TYPE_GID LIKE '%SHIPMENT_HD_LOAD_STATUS' and STATUS_VALUE_GID LIKE

'%SHIPMENT_NOT_READY_TO_LOAD'

Similar to the case of order releases, these statuses are modified and uploaded to OTM.

3. Invoices and Bills: No additional actions need to be done for transferring the related invoices and Bills,
once the respective orders and shipments have been marked for and picked up by the transfer process and
they will be automatically picked up.
Setting up an ETL Batch Process:

For setting up an ETL transfer process, the user needs to log in using the DBA.ADMIN credentials and go to the
following path:

In case of running the ETL process right away:

Transportation Intelligence -> Process Management -> Run ETL

This will open the following screen:

Click on submit and the process starts executing.

In case of scheduling an ETL process to run at a later point of time:

Transportation Intelligence -> Process Management -> Recurring Processes. This opens the following screen:

Select the Run ETL Recurring process and click search. In the search results, click in Run ETL and in the following
screen, select the scheduling time and click on submit. This will schedule a timed ETL process:
Unloading OTM objects from FTI:

For unloading OTM objects from FTI when the corresponding OTM object is deleted, the following five automation
agents have been designed:

1. PL.ORDER_RELEASE_REMOVED_UN_HD: Uses the standard OTM action UNLOAD ORDER RELEASE

FROM HD
2. PL.BUY_SHIPMENT_REMOVED_UN_HD: Uses the standard OTM action UNLOAD SHIPMENT FROM HD
3. PL.SELL_SHIPMENT_REMOVED_UN_HD: Uses the standard OTM action UNLOAD SHIPMENT FROM
HD
4. PL.INVOICE_REMOVED_UN_HD: Uses the standard OTM action UNLOAD INVOICE FROM HD
5. PL.BILL_REMOVED_UN_HD: Uses the standard OTM action UNLOAD BILL FROM HD