| Retrobilled Price Change Advice (tdsls3570d000) |  |
| Use this session to display price change headers that are generated in the Generate Retrobilled Price Change Advice (tdsls3270d000) session. On the appropriate menu you can choose: Lines, to start the Retrobilled Price Change Advice Lines (tdsls3571d000) session. History, to start the Retrobilled Price Change History (tdsls3575d000) session. Note The detailed information that is displayed when you select a record cannot be changed. This information is based on the settings in the Generate Retrobilled Price Change Advice (tdsls3270d000) session when the update was run. However, you can delete a price change header if no price change lines for the header are approved. Related topics Retrobilling
Fields | Description
Update Number | A number that identifies the update run associated with the price-change header. The value of this field is based on the Number Group Update field in the Sales Order Parameters (tdsls0100s400) session.
Sales Order | An agreement that is used to sell items or services to a business partner according to certain terms and conditions. A sales order consists of a header and one or more order lines. The general order data such as business partner data, payment terms, and delivery terms are stored in the header. The data about the actual items to be supplied, such as price agreements and delivery dates, is entered on the order lines.
Sales Order | An agreement that is used to sell items or services to a business partner according to certain terms and conditions. A sales order consists of a header and one or more order lines. The general order data such as business partner data, payment terms, and delivery terms are stored in the header. The data about the actual items to be supplied, such as price agreements and delivery dates, is entered on the order lines.
Contract | Sales contracts are used to register specific agreements with a sold-to business partner about the delivery of certain goods. A contract is comprised of: A sales contract header with general business partner data, and optionally, a linked terms and conditions agreement. One or more sales contract lines with price/discount agreements and quantity information that apply to an item or price group.
Contract | Sales contracts are used to register specific agreements with a sold-to business partner about the delivery of certain goods. A contract is comprised of: A sales contract header with general business partner data, and optionally, a linked terms and conditions agreement. One or more sales contract lines with price/discount agreements and quantity information that apply to an item or price group.
Item | In ERP LN, the raw materials, subassemblies, finished products, and tools that can be purchased, stored, manufactured, sold, and so on. An item can also represent a set of items handled as one (kit), or exist in multiple product variants. You can also define nonphysical items, which are not held in inventory but can be used to post costs or to invoice services to customers. Examples of nonphysical items: Cost items (for example, electricity) Service items Subcontracting services List items (menus/options)
Item | In ERP LN, the raw materials, subassemblies, finished products, and tools that can be purchased, stored, manufactured, sold, and so on. An item can also represent a set of items handled as one (kit), or exist in multiple product variants. You can also define nonphysical items, which are not held in inventory but can be used to post costs or to invoice services to customers. Examples of nonphysical items: Cost items (for example, electricity) Service items Subcontracting services List items (menus/options)
Sold-to Business Partner | Usually a customer's purchase department, the business partner who orders goods or services from your organization, that owns the configurations you maintain, or for whom you perform a project. Details of the agreement with the sold-to business partner can include the following: Default price and discount agreements Sales order defaults Delivery terms The related ship-to and invoice-to business partner
Sold-to Business Partner | Usually a customer's purchase department, the business partner who orders goods or services from your organization, that owns the configurations you maintain, or for whom you perform a project. Details of the agreement with the sold-to business partner can include the following: Default price and discount agreements Sales order defaults Delivery terms The related ship-to and invoice-to business partner
Ship-to Business Partner | The business partner to which you ship the ordered goods. This usually represents a customer's distribution center or warehouse. The definition includes the default warehouse from which you send the goods, the carrier who carries out the transport, and the related sold-to business partner.
Ship-to Business Partner | The business partner to which you ship the ordered goods. This usually represents a customer's distribution center or warehouse. The definition includes the default warehouse from which you send the goods, the carrier who carries out the transport, and the related sold-to business partner.
Invoice-to Business Partner | The business partner to which you send invoices. This usually represents a customer's accounts payable department. The definition includes the default currency and exchange rate, invoicing method and frequency, information about the customer's credit limit, the terms and method of payment, and the related pay-by business partner.
Invoice-to Business Partner | The business partner to which you send invoices. This usually represents a customer's accounts payable department. The definition includes the default currency and exchange rate, invoicing method and frequency, information about the customer's credit limit, the terms and method of payment, and the related pay-by business partner.
Date | The date and time when the order/schedule/contract (line) is changed and/or written to the history file.
Order Origin | The origin of the sales order. This is the value from the Generate Retrobilled Price Change Advice (tdsls3270d000) session when the update was run.
Order Origin | The origin of the sales order. This is the value from the Generate Retrobilled Price Change Advice (tdsls3270d000) session when the update was run.
Update Type | This field specifies the update type. You can add an update percentage or an update amount to change the selected prices during the update run in the Generate Retrobilled Price Change Advice (tdsls3270d000) session. The following options are available: Value: The price change is a fixed amount. Percentage: The price change is a percentage.
Update Percentage | If the Update Type field is Percentage, this field represents the percentage price change. This is the value from the Generate Retrobilled Price Change Advice (tdsls3270d000) session when the update was run.
Update Amount | If the Update Type field is Value, this field represents the amount price change. This is the value from the Generate Retrobilled Price Change Advice (tdsls3270d000) session when the update was run.
Creation Date | The date on which the update number is created.
Currency | If the Update Type field is Value, this is the currency for the value amount in the Update Amount field. Default value If no value is entered, the default value is the local currency. This is the value from the Generate Retrobilled Price Change Advice (tdsls3270d000) session when the update was run.
Logname | The user that started the update run.
Date | The date and time when the order/schedule/contract (line) is changed and/or written to the history file.
Position Number | The number used to identify the position of the order line on the sales or purchase order.
Position Number | The number used to identify the position of the order line on the sales or purchase order.