Environment
Novell Identity Manager 3.0.x SAP HR Driver
Novell Identity Manager 3.5 SAP HR Driver
Novell Identity Manager 3.5.1 SAP HR Driver
Novell Identity Manager 3.6 SAP HR Driver
Novell Identity Manager 3.6.1 SAP HR Driver
Situation
When deploying the Novell Identity Manager SAP HR driver, it is frequently necessary to extend the driver to support custom SAP Infotypes. This is done by modifying the HRMD_A*.meta file, where * represents a 2 digit number.
The SAP HR driver comes with two sample files, HRMD_A03.meta and HRMD_A05.meta . For example, we can copy the HRMD_A05.meta file to a HRMD_A06.meta file. Then perform our modifications on the HRMD_A06.meta file and have the driver use it.
The SAP HR driver comes with two sample files, HRMD_A03.meta and HRMD_A05.meta . For example, we can copy the HRMD_A05.meta file to a HRMD_A06.meta file. Then perform our modifications on the HRMD_A06.meta file and have the driver use it.
Resolution
Here are a few lines from the file, followed by an explanation of their structure:
SEGMENT:P0000:E1P0000:
P0000:PERNR:0:8
P0000:INFTY:8:4
P0000:SUBTY:12:4
The first line defines the infotype boundary. It's parts are as follows:
SEGMENT - Delimiter used to define the segment infotype boundary
P0000 - Segment infotype code
E1P0000 - Full infotype code as shown in SAP, not used by the driver
Following the segment lines are lines that define the attributes of the segment infotype.
SEGMENT:P0000:E1P0000:
P0000:PERNR:0:8
P0000:INFTY:8:4
P0000:SUBTY:12:4
The first line defines the infotype boundary. It's parts are as follows:
SEGMENT - Delimiter used to define the segment infotype boundary
P0000 - Segment infotype code
E1P0000 - Full infotype code as shown in SAP, not used by the driver
Following the segment lines are lines that define the attributes of the segment infotype.
So for the second line:
P0000 - Segment infotype
PERNR - Attribute name in SAP HR
0 - Character (not byte) offset in the iDoc where this attribute starts
8 - Size of the attribute in the iDoc, in characters
Third line:
P0000 - Segment infotype
INFTY - Attribute name in SAP HR
8 - Character (not byte) offset in the iDoc where this attribute starts
4 - Size of the attribute in the iDoc, in characters
Forth line:
P0000 - Segment infotype
SUBTY - Attribute name in SAP HR
12 - Character (not byte) offset in the iDoc where this attribute starts
4 - Size of the attribute in the iDoc, in characters
So to add a custom infotype, first you obtain the segment infotype code and its attribute list with their names and sizes in the iDoc from SAP HR. Then add a SEGMENT line with the custom infotype followed by one line for each attribute, in the order they appear in the iDoc, as per the example shown above.
Remember that attribute offsets start counting from 0.
P0000 - Segment infotype
PERNR - Attribute name in SAP HR
0 - Character (not byte) offset in the iDoc where this attribute starts
8 - Size of the attribute in the iDoc, in characters
Third line:
P0000 - Segment infotype
INFTY - Attribute name in SAP HR
8 - Character (not byte) offset in the iDoc where this attribute starts
4 - Size of the attribute in the iDoc, in characters
Forth line:
P0000 - Segment infotype
SUBTY - Attribute name in SAP HR
12 - Character (not byte) offset in the iDoc where this attribute starts
4 - Size of the attribute in the iDoc, in characters
So to add a custom infotype, first you obtain the segment infotype code and its attribute list with their names and sizes in the iDoc from SAP HR. Then add a SEGMENT line with the custom infotype followed by one line for each attribute, in the order they appear in the iDoc, as per the example shown above.
Remember that attribute offsets start counting from 0.
Additional Information
The first 63 characters in an iDoc file are header data fields, so the infotypes and their data comes only after that.
The driver's Schema mapping policy uses a slightly different format than the HRMD_A*.meta files, using 5 fields instead of 4. The driver documentation has an explanation on the file's format that can be found at https://www.novell.com/documentation/idm36drivers/sap_hr/data/abbe4cv.html .
The driver's Schema mapping policy uses a slightly different format than the HRMD_A*.meta files, using 5 fields instead of 4. The driver documentation has an explanation on the file's format that can be found at https://www.novell.com/documentation/idm36drivers/sap_hr/data/abbe4cv.html .