| Description |
Requirement:
1. when starting a ticket with selecting a contract or load, it will assume the contract/laod is the delivery customer who will be getting the IR/IS and eventrual Voucher or Invoice. If the customer is changed on the ticket screen, that will change the IR/IS and voucher/invoice.
2. when changing the apply to contract (on the ticket or in the manual distribution) then as noted in 1, the IR/IS remains with the ticket customer/vendor selected but the contract rules (like discounts, fees), prices and units come off of the selected contract. There are many cases this can be true, especially when families. A son brings in a load of corn, wants to be paid, but uses his fathers contract so help furfill that obligation to the elevator.
EG:
Mike has a contract with Pete to deliver 10000 bushels of Corn at 3.50 using discount code 10.
Mike purchases 1000 bushels of Corn from Phil on an inbound ticket.
Phil applies his units to Pete's contract.
Petes contract goes -1000 units on open units and is no 9000.
Phil recieves payment based on the discount schedule and dollar amount of Pete's cnotract of 3.50 per bu assume no discounts.
NOTE: We did not restrict use of any contract by a setting. However, in origin, this was not part of a look up and table, they had to know the contract number to apply to. Though there are ways around that so I'm sure that some companies have used customer inquiry or something to find the contract number rather than enforcing it. If a setting to lock this down is needed, I'm not against it but it may be something by customer or by locations or scales. It depends if it is a "business rule for the elevator to allow it" or if it is "a customer allowing or stopping others applying" to the contracts.
|