1 24 25 26
0

Customer Pricing Customization – Driven by “MarkUp” Based on Unit Cost

  • 28 February 2012
  • cre8
  • 0 Comment

Requirement: Customer Pricing is driven by ‘markup” based on a unit cost, either from the system or entered manually (special pricing from a Supplier). The Special Pricing from the Supplier is known at the time of Sales Order placement, but needs to be passed to the PO Suggestion for the buy to order or make direct release, so that the costs are assigned to the correct shipment. Price lists will not be used- each order will be treated as a…

0

Delivery of EFT in SWIFT Format Customization

  • 21 February 2012
  • cre8
  • 0 Comment

Requirement: electronic payments (EFT – Electronic Transfer of Funds) in SWIFT format, including e-signature. This is used for many electronic transfers of funds, primarily international transfer. The configuration requirements are specific and detailed, but once complete, require no update. Included in the configuration are several user codes for management of acknowledgement and error messages, as well as several new used defined fields for management of A/P payments. This project also required confirmation of approval, though the approval process itself was…

0

Warehouse to warehouse transfer with Landed cost applied Customization Delivered

  • 10 February 2012
  • cre8
  • 0 Comment

Transfer order from one warehouse to another in the same plant requires that freight costs be disbursed and added to the material cost of a part being transferred, and the material be accounted for as “in transit”. The transfer will have all of the required functions of planning a truck for any shipment, including selection of a trucking supplier, setting a due date for the shipment, selecting a part and quantity to be transferred, a ship-to warehouse (and therefore the…

0

Training for Suppliers, Customers, as well as Employees Customization Delivered

  • 10 February 2012
  • cre8
  • 0 Comment

A customization was created to auto assign an existing but Reusable Non-Payroll Employee Record when a Course is requested for a Supplier or Customer Person/Contact. When user clicks the ‘Course Request’ button on the Case Entry form or from Course Request Entry, the system will determine if the person to take the course is a Supplier or Customer. If so, then the system will create a Reusable Non-Payroll Employee record and display the Supplier / Customer information (Type, ID, Name)…

0

Tax reporting – Refundable Tax Delivered to Customer

  • 10 February 2012
  • cre8
  • 0 Comment

Some states and countries have refundable taxes collected, and these need to be reported. One reporting requirement is system calculated tax where a manually calculated tax was applied. This comparison allows errors to be defined more readily, and assists in the reconciliation process. A new report was generated to show taxes in both forms- system calculated, and the actual manual tax applied. A customization was required to support reporting, though no change to the User Interface was made. Taxes by …

1

Job Scheduling and Dispatch Customization – Delivered to Customer

  • 10 February 2012
  • cre8
  • 1 comment

The customer requires the ability to see all open Projects displayed as “Cards” in a dynamic scheduling board, with all open project phase jobs listed, as well as certain resource types (Vehicles and Technicians are used in the example) that can be “dragged and dropped” into each project/ job. Also, colors are needed to highlight technicians or vehicles that are not available, or have been scheduled previously, using Production Calendar to mark non-working days. Also required is the capability to…

3

Cycle Count Customization – Delivered to Customer

  • 10 February 2012
  • cre8
  • 3 comment
Categories: Epicor

Standard EPICOR 9 cycle count is a very stringent process, with many complex steps. The customer requires the ability to create a cycle count “on the fly”- a single user selects the count schedule, adds parts by part class, warehouse, or zone, generates tags, prints tags, and starts the count all as a continuous process. Close adherence to standard functionality is required, for the completed cycle count must use the standard Tag Entry transaction and Variance report. Per standard E9 process, cycle…


1 24 25 26

Popular posts

Featuered posts

Categories