The shortcut should still be in the start menu. If not, look for MSDynamicsSL.exe on the mapped drive
↧
Forum Post: RE: SL 2015 -- Newly installed client won't open
↧
Forum Post: RE: Payroll check deduction duplicating
Sorry, none of my clients run multi-company so my knowledge is limited here. However, any table that can be shared under multi-company would have a cpnyid field (I suspect). Given that the SQL query did not produce duplicates then I am thinking the multi-company is not a prime suspect. Further, since the other companies do not use payroll, they would not be part of the issue anyways. So, the correctly working company is in its own database. But, one the same server? If so them the same report definition is being used by both entities which suggests the issue is not with the report definition but something in the database. However, the SQL query eliminated that (or so it seems) so we are basically back at the beginning other than we have eliminated some of the potential causes. SL uses Crystal Reports and Crystal Reports interfaces with the database through ODBC. While I am hard pressed to see where ODBC could be the issue, we could use the ODBC Manager to delete that ODBC definition for the failing database and then run any SL report which will rebuild the ODBC definition and see if that has any effect. Payroll check issues are more difficult to resolve because they utilize PRCheckTran which only exists after payroll is calculated and before the checks are kept which means the issue can only be diagnosed in that window or if you are willing to create a dummy payroll check that you void at some point. I am not sure where your payroll stands right now but, since you are able to run the SQL queries you have run, you are in that window with either the live payroll or a dummy check. If it is the live payroll then I suspect you have a short time frame before you have to keep the checks and thereby lose the data we need.
↧
↧
Forum Post: RE: Payroll check deduction duplicating
Since we seem to be at a bit of a dead end here. You indicated that payroll was set up for 2016 but no live payrolls we done until 2017. If that is the case, we could trying deleting the 2016 records from the Deduction table (delete from deduction where calyr = 2016) and see if that has any effect. Not holding a lot of hope on that but it would not harm anything to try.
↧
Forum Post: RE: VOIDING A HAND CHECK THAT TRANSACTION DATE IS 07/27 AND THE CORRECT MONTH IS 03/27
Hi Rick I have a Question .. Do you Know , whats mean status "O" from report " Check Reconcilation" ?
↧
Forum Post: REPORT " CHECK RECONCILATION " STATUS "O"
Hi I have a Question .. Do you Know , whats mean status "O" from report " Check Reconcilation" ?
↧
↧
Forum Post: RE: REPORT " CHECK RECONCILATION " STATUS "O"
That indicates that the check is outstanding (not reconciled). This status is set if you indicate, in AP Setup, that you keep checks for reconciliation. Once a check is reconciled (or you do not keep checks for reconciliation) the status becomes a C.
↧
Forum Post: RE: REPORT " CHECK RECONCILATION " STATUS "O"
thanks
↧
Forum Post: Is MS Dynamics SL 7 SP1 compatible with NetFramework 4.0?
I Need to install Netframework 4.0 on my Dynamics SL Server 7.0 SP1 (Wind 2003 Server with with SQL 2005) for another app. Does anyone has done this? Thanks Carlos
↧
Forum Post: Cash manager or bank reconciliation
Hi, I'm new in the blog, hope to be in the right one to post my question....I´m also new using Dynamics SL and I need to know which module to use to do the bank reconciliation, Cash Manager or Bank Reconciliation (module 20* or BR*)...thanks!!
↧
↧
Forum Post: SOPORTE EN ESPAÑOL
Hola Buen Dia Tienen algún asesor que escriba en español ó soporte en español ? Gracias , Saludos !!
↧
Forum Post: RE: Cash manager or bank reconciliation
The BR module is a reconciliation focused on a by-transaction approach. To take full advantage, you should be able to import transaction data from your bank. If you are inside the US or Canada, it's likely your bank can feed you with the BAI2 format, which SL understands. Since SL started as a US based product, US oriented bank reconciliation is pretty much built in. The Cash Manager reconciliation, on the other hand, is a by-total reconciliation. You enter a checkpoint date in which a bank-to-book reconciliation is performed as a balance total. There can be offsets, but those are to be matched to well known transactions (like AP or AR payments not yet collected). So, the questions you should ask yourself are: 1. Am I in a business in which regulations force me to perform by-transaction reconciliation? 2. Am I inside US or Canada? 3. If not, can my bank produce the BAI2 format anyway, or some csv file that make sense? 4. If the bank won't help, do I have a small volume of monthly bank transactions so doing it by hand is not so crazy? 5. Are there any business related procedures that would prevent a meaningfull by-transaction reconciliation? Like branch office consolidating deposits from many AR transactions, or a non-SL POS software, or a voucher delay issue?
↧
Forum Post: RE: SOPORTE EN ESPAÑOL
Si, por supuesto. En latinoamérica existen varios partners establecidos de Microsoft que tienen práctica de SL. Particularmente conozco en Chile, Colombia y Ecuador. Aparte de ellos, existen varios free-lance que están disponibles. ¿Qué versión tienes? ¿Dónde estás localizado?
↧
Forum Post: RE: Cash manager or bank reconciliation
Thanks a lot, very clear your answer!!....and the question now is, can I use cash manager other functionality and BR for reconciliation?
↧
↧
Forum Post: RE: SOPORTE EN ESPAÑOL
Excelente Gracias !! Estamos en Cancun ( México ) ... Tenemos la versión 2011 . Para mis dudas sobre como sacar un reporte del Programa solo levanto tickets , es correcto ? Saludos Buen Dia
↧
Forum Post: MODULO REPORT. " VENDOR TRIAL BALANCE "
Ruta : Report ] Trial Balance En el Reporte de "Vendor Trial Balance " selecciono en la Pestaña " Selec" la siguente opcion [ Field ] [ Operator ] [ Value ] " vr_03650c.venid " " Contains " ( Pongo el Id del Vendor correspondiente ) El reporte me muestra las Facturas del Vendor ( Historial ) y un Cheque mostrando a que Factura de aplicó ... Pero solo me muestra un cheque que corresponde al periodo que esta corriendo. Sin embargo tengo otro cheque de un periodo anterior que no me lo agrega en el reporte , Que opcion tengo que agregar para que me lo incluya con la demas informacion del reporte ? Quedo a sus ordenes ..
↧
Forum Post: Printing Indented BOM from command line doesn't work
Step 1: Find a BOM Step 2: Verify can print indented BOM From the ROI Screen (Report number: 11600, format is 11600I) Notice - Pre process honors the kit.kitid = ? criteria, so doesn't run for all BOMs Step 3 - Try through command line (found needed two ' in order to have show in the RPTRunTime) e.g. "C:\Program Files (x86)\Microsoft Dynamics\SL\Applications\ROI.EXE" 1 11600/RUN 11600I/FORMAT ({kit.kitid} = ''F102-A117-S-02-1-00-0-00-00-A'' )/WHERE /PSCRN this runs, but explodes every BOM Due to the pre-process 1160000.exe At client site, with a couple of thousand BOMs, goes from ~5 seconds in step 2 to > 15 minutes (Eventually crashes, due to Int overflow) RPT Runtime DB Record: (Wrk first, then fail) AccessNbr Acct Banner BatNbr BegPerNbr BusinessDate CmpnyName ComputerName CpnyID DatabaseName DocNbr EndPerNbr LongAnswer00 LongAnswer01 LongAnswer02 LongAnswer03 LongAnswer04 NotesOn PerNbr RepBegDate RepEndDate ReportDate ReportFormat ReportName ReportNbr ReportTitle RI_BEGPAGE RI_CHKTIME RI_COPIES RI_DATADIR RI_DICTDIR RI_DISABLEDS RI_DISABLEQS RI_DISPERR RI_ENDPAGE RI_ID RI_INCLUDE RI_LIBRARY RI_NOESC RI_OUTAPPN RI_OUTFILE RI_PRINTER RI_REPLACE RI_REPORT RI_STATUS RI_TEST RI_WHERE RI_WPORT RI_WPTR RI_WTITLE SegCustMask SegCustTitle SegInvenMask SegInvenTitle SegSubMask SegSubTitle SegVendMask SegVendTitle ShortAnswer00 ShortAnswer01 ShortAnswer02 ShortAnswer03 ShortAnswer04 Sub SystemDate SystemTime UserId tstamp --------- ---------- ------ ---------- --------- ------------ ------------------------------ --------------------- ---------- -------------------- ---------- --------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ------- ------ ----------------------- ----------------------- ---------- ------------------------------ ------------------------------ --------- ------------------------------ ---------- ---------- --------- --------------------- --------------------- ------------ ------------ ---------- ---------- ------ ---------- -------------------------------------------------------------------------------- -------- ---------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ---------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------ --------- ------- ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------ ---------------- ---------------- -------------------------- -------------------------- -------------------------------------- -------------------------------------- ---------------- ---------------- ------------- ------------- ------------- ------------- ------------- ------------------------ ---------- ---------- ----------------------------------------------- ------------------ WRK88 F 201708 8/11/2017 ### TST TEST SYSTEM ### TSTTESTRDP-Tcp#8 SRSD SRSDP 201708 0 201708 1900-01-01 00:00:00 1900-01-01 00:00:00 08/11/2017 Indented 11600I 11600 Bill of Material Lists 1 R 1 SRSDP 0 0 T 9999 3 F D >, Bill of Material Lists 1 nul: Send To OneNote 16 Bill of Material Lists @R XXXXXXXXXX Customer ID @R XXXXXXXXXXXXXXXXXXXXXXX Inventory ID @R X-XX-XX Subaccount @R XXXXXXXXXX Vendor ID FALSE FALSE FALSE FALSE FALSE 8/11/2017 03:44pm MAXQ 0x0000000B648C8093 FAI89 F 201708 8/14/2017 ### TST TEST SYSTEM ### TSTTESTRDP-Tcp#9 SRSD SRSDP 201708 0 201708 1900-01-01 00:00:00 1900-01-01 00:00:00 08/14/2017 Indented 11600I 11600 Bill of Material Lists 1 R 1 SRSDP 0 0 T 9999 3 F >, Bill of Material Lists 1 F ({kit.kitid} = 'F102-A117-S-02-1-00-0-00-00-A') nul: Send To OneNote 16 Bill of Material Lists @R XXXXXXXXXX Customer ID @R XXXXXXXXXXXXXXXXXXXXXXX Inventory ID @R X-XX-XX Subaccount @R XXXXXXXXXX Vendor ID FALSE FALSE FALSE FALSE FALSE 8/14/2017 08:07am MAXQ 0x0000000B648C8E11 Note the Where clause is removed when run through ROI actual code that launches it: XParmStr = "ROI.EXE " + PRMSEP + "11600/RUN" + PRMSEP + "11600I/FORMAT" + PRMSEP _ + "({kit.kitid} =" + RTrim(SParm(strKitID)) + ")/WHERE" XParmStr = XParmStr + PRMSEP + "/PSCRN" serr = Launch(XParmStr, True, True, 0) I've tried a trigger to catch the changes to RPTRuntime, SQL Traces, running from command line. Fails same way on multiple machines, fails same way if launch through RDT rather than VBA, fails if run from command line too Parameters to exe seem to be the same (Fun to get, too:) Fails: "C:\Program Files (x86)\Microsoft Dynamics\SL\Applications\BM\1160000.EXE" 4 68656 3 PRINT Y Works: "C:\Program Files (x86)\Microsoft Dynamics\SL\Applications\BM\1160000.EXE" 4 527474 3 PRINT Y Looking for ideas, really rather not write my own replacement pre-process...
↧
Forum Post: RE: Printing Indented BOM from command line doesn't work
This is in SL 2015, 9.02.41201.02
↧
↧
Forum Post: RE: SOPORTE EN ESPAÑOL
Hola, Microsoft atiende a través de sus partners y en Mexico hay varios. Sugiero revises el registro de tu licencia y alli debe indicar qué partner instaló el SL en tu empresa. Si no puedes contactarlos localmente, entonces puedes recurrir a los que están en otros países para soporte remoto. Saludos, Peter Pino ERPMATICA S.A.C Tel. (511)717 6541 Ext. 112 Skype ID: Peter.Pino Cel. 9990-47726 RPM: *544906 www.erpmatica.com
↧
Forum Post: RE: SOPORTE EN ESPAÑOL
Benja, Este es un foro de comunidad. No es un canal de soporte de Microsoft donde levantes tickets. Tampoco hay asesores de Microsoft que estén regularmente revisando el foro. Puedes exponer una pregunta y alguien te podrá contestar algo como "a mí me ocurrió parecido y lo que me funcionó fue x". En general, el contenido es en inglés, pero no existe concepto de idioma oficial.
↧
Forum Post: RE: MODULO REPORT. " VENDOR TRIAL BALANCE "
El reporte Vendor Trial Balance no va a mostrar un cheque de periodos anteriores si el cheque ya está cobrado, dado que ya no forma parte del saldo del proveedor. Este informe sólo muestra las facturas que no se han pagado, o que han tenido actividad el este mes o el anterior. Si necesitas información de cheques anteriores, el informe Check Register puede mostrar cheques de cualquier periodo indicando las facturas que fueron aplicadas. ==================== ENGLISH The Vendor Trial Balance report won't show a check from a prior period that's already been cashed, since it doesn't add to the vendor balance anymore. This report shows only the open documents, or those that had activity in the last or current month. If you need data from past checks, the Check Register report do show checks from any period indicating the applied invoices.
↧