Hierarchy
CPRXRPM (Software Component) SAP Portfolio and Project Management 6.0⤷
PPM-PRO (Application Component) Project Management⤷
DEVELOPMENT_PROJECTS_CUSTOMIZE (Package) General Customizing for Project Management
IMG Activity
| ID | CPRO_PRP_BADIALE | BAdI: Customer-Defined Inbound Processing |
| Transaction Code | S_APL_52000045 | (empty) |
| Created on | 20020809 | |
| Customizing Attributes | CPRO_PRP_BADIALE | BAdI: Customer-Defined Inbound Processing |
| Customizing Activity | CPRO_PRP_BADIALE | BAdI: Customer-Defined Inbound Processing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HRALE00SPLIT_INBOUND |
HRALE00SPLIT_INBOUND
SAP-internal inbound processing for HR master data:
The system determines which HR objects should be removed from standard processing because no data structures exist for them in the receiving system. Irrespective of the type of receiving system, you can further process these HR objects.
For instance, receiving system CRM or EBP: personal data must be represented by an own data model because database tables for personal data are not available in these systems. Furthermore, a business partner must be created and be included in the organizational structure analogous to the person in HR.
Two methods are available:
- select_objects can be used to select objects for which inbound processing is performed in a way that deviates from the standard system. The objects are selected in accordance with the plan version, object type, and object ID parameters.
- process_selected_objects can be used to write the objects selected this way.
Execution
When the select_objects method is used, the select_plvar, select_otype, and select_objid selection tables are filled. The lines in these tables of the rnge_plvar, ... type are structures with sign, option, low, and high fields. For more information, see the section on selection tables in the SAP Library.
When the process_selected_objects method is used, the system writes the data filtered from the IDoc in accordance with the criteria defined in select_objects. The data is transferred to four tables:
t_plogi
The E1PLOGI segments are collected in this table.
t_porig
The E1PORIG segments are collected in this table.
t_pityp
The E1PITYP segments are collected in this table.
t_pnnnn
The E1Pnnnn and E1PADnn segments are collected in this table. The IDoc data is copied to the sdata field of the line structure. The application interprets the data. If an E1Qnnnn segment exists for infotypes, the data from this segment is written to the sdata field with an offset of 1000. The structures subordinate to the segments are stored in DDIC using the same name.
The method is only called if the tables are not empty.
For information on the structure of IDocs of message type HRMD_A, see note 134085 in the Online Service System.
Error handling
Errors that occur when process_selected_objects is processed must be returned to the t_errors table so that IDoc status records can be generated. The line type of this table is hrale_err. The fields in this structure must be filled as follows:
repid
Name of implementation.
routid
Name of subroutine in which the error occurred.
segfld
Name of field that causes the error.
segnum
Number of the E1PLOGI segment that belongs to the data record that causes the error. This number is included in the segnum component of the line in the t_plogi table determined on the basis of the plan version, object type, and object ID.
msgid
Message class.
msgty
Message type. A message of type 'W' or 'I' results in a record with status 52 (incompletely written). Other types result in a record with status 51 (not written). Once inbound processing is complete, the IDoc is assigned the minimal status resulting from all of the errors that occurred during processing.
msgno
Message number.
msgv1...msgv4
Message variables.
Example
Organizational units 666 to 999 must not be written. If an IDoc contains such an object, the IDoc is assigned status 52 (incompletely written) if a serious error did not occur when the remaining records were processed.
In select_objects, the select_otype table is filled with the select_otype-sign = 'I' select_otype-option = 'EQ' select_otype-low = 'O' line. The select_objid-sign = 'I' select_objid-option = 'BT' select_objid-low = '666' and select_objid-high = '999' line is written in the select_objid table.
In process_selected_objects, the required error message of type 'W' or 'I' is returned to the t_errors table.
Requirements
Standard settings
Recommendation
Activities
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 | HRALE00SPLIT_INBOUND | 0 | HLA0009700 O | |
| SIMG | HRALE00SPLIT_INBOUND | 1 | HLA0009704 O | |
| SIMG | HRALE00SPLIT_INBOUND | 2 | HLA0009706 O | |
| SIMG | HRALE00SPLIT_INBOUND | 3 | HLA0009703 | Training and Event Management |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20020809 |
| SAP Release Created in | 200 |
