Hierarchy

⤷

⤷

IMG Activity
ID | HRWPC_PCR_EFF_DATE | BAdI: Adjust Effective Date for Request Forms |
Transaction Code | S_AX8_68000141 | (empty) |
Created on | 20020117 | |
Customizing Attributes | HRWPC_PCR_EFF_DATE | BAdI: Adjust Effective Date for Request Forms |
Customizing Activity | HRWPC_PCR_EFF_DATE | BAdI: Adjust Effective Date for Request Forms |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | HRWPC_PCR_EFF_DATE |
This Business Add-In (BAdI) enables you to set the effective date in the form header of personnel change requests customer-specifically.
You have the following option:
- You can preset the effective date.
As standard, the system always uses the system date (SY-DATUM) as the initial value for the effective date. In that case managers must usually overwrite the date. If change requests are subject to general enterprise rules (for example change requests always become valid at the end of the next month or quarter), you can use this BAdI to preset the date.
Example
For example code, see the documentation for the method MANIPULATE_EFF_DATE.
Requirements
Standard settings
This BAdI is not implemented in the SAP standard. Unless you create an implementation, the system runs the standard code.
Recommendation
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:
- 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.
- Enter a short text for the implementation in the Short text for implementation field.
- 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.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- 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.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Further notes
InterfaceMethod: Adjust Effective Date in Change Request Forms.
Business Attributes
ASAP Roadmap ID | 262 | Technical and Graphical Settings |
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 | HRWPC_PCR_EFF_DATE | 0 | AXA0000002 | Business Package for Manager Self-Service (HR) |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030310 |
SAP Release Created in | 1999_1_46C |