|
Functionality
By means of this BAPI you can import invoices from a mobile data entrydevice (e.g. handheld) into the Route Accounting DB.
At least the general data (by means of structure ISGENERALHD), theinvoice header (by means of table ITINVOICEHD), the invoice item (bymeans of table ITINVOICEITM), and the invoice condition data (by meansof table ITINVOICECOND)
must also be provided as input parameters.
In the BAPI function modules of the following function groups are used:
- /DSD/HH_UL_ALE (DSD - Route Accounting Upload: generated ALE inputprocessing)
- /DSD/HH_UL_CONVERT (DSD - Route Accounting Upload: Field conversions)
- /DSD/HH_UL_MISC (DSD - Route Accounting Upload: Other, such asAuthority Check, Application Log...)
When the function module has been called, the table ETRETURN (of thetype BAPIRET2) contains all log entries created by the process.Depending on the Customizing settings, an application log is createdfrom the table or not.
The BAPI is assigned to the method CInv0 of the business object/DSD/RTACC as API function. Notes
Transaction control
The BAPI neither executes a database commit nor a rollback work.Therefore the calling application needs to initiate the commit or therollback work to make the changes in the data base. To do so, the BAPIsBAPI_TRANSACTION_COMMIT and BAPI_TRANSACTION_ROLLLBACK are madeavailable. Further information on the BAPIs can be found in thefunction group 'BAPT'. Further information Description
Return parameter Description
Route accounting: Header data Description
Return parameter Description
Reference structure for BAPI parameter ExtensionIn/ExtensionOut Description
Route accounting: Invoice conditions Description
Route accounting: Invoice header Description
Route accounting: Invoice items |