If Winshuttle Function Module (WFM) is installed on the SAP system, you can attach documents to transactions for some t-codes that are recorded in Batch Input mode, Non-Batch with Controls mode, or Non-Batch without Controls mode. See below for a list of supported t-codes and the recording modes to use for them, as well as a list of the supported attachment file types.
If WFM is not installed on the SAP system, documents can be attached only to Transaction scripts that are recorded in GUI Scripting mode, and only the BDS attachment type is available.
Attach a document
- Click Add File Attachment Rows.
- Choose the method that you want to use. Winshuttle Studio v12 supports three ways to attach a document:
- GOS: Store the business document in an archival table, so that main tables are not affected by large attachments.
- DMS: Create an external document (URL). The attachment is stored on an external server.
- BDS: Create an attachment. This attachment option was offered in previous versions of Winshuttle Transaction.
Note: If WFM is not installed on the SAP system, only the BDS method is available.
- Map the field to the data file.
- Open File Explorer and locate the document that you want to attach.
- Copy the file path and file name.
- In Studio, click the Run tab.
- Paste the file path and name in the Location field.
Important: Upload speed depends on the network and on the SAP system.
Note: You can use "attach current file" for a document attachment, when the attachment location is defined inside the If condition for the script.
Note: To request an enhancement to incorporate new t-codes into Winshuttle Function Module, contact Support.
Add other document types
You can customize which document types you can attach.
- Open the ShuttleRule.xml file (in C:\Program Files\Winshuttle\STUDIO or in C:\Program Files (x86)\Winshuttle\STUDIO).
- Enter the MIME type for the document type that you want to add.
For example, to add .mht files, enter the following:
Note: You can use the Current File as a document attachment, when the attachment location is defined inside the If condition for the script.
The default maximum file size is set at 30 MB.
The tested maximum file size for attachments for web services is 20 MB.
You can change the maximum file size in the Studio Options box.
- Click File, and then click Options.
- Click the SAP Settings tab.
- Under Advanced, in the Document attachment limit (MB) box, type the maximum size for attached documents.
Note: For documents attached during AutoRun, the maximum file size must be changed on SAP Integration Server. For more information, see Add Attachment plugin properties.
Document attachment scenarios
Sales order and material processes in SAP often include the capability to attach and upload supporting documents along with the data upload. Depending on the transaction, you might want to attach and upload the following types of documents:
- Personnel (PA30): Social Security/national insurance paperwork, proof of residency or citizenship, work permits, passport scans, personnel photos, training certificates
- Sales Order: Faxed orders, PDF files, invoices, POs, purchase requisitions
- Material Master: Drawings
- BOMs: Drawings
- Customer: Credit reference, registration certificates
- Vendor: Credit reference, registration certificates
You can also attach the current document to use for the next script in a chain. For example, you can run an FB50 script to return document numbers and then link it to an FB03 script, with the data file as an attachment so that FB03 can use the document numbers and return the attachment and run logs to that data file.
Note: This is not available for scripts that use the data file type XML Form.
- Record and map the first script.
- Record the second script and map it to the data file that you used for the first script.
- Click Add File Attachment Rows, and click Use Current File.
- Save and close the second script.
- In the first script, click the Run tab, and then click Chain Scripts.
- Add the second script to the chain.
- Run the first script. Studio will automatically run the second script.
Note: The run logs from the second script will not be available in the Excel file that is attached to the SAP document.