SAP® Documentation

Single view

/SAPSLL/PRE_VD_EU_CONDENSE - EU: Aggregate Long-Term Vendor Declaration

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

Purpose

The "Aggregate Long-Term Vendor Declarations" program is used with a selected aggregation model to aggregate the vendor declarations for a product according to its status. The worst status of all the vendor declarations found applies here.

Integration

The report is integrated into the SAP Global Trade Services preference scenario.

Prerequisites

To be able to run this report, vendor declarations must first be transferred from the feeder system and be requested from the vendor.

Features

Selection

You can define the following parameters on the selection screen:

- Preference model

,,This determines the organizational criterion to be used for aggregation. At present two ,,preference models exist:

,,,,- Cross-plant preference calculation

,,,,,,Aggregation applies to cross-plant groups and the products

,,,,- Plant-related preference calculation

,,,,,,In this model, the vendor declarations are aggregated for each product and plant

- Group of logical systems

,,If an external product number is to be used for restriction purposes you must specify a group of logical ,,systems from which the external number originates.

- External product number

,,If the restriction is to be applied to a product number, you may only enter external ,,product numbers

- Simulation mode

,,You can use the indicator to determine whether the aggregation result can be stored ,,or not.

- Select address data

,,This indicator determines whether address data should be included when a business partner result is ,,displayed. If so, you must select the addresss data. Note: This can affect adversely affect performance.

- Save log

,,This indicator determines whether or not a processing log is saved. Note: The log can only be saved in update mode.

Standard Variants

Output

After aggregation is completed, the system displays a list of aggregated vendor declarations. If these are not in simulation mode, the result can be saved.

The following rules apply when determining the status for an aggregation: The worst status of a vendor declaration is always used as a model:

- The statuses 10 (not checked), 20 (not checked: Long-term declaration requested) and 30 (checked: Not OK, no long-term declaration exists) in vendor declarations result in status A (not maintained) for aggregation

- The status 40 (checked, not OK, negative long-term declaration exists) in a vendor declaration results in status F (preference does not exist - date-dependent vendor declaration) for aggregation

- The status 50 (checked: OK: Validity of inactive long-term declaration extended) and 60 (checked: OK: long-term declaration exists) in the vendor declarations result in status E (preference exists - date-dependent vendor declaration) for aggregation

Activities

Example






TXBHW - Original Tax Base Amount in Local Currency   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3282 Date: 20191215 Time: 062223     sap01-206 ( 14 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.