SAP® Documentation

Single view

/ISIDEX/RESETTLPODLIST - Itemized PoD Statement for Overtake and Undertake Amounts

BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

The result of an overtake/undertake amount determination run is the overtake or undertake amount for each settlement unit or each customer group in each settlement.

Once you have carried out synthetic settlement and determined the overtake and undertake amounts, the PoD-specific itemized statement ensures that it is possible to track the bill for the respective supplier.

Integration

Prerequisites

You must have successfully determined the overtake/undertake amounts before you can execute this report.

Note:
This program cannot be run as a background job because local files are generated.

Features

Selection

The data is selected via via the settlement document. It is only possible to start the report by entering a valid document. You can also restrict the selection of points of delivery to specific service providers and settlement units. You can use the multiple selection features to enter individual values and intervals.

Note:
This program does not support overtake and undertake amounts that are based on time slices. Instead, you receive one entry for the relevant time slice. Manual preparation may be necessary.

Standard Variants

Output

Choose |@3Z@ with quick info text Number of Entries in the application toolbar to preview an evaluation of how many entries exist for the specified parameters.

This preview can be output in an ALV grid or as a local file on your PC.
The following fields are displayed in the ALV grid as standard:

  • Actual Time and Actual Date
  • Planned Time and Planned Date
  • CI Include Fields (if available)

You can also implement BAdI /ISIDEX/SETTLPODLIST and program the methods.

  1. Output as ALV Grid (Display Data):
Output in an ALV grid is proposed as standard. To start a report using an ALV grid output, enter a document and, if necessary, restrict the selection by entering service providers or settlement units. The maximum number of hits is set to 500 as standard and means that a maximum of 500 entries can be displayed for this type of output. This does not apply if you choose to generate the preview as a local file.
If the system has selected more entries than can be displayed, a status message will inform you of the number of selected entries.
In addition to the fields listed above, the ALV field catalog contains more output fields, which you can adjust with the help of the layout. The ALV also offers various options for exporting or processing the displayed data.
  1. Output as Local File (Save Data):
If you choose to save the preview as a local file, use the input help to choose a file path and then enter a file name.
If you save the data as a local file, one file is written for each service provider. The file name is made up of a freely definable prefix (corresponds to the file name you gave previously) and a suffix (the name of the service provider and the current date and time stamp).
Once all the files have been created, a status message informs you of the number of files.
A line with the names for the individual fields is generated in the files. If you define the CI include, the titles for the new fields are taken automatically from thr ABAP dictionary.

Activities

The ALV grid provides the option of forward navigation.

You can display the following objects by clicking on them:

  1. Settlement document
  2. Settlement unit
  3. Supplier
  4. Profile
  5. Point of delivery
  6. Installation

Example






rdisp/max_wprun_time - Maximum work process run time   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 5906 Date: 20191021 Time: 172131     sap01-206 ( 21 ms )

Our Service

Looking for Support? Questions?

The

Consolut

Callback-Service

Leave us your contact details and we will call you back. Panels marked with * are mandatory.