# 🍿 Manifest Billing Pay Flag - Descriptions

**URL:** <https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550>\
**Category:** Kinetic ERP\
**Tags:** dumpster-fire\
**Created:** [June 11, 2025, 9:00pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550 "2025-06-11T21:00:29Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![kve](https://www.epiusers.help/user_avatar/www.epiusers.help/kve/32/76150_2.png) [@kve](https://www.epiusers.help/u/kve)\
**Post date:** [June 11, 2025, 9:00pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/1 "2025-06-11T21:00:29Z")

</div>

Anyone know where these are stored? There are about 15 of them in the PayFlag (“Billing Type”) options, but I don’t have a reference for the description =\> value. Trying to get the description to print on an SSRS form.

---

<div class="post-metadata">

**Author:** ![aosemwengie1](https://www.epiusers.help/user_avatar/www.epiusers.help/aosemwengie1/32/95533_2.png) [@aosemwengie1](https://www.epiusers.help/u/aosemwengie1)\
**Post date:** [June 11, 2025, 10:51pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/2 "2025-06-11T22:51:58Z")

</div>

Pretty sure these are just hardcoded in the application.

---

<div class="post-metadata">

**Author:** ![chaddb](https://www.epiusers.help/user_avatar/www.epiusers.help/chaddb/32/89855_2.png) [@chaddb](https://www.epiusers.help/u/chaddb)\
**Post date:** [June 12, 2025, 2:58pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/3 "2025-06-12T14:58:08Z")

</div>

Correct. Hard coded and can’t be changed. And several aren’t even supported anymore in Quick Ship.

---

<div class="post-metadata">

**Author:** ![jgiese.wci](https://www.epiusers.help/user_avatar/www.epiusers.help/jgiese.wci/32/51553_2.png) [@jgiese.wci](https://www.epiusers.help/u/jgiese.wci)\
**Post date:** [June 12, 2025, 2:59pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/4 "2025-06-12T14:59:32Z")

</div>

I created a UD code list with the same codes as the ones hard coded into the system. I then only created the ones that we use. Replaced the combos in key screens with the UD codes with our specific pay flags we want and the descriptions we want.

---

<div class="post-metadata">

**Author:** ![chaddb](https://www.epiusers.help/user_avatar/www.epiusers.help/chaddb/32/89855_2.png) [@chaddb](https://www.epiusers.help/u/chaddb)\
**Post date:** [June 12, 2025, 3:00pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/5 "2025-06-12T15:00:09Z")

</div>

How does that work with Quick Ship? The QS integration looks at only the default fields I think.

---

<div class="post-metadata">

**Author:** ![jgiese.wci](https://www.epiusers.help/user_avatar/www.epiusers.help/jgiese.wci/32/51553_2.png) [@jgiese.wci](https://www.epiusers.help/u/jgiese.wci)\
**Post date:** [June 12, 2025, 3:01pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/6 "2025-06-12T15:01:28Z")

</div>

I am using the native PayFlag column and the codes themselves, that are sent to QuickShip, are all the same as the base ones. I just have a limited set and my own descriptions.

 ![image](https://www.epiusers.help/uploads/default/original/3X/2/7/27e33fe464c4ea07d435a26829905cd58dfbd993.png)

Base field list

 ![image](https://www.epiusers.help/uploads/default/original/3X/8/2/82b5a5f3c451aa2c88ec54e90a54f43daaddcab2.png)

---

<div class="post-metadata">

**Author:** ![chaddb](https://www.epiusers.help/user_avatar/www.epiusers.help/chaddb/32/89855_2.png) [@chaddb](https://www.epiusers.help/u/chaddb)\
**Post date:** [June 12, 2025, 3:03pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/7 "2025-06-12T15:03:11Z")

</div>

Oh, duh. I was thinking custom field not just changing the code list. Nm on that lol

Great solution. Right now we just have warnings not to use the ones that aren’t supported. I like switching that to a Ud code list.

---

<div class="post-metadata">

**Author:** ![kve](https://www.epiusers.help/user_avatar/www.epiusers.help/kve/32/76150_2.png) [@kve](https://www.epiusers.help/u/kve)\
**Post date:** [June 12, 2025, 3:28pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/8 "2025-06-12T15:28:25Z")

</div>

Does that list include only the ones supported by QuickShip? That was my next task. I was thinking I’d filter the DataView in App Studio, but I like your solution better.

---

<div class="post-metadata">

**Author:** ![jgiese.wci](https://www.epiusers.help/user_avatar/www.epiusers.help/jgiese.wci/32/51553_2.png) [@jgiese.wci](https://www.epiusers.help/u/jgiese.wci)\
**Post date:** [June 12, 2025, 3:47pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/9 "2025-06-12T15:47:39Z")

</div>

I’m not sure what is all supported by QuickShip we just setup the UD codes with the ones we knew we needed and that was it. If you wanted to be a super hack you could just go modify the list in the database directly.

I can say that cause #OG but not a newb move for sure. Always have a backup plan.

 ![image](https://www.epiusers.help/uploads/default/original/3X/f/f/ffa687d62c215b03f1c1c7545c6f79c92955d260.png)

---

<div class="post-metadata">

**Author:** ![chaddb](https://www.epiusers.help/user_avatar/www.epiusers.help/chaddb/32/89855_2.png) [@chaddb](https://www.epiusers.help/u/chaddb)\
**Post date:** [June 12, 2025, 4:00pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/10 "2025-06-12T16:00:26Z")

</div>

Here’s what Epicor will share as supported by QS.  
[EpicorQuickShip.BillingTypeDefinitions.pdf](https://www.epiusers.help/uploads/short-url/v6K4vstwoC5jMUIfnKBQtbMwn37.pdf) (51.4 KB)

---

<div class="post-metadata">

**Author:** ![jgiese.wci](https://www.epiusers.help/user_avatar/www.epiusers.help/jgiese.wci/32/51553_2.png) [@jgiese.wci](https://www.epiusers.help/u/jgiese.wci)\
**Post date:** [June 12, 2025, 4:39pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/11 "2025-06-12T16:39:21Z")

</div>

Any idea the age of that document? There’s no dates or rev numbers on it of course lol

---

<div class="post-metadata">

**Author:** ![jkane](https://www.epiusers.help/user_avatar/www.epiusers.help/jkane/32/57624_2.png) [@jkane](https://www.epiusers.help/u/jkane)\
**Post date:** [June 12, 2025, 4:42pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/12 "2025-06-12T16:42:56Z")

</div>

This is where they are stored.

> [@Has Anyone Looked Into Customer Manifest Billing in Web UI?](https://www.epiusers.help/t/has-anyone-looked-into-customer-manifest-billing-in-web-ui/107715/8):
>
> You gonna love this one SELECT CodeDescriptionList, \* FROM ice.ZDataField WHERE DBTableName='CustMFBill' AND FieldName='PayBTFlag' You want to add more? Have at it wink (Now I dont know if the new ones you add will have any effect on Manifest…)

---

<div class="post-metadata">

**Author:** ![chaddb](https://www.epiusers.help/user_avatar/www.epiusers.help/chaddb/32/89855_2.png) [@chaddb](https://www.epiusers.help/u/chaddb)\
**Post date:** [June 12, 2025, 4:49pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/13 "2025-06-12T16:49:17Z")

</div>

The KB it’s linked to is old. But it’s what Epicor and the QS guys still reference.

---

<div class="post-metadata">

**Author:** ![kve](https://www.epiusers.help/user_avatar/www.epiusers.help/kve/32/76150_2.png) [@kve](https://www.epiusers.help/u/kve)\
**Post date:** [June 12, 2025, 4:53pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/14 "2025-06-12T16:53:23Z")

</div>

Nice, thank you. Reeeeeally debating editing that, because I can’t get the stupid Kinetic UserCodeCombo re-usable Combo to work on SO Entry.

---

<div class="post-metadata">

**Author:** ![chaddb](https://www.epiusers.help/user_avatar/www.epiusers.help/chaddb/32/89855_2.png) [@chaddb](https://www.epiusers.help/u/chaddb)\
**Post date:** [June 12, 2025, 5:27pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/15 "2025-06-12T17:27:35Z")

</div>

As long as you remember you modified it. May just have to just change it back after an upgrade.

---

<div class="post-metadata">

**Author:** ![kve](https://www.epiusers.help/user_avatar/www.epiusers.help/kve/32/76150_2.png) [@kve](https://www.epiusers.help/u/kve)\
**Post date:** [June 12, 2025, 6:14pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/16 "2025-06-12T18:14:52Z")

</div>

> [@jgiese.wci](#):
>
> I created a UD code list with the same codes as the ones hard coded into the system. I then only created the ones that we use. Replaced the combos in key screens with the UD codes with our specific pay flags we want and the descriptions we want.

So after fighting with App Studio for like an hour, this solution will not work in Kinetic (at least on Sales Order Entry). If your combo is bound to OrderHed.PayFlag, any changes you make to the combo are overridden with the default list. This is including UserCodeCombo or a straight up customized combo box, or even hard coded values.

To work around it, I created a new combo with EpBinding: TransView.TmpPayFlag, and an event to update OrderHed.PayFlag with the value from TransView.TmpPayFlag.

Event Trigger: DataTable ColumnChanged (Table: TransView; Column: TmpPayFlag) → Row Update on OrderHed.PayFlag with the value “{TransView.TmpPayFlag}”

---

<div class="post-metadata">

**Author:** ![josecgomez](https://www.epiusers.help/user_avatar/www.epiusers.help/josecgomez/32/55731_2.png) [@josecgomez](https://www.epiusers.help/u/josecgomez)\
**Post date:** [June 18, 2025, 4:14pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/17 "2025-06-18T16:14:41Z")

</div>

> [@kve](#):
>
> So after fighting with App Studio for like an hour, this solution will not work in Kinetic (at least on Sales Order Entry). If your combo is bound to OrderHed.PayFlag, any changes you make to the combo are overridden with the default list. This is including UserCodeCombo or a straight up customized combo box, or even hard coded values.

So Kinetic makes a call when the App loads that gets All the “default” attributes for a column this is done via the BO

Ice.Lib.ClassAttribute.GetAllAttributesForTables

The response of this call is a list of columns and their default / special attributes one fo them being a code list (referenced above)

 ![image](https://www.epiusers.help/uploads/default/original/3X/f/c/fc3b52b9b1bf2bb7f067a58a0ddc69e9a4ef935a.png)

It also appears that there is a bug (or maybe working as intended) but if a column is bound to a combo and this CodeDescriptionList is populated then Kinetic App will override any behaviors set on App Studio and default the dropdown to this list exclusivelly.

However, someone could if they wanted to put a post processing BPM on  
Ice.Lib.ClassAttribute.GetAllAttributesForTables that checks to see if the key

“erp.orderhed.payflag” is in the response and then one could alter the output of said  
CodeScriptionList (or eliminate it all together, which would let the combo behave properlly when overriden)

 ![image](https://www.epiusers.help/uploads/default/original/3X/4/5/451de3b595ee6ee5e2310016d024892b38d4b314.png)

For now I chose to just “limit” the list to 2 values instead of All of the ones that show up by default

```auto
if(this.result.ContainsKey("erp.orderhed.payflag"))
{
this.result["erp.orderhed.payflag"]["CodeDescriptionList"]="CON`Consignee~FEDCOLL`Fedex Collect~FEDPRE`Fedex Prepaid";
}

```

This yields a much more useful combo

 ![image](https://www.epiusers.help/uploads/default/original/3X/4/8/4854f1a414e48324b96fc068f26936fef8d847f1.png)

Or you can get creative and play with it in other ways 🤐

![PrimeTimeBaby](https://www.epiusers.help/uploads/default/original/3X/8/3/835683accbaa8c788a2a2defcfad1acb54272e90.gif)

---

<div class="post-metadata">

**Author:** ![utaylor](https://www.epiusers.help/user_avatar/www.epiusers.help/utaylor/32/64664_2.png) [@utaylor](https://www.epiusers.help/u/utaylor)\
**Post date:** [June 18, 2025, 5:57pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/18 "2025-06-18T17:57:10Z")

</div>

Just noticed your drop-down selections

---

<div class="post-metadata">

**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\
**Post date:** [June 18, 2025, 7:15pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/19 "2025-06-18T19:15:52Z")

</div>

> [@josecgomez](#):
>
> ![PrimeTimeBaby](https://www.epiusers.help/uploads/default/original/3X/8/3/835683accbaa8c788a2a2defcfad1acb54272e90.gif)

This is @kve, not me but lol, relevant…

Try putting two lowercase `s` in an email…

![EmailValidationSShort](https://www.epiusers.help/uploads/default/original/3X/b/6/b65c3491cf7a5c7d28a87ba538ec740e2d50fe97.gif)

---

<div class="post-metadata">

**Author:** ![josecgomez](https://www.epiusers.help/user_avatar/www.epiusers.help/josecgomez/32/55731_2.png) [@josecgomez](https://www.epiusers.help/u/josecgomez)\
**Post date:** [June 18, 2025, 7:17pm UTC](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550/20 "2025-06-18T19:17:46Z")

</div>

> [@klincecum](#):
>
> Try putting two lowercase `s` in an email…

The heck you going on about?  
 ![Animated GIF](https://media2.giphy.com/media/v1.Y2lkPWU5MGVkYmEzeDdxcmt5aXNzeG5oem16d3ljeGZvaTlxZHdjcjBvc296d284MXh5eSZlcD12MV9naWZzX3NlYXJjaCZjdD1n/3o7aTskHEUdgCQAXde/giphy.webp)

[Next page](https://www.epiusers.help/t/manifest-billing-pay-flag-descriptions/126550.md?page=2)
