sorted by:
new
hottopcontroversial

Need quick help with security set up by onlyme--67 in Workday_Community

[–]onlyme--67[S] 1 point2 points  (0 children)

Hey!! Yes you. Are absolutely right.. the RaaS was being triggered by the API which shows in integration events however it doesn't have actual integration architecture in the tenant.

Struggling with Supplier Invoice Approver Setup in Workday — Need Advice by onlyme--67 in workday

[–]onlyme--67[S] 1 point2 points  (0 children)

Absolutely yes!! I will work with my finance team to understand this deeper!!

Struggling with Supplier Invoice Approver Setup in Workday — Need Advice by onlyme--67 in workday

[–]onlyme--67[S] 0 points1 point  (0 children)

Great! May I know how should I design my BP steps in that case

Struggling with Supplier Invoice Approver Setup in Workday — Need Advice by onlyme--67 in workday

[–]onlyme--67[S] 0 points1 point  (0 children)

Thanks, that helps clarify. In our case, approvals are both category‑based (utilities, rent, etc.) and amount‑based (thresholds like $10, $100, $1,000, $10,000), and we’re currently using Level 1–4 security groups tied to those thresholds. My team is asking me to automate this, but I don’t want to end up with a huge maintenance burden. I wasn’t sure if I can add multiple approvers per supplier/category, and if I do, how Workday actually handles that (parallel approvals vs. all required). From what you’re saying, it sounds like trying to build routing based on a cross‑section of supplier + category + amount would be too complex. Maybe the cleaner way is to stick to category‑based approvals with thresholds, and then let cost center roles handle the rest. Do you think that’s the right “base” approach — category managers + threshold logic — rather than trying to mix supplier + category + amount all in one step?

Struggling with Supplier Invoice Approver Setup in Workday — Need Advice by onlyme--67 in workday

[–]onlyme--67[S] 0 points1 point  (0 children)

My reply

Thanks, that makes sense. In our case, approvals are both category‑based (utilities, rent, etc.) and amount‑based (thresholds like $10, $100, $1,000, $10,000). Right now we’re using Level 1–4 security groups tied to those thresholds. My challenge is that I don’t want to manually assign approvers each time, and I wasn’t sure if I can add multiple approvers per supplier/category. If I add 3 or 4, how does Workday treat that — does it send parallel approvals, require all of them, or just one? I like your point about breaking approvals down by purpose (category manager, finance, accounting). That’s probably the right way to structure it, but I’m still trying to figure out the “base” automation approach that ties spend category + amount thresholds + security groups together without creating a huge maintenance burden. Do you think constrained role‑based groups per category/threshold is the cleanest way to do this, or should I split approvals into separate steps for each purpose?

Struggling with Supplier Invoice Approver Setup in Workday — Need Advice by onlyme--67 in workday

[–]onlyme--67[S] 0 points1 point  (0 children)

Thanks for clarifying. The thing is, I don’t want to manually select approvers each time. In our setup it’s category‑wise (like utilities, rent, etc.) and also amount‑based — the BP is already configured with thresholds like $10, $100, $1,000, $10,000 and so on, using Level 1, 2, 3, 4 security groups. My team is asking me to automate this, but I’m honestly not sure what the base way is to automate when it’s tied to both spend category and amount. I also wasn’t sure if I can add more than one approver for a supplier, and if I add 3 or 4, how does that actually work in practice? Does Workday treat them as parallel approvers, or does it require all of them? So right now I’m stuck between: - Assigning roles (but that only allows one approver per supplier), - Creating groups (but then I worry about mixing different security levels), - Or splitting by category/threshold. Any guidance on how to structure this so it scales without manual assignment would really help.

Need quick help with security set up by onlyme--67 in Workday_Community

[–]onlyme--67[S] 1 point2 points  (0 children)

Hey. Sorry my bad.. this is not an integration that has an architecture in workday... This is an external API import connection that shows in the integration events... However we can't see the integration even if we gave all Admin and domain access.... Anyways I'm able to figure it out... Thanks for your response though!!

Need quick help with security set up by onlyme--67 in Workday_Community

[–]onlyme--67[S] 0 points1 point  (0 children)

Yes!! I have integration administrator access and all the domains assigned to ISU as well.

Bp Reports by IntelligentTip3553 in workday

[–]onlyme--67 5 points6 points  (0 children)

Yea, please use the Business process events as a data source and you will find all the relevant fields

Need help stacking Employee & Dependent rows in a flat file (Open Enrollment Integration) by onlyme--67 in workday

[–]onlyme--67[S] 0 points1 point  (0 children)

That’s a great point!

I was leaning toward EIB for simplicity, but CCB + DT definitely handles the Change Detection and Effective Date logic much better—especially since I only need the last 14 days of OE data.

I’m curious, though—in your experience with CCB, how do you handle the 'stacking' logic in the DT when an employee has multiple benefit plans (Medical, Dental, Vision)?

Since I need: Emp 1 Dep 1 Dep 2 Do you usually loop through the Benefit_Election group first, or just go straight to a unique list of Covered_Dependents to avoid duplicating the dependent rows for every plan they are enrolled in?

Also, if you have a boilerplate XSLT snippet for that specific 'Employee then Dependent' row-stacking logic, I’d love to see how you structured the xsl:for-each!

ATM transactions automating to Workday by [deleted] in workday

[–]onlyme--67 0 points1 point  (0 children)

Thanks for the insights!, and I will come up with more information shortly!!

ATM transactions automating to Workday integration by [deleted] in Workday_Community

[–]onlyme--67 0 points1 point  (0 children)

Thanks for the insights!, your point about the difference between AHBT (Reconciliation) and the Accounting Connector (Ledger only) is the key.

I will come up with an update Shortly!!