Manual Data Upload 
You need to upload data manually in the following cases:
You want to upload company-internal data from an ERP system like SAP ERP
The folder or Persistent Staging Area (PSA) scanner fails
You want to do a test upload for data from a new DataSource, such as a new retailer
SAP NetWeaver Business Warehouse (SAP NetWeaver BW) allows you to upload data by executing the appropriate InfoPackage manually.
Prerequisites
You have configured the following:
An active data delivery agreement
You may wish to define a separate data delivery agreement for each individual data set: one agreement for product, one agreement for location, and one for sales data.
You may also reuse an existing data delivery agreement.
The process scheduler job
Ensure it has the status In Process so that subsequent steps can be triggered automatically by the process scheduler.
The process definition
Ensure it has a step with a process chain assigned for transferring data from the Acquisition DataStore object (DSO) to the Propagation DSO
The step definition
You must assign the step to an upload stage for manual uploads. Ensure you select the correct upload stage setting, as this setting determines which steps should and should not be instantiated in the manual upload.
If you upload data by manually triggering a process chain and you want the subsequent steps to be triggered automatically by the process flow control (PFC), you must assign the process type /DDF/STATU at the end of the process chain.
If you want to use the same data delivery agreement for a manual upload as you have used for an automatic upload with the folder scanner, you have to define upload stages in Customizing.
Procedure
Log on to SAP NetWeaver BW Data Warehousing Workbench (transaction RSPC) and navigate to the appropriate InfoPackage.
Trigger the data upload by doing one of the following:
Execute the InfoPackage to trigger the data upload to the relevant PSA.
If you upload a file, you must include the file name in the InfoPackage file name routine.
If you upload company-internal data from SAP ERP, you use an SAP ERP DataSource.
The PSA gets the relevant data delivery agreement from the file or SAP ERP.
Execute the Data Transfer Process (DTP) to do one of the following:
Bring the data from a PSA request to the Acquisition DSO
Bring the data from any DSO to the Acquisition DSO
Execute the Process Chain that brings the data to the Acquisition DSO.
The process chain must have the process type /DDF/STATU at the end of it.
A delivery ID and process ID are created.
An additional step is created with step number 000000 and initial status Manual.
This status is for the step only and is not propagated. While the step has the status Manual, you can find it in the process monitor UI under the status category Running for the related process.
If you did the manual upload without a process chain, then this step has neither a process chain nor a process chain log ID. You must set the status manually to Completed, as there is no PFC interaction.
If you used a process chain in the manual upload, then this step is instantiated with a process chain and a process chain log ID. The process type /DDF/STATU sets the step status to Completed.
Subsequent steps are created.
Using the delivery and process created in the previous step 4, the subsequent steps, which are assigned to upload stages other than Data Acquisition, are created with the status Ready. The PFC executes the subsequent steps once the additional step (with step number 000000 and initial status Manual) has the status Completed.
Check in the Process Monitor UI whether the upload was successful or not.
Example
If you want to use the same data delivery agreement for a manual upload as you have used for an automatic upload with the folder scanner, you have to define upload stages in Customizing as described below.
Step Attribute |
Value |
|---|---|
Agreement Type |
Retailer Data |
Upload Method |
Automatic Upload With Folder Scanner |
Data Format |
Comma-Separated Values |
The process definition has the following steps assigned:
PRODUCT_FILE with upload stage Data Acquisition
LOCATION_FILE with upload stage Data Acquisition
PRODUCT_STAGE with upload stage Quality Validation
LOCATION_STAGE with upload stage Data Propagation
You decide you want to upload the product file manually and you can use the same data delivery agreement Customizing for this.
The system creates an additional step with the step number 000000 with status Manual for the manual upload and instances for the steps that are not relevant for data acquisition (PRODUCT_STAGE and LOCATION_STAGE).
The system does not create an instance for the step LOCATION_FILE because you want to upload only the PRODUCT_FILE in the manual upload.
Although no location data is uploaded, the step LOCATION_STAGE is nevertheless executed This does not cause any conflicts because the Acquisition DataStore object does not contain any location data with the delivery ID that was created from the manual upload.