End date is greyed out while raising the travel plan

[Former Member]

Dear Team,

I am facing an issue with Raising a travel request in the portal.

   The end date is greyed out and when ever employee is filling out Start date of the trip, system automatically taking that as end date of the trip.

   As per the requirement, Employee has to go fillout the End date of the trip.

  Could you please advice me to enable the End date field.

Regards,

Sairam.

[Lukas_Weigelt · Accepted solution]

Hi Sairam,

first of all please clarify what scenario you are using. In your opening post you used three different terms:

Travel Request, Travel Plan, Trip (Expense Claim)

Which of those scenarios is the one you are talking about?

Furthermore: What System are you on and what Technology are you using? You stated you use a portal but that could mean you are using transactional iview, WebDynpro JAVA or WebDynpro ABAP.

In any case you should check your field control in FITVFELD (if it's transactional) and FITVFELD_WEB (if it's WDA) for the corrsponding field.

Cheers, Lukas

[Former Member · Accepted solution]

Hi Lukas,

Thanks for the reply.

I can able to solve the issue.

But right now in travel expenses page of  Transactional Iview /webdynpro abap, I could not able to see the Trip schemas which i Have configured in the back End.But I can seen them in PR05 screen.

How  should I do get the schemas in Travel expenses page.

Please advice.

Regards,

Sairam.

[Lukas_Weigelt · Accepted solution]

Hi Sairam,

I assume you mean Application FITE_EXPENSES and I think I understand your confusion. It's an excellent question by the way. Let me elaborate:

PR05

When you create an expense claim in PR05 you always have to pass the overview screen and no matter whether you create a standalone expense report or whether you create an expense report on an existing trip object (request or plan) then you are forced to choose an expense schema, i.e. the system is explicitly prompting you for one.

WebDynpro ABAP FITE_EXPENSES

Use Case 1: You already have existing travel objects like requests which qualify for an expense report. In that case FITE_VC_PRESELECTION is executed and sent as a client response so you can explicitly choose what schema you want to use for an existing trip OR just choose a trip schema from the list and create a standalone expense report. Then it looks like this:

Use case 2: If you launch FITE_EXPENSES and there are no existing travel objects you could build an expense report on, then FITE_VC_PRESELECTION is defaulting to the first entry of qualified schemas as per your trip provision variant and skips the navigation to FITE_VC_GENERAL_DATA so you have no chance of choosing the schema yourself. Usually, schema 01 is the one defaulted to, i.e. a domestic trip.

If you want to change this behaviour, you need to enhance FITE_VC_PRESELECTION and prevent the skipping of the navigation.

Cheers, Lukas

[Former Member · Accepted solution]

Thank you  for the advice.

Sairam.