Right now, I am working with one of the home builder technologies. JD Edwards World ( /products/jd-edwards-world-reviews ) is being used as a part of job costing. There are multiple interfaces wherein sales are getting captured, which get migrated to JD Edwards World ( /products/jd-edwards-world-reviews ). For payment, it is the same. Contracts are also getting captured in another interface, which gets migrated to JD Edwards World job cost. So, it is a completely integrated and customized system as of now.
I have two different kinds of customers. One produces mass market goods like toilet paper and similar products. The other operates in the food environment, producing food packages for retailers. Both customers use JD Edwards World in their infrastructure, implementing it on-premises rather than on the cloud.
We primarily use the solution for manufacturing, with bills and routings. We use configured products almost exclusively. A bill configurator is a must. The product we sell is highly configurable. We need the ability to generate a bill by doing a callout as we know it. Our manufacturing facility would shut down without this. There are hardly any errors today, however, the errors we do find are in the modified code in JD World. Some functionality is not utilized. We need to understand what our current solution offers and what we need to have in a new solution.
Oracle's JD Edwards World single platform solution enables better collaboration both within and outside your business network. Get all of your lines of business working together sharing information, boosting performance, trimming costs, and driving profitable growth. ERP Suite.
Right now, I am working with one of the home builder technologies. JD Edwards World ( /products/jd-edwards-world-reviews ) is being used as a part of job costing. There are multiple interfaces wherein sales are getting captured, which get migrated to JD Edwards World ( /products/jd-edwards-world-reviews ). For payment, it is the same. Contracts are also getting captured in another interface, which gets migrated to JD Edwards World job cost. So, it is a completely integrated and customized system as of now.
I have two different kinds of customers. One produces mass market goods like toilet paper and similar products. The other operates in the food environment, producing food packages for retailers. Both customers use JD Edwards World in their infrastructure, implementing it on-premises rather than on the cloud.
We use the solution for HR, maintenance, finance and supply chain.
I use JD Edwards for warehouse management and item tracking, recording the movement and history of artifacts in our ecosystem.
We use the solution for managing sales, warehouse, manufacturing process, etc.
We primarily use the solution for finance, procurement, and capital asset management, among other things.
We use the product for operations as well as for finance. The World application that we use as a finance ledger.
We primarily use the solution for manufacturing, with bills and routings. We use configured products almost exclusively. A bill configurator is a must. The product we sell is highly configurable. We need the ability to generate a bill by doing a callout as we know it. Our manufacturing facility would shut down without this. There are hardly any errors today, however, the errors we do find are in the modified code in JD World. Some functionality is not utilized. We need to understand what our current solution offers and what we need to have in a new solution.
We are using JD Edwards World as our core backbone for our retail business in distribution and accounting.
I'm using the solution for financials, taxes, supply areas, and backup functionalities.
With the World version, we use the finance module, distribution module, and the manufacturing module.
A global system with a local presence and intercontinental communication. It provides us with a common language, product, and customer base.