Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
CA-GTF-DOB (Application Component) Document Builder⤷
/IPRO/PROGS (Package) programs
IMG Activity
| ID | /IPRO/NAME_VALIDATOR | Validate Element or Variable Names |
| Transaction Code | /IPRO/67000041 | (empty) |
| Created on | 20041112 | |
| Customizing Attributes | /IPRO/NAME_VALIDATOR | Validate Element or Variable Names |
| Customizing Activity | /IPRO/NAME_VALIDATOR | Validate Element or Variable Names |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /IPRO/NAME_VALIDATOR |
Use
Implement this Business Add-In to determine how an element or variable name is validated.
The Business Add-In consists of the method described below, which can be used instead of the standard algorithm.
VALIDATE_NAME
The following import parameters are provided:
- IV_NAME
Name to be validated. - IV_TYPE
Type of the name. For example, 'V' for variable name (default) and 'E' for element name.
The following return parameters must be provided by your coding:
RV_CODE
Indicates whether the name is valid ('X') or not ('').
Requirements
Standard settings
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.
If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:
1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
The screen for creating BAdI implementations is now displayed.
2. Enter a short text for the implementation in the Short text for implementation field.
3. From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
4. Save your entries, and assign the implementation to a development class.
5. Place the cursor on the method, and double-click to enter method processing.
6. Enter the coding for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
7. Save and implement your coding. Return to the Edit Implementation screen.
8. Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
9. Choose Activate.
The coding you stored in the methods will be run when the application program is executed.
Example
The default implementation logic is that a valid name should start with a letter or "_" and does not contain space, quote, slash, equal and double quote characters.
Additional hints
For more information on using Business Add-Ins, see the SAP Library under Basis Components -> ABAP Workbench (BC-DWB) -> Changing the SAP Standard (BC) -> Business Add-Ins.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | /IPRO/NAME_VALIDATOR | 0 | HLB0009110 | Cross-Application Components |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20050119 |
| SAP Release Created in | 100 |
