Single Blog

Vistex Agreement Workbench

14. 4. 2021, Written by 0 comment

After creating a group of agreements, you assign the group number to each contract. In the event of a mass change in several agreements, the system can be configured to establish a collective agreement requirement for all amended agreements. Otherwise, the system establishes a separate request for agreement for each agreement. In the configuration of the type of agreement request, check the requirement to collect the identifier. If you record the mass changes as a request for agreement, the system displays a dialog box indicating the type of contract requirement. In the window, check the „Collect“ box to create a collection request, or leave the checkbox empty to create separate individual requirements. Instead of establishing application-specific agreements, you have the option to create direct agreements. A direct agreement is used to develop a contract directly with the customer/supplier. Direct agreements can be applied directly to the market. The requirement of the agreement allows for one or more phases of approval as part of an approval process. During an approval process, the department, team or person assigned to each level of the approval process must approve the agreement requirement before the amendments are transferred to an agreement or before the requirement is transformed into a new agreement. If the requirement of the agreement is rejected during the approval process, the agreement requirement will continue to be kept in the workbench of the association appeal.

To activate the check sheets, the types of models must be identified as relevant to the fact sheet when setting up price agreements. Check sheets are also configurable for templates and clauses, instead of displaying only tabs and rules configured in order. NOTE: The agreement can be incorporated into the SAP condition contract. In the configuration, assign the type of packaging contract to the type of contract to store information in the packaging contract. Vistex`s root requirement combines several price elements for analysis in a single workbench. In a master`s application, „editions“ can be created to track changes in rules and reservations. However, if you need the ability to differentiate between offers and offers or to track changes to legally binding documents, you can use the master`s contract to change a master`s requirement with complete follow-up. The sales rebate agreement is integrated into the system using the Workbench-Booking agreement. The agreement agreement is used to establish and modify the terms of each sales rebate agreement.

Data generated in the Workbench is stored in SAP`s default packaging contract tables. The root chord uses the same configuration as the master requirement, except that the use is a master contract and the values are entered for the types of revision. Agreement requirements can be configured to simultaneously authorize multiple open requirements or to allow only one requirement per type of agreement requirement, based on the organization`s requirements. An organization can, for example. B limit the number of requirements per type of agreement, which can be opened simultaneously, so that each change request is verified before a new requirement can be proposed.