IBM Support

Interop agent not picking up records from YFS_EXPORT to create files for upload

Troubleshooting


Problem

Interop agent not picking up records from YFS_EXPORT to create files for upload

Symptom

PART: Agents 4.0 SP3 Platform
OS: All
DATABASE: Oracle 8.1.7

Interop agent not picking up records from YFS_EXPORT to create files for upload

Cause

Resolving The Problem

Shipment Confirmations and Inventory changes in DCS are to be uploaded to Yantra order management system and back to the ERP system. Shipment Confirmation data is published in the YFS_EXPORT table in XML format. The unprocessed data is picked up by the yfsexport class, merged with an xsl and the flat file output is saved in the /mnt/hercules/exports/wms/transout/output directory. PO receipts are equivalent to inventory change upload.

Steps required are as folows -
I.A.1.i. Shipment Confirmation and Inventory Change Upload steps
Execute the intbu101 agent in WMS. This will pick up new orders in the shipped status and insert them into the INFC_UPLD_TAB_1 table. The INTERFACE_TYPE for shipment records are ?PCKU?.
Execute the intbu091 agent in WMS. This will pick up new inventory changes in WMS and insert them into the INFC_UPLD_TAB_1 table. The INTERFACE_TYPE for inventory change records are ?STKU?.
Execute the yfs.agent.wmsshipconfirm agent in Platform. This will pick unprocessed shipment records from INFC_UPLD_TAB_1 table and confirm the corresponding shipments in the platform. The shipment confirmation in platform will also trigger the system to publish an XML into the YFS_EXPORT table with API_NAME=? SHIPMENT_UPLOAD? and status=?00?.
( This is achieved by the java call extension which is executed on ship confirmation -
com.scansource.yantraimpl.eventhandlers.SCEventsShipment(SSDBCommSystem,SSD BInterfaceSystem )

Execute the yfs.agent.wmsinventory agent in Platform. This will pick unprocessed inventory change records from INFC_UPLD_TAB_1 table and confirm the corresponding inventory picture in the platform. The inventory change in platform will also trigger the system to publish an XML into the YFS_EXPORT table with API_NAME=? INTY_CHANGE? and status=?00?.
( This is achieved by the java call extension which is executed on ship confirmation -
com.scansource.yantraimpl.eventhandlers.SCEventsInventoryChange(SSDBCommSys tem,SSDBInterfaceSystem)

Execute the yfsexport class on the platform server. This pick?s up unprocessed Shipment and Inventory change XML from the YFS_EXPORT table, merges them with the appropriate XSLT file and inserts the flat file output to the /mnt/hercules/exports/wms/transout/output directory. Each record is inserted into an indivitual file.
Found in Section IILD.2 of the doc the following -
I.A.1 ScanSource Custom Agents
run_facts_export.sh - This script executes the yfsexport.class. The application server is mapped to /mnt/hercules/exports/wms/transout/output. This agent picks up shipment and inventory change records from the YFS_EXPORT table merges them with the appropriate xsl and saves the output file in the mapped output direcorty. FACTS will pick up these records and process them
there were no agents running and the nightly cron had been stopped.
Asked him to submit the run_facts_export.sh and check a count of unprocessed records in the YFS_EXPORT table . The count began to go down as the agent worked on the records and picked them up.

[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

PRI49156

Product Synonym

[<p><b>]Fact[</b><p>];

Document Information

Modified date:
16 June 2018

UID

swg21533637