1. Home
  2. /
  3. V12 Documentation
  4. /
  5. User Guides
  6. /
  7. Data Interface

Data Interface

Data interface

ONIX interface

Incoming ONIX data can be imported into IP1 to update product data or create new products on approval. Similarly outgoing data can be generated for specific products and stored as XML files and pushed to customers as required.

ONIX data can be exported to XML files from IP1 either manually or based on an interface trigger controlled by the user or scheduled to run on a pre-determined frequency which can be on an hourly/daily basis or as required by the user.

 ONIX interface maintenance

ONIX import
LOB interface LOB interface maintenance

LOB entity maintenance

LOB property maintenance
DI interface – management DI interface maintenance

Adobe print batches
DI interface – outbound data Outbound MEDIUS invoice payment information
DI interface – digital sales reporting (DSR)

IP1 uses book industry standard Digital Sales Report (DSR) format as the standard sales order interface for all incoming sales data. Incoming sales data from different sources will be processed by IP1 to generate sales transactions, update sales information and generate debtor transactions. The generated transactions in IP1 from the DSR sales data interface will be used in the sales analysis, product profitability, and the processing of the payment by the online stores to the publishers. The data will also be used in the generation of the royalty earnings and payment.

IP1 can also use the same interface to handle transaction types that are not related to online stores e.g. Consignment Sales and Distributor Sales.

 Process flow – DSR

  1. An Excel template (DSO415.xlsx) with all the relevant system fields that are required in the processing of the interface file is provided. This template and Excel date file must exist in the relevant system folder.
  2. Flag in the Excel file the relevant columns that relate to the system fields.
  3. Run Sales Upload program (DSO415).
  4. The system will process the Excel input and generate AR, AP and G/L interface files.
  5. Generated AR and AP/GL interface files can be enquired on and validated before it is posted. (DSW070/AGW005).
  6. There are 4 different sales report types as listed below. Each of these types will have mandatory and optional field requirement. Depending on the report type, the back end process can be different when the transactions are posted to IP1.
    1. Online sales – this is a charge only invoice since the products have already been delivered and there is no need to update stocks in the warehouse.
    2. Consignment sales – this is an already delivered sale that requires decrementing of stock in the consignment warehouse.
    3. Distributor sales – this is an already delivered sale that requires updating of stock in the distributor specific warehouse.
    4. POD charges – this will generate an AP invoice to the POD supplier for the print and customer delivery service.
DI interface – AP & GL processing Work with AP/GL interface

Subledger posting to AP/GL

Data queue maintenance

Data queue must be setup and activated for the interface trigger program to export delta changes from IP1 to external system.

  1. Select menu option DI Interface Data Queue from Other Options> Data Interfaces> DI: Interface> Interface Management menu. XAW000 Work with Data Queues – Selection panel appears.
  2. Click Add to add the data queue. XAW000 Work with Data Queues panel appears.
Field Description
Data Queue Name for the data queue.
Description Brief description of the data queue.
Function Function group is ‘DILOPT’ as setup in system defined control ********/DQ-GRP for outbound database trigger.
Activation 0 = Inactive – Automatic interface updates will not occur.

1 = Manual – to be started manually for automatic interface updates. With manual setup you will need to manually access the Data queue and activate the processor.

2 = Auto –  EOD will check and stop the data queue on start of EOD and restart it when EOD is finished
Program Interface trigger program for data queue (DIO520A).
  1. Enter the above information and click OK to create the data queue.
  2. Select the newly created data queue and click function Create queue to initialise/setup the queue and all the necessary components. Create queue function must be used on newly created data queues. When this function is activated you will see the new data queue on the selection list.
  3. Select the data queue and activate it.

Database trigger management

The triggers setup for automatic interface (TMSDI/LOB-TRIG) can be turned on/off as required. For automatic interface on record change ensure the triggers are turned on.

  1. Select menu option DI Interface Database Trigger from Other Options> Data Interfaces> DI: Interface> Interface Management menu. DIO500 Database Trigger Management panel appears.

  1. Select to add all triggers to start the trigger program.

Background job management

This program is used to manage the background jobs, stock replenishments, interface with 3rd party software and deal with suspended web orders. It is possible to run or hold these jobs simultaneously or each job can be dealt with individually as and when required.

The panel will display current job status and data queue library the status applies to. The status can be 1=Run or 2=Hold. Jobs managed by this program are defined in the control file TMSWH/WI-QUEUE with the initial value set up. Refer to the Cross Applications User Manual – WIM500 Background Job Manager document for details on this process.

Print Friendly, PDF & Email