Best Of

Hi @Red Velasco-Oracle,
I used the script solution and it worked 😊(except I store the location internal id itself in a custom field and I was able to reference the address fields on this new location custom field on the PDF)
Thank you!

Hi,

We found out that it was cache error. Nothing is changed from our side and error disappeared after a day.

Thank you all for your help!

Zeynep

It does allow multiple operators to work in the same operation, however the run time is captured under the operator who started the run for the operation. It will not have the run time broken down by operator.

Hi @User_VW1KQ

This is expected behavior in Advanced PDF/HTML templates. The item line field ${item.location} can display the location value/name correctly, but it does not reliably expose the full related Location record fields, such as city/address, per line.

That is why ${item.location.city} keeps returning the same city or the first location’s city. The template is not really doing a fresh lookup of the Location record for each item line.

For this requirement, yes, a script is usually the cleaner approach.

The common solution is:

1. Use a User Event script on the Sales Order.
2. Loop through the item lines.
3. Get each line’s location internal ID.
4. Look up the Location record address fields.
5. Store the needed address/city values in custom transaction line fields.
6. Reference those custom line fields in the Advanced PDF template.

Example concept:

var locationId = rec.getSublistValue({

sublistId: 'item',

fieldId: 'location',

line: i

});
var locationInfo = search.lookupFields({

type: 'location',

id: locationId,

columns: ['city', 'state', 'zip']

});

Then populate custom line fields such as:

custcol_location_city

custcol_location_state

custcol_location_zip

And in the PDF:

<#list record.item as item>
  <p>${item.location}</p>
  <p>${item.custcol_location_city}</p>
</#list>

So the issue is not the loop itself. The limitation is that the template can display the line location, but it cannot reliably pull the related Location record address fields per line. Storing the values on the line first is the safest approach.

Hope this helps.

aah I found SuiteAnswer ID26791.. gonna try this

Hi @Mary Rivas

Tigran is correct, Invoices and Credit Memo will automatically create their own Revenue Arrangements.

If both the Invoice and Credit Memo are generated from the same Subscription and contain the same ARM-enabled item, they are typically included in a single Revenue Arrangement.

However, if the Credit Memo is created as a standalone transaction (not generated from the Subscription), it will generally create a separate Revenue Arrangement.

Hey @Mary Rivas,

The most common configuration is for the Invoice and Credit Memo to create their own Revenue Arrangements. The Credit Memo typically has a negative amount and reverses the revenue.

Hi Angela

Thanks for the reply. The Vendor Bill was paid.

My colleague found a relevant workaround solution from Suite Answer 90906.