Brad Teague
- Total activity 70
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 10
- Subscriptions 23
Comments
Recent activity by Brad Teague-
We primarily need the Company Code, but there are other worktags that we need to identify the purpose of the purchase order line.
-
No. This is a request to add Purchase Order Type the Purchase Order table, thus the screen capture. Nothing to do with Supplier Invoice.
-
Correction: There is a Status column in the Line detail that is always available.
-
-
If that is the case, the destination column should be CODE or LEDGER_ACCOUNT_CODE. ID in most of the other tables, if not every other table, in your schema is the Workday ID, specifically in the JO...
-
Clarification: This column may be RESOURCE_CATEGORY rather than SPEND_CATEGORY and can be combined with a similar Connector Improvement: Workday Financial Management PURCHASE_ORDER_SERVICE_LINE mis...
-
Nothing is resolved. The guidance in your schema is invalid. The following query returns no results. I assume you are just asking us to defer to the newly announced Workday Data Cloud to cover gaps...
-
Just confirming, I should expect the new OPERATIONAL_TRANSACTION_ID and OPERATIONAL_TRANSACTION_REFERENCE columns in the JOURNAL_ENTRY table to accommodate this request?
-
The Community P&L (Standard Report) in Workday has a "drill report" when you click on the Actuals that displays Journal Entry details with two columns: Journal Number and Purchase Order or Supplier...
-
See REVENUE_CATEGORY_NAME in your REVENUE_CATEGORY table.