Phew, after many late nights and early mornings, we have our JD Edwards digital platform at version 1.0.
We developed complete MCP servers for JD Edwards orchestration and AIS and then needed to wrap them up with some more prescriptive functionality, so our container based AI powered digital workforce is here.
You can drill down to any JD Edwards expert from the front page, or just start talking... Each expert has been trained on everything that the internet has to offer and the solution also has a RAG based knowledge system which you can add your custom documentation too - or just rely on the standard JDE doco that we have vectorised for you.
You can see that once you choose and expert there are some intuitive (and configurable) operations that are available immediately. In my example I chose the AP expert - it's book smart and connected to my JD Edwards!
Critical Setup Tables and Configuration for Accounts Payable Module
Based on my analysis of the live JDE system, here are the essential setup requirements for the AP module:
1. CRITICAL AAI (Automatic Accounting Instructions) - F0012
PC - Trade Accounts Payable (MANDATORY)
- Purpose: Controls the liability account for all vouchers
- Standard Account: 4110 (Trade Accounts Payable)
- Critical Configuration: Must be set for each company
- Failure Impact: Voucher posting will fail without PC AAI
From the system data, I can see PC AAI is configured across multiple companies (00001, 00028, 00050, etc.) primarily using account 4110.
Other Critical AP AAIs:
| AAI | Description | Purpose | Account Type |
|---|---|---|---|
| PCM | AP Clearing | Matching/clearing account | Asset |
| RT | Cash Account | Payment posting | Asset |
| 4310 | GRNI (Received Not Invoiced) | Purchase receipt liability | Liability |
2. AP Constants Table - F04001 (If Available)
⚠️ CRITICAL SETUP FIELDS:
| Field | Description | Setup Requirement |
|---|---|---|
| DCAN8 | Company Address Number | Valid address book number |
| DCPST | Default Pay Status | Match approval workflow (blank/A/#) |
| DCDPF | Duplicate Checking | MUST BE 'Y' (Error or Warning) |
| DCEDI | Allow EDI Override | Security control |
| DCGLBA | Default Bank Account | Valid GL bank account |
| DCEDIT | Edit Supplier | MUST BE 'Y' |
| DCPTC | Default Payment Terms | Standard terms code |
| DCTXA | Default Tax Area | Correct tax jurisdiction |
| DC1099 | 1099 Processing | 'Y' for US companies |
3. Supplier Master Configuration - F0401
MANDATORY FIELDS FOR EACH VENDOR:
| Category | Fields | Critical Settings |
|---|---|---|
| Payment Control | HDPY, HOLD | Payment holds ('Y'/'N') |
| Payment Method | PYIN | Check/EFT/Wire/ACH |
| Tax Reporting | TRAP, A61099 | Tax ID + 1099 code |
| Default Terms | PTC | Payment terms code |
| Banking | GLBA | Bank account for payments |
4. Payment Terms Master - F04575
REQUIRED TERMS SETUP:
| Field | Description | Business Rule |
|---|---|---|
| PTPTC | Terms Code | Unique identifier |
| PTDSC | Discount % | Early payment discount |
| PTDDD | Discount Days | Days to earn discount |
| PTNDD | Net Due Days | Payment due days |
| PTDP | Date Pattern | Due date calculation method |
5. UDC Codes (F0005) - CRITICAL CONFIGURATIONS
UDC 00/DT - Document Type
PV - Standard Voucher
PM - Manual Payment
PW - Automatic Payment
PD - Debit Memo
PP - Prepayment
UDC 00/PS - Pay Status
(blank) - Pending Entry
# - Pending Manager Approval
% - Pending Reapproval
A - Approved (ready to pay)
H - Hold
P - Paid
D - Draft
V - Void
UDC 00/PY - Payment Instrument
C - Check
D - Draft
E - EFT
W - Wire Transfer
A - ACH
UDC 00/1099 - 1099 Reporting Types
M - 1099-MISC
N - 1099-NEC
I - 1099-INT
D - 1099-DIV
6. Processing Options - CRITICAL SETTINGS
P0411 - Standard Voucher Entry
- Duplicate Invoice Checking: Error or Warning (not Bypass)
- Supplier Validation: Error level
- Auto Next Number: Enabled
- Default Pay Status: Match workflow
P04575 - Create Payment Groups
- Pay Status Selection: 'A' (Approved)
- Bank Account: Valid account
- Payment Format: Match bank requirements
7. MANDATORY TABLE RELATIONSHIPS
F0401 (Supplier Master) → F0101 (Address Book)
F0411 (AP Ledger) → F0401 (Supplier Master)
F0411 (AP Ledger) → F04575 (Payment Terms)
F0012 (AAIs) → Chart of Accounts
8. VALIDATION CHECKLIST
✅ MUST VERIFY:
- PC AAI exists for every company - Voucher posting fails without it
- Supplier Master completeness - Payment method, terms, tax setup
- Payment Terms accuracy - Discount rates and days
- UDC code completeness - All status codes defined
- Processing Options alignment - Match business rules
- 1099 compliance - Tax IDs for reportable vendors
🚨 FAILURE POINTS:
- Missing PC AAI = Voucher posting failure
- Missing payment method = Payment processing failure
- Missing 1099 setup = Tax compliance failure
- Incorrect terms = Cash flow impact
This configuration framework ensures proper AP module operation, financial accuracy, and regulatory compliance.
So a simple prompt get's a comprehensive result!
You can discover and call orchestrations, call BSFN's run reports AND interpret the PDF results with AI! And more and more and more.
You can see how simple questions get comprehensive answers...
The functionality is incredible and drives productivity.
The enxt view we have is the custom agent builder:
This allows our customers to create individual, purposeful and proactive agents to process JD Edwards transactions autonomously. We have provided the tools for you to create your agentic workforce. Choose the module, discover the data and orchstrations and then define the business rules!
You can then export your agent definitions to claude or copilot and get them working for you.
My favourite feature is creating the agents from a functional specification:
You can see I am able to drag a functional specification into this portal and it will reverse engineer all of the JDE tables, reports and orchestrations needed to support the agent definition! Pretty cool.
Let me know what you think, we are carefully choosing the first round of customers and the demand is high! People can see the potential. This has been amazing for AI literacy too, enabling people to chat with JDE and build out complex automations over time.
No comments:
Post a Comment