Title
Ticket Transfer Report ROIJ_TICKET_TRANSFER

Caution
This report acts like an XPRA with new DB entries and should be usedonly by system administrators or people responsible for TSW functions.
As the ticket transactions and interfaces used with SAP Oil & Gas 4.6CService Pack 1 are still available and the Ticketing process iscontrolled by Customizing settings, it may not be necessary to run thisprogram. As a result of this, it is not delivered as an XPRA.
There is no authorization check included in XPRAs.
To avoid runtime problems, run the program in the background.

Purpose
As of SAP Oil & Gas 4.6C SP2, Trader's and Scheduler's Workbench (TSW)contains new tables to store QCI-relevant information.
Up until Service Pack 1 (SP 1),oil material data that was relevant tothe QCI was stored in ticket item table OIJ_EL_TICKET_I. Examples ofthis data include:
Test temperature
Test density
Material temperature
Test temperature unit of measure
Material temperature unit of measure
Additional units entered in the tickets were stored in tableOIJ_EL_TCKET_UOM.
This report reads all ticket items according to the ticket selection andcopies the QCI parameter data to the new table OIJ_EL_TKT_I_O1. This isdependant on the ticket Logic of the TSW movement scenarios.
The additional data from table OIJ_EL_TCKET_UOM is copied to tableOIJ_EL_TKT_I_O2 and filled with remaining units according to the ticketlogic.
The program provides a log and you can restart it. The package size forDB access is flexible (the default is 3000 entries for each DB cursorfetch).

Prerequisites
Ensure that TSW is active for SP2 and new CIP Functions are maintainedfor Ticketing (Define Junctions)

Selection
The program's selection screen allows you to restrict the data to beread or transferred by using the ticket key and status.

Example

Ticket Key Parameter
Depending on the use of ticket keys in your system (see number rangesetup of Number Range object in Customizing under Industry SolutionOil & Gas (Downstream) -> Trader's and Scheduler's Workbench (TSW) ->Tickets -> Define number ranges for tickets), you may not know howbest to use the ticket key parameter.
Example: You use interval "01" for pipeline tickets, the intervalsetting is from "1" to "100000000000".
The current number is "12345". If you want to transfer the pipelinetickets in two steps, run the program with ticket Key "1" to "6172" andthe second run with ticket key "6173" to "12345".

Parameter Package Size for DB Cursor
This parameter is defaulted to 3000.
If you are certain that, for example, most of your tickets do notcontain external QCI parameters such as test temperature and testdensity, or additional units were almost never used, you may increasethe parameter (to check this, use transaction SE16OIJ_EL_TCKET_UOM -> "Number of entries").

"Ticket Status" Selection Group 1)
Completely processed tickets are either deleted or archived. Given this,it does not make sense to transfer them to the new QCI tables. Youshould process only incomplete tickets with the new transaction. ->Choose Process incomplete tickets.
With SP2 installed, you should process incomplete tickets with the oldtransaction. Ensure in this case, that you post them completely beforeactivating the new CIP functions for Ticketing. You should be able todisplay all tickets (including QCI screen) in the new tickettransaction. -> Choose Process completed tickets.
With SP2 installed, you decide to handle all tickets (old, new, complete
, incomplete) with the new transaction -> Choose Process all tickets
.

"Log Display Options" Selection Group
If you want to see only those ticket items that were successfullytransferred, choose the Log Show Success parameter.
If you want the see only those ticket items that failed the transfer soyou can analyze the cause of failure, choose the Log Show Errorsparameter.
To display the whole log, choose the Log show all parameter.
Note: When you restart the program, you see a warning message fortickets that have already been transferred to the new tables.

Output
The output list is implemented as a Standard SAP Application Log andshows:

• Success messages for all transferred tickets (green LED @5B@)


• Warning messages (yellow LED @5D@) such as when you transfer obsolete
data

• Error message (red LED @5C@) when the data could not be transferred (for
example, if the QCI default data could not be found)