Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
CO (Application Component) Controlling⤷
QISR (Package) Internal Service Requests
Basic Data
| Data Element | QISR_TEMPLATE |
| Short Description | Form for ISR Scenario |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table |
Further Characteristics
| Search Help: Name | HFPWBFORM | |
| Search Help: Parameters | NAME | |
| Parameter ID | FPWBFORM | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Form |
| Medium | 15 | Form |
| Long | 20 | Form |
| Heading | 55 | Form |
Documentation
Definition
Adobe PDF Form for ISR Scenario
Use
You can generate a form. If you do not enter a name for the form, one will be created automatically when you generate the form. The name will be ISR_FORM_XXXX (XXXX = technical name of scenario). You can generate a form using a template. You can use either a standard SAP form or a form from another scenario.
During generation, the characteristics of the scenario are automatically transferred to the interface and the context of the form. You can switch to the Form Builder and change the layout. If you define new fields in the layout, you can transfer these automatically as characteristics to scenario Customizing when you exit the Form Builder. When you do this, the data binding of the new fields is also automatically stored in the layout.
For more information about the Form Builder, choose Help -> Application Help in the Form Builder.
For more information about the use of Adobe PDF forms in ISR scenarios, see the ISR cookbook on the SAP Service Marketplace under service.sap.com/isr.
Dependencies
Example
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 500 |
