Hierarchy
SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation⤷
SLL-LEG (Application Component) Global Trade Services⤷
/SAPSLL/LEGAL_PRE_CORE (Package) Legal Services: Preference Handling - Core Functions
IMG Activity
| ID | /SAPSLL/PRE_CTR_VDFR | Control Settings for Vendor-Based Long-Term Vendor Declarations |
| Transaction Code | /SAPSLL/04000029 | (empty) |
| Created on | 20040623 | |
| Customizing Attributes | /SAPSLL/PRE_CTR_VDFR | Form Control for Vendor-Based Vendor Declaration |
| Customizing Activity | /SAPSLL/PRE_CTR_VDFR | Form Control for Vendor-Based Vendor Declaration |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPSLL/PRE_CTR_VDFR |
Use
In this Customizing activity, you define the document types for requesting and sending reminders for vendor-based long-term vendor declarations, as well as the form details, for each administrative unit. You can also specify the reminder levels for the vendor-based long-term vendor declaration. You can define a maximum of 999 reminder levels.
You can also define what is known as a residence time for requests and reminders that you have issued for a long-term vendor declaration. The residence time, which is specified as a number of days, determines how many days after a document has been created that the system assigns the For Archiving status for the document. In the archiving function, you can therefore only archive documents that have the For Archiving status due to the expired residence time.
If you want to define agreement-specific forms for an administrative unit, you can enter the form details in the Form Data for Specific Agreements area. The system adopts the information for the reminder levels and residence time that you specified for the entire administrative unit for this form data. If you want to define agreement-specific forms exclusively, you can leave the administrative unit-wide form data blank and simply define agreement-dependent forms. In this case, however, you have to define the residence time, the reminder levels, and the type of document at the level of the administrative unit.
In a second step, you can assign different cover letter forms to each of the reminder levels and define different form parameters. This allows you to vary the letter text for the reminders at each level.
You can also define different form parameters for the different reminder levels, just like you do for the cover letter text. You can define them either at the administrative unit level or agreement-specifically. In addition, you specify the intervals that are to fall between the expiration of a long-term vendor declaration and a request for a long-term vendor declaration and possible reminders. You configure the system to start request and reminder runs automatically for vendor-based long-term vendor declarations by entering a number of days for the respective reminder level.
Requirements
Standard settings
Activities
- Enter the administrative unit and (if applicable) the document type.
- Define the residence time.
- Define the form details:
- Number of the maximum reminder level (reminder level 0 is a request for a vendor declaration)
- Form name, including form text and letter
- Specify the text variants for reminders, if needed.
- Also define the intervals between the expiration of a long-term vendor declaration and the request and reminders.
Example
"Reminder level 0" means "request vendor-based vendor declaration"
The number of days entered refers to the date on which the existing long-term vendor declaration becomes invalid. We recommend that you request a subsequent vendor declaration before the existing declaration expires. You do this by entering a negative value in the system. Make sure that the minus sign is shown after the number of days.
Example:
If the most recent long-term vendor declaration is due to expire on December 31 this year and you enter 45- as the number of days for reminder level 0, the system lists this long-term vendor declaration as relevant for request as soon as you start the request run in the period 45 days BEFORE the current long-term vendor declaration expires.
"Reminder level 1" means "First reminder run"
The number of days entered is added to the date that the request was issued.
Example:
If you requested a long-term vendor declaration on November 16 of this year, and this vendor declaration had not previously been entered in the system, the system starts the first reminder run. If you defined the number of days as 30 for reminder level 1, the system will output the first reminder on December 16 this year.
"Reminder level 2" means "Second reminder run"
The number of days entered is added to the date of the first reminder run.
Example:
If the system performed the first reminder run on December 16 of this year and you had not previously entered a long-term vendor declaration in the system, the system starts the second reminder run. If you defined the number of days as 15 for the second reminder level, the system will output a second reminder notice on December 31 this year.
"Reminder level 3" means "Third reminder run"
The number of days entered is added to the date of the first reminder run.
Example:
If the system performed a second reminder run on December 31 of this year and you had not previously entered a long-term vendor declaration in the system, the system starts a third reminder run. If you defined the number of days as 45 for reminder level 3, the system will output a third reminder notice on February 14 of next year.
Reminder levels 4 through 99: See reminder level 3
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | /SAPSLL/PRE_CTR_VDFR | 0 | /SAPSLL/SLL0000003 | Global Trade Services |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| /SAPSLL/VC_TVDFRM | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20060621 |
| SAP Release Created in | 300_620 |
