cancel
Showing results for 
Search instead for 
Did you mean: 

Travel Infotype P0017 Couldnot be read error

Former Member
0 Kudos

Dear All,

While executing the T code TRIP in travel management , its throwing an error.

We maintained infotype 0017 too but error is continuing .

Please give your valuable inputs to resolve ....

Thanks in advance

Regards,

Y.V.P.Deepak.

Accepted Solutions (1)

Accepted Solutions (1)

Lukas_Weigelt
Active Contributor
0 Kudos

The Infotype is maintained incorrectly, i.e. it is non-existent for the current system date. It's as simple as that . Check ENDDA of the Infotype is 'open end' or at least greater than the current system date.

Cheers, Lukas

Former Member
0 Kudos

Hi Lukas,

Could you please tell me how we can make groupings for IT0017 with some examples.

Iam new to to travel management configuration.

Iam little bit confused in configuring the groupings for Travel privileges.

I checked the periods it placed for the period 01.12.2012 to 31.12.9999.

Please guide in this.

Thanks & regards,

Y.V.P.Deepak

Lukas_Weigelt
Active Contributor
0 Kudos

What to you mean with "groupings"? If ENDDA really is 31.12.9999, then the error you mentioned can technically not happen, see for yourself:

CALL FUNCTION 'HR_READ_INFOTYPE_AUTHC_DISABLE'.
   CALL FUNCTION 'HR_READ_INFOTYPE'
     EXPORTING
       pernr           = employeenumber
       infty           = '0017'
       begda           = sy-datum
       endda           = sy-datum
     IMPORTING
       subrc           = subrc
     TABLES
       infty_tab       = p0017
     EXCEPTIONS
       infty_not_found = 1.
   IF sy-subrc = 1.
     CLEAR employeenumber.
     MESSAGE e861(56) WITH 'P0017'.
   ENDIF.
   CASE subrc.
     WHEN '0'.
       rp_provide_from_frst p0017 space sy-datum sy-datum.
       MOVE-CORRESPONDING p0017 TO p0017_sydat.
     WHEN OTHERS.
       CLEAR employeenumber.
       MESSAGE e861(56) WITH 'P0017'.

   ENDCASE.

Maybe you access a wrong employee number by accident or you are on the wrong client or something 😕

Cheers, Lukas

Former Member
0 Kudos

Hi Lukas,

I am accessing correct employee, and client  is development.

and i hope maintained the infotype correctly.

Thanks & Regards,

Y.V.P.Deepak

Lukas_Weigelt
Active Contributor
0 Kudos

Hi Deepak,

the Infotype looks good. In fact, for the mere reading the only relevant part is BEGDA and ENDDA. Now I also see what you meant with "groupings", I can't tell you from a functional point of view whether they make sense but they won't influence the initial reading of the infotype anyway.

If the error still remains with this configuration, I'd advise you to debug the part of coding where this error is thrown, this would be Include MP56T_OVERVF02, line 1474 or so (it's the part of coding I posted earlier).

Cheers, Lukas

Former Member
0 Kudos

Hi Lukas,

I will go through that and get back to you .

Thanks & regards,

Y.V.P.Deepak

0 Kudos

Does the user also have an IT105 subtype 1 record (system user name). If you start trip and the user of the person who starts transaction is assigned to an employee number the system tries to default this employee number in TRIP.

Let us know if still having problems

cheers

Sally

Former Member
0 Kudos

Hi Sally,

infotype 105 with subtype 0001 existed.

Please be clear about your explanation .

Thanks & Regards,

Y.V.P.Deepak

Lukas_Weigelt
Active Contributor
0 Kudos

Oh, didn't even know this o_O. Good to know.

Cheers, Lukas

Lukas_Weigelt
Active Contributor
0 Kudos

Please be clear about your explanation .

If I understood Sally correctly, when you enter the Transaction TRIP with your regular development-user the system will try to default via the development user's IT0105 assignment to its employee number before you even get a chance to enter a freely chosen PERNR.

Former Member
0 Kudos

Hi Lukas,

Problem solved .i did what sally told.

Thanks for helpful support.

Regards,

Y.V.P.Deepak.

0 Kudos

Good stuff.. was just about to reply and Lukas answered exactly (sorry it wasnt very clear!)  - starting with ERP2005 I think it was, the CP-P-US concept applies also to Travel Management so this is when it became a requirement and as Lukas mentioned it does look for employee number when defaulting to trip/PR05 etc!

Answers (0)