Ansicht
Dokumentation

SIMG_PTRV_T100C - Message Control for Dialog

SIMG_PTRV_T100C - Message Control for Dialog

ROGBILLS - Synchronize billing plans   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

The following messages from Travel Management can be controlled at present:

From the application area FITVPS:

  • 439,,No separation allowance assigned to travel request for trip to start work
  • 440,,No separation allowance assigned to travel request for bus. trip return

From the application area PTRA_WEB_INTERFACE:

  • 062,,Changes in settlement past trigger retroactive settlement

    Deactivating this message affects only the creation of an expense report based on a posted request.
  • 063,,Changes in posting past trigger adjustment postings

    Deactivating this message affects only the creation of an expense report based on a posted request.
  • 150,,Amount, currency, and date fields and service provider reset
  • 666,,Company code was changed from &1 to &2

    If this message is not deactivated, the company code is automatically adjusted in the background when a CO account assignment object is created. This is only possible for cost centers if a cost center does not exist in multiple controlling areas. In addition, only the company codes in the employee’s master controlling area are checked in the browser applications. The list of possible company codes can be enhanced with the BAdI TRIP_WEB_CUSTOMIZING, PAOC_MTE_BADI, or PAOC_MTR_BADI, depending on the application.
  • 081,,Start date & of receipt & is outside the travel time

    Together with the following message 082 from this application area, this message controls whether the from-date and to-date of the receipt must be within the travel time. This is valid for browser applications and SAP GUI.
  • 082,,End date & of receipt & is outside the travel time
  • 039,,Receipt no. & of & is not within the travel time

    If this message is set to error, no receipt with a date outside the travel time can be entered. Credit card receipts with a receipt date outside the travel time cannot be transferred from the receipt buffer to the trip for the TRVPA-CCC values 3 or 4. The receipt can be transferred for the values 1 or 2; however, the receipt date needs to be modified in this case. This is valid for the browser applications.

From the application area 56:

  • 222,,Trip & has more than 99,999 km

    In principle, trips with more than 99,999 kilometers/miles can also be settled correctly. However, the statistical evaluations can consider a maximum of 99,999 per trip.
  • 287,,The trip to be saved entailed no costs
  • 509,,Exch.rate variance & % too high for comp.code &
  • 893,,The trip segment comparison calculation is not current
  • 894,,No trip segment comparison calculation has been executed
  • 146,,Trip data for the period from &1 &2 to &3 &4 already exists
  • 243,,The selected trip schema & does not allow advances

    If this message is activated, an expense report based on a request with advance can only be created if the trip schema of the expense report allows advances to be entered.
  • 155,,Date &1 is not within travel time &2

    If this message is set to error, no receipt with a date outside the travel time can be entered. Credit card receipts with a receipt date outside the travel time cannot be transferred from the receipt buffer to the trip for the TRVPA-CCC values 3 or 4. The receipt can be transferred for the values 1 or 2; however, the receipt date needs to be modified in this case. This is valid for the SAP GUI transactions.

From the application area PTRA_DIALOGUE:

  • 092,,Vehicle master data updated based on trip date
  • 097,,Tax code &1 is not permitted for company code &2

    If this message is not deactivated, the tax code entered in the trip is checked against the permitted reporting country for the tax code (foreign plants).
  • 098,,Warning: Meals deductions must be entered on 2nd calendar day

    This message is to be deactivated. For trips between 16:00 and 08:00, the user of the German trip provision variant should be forced to enter deductions on the second calendar day, since only deductions on the second calendar day were settled. This is no longer necessary; deductions on both calendar days are settled.
  • 100,,Account assignment objects used in the trip are no longer valid
  • 120,,Advance date is in the past or after the end of the trip

    If the advance date is to be used as the posting and/or receipt date, and thereby as the payment date for advances when posting travel requests, it is recommended that you do not deactivate this message, so as to ensure consistency.






TXBHW - Original Tax Base Amount in Local Currency   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 5750 Date: 20240523 Time: 165015     sap01-206 ( 101 ms )