Reusable, Interfaced Component for File Attachment?

[mike_mcinerney]

GIVEN:

We are developing a multi-level-input, multil-level-approval form with a Web Dynpro for ABAP  front-end and a workflow back-end.  

The underlying form data is stored in z-tables, accessed by an ABAP object.   Creation of the form/workflow initialization is (portal based and/or) via direct call to the WD4A application URL.  Subsequent edits, approvals, etc are routed to appropriate parties and accessed via the UWL, where launching the item in the UWL brings up the WD4A form, populated with a combination of workflow container and z-table data.  The form is edited, rejected, approved, etc, and the data is saved to the data store and the current workitem is completed, allowing the workflow to proceed.

This is all working nicely.

NEED:

We have a requirement for the users to be able to attach supporting documentation to the form from the web dynPro.

Is there an already established WD component that I can use to provide this functionality? (We are not developing under a floor plan manager infrastructure.)

I’m hoping it may be as easy as attaching a new or existing (SWO1) object to the workflow and, on the WD side, setting up a component usage and binding in a couple of values (similar to using SALV_WD_TABLE).

THANKS:

...Mike

[Former Member · Accepted solution]

Check SALV_WD_TEST_FILE_UPLOAD.

It is basically File upload and then take the attachment get the Mimetype and use it accordingly.

Phani