on 08-27-2015 1:28 PM
Hi All,
Greetings, I am facing an issue with IT 0021 object identification field. object Identification has already activated for the subtype AA01 , time constraint '2'. but i am not able to save a reacord for subtype AA01. system throwing an error message "ID number should have only 11 digits". I proposed solution to my user to change error message into information message from the table T100S. but even i feel that i am missing some configuration set up . could you please advice me on this??
for reference snap shot below on this.
Thanks in advance.
Ashok.
Hi,
Can you check infotype 0185 record for the employee?
Hope this helps.
Donnie
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Donnie,
we are facing this issue for the country grouping "QA". same functionality is working fine for "BH" country grouping. as you suggested i haved checked in IT 0185. system allowing me to save the record for "BH" without considering IT 0185. my assumption was technically 0021 and IT 0185 are no where related. please correct me if i am thinking incorrect, and advice why system behaving like this for paricular country grouping only.
Thanks in advance
Ashok
Hi,
For Qatar, infotype 0021 has an additional view coming from infotype 3304. One cannot maintain additional infotypes directly – SAP does it for you. In the input module MP330430 for infotype 3304, there is logic in form ICNUM_QA to check length for ID number maintained on infotype 0185 - document types 01 or 02. The ID must be 11 digits long. Here’s a snippet of the code that has comments on validation rules:
* Validation on the Qatar specific identity number field on
* infotype 0185 (ID Asia).
*• ID card
*(11 numbers, and 1st digit is 2), ), it should be followed also by employee
* file number at arrival affairs section in ministry of interior, the file number
* format is (4 chr.)yyyy/ (10 chr.) xxxxxxxxxx ex. employee ID no. 21345678901,
* attached. example of file number is 2011/1234567890
*• RP (Resident permit – 11 numbers and 1st digit is 2)
Further, form ICNUM_QA in include P0185QA0 (which is for infotype 0185 for Qatar) has logic to check length for ID number. In addition to the validation rules mentioned above, it has these rules:
**--> For year below 2000. ID number should start with "2"
* For year from 2000. ID number should start with 3.
**--> Get Year first field and increment by 1.
Bottom line, as suggested earlier, you need to check infotype 0185 for the employee.
Hope this helps.
Donnie
Hi Donnie,
sorry to chase you like this, herewith my observations below:
as per standard IT 0185 will updates IT 3304, from IT 3304 >>IT 0021 will be created.
Many thanks,
Ashok
Hi,
If you are able to maintain infotype 0185 record, you would need to run report RPUPAV00 to generate the corresponding record for infotype 3304. Please be very careful with that report. I highly recommend going through the documentation and doing a test run. There is no transaction code for it either. You will need to run it through SE38/SE80.
Reason you need to do this because of new infotype framework, SAP expects and maintains additional infotype views. Report RPUPAV00 is delivered to "convert" legacy records.
You can look in tables T582V and T582W for other infotypes that have an additional view.
Hope this helps.
Donnie
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you double click on the error message and send a screenshot
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is a difference in the screen. The identification documents section is not there. Can you check the screen modifications in T588M based on P0021 return value for the two countries. I think if you are okay with the same screen in both, then the return value of the feature can be updated accordingly.
User | Count |
---|---|
100 | |
11 | |
10 | |
6 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.