The form is automatically e-mailed to the responsible sales representative before his or her scheduled customer visit. The sales representative saves the PDF to the hard drive on his or her laptop for later use.

 

Upon arriving at customer side, the salesperson and the customer work together to complete the form.

 

While still at the customer's location, the salesperson prints out the completed form for the customer's records using the print capabilities of Adobe Reader.

 

Then the salesperson forwards the completed form to SAP CRM, either by using the e-mail Submit button in the form or by uploading the form to the corresponding site in the internal company portal upon returning to the office.

 

SAP CRM receives the data entered by the sales representative, processes it, and automatically triggers the next step in the business process.

 

 

Possible actions during forms processes:

• Forms are created on the application side.
• Forms can be visualized, printed, downloaded, archived, and sent via e-mail.
• Forms can then be uploaded and parsed, and the data can be extracted.
• The forms data can be saved on the database.

 

This training course treats the main form processing steps.

 

Training course example 1 (the offline scenario):

1. A PDF print form is created.
2. The form is displayed.
3. The print program will be extended by the download and e-mail functionality.
4. Next, the form is edited and missing fields are filled.
5. Afterward, the changed form can be sent again via the e-mail button or simply uploaded to the application.
6. Finally, the form data in XML notation is parsed, extracted, and saved back to the database.

 

 

Training course example 2 (the online scenario):

1. A Web Dynpro application template has to be extended. It should carry an online PDF form for printing and editing data online!
2. First, the Web Dynpro application template needs to be analyzed.
3. On the second view of the Web Dynpro application an Interactive Form UI element is included.
4. The mapping to the Web Dynpro context is established and the new form is generated via forward navigation.
5. Finally, the form is part of the whole Web Dynpro application.
6. It is embedded in a view, and its fields can be edited just like the the other Web Dynpro fields.