BAPI for travel request reject..

[Former Member]

Hi Experts,

Kindly help me.

BAPI / FM for rejecting travel request.

According to my assumption a trip can have multiple travel request .

Example: Five person is going for onsite project, for this a trip is created for all and each person create their own travel request with help of this trip.

If i am wrong please clear me the scenario..

Thanks a lot in advance..

[former_member131723 · Accepted solution]

Hi Prachi

You want a BAPI to reject multiple trips being raised? There is nothing immediately that I can think of that would fit that purpose as even our standard workflows dont come with a reject step in the template.

There was another recent topic on this if you search this forums (most likely had participants as the tag word but I cant find it at first glance!) but in terms of how the trip is raised  - one trip cannot be reimbursed for multiple pernrs as enqueue logic means trip is raised by pernr, however you have the possibility to copy trip and in web dynpro, FITV_POWL_ASSISTANT provides possibility to open trip on behalf of other employees  - you also have the possibility to enter internal and external participants in expense types but settlement and reimbursement always goes to principal pernr raising the trip.

Hope this helps!.

Kind regards

Sally

[Lukas_Weigelt]

Hi,

According to my assumption a trip can have multiple travel request .

No.

The Standard business process in SAP is always the following (and it's always dedicated to one single person😞

• In case the Travel Request Service is used: Travel request is created --> Trave request is approved/rejected
• In case the Travel Planning Service is used: Travel Plan is created --> Travel Plan is approved
• the trip takes place
• Travel expense Claim is created --> Travel expense Claim is approved
• Travel expense claim is settled, posted, etc.

An expense claim can be created on basis of a existing travel request or plan but not vice versa.

Concerning your scenario. If 5 people go for an onsite project, each of them creates a dedicated travel request. Once the travel requests have been approved and the trip has taken place each of them creates a dedicated travel expense claim (trip). This is the way it would work in the standard.

Cheers, Lukas

[Former Member]

Hi Lukas,

Thanks a lot for quick response.

As you said,

• In case the Travel Request Service is used: Travel request is created --> Travel request is approved/rejected

So how can manger disapprove/reject employee travel request ??

Is there any BAPI/FM ??

Thanks.

[Former Member]

Hi Lukas,

I think i am missing few points from what i had read about the travel management it says typically it will follow:

1. Trip – Any travel that is done by an employee who is eligible for reimbursement .  A trip begins at the time the traveler leaves source for destination until the time they return back
2. Travel Request – A document that estimates the expected expenses to be committed to a particular trip and their source of funding.
3. Trip Expense Report – A document that lists the actual expenses incurred on the trip and their source of funding.  All employee-reimbursable expenses should be listed for a trip .

As per my assumption:

a ) trip is created and against a trip the travel request is created and against the travel request/trip, we create travel expense.

b) Travel request  can be created with out a trip because it will still generate a trip no.

Suppose two employees of same designation and same eligibility are traveling for the same purpose and on a similar trip. In that case do we create 2 trips and 2 request or we just create one trip and create two request for the same.

Please suggest.

Thanks..

[Lukas_Weigelt]

The terminology is confusing, I admit that.

Trip = (usually) Travel expense report/claim

Travel Request = Travel Request.

A Travel Request normally is created first (and approved) before the trip takes place.

After the trip has taken place, an expense report is created on basis of the travel request (technically the data is the same, only a flag in the cluster determines whether the saved data is a travel request or an expense report). The order of these sub-processes can differ depende

nt on your specific in-firm business process. If in your company, people just go on business trips and create requests and expense claims afterwards, that would be possible too; it really depends what you want.

But for the usual case and flow of process, your example would take shape in the following:

• Let's suppose it is July 1st and two employees want to go on a business trip on July 20th.
• On July 1st they both independently create a travel request (each one them creates one) which both get approved on the same day.
• On July 20th the trip takes place and they return on the same day.
• After July 20th both of the employees create a travel expense claim on basis of their travel requests (for each for his own)

As Sally said, the whole FI-TV process is bound to the PERNR, i.e. there is no such thing as a Travel request or expense claim valid for several employees.

Cheers, Lukas