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. The integration, using the time stamp, determines, by study, which is the latest file at the configured sFTP location.
3. The data is then imported into Clinical One Cloud Service. The manufacturing lot is created for a given kit type with the corresponding quantity, material number, and expiration date. The manufacturing lot is associated with the corresponding blinded lot.

   Note:

   If a manufacturing lot already exists, the information in Clinical One Cloud Service is updated as per the details in the stock report file that is being processed.
4. If a manufacturing lot exists in Clinical One Cloud Service but is missing in the stock report, the quantity for such lots is updated to zero. This ensures they are not available when a shipment request is generated.

Note:

The stock report file manages country associations only. 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.