Hi @Lakna K,

Pseudo codes are defined to use as a quick code for code part combinations and Code string completion is used to default a second code part value when using a primary code part.

For example, If you have recurring expanse entry or voucher entry which has same code part combinations then you can define a unique Pseudo code ID for this combination. Then as soon as you entered this Pseudo code in the entry it will automatically fill out the Code Part details connected to that Pseudo code.

As a example for Code string completion, let’s say if you want to always default a secondary code part value when using an GL account (ie. Cost Center), in this case you can define a Code string completion record for that particular GL account. So whenever you used this GL account in a transaction application will automatically post the secondary code part value in the transaction.

Both these functionalities are used to enter code part combinations easily and quickly in a transactions. But none of them are mandatory setups and can be used based on users’ preferences.

Hope this will help.

Regards,

Akila

Thanks @AkilaR . This is insightful!

Would be interested in the differences of the two? Are there scenarios where one is better/worse? Or do they both function the same?

Hi @DV - JL ,

I wouldn’t say these two functionalities are same. But both of them have similar usage. While Pseudo code is used to enter combination of code parts whenever you required in a transaction, Code string completion is used to always default a secondary code part when using the main code part value. So these two functionalities will be used in two different scenarios.

As I mentioned in the previous response, Pseudo codes are mainly used when there are recurring transactions such as expenses or journal entries where you need to record same code part values in a transaction. So that user just only need to enter the code in a code part column and application will automatically update the corresponding code part values in the transaction. In the Code string completion, secondary code parts will always get updated when you enter the main code part value in the transaction. This is the main difference between these two options. 

You can use these two options in different scenarios based on your preferences. For example when you create a Expense entry in a supplier invoice and if it is the same code part combination is being used in every time then you can use Pseudo code. And if you want to use a fixed Cost Center code part value whenever you use specific Cost Account in all the transactions that this account is being used then you can use ode string completion option. Based on the situation and your preference you can select which options to be select.

Hope this help.

Regards,

Akila

Thanks for the reiteration. I guess in the past I have used code string completion just like you are describing the use for pseudo codes, and we just filled out our entire code string with it, not just one code part. Of course you can override and update if needed. Thanks again!