Hierarchy

⤷

⤷

IMG Activity
ID | HR_PBS_00_WB_RPL | Example Implementation of Customer-Specific Business Scenario |
Transaction Code | S_L7D_24000130 | (empty) |
Created on | 20051214 | |
Customizing Attributes | HR_PBS_00_WB_RPL | Example Implementation of Customer-Specific Business Scenario |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | HR_PBS_00_WB_RPL |
Use
When you edit process scenarios, you have to perform the numerous checks and actions that the BAdI implementation HRPBS00I0716, which belongs to the business scenario, automatically performs for standard business scenarios. These include, for example, consistency checks when deleting or assigning a unique application reference number (field P0716- APRFNR) when creating new processes.
In the standard SAP system, you can select one of the three subtypes in infotype 0716 as a business scenario:
- DEAU Information on benefits
- DEDU Civil servant unable to work
- DEPA Benefits administration
If you want to create customer-specific business scenarios in addition to these business scenarios, you can use the BAdI for Infotype 0716 (HRPBS00I0716) in the next IMG activity BAdI: Activate Customer-Specific Business Scenario for PAdm. Since you must always implement this BAdI, it is imperative that you also implement it for new business scenarios. Here, you do not have to copy the standard source code to the BAdI. Instead, you can implement a call for the standard source code (see below).
Example
Implementing a customer-specific business scenario:
To create a customer-specific business scenario (subtype for infotype 0716), you must create your own implementation of the BAdI HRPBS00I0716.
For more information, read the documentation for the IMG activity BAdI: Activate Customer-Specific Business Scenario for PAdm.
For the two methods contained there, you can copy the following source code into your implementation:
- Method BEFORE_OUTPUT "Infotype maintenance: Call with event PBO"
METHOD if_ex_hrpbs00i0716~before_output.
IF ar_standard IS INITIAL.
CREATE OBJECT ar_standard.
ENDIF.
CALL METHOD ar_standard->if_ex_hrpbs00i0716~before_output
EXPORTING
flt_val = flt_val
ipsyst = ipsyst
mode = mode
CHANGING
p0716 = p0716.
ENDMETHOD.
- Method AFTER_INPUT "Infotype maintenance: Call with event PAI"
METHOD if_ex_hrpbs00i0716~after_input.
IF ar_standard IS INITIAL.
CREATE OBJECT ar_standard.
ENDIF.
CALL METHOD ar_standard->if_ex_hrpbs00i0716~after_input
EXPORTING
flt_val = flt_val
old_innnn = old_innnn
ipsyst = ipsyst
mode = mode
fcode = fcode
CHANGING
p0716 = p0716
EXCEPTIONS
error_with_message = 1.
* OTHERS = 2
.
CASE sy-subrc.
WHEN 0.
WHEN 1.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
RAISING error_with_message.
ENDCASE.
ENDMETHOD.
You must also create an attribute in your customer class:
AR_STANDARD Static Attribute Private Type Ref To CL_IM_HRDEPBSVA_VADM
You must enter your customer subtype as a filter value for the implementation.
Since this implementation ensures that the source code called for your customer subtypes is the same source code called for the standard SAP subtypes, you will not experience any problems if you adjust the standard SAP source code in the future.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
HR_PBS_00_WB_RPL | DE | Germany |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | HR_PBS_00_WB_RPL | 0 | L6B0000001 | International Functions for the Public Sector |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20051214 |
SAP Release Created in |