SAP ABAP IMG Activity HRALE00ORIGSYSTEM (BAdI: Fine Tuning of Original System Mechanism)
Hierarchy
☛ SAP_HRGXX (Software Component) Sub component SAP_HRGXX of SAP_HR
   ⤷ CA-ESS (Application Component) Employee Self-Service
     ⤷ PWWW (Package) HR: Internet Services and BAPIs
IMG Activity
ID HRALE00ORIGSYSTEM BAdI: Fine Tuning of Original System Mechanism  
Transaction Code S_PH0_48000531   (empty) 
Created on 20000204    
Customizing Attributes HRALE00ORIGSYSTEM   Attributes for HRALE00ORIGSYSTEM 
Customizing Activity HRALE00ORIGSYSTEM   Maintenance Objects for HRALE00ORIGSYSTEM 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRALE00ORIGSYSTEM    

HRALE00ORIGSYSTEM

Business Add-In for Original System Mechanism

The following methods are available:

  • otype_has_original enables you to determine the object types for which the original system mechanism is active.
  • write_chgptr_for_replica enables you to determine that change pointers are also written for individual infotypes of replications.
  • save_data_for_original allows originals to be overwritten in ALE inbound processing.

Execution

The otype_has_original method includes the otypes_with_orig parameter, to which a table is written for object types supported in the standard system by the original system mechanism. This table can be manipulated as required. Note, however, that this does not override the status of the ALE-REPLI and ALE-REPPA switches in T77S0. This means, for example, that even if object type 'P' has been added, the original system mechanism is not active for employees unless ALE-REPPA has been set.

If the WRITE_CHANGEPOINTER exception is triggered in the write_chgptr_for_replica method, change pointers are written for the object determined by the plvar, otype, and objid parameters and for infotype infty, subtype subty.
The supplied example coding facilitates change pointers to replicated positions (object type 'S') for infotype 1007 Vacancy. This method does not affect objects that exist as originals, or for which the original system mechanism is inactive.

In the standard system, objects that exist as originals in the current system are skipped in ALE inbound processing. This is documented by an appropriate IDoc status record. If the DO_NOT_SAVE_NO_MESSAGE exception is triggered in the save_data_for_original method, status record documentation is not generated. If the SAVE_OBJECT exception is triggered, the data of the current IDoc is saved for the current object, even though the object exists as an original. The IDoc data is written to tables t_hrobjorig, t_hrobjinfty, and t_hrobjsdata, which contain IDoc segments E1PORIG, E1PITYP, and E1Pnnnn. In ALE inbound processing, the method is accessed for an object determined by the plvar, otype, and objid parameters if the object exists as an original and is not locked. For safety's sake, you should only use the option of reading originals in update mode. This is the case if the value of the opera parameter is 'U'. If a status message needs to be created to record the fact that standard system behavior has been overridden, a corresponding line must be appended to transferred table t_protocol. To create a status 52 record, message type 'W' or 'I' must be selected. The method is only accessed for objects that exist as originals. Changes to specified IDoc data only affect current inbound processing. Apart from any status messages that may have been generated, the IDoc on the database remains unchanged.
The supplied example coding ensures that infotype 1007 Vacancy is written for positions that exist as originals (object type 'S'). If the IDoc contains a record of infotype 1007, all other records are removed from the IDoc data and the SAVE_OBJECT exception is triggered. This is recorded in the IDoc.

Example

In the 'Distributed HR Master Data' scenario, infotype 1007 Vacancy is maintained for positions in operational systems, even though they include the positions as replications. If the example coding for the write_chgptr_for_replica method is written to the operational systems, change pointers are written if a vacancy is created or delimited. To facilitate reading the changes to the corporate system, the example coding of the save_data_for_original method must be written to the corporate system.

Requirements

Standard settings

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:

  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 code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. 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 code you stored in the method will be run when the application program is executed.

Further notes

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 HRALE00ORIGSYSTEM 0 HLA0009700 O  
SIMG HRALE00ORIGSYSTEM 1 HLA0009704 O  
SIMG HRALE00ORIGSYSTEM 2 HLA0009706 O  
SIMG HRALE00ORIGSYSTEM 3 HLA0009703 Training and Event Management 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20011211 
SAP Release Created in 46C