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/GET_RGSET | Set Up Regulation Sets per Group |
| Transaction Code | /IPRO/67000023 | (empty) |
| Created on | 20040603 | |
| Customizing Attributes | /IPRO/GET_RGSET | Set Up Regulation Sets per Group |
| Customizing Activity | /IPRO/RGSET_DEF | Get regset |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /IPRO/RGSET_DEF |
Use
Implement this Business Add-In to determine a different collection of regulation sets used for creating SAP Document Builder documents.
The Business Add-In consists of the method described below, which can be used instead of the standard algorithm.
EDIT_DOC_REGSETS
The following import parameters are provided:
- PIS_DOCMNT
Structure containing document header data. - PIV_EFFT_DTE
The effective date of the document. - PIO_REGSET
An object that implements the /IPRO/IF_REGSET interface. This interface contains two methods: a method to identify available regulation sets (regsets) in the system, and a method to retrieve details for a selected regulation set.
The following change parameters can be edited:
PCT_REGSETS
On input, this internal table contains details on the default set of regulations that will be used to create SAP Document Builder documents. This set can be edited in your code. On output, this internal table contains the edited (or actual) set of regulation sets that will be used create SAP Document Builder documents.
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.
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 |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20040727 |
| SAP Release Created in | 100 |
