It is possible, generally for employees in the USA & Canada, to come across an inconsistency in Infotype 21 when recording the Spouse’s gender.
If the Spouse’s gender is captured as „Undeclared“ in the full screen, then in the Overview Screen it is shown incorrectly as Female if the employee is Male, or vice versa.
This seems to be a SAP error. The US config calls screen 2010 for the Detailed view and screen 3010 for the Overview list. However, the list screen 3010 is only processing the international output module P0021 without the bespoke US modules from module pool include MP002120 in the flow logic; and it is here that we find the piece of logic that causes the inconsistency.
This code automatically changes the gender of the spouse to the opposite sex of the employee, if the gender of the spouse is not declared. („1“ is the standard subtype for Spouse.)
For the full Detailed view screen (2010), for the US a special US output module P0021_US from module pool include MP00212U is processed before and after the international one:
This module is specifically designed to prevent the international part to switch to the opposite sex, by changing FASEX (spouse gender) to „3“, rather space. You can check the coding – it’s very obvious.
We haven’t looked at it in detail, but it may be enough to call the module pool P0021_US in screen 3010 in the same way as in screen 2010 – or it may require slight coding changes. In any case, this would be a modification. So, if this isn’t a pressing issue for your organisation, you’d better wait until it’s hopefully rectified by SAP in a future note.
Another solution to get around it with Config only, would require you to create a custom subtype for IT0021 as „Spouse“ and use that instead of „1“ (e.g. using Subtype „9001“). However, this would require you to change all existing data and if the „1“ is hard-coded elsewhere in the same way it’s done here in the dynpro logi (e.g. in the benefits module), then a custom subtype may shoot down other functionality. Therefore, contrary to usual recommendation: if you truly want to change this urgently, the suggested modification would be safer than the config solution (to be removed, once SAP provides a SNOTE).
