Kontakt

Ansicht
Dokumentation

RPR_AIRP_LRS_TO_FI_V3 - Post Lufthansa AirPlus Invoice Record (LARS) to FI

RPR_AIRP_LRS_TO_FI_V3 - Post Lufthansa AirPlus Invoice Record (LARS) to FI

Vendor Master (General Section)   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

Post a file in LARS format from Airplus to financial accounting

Integration

Only with the travel management onPremise solution.

Prerequisites

  • In particular the clearing process is only supported in the use-case of the travel onPremise solution.
  • In transaction WE20, the vendor for AirPlus (invoicing party) has to be created as the partner profile for the partner type LI. It is strongly recommended, that the vendor master data settings allow double-invoice check.
  • Company code: In transaction OBCA, the assignment is made, using this partner, to the AirPlus partner number and the company code into which the invoice is to be posted. Instead of the partner number also the Airplus company account number can be used.
  • G/L accounts: On the selection screen of the report, you can enter the G/L account to which the items are to be posted. If you want the assignment to be more precise, you can make the entries in transaction OBCB. Here, the assignment is made between the sales type and the G/L account. Example: "DB" (Deutsche Bahn) is to be posted to account 190990.
  • In case, that files need to be processed which leads to more than 999 posting lines, a document split is carried out. Per default, several documents with one vendor line each will be created. If you prefer that only 1 of these documents contain a vendor line with the full gross invoice amount, you must maintain a technical split account in OBCB with the dummy sales type DOCUMENT_SPLIT_ACCOUNT. Then the created documents will be connected via this G/L account.
  • In transaction OBCD, the assignment is made between the tax rate and the tax code. Example: 16 percent => entry: 001600000, tax code: V1.
  • Any alternative foreign currency translation for tax items is not supported, in other words, the company code should not have an entry for "Currency translation for tax" in the global data.
  • Account assignment objects are copied from the file (additional data record 400). The following account assignments are supported:

    - Cost center
    - Internal order (sales order; see description below)
    - WBS element

    If it happens, that the LARS file contains invalid cost assignment objects, you may use the report RPR_AIRP_PRECHECK_CO_OBJECTS (transaction PTRV_LARS_PRECHECK) in order to check all contained cost assignment object and if necessary replace them and save a new file with the replacements done.
  • To post rounding differences, the G/L accounts for rounding differences must be maintained in Customizing.
    As of Release 4.70, there is the option of integration into SAP Travel Management in addition to the option of posting to expense accounts. The postings are usually made to a clearing account. Using the assignment number and the text for the line item, the posted documents from this report can be cleared with the documents from Travel Management.
  • Furthermore, there is the option to access the original data of the file within a Business Transaction Event (BTE, "open FI") in order to enhance the document with further information, if necessary. (BTE RWBAPI01). Also the Badi BADI_AIRP_LRS_TO_FI exists to modify the G/L account lines (but not the tax code!).

Features

Additional information -> FI line item (if it is available in the file)

  • Transaction number → Assignment number (ZUORD)
  • Personnel number → Ref1 (XREF1)
  • Invoice item → Ref2 (XREF2)
  • Card number → Ref3 (XREF3)
  • Sales type / name of traveler / trip destination / sale date → text (SGTXT)

Selection

  • With travel management: the file is posted without VAT and without CO accounting objects. The used G/L accounts must allow posting without VAT and without CO objects in this case. The VAT and CO relevant posting then is carried out via the travel posting process in transaction PRRW. You then receive a 2nd file from Airplus to be uploaded into the credit card buffers of the employees.
  • Without travel management: the file is posted as invoice with CO accounting objects and with VAT.
  • Max. number of posting lines per document: per default there will be max. 999 lines per document. If necessary the max. number of posting lines per documents can be reduced to any number between 5 and 999.
  • G/L account is fixed: if this checkbox is checked, transaction OBCB will not be read to get a more precise G/L account assignment. Only the G/L account specified on the selection screen is then relevant. Exception: the document split account.
  • Payment block: You can choose a payment block indicator here. The vendor position will be posted with this payment block indicator.
  • Orders are sales orders: if this checkbox is checked, all values in the field 'order' will be interpreted as sales orders. Otherwise all values in this field will be interpreted as internal orders.
  • Separator sales ord./posit. the value of the sales order is split at this sign into sales order and sales order position.
  • Other field for sales order: if this checkbox is set, the value for the sales order will be looked for in another field in the dataset. Which field exactly is specified below:
  • ...Field with sales order: in this field, you specify the field in the Lars dataset, which is supposed to contain the value of the sales order. Per default this field is 400-INT_KONTO. The separator will also be applied to sales orders in this field.

Standard Variants

Output

You get a list with success, warning or error messages.

Activities

Example






CPI1466 during Backup   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 6782 Date: 20240601 Time: 024515     sap01-206 ( 116 ms )