Stock Report Integration

This integration maintains the study drug inventory in your Clinical One Cloud Service studies.

Table 2-24 Stock Report integration details

Specification	Details
Data flow	Inbound from SAP to Clinical One Cloud Service via Oracle sFTP
Frequency	Scheduled (configurable)
Data type	Unblinded and cumulative

Integration workflow

1. SAP generates a stock report file and posts it on the Oracle sFTP server at a configured location.
2. Using the time stamp, the integration determines the latest file for each study at the configured sFTP location.
3. The data is then imported into Clinical One Cloud Service. The integration creates or updates the manufacturing lot and associates it with the applicable kit type, depot, and country. The integration includes the corresponding quantity, material number, expiration date, and blinded lot.

   Note:

   The stock report file manages country associations. Do Not Count (DNC) and Do Not Ship (DNS) values are not imported from the stock report file. Configure these values manually in Clinical One Cloud Service. For more information about configuring DNC and DNS values, see Manage expiration dates with lots.
4. If an inventory record for a manufacturing lot exists in Clinical One Cloud Service but is missing from the stock report file, the quantity for that record is updated to zero. This ensures the inventory is not available when a shipment request is generated.

5. After successfully processing a stock report file, the integration can be configured to move the file from the inbound Oracle sFTP folder to a processed folder.

   By default, successfully processed stock report files remain in the inbound Oracle sFTP folder. If SAP does not post a newer file, a subsequent scheduled run can reprocess the prior file and replace current inventory values in Clinical One Cloud Service with stale values. This can result in inaccurate inventory availability for supply, depot, and site decisions.