Validation of EEO code using ad hoc query

[Former Member]

Hi,

I just want to ask for a help or any ideas with regards to the case below.

The EEO job categories have been revised and I've already map the existing job codes to the correct EEO job category in table T5U13. But when I try to run a query for a specific job to check and verify if the mapping of the new EEO job category to the existing job code is correct, the EEO code field is left blank. Meaning that there is no EEO job category attached to the job code. But I've maintain the mapping already and when I double check table T5U13, the job code is map to the new EEO job category. I just want to ask for help that if I run the query, the EEO code field would have an entry based on the mapping I've done.

Thanks in advance for your help!

[Former Member · Accepted solution]

Hi Bernie,

Which Infoset you are using for the Ad hoc query ? If you are using PNPCE or PNP then you will not get anything in return. Try to use PCH database with Object type C and select the US Job attributes in the related object attribute category. you will get AAP , EEO etc. To include the PA data you can select the Person/Holder and the infotypes.

Or you can create an infoset by joining IT0000, IT0001 and T5U13. We are using the former method and it works fine.

Sanghamitra.

[Former Member · Accepted solution]

Hi Sanghamitra,

Thanks for helping me in this case. Really appreciate it!

Just a follow up question... I can't include a PA data wherein I can select the person/holder and its related infotypes to the new infoset I've created. May I know how can I include PA fields and infotypes? Also, how can I join IT0000, IT0001 and T5U13 in an infoset?

Thanks Sanghamitra!

[Former Member · Accepted solution]

When you created the new Infoset, did you select the Object type as C ? When you are in SQ02 you should select the logical database as PCH and from Determine Object type - select C. You will see at the end a folder 'Infotype of related Objects". From here select Person and then go to relationship A017 'is carried out by'. You will see all PA infotypes.

If you have not done table joins before, it will be difficult to describe over an email. You can select table join as database and enter the three tables I have given earlier (one by one) . System will default the key fields.

I will suggest go for the first method, its easy to create.

Sanghamitra

[Former Member · Accepted solution]

Ok. Thanks! Got it.. Yes, I would go on the first method as its easy to create. By the way, after selecting the object and the infotypes, do I still need to do anything before saving the infoset. Its because in the change infoset screen, there's a statement saying "No field selected: Select a field by double-clicking". As I think I should select the data field first that I need for the query before saving the infoset.

Thanks!

[Former Member · Accepted solution]

Hi,

I am new to Infoset. I have a doubt. When generating Infoset system is asking to give package name. What should I write here and what exactly is pacakge?

I just saved it selecting Local object.

Thanks,

GRM

[Former Member · Accepted solution]

Hi GRM,

Related objects in the ABAP Workbench are grouped together in a package. The package determines the transport layer that defines the transport attributes of an object.

The package name will depend on the area on which you are working on. The package should describe the area that the object belongs to.

As you saved it selecting local object... it means that changes to the objects are not recorded by the Transport Organizer. The package does not belong to a transport layer. The objects cannot be transported.

[Former Member · Accepted solution]

Yes. When you select the required fields from Object type and its related objects, after you click on the green check you will see a small pop up screen asking you to select the data fields. You should select all data fields. Sometimes this pop up screen is hidden behind other windows screen. So close all IE and other screens and go to desktop, you will see this pop up box.

Sanghamitra

[Former Member · Accepted solution]

Hi,

Thanks for your reply.

Regards,

GRM

[Former Member · Accepted solution]

Hi Sanghamitra,

My problem is still not solve up to now.. I've already created the infoset based on your instructions (with logical database PCH). But I can't find this infoset in transaction PAAH. Thus, I can't run the query. Instead, I've seen this infoset in SQ01 but upon running it (I think this is not the right transaction to run the query), I didn't get any results (Hitlist resulted to 0). The system can't find any employee data but actually the system has master records.

Please help!

Thanks in advance!

[Former Member · Accepted solution]

PAAH is the old transaction code and not in use anymore. You should use the new tcode for ad hoc query S_PH0_48000513. If you cant find the infoset that means you haven't assigned it to the correct user group. You have to assign the infoset to the user group via tcode SQ03.

Sanghamitra

[Former Member · Accepted solution]

Ok. Thanks! I'll try to use the new t-code. I've created already the infoset based on your instructions but why there's no "EEO Code" field? I needed this field for the query. Its not in the US Job Attributes.

Thanks again!

[Former Member · Accepted solution]

Hi Sanghmitra,

I have got a query in AD-HOC query.

After creating the Adhoc query using the join table functionality the resulting adhoc query does not results any out put.

What I have done is :

1.Created a user group through SQ03

2.Attched user to My user group

3.Created an infoset using join table functionality(SQ02).

4.Saved and generated the infoset

5.Added the user group to the infoset and than run the ADHOC query.

The table I have used to join is all PA table (For test pupose)

Though the purpose of the custom infoset is to join PA,OM and E rec infotypes, for testing purpose I have joined only PA infotypes.

Result:The adhoc query does not gives any out put instead it says no data could be read.

Could you please tell what else I need to do so that the custom infosets gives an out put.

Will greatly appreciate your help.

Thanks and best regards

Rajeev

[Former Member · Accepted solution]

Bernie,

Make sure you have selected the right field for EEO. Can you confirm the technical name of the field you are using as EEO output field.

Sanghamitra

[Former Member · Accepted solution]

It looks like your table joint is not proper. In this message we have been discussing about EEO related ad hoc query so it will be better if you can start a new thread.