Has anyone had a requirement on Automating a sales price list number?

1. Create a Number Counter (sequence source)

• Page: Number Counters

  1. Go to Document Management > Basic Data > Number Counters.

  2. Click New and create counter, e.g. PL_SEQ.

  3. Set: Prefix (PL-), length/padding (e.g. 6), start value (1), and save.​

This will generate values like PL-000001, PL-000002, etc.

2. Identify the Configuration Price List entity

• Page: Configuration Price List

  1. Open Sales > Sales Prices > Configuration Price Lists (name may be exactly Configuration Price List).​

  2. Use Page Actions > About / Technical Info (or similar) to see:

     • Logical Unit: e.g. Configured_Price_List (exact name from tech info).

     • Projection name used in Aurena.

You will use this LU in the custom logic step.

3. Add custom logic to assign the number (25R2 Extensions)

Your IFS developer/partner does this in Custom Logic:

• Page: Custom Logic

  1. Navigate Solution Manager > Configuration > Application Configuration > Custom Logic.

  2. Create a new Server Script for LU Configured_Price_List.

  3. Hook on event BeforeInsert (or OnNew) so it runs when a new configuration price list is created.

  4. In the script, call Document Management’s API for your counter, e.g.:

     • Doc_Number_Counter_API.Get_Next_Value('PL_SEQ') (exact API/namespace from tech docs).​

  5. Assign the returned value to the key field (or a custom field), e.g.:

     • Price_List_No := <returned value>;

Save and activate the script for the relevant companies/contexts.

4. Control field behavior on the page

• Page: Configuration Price List

  1. Open Solution Manager > Configuration > User Interface > Page Designer.

  2. Select the Configuration Price List page.

  3. For field Price List No (or your custom sequence field):

     • Ensure it is visible.

     • Optionally set it to Read‑only for normal users so they cannot change the generated value.

5. User flow in 25R2

• Page: Configuration Price List

  1. User clicks New to create a configuration price list.

  2. On save, the Custom Logic calls the Number Counter PL_SEQ and writes the next number into Price List No.

  3. User completes the rest of the configuration; the sequence‑based key is already in place and unique.

Thanks ​@TntAnnmaS will check this :)