Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Question regarding Infotypes 167 and 21

Former Member

‎2008 Sep 02 4:42 PM

0 Likes
851

It was my understanding that the DTYXX and DIDXX fields of infotype 167 were populated from 21 using the subtype and objps, respectively, from that infotype.

That is, if I have a spouse on 21 with subtype 1 and objps 01 then I would see on some group of DTYXX/DIDXX records those two values which would would then show which dependent(s) were covered.

However, I'm looking at PA0021 in SE11 right now and I see two records (of the four) that have no OBJPS value (it's blank). I'm confused now as I have an interface that will need to add an existing dependent to a new plan that I'm creating programmatically. I though I could query 21 and get the subty and objps and then update the new 167 record accordingly but since objps is blank I've hit a dead end. Apparently I'm missing something.

PLEASE HELP

3 REPLIES 3
Read only

Former Member

‎2008 Sep 08 7:44 AM

0 Likes
692

Hi Steve,

Recently i had faced the same Dead End but i had left these type of records to the admin itself so that they can manually do it.

This Issue comes only when someone has changed the existing configuration settings in T591A(Objrq) for the corresponding subtype of IT21.

one sol is that if IT167 is not present than update the sequence numbers in IT21 for such records based on birth dates which could be one possible solution. As you are going for a new plan first update the IT21 records then go for IT167 new plan.

Cheers,

Jacks M

Read only

Former Member
In response to Former Member

‎2008 Sep 08 2:20 PM

0 Likes
692

Jacks:

Thanks for the response.

In some cases I have to create the 167 first; in others, it already exists and I'm simply updating it.

I did discover, from talking to my colleagues here, that an OBJPS which is blank is fine. Apparently, the next value for OBJPS is "01", "02", etc. for subsequent entries that would otherwise conflict on the key values.

At least in my case, I can live with that. I had originally thought that OBJPS should start with "01". For example, if I created a child (subtype 2) record on 21 for a given pernr and it was the first subtype 2 record for that pernr the value of OBJPS for that new record would be "01"; in fact, it's blank. If I add a second child then it's OBJPS would be "01".

Like everything else in SAP I'm sure there's some grand logic to explain this behavior. Unfortunately, I don't have the time to look into it - I have a deadline LOL.

Read only

Former Member
In response to Former Member

‎2008 Sep 09 7:03 AM

0 Likes
692

Thanks Steve for the Info..

Infact i found that the SAP allows you to save the Seq No. with 00 as it is a part of primary key and we have avoided that by putting an user exit check where Admin is not allowed to save with it as it is confusing to identify the child/guardian.In case if the user doesn't give any input then SAP would prefer '01' and for the nxt records 02,03..as default values.

As you said No two records will have same OBJPS (your case with two blank records) bcoz it is a part of primary key..Obviuosly SAP would generate the nxt seq no.

Cheers,

Jacks M