The Organization tab fields are used to illustrate all the organizational data associated with the agreement. If the creation of a new agreement and validity is changed from 01/01/20xx to 04/01/20xx and the validity is 12/31/20xx (same year as the Valids), this automatically changes the duration of the contract from 365 days to 275 days. The Review Type drop-down list is a fixed field associated with the status of an agreement request. Below are the ways to view the list of revisions: The control number is a free text field used only for information purposes. TerminationRsn is used to assign a reason for termination of an agreement in the event of termination, i.e. “customer request,” “sales management request” or “non-operating business.” Replacing 1 is either automatically replenished in the instance where Fast Replace was used, or allows the user to manually replace a specific clause with a clause manually added in the agreement. This analysis is only done if the appropriate configuration for the text search procedure and access sequence is available. A chord can be copied from the change or display mode. There are improved margins due to current discount and price calculations. In the pricing procedure just above the net value of the item, we specify a sub-total basis for “discounts” by indicating the value “7” for the “sub-total” field that updates the discount base in the “KOMP” table and the “BONBA” field. Payment procedure: Indicates whether the discount should be paid up to the anticipated value or if there is no limit to manual payment.
Sales discount agreements are implemented as sales contracts using standard price functionality. The IP module uses the same price architecture used for orders, billing documents and purchase documents. This means that the types of packaging, access sequences and access conditions can be reused at the same time as other IP request documents while the sales are processed. Create the “partial discount compensation” (credit) billing document in reference to the “partial compensation requirement” using the “VF01” reservation code. The type of contract indicates the type of agreement used for the respective IP application. There may be one or more types of agreements for sales discounts, and the corresponding type is chosen when the agreement is created. To see the errors, the user must display them himself in the Rules tab or try to save the agreement with a rule error on them. The type of date indicates different types of dates that can be tracked with respect to contract bookings. For example, it is possible to keep a type of date for “re;renewal notification” in order to track and report on processing times related to the extension of the agreement. Note: If it is a customer discount, the condition rate is maintained for the payer. Final count: Here we must indicate the “B1” file to create Belegra`s discount credit requirement, while the final tally is final to the debitor.
Version 000 is copied from the model. It`s the original version. When new versions are created, the system automatically assigns the version number accordingly. Whatever version the user says in the agreement when the user creates a new version, that version should be the source version. Territories can be derived on the basis of an agreement based on the individual rules or terms of the agreement. In the configuration, the condition search logic is defined and assigned to a type of agreement. Logic uses information that is present in contractual rules, such as Z.B. Customer and hardware, to find and extract territory information that relates to that customer and/or material. The derived territorial information is then filled in the Territories tab.
This information can then be used for the search for appropriate funds or for the management/ownership of the agreement.