Ir al contenido principal

Preview of coming transactions



Preview of coming transactions
Did you ever want to see what accounts were going to be hit by the posting of a transaction before you committed it to the General ledger? Maybe, you are setting up a new company and/or product line and want to check the account postings before bringing everything live. You may have newbies and want to review their BP supplier or BP customer invoice coding before the transactions are validated.
In the regular transaction posting process, Sage X3 doesn’t give you a peak at the journal transaction before it hits the General Ledger. I will show you how we can accomplish this preview with the aid of User parameter ACESIMTRC - Simulated entry generation. Let’s look at the posting process and how we can use this parameter.
How do transactions get to the General Ledger in Sage X3?
The Sales, Purchase and A/P-A/R journals as well as manually entered Journals post to the General Ledger in real time.
This means when we post or validate the transaction, a journal is immediately created which hits the General Ledger. I should say hits the General ledger if the Accounting Tasks function is running.
The Production, Fixed Assets, and Stock journals post to the General Ledger via a user-controlled interaction, which can be run by a batch process
For Inventory transactions, select Stock, Periodic Processing, Valuation, Account. Interface.
For Production transactions, run the WIP Accounting Interface by selecting Costing, WIP, WIP posting.
For Fixed Assets transactions, select Fixed Assets, Processings, Account. interface, Generation of accounting entries.
Can I just use GTEST to preview the journal entries?
Sage X3 doesn’t create out-of-balance or one-sided journals, instead, it rolls problem transactions back. With GTEST, you do get a preview and it is great for looking at problem entries with unbalanced or mandatory dimension issues (see Sage knowledgebase article 16796 for instructions on using GTEST). GTEST allows you to preview the problem journal so you can rectify the issue. However, if the journal is good-to-go from the balanced/valid accounts and dimensions sides, the process follows through with the creation of the journals and doesn’t leave you the opportunity to stop the post. It won’t prevent the newbies from posting their unreviewed transactions either.
User parameters: ACESIMTRC - Simulated entry generation.
We should look at the Online help center to see how it defines the parameters and its potential values:
This parameter is used when implementing unit or mass generation processings of accounting entries using automatic journals.
You can use this parameter to request a simulated generation of entries in a dedicated simulation screen. No accounting entry will actually be generated.
No
No simulation run. Entries are generated.
This is the default value.
Yes always
The generation of entries is simulated.
During the generation, a screen automatically opens and displays the simulation results and potential warning messages.
During mass processings, all the entries are displayed.
Yes if error
The generation of entries is simulated.
The screen displaying the simulation results only opens when an error occurs.
During mass processings, only entries in error are displayed.
In mass processing, when this parameter has the value Yes always or Yes if error, click OK to go to the next entry. Once the last entry has been displayed, the log file details the list of entries in error and associated error message.
We’ll proceed to Setup, Users, Users and select the User that we want to restrict. Note that I’ve selected the ADMIN user. On the Parameters tab, select Chapter CPT and Group ACC to find the ACESIMTRC parameter. We’ll prevent all postings by selecting Yes – always. Click OK and Save.
I am signed in as the ADMIN user. So, let’s post a Supplier BP invoice PIDNA01220-000001 (under A/P-A/R accounting, Invoicing) to see what happens with this value set to Yes - always:
After I click Post on the Supplier BP invoice screen, the Simulation window displays my debit and credit amounts and accounts.
A Pop Up view of the first line, displays the dimensions and other information that I would see in a posted journal. I have a detailed preview of where the transactions will post on the General Ledger and the amounts.
What happens when I click OK on the simulation screen? Because I’m signed in as ADMIN and there are no errors displayed, will this override the parameter value and allow me to post the transaction through to the General Ledger?
No, the transaction didn’t post. It won’t post until I change the parameter ACESIMTRC value to No or Yes - if error and click Post again.
If you run Stock Accounting Interface (FUNSTKACC), you get the same Simulation screen as with the invoice.
The Log indicates that there were no errors and no journal entry was created.
Hope you find this makes reviewing transactions a little easier.

Entradas populares de este blog

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...
Leer más

How to create an additional line text (ACLOB) on purchase orders for internal notes

Sin conexión Kyle Klinger hace 1 día Origen:  https://www.sagecity.com/support_communities/sage_erp_x3/f/sage-x3-general-discussion-forum/143870/how-to-create-an-additional-line-text-aclob-on-purchase-orders-for-internal-notes I was trying to add internal notes to the purchase orders at a line level and was thought I would share a how to.  If you have a better way, please share.     Add column to PORDERQ; YLINTEX2, Type TXC   Save and validate table This is where the ID of the text will be stored at the record level, i.e. POQ~00000007, this is similar to field LINTEX  On screen POH2 Add column YLINTEX2, to Block 1. Most likely you will want this field to be hidden. On column NBLIG add a button action ACLOB2, description "Text internal" This button action will require an action parameter "CODE2", it will not be available until after save. Set the parameter "CODE2" to [M:POH2]YLINTEX2(nolign-2), the field that was just added....
Leer más

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente:  https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor:  https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending  through  meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending  through  Workflow 4) Sending  through  ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is  meladx  executable file, that you can find in  runtime\bin  directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES”  go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail  ...
Leer más