Solution : 1860 VERSION(S): tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3 tfB40_c SITUATION IDENTIFIED IN: Maintain Transaction Types by Transaction Origin (tfgld4126m000) SITUATION DESCRIPTION: Document number on Financial integration transactions are not using the correct series. SOLUTION DESCRIPTION: Changed the Maintain Transaction Types by Transaction Origin script to allow the entry of series number for transportation data. This solution solves defect 1416 VRC package component comp_type comp_code B40 c4 tf tfgld4126m000 Script/Library Source gld4126 Solution : 1866 VERSION(S): tf3.1L_b_glo0, tf3.1L_b1_glo0, tf3.1L_b2_glo0 tfB40L_b_glo0, tfB40L_b1_glo0, tfB40L_b2_glo0, tfB40L_b3_glo0 tfB40_c SITUATION IDENTIFIED IN: Transfer Payments (tfcmg1260s000) SITUATION DESCRIPTION: In IVC, company 400, Maintain Check Master, Checks 93-94 are duplicates of one another. Although 93 has a status of Anticipated, 94 is already Paid and reconciled. However, both checks have the same anticipated payments and invoices linked to them. It looks as if Check 94 is a copy of 93. When you try to reconcile check 93, it doesn't allow you to do it -- in reconciling, the system does not even recognize check 93 as being anticipated. SOLUTION DESCRIPTION: This error was caused by a problem with the report that actually prints the checks. This problem has now been corrected. This solution solves defect 2297.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Solution : 1860
VERSION(S): tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3
tfB40_c
SITUATION IDENTIFIED IN: Maintain Transaction Types by Transaction Origin (tfgld4126m000)
SITUATION DESCRIPTION:Document number on Financial integration transactions are not using the correct series. SOLUTION DESCRIPTION:Changed the Maintain Transaction Types by Transaction Origin script to allow the entry of series number for transportationdata.This solution solves defect 1416
SITUATION IDENTIFIED IN: Transfer Payments (tfcmg1260s000)
SITUATION DESCRIPTION:In IVC, company 400, Maintain Check Master, Checks 93-94 are duplicates of one another. Although 93 has a status ofAnticipated, 94 is already Paid and reconciled. However, both checks have the same anticipated payments and invoices linkedto them. It looks as if Check 94 is a copy of 93. When you try to reconcile check 93, it doesn't allow you to do it -- inreconciling, the system does not even recognize check 93 as being anticipated. SOLUTION DESCRIPTION:This error was caused by a problem with the report that actually prints the checks. This problem has now been corrected.This solution solves defect 2297.
SITUATION IDENTIFIED IN: Assign Credit Notes to Invoices (tfacr2121s000)
SITUATION DESCRIPTION:Assignment of sales credit notes using a both a negative and positve amount, then reversed, leaves a one line transaction inthe gld102.] SOLUTION DESCRIPTION:The line that remained was the debit to the control account. This was because the program was processing one line at atime, and when all assignments previously done were reversed out one by one, the amount of this line was reduced. Theproblem was that there was no check in the program to ascertain whether the amount had reduced to zero. This check has nowbeen put in and if the amount reduces to zero then the record is removed.This solution solves defect 2258.
SITUATION DESCRIPTION:This session is defaulting the fiscal year to the current calender year. SOLUTION DESCRIPTION:The program script was found to be defaulting this sessions fiscal year to the current calender year. The program script waschanged to use the company's current fiscal year as the default into this session. This solution solves defect DF2219-1.
SITUATION DESCRIPTION:When using the Create Transactions from Schedule function in this session the first reference field would turn to blankswhen tabbed through. Subsequent reference fields would change to the values in the previous record. SOLUTION DESCRIPTION:The program script tfgld1103 was modified so that when the reference field is non-blank (has a value) it is not overwrittenwith default data.This solution solves defect DF2229-1
SITUATION IDENTIFIED IN: Close Periods (tfgld1206m000)
SITUATION DESCRIPTION:When closing periods, the customer received an error message that debits & credits were not in balance and was not permittedto close the period.
SOLUTION DESCRIPTION:Due to slight rounding errors, debits and credits do not balance. Analysis of the program script tfgld1206 noted that noneof the double compare statements rounded debits or credits. We have added an "absolute" function to any doublecomparisons where a variable is compared to 0.0.
SITUATION IDENTIFIED IN: Aging Analysis by Supplier (tfacr2420m000)
SITUATION DESCRIPTION:When you deal with sales invoices with a receipt schedule, the amounts open in the Aging Analysis are not correct in somecases.e.g.I Sales invoice: ACR 95000016, with the following receipt schedule
1/3/97 hfl 501/4/97 hfl 501/5/97 hfl 50
II Receipt from client CSB96 hfl 50Receipt from client CSB97 1 hfl 50Receipt from client CSB97 2 hfl - 50
III Running Aging Analysis Report, session tfacr2420m000, Based on due dateOne gets the following results:
Invoice amount: 250 ok
Amount received: 5050-50 ok
Balance 200 okOpen amount 150 NOT ok, the amount open should be: 200
The error seems to occur because of the bank receipt CSB97 which consists of two receipts, namely 50 and -50.
SOLUTION DESCRIPTION:This problem was caused by improper updation of the receipt schedule. The negative receipt was treated like a new receiptand got added to the schedule receipt amount like a positive amount instead of adjustment against already received amounts.Now if a negative receipt is entered then the amount is subtracted from the existing positive amount already received. Whenthese entries are corrected the Aging Analysis report prints properly.This solution solves defect 16373.
tcB40_c SITUATION IDENTIFIED IN: Process Cycle Counting Data (tdinv1221m000)
SITUATION DESCRIPTION:A cycle count order the system assigns a specific series (series 7) when the quantity is adjusted on this cycle count order theentries are generated by the system against this series 7. In tfgld415 table this transaction gets posted with series 5, whichis the series for manual inventory adjustments. This could cause transactions in finance to go to the wrong dimensions ifyou are using the series number to drive them to the general ledger. SOLUTION DESCRIPTION:Changed the script to give series 5 to manual inventory adjustments and series 7 to inventory adjustments made by cyclecounting.This solution solves defect 2138
SITUATION DESCRIPTION:While entering the Sales Invoice Transactions if one skips the tax code field and backs up after passing the amount field thenthe tax code entered has no effect on the amount. e.g. if the tax code entered is of type net then the amount field should bereduced by the tax amount. SOLUTION DESCRIPTION:The problem was that the amount was not getting re-calculated in case the tax code was changed. This has now beencorrected, so that whenever a tax code is entered/changed the amount field is recalculated.This solution solves defect 2319.
SITUATION IDENTIFIED IN: Close Year (tfgld6203m000)
SITUATION DESCRIPTION:When closing the year, the customer received an error message that debits & credits were not in balance and was notpermitted to close the year.
SOLUTION DESCRIPTION:Due to slight rounding errors, debits and credits do not balance. Analysis of the program script tfgld6203 noted that noneof the double compare statements rounded debits or credits. We have added an "absolute" function to any doublecomparisons where a variable is compared to 0.0.
SITUATION IDENTIFIED IN: Convert Electronic Bank Statements (tfcmg5202m000)
SITUATION DESCRIPTION:Amount field is not being filled in correctly when converting electronic bank statements. The amount is being read inwithout any decimal places, causing the documents to not match. SOLUTION DESCRIPTION:This problem was caused by an error in the part of the program which reads in the amount. The amounts will now beconverted with the correct number of decimal places.This solution solves defect 1196.
SITUATION IDENTIFIED IN: Update Integr Trans and Real Time Post to Finance (backgrd.) (tfgld4200s000)
SITUATION DESCRIPTION:The Item Data online help lists the Sales and Purchase Statistics Groups as valid key elements for the integrationtransaction combination of Production and Receipt when, in reality, they are not. SOLUTION DESCRIPTION:The help text now clearly indicates that the Statistics Groups may only be used as a key element for Sales and Purchase
VRC package component comp_type comp_codeB40 c4 tf tfgld4200s000 Help Text LBtcgen.help.intitm
Solution : 1913
VERSION(S): tf3.1_b, tf3.1_b1, tf3.1_b2, tf3.1_b3, tf3.1_b4, tf3.1_b5tf3.1L_b_glo0, tf3.1L_b1_glo0, tf3.1L_b2_glo0, tf3.1L_b3_glo0, tf3.1L_b4_glo0, tf3.1L_b5_glo0 tfB40_a, tfB40_a1, tfB40_a2tfB40L_a_glo0, tfB40L_a1_glo0, tfB40L_a2_glo0tfB40L_a_gls0, tfB40L_a1_gls0, tfB40L_a2_gls0 tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3tfB40L_b_glo0, tfB40L_b1_glo0, tfB40L_b2_glo0, tfB40L_b3_glo0tfB40L_b_gls0, tfB40L_b1_gls0, tfB40L_b2_gls0, tfB40L_b3_gls0 tfB40_c SITUATION IDENTIFIED IN: Post Sales Invoices (tfacr4220m000) SITUATION DESCRIPTION:The program scripted for "Posting Sales Invoices" session was not calculating expected cash date (tfacr200.liqd). SOLUTION DESCRIPTION:The program scripted was changed to include the calculation of expected cash date (tfacr200.liqd) whichis the sum of invoice due date (tfacr200.dued) + extra days after due date (tccom010.eded). This solutionsolves defect 2403-1.
SITUATION DESCRIPTION:The zoom sessions for several integration display and print sessions were not zooming to the correct subsession. SOLUTION DESCRIPTION:The 'zoomto' fields for field tfgld410.ocom Original Company was modified to zoom to session tccom0500s000 Display Company Data in the following sessions:
tfgld4201m000 Post Integration Transactions to Finance Transactionstfgld4210m000 Archive and Purge Integration Transactionstfgld4220m000 Purge Integration Transactions Credit Linestfgld4240m000 Purge PCS Non Finance Integration Transactionstfgld4510m000 Display Integration Transactions by Project / Order tfgld4532m000 Display Integration Transactions Log tfgld4410m000 Print Integration Transactionstfgld4432m000 Print Integration Transactions Log
This solution solves defect 2381-1VRC package component comp_type comp_codeB40 c4 tf tfgld4220m000 Form gld4220m0001B40 c4 tf tfgld4410m000 Form gld4410m0001B40 c4 tf tfgld4510m000 Form gld4510m0001B40 c4 tf tfgld4510m000 Form gld4510m0003B40 c4 tf tfgld4510m000 Form gld4510m0005B40 c4 tf tfgld4532m000 Form gld4532m0001B40 c4 tf tfgld4532m000 Form gld4532m0002B40 c4 tf tfgld4510m000 Form gld4510m0006B40 c4 tf tfgld4510m000 Form gld4510m0004B40 c4 tf tfgld4510m000 Form gld4510m0002B40 c4 tf tfgld4432m000 Form gld4432m0001B40 c4 tf tfgld4240m000 Form gld4240m0001B40 c4 tf tfgld4210m000 Form gld4210m0001B40 c4 tf tfgld4201m000 Form gld4201m0001
SITUATION DESCRIPTION:Form 3 of the Display Sales Invoice Details has a label that reads "Purchase Order." It is incorrectly pointing totdpur040.orno. SOLUTION DESCRIPTION:Label was replaced with a new one that reads "Order." (tdsls040.orno)
SITUATION IDENTIFIED IN: Assign Unallocated/Advance Receipts to Invoices (tfcmg2105s000)
SITUATION DESCRIPTION:While doing manual allocations in tfcmg2100m000, continuing into session tfcmg2105s000 by hitting "maintain" in GUI, if theescape button is hit, the allocations already done are reset to "No". The remaining balance, however is not reset, and whenyou go back to allocate manually again, the remaining balance continues to subtract even after everything is reset. The useris not allowed to re-allocate the invoices to the amount correctly.
SOLUTION DESCRIPTION:The escape key is now suppressed. If the user in GUI presses the escape key no action will be taken. This solution solves defect 2442.
SITUATION DESCRIPTION:When in session thgls4432m000, "Print Integrations Transactions Log, when zooming from the field "Order", the sessionwould always zoom to the display session " tdpur4512s000 - Display Purchase Order by Order Number". This occurred nomatter what transaction origin was entered. SOLUTION DESCRIPTION:
Code was introduced to the programscript to set the proper zoom session for the transaction origin, or to disable zooming from the Order field if the transactionorigin type does not support a zoom session for lookups. The form was also modified so that it does not point to a specificsession for zooming from the Order field, but allows that session to be specified in the code.This solution solves defect DF2380-1
VERSION(S):tf3.1_b, tf3.1_b1, tf3.1_b2, tf3.1_b3, tf3.1_b4, tf3.1_b5 tf3.1L_b_glo0, tf3.1L_b1_glo0, tf3.1L_b2_glo0, tf3.1L_b3_glo0, tf3.1L_b4_glo0, tf3.1L_b5_glo0 tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3tdB40L_b_glo0, tdB40L_b1_glo0, tdB40L_b2_glo0, tdB40L_b3_glo0tdB40L_b_gls0, tdB40L_b1_gls0, tdB40L_b2_gls0, tdB40L_b3_gls0tdB40L_b_sch0, tdB40L_b1_sch0, tdB40L_b2_sch0, tdB40L_b3_sch0 tfB40_c SITUATION IDENTIFIED IN: Maintain Transaction Types (tfgld0111m000) SITUATION DESCRIPTION:When using Maintain Transactions session (tfgld1101m000) and entering a Transaction Type with aTransaction Category of Cash with Checksums Required (Control Amount entered) and the MainSession was not tfgld2100s000 (Maintain Bank Transactions), the Batch could not be finalizedbecause the controls totals were not matching. No warning message was displayed when selectinga "Cash" Transaction Category with Checksums Required and the Main Session was nottfgld2100s000 (Maintain Bank Transactions). Hence forth-logical totals should not be taken forcontrol totals. SOLUTION DESCRIPTION:Display a warning message in session tfgld0111m000 (Maintain Transaction Types) when theTransaction Category is set to "Cash" and the Checksums Required is set to "Yes" and the MainSession is not tfgld2100s000 (Maintain Bank Transactions). This message will be displayed as follows: "Warning: For Transaction Category "Cash" and Checksums Required, the main sessionmust be tfcmg2100s000.". The program script tfgld1211s000 (Audit Batches) and MaintainTransaction session (tfgld1101m000) function tfgld0019 was changed to correctly accumulatea Hash Total for Cash Bookings (Currency and Sundry cost will not be included). This solution solves defect DF 2369-1
SITUATION IDENTIFIED IN: Enter Amounts for Assignments (tfcmg2107s000)
SITUATION DESCRIPTION:When you hit the esc key in the session tfcmg2107s000 the amount field gets corrupted (in GUI). A similar defect waslogged for tfcmg2105 and has been solved. Can something similar be done for this session as well. SOLUTION DESCRIPTION:The program has been modified so that pressing the escape key will have no effect on the remaining amount field.This solution solves defect 2547.
VERSION(S): tfB40_c SITUATION IDENTIFIED IN: Maintain Business Information Detail (tffas0113m000) SITUATION DESCRIPTION:This session would display "Transaction is on, can't continue" when inserting a new record for aFixed Asset that had more than one Business Information Definitions assigned to it. SOLUTION DESCRIPTION:Changed program script to properly insert records when multiple Business Information Definitions are assigned to a Fixed Asset. This solution solves defect DF 2585-1
SITUATION DESCRIPTION:A zoom should be provided on the customer number field for selecting a customer. SOLUTION DESCRIPTION:A zoom to sub-selection tccom1510s000 Display Customer list has been added to the field to facilitate selection ofcustomers.This solution solves defect 17090.
VRC package component comp_type comp_codeB40 c4 tf tfacr2533m000 Form acr2533m0001
Solution : 1998
VERSION(S):
tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3
tfB40_c
SITUATION IDENTIFIED IN: Display Distribution by Child Customer (tfacr2527s000)
SITUATION DESCRIPTION:Invoice balances relating to the child customer of a parent do not reflect when viewing the customer sales invoices for theparent ie: you cannot view the child invoices in the parent account. However, if you choose "special" and "DisplayDistribution by Child Customer", you can sometimes zoom down to the child account. This zooming down does not work inall cases eg: from parent #770000, you can view its child 772000 but not its child 771000.tfacr2527s000 - Display distribution by Child Customer - only ever reflects one child. If the parent has more than one childonly the first child is shown. If the child has children these are not shown either.
SOLUTION DESCRIPTION:Child customers with zero invoice, order balances and credit limits do not get displayed by default in this session. One hasto use Ctrl-A in ASCII or the Special/Application drop down in GUI to view these child records. Also, this session waslooking up a wrong table to find the order and invoice balances. Hence these were always zeros, thus sometimes skipping thechild record from normal display. The session has been corrected to read the right table to find out the invoice and orderbalances. This session has been designed to go only one level down i.e. only upto child customer level. Children of a child customerare not processed in this session.This solution solves defect 17088.
The purchase price variance was not calculated consistently correct in the matching sessions Match Receipts(tfacp1131s000) and Maintain Matched Receipts (tfacp1132s000). With a match of 0 pcs for any value, a difference wasgenerated equal to the total of the Purchase Order.
SOLUTION DESCRIPTION:The program scripts tfacp1132 and tfacp1131 along with the function itfacp0015 were edited so that they return a consistentprice difference value to the Approve Invoices session (tfacp1140s000). The price difference generated is consistent with theformula in the help file in all cases.This solution solves defect DF2415-1
SITUATION IDENTIFIED IN: Convert Electronic Bank Statements (tfcmg5202m000)
SITUATION DESCRIPTION:When a negative value is passed through field tfcmg502.docd (Document Date), the user receives error 205 'Out of range;field value does not agree with the domain definition'. SOLUTION DESCRIPTION:An if statement was added to check for negative values and reset them to 0 to avoid this error. The same modification hasbeen made on field tfcmg502.trnd (Transaction Date) since the same error could potentially occur here as well.
SITUATION DESCRIPTION:When 2 or more users create a new batch at the same time, the last used batch number is not always correctly updated intable gld014. Further, this problem is compounded when the next new batch is entered. Since the batch number in tablesgld100 and gld101 were updated correctly, the last used batch number in gld014 will always be out of sequence with theother 2 tables making it impossible to enter any more batches.
SOLUTION DESCRIPTION:A modification was made to properly update table gld014 and make certain it stays in sequence with gld100 and gld101.
SITUATION DESCRIPTION:Zooming on the Order Number field does not consider the Original Company number. SOLUTION DESCRIPTION:A modification was made to the script to check table tfgld000 and verify if the Original Company entered is a financial or
logistic company. If it is, the zoom on Order Number references the Original Company. If it is not a financial orlogistic company, Order Numbers for the current company are displayed.This solution solves defect 2637-1.
SITUATION IDENTIFIED IN: Process Periodical Depreciation Calculation (tffas2200m000)
SITUATION DESCRIPTION:Have defined an asset and a depreciation code to calculate depreciation based on "period in use". The order date is 01-01-98The date of first use is 01-15-98The date of last use is 01-14-2010The number of years in use is 12.The asset is purchased on 03-12-98 for $92,592.00Depreciation is calculated for this asset for periods one through period threeDepreciation is calculated for period three only. SOLUTION DESCRIPTION:Depreciation for period 1 and 2 in this case has been designed to calculated in the last period of the year. However, if theFixed Asset Parameter "Round Results of Last Period" was set to "No" then the depreciation for the period beforeinvestment was not getting calculated. This dependency has been removed.This solution solves defect 2593.
SITUATION IDENTIFIED IN: Print Aging Analysis by Customer (tfacr2420m000)
SITUATION DESCRIPTION:
Aging analysis inconsistently prints a cash transaction: We have several copies of the aging analysis for the same customer,and the first cash transaction sometimes prints and sometimes does not. The total for the Amount Received varies, dependingon whether or not this line prints. SOLUTION DESCRIPTION:When using Aging Analysis by Due Date the receipt/payment schedule is read to determine the Due Date. In this procedure avariable was set to indicate whether a schedule existed or not. The value of this variable did not get updated in some cases.Also, since printing of some report lines depended on this variable the printing and consequently the totals went wrong. Withthe correct setting of this variable all lines will get properly printed.This solution solves defect 2775.
SITUATION DESCRIPTION:Create a sales invoice. Make a correction using a correction transaction type. e.g. Change the amount, then process.Following message comes up "No changes made, process aborted". Trace in debug on the field new.amnt and see that it ischanged to the old.amnt again.
SOLUTION DESCRIPTION:Because of the changes made to improve performance the program was executing differently internally and hence called afunction in which the whole set of new variables was initialized with the values of the old variables even before the newvalues were written to the database. Hence all modifications made by the user were lost and one got the error "Nomodifications made à". The initializations of the new variable set has now been put under condition so that they getinitialized when a new record is searched by the user.This solution solves defect 17259.
SITUATION IDENTIFIED IN: Close Periods (tfgld1206m000)
SITUATION DESCRIPTION:This session allowed Closing of the GLD module for a period when the ACP, ACR or CMGmodule(s) were currently Open for the same period. SOLUTION DESCRIPTION:Modified program script to not allow Closing of the GLD module for a period when the ACP, ACR or CMG module(s) are still Open for the same period. The following message will be displayed: "ACP, ACR and CMG should be "(Finally) Closed" before closing GLD for period ##"This solution solves defect 2197-1
SITUATION IDENTIFIED IN: Select Invoices for Payment (tfcmg1220m000)
SITUATION DESCRIPTION:When running the session "Select Invoices for Payment" (tfcmg1220m000), the customer gets the error:"Fatal error 206, record is not locked on tfacp200312." SOLUTION DESCRIPTION:The session was loosing its table lock, before the table update was being done. A correction has been made, and the errorno longer occurs.
gld410 (Integrations Transactions table) that originate from Replenishment Orders if Order No exists as a Purchase OrderNo.
SOLUTION DESCRIPTION:The program was checking for existence of the order in the purchase order table. It has been modified to check theReplenishment Order Header table (tdrpl105) for existence of the order number instead of the Purchase Order table(tdpur040) before purging.This solution solves defect 17005.
SITUATION IDENTIFIED IN: Print Trial Balance - with Dimensions (tfgld3405m000)
SITUATION DESCRIPTION:When printing Budget Variances by dimension/ledger account (tfgld340514000) if the last ledger account has zeros as theactual amount and budget then the dimension total line does not get printed. SOLUTION DESCRIPTION:The dimension totals line was not getting printed because the check of whether to print the line or not was based on the ledgeraccount line variables instead of the total variables. Hence if the last ledger account has zeros in its line variables thetotals line also got suppressed. This has now been changed. Now the check is based on the dimension total variables and onlywhen all totals for the dimension are zero will this line get suppressed.This solution solves defect 2779.
SITUATION IDENTIFIED IN: Select Invoices for Direct Debits (tfcmg4220m000)
SITUATION DESCRIPTION:When the payment method selected specified Planned Payment Date = Due Date = Yes in session tfcmg0140m000 - MaintainPayment Methods the due date of the invoice is being set as the Planned Debit Date in the Debit Advise even if a schedule isattached to the invoice. SOLUTION DESCRIPTION:The schedule due date was being over-written with the invoice due date in the program before the Debit Due date got its
value. This has now been corrected. Hence if the payment method specifies that the Planned Payment Date = Due Date = Yesand the selected invoice has a schedule attached then the due date specified in the schedule will be selected and used in theDirect Debit Advise.This solution solves defect 17292.
SITUATION IDENTIFIED IN: Match Electronic Bank Statements (tfcmg5212m000)
SITUATION DESCRIPTION:In some cases, the document number in tfcmg503.docn reflects a version of the actual document number. This is very bad, ason occasion this truncated version is also a valid document number. When this is the case, the item is matched to the wrongcustomer and invoice, and the only way to know this is to check every single matched item to verify that it is matchingcorrectly. SOLUTION DESCRIPTION:The session Match Electronic Bank Statements uses a very complex matching system. There was a small problem with thissystem that caused it to occasionally use a truncated version of the document number when matching. Unfortunately, whenthere was a valid invoice on the system with that (truncated version of original) document number, the match would be madeto that invoice, rather than the correct one. This error has been solved, and the session will now only check the fullversion of the document number when matching.
SITUATION IDENTIFIED IN: Copy Ledger Accounts to Statement Accounts (tffst1201s000)
SITUATION DESCRIPTION:Error 206 - Record not locked on tffst120 in db.update while copying Ledger Accounts as Statement Accounts. SOLUTION DESCRIPTION:In this VRC to reduce the amount of time a record is locked a different record locking scheme is used. However, this programis also creating / updating Statement Account Records from Ledger Accounts. Before doing this the statement account recordwas set to default values which reset the flag specifying that the record was set for delayed locking. Hence while trying toupdate the record did not get locked and the error message was displayed by the database. Now the value of this flag is storedbefore setting the record to default values and restored after setting to defaults. Hence the record gets locked just beforeupdate.This solution solves defect 2854.
VERSION(S): tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3tfB40L_b_mcr0, tfB40L_b1_mcr0, tfB40L_b2_mcr0, tfB40L_b3_mcr0 tfB40_ctfB40B_c1_adg0, tfB40B_c2_adg0, tfB40B_c3_adg0tfB40B_c1_mcr0, tfB40B_c2_mcr0, tfB40B_c3_mcr0 SITUATION IDENTIFIED IN: Integration Transactions to Finance Transactions (tfgld4200s000) SITUATION DESCRIPTION:Running Oracle 7.2.3 with porting set 6.1b.03.03 the query in dll "glddll4010", functionitfglddll4010.invoke.background.after.session() shows up as running very inefficient. The code is in itfglddll4010 as shownbelow in the code fragment. Correcting this query may help overall performance of the system since the query executes manytimes per day. The query is inefficient because the driver resolves the query and provides an index hint of index 1 whenthe best index would be index 2.
Inefficient SQL found (see attachment below). The sql is translated in the Oracle trace to SELECT /*+ FIRST_ROW index(a ttfgld102997$idx1) */ a.t$cono,a.t$year... from triton.ttfgld102997 a where a.t$eupd != :1 and a.t$trno=:2 group by a.t$cono,a.t$year... order by 1,2,3,4 Number of executions can range from 4000 to 6000 times a day with NO rows processed. Each execution takes over 1 CPUsec (more than 1 CPU hour per day). SOLUTION DESCRIPTION:Implemented a performance enhancement to a query in tfglddll4010 library script by removing the Order By clause to forcethe driver to use Index 2. This solution solves defect 2830-1.
SITUATION IDENTIFIED IN: Maintain bank Transactions (tfcmg2100s000)
SITUATION DESCRIPTION:When bank transactions from tfcmg2100s000 with type of transaction Customer Transaction, Supplier Transaction,Unallocated Payment, Unallocated Receipt, Advance Payment, Advance Receipt or Journal the field tfgld102.tran correctlyupdates with the correct flag but when the type of transaction is Customer Reconciliation or Supplier Reconciliation thefield is not updated and remains (0) empty. SOLUTION DESCRIPTION:The program had missed updating this field. Updation has now been added for Supplier/Customer Reconciliation too.This solution solves defect 17639.
SITUATION DESCRIPTION:In the ACR module, when one drills down from acr3130m000 (Maintain Reminder Diary) to acr2522s000 (Display SalesInvoice) no data is displayed. SOLUTION DESCRIPTION:The main session Maintain Reminder Diary did not pass the customer number to the sub-session Display Sales Invoices(tfacr2522s000). Hence no data was getting displayed. Now the variable expected by the sub-session has been created andpopulated with the current customer number displayed in Maintain Reminder Diary. Hence data is properly displayed by thesub-session.This solution solves defect 2871.
SITUATION IDENTIFIED IN:Write Off Payment Differences (tfacp2230m000)Write Off Payment Differences (tfacr2240m000)
SITUATION DESCRIPTION:When writing off payment differences, if an invoice that has a check processed (anticipated) meets the criteria for"Maximum Amount" and "Max Percentage" the invoice is still written off.
SOLUTION DESCRIPTION:An invoice with anticipated payments/receipts will not get selected for processing in these sessions now. Allowingwriting-off of invoices with anticipated payments/receipts cannot be allowed with a user accepted parameter because it willalways lead to incorrect results when the invoice is reconciled.This solution solves defect 2862.
SITUATION IDENTIFIED IN: Convert Electronic Bank Statements (tfcmg5202m000)
SITUATION DESCRIPTION:EBS batch number not being incremented when run as a job. When trying to convert multiple EBS files in separate batches asa job in Baan, the different daily batches are all being combined into the batch originally used to create the job.
SOLUTION DESCRIPTION:When creating a job to convert an EBS file, the first unused batch number is defaulted in as the batch for the job. Whencreating multiple jobs, each job receives the same default batch number, but the actual batch used should change if thedefault batch was already used. This was not being done correctly. The program script has been modified to fix theproblem, so even though multiple jobs will have the same default batch number, only the first EBS batch processed will usethe default batch. All subsequent jobs will get a new batch number.
SITUATION DESCRIPTION:A correct purchase price variance was generated and appeared on-screen from the Invoice matching sessions, tfacp1131s000and tfacp1132s000. This purchase price variance was overwritten in the Approval session tfacp1140s000 with an incorrectamount. SOLUTION DESCRIPTION:The problem was in the function tfacp0015 Make Approval Transactions, called by tfacp1140. In this function, the code wasedited to take into account situations where the invoice had a zero quantity or a zero amount. These were the situationswhere the purchase price variance calculation had been failing.
VERSION(S): tf3.1_b, tf3.1_b1, tf3.1_b2, tf3.1_b3, tf3.1_b4, tf3.1_b5 tfB40_a, tfB40_a1, tfB40_a2 tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3tfB40L_b_mcr0, tfB40L_b1_mcr, tfB40L_b2_mcr0, tfB40L_b3_mcr0 tfB40_c SITUATION IDENTIFIED IN: Print Statements of Account (tfacr3440m000) SITUATION DESCRIPTION:The currency label was not displaying the company's home currency for Grand Total and Aging Analysis report lines. SOLUTION DESCRIPTION:Changed the currency label for Grand Total and Aging Analysis report lines to use the company's home currency label(tccom000.ccur). This solution solves defect DF 2814-1.
SITUATION IDENTIFIED IN: Match Receipts (tfacp1131s000)
SITUATION DESCRIPTION:In the Match Purchase Invoice session (tfacp1131s000) a new record was defaulting to closed.no, resulting on no purchaseprice variance being calculated. In a related session Maintain Matched Receipts (tfacp1132s000) records with no amountwere defaulting to a status of registered rather than matched even if they were matched.Further, in acp1132 if a zero qty. item was entered, the closed field defaulted to no. This was changed to default to yes.
SOLUTION DESCRIPTION:The program scripts for acp1131 was edited so that a new record would default to closed.yes so that it can generate apurchase price variance. The closed status can be changed back in Maintain Matched Receipts. The program script foracp1132 was edited so that if an invoice record has an amount OR a quantity, the status defaults to matched rather thanregistered.
SITUATION IDENTIFIED IN: Background Process for End of Session Updates (tfgld1203s000)
SITUATION DESCRIPTION:Message "Transaction is on, can't continue" is displayed when trying to create a document having rounding differences and'End of Session' update mode. This creates a unbalanced document which cannot be finalized. SOLUTION DESCRIPTION:The transaction containing the rounding difference line was not committed to the database before the next transaction wasstarted. This led to the error. Now the rounding difference transaction is committed after creation and hence the error will
SITUATION DESCRIPTION:When a multi-line PO was received with one or more lines not received ( 0 qty rec'd ; 0 qty backordered), the amount of thenon-received lines was included in the Received field of the Automatic Matching session, resulting in an inaccurate number.It was also found after correcting this problem that the amount of the lines NOT received would also show up as a pricedifference. This situation was corrected as well and the Solution re-delivered 04/22/98. SOLUTION DESCRIPTION:The program script was modified so that this field accumulates only those receipts which have actually been received. Thepossibility of zero amount PO's was taken into consideration in this fix. In reading the table tfacp045 to accumulate thereceipts amount, only records with a receipt qty or amount are considered.
SITUATION IDENTIFIED IN: Import Journal Voucher Batches by ID Number (tfgldl200m000)
SITUATION DESCRIPTION:When trying to import a journal voucher batch, one get the error "Document number must be <= 8 characters" even thoughthe length of the document number is eight characters.
SOLUTION DESCRIPTION:The document number field used by this program has been defined as a string of length 9. Hence even when 8 digits are filledit string is always 8 digits followed by a space. The check for the length of the document number field was being donewithout removing the trailing spaces. This check is now done after removing all spaces (preceding and trailing). This solution solves defect 2982.
SITUATION IDENTIFIED IN: Transfer Payments (tfcmg1260s000)
SITUATION DESCRIPTION:The function "tfcmg0005.decode.amount", is used by various sessions, including the Compose Payments process, to converta numeric value into its corresponding words.When accessing this function for Spanish, the rountine will flip the positions of the 10s and 1s places and insert an "and"between them. According to several people in our organization who are fluent in Spanish, this is not proper syntax.Ex. The Amount $10,099.00 would be converted to (I am using English words instead of Spanish): ten thousand nine and ninetyThe proper syntax for Spanish should be: ten thousand ninety nineSpanish should work the same way as English as well. SOLUTION DESCRIPTION:The function has been modified to decode amounts like English. The delivered components do not contain Spanish languagecomponents. However, the function can be used and the necessary reports re-compiled for language 5 (Spanish) so that thechanged function will be used.This solution solves defect 2805.
SITUATION IDENTIFIED IN: Match/Approve Purchase Invoice with Orders (tfacp1130m000)
SITUATION DESCRIPTION:When we drill down on Supplier (Order-choice2, binoculars [search]), the display purchase Invoice appears, not the displaysuppliers screen SOLUTION DESCRIPTION:The zoom from the supplier field has been changed to session tccom2510s000 Display Supplier List.This solution solves defect 3024.
VRC package component comp_type comp_codeB40 c4 tf tfacp1130m000 Form acp1130m0001
SITUATION DESCRIPTION:The Maintain Transactions session was not properly updating the Last Used Batch Number table (tfgld014).
SOLUTION DESCRIPTION:The session script has been modified to properly update the table with the last used batch number and be in synchronizationwith tables Batch Status (tfgld100) and Transaction Type Batch Status (tfgld101)
SITUATION DESCRIPTION:The page number was not printing on the customer statements. SOLUTION DESCRIPTION:Added "Print page number" option to the Print Statements of Account (tfacr3440m000) session, which will allowthe page number to print on the customer statements. This solution solves defect DF 2671-1.
SITUATION IDENTIFIED IN: Assign Unallocated/Advance Receipts to Invoices (tfcmg2105s000)
SITUATION DESCRIPTION:When there are no invoices to assign to an advance/unallocated receipt a blank form is shown. If one scrolls from form 1to 2, then to 3 and scrolls back then forms 1 and 2 display overflow characters under company and document number fields. SOLUTION DESCRIPTION:The display of overflow characters has been suppressed in the program when there are no invoices to assign to the receipt.This solution solves defect 3046.
SITUATION IDENTIFIED IN: Change Access Mode by Batch (tfgld1108m000)
SITUATION DESCRIPTION:In session tfgld1108m000 the option [K] ( Change Order ) gives 4 possibilities. However, when giving [^F] ( Find ) only
fields 'Fiscal Year' and 'Batch Number' are available. SOLUTION DESCRIPTION:The form and session have been modified to accept values in the alternate key fields when order is changed on the form.This solution solves defect 3060.
SITUATION IDENTIFIED IN: Generate Missing tfgld415 Records (tfcor0218m000)
SITUATION DESCRIPTION:The table ttfgld415 was not written for the combinations Project/Invoice(Purchase Order), Project/Commitment ReverseEntry. The correction program otfcor0218 has to be modified to include these combinations also. Note the problem is nolonger happening with the customer. SOLUTION DESCRIPTION:Added capability to copy data related to Projects into Integration table tfgld415.This solution solves defect 2648.
SITUATION IDENTIFIED IN: Close Periods (tfgld1206m000)
SITUATION DESCRIPTION:When running the Close Periods session in General Ledger with the routine set for 'Final Closing,' the profit and lossbalance does not always equal zero, preventing the user from finally closing.
SOLUTION DESCRIPTION:The problem is caused due to slight rounding differences. The routine that reads Opening and History balances has beenmodified to round these totals within user-defined tolerances.
SITUATION DESCRIPTION:In a multi-site scenerio while entering a purchase order in company A, if company B is entered as the logistic companythen one cannot zoom to select projects from company B. Only projects from company A are displayed. SOLUTION DESCRIPTION:The program has been modified so that when one zooms to pick up the project field, projects from the entered logisticcompany are displayed.This solution solves defect 2984.
SITUATION DESCRIPTION:Enter a PO into co. 401 with finance co. of 400 on the PO header. Complete all PO steps.In co. 400, enter purcahse invoice and on the first screen (tfacp1110s000) enter the logistic co. 401 and then the PO numbercreated earlier. As soon as you hit 'return' from the PO field you get the message ' Purchase order not present in table"Purchase Orders" ' (message code tfacps0210). The system will not let you enter the PO.
SOLUTION DESCRIPTION:This was only a warning message. One could go ahead in the session after the message. This message was cause because avalidation check was made on the existence of the order number. However, this check was made in the company in which thesession was being run and not the logistic company entered by the user. This lead to the error. Now if a logistic company isentered the existence check of the Purchase order will be carried out in the logistic company. This solution solves defect2980.
SITUATION IDENTIFIED IN: Close Year (tfgld6203m000)
SITUATION DESCRIPTION:When running Close Year, total debits do not equal total credits, preventing the user from closing the year. SOLUTION DESCRIPTION:The problem is caused due to slight rounding differences. The routine that reads Opening and History balances has beenmodified to round these totals within user-defined tolerances.This solution solves defect 3102-1.
SITUATION IDENTIFIED IN: Display Integration Transactions by Project / Order (tfgld4510m000)
SITUATION DESCRIPTION:When running this session, the customer can see that there are more than five forms for this session, but can only get to thefifth form.
SOLUTION DESCRIPTION:Due to a change in Baan IVc, the sixth and seventh form for this session should no longer be displayed. The options for thefifth form have been modified, so that there will not be any indication that there are more than five forms for this session.
This solution solves defect 3140.
VRC package component comp_type comp_codeB40 c4 tf tfgld4510m000 Form gld4510m0005
SITUATION DESCRIPTION:Cannot copy a ratio. When trying to copy a ratio from the Source Ratio to Target Ratio, the error "Transaction is on, can'tcontinue" appears. SOLUTION DESCRIPTION:This was due to a problem in the program. A second transaction was tried to be started before the first one was closed. Thishas now been corrected.This solution solves defect 3092.
SITUATION IDENTIFIED IN: Maintain Period Status (tfgld0107m000)
SITUATION DESCRIPTION:When trying to close periods with Maintain Period Status sessions (tfgld0107m000), the user sometimes receives an errormessage 'Unposted transactions present - closing period not allowed', even when there are no transactions present. Thisproblem does not occur when using the Close Periods session (tfgld1206m000). SOLUTION DESCRIPTION:A modification was made to the program script for Maintain Period Status (tfgld0107) in order to indicate any non-finalizedbatches. This solution solves defect 3129-1.
SITUATION IDENTIFIED IN: Match Invoices (tfacp1131s000)
SITUATION DESCRIPTION:1. DF3157: the form for acp1131 displayed improperly - negative amounts were not showing a sign and approved qty wasdefaulting to zero.2. DF3094: Approving Invoices for cost items was generating result transactions with a wrong DR/CR and sign. SOLUTION DESCRIPTION:1. The form for tfacp1131s000 was changed to link the quantity field. The script was edited so that the fields updateproperly.2. The code was edited in the include itfacp0015 to set the debit / credit marker properly
SITUATION DESCRIPTION:When level of tax calculation is set to transaction lines and a Vat code of type shifted is entered the shifted vat amount inhome currency is not updated into the Open Items table tfacp200.Also the approval document created when this invoice is matched and approved is unbalanced. SOLUTION DESCRIPTION:The program was deciding the updation of the shifted Vat amounts in foreign currency and home currency based on different
criteria. This led to the mismatch. Now whenever a Vat amount for shifted tax exists the home currency amount will also beupdated with it.This solution solves defect 17750.
SITUATION DESCRIPTION:An invoice could be approved even with a price difference greater than the price difference defined in the sessiontfacp0150m000 for a particular user. SOLUTION DESCRIPTION:The code for the session tfacp1140s000 was modified so that it checks the allowed price difference tolerances in all cases.This solution solves defect 17537
VERSION(S): tfB40_c SITUATION IDENTIFIED IN: Maintain Posting Data of Standing Orders/Stand-Alone Payments (tfcmg1113s000)
SITUATION DESCRIPTION:When trying to enter a Stand alone Payment through Maintain Payment Advice (tfcmg1120m000) and after entering theappropriate information in session Maintain Posting Data of Standing Orders/Stand-Alone Payments (tfcmg1113s000), amessage box appears with the message "Remaining amount not zero" preventing the ability to save and exit. SOLUTION DESCRIPTION:The Backport for defect DF 394-1 was not done correctly. I backported script from tfB40_b5 to solve this problem. Thissolution solves defect DF 3190-1.
SITUATION IDENTIFIED IN: Match Receipts (tfacp1131s000)
SITUATION DESCRIPTION:In Baan Windows when in Match Receipts session (tfacp1131s000), one record is marked and then the user goes to form 2 andreturns to form 1 and tries to modify the record the system automatically displays form 2 again and hangs. SOLUTION DESCRIPTION:This problem is happening because at some point the program is losing the current form value. A workaround has beeninstalled in the program to force it to go to the correct form.This solution solves defect 17955.
SITUATION IDENTIFIED IN: Post Electronic Bank Statements (tfcmg5222m000)
SITUATION DESCRIPTION:The document column on the EBS posting report (tfcmg522211000) is being truncated. SOLUTION DESCRIPTION:There was an error in the report layout which caused the document number to be truncated. This has been corrected, andthe document number will now be displayed correctly.
SITUATION IDENTIFIED IN:Print Aging Analysis by Customer (tfacr2420m000)Print Aging Analysis by Supplier (tfacp2420m000)
SITUATION DESCRIPTION:In some lines of the aging report the currency specified and the invoice amount are mismatched i.e. against the homecurrency the invoice amount in foreign currency is printed and against foreign currency the invoice amount in home currencyis printed. SOLUTION DESCRIPTION:This problem was noted in the lines relating to invoices with payment schedules. The variables on the report lines had gotinterchanged and hence the wrong amounts appeared against the currencies. The problem has been corrected wherever itoccurred in all aging analysis reports of Accounts Receivable and Accounts Payable.This solution solves defect 3206.
SITUATION IDENTIFIED IN: Match Invoices (tfacp1131s000)
SITUATION DESCRIPTION:In a multi-site environment, upon reloading a saved record only records from the Invoice table with the Logistic company number were being used to populate the amount field, hence the value of this field was incorrect as well as the fields calculated upon its value. Also, Balances were not always being calculated using data from the current record.
SOLUTION DESCRIPTION:The code in the script tfacp1131 was modified so that the form loads invoice amounts forthe proper financial and logistic companies. Also, the record on which the cursor lies is selected before calculating balances, ensuring that the proper amounts are calculated.
SITUATION DESCRIPTION:Report "tccom2401m000" is showing year 0000 for turnover information. When selecting the second report "SupplierPurchase Data".
It has been found that the tccom020.cryr is not being filled therefore is printing as zeros on the report.
SOLUTION DESCRIPTION:Changed the include for Update supplier balances (tccom0005) to update the year correctly to the current year rather thanleave it at 0.This solution solves defect 2860
VERSION(S): tf3.1_b, tf3.1_b1, tf3.1_b2, tf3.1_b3, tf3.1_b4, tf3.1_b5 tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3 tfB40_c SITUATION IDENTIFIED IN: Print Standing Orders (tfcmg1410m000) SITUATION DESCRIPTION:This session was not printing the Posting Data correctly. This occurs when a Sequence numberfor a planned payment date for a Payment Schedule has multiple Posting records assigned to it. SOLUTION DESCRIPTION:The program script was changed to print all posting data under its associated sequence numberwithin a payment schedule for standing orders. This solution solves defect DF 3167-1.
SITUATION DESCRIPTION:1998 batches are attaching to the 1997 run, and 1997 batches are attaching to the 1998 run for Integration transactions. Therun number is hung up 'in use'. Batches from the other year are selected but never processed. SOLUTION DESCRIPTION:The program was missing the functionality to be able to finalize batches in multiple years. The following functionality hasbeen added : 1. If batches from multiple years are existing then the finalization run numbers from the respective years are picked up andbatches in a single year are correctly connected to that year's finalization run number.2. All batches for all years are now taken up for finalization and finalized starting from the lowest year if no errors arefound. If errors are found then the batches can be finalized using the normal finalization procedure after the errors arecorrected.This solution solves defect 3052.
VERSION(S): tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3tfB40L_b_mcr0, tfB40L_b1_mcr0, tfB40L_b2_mcr0, tfB40L_b3_mcr0 tfB40_c SITUATION IDENTIFIED IN: Enter Amounts for Assignments (tfcmg2107s000) SITUATION DESCRIPTION:When modifying an allocation, an error was encountered during the saving process. The systemwas resetting the previous allocation and the remaining amount. An error message was displayedindicating that the Financial Customer groups Discount Transaction was not assigned a G/L account.This was correct, but the user was allowed to continue rather than the system requiring a change tothe entry. As a result, when the user exits back to tfcmg2130s000, the balance on the unallocatedreceipt was now a positive amount for the full amount of the receipt. SOLUTION DESCRIPTION:
Modified the program script for session tfcmg2107s000 to verify that if a Discount amount is entered, the Financial customer/supplier groups Discount Transaction must have a G/L Account entered forit or the Discount amount will be reset to the original value and the following message will be displayed:"Discount account for customer/supplier group (???) not found". This solution solves defect DF 3224.
SITUATION DESCRIPTION:When the session Maintain Account Specifications by Statement Column (tffst1112m000) is used to define a constant valuefor a column in a financial statement and the value of this column is used in the formula to calculate another column theformula does not compute correctly. While computing the formula the value of the constant column is taken as zero. SOLUTION DESCRIPTION:This was happening because of variable value setting problems in the program script. The constant values entered for acolumn and statement account are read from the table and stored in internal arrays in the program. When this array wasaccessed not all values were read into program variables and thus the program processed incorrectly.This solution solves defect 3096.
SITUATION IDENTIFIED IN: Print Options by Integration Element (tfgld4421m000)
SITUATION DESCRIPTION:When compiling the sessions tfgld4421m000 and tfgld4422m000, we are getting the errors:ptfgld44210( 210): Error: Unresolved reference to function 'itfgld4002.fill.pseudo.fields'.ptfgld44210( 212): Error: Unresolved reference to function 'itfgld4002.adjust.field'. SOLUTION DESCRIPTION:Two functions were missing from an include file, causing the compile errors. The missing functions have been re-added,which will take care of the problem.
SITUATION IDENTIFIED IN: Match Electronic Bank Statements (tfcmg5212m000)
SITUATION DESCRIPTION:New EBS Matching session will double pay an invoice. After testing on our development system, I found that if multiple itemsare matched to the same invoice, the posting session will over pay that invoice. It is ok if an multiple items get matched tothe same invoice, as long as it only occurs in situations where the invoice will not be overpaid. SOLUTION DESCRIPTION:The session "Match Electronic Bank Statements" (tfcmg5212m000) has been modified to only match multiple items to the sameinvoice if the combined total of the items will not overpay the invoice. If an item attempts to match to an invoice that willcause an overpayment, the item will not match, its status will remain at "Converted", and the report will display an errormessage, to tell the user why the item was not matched.
SITUATION IDENTIFIED IN:Select Invoices for Payments (tfcmg1220m000)
Select Invoices for Payments (Print Not Selected) (tfcmg1222s000) in B40b and B40c.
SITUATION DESCRIPTION:An invoice with no transaction lines entered with approval necessary for payments. When the Select Invoices for Payments isrun this invoice does not get selected and the reason given for non-selection is that the invoice is not approved. This isincorrect. The correct reason is that the invoice is not balanced. SOLUTION DESCRIPTION:This was just a matter of how the validations were sequenced. Since the 'approval' check was carried out before the'balanced' check and since the very first check the invoice failed is written in the non-selected invoice report thenon-approved error message was written. The sequence of checks has been changed so that the 'balanced' check is carried outbefore the 'approval' check.This solution solves defect 18316.
SITUATION DESCRIPTION:On conversion from B40b to B40c and subsequently from B40c1 to B40c2, the check numbers were not aligned correctly. As aresult, the application will not recognize the historical check numbers after conversion and will also allow you to reuse thecheck numbers that are present in history.
SOLUTION DESCRIPTION:This happened because the check numbers were of type "double" in B40b platform and have been converted to type "string" of15 characters and right aligned. Download the following correction program and run it in B40c environment before running theapplication. This has to be the last step of conversion and must be run prior to attempting to process checks..
This is applicable for Customers who have converted from B40b to B40c platform only.
SITUATION IDENTIFIED IN: Automatic Matching of Purchase Orders (tfacp1230s000)
SITUATION DESCRIPTION:The GUI version of Baan allows the user to change the "no" defaults on automatic match & approve even when the variance isoutside the user's designated tolerances for approval.
SOLUTION DESCRIPTION:The program script was modified to prevent the user from being able to change the "no" default in the GUI product.This solution solves defect 17113-1.
SITUATION DESCRIPTION:Expense tax functionality did not work for projects SOLUTION DESCRIPTION:The code in the include acp0015 was modified to make expense tax transactions for projects as well as other situations.
SOLUTION DESCRIPTION:The code for the lookup session (tfacr2520s000) was edited so that only invoices for the customer in the calling session aredisplayed.
SITUATION IDENTIFIED IN: Background Process for End of Session Updates (tfgld1203s000)Assign Advance / Unallocated Receipts to Invoices (tfcmg2130s000)Assign Advance / Unallocated Payments to Invoices (tfcmg2131s000)
SITUATION DESCRIPTION:1. When trying to finalize transactions generated from linking advanced payments to invoices, a message appears indicatinga background process not yet completed.1. After allocating a payment to an invoice using a transaction type with an update mode of End of Session, the backgroundprocess (gld1203) hangs. Eventually one receives the bshell error message "Error: otfgld1203 : A not terminatedtransaction is aborted". SOLUTION DESCRIPTION:Error 1 was happening because the time the background program waits for the user to release batch + transaction type tostatus 'ready' has been reduced. Thus if the user has not exited to Maintain Transactions level (tfgld1101m000) fast enoughthe background program was logging an error and not processing the transaction. Hence one got the error 'Background processnot yet completed' when one tried to finailze the batch. Now a second call to the background has been placed (in the exitprogram section) of the first sessions (tfcmg2130s000 and tfcmg2131s000) of the transaction type. This will process thetransaction properly.
Error 2 was due to a program error. A transaction was not being ended under some conditions. This has been corrected.This solution solves defect 2470.
SITUATION DESCRIPTION:There is no check to find out whether the document number entered by the user is of type integration. Hence evennon-integration transactions are accepted for processing which leads to wrong results. SOLUTION DESCRIPTION:This check has been added. Only if the document entered by the user is of type integration is the program is allowed to
SITUATION IDENTIFIED IN: Transfer Payments (tfcmg1260s000)
SITUATION DESCRIPTION:The report script for this session was displaying "No empty checks found in check master for this bank/payment method"when all processing completed successfully.
SOLUTION DESCRIPTION:Modified the program script to bypass reading the check master after all payments in a batch have processed successfully. This will eliminate displaying the message when attempting to read the check master when all processing is complete andthere are no more unused checks in the check master. This solution solves defect DF 3395-1.
SITUATION IDENTIFIED IN: Match / Approve Purchase Invoices (tfacp1131s000)
SITUATION DESCRIPTION:In GUI, using the scroll bar to traverse the form caused the message boxes; "Enter Positive Amount" or "Enter NegativeAmount" to appear whether or not these boxes were applicable. SOLUTION DESCRIPTION:The problem was caused by a function which checks whether or not the amount in a field should be positive or negative. Intraversing the field via scrolling, the quantity (a table field) and the corresponding amount (a form field) were getting outof sync and causing the error message to appear. The code in acp1131 was modified so that the quantity and amount fieldsremain in sync when calling this function.
SITUATION IDENTIFIED IN: Match / Approve Purchase Orders (tfacp1131s000)
SITUATION DESCRIPTION:Purchase order lines which were rejected in Approve Receipts were showing up in the Match/Approve Invoices session. Theselines had a qty of zero but an amount equal to that on the purchase order line. This amount should be zero also if the linewas indeed rejected. SOLUTION DESCRIPTION:
The code in the function iacp0021 (called by acp1131) was edited so that if the approved quantity is zero it returns a lineamount of zero. Now rejected lines still appear, but show both a quantity and amount of zero.
SITUATION IDENTIFIED IN: Reset Payment Status (tfcmg1280m000) SITUATION DESCRIPTION:When using a payment method with no anticipated steps, checks cannot be reprinted without creating two entries in the checkmaster for the same amount because the functionality does not allow a check with the status of "Paid" to be reset. Checksusing a payment method with no anticipated steps receive the status "Paid" as soon as they are printed. This leaves nomargin for error if the checks are damaged or need to be voided for any reason. SOLUTION DESCRIPTION:This solution solves defect DF3464-1 and defect DF70372-1 (for tf3.1 and tfB40_b5). Modified program script for session tfcmg1280m000 to allow resetting of the payment status for checks that have a statusof "Paid" and the payment method has no anticipated steps.
SITUATION DESCRIPTION:When you delete a payment batch you still see the record on the screen. After pressing a 'p' or 'n' or exit the screen the screenis updated. This is a little dangerous because you think the record isn't still deleted and you press 'd' again an then you deletean other batch or record!!! SOLUTION DESCRIPTION:This situation was happening when the set of payment advises belonging the last supplier were deleted. Though the recordswere deleted the screen did not refresh to display the previous valid payment advice. This has been corrected.This solution solves defect 18534.
SITUATION DESCRIPTION:Cannot tab through Check Number field (cheq.f). User must click on the next field in order to continue data entry. **NOTE** This problem ONLY occurs in the Baan GUI product.
SOLUTION DESCRIPTION:The default value of Check Number "from" field (cheq.f) was changed to 0. The program script was modified to align thefield according to the domain definition.This solution solves defect 3554-1.
SITUATION DESCRIPTION:In a multi-site environment using Vertex as a tax provider, matched invoice approval in tfacp1140s000 returned the message"Jurisdiction Failed, tax amount not calculated". This was due to the financial company number being passed to thelibrary tccomdll0020. The library needs the number of the logistic company in which the PO was issued. Hence the librarywas returning a zero tax amount which triggered the message and abort in the approval process (tfacp1140s000/itfacp0015). SOLUTION DESCRIPTION:The include (itfacp0015) was edited so that it passes the logistic company number to the library (tccomdll0020).
SITUATION IDENTIFIED IN: Copy Integration Transactions to Finance (tfcor0209m000)
SITUATION DESCRIPTION:We have many unposted integration transactions which are not there in table tfgld416 . So we try to run the correctionprogram tfcor0209m000 . On running we got the error "Error 519(No company number specified or illegal companynumber) on tfgld4168224". Please note we do not have any company 8224.
SOLUTION DESCRIPTION:In Baan IVc, designs of the integration tables have been changed. These changes had not been reflected in the correctionprogram and hence the error. The program has now been changed in keeping with the design changes.This solution solves defect 18542.
SITUATION DESCRIPTION:When matching an invoice including Service Items belong to the cost item group specified in ACP parameters, the second andsubsequent lines are being treated as if they are standard items (not requiring a ledger account be specified and creating aprice difference) SOLUTION DESCRIPTION:This situation had been corrected in tfacp1131s000, so the first lines were being handled correctly. This solution addressessubsequent lines which are handled in tfacp1132s000. The code for this session was modified so that Service Items belongingto the cost item group are handled as cost items. Thus they require the user to specify a ledger account and they create noprice difference.This solution solves defect 3020-2
SITUATION IDENTIFIED IN: Match/Approve Purchase Invoices with Orders (tfacp1130m000)
SITUATION DESCRIPTION:If you scroll through documents in this session you will notice that the Supplier(order) field does not change. This appearsto be random. Apparently the supplier for one document 'sticks' and remains for the following documents as well. SOLUTION DESCRIPTION:The field was not initialized each time a new record was read. This led to the problem. It has not been corrected.This solution solves defect 3483.
SITUATION IDENTIFIED IN: Maintain Business Information Details (tffas0113m000)
SITUATION DESCRIPTION:When a Fixed Asset has more than one Information Number field, the Information Code and Description associated with thisnumber is not automatically refreshing leaving the first occurrence to display. SOLUTION DESCRIPTION:Modified the program script to display the correct Information Code and Description for the associated Information number. This solution solves defect DF 3539-1.
SITUATION DESCRIPTION:When the user raises a new batch containing an invoice and a credit note everything is ok. When the user thenamends the credit note field ORIGINAL INVOICE to contain the newly raised invoice number, then the status of thecredit document changes to FREE instead of READY and the message CONTROL AMOUNT NOT MATCHING is displayedin the status. SOLUTION DESCRIPTION:Modified the script for function tfgld0019 to bypass adding the tfgld102 transaction that are created when linking a creditnote to an invoice to the running total that is used to compare against the Control Amount entered in sessiontfgld1101m000. This solution solves defect DF 18420-1.
SITUATION IDENTIFIED IN: Change Default Values for Finalization (tfgld1113s000)
SITUATION DESCRIPTION:When Selecting Batches for Finalization (tfgld1110m000), the Journal Report Number would alwaysdefault to 3 (sorted by Transaction Category). SOLUTION DESCRIPTION:Modified the program script to display the screen defaults and use the defaults in the finalization processwhen the defaults are saved in the Options drop down menu (save defaults) in session tfgld1113s000. This solution solves defect DF 3595-1. The following steps must be performed one time for each userwho wants to change their default values for the finalization process.
1. Enter session tfgld1110m000 (Select Batches for Finalization).
2. Insert for a new finalization run, then click Select (GUI) or enter "Y" (ASCII). This will bring you to session tfgld1111s000.
3. Zoom (ASCII) or click Special (GUI) and select "Accept Options for Changing Defaults". This will bring you to session tfgld1112s000 (Accept Options for Changing Defaults). 4. Select option 2 - Change Default Values for Finalization and this will bring you to session tfgld1113s000 (Change Default Values for Finalization).
5. Change Field Number 3 (Journal Report Number) to the report number you would like.
1 = Sort by Document/Company2 = Sort by Company/Document3 = Sort by Transaction Category
6. Click Options (GUI) or enter "o" in choice field (ASCII) and select Save Defaults.
7. Save and exit back to session tfgld1111s000 (Select Batches for Finalization).
SITUATION IDENTIFIED IN: Match Purchase Invoices (tfacp1131s000)
SITUATION DESCRIPTION:In the case of cost items (spec.cost.item = true), the zoom to tfacp1133 from tfacp1131was being done before switching to the financial company. This resulted in acp1133 not populating correctly and anabort/error 506 upon leaving acp1133.
SOLUTION DESCRIPTION:The code in tfacp1131 was modified so that the company number is switched to the financial company before callingtfacp1133 in the case of cost items.This solution solves defect 3662
SITUATION DESCRIPTION:The open invoice amount for the suppliers is updated wrong when we run the session write off payment differences. Theamount is added instead of subtracted.
SOLUTION DESCRIPTION:The program has been corrected to deduct the payment difference amount instead of add it to the supplier invoice total.This solution solves defect 18673.
SITUATION IDENTIFIED IN: Assign Credit Notes to Invoices (tfacr2120s000)
SITUATION DESCRIPTION:tfacr2120s000 (Assign Credit Notes to Invoices) - find function does not return particular document search. SOLUTION DESCRIPTION:The program did not use the entered values for document type and document number. It only used the value of the customernumber entered. Hence the first eligible record for that customer got displayed instead of the one requested by the user.This has now been corrected.This solution solves defect 3654.
SITUATION DESCRIPTION:The background session used to hang sometimes after leaving the session "Maintain Anticipated Receipts"(tfcmg2111s000).
SOLUTION DESCRIPTION:The above-mentioned session used to leave the documents with the status "in use - maintain" based on certain conditions.The program script has been changed and this solves DF 3562-1.
SITUATION DESCRIPTION:If in tffst4450 (Print Consolidated Statement) accounts are selected with sublevel > 0 and not the child accounts, the parentaccounts get value 0,00. If all accounts are selected (childs & parents) the parents do get the correct value. This is not thecase in session tffst1450m000 (Print Financial Statements). SOLUTION DESCRIPTION:This was happening because the totals for the children account were being deducted from the parent's total as the childrenstatement accounts were not in the range of statement accounts specified by the user. A new form field is now accepted fromthe user "Recalculate Statement Accounts". If the user enters 'yes' here then the children account amounts will also beconsidered while calculating the parent account amounts. A 'no' will disregard the children account amounts while arrivingat the parent account amounts.This solution solves defect 18648.
SITUATION DESCRIPTION:It was possible to delete a subcontractor without regard to open invoices for that subcontractor. If this was done, theamount for the subcontractor's invoice which was to be allocated to the blocked account would not be paid.
SOLUTION DESCRIPTION:A check was added to the session tfacp3110m000 which queries the acp200 and acp303 tables for invoices for thesubcontractor. If any are found, the user gets the message (tfacps0212) "Invoices present; deleting not allowed", and thedelete process is stopped.
SITUATION DESCRIPTION:When maintaining a non-matching payables invoice in this session, credits were displaying and posting as negative creditsregardless of the "negative amounts allowed" setting in ACP parameters.
SOLUTION DESCRIPTION:The code for the session was edited so that the acp parameters setting is checked before allowing negative amounts to becalculated or entered in this session. If the acp setting is negative amounts allowed = no and the user tries entering anegative amount an error message now appears and the input is rejected.
VERSION: tfB40_b, tfB40L_b_mcr0 tfB40_c, tfB40L_c_mcr0 SITUATION IDENTIFIED IN: Assign Unallocated/Advance Receipts to Invoices (tfcmg2105s000) SITUATION DESCRIPTION:When changing allocation type from manual to automatic the allocation amounts were not recalculated. The allocation typewould display Automatic but the allocation amounts remained the values entered for the manual allocation. SOLUTION DESCRIPTION:Modified the program script to reset the values entered for a manual to automatic allocation when the allocation type ischanged. This solution solves defect number DF 3655-1.
SITUATION IDENTIFIED IN: Print ACP Distribution Report (tfacp4410m000)
SITUATION DESCRIPTION: If the user selected a Purchase Order or range of Purchase Orders, the session would notlaunch report but would return the error message "no data within selection"
SOLUTION DESCRIPTION: The code for the session was modified so that the query matched the PO number with the POnumber in the acp200 table rather than the Document number in the table as was originally the case.
SITUATION IDENTIFIED IN:Maintain Period Status (tfgld0107m000)Close Periods (tfgld1206m000)Close Year (tfgld6203m000)
SITUATION DESCRIPTION:The period setup at this customer is that the Fiscal Year ends in March, but the Tax Year ends in February. There are 12 periods in both Fiscal and Tax years. All transactions for Fiscal period 1997/08 are processed.This is equivalent to Tax period 1997/09. Also, there are Integration transactions present for Fiscal period 1997/09,which is Tax period 1997/10. When we tried to close Tax 1997/09, we get the message : Not all Integration transactions (SalesInvoices) are posted for year 1997. The session seems to check if there are transactions in the Tax period of the Fiscal year.But it should check if there are transactions in the Tax period of the Tax year.
SOLUTION DESCRIPTION:When one has different dates for fiscal and tax years and a tax period is being closed, the check for existence of integrationtransactions was done in the fiscal year instead of the tax year. Hence even though no integration transactions existed forthe tax period an error was reported. This has been corrected.This solution solves defect 18438.
SITUATION DESCRIPTION: The report was missing divider lines at the bottom of the header and the header containedextraneous characters before and after the label,"Trial Balance For:"
SOLUTION DESCRIPTION: The reprt was edited and extra characters removed, divider lines added and recompiled.This solution solves defect number 3720.
SITUATION DESCRIPTION: In a multi-logistic / single-finance situation, the tax entry was posting to the logistic ratherthan the finance company.
SOLUTION DESCRIPTION: The code in the include tfacp0015 was edited so that if the current company and the logisticcompany numbers are the same it posts to the current company (which would be the finance company). If the current andlogistic company numbers are different, the the entry is made for the finance company entered on the PO header.This solution solves defect number 3820.
SITUATION IDENTIFIED IN: Import Journal Voucher Batches by ID Number (tfgld2215m000)
SITUATION DESCRIPTION:Customer cannot create a batch when running session tfgld2215m000. tfgld2215m000 does not perform a commit until the veryend, locking the tfgld014 table until the session completes. Customer would like to know if it is possible to insert commitsin tfgld2215m000 before the end. SOLUTION DESCRIPTION:The fetching of the next batch number to use has been moved into another sub-session. This will avoid the Last Used BatchNumber table (tfgld014) being involved in long transactions. Please note that since this solution contains a new session, thedata dictionary needs to be created again after importing the modified components.This solution solves defect 3754.
SITUATION DESCRIPTION:ACP Parameter "item group of cost item to be specified" has value. A Purchase Order for an item belonging to that group isbeing matched and approved. Even if the corresponding invoice is being matched for zero quantity and partial amount, theentire PO line amount is being reversed instead of the amount of the invoice only. SOLUTION DESCRIPTION:Suppose the PO is for 10 items of type cost @ 10, giving amount 100. If an invoice of amount 10 and quantity 0 is matchedand approved then following are the entries :Invoices to be Received 100To Raw Material 100
Since the amount of the invoice is 10 in the above reversal entries amount 100 is wrong. It should be :Invoices to be Received 10To Raw Material 10
This amount of 100 was being calculated at the time of matching. The routine which calculated this amount, assigned thewhole PO line amount whenever the quantity on the invoice was zero. This has now been over-ridden in the programsspecifically for cost item invoices with quantity zero to be equal to the invoice amount.This solution solves defect 3837.
SITUATION DESCRIPTION:If data in the Documents table tfgld018 cannot be read for some reason at run-time then the finalization run returns anambiguous message. The message states that finalization has failed - see error log, and the error log gives precisely thesame message. SOLUTION DESCRIPTION:In case of failure to read the Documents table a different error message specifying that reason has been added to the programscript. This message will put in the log table.This solution solves defect 18800.
SITUATION DESCRIPTION: After installing solution 2550 (df3483), when the supplier number is changed, the changed value isoverwritten with the original value when continuing on to the Match Invoices session (tfacp1131s000). It should be notedthat when scrolling through the records in the Maintain / Approve session (tfacp1130m000) that the records will always returnto the original value as that is based upon the value in the Purchase Order (from table tdpur040) already associated with therecord in the Open Invoices table (tfacp200).
SOLUTION DESCRIPTION: The code in the program script for tfacp1130m000 was edited to allow the changed value for thesupplier to be passed on to tfacp1131s000 when the continue option is executedThis solution solves defect number 18101, 18890, 18957.
SITUATION IDENTIFIED IN: Assign Unallocated/Advance Payments to Invoices (tfcmg2106s000). SITUATION DESCRIPTION:Vat transactions (nett/gross) where made in session Maintain Bank Transactions (tfcmg2100s000) for advance paymentswith a Vat-code, Vat-amount of zero and with a Tax Type of "On Payments". These Vat transactions (nett/gross) were notreversed out when the advanced payment was reconciled in session tfcmg2106s000). SOLUTION DESCRIPTION:Modified the program script to reverse Vat transactions (nett/gross) that were made for advance payments that have aVat-code, Vat-amount of zero and a Tax Type of "On Payments". This solution solves defect number 19090-1 .
SITUATION IDENTIFIED IN: Create New Trans. in gld416 from gld410/gld418, Reset Posted Flag (otfcor0224)
SITUATION DESCRIPTION:This is a correction program has been ported to the B40c and it resets the status of posted integration transactions tounposted based on the tables gld410/gld418. SOLUTION DESCRIPTION:The changes for B40c are incorporated in the script. This solution solves defect Defect Number 3385-1.
SITUATION DESCRIPTION:When a tax code of space with setting Purchase Expense Tax = yes was used while creating invoices error message "ExpenseTax Code not allowed on Misc. Invoices on Header", tfacps0209 for the second insert onwards. This message does not get
displayed while inserting the first record. SOLUTION DESCRIPTION:In finance a tax code of spaces or empty is to be treated as if no tax code is entered (except in integration transactions).The condition, which validated for the above error, did not have this check. Now this check is made only if a non-space taxcode is entered. The reason why the message did not appear the first time was because the database validation condition forthe country and tax code is done only if both the fields are filled (Mandatory unless empty). Since an empty tax code wasbeing entered, tools did not make the reference check on the table Tax Codes by Country (tcmcs036) and hence the data intcmcs036 was not available for further validation at that point. Later on in the program, this table is read, and hence forthe second insert onwards for the same tax code the error message gets displayed.This solution solves defect 3895.
VERSION: tf3.1_b tfB40_b, tfB40L_b_mcr0 tfB40_c, tfB40L_c_mcr0 SITUATION IDENTIFIED IN: Create Intergroup Transactions (tfgld2201m000) SITUATION DESCRIPTION:When typing the Source Company's information in and you zoom on the Fiscal or Reporting period, it only allows you to seethe Tax periods. You can not switch to the Period Type you want to zoom to. SOLUTION DESCRIPTION:Modified program script so that when zooming on the Source Company's information Fiscal or Reporting Period, theappropriate Fiscal or Reporting Period Type is used in zoom to session Display Period Master (tfgld0505s000). Thissolution solves defect number DF 3958-1.
SITUATION DESCRIPTION:Finalized batches were displayed and the user could enter new transaction types and transactions in the previously finalizedbatch.
SOLUTION DESCRIPTION:Some batches with the termination status were selected and displayed because the batch status in some cases was empty orready. The script gld1101 has been modified to skip all records that have the finalization status as 'finalized' even if thebatch staus is not finalized. This solution solves defect 3933-1.
SITUATION DESCRIPTION:When the Composing Limit is set to three or more, Composing Option set to Invoices and the field tccom020.ocus "OurCustomer Number" is used as the invoice reference, then invoices per check would print incorrectly.
SOLUTION DESCRIPTION:Modified program script so that the Composing Limit would be used correctly when the field tccom020.ocus "Our CustomerNumber" is used as the invoice reference. This solution solves defect number DF 3981-1.
SITUATION DESCRIPTION:The amount field on the tfacp3525m000 screen isn't calculating correctly. The 1-30 days amount fields are correct, but theover 91 days field is getting an amount which is much higher than it should have. SOLUTION DESCRIPTION:There was a small problem in the program script which was causing the wrong values to be added to the over 91 days amountfield. The problem has been corrected and the values in this field should now be correct.
SITUATION DESCRIPTION: If the city name passed to the tax provider (VERTEX) has more than 20 characters, the transaction fails, returning the errormessage,"invalid city,state,zip"
SOLUTION DESCRIPTION:The code in tcapidlll002 was edited so that the city name passed to Vertex is no longer than 20 characters.This solution solves defect number 3876.
SITUATION IDENTIFIED IN: Assign Advance/Unallocated Receipts to Invoices (tfcmg2105s000)
SITUATION DESCRIPTION:In GUI use session Maintain Transactions (tfgld1101m000) of type receipt allocation. Go to session tfcmg2130s000. Select areceipt for a customer with no outstanding invoices. Go to session tfcmg2105s000 - Assign Unallocated /Advance Receipts toInvoices. Go to form 3. Go back to form1. All fields are filled with overflow characters. SOLUTION DESCRIPTION:The display of overflow characters has been suppressed in the program when there are no invoices to assign to the receipt.This solution solves defect 3988.
SITUATION DESCRIPTION:When we using this transaction type, and we're on the session tfacp2110s000 (Maintain Purchase Invoice Corrections), thezoom will let us select from many different transaction types, including those that are not of type Purchase Invoice. Wewould think that a session for Maintain Purchase Invoice Corrections would only let you correct transactions that are oftype Purchase Invoice. SOLUTION DESCRIPTION:The validation to determine the type of record selected for processing was missing in the program. This validation has beenadded so that only valid Purchase Invoice related records are selected for processing in the session.This solution solves defect 4027.
SITUATION IDENTIFIED IN: Select Invoices for Payment (tfcmg1220m000)
SITUATION DESCRIPTION:A standing order payment with a payment schedule does not get selected for payment in tfcmg1220m000 (Select Invoices forPayment) when the selection is run for the specific payment date indicated in the schedule. It gets selected only when the duedate selection is left wide open. SOLUTION DESCRIPTION:When a standing order has a payment schedule attached, the payment date on the standing order is left blank since there aremultiple payment dates involved. The selection for payment procedure did not cater to this, and always expected the due dateto be filled. This has been corrected so that standing orders with schedules attached are selected based on the due dateindicated on the schedule.This solution solves defect 4036.
VERSION: tfB40_c SITUATION IDENTIFIED IN: Update period data for tfgld410 (Integration transactions),
Correction Program (tfcor0410) SITUATION DESCRIPTION:Original correction program (tf3.1, tfB40b) would only use tfgld410.crdt (transaction date) to update the period data. If thetransaction date (tfgld410.crdt) not present, then no updates would take place. SOLUTION DESCRIPTION:Modified script to update period data and transaction date (tfgld410.crdt) with log date (tfgld410.trdt) if transaction date(tfgld410.crdt) is not present. Also used Integration References table tfgld418 (field tfgld418.sint <> tfgld.sint.posted) todetermine transactions to update on tfgld410 (Integration transactions). Table tfgld418 (Integration References) is new totfB40c and was not currently used in the script. This solution solves defect number DF 3976-1.
SITUATION DESCRIPTION:The exchange rates used to enter the Purchase Invoice and the one used in the approval documents sometimes differ. Thishappens even when there has been no change in the exchange rates of the currency involved between the time the invoice wasregistered and it was approved. Due to the differences in the exchange rates, currency difference may arise when in fact thereis no reason for a currency difference. SOLUTION DESCRIPTION:The exchange rate to be used for approval has to be the same as the rate used in registering the invoice. To achieve this the program was
calculating the rate using the amounts in home currency and foreign currency stored in the invoice record of Open Items table tfacp200. Due to the calculation involved sometimes it led to a rounding difference which is why the approval transactions showed a slightly different rate. The concerned
programs have now been modified to pick up the correct exchange rate using the following criterion. If no change in exchange rates was noted from the time the invoice was registered to the time of approval the rate is picked up from the Open Invoice table tfacp200. If the exchange rate has changed in between then it is picked from the invoice records available in Transactions tables tfgld102 or tfgld106 which ever is applicable.
SITUATION IDENTIFIED IN: Add Range of Checks (tfcmg2210s000)
SITUATION DESCRIPTION:When you insert a range of checks via the zoom option (or the insert button) and the check numbers are greater than 10digits, then the checks that are generated have negative numbers.
SOLUTION DESCRIPTION:There was an overflow problem in the size of field used for generating check numbers and this has been corrected. Thissolution solves DF 4095-1.
SITUATION IDENTIFIED IN:Assign Credit Notes to Invoices (tfacp2120s000)Assign Invoices to Credit Notes (tfacp2121s000)
SITUATION DESCRIPTION:Once a credit note and invoice are linked it is no longer possible to approve the invoice. Why does it let you link and thennot allow you to approve? SOLUTION DESCRIPTION:The restriction of not allowing linked invoices to be approved has been recently added. Please refer to defect 12826 (solution12181) for the reason of why this functionality was restricted. To support this new functionality if a credit note or invoicecan be approved and before approving if they are selected for linking a warning message indicating that the Invoice is notyet approved will be displayed in the linking sessions.This solution solves defect 3759.
SITUATION IDENTIFIED IN: Convert Electronic Bank Statements (tfcmg5202m000)
SITUATION DESCRIPTION:When using EBS, the amounts are not always being converted correctly. The value 813.06 is being converted as 813.60.
SOLUTION DESCRIPTION:When reading the amount from an EBS file, there was a problem which caused the zero in the decimal portion to be left out. This has now been fixed.
SITUATION IDENTIFIED IN: Global Selection of Batches for Finalization (tfgld1210s000)
SITUATION DESCRIPTION:When the company parameters (tfgld0103m000) are set as 'Default finalization per batch = Individual User', it should not bepossible to select batches belonging to other users for finalization. This however, is possible in the Global Selection ofBatches for Finalization by giving a different user code. SOLUTION DESCRIPTION:When the above parameter is set, the values from and to for the user codes will no longer be accepted, but will be defaultedto the current user. Hence with the parameter setting at individual users, only batches belonging to the user running thesession will be considered for selection.This solution solves defect 4018.
SITUATION IDENTIFIED IN: Maintain Chart of Accounts (tfgld0108m000)
SITUATION DESCRIPTION:When starting the session, first an empty form is shown instead of the first record. When we want to insert a new ledgeraccount, we have to click on the button "insert" twice. After the first time, the field ledger account has the color grey.When we click on "insert" again, the field becomes white and we can insert a new ledger account. SOLUTION DESCRIPTION:There was a bad fix and this has been corrected. This solution solves defect DF 19613-1.
SITUATION IDENTIFIED IN: Post Electronic Bank Statements (tfcmg5222m000)
SITUATION DESCRIPTION:When posting electronic bank statements, the customer is getting the message "Supplier with 'potential' status not allowed." onthe audit report. The supplier status is blocked for payments, but it is not a potential supplier. The customer should nothave to unblock the supplier to be able to reconcile this check.
SOLUTION DESCRIPTION:The session was checking the supplier status and would give the error message "Supplier with 'potential' status not allowed."for any supplier who's status was anything but "Actual". This included suppliers with a status of "Blocked for Payment". Since the supplier status should have already been checked at the time that the payment was composed, it is not necessary tocheck the status again when the reconciliation is done, therefore, this check has been removed.
SITUATION DESCRIPTION:Transaction is on "can't continue" when using tax at line level. SOLUTION DESCRIPTION:This was happening because a second transaction was being started in the program before the prior one was completed. Now astatement indicating the completion of the prior transaction has been added in the program.This solution solves defect 4146.
SITUATION DESCRIPTION:The report was including lines for invoices which had 0 quantity and 0 $amount, but it was replacing the 0 amount with thefull amount from the purchase order line.
SOLUTION DESCRIPTION:The script for tfacp1432m000 was edited so that if the received quantity is 0 and the received $amount is also 0 the line doesnot appear on the report.This solution solves defect number 19267.
SITUATION DESCRIPTION:If parameters were set to 'Group All Letters under Highest Letter' when adding a new record in tfacr3110m000, the newinvoice was assigned the highest letter number for all invoices in the reminder advice even though the highest letter codewas of another customer.
SOLUTION DESCRIPTION:Now (tfacr3110) also does a check on the customer number when it checks maximum letter number. This solution solvesdefect number 19591-1.
SITUATION IDENTIFIED IN: Match Receipts (tfacp1131s000)
SITUATION DESCRIPTION: In GUI only, if the user clicked the arrow button to access the drop-down box to select a matchtype, the Matched Amount and Balance fields would recalculate and indicate a wrong value. This was due to the Invoice amountbeing the last field on the form, and clicking the arrow button fired the after field event for the last field. This eventincluded calculations to update the Balance and Matched Amount fields, but without first backing out the current amount.
SOLUTION DESCRIPTION: A non-display field was added to the form for this session (tfacp1131s0001) as the last field. This non-display field prevents the calculation tied to the invoice amount field from occurring when the drop-down box isaccessed via the arrow buttonThis solution solves defect number 18971.
VRC package component comp_type comp_codeB40 c4 tf tfacp1131s000 Form acp1131s0001B40 c4 tf tfacp1131s000 Form acp1131s0001B40 c4 tf tfacp1131s000 Form acp1131s0001
SITUATION DESCRIPTION:The open amount of an invoice in (tfacr3130m000) was different than the open amount of the same invoice in session(tfacr3110m000) 'Maintain Reminder Advice'.
SOLUTION DESCRIPTION:It was found that (tfacr3130m000) did not consider the discount amount or late payment surcharge that was entered for anadvanced receipt in 'Enter Amounts for Assignment' (tfcmg21007s000). This solution solves defect number 4174-1.
VERSION: tfB40_c, tfB40L_c_mcr0 SITUATION IDENTIFIED IN: Transfer Payments (tfcmg1260s000) SITUATION DESCRIPTION:This session was displaying message tfcmgs0190 (No empty checks found in check master for this bank/payment method)when the checks were present in the check master. SOLUTION DESCRIPTION:Report script was modified to use val function (converts a string to a double) for the check number so that it will find thenext available check in the check master. This solution solves defect number 4153-1.
SITUATION IDENTIFIED IN: Select Batches for Finalization (tfgld1111s000)
SITUATION DESCRIPTION: When the update mode is set to real time for the approval transaction type, the batch cannot befinalized due to a "Background Process Not Completed" error in the select batches session (tfgld1111).
SOLUTION DESCRIPTION: The background status field in table tfgld102 was not being updated for the first approval recordin the batch. This caused the error in tfgld1111. The scripts for the real-time background programs (tfgld1201 andtfgld1203) were modified so that the first record would no longer be skipped.This solution solves defect number 4132.
SITUATION DESCRIPTION: The report was printing with no receipt date. No financial transactions are generated fromthese receipt lines, therefore they should not be displayed on the report.
SOLUTION DESCRIPTION: The script for the session tfacp1432m000 was edited so that if the receipt date in the receipt tableis zero, the record is not sent to the report.This solution solves defect number 4195.
SITUATION DESCRIPTION:Corrections made to invoice amounts using the correction document type appear as amount paid in the Maintain Schedulesessions. SOLUTION DESCRIPTION:The programs have been modified so the correction amounts do not get added to the amount paid fields.This solution solves defect 4213.
1. If an invoice is matched to a receipt line for a zero qty and the line is set to closed = no, the invoice dollars are neverconsidered in the in the final calculation for the purchase result or the latest and avg purchase price. * this will also leave thedollars in the a/p accrual acct.
2. If an invoice is matched to a receipt line for a zero qty and the line is set to closed = yes, the invoice dollars do create apurchase result, but if this is done before a "quantity line " is matched it is never considered in the in the final calculationfor the latest and avg. purchase price.
*If this is done after a quantity line is matched, then it works okay. SOLUTION DESCRIPTION:The updation of the average purchase price (while approving) is done if the user sets the Closed flag = "Yes" while Maintaining Matched
Receipts (tfacp1132s000). However the formula for this price calculation needs to use the matched quantity to calculate the average unit purchase price. If quantities on all lines being closed (closed = yes) are zero then the new average purchase price is the same as the old average purchase price. To avoid this from happening the user will be allowed to close a line in tfacp1132s000 i.e. set closed = yes only if a non-zero quantity exists in the current line or prior matched and not yet closed invoice lines. This new condition also needs a non-zero receipt quantity to work as specified above. This will also help keep the Purchase Result entries generated in Finance to be in sync with the average price calculation in Distribution.
SITUATION IDENTIFIED IN: Create New Trans. in gld416 from gld410/gld418, Reset Posted Flag (otfcor0224)
SITUATION DESCRIPTION:These correction programs have been ported to the B40c and it delete & reset the status of posted integration transactions
to unposted based on the tables gld410/gld418. SOLUTION DESCRIPTION:The changes for B40c are incorporated in the script. This includes the table changes that were made in B40c. **NOTICE** After running tfcor0223, the user MUST run tfcor0224, then run Rebuild Ledger History (sessiontfgld3203m000)!!!
SITUATION DESCRIPTION:When this session zooms to session (tfacp1103s000) the changes made in (tfacp2110s000)are not shown when using an ORACLE database.
SOLUTION DESCRIPTION:A commit.transaction was added to write the changes before zooming to (tfacp1103s000). This solution solves defectnumber 4192.
SITUATION DESCRIPTION:The budget amounts for ledger accounts are doubled when using higher dimensions for a single ledger account in thebudget. Problem in tfgld3402.
SOLUTION DESCRIPTION:This solution solves defect number 11075.The budget has to be counted for all the amounts where the dimension sub-level = 0. So, if a dimension code is defined fora dimension in the session Maintain Budget amounts and Quantities (tffbs1101m000), and this combination of dimension anddimension code has a sub-level higher than 0, then all the amounts for this budget will be skipped.
SITUATION IDENTIFIED IN: Print Trial Balance with Dimensions ( tfgld3405m000)
SITUATION DESCRIPTION:The total Budget Amount was calculated wrongly for the column 'To Period'. The total budget amount should be calculatedonly for those dimensions whose sub level is 0.
SOLUTION DESCRIPTION:The error occurred because a print condition to check that addition was not done for the parent dimension had been missed.This has been corrected by adding the required print condition.
SITUATION DESCRIPTION:Patch for defect 10359 was applied, justification problem was fixed,string recognition was also fixed, but the footer nowappears on the next page rather than on the bottom of the first page, like before the patch was installed.
SOLUTION DESCRIPTION:.From now on the footer will be printed at the end of the page and the $-variable will be substituted.
VERSION: tf3.1_b, tfB40_b, tfB40_c SITUATION IDENTIFIED IN: Maintain Posting Data of Standing Orders/Stand Alone Payment (tfcmg1113s000)
SITUATION DESCRIPTION:The posting data information entered in the "Maintain standing orders" session did not reappear when the session calls it asecond time.
SOLUTION DESCRIPTION:This problem was appearing because of the changes made under the ID 10240296. Source has been repaired and now theposting datadetails are visible.
VERSION: 3.1_b, B40_b, B40_c SITUATION IDENTIFIED IN:Maintain Bank Transactions (tfcmg2100s000)
SITUATION DESCRIPTION:This defect showed up after a solution was made and delivered for defect 13018. If you want to book tax on advancedreceipts and vat country and vat code in not empty, but the vat amount is zero, no nett/gross booking is made. Allthough itis reversed when assigning the advanced receipt to the invoice via tfcmg2105s000.
SOLUTION DESCRIPTION:The check on a zero vat amount is wrong. Only if vat code and vat country is empty, nett/gross bookings should not bemade (not in tfcmg2100s000 and not in tfcmg2105s000)..
SITUATION DESCRIPTION:When during the unapproval procedure, a negative credit amount is entered in the session "Maintain Matched PurchaseInvoice Transactions " (tfacp1130s000 ), an error message "Still transactions to be entered, invoice not approved" isgiven. The invoice cannot be unapproved.
SOLUTION DESCRIPTION:This solution solves defect 13510 & 12826.There are two situations in this case:
1. The invoice and creditnote are first linked and then the invoice is approved.Now, reverse approval of the invoice has been made possible.
2. The invoice and credit note are first seperately matched and approved and then linked.Reverse approval is not possible because the postings which would be made cannot be balanced. Now, a message is
given by the system.The credit note should first be unlinked from the invoice. Then the invoice can be unapproved.
SITUATION IDENTIFIED IN:Write off Currency differences (tfacr2250m000) Write off Currency differences (tfacp2240m000)
SITUATION DESCRIPTION:While running session 'Write Off Currency Differences" the system is creating records in Non finalised Transactions. Whenthe system creates more than 32676 records for a single document an error occurs. There are no more records created in 'NonFinalised Transactions' but 'Open Items" is still updated which causes a lot of differences on the control account checklist.
SOLUTION DESCRIPTION:The structure of the program is changed. Now the problem DF14320 is rectified.
SITUATION DESCRIPTION:There is no check on the existence of the order number entered in the session. A check should be built to see if the orderentered is a valid purchase order.
SOLUTION DESCRIPTION:This solution solves defect number 15607. A check is build in to read table tdpur040 to check for the purchase order.
SITUATION DESCRIPTION:Bad performance in combination with Oracle.Marking as DF 15464-2.
SOLUTION DESCRIPTION:This solution solves defect number 15464.Or construction replaced by skip.io(), to avoid sorting, and to speed up fetching of first records.
Background proces finalisation (tfgld1213s000)Background proces real time (tfgld1201s000)Background proces end of session (tfgld1203s000)
SITUATION DESCRIPTION:It is possible to have finalised batches containing unbalanced intercompany documents. Theprograms tfgld1201/1203/1213 are adjusted to make sure that not one line is missing. The programtfgld1211 is adjusted to make sure that the transactiontype for the original and target companyis completely balanced.
SOLUTION DESCRIPTION:Before finalising the batch the background processes check if the batch contain unbalanced documents.This solution solves the defect number 14533.
SITUATION DESCRIPTION:When printing the VAT-analyses there is no description printed for VAT-code <space> although in tcmcs0137m000 there is adescription filled.Other VAT-code-descriptions are printed fine.
SOLUTION DESCRIPTION:This solution solves defect number 16042 . Description of VAT-code is being picked up now for the above mentionedsituation.
SITUATION IDENTIFIED IN: Process Delivered Sales Orders (tfglddll4010)
SITUATION DESCRIPTION:The fields container(cntr) and inbound position(inpo) were left empty in table tfgld410, when the performance booster isactive. In B40_c this was only applicable for the field inbound position(inpo).
SOLUTION DESCRIPTION:This solution solves defect number 16188. When performance boosters were active the contents of these fields were notcopied, copying has been added.
SITUATION DESCRIPTION:It is not possible to follow what the program is doing.
SOLUTION DESCRIPTION:This solution solves defect number 15810.On the screen it is possible to follow which transactions and document is handled by the program.
SITUATION DESCRIPTION:The fields Blocking code, Order and Reason for Payment were not blanked in Maintain Purchase invoices when insertingmore than one purchase invoice records. The fields Order and Problem Code were not blanked in Maintain Sales Invoiceswhen inserting more than one Sales invoice records.
SOLUTION DESCRIPTION:This solution solves defect number 16246. Now the fields are blanked everytime a new record is inserted.
VRC package component comp_type comp_codeB40 c4 tf tfacr1110s000 Form acr1110s0002B40 c4 tf tfacp1110s000 Form acp1110s0002B40 c4 tf tfacp1110s000 Form acp1110s0001
SITUATION DESCRIPTION:Message "Ledger account < > not filled for company xxx"The case is that a mandatory dimension for a tax l/a is not filled in tcmcs0136m000 "Maintain tax codes by country"
SOLUTION DESCRIPTION:This solution solves defect number 15387.Created a message tfglds0151"Dimension not filled for tax ledger account"
SITUATION DESCRIPTION:When deleting a transaction type from the batch of type "recurring transactions" the tfgld103 records where not thrown awayalso. Because of the existing tgld103 records, the period can not be closed.
SOLUTION DESCRIPTION:The correction program is the first part of the solution and is able to check three kinds of errors:1. Check if recurring transactions can be found in tfgld102 and tfgld1062. Check if recurring transactions instructions exist for deleted batches.3. Check if the original transaction is deleted when all the recurring transactions are posted.
TAKE CARE: The correction program can only be used if ALL BATCHES with recurring transactions are finalized.
Second part of the solution:When a transaction type is deleted from a batch also the recurring transactions instructions should be deleted. This solutionsolves the defect number 15216.
VERSION: 3.1_b, B40_b, B40_c SITUATION IDENTIFIED IN:tfgld6203m000 Close year
SITUATION DESCRIPTION:Question: 'Delete history for fiscal year xxxx' was sometimes given after some hours.
SOLUTION DESCRIPTION:This solution solves defect number 16360.Question is replaced by field 'Delete History upto Fiscal Year:" that can be filled in the form.
VERSION: B40_b, B40_c SITUATION IDENTIFIED IN:tfacp2433m000 Print Supplier's Total Balance
SITUATION DESCRIPTION:
When printing the report of session tfacp2433m000 the system asks several times for a device.
SOLUTION DESCRIPTION:This solution solves defect number . 2173The system will now only ask one time for a device. Depending on the data filled on the form a report will be printed.
SITUATION DESCRIPTION:The format for the BGC-file contains several errors.
SOLUTION DESCRIPTION:This solution solves defect number 16364.This fix includes for example:- The two spaces between the bank account numbers for line 40 have been decreased to one space.- The total number of records is printed now (Not only the number of detail lines anymore).- The calculation of the total of the bank account numbers has been altered.
SITUATION DESCRIPTION:In case no recurring transactions were made in the original batch but inserted via tfgld1107m000the posting of the recurring transactions went wrong.
SOLUTION DESCRIPTION:This solution solves defect number 15784It is not possible anymore to create recurring transactions for batch in which the recurring transactions are not made.
SITUATION DESCRIPTION:There are a number of sessions where zoom sessions will depend on the value of a variable. In all such sessions a #pragma used session statement must be used for every possible value of the variable.
SOLUTION DESCRIPTION:This solution solves defect number 14015. Now all the sessions where zooms are based on variables have the #pragmastatement.
SITUATION DESCRIPTION:When finalizing a batch on a Windows NT the finalization reports are printed but there appears a bshell message on the screen'No retry point specified for prcess .....'.
SOLUTION DESCRIPTION:This solution solves defect number .14553The retry point is now specified in session tfgld1213s000.
SITUATION IDENTIFIED IN:tfcmg2106s000 "Assign Unallocated/Advance Receipts to Invoices"
SITUATION DESCRIPTION:Linking could be done to blocked invoices
SOLUTION DESCRIPTION:This solution solves defect number 13779.Now a message ("Invoice is blocked") comes up when trying to link a blocked invoice to an unallocated/advance receipt
SITUATION DESCRIPTION:When entering a credit amount in tfcmg2120s000 with a tax code defined as 'nett' in tcmcs0136m000 (Maintain tax codes bycountry),the system generated a default negative vat amount where it should come up with a positive amount.
SOLUTION DESCRIPTION:This solution solves defect number 16278.The system comes up with the correct default value for tax
It was not possible to remove a fully disposed fixed asset. Due to that, the reports were full of disposed fixed assets.
SOLUTION DESCRIPTION:This solution solves defect number 14589. Session tffas3300m000 (Archive disposed fixed asstes) is created. Now a fixedasset can be archived when it is fully disposed and the year of disposal is smaller than the current year. The session isadded to the menu tffas2002m000.
SITUATION DESCRIPTION:After having deleted Received Invoices which are copied or cancelled, the belonging Authorization data is still present intfacp1104m000.
SOLUTION DESCRIPTION:This solution solves defect number 16301.When deleting Received Invoices which are copied or cancelled, the belonging Authorization data is deleted too.The correction program tfcor0322 is provided to cleanup invalid data from the table tfacp102
SITUATION IDENTIFIED IN: Selection for Automatic Reconciliation (tfcmg2123s000)
SITUATION DESCRIPTION:In session tfcmg2123s000 ("Selection for Automatic Reconciliation") the total amount is not being actualized , when paymentsare selected or rejected. Actually there are two problems:
1 If you are in session tfcmg2123s000 and you change the field "sel." ,which selects lines for payment, from yes to or no toyes the total amount is not updated until you are on the choice field and you save the changes. If you are selectingpayments from a list it would be handy if you know until which amount the payments are selected without continously havingto change to the choice field.
2. If you have a list of invoices and you deselect them all by changing the field "Sel." to No and then press save the totalamount is not updated.
SOLUTION DESCRIPTION:This solution solves defect number 16420. Both problems are solved now. The field 'total amount' is directly updated when theselecting of a line is changed. Also, when all lines are set to 'no', the field 'total amount' is updated.
SITUATION IDENTIFIED IN:tfcmg2105s000 Assign Unallocated / advanced receipts to invoices
SITUATION DESCRIPTION:When you use a customer parent/child structure in the system. And an advanced receipt is booked on the parent customerand you zoom to session tfcmg2105 to assign the advanced receipt to an invoice and the assignment is done on thechildcustomer. Everything goes O.K., but when you go back to session tfcmg2105s000 and now assign an invoice of theparent to the advanced receipt. The assignment of the childcustomer will be lost.
SOLUTION DESCRIPTION:This solution solves defect number . 16288When an invoice of a childcustomer is linked to an advanced receipt of the parentcustomer, this invoice will be shown whenstarting session tfcmg2105s000.
SITUATION DESCRIPTION:Invoice amount in Home Currency was printed as 0,00 in case the fully paid sales- or purchase invoice was alreadyremoved.
SOLUTION DESCRIPTION:This solution solves defect number 16381.When the sales- or purchase invoice is already removed the invoice amount in Home Currency will be taken from thefinalized transaction.
SITUATION DESCRIPTION: Brought forward amount was correct; create manual invoice with two lines; display D (20 lines) brought forward amount
includes amount of second line.
SOLUTION DESCRIPTION:This solution solves defect number 16455. The problem was due to the fact that the carry forward amount was not beingcomputed the end of each layout. Instead, the brought forward amount was being computed before the layout. Thecomputation was done after each layout and hence the defect was solved.
SITUATION DESCRIPTION:The total number of detail lines that were printed should be 10 but was 3.
SOLUTION DESCRIPTION:This solution solves defect number 15489.Modifications have been made to the report in order to invoke it to always fill the detail lines up with x's, to a total of 10detail lines.
SITUATION IDENTIFIED IN:tfgld1211s000 Audit and Terminate Batchestfgld0130m000 Maintain Schedule for Automatic Transactions
SITUATION DESCRIPTION:In tf3.1_b is was not possible to enter a schedule for a ledger account with blocking status "Blocked for Manual Input"In B40_b and B40_c it was not possible to finalize batches with lines automatically created by a scheme entered intfgld0130m000 containing ledger accounts with blocking status "Blocked for manual input"
SOLUTION DESCRIPTION:This solution solves defect number 16433 .Changes made to make it possible to enter ledger accounts with blocking status "Blocked for Manual Input" in tfgld0130m000and finalize the created transactions.
SITUATION IDENTIFIED IN: Maintain Bank Transactions (tfcmg2100s000)
Maintain Journal Vouchers (tfgld1103s000)SITUATION DESCRIPTION:It is possible to have same document number twice during bank transactions resulting in error 100 dupl. value.Thishappens only when batch number is the same.
SOLUTION DESCRIPTION:This solution solves defect number 16094. A new check has been built on the presence of a document in the documentstable.
SITUATION IDENTIFIED IN: Transfer Payments (tfcmg1260s000)
SITUATION DESCRIPTION:When printing report tfcmg126032000 (Checks German Layout), the system generates the message 'Bad Skip Value' when 12lines have been printed.
SOLUTION DESCRIPTION:This solution solves defect number 16596.
The skip was done with a negative number (-1). It now always is zero or more.
SITUATION IDENTIFIED IN:tfacr2420m000 ("Print Aging Analysis by Customer")
SITUATION DESCRIPTION:The reports 'Aging Analysis sorted by Customer' , 'Aging Analysis sorted by Financial Group' and 'Aging Analysis Totalsby Customers' are not sorted correct.
SOLUTION DESCRIPTION:This solution solves defect number 16435.Now the reports 'Aging Analysis sorted by Customer' , 'Aging Analysis sorted by Financial Group' and 'Aging AnalysisTotals by Customers' are sorted correct again.
SITUATION IDENTIFIED IN: Transfer Payments (tfcmg1260s000)
SITUATION DESCRIPTION:Detail Line 21 for Report tfcmg1260e1000 ("BTL91"), missed one space.
SOLUTION DESCRIPTION:This solution solves defect number 16562.Modified the layout for the report so the correct detail line length is printed.Also, batch number in file has leading zeroes now.
SITUATION DESCRIPTION:The report of the session tfacr3440m000 ("Print Customer Statements") shows an amount received which shouldn't be printedbecause the document date of the receipt document does not fall in the period as filled in on the form.
SOLUTION DESCRIPTION:This solution solves defect number 16640. Now the correct received amount is printed on the report.
SITUATION DESCRIPTION: When a new user tries to add a transaction type to an existing batch ( created by other user ) , the system is creating a new batch . The newly added transaction type is appearing in the batch created.
SOLUTION DESCRIPTION:This solution solves defect number 16656. Now different users can add an other transaction types in the existing batches provided the parameter is set to " All users ".
SITUATION IDENTIFIED IN:tfcmg2100s000 Maintain Bank Transactions
SITUATION DESCRIPTION:When the status of a supplier is 'Purchase Entry Blocked' , it must still be possible to process payment for this supplier.
SOLUTION DESCRIPTION:This solution solves defect number . 16719It is now possible to process payment for a supplier which has status 'Purchase Entry Blocked'
SITUATION DESCRIPTION:'Container' wasn't filled always in Financial integration transactions (tfgld410).
SOLUTION DESCRIPTION:'Container' (cntr) and Inbound position' (inpo) are now stored in Financial integration transactions (tfgld410).Modifications in software components have been marked with DF16188-2.
SITUATION IDENTIFIED IN:tfgld1211s000 ("Audit and Terminate Batches")
SITUATION DESCRIPTION:Problem with intergroup transactions with integration indicator project costs:
Reproduction:1. Enter ledger account for intergroup transaction (as defined in tfgld2101m000), transaction type doesn't matter.2. System will come up with session tfgld2102s000 where you can enter ledger account for intergroup company.3. System will zoom to tpppc2111m000 where you can enter project, article, etc.4. Finish transaction and finalize batch.5. Switch to intergroup company and create intergroup transactions with tfgld2201m000.6. If you try to finalize the batch message will come up "amount project not split up completely".
SOLUTION DESCRIPTION:This solution solves defect number 16522. Now, the intergroup transactions with integration indicator project costs can befinalized without the message "amount project not split up completely".
SITUATION IDENTIFIED IN: Change Interrupted Batch Status (" tfgld1116m000 ")
SITUATION DESCRIPTION:When the transaction type status is " in use background ", the session tfgld1116m000 is not updating the table tfgld018 to "free " .
SOLUTION DESCRIPTION:This solution solves defect number 16990. Now the table tfgld018 is updated.
SITUATION IDENTIFIED IN: Maintain Chart of Accounts (tfgld0108m000)
SITUATION DESCRIPTION:If the field Currency Analysis(tfgld008.icur) is set to "not required" the sytem should update on history tables only in Homecurrency.But it was updating the history tables in transaction currency and home currency. This should be done only if theoption is "required".
SOLUTION DESCRIPTION: This solution solves defect 15799.The option Currency Analysis "not required" is implemented now.It will not be allowed to change the parameter currency analysis in tfgld0108m000 "Maintain chart of accounts" if the L/A isfound in the history tables.
SITUATION DESCRIPTION:1 :process 4 - Fatal Error : zero pointer: name '' in qss.search2: process 4 - Fatal Error : can not continue in tffst1205m0003: process 4 - Fatal Error : use of NULL pointer on ''4: process 4 - Fatal Error : Can not continue in tffst1205m000
SOLUTION DESCRIPTION:This solution solves the defect number 16632. There was a programming error.
SITUATION IDENTIFIED IN: Select Invoices for Trade Notes (tfcmg4230m000)
SITUATION DESCRIPTION: In the session Select Invoices for Trade Notes, after selecting the invoice, while inserting the data into the table tfcmg401, the filed tfcmg401.pcun was not getting filled.So fatal error was coming while using the session.
SOLUTION DESCRIPTION:This solution solves defect 16846.The field tfcmg401.pcun is assigned the value of Parent Customer if the Customer has got a Parent Customer.Else the fieldis assigned the Customer Code itself.
SITUATION DESCRIPTION:It is not possible to enter the same supplier's invoice no twice in session tfacp1110s000 ("Maintain Purchase Invoices"').The system gives the message "Invoice number already exists in open items file".It is correct that the warning is given, but it should be possible to continue, because a lot of suppliers reset their invoicenumbers (for example every year).
SOLUTION DESCRIPTION:This solution solves defect 16854. Now it is possible to enter the same supplier's invoice number twice. Only a warning isgiven.
SITUATION DESCRIPTION:If you create in tfcmg1120m000 "Maintain Payment Advice" a Type of Advice : Advance Payment, that includes Taxes (addedin the second form) regardless of the steps of payment the VAT line is never generated .
SOLUTION DESCRIPTION:This solution solves defect number 15928.Functionality now implemented.
When column references of type "Other Column" are used, and they are referring to a higher column number than they are,then these values aren't selected.
SOLUTION DESCRIPTION:This solution solves defect number 16565. This solution repairs the priority scheme of the column references enabling thecorrect values now to be selected. The problem originated in a Bad Fix on ID 10226127.
SITUATION IDENTIFIED IN : Process Delivered Sales Orders (tdsls4223m000).
SITUATION DESCRIPTION :If invoice date + payment period results in month 01 and day 30 or 31 AND day greater than payment day 1, 2 and 3 ANDpayment day 1 = 29 or 30, then a wrong due date can be/is calculated (i.e. : 29/30 february).
SOLUTION DESCRIPTION :The due date will now be calculated correctly in each situation.The modification has been marked with : DF 2495-1.
SITUATION DESCRIPTION:The remainder costs are not calculated when the field "Update letter numbers for due invoices " is set to "No" for the firsttime . Also in tf3.1_b Version Interest amount were not displayed ( only zero amount displayed ) for Invoices wherereceipt schedule were not maintained . This was due to the fix for the defect DF 11110
SOLUTION DESCRIPTION:Now the interest and remainder costs are calculated properly. This solution solves defect 16490 .
tfgld4122s000 Maintain Integration Relations by Rangestfgld4123s000 Maintain Integration Relations by Elementstfgld4124s000 Maintain Integration Relations by Rangestfgld4125s000 Maintain Integration Relations by Elements
SITUATION DESCRIPTION:Errormessage 'Overlapping Ranges not allowed' is given when Ranges are not overlapping.
SOLUTION DESCRIPTION:This solution solves defect number 16561.Errormessage 'Overlapping Ranges not Allowed' is now only given when both given ranges are overlapping.Also made it possible to use integration options with domain type Multi Byte.
SITUATION IDENTIFIED IN: Link Advance Receipts to Proforma Invoice (tfcmg6210s000)
SITUATION DESCRIPTION:Wrong amount gets displayed in the field 'Balance to be linked' when a negative advance receipt is linked to the proformainvoice.
SOLUTION DESCRIPTION:This solution solves defect number 16022. The problem has been fixed and now the correct amount is displayed in the field.
SITUATION IDENTIFIED IN:tfgld4121m000 Maintain Options by Integration Element
SITUATION DESCRIPTION:When you specify two lines in session Maintain Options by Integration Element (tfgld4121m000) with both one integrationoption and specify the range for the last line. After that you must leave the session. Go in session tfgld4121m000 again andfill the second integration option for the first line. Try to save the record . You get the errormessage 'Invalid Dimension Xfor Dimension code X'
SOLUTION DESCRIPTION:This solution solves defect number 16951.The error mentioned in the situation description has been solved.
SITUATION DESCRIPTION:When text was added on the record via the Text Manager there was no indicator if text was added or not.SOLUTION DESCRIPTION:Indicator Text: YES/NO is added on the second form of both sessions.This solution solves defect number 16519-1.
SITUATION IDENTIFIED IN: Post Sales Invoices.(tfacr4220m000)
SITUATION DESCRIPTION: When the time frames of Fiscal and Tax periods differs,this session gives an error message. For eg,if the fiscal year ends on 31/03/98 and the Tax year ends on 01/03/1998, and if the transaction entry date field is filled withany date after 01/03/1998 , then the session gives an error message.
SOLUTION DESCRIPTION: This solution solves defect number DF16970 .Now the error message is not displayed.
SITUATION DESCRIPTION:The Display Check Master session does not display all the invoices associated with a manual check. After linking multiplepuchase invoices with a manually cut check (for example, check 203) in the maintain anticipated payments session, we viewthe transaction in Check Master. However, drilling down on check 203, we can only see one purchase invoice linked withit.
SOLUTION DESCRIPTION:This solution solves defect number 16842. The defect was due to the fact that the zoom session Display Anticipated Payments( Details ) [ tfcmg2507s000 ], was selecting only those records which has the series for composition field having the valuesame as that of the first record. Where as it should have taken all the records belonging the the given cheque.
SITUATION DESCRIPTION:When entering data in session tfgld1115s000, the Ledger Account description is not displayed.
SOLUTION DESCRIPTION:This solution solves defect number 16735.Now the description is displayed when entering a Ledger Account in session tfgld1115s000.
SITUATION IDENTIFIED IN:otfcor0261 Recalculate Open Entries (tfacr200)
SITUATION DESCRIPTION:When a sales invoice was partially paid and the receipt was completely reconciled there was still an anticipated balance.This was the case in a payment method with steps Yes, No, No which is already prohibited.
SOLUTION DESCRIPTION:This solution solves defect number DF 16971-1.Anticipated balance is calculated now on base of the anticipated documents which aren't reconciled complete or partially.
SITUATION DESCRIPTION:It is possible to enter 2 records with the same Sequence Number. The data gets corrupted. From the previous sequencenumber the Cost catagory is overwritten on the screen. Once the new record is deleted the old record comes back.
SOLUTION DESCRIPTION:This solution solves defect number 2432.
SITUATION DESCRIPTION:CTRL-X option in tfacp2529s000 doesn't work.
SOLUTION DESCRIPTION:This solution solves defect number 16552. CTRL-X Option has been removed and is no longer available. Also the HelpMessage displayed in the forms have been changed.
VRC package component comp_type comp_codeB40 c4 tf tfacp2529s000 Form acp2529s0001
SITUATION IDENTIFIED IN: Maintain Variable Depreciation Data (tffas0108m000)
SITUATION DESCRIPTION:When we have a fixed asset displayed on the screen and we try to create a new group, it is not possible to fill fixed assetgroup.
SOLUTION DESCRIPTION:This solution solves defect number 17070.The check for the Fixed Assest Group is removed.Now when we have a fixed asset displayed on the screen, it is possible toenter the Fixed Asset Group in a new group.
SITUATION IDENTIFIED IN:tfacr2433m000 ("Print Customer's Total Balance")
SITUATION DESCRIPTION:When in session tfacr2433m000 ("Print Customer's Total Balance") report tfacr243313000 ("Total Balance by Parent/Child") ischosen, for every child a parent is printed. This is not correct: all childs should be grouped under the parent.
SOLUTION DESCRIPTION:This solution solves defect number 16747-1. Now, all childs are grouped under the parent in report tfacr243313000 ("TotalBalance by Parent/Child").
SITUATION DESCRIPTION:When the revaluation amount is reset to zero only the revaluation depreciation costs are also reset to zero. The revaluation depreciation is not but should be reset to zero.
SOLUTION DESCRIPTION:This solution solves defect number 16815.When the revaluation amount is reset to zero the revaluation depreciation amounts and revaluation depreciation costs are nowboth reset to zero.
SITUATION DESCRIPTION:When a credit note is linked to a sales invoice, session tfacr3440m000 ("Print Customer Statements") the amount of thecredit note is included in both the invoice amount and the amount received. This is not correct, only the invoice amount should be adjusted.
SOLUTION DESCRIPTION:This solution solves defect number 17115. Now, only the sales invoice amount is adjusted with the credit note amount.
SITUATION DESCRIPTION:The spaces between references in tfcmg103 are not accumulated in the total count to measure the number of invoices tocompose for option characters in tfcmg0140m000 "Maintain Payment Methods"
SOLUTION DESCRIPTION:This solution solves defect number 17087.
SITUATION DESCRIPTION:While using the sessions Maintain Payment Advice(tfcmg1120m000) and Maintain Direct Debit Advice(tfcmg4120m000) ,without inserting data in the first form, when the user goes to the second form, fatal error was coming.
SOLUTION DESCRIPTION:This solution solves defect 17192.While the user goes to the second form without inserting data in the first form, the company number is having a value 0and a selection was done based on this company number because of which the fatal error was coming.Now the selection isno more done, if the company number is 0.
SITUATION DESCRIPTION:The combination variable depreciation and start of depreciation other then date in use or period in use made thefixed asset year longer or smaller the the defined periods of the year.
SOLUTION DESCRIPTION:This solution solves defect number 16567 . The first period of the fixed asset in case of depreciation calculation is
SITUATION DESCRIPTION:When normal receipts or advanced receipts or unallocated receipts are linked to a particular Sales Invoice and if they are ofdifferent currencies(with respect to the Sales Invoice ),then the open amount calculated is wrong. It is different from theopen amount calculated in session tfacr3130m0000(Maintain reminder Diary).
SOLUTION DESCRIPTION:This solution solves defect number DF17245. Now the open amounts are calculated correctly when normal receipts or advancedreceipts or unallocated receipts are linked to a particular Sales Invoice and if they are of different currencies(with respect tothe Sales Invoice)
SITUATION DESCRIPTION:In the session tfacp1132s000, Company description was wrongly displayed.
SOLUTION DESCRIPTION:
This solution solves the defect 17290.The company description field was previously tccom010.nama.Now this is changed to tccom000.nama.
VRC package component comp_type comp_codeB40 c4 tf tfacp1132s000 Form acp1132s0001
Solution : 14098
VERSION: 3.1_b, B40_b, B40_c
SITUATION IDENTIFIED IN: Write off Payment Differences(tfacr2240m000)
SITUATION DESCRIPTION: (1) Amount Paid is wrongly printed in the report. (2). Also the default value of the form field "from period" is changed to thecurrent period when entering into that field. (3) Moreover the report totals are not aligned straightly in the report.Note: Situation(1) is present only in B40_c,.Situation(3) is not present in tf3.1_b7 and tf B40l_b5_mcr0
SOLUTION DESCRIPTION:This solution solves defect number 17239. Now the Amount paid and the Payment difference are printed correctly.Also thedefault value of the form field "from period" remains zero while entering the field.Moreover the Report totals in the reporthas been aligned correctly now.:
SITUATION DESCRIPTION:While running the session Print Journal Report, the columns for Debit and Credit, in the case of Belgium, were appearing aszero.
SOLUTION DESCRIPTION:This solution solves defect number 17252. The problem occurred because the amount was not being selected, whileprinting. The amount was selected and hence the defect was solved.
SITUATION IDENTIFIED IN:tfcmg1220m000 "Select Sales Invoices for Payment"
SITUATION DESCRIPTION:Selecting purchase invoices with the option settle sales invoices on yes does not work correctly.Only when the entered range is totally open, sales invoices are selected as well.
SOLUTION DESCRIPTION:This solution solves defect number 16989.
SITUATION IDENTIFIED IN: Display Dimension Distribution By Company (tfgld3528s000)
SITUATION DESCRIPTION:When zooming from Display dimension history (tfgld3520m000) to Display Dimension Distribution By Company(tfgld3528s000), after setting the field <Display for Company> to "All Companies" in session Change Display HistoryDefaults (tfgld3503s000), the wrong amounts are displayed: The total of the <Actual Amounts> in tfgld3528s000 does notcorrespond the <Actual amounts> in tfgld3520m000.
SOLUTION DESCRIPTION:This solution solves defect number 17318. In the situation as specified above, the total amounts in tfgld3528s000 and tfgld3520m000 will correspond to each other.
SITUATION DESCRIPTION:The user cannot see if the session is still running or not, because only the word 'busy.....' is displayed.
SOLUTION DESCRIPTION:This solution solves defect number .17107-1On the forms of sessions tffbs1202m000 and tffbs1204m000 is now displayed what the session is doing.
SITUATION DESCRIPTION:Wrong dates were filled in clieop file. The creation date was filled with the date entered on the form of sessiontfcmg1260s000.The cash date on the '0030' line was filled with the last planned cash date filled in tfcmg1120m000 "Maintain PaymentAdvice".
SOLUTION DESCRIPTION:This solution solves defect number 17396.The creation date in the '0001' line is now always filled with the system date. The date of the '0030' line is now filled withthe date filled on the form of session tfcmg1260s000 "Transfer Payments".
SITUATION DESCRIPTION:When a purchase invoice with an amount of zero is matched with a project order with a negative quantity and amount, andthen the invoice is approved, the reversal commitment in Project is not made.
SOLUTION DESCRIPTION:This solution solves defect number 16892. Now the reversal commitment (marked with an asterix) is made in tpppc2110m000("Maintain Commitments (Material)") in case the order quantity and amount are negative and the invoice amount is zero.
SITUATION DESCRIPTION:The possibility to redefine the ledger accounts and dimensions defined in the statement accounts was not properly executed.When the redefine for ledger accounts was set on YES for blank to ZZZZZZ all ledger accounts were selected instead of theledger accounts defined in the statement accounts.
SOLUTION DESCRIPTION:This solution solves defect number DF 15384-1.Function fst0005 modified to make the output of the redefine according to the selection given.
SITUATION IDENTIFIED IN:Background process real-time tfgld1201s000
SITUATION DESCRIPTION:Bad performance caused by defect 14553 in background processes.
SOLUTION DESCRIPTION:This solution solves defect number 17453. Some adjustments of defect 14553 are undone in order to improve theperformance of the background processing sessions.
SITUATION DESCRIPTION:In session tfacr3440m000 open amounts with a value of zero are also shown.
SOLUTION DESCRIPTION:This solution solves defect number 17373. The problem was solved taking care in the print condition that if the Amount Openis zero, the invoice is not printed.
SITUATION DESCRIPTION:Lines in session tfcmg1246s000 "Compose Payments Manually" were doubled after using cursor keys to view the next halfscreen.
SOLUTION DESCRIPTION:This solution solves defect number 15801.Because the lines of the payment advice could not be identified uniquely, the system generated lines twice when using thearrow-keys.This has now been rectified by using a unique field to identify every record visible on the form.
SITUATION IDENTIFIED IN: Maintain Posting Data ( " tfcmg1258s000 ")
SITUATION DESCRIPTION: The user was not able to access the " period " fields for the first time. But he was able to access them the next time andalso when he was using the mouse ( in BW).
SOLUTION DESCRIPTION:This solution solves defect number 17505. Now the user can access the period fields all the time.That is even for the firsttime, the user can access the period fields.
SITUATION IDENTIFIED IN: Reconciliation of Receipts/Payments ( tfcmg2103s000 )
SITUATION DESCRIPTION:Even though the Reconciliation is ' Complete ' , the system allows the user to change the 'Reconciliation Amount'.
SOLUTION DESCRIPTION:This solution solves defect number 17214 . Now the system does not allow the user to change the ' Reconciliation Amount ' ifthe Reconciliation status is ' Complete ' .Also Backported ID 10242953 to B40_b. This ID creates a reconciliation button in tfcmg2102s000 and ends tfcmg2103s000immediately after processing.
SITUATION DESCRIPTION:Create a new batch in tfgld1101m000. Use transaction type of Purchase invoice. Mark the particular record to insert data.After inserting data in the first form of tfacp1110s000, go to the second form, press "undo" button. Now come back to thefirst form and press the "first record" button. Then the first record of the particular transaction type was displayed. Actuallynothing should be displayed as there are no records in the current batch.
SOLUTION DESCRIPTION:This solution solves defect 17503.When the user presses the first record button, the records were selected based on the transaction type alone. No limits wereplaced on the "document line number". Now this is done, so that documents belonging to the current batch number will only beselected. If there is already a record in the current batch, then that particular record will be displayed.
SITUATION DESCRIPTION:When the fas set-up was activated during the year the depreciation calculation for the last periodgave is some cases wrong results.
SOLUTION DESCRIPTION:This solution solves defect number 17035.When the set up is activated during the year the calculation in the last period is nowcorretly calculated.
SITUATION DESCRIPTION:When trying to match an ebs-record for an anticipated receipt the system creates a matched record for an anticipatedpayment.
SOLUTION DESCRIPTION:This solution solves defect number 16116.The problem was that the system never could match to an anticipated receipt because it was considered by the program
always to be a payment.This is modified now. Both payments and receipts are taken into account for this situation now.
SITUATION DESCRIPTION:This situation only occurs in the german version.Under form-option Special (BW) or Application (GUI) the option "Display Fully Paid Invoices" refered to the InvoiceDetails and visa versa. In version 3.1_b the text under the choice option in form acp2522s000 and acr2522s000 displayes the <Ctrl>[A] option twicefor different choices.
SOLUTION DESCRIPTION:This solution solves defect number 17569.The special options on the forms <Display sales- and purchase orders> (tfacr2522s000 and tfacp2522s000) are corrected.The link between label description and session are clear and correct now. The choice option <Ctrl>[A] is is to display"Fully paid Invoices" and Ctrl>[E] is for "Display Invoice Details".
VRC package component comp_type comp_codeB40 c4 tf tfacp2522s000 Form acp2522s0001
SITUATION DESCRIPTION:In session tfacp2421m000 ("Print Purchase Invoices"), invoices are printed with a balance when the option 'Print Fully PaidInvoices' is set to 'yes', while those invoices are not printed with the option 'Print Fully Paid Invoices' set to 'no'. This is notcorrect.
SOLUTION DESCRIPTION:This solution solves defect 17263-1.Now, the option 'Print Fully Paid Invoices' checks the balance which is printed on the report. In the old situation the optionchecked the balance of the invoice in the open entries table (field tfacp200.balc - tfacp200.bala).Defect 13662-1 is reversed.
SITUATION IDENTIFIED IN: Process Periodical Depreciation Calculation ( tffas2200m000 )
SITUATION DESCRIPTION:It was not possible to use job option in the session Process Periodical Depreciation Calculation ( tffas2200m000 )
SOLUTION DESCRIPTION:This solution solves defect number 17551. Now the form option make job has been enabled and the customer can use the joboption in the session Process Periodical Depreciation Calculation ( tffas2200m000 ).
VRC package component comp_type comp_codeB40 c4 tf tffas2200m000 Form fas2200m0001
SITUATION DESCRIPTION:Error 100 (Duplicate value) on Tax Analysis(tfgld110). Records in the Interim tax table(tfgld107) aren't deleted.Missing records in Tax Analysis table(tfgld110) or Tax Analysis <> Finalized transactions
SOLUTION DESCRIPTION:This solution solves defect number(s): 16932 and 16869.- The records from the interim tax table will be deleted after finalisation with the exception of records which are using taxon payments. - The records in the tax analysis table are stored with the original transaction type & document now. This only affects multi-finance environments. To correct the old records in the tax analysis table, correction program otfcor0612 can be used. If the correction program otfcor0603 hasn't run on your system, then this has to be executed first (not for B40 C).- Besides updating Tax Analysis records (see former point), the correction program otfcor0612 also creates missing records. Also for this point run the correction otfcor0603 first if you have an multi finance environment and you haven't executed it before (Not for B40 C).
SITUATION IDENTIFIED IN: Assign Banks To Payments (tfcmg1251s000)
SITUATION DESCRIPTION:After executing session "Compose Payment (tfcmg1240m000)" , some payments are assigned to the bank which priority isset as zero.
SOLUTION DESCRIPTION:This solution solves defect number 17406. Now, when user defined priorities are considered for assigning Banks to payments(ie after the stage where the Banks could not be assigned using the programmed priorities), Banks whose priority is set aszero are not selected.
SITUATION DESCRIPTION:When in the integration setup a ledger account with a mandatory dimension is defined for purchase/receipt, problems arise onapproval of the purchase invoice in case the ledger account and dimensions are not yet filled in the integration tables (e.g.on Windows NT systems). When the purchase invoice is approved, the purchase/receipt posting is reversed, including thedimensions. But in case the ledger account and dimensions are not present yet in the integration tables, no dimension is filledin the approval booking. The result is that the batch cannot be finalized.
SOLUTION DESCRIPTION:This solution solves defect number 17135. Now, the dimensions are filled in correctly in the approval booking, also when theintegration bookings are not yet posted to Finance.
SITUATION IDENTIFIED IN: Post FAS transaction to general ledger (tffas1201m000)
SITUATION DESCRIPTION:Bookvalue transactions were not made during posting, when the disposal was done with an intercompany booking.
SOLUTION DESCRIPTION:This solution solves defect number 17531.Bookvalue transactions will also be posted for every disposal done in a different company.
SITUATION IDENTIFIED IN:tfacp2137s000 Change Date / Period Range
SITUATION DESCRIPTION:When a certain year and period was filled in the related 'to Date' field was not calculated properly. As a result of that theopen items were not correctly selected.
SOLUTION DESCRIPTION:This solution solves defect number DF 17564.Program script changed so that in any case the open items are selected upon the period selected.
SITUATION IDENTIFIED IN:Maintain Simple Integration Relations by Range (tfgld4122s000)Maintain Simple Integration Relations by Element (tfgld4123s000)Maintain Integration Relations by Range (tfgld4124s000)Maintain Composed Integration Relations by Element (tfgld4125s000)
SITUATION DESCRIPTION:When an Integration relation is entered in session tfgld4124s000 and the record is saved, after that you try to changed thedimension code used, you get the error 'Overlapping ranges not allowed'.
SOLUTION DESCRIPTION:This solution solves defect number 2700.All above mentioned session are totally rewritten. The userinterface is changed from ASCII to GUI.Most of the forms are changed a little, but no functionality has been removed.
SITUATION DESCRIPTION:The wrong Ledger Account is used when you have set the field 'Ledger Account by Currency' in the session MaintainCompany Parameters (tfgld0103m000) to 'Yes'.
If you Calculate Currency Difference for several currencies, only the Ledger Account for the last currency is determinedcorrectly.The other previous currencies use the wrong ledger account, by using the ledger account for the currency whichfollows immediately after each one.
For example:Calculate Currency Difference for currencis : ECU, USD, DEMIn the session Maintain Ledger Account by Currency (tfgld0119m000) you must specify which Ledger Accounts are to beused when posting the currency profits or losses.In this example, there are currency profits for all currencies. In session tfgld0119m000 is the following specified:
Currency Ledger AccountECU Profit ECUUSD Profit USDDEM Profit DEM
When you now go to Calculated Currency Differences the following will happen :Currency profits for ECU will be posted to Ledger Account 'Profit USD'Currecny profits for USD will be posted to Ledger Account 'Profit DEM'
but Currency profits for DEM will be posted to Ledger Account 'Profit DEM' (- the correct account)
SOLUTION DESCRIPTION:This solution solves defect number DF 17303-1The situation as described in the Situation Description will not appear any more. The right Ledger Account will be takenwhen Calculating Currency Differences.
SITUATION DESCRIPTION:It is not possible anymore to create a payment/receipt method with steps: - doc received : yes and doc acc/sent : no for payments - doc sent to cust : yes and doc acc by cust : no and doc sent to bank : no for receipts.
SOLUTION DESCRIPTION:This solution solves defect number 17257.All variations of payment steps are possible again.
SITUATION DESCRIPTION:When selecting the records which must be Purged the field tfgld410.trdt (Log Date) is used.When selecting the records which must be deleted after Purging the field tfgld410.crdt (Transaction Date) is used.This should be the field tfgld410.crdt (Transaction Date) in both cases
SOLUTION DESCRIPTION:This solution solves defect number 17586-1.The field tfgld410.crdt (transaction Date) is now used for selecting the records which must be Purged as well as for therecords which must be deleted after Purging.Also the Label on the form has been changed from Transaction Date to Creation Date.
SITUATION IDENTIFIED IN: Print Supplier's Total Balance (tfacp2433m000)
SITUATION DESCRIPTION:In session "Print Supplier's Total Balance" (tfacp2433m000), if the following fields are filled as follows, Total After Group : NoPrint Supplier/Factor Comp. Relatio : Yesthen, the report shows only ZERO balance.
SOLUTION DESCRIPTION:This solution solves defect number 17690. Now the Invoice Balances are printed correctly if the field Total after group isgiven "No" and.the field Print Supplier/Factor Comp. Relation is given " Yes"
SITUATION IDENTIFIED IN: Restart Finalization Run (otfcor0203)
SITUATION DESCRIPTION:The correction program doesn't process the records remaining in the interimtables (from gld207 untill gld212) after afinalizationrun was interrupted.
SOLUTION DESCRIPTION:This solution solves defect number 17243.Functionality to process the records in the interimtables moved to a new correctionprogram otfcor0204.The otfcor0203 is now only processing remaining records in gld102.
SITUATION IDENTIFIED IN: Print Receivable Invoices Specifications Net Change (tfacp1435m000)
SITUATION DESCRIPTION:Raise a purchase order from distribution. Link it to an invoice.Match and approve the invoice completely and then do aprint using the session tfacp1435m000.Since the entire quantity is approved, the amount displayed should be zero.Insteadit was printing negative amount.
SOLUTION DESCRIPTION:This solution solves defect 17622.The quantity passed on to the function calculating the "net amount" was wrong.So negative amount was printing. Now thecalculation is done correctly.
SITUATION DESCRIPTION:1.The session Maintain Journal Vouchers (multiple lines) was using the script tfgld1103(Maintain Journal Vouchers). Due to the functional differences between single line and multiple line journals, it was decided to have a seperatescript for Maintain Journal Vouchers(multiple lines)2. The dimension description was not being displayed in Maintain Journal Vouchers (Multiple lines)3. The ledger account description default was coming as all "**********" in both tfgld1115s000 and tfgld1103s000 (Maintain Journal Vouchers).4. The dimension description (in tfgld1103s000) was not blanked when a record is shown without dimensions being used after a record is shown with dimensions being used. SOLUTION DESCRIPTION:This solution solves defect number 17051. 1. A new script tfgld1115 has been created using tfgld1103 and linked to the session Maintain Jounal Vouchers (MultipleLines) (tfgld1115s000). 2. A form field 'Dimension Descr.' is added in the form Maintain Journal Vouchers (Multiple Lines) tfgld1115s0001 to display the dimension descriptions.3. Now the default ledger account description is made blank in both Maintain Journal Vouchers (tfgld1103s000) andMaintain Journal Vouchers (Multiple Lines)(tfgld1115s000) 4. Now the dimension description is blanked if dimensions are not used in the record.
SITUATION DESCRIPTION:When printing the Yearly Tax Report for two customers with the same taxnumber only one is printed. Although the totalamount is the tax amount of the two customers accumulated.
SOLUTION DESCRIPTION:This solution solves defect number 17703.Now the report will print the customers or supplier with the same tax number separately.Also the total per tax number will be printed on the report.
SITUATION DESCRIPTION:When trying to post sales invoices via session tfacr4220m000. The error message 'Invalid period for all modules' came up.Also the message 'Period Status not defined for Company' sometimes appeared.
SOLUTION DESCRIPTION:This solution solves defect number .17774-1The error message appeared most of the time when a broken year was used in the company. The error as described above iscorrected.
SITUATION IDENTIFIED IN:Select Invoices for Direct Debits (tfcmg4220m000)
SITUATION DESCRIPTION:
Selecting purchase credit notes for direct debits is not possible.When the system was reviewing whether a document should be selected or not, it did not take into account that a purchasecredit note is registered as payable.
SOLUTION DESCRIPTION:This solution solves defect number 17823.Creditnotes can be selected too now.
SITUATION DESCRIPTION:1. It should not be possible to match a positive quantity with a negative amount. When matching completely however, it ispossible to match a positive quantity with a negative amount (or vice versa). In ASCII-mode it is also possible to match partially a positive quantity with a negative amount. These situations are notcorrect.2. The minus sign of the field 'invoiced amount' was not displayed when matching completely with a negative order line.
SOLUTION DESCRIPTION:This solution solves defect number 17700. 1. Now, it is not possible anymore to match a positive quantity with a negative amount (or vice versa) in all situations.2. The minus sign of the field 'invoiced amount' is now displayed.
VRC package component comp_type comp_codeB40 c4 tf tfacp1131s000 Form acp1131s0001
SITUATION DESCRIPTION:It is possible to enter tax transaction on an approved invoice. This is causing in correct postings.
SOLUTION DESCRIPTION:This solution solves defect number .16578It is no longer possible to enter Tax Transaction on an approved invoice. If you try it you will get the message 'Invoicealready approved' and the session Maintain Tax Transaction (tfacp1112s000) will end.
Control Amount not inserted in table Transaction Type Batch Status (tfgld101)
If you create a batch with recurring transactions in it and use a transaction type where checksums are used, the createbatches after running session Create Recurring Transactions cannot be Finalized. When you try to finalize these batch youwill get the error message 'Control amounts do not tally'.
SOLUTION DESCRIPTION:This solution solves defect number 17498.When you now create recurring transactions the control amount for the batch will be added in the table Transaction TypeBatch Status (tfgld101).The errormessage 'Control amounts do not tally' will not occur anymore.
SESSION ERROR IDENTIFIED IN: tfacp1460m000 "Update Accounting for PUR Results"
SITUATION DESCRIPTION:When starting tfacp1460m000 (Update Accounting for PUR Results) several times, a fatal error occurred.This happened because the variable 'tot.mat.cost' was not initialized.
SOLUTION DESCRIPTION:Variable 'tot.mat.cost' is initialized now. Modifications have been marked with DF 17378-1.
SITUATION IDENTIFIED IN: Select Invoices for Reminding (tfacr3210m000)
SITUATION DESCRIPTION:Unallocated Receipt documents are not selected for reminding - in case there are more than one unallocated receipt within onedocument and the first unallocated receipt (line number = 1) is assigned to a sales invoice and is balanced, than the rest ofthe unassigned receipts are not selected for reminding.
SOLUTION DESCRIPTION:This solution solves defect number 17516 and 12138. System was skipping the following line number records in the open itemtable and with this fix the problem has been solved.
SITATION DESCRIPTION: When pressing continue before filling in the companynumber, the program is looking for company 000 in line 0551. Resulterror 506 on select.
SOLUTION DESCRIPTION:This solution solves the defect number 17902. The problem was due to the fact that it was reading non existant values from the company table. The problem was solvedby reading company table only when a valid company is entered.
SITUATION DESCRIPTION:When changing the price of an purchase order, the system did not take the modified price into account when running the cashforecast.
SOLUTION DESCRIPTION:This solution solves defect number 17497.The new price for the received order is now taken into account in the cash forecast.This will only be done for the part of the order that is received.
SITUATION DESCRIPTION:When in the parameters for CMG the parameter Adjust Tax for Deductions is set to Yes and Multi Finance is used, thefollowing problem occurs:
I have made a sales invoice in company 814 with VAT. After that I booked a bank receipt in company 813 for this invoice.All the intercompany bookings seem to be correct except the VAT booking on the deduction, this transaction should bebooked in company 814 and is booked in company 813.
SOLUTION DESCRIPTION:This solution solves defect number 16880.If tax on deduction is used in an intercompany environment, the posting of the tax will be made in the company of theoriginal invoice.
SITUATION DESCRIPTION:When copying a letter from one language to another the system ask a question wheter you want to copy the text or not. If youanswer with 'Yes' and have a look in the header and footer text, nothing is in there.
SOLUTION DESCRIPTION:This solution solves defect number 17878.This problem is solved now in the software. The text is now copied from one language to another. This can be useful whenyou want to translate the letter from your mother language to a foreign language.
SITUATION IDENTIFIED IN: Print Aging Analysis by Customer (tfacr2420m000) Print Aging Analysis by Supplier (tfacp2420m000)
SITUATION DESCRIPTION:In the specific situation of having a customer with one invoice, which is paid and one unallocated receipt, the paid invoiceis wrongly shown in aging analysis.
SOLUTION DESCRIPTION:This solution solves defect number 17724. The invoice amount was not being initialised properly, now it is.
SITUATION DESCRIPTION:When the integration parameter Compression is kept as "compression" or "Compression by transaction origin" and if twotransport order cost lines are processed into finance at the same time and each line has a different supplier, then whenposting to finance (in the table "Non-finalized Transactions", tfgld102) the transaction are compressed and the compressed
amount is attributed to the same supplier (the first cost line's supplier). This also happens for other transaction origin,eventhough, not for the same order.
SOLUTION DESCRIPTION:This solution solves defect number 1915 . Now a new functionality is added where by , the supplier\customer fields alsoare taken into consideration before compression in the Non-Finalized Transaction Table (tfgld102). Back Ported ID10243176.
SITUATION IDENTIFIED IN:Assign Unallocated /Advanced Receipt to invoices (tfcmg2105s000)
SITUATION DESCRIPTION:When you create a unallocated of Advanced Receipt in session tfcmg2100s000 on a parent customer, and save it. You canzoom to session tfcmg2105s000. In the session you 'select open item' from the special menu.You will get also the invoices of the child customers linked to the parent.If you now assign a part of the receipt to the parent customer and a part to the child customer and process it, everything isO.K.But when you enter again tfcmg2105s000 and unlink the assignment of the child customer, donot process it, select openitems again, and return to session tfcmg2105s000. The remaining amount on the bottom of the screen is not correct anymore,and the status of the child customer is linked (manual, automatic) again.
SOLUTION DESCRIPTION:This solution solves defect number . 17976-1When you now first link the unallocated / advanced receipt to a parent and a child customer, process it, enter sessiontfcmg2105s000 again, unlink one of the assignment, select opten items, and go back to session tfcmg2105s000. Theremaining amount will be update O.K.
NOTE: the changed you made before zooming to session tfcmg2118s000 (select open items) are not processed.
The problem was due to the fact that in the session tfcmg2118s000,only computation was to be done for the unallocated/advance payment's table. Where as the transaction type was also beingupdated from the sales invoice table. This was not supposed to happen.
SITUATION IDENTIFIED IN: (tfgld1206m000) Close Periods (tfgld0107m000) Maintain Period Status
SITUATION DESCRIPTION:If a period can not be closed, then the user receives only a message that the period for ACP/ACR/CMG/GLD can't be closed.But the warning message should also mention the record (table and the data in the key of the record) which is blocking theclosing of a period.
SOLUTION DESCRIPTION:This solution solves defect number 17546. Display fields have been inserted in the form "Close Periods (tfgld1206m0001)" and " Maintain Period Status (tfgld0107m000)" to display the details of the record blocking the closing of a period.
SITUATION IDENTIFIED IN: Post FAS Transactions to General Ledger ( tffas1201m000)
SITUATION DESCRIPTION:The wrong error description is displayed, if for any ledger account the dimension is out of range. It displays "Dimension1 is out of range for ledger account xxxxxx" , with the wrong accountnumber.
SOLUTION DESCRIPTION:This solution solves defect number 18019. Now the error message is correctly displayed, specifying the ledger account anddimensioncode.
The update of a Sales Credit Note or an Advance Receipt resulted in a mistake in the printing of the Reminder Letter textgiving the wrong numbering to the letter relating to the invoice.
Also, the printout of "Letter numbers" doesn't make any sense in case of "credit notes" or "advance receipts".In case of "advance receipts" and "credit notes" the lines have to be printed out, but without the "Letter number".
SOLUTION DESCRIPTION:This solution solves defect number 17743. The Reminder letter field for documents with the the transaction type creditnotes or advance receipts is not updated anymore.
SITUATION DESCRIPTION:It takes a very long time for session tfgld1406m000 ('Print Finalized Transactions") to print the finalized transactions of 1ledger account.
SOLUTION DESCRIPTION:This solution solves defect number 17906. The performance of the session has been improved. Now depending on what isentered on the form, a different index is chosen to read the data from the database.
SITUATION IDENTIFIED IN: Selection of Open Items (tfcmg2118s000)
SITUATION DESCRIPTION:When having a parent child structure like this: parent(1) - child/parent(2) - child(3)selecting invoices of (3) for parent(2) is not possible
SOLUTION DESCRIPTION:This solution solves defect number 17895.For any parent in between, their childs can be selected now. Selection can only be done to a lower level.
SITUATION DESCRIPTION:Transactions with the status "document sent to customer" appear in the amount received column of session tfacr3440m000("Print Customer Statements"). This is not correct. Only the document has been sent to the customer and the customer hasnot accepted the document yet. So these transactions should not appear in the amount received column.
SOLUTION DESCRIPTION:This solution solves defect number 18086. Now transactions in tfacr200 ("Open Entries") with the status "document sentto customer" no longer appear in the amount received column of session tfacr3440m000
SITUATION DESCRIPTION:When the latest non-posted instruction is deleted in tfgld1107m000, the recurring transaction(tfgld102) and the recurringtransaction instructions(tfgld103) are remaining in the tables. This will cause problems when closing periods in the generalledger.
SOLUTION DESCRIPTION:This solution solves defect number 18120. Now when a recurring instruction is deleted and all other instructions are postedthen the records in tfgld103 and tfgld102 ( the original batch ) pertaining to the batch,year and transaction type are alsodeleted.
SITUATION IDENTIFIED IN: Reset Divided by Zero Amounts on ACR, ACP and GLD (tfcor0225m000)
SITUATION DESCRIPTION:Tax amount field in the open items table for sales (ttfacr200) has zero value after reset of the tax amount field in the homecurrency (tfacr200.vath).
SOLUTION DESCRIPTION:This solution solves defect number 17815. Incase tax amount field for the home currency is reset then the tax amount field isalso reset.
SITUATION DESCRIPTION:When the user runs the session , and in the report if [E] is pressed , it comes out of the session itself. This happens evenwhen there is no data within selection.
SOLUTION DESCRIPTION:This solution solves defect number 18145. Now the session is not aborted automatically.The user comes back to the sessionby exiting the report.Even if there is no data within selection, the user remainsl in the session.
SITUATION DESCRIPTION: 1) After reconciliation of Unallocated/Advance anticipated receipt and allocation of the unallocated receipt to an invoice, itwas possible to switch the status from "complete" to "open" and delete the reconciliation. It is not possible to reverse theallocation then.2) Changing sundry costs was only possible when changing the status.
SOLUTION DESCRIPTION:This solution solves defect number 17720.1) When an allocation is active, it is not possible to continue in tfcmg2103s000. To change the status or sundry costs, youfirst have to delete the allocation.2) Sundry costs can be changed, even when status is already "complete".
SITUATION DESCRIPTION:While Printing Yearly Tax Report (Sorted by suppliers)/(Sorted by customers), Wrong address was being printed for Onetime Suppliers/ Customers. However correct address was being printed for one time Suppliers/ Customers when the secondreport (Sorted by Tax Number) was printed.
SOLUTION DESCRIPTION:
This solution solves defect number 18180. Now the correct address of One time Supplier/ Customer is being printed in boththe reports.
SITUATION DESCRIPTION:Not all subcontracting invoices were composed correctly.
SOLUTION DESCRIPTION:This solution solves defect number 17781.Subcontracting invoices of more then one supplier are now all composed in the payment batch correctly.
SITUATION IDENTIFIED IN: Post FAS transactions to Finance (tffas1201m000)
SITUATION DESCRIPTION:If the Transactions of the Original asset and the Transferred asset are booked into two different documents due to the linenumber restriction of 30000. then the documents become unbalanced.
SOLUTION DESCRIPTION:This solution solves defect number 18018 .Now if the transactions of either one asset(i.e. original or transferred) is bookedin one document, then the transactions of the other asset is also booked into same document even when the line no. limithas been reached.
SITUATION IDENTIFIED IN:Correction program tfcor0316.
SITUATION DESCRIPTION: 1. On the 1.0.6 record, the Currency rate is always set to 0.0000. 2. On the 1.0.5 record, the Currency rate is always set to 0.0000, and the 3 Fiscal Year is always set to zero.
4 Introduction of tfgld112 required to make a quicker and better search possible.
SOLUTION DESCRIPTION:This solution solves defect number 17275 . 1. On the 1.0.6 record, the Currency rate is always set to the rate of the original transaction. 2. On the 1.0.5 record, the Currency rate is always set to the rate of the original transaction, and the 3 Fiscal Year is always set to the year of the original transaction. 4 Introduction of tfgld112 to make a quicker and better search possible.
SITUATION DESCRIPTION: After archiving fully paid invoices, the check number of the payment is not displayed anymore.
SOLUTION DESCRIPTION: This solution solves defect number 18222. Now the check number is displayed, in the session Display purchase invoices.This only counts for newly archived data.
SITUATION DESCRIPTION:Using a taxcode with the status 'Net' in the field 'Amounts entered in Baan finance' in tcmcs0136m000 'maintain taxcodes bycounty.' After you entered an amount in the 'net amount' field and you press tab to go to the 'debit/credit' field, the fielddescription 'net amount' changes to 'gross amount'. This is very confusing, as the amount should be filled in without TAX (net).After saving the record, the description changes from 'gross' to 'net' in the right position.
SOLUTION DESRIPTION:This solution solves the defect number 18306. The problem was due to the fact that no relevant record was being selected. Assuch the default value i.e. Gross amount field was being used. This was solved by selecting the relevant record.
SITUATION IDENTIFIED IN: Maintain Values for Copying Transactions to History (tfgld6205m000)
SITUATION DESCRIPTION:The functionality of archiving/deleting should be moved from tfgld6203m000(Close Year) to tfgld6205m000 in order toimprove the performance of tfgld6203m000.
SOLUTION DESCRIPTION:This solution solves defect number 17987.The functionality of archiving/deleting has been moved from tfgld6203m000 to tfgld6205m000. Now it is possible to copytransactions to a history company (if a valid history company exists and if the answer to the question " ArchiveTransactions to History Company?" is Yes) and delete transactions from the live company using session tfgld6205m000 and itis not possible to do this in session tfgld6203m000.
SITUATION DESCRIPTION:When posting sales invoices through session tfacr4220m000 "Post Sales Invoices", the vat amount for late payment surchargewasn't split up.For every line entered in tfacr4101s000 "Maintain Sales Invoice Lines" the vat amount was posted as one, including vat onlate payment surcharge, in table ttfgld102 "Non-finalized Transactions".
SOLUTION DESCRIPTION:This solution solves defect number 17111.The vat amounts are split up when having vat on a late payment surcharge. Seperate lines are posted to the general ledger'snon-finalized transactions.
SITUATION IDENTIFIED IN: Print Trial Balance - With Dimensions (tfgld3405m000)
SITUATION DESCRIPTION:When printing with a range for sublevel for dimension > 0, totals are always zero.
SOLUTION DESCRIPTION:This solution solves defect number 18131.The totals are from now on always shown for the first entered sublevel on the form of session tfgld3405m000.
SITUATION DESCRIPTION:If a customer statement is printed for a customer without transactions, it is no longer possible to delete this customer.Message 'Update Cancelled' is displayed and the customer is not deleted. It should be possible to delete the customer since hehas no activities.
SOLUTION DESCRIPTION:This solution solves defect number 18186. When running session "Print Customer statements" (tfacr3440m000) a record isonly inserted now in table tfgld304 (Latest used reminder by Customer) for a customer that has transactions. Hence it isthen still possible to delete the customer.
SITUATION DESCRIPTION:Procedure:- Match a purchase order for a cost-item with a PCS-project to a purchase invoice. Make sure there is a price difference- Approve the invoice- Check the integration bookings which are generated- The integration booking 'general costs', which is created because of the price difference, has the status 'Not for Finance'. This is not correct, the status should be 'unposted'
SOLUTION DESCRIPTION:This solution solves defect number 17925.Now, the integration bookings have the correct status after the invoice has been approved.
SITUATION DESCRIPTION:Error message: "cannot sort scratch file ... " when using Windows NT
SOLUTION DESCRIPTION:This solution solves defect number: 18417Because NT has problems with the "|" symbol, which is used in a temporary file, this symbol is changed.
SITUATION DESCRIPTION:Book value should be shown as zero for a disposed fixed asset. When the fixed asset is disposed for amount less than zero,it was not shown as zero.
SOLUTION DESCRIPTION:This solution solves defect 18522. When disposal amount is less than zero, book value calculation were not done correclty.Now this is done correcly. Bookvalue is displayed as zero in the report now.
SITUATION DESCRIPTION:In Transaction types, if the field Documents in Fixed Sequence is NO, then it is possible to maintain negative documentnumbers in all Transaction Categories.
SOLUTION DESCRIPTION:This solution solves defect number 18429. The range of the domain tfgld.docn has been modified in order not to allownegative numbers. Now it is not possible to maintain negative document numbers in any transaction category.
SITUATION DESCRIPTION:It is not possibe to post Journal Vouchers (summarized) if the ledger account has a default tax code maintained. An error"Tax Type must be Sales/Purchase" occurs while saving the Journal Voucher.
SOLUTION DESCRIPTION:This solution solves defect number 18566. The tax code is emptied for session Maintain Journal Vouchers(summarized)(tfgld1114s000). The message "Tax type should be Sales/Purchase" no longer occurs.
SITUATION IDENTIFIED IN: Correct Company Number after Copying Company (PART 1) ( "tfgld9000m000 ")
SITUATION DESCRIPTION:Not all tables get the correct company number after running the session Correct Company Number, after Copying Company(PART 1) (" tfgld9000m000 "). In the tables, the company number is 000 after copying instead of the new companynumber.
SOLUTION DESCRIPTION:This solution solves defect number 18509. The new company Number is updated correctly in all the tables which arecopied.
SITUATION DESCRIPTION:Performance of the session tfacr2100m000 is too slow.
SOLUTION DESCRIPTION:This solution solves defect number: 18235Query extension used a field which wasn't the first in an index. Because of this it took a while before the first row wasfetched.The query extension is replaced by a skip.io("").
SITUATION IDENTIFIED IN: Integration Transactions to Finance Transactions (tfgld4201m000)
SITUATION DESCRIPTION:The expected dimension for a project element was not selected.
SOLUTION DESCRIPTION:This solution solves defect number 18150. Now in the include tfgld4005 theelement is directly read. With this directly read element the dimension is now selected.
SITUATION IDENTIFIED IN: Assign Unallocated/Advance Payments to Invoices (tfcmg2106s000)
SITUATION DESCRIPTION:It is possible that rounding differences occur on unallocated payments in foreign currencies when they are assigned tomultiple purchase invoices. These differences cannot be written off in any way. As a result of this, the unallocated paymentskeep appearing on several reports although they are fully assigned.
SOLUTION DESCRIPTION:This solution solves defect number 17044. Now, when the total amount in foreign currency of an unallocated payment isassigned, the allocated amount in home currency is calculated by taking the remaining amount in home currency. As a resultof this, no rounding difference is present in the balance in home currency. So the unallocated payments which are fullyassigned wil no longer appear on the open item reports.
SITUATION DESCRIPTION:Creating payment orders with a payment amount of 0 is possible. This is possible through either manually or automaticallycomposing.
SOLUTION DESCRIPTION:This solution solves defect number 18608.Processing composed payments with an amount of 0 will only be possible now if check master is used.For all other payment types the message "Payment amount = o" will come up on the report of tfcmg1255m000 "AuditPayments"
SITUATION DESCRIPTION:Clieop file miss the membership numbers for industrial insurance boards and exchequer.
SOLUTION DESCRIPTION:This solution solves defect number 17876.Now the membership numbers for industrial insurance boards and exchequer are displayed by the clieop.
SITUATION IDENTIFIED IN:Maintain fixed asset master data (tffas0106m000)
SITUATION DESCRIPTION:When setup is not done and an investment amount of a fixed asset is corrected, it sometimes does not get updated correctly.
SOLUTION DESCRIPTION:This solution solves defect number 3621.When the setup is not done and the purchase value of a fixed asset is corrected with an amount twice as big as the originalpurchase value, the investment record in logged transaction does get updated correctly now.
SITUATION DESCRIPTION:The correction program otfcor0566 has been adding the missing depreciation records in the table tffas020 (the depreciation
set up records that were not present in the table tffas020 but were correctly registered in the table ffas200). Then set up wasexecuted but the annual depreciation amount in the table tffas201 was still incorrect.The depreciation amount in tffas201 should be equal to the depreciation amount till the set up + the calculateddepreciation amounts after the setup period . In this case, the amounts in tffas201 are only equal to the calculateddepreciation amount.
SOLUTION DESCRIPTION:This solution solves defect number 17597..Now a new session tffas1203m000 has been created ,which recalculates both thetables fas200 and fas201 based on the records in table fas020. Now the results in all the three tables correspond to each othercorrectly.
SITUATION DESCRIPTION:Correction program required to reset the letter number field in the open items table tfacr200 for sales credit notes.
SOLUTION DESCRIPTION:This solution solves defect number 18412.Within this correction program the letter number field (tfacr200.lett) of sales credit notes and advance receipts is initializedto zero.
SITUATION DESCRIPTION: When multiple users are finalizing and when the the finalization of a batch is aborted , the status of the finalization run is changed to "finalized successfully ", even though there are still some records left in tfgld102 table.
SOLUTION DESCRIPTION:This solution solves defect number 17894.Now, when the finalization of a batch is aborted, the status is changed to " in use " .
SITUATION DESCRIPTION:After processing cost allocation (tfcal1204m000) the unallocated amounts are still present in session tfcal1110m000(Maintain Unallocated Amouts). They can only be removed manually in case the allocation code is not a Finance allocation.Request for an option to remove the unallocated amounts after processing.
SOLUTION DESCRIPTION:This solution solves defect number 18712. In session tfcal1204m000 (Process Cost Allocation) an option has been added toremove the unallocated amounts after the processing.
SITUATION DESCRIPTION: When specific blocking codes were entered, even fully paid invoices were being printed, even iffully paid invoices were not to be printed in the report.
SOLUTION DESCRIPTION:This solution solves the defect number 18103. Now only the right information is printed.
SITUATION IDENTIFIED IN: Select Batches for Finalization (" tfgld1111s000 ")
SITUATION DESCRIPTION: After selecting a batch for finalization, if the user selects that record with the mouse , the value of the field "select" will be changed to " No" .But it will again show as " yes " if the cursor is placed on that field .This occurs in BW.
SOLUTION DESCRIPTION:This solution solves defect number 18841 . Now when ever the batch is selected for finalization , the value of the field "select" will have the value as "yes" and this will remain as it is unless the user again changes it .
SITUATION DESCRIPTION:Error message occurs because of an incorrect read of Posting Data for Payments without Invoice.
SOLUTION DESCRIPTION:This solution solves defect number 18852.In the select the field tfcmg102.dbcr was missing. It is added so a correct read of Posting Data for Payments without Invoiceis now done.
VERSION: 3.1_b, B40_b, B40_c SITUATION IDENTIFIED IN:Reports of session tfgld1430m000
SITUATION DESCRIPTION:1. The description of report tfgld143011000 contains the word Espagne. (Language German / French)2. label tfgld.amth in language French not translated as 'Montant net DL'
SOLUTION DESCRIPTION:This solution solves defect number 18877
Report names in language 'German' and 'French' are changed.Label with the correct length created.
SITUATION DESCRIPTION:In a situation where ACR parameter 'Group all letters under Highest Letter' is set to 'yes', the letter number of theremaining invoices does not change when an invoice with the highest letter number is deleted by the user (i.e., field tfacr200.lett is highest in open items tabletfacr200).
SOLUTION DESCRIPTION:This solution solves defect number 18409.If the user now deletes the reminder advice with the highest letter number then the remaining invoices get the letter numberof the remaining next highest letter number.
SITUATION DESCRIPTION:In the column Amount in HC the gross amount for every VAT transaction is registered. This amount is OK when only one VATcode is used.If more VAT codes are used for a prurchase invoice the gross amount is not printed once but several times, thisis not correct
SOLUTION DESRIPTION:This solution solves the defect number 18842. The problem was due to the fact that even if lines were there, the actualinvoice amount(sum of all the lines) was being picked up. This was solved by replacing the invoice amount field from thelayout with the sum of the tax amount and the net amount fields respectively. Hence the problem doesn't exist even if linesare there for the invoice.
SITUATION DESCRIPTION:When a new line is being inserted the description of the ledger account of the previous line is seen.
SOLUTION DESCRIPTION:This solution solves defect number 18978 . Now when a new line is inserted in Maintain Purchase Invoice Transactions (tfacp1120s000 ) , the leder account description no longer shows the previous ledger accounts description.
SITUATION DESCRIPTION:1. A purchase invoice which is not linked to an order and which is not yet finalized is not printed on the report ofsession tfacp4410m000 ("Print Accounts Payable Distribution").
This is not correct. These invoices should be printed.2. Approval transactions are printed, while they should not be printed according to the ledger account selection on theform.3. The selection on purchase orders on the form is not working proporly: Invoices are not printed while they should beprinted.4. If more than one order is linked to a purchase invoice, only the last one is printed.
SOLUTION DESCRIPTION:This solution solves defect number 18863.The problems have been solved:1. Purchase invoices which are not linked to an order and which are not yet finalized are now printed2. The selection on ledger account on the form does now also apply to the approval transactions3. The selection on the purchase orders on the form now relates to the integration transactions instead of the order which isfilled in on the purchase invoice.4. Al the matched orders are printed now.
SITUATION DESCRIPTION:During the finalization of the batch of year end closing, postings were done using the currency rates of the period the batchis going to be booked in.This is wrong.
SOLUTION DESCRIPTION:This solution solves defect 18985.The currency rates picked up was that of the period to which the batch is going to be booked in.This is wrong.The currencyrates that is to be used is the one corresponding to the last date of the closing year.Now it is done correctly.
SITUATION IDENTIFIED IN: Post Integration Transactions to Finance (tfgld4200s000)
SITUATION DESCRIPTION:There is no ledger account found for material costs when the integration transactions are posted to Finance. The integrationsetup is done correctly however.
SOLUTION DESCRIPTION:This solution solves defect number 18862. In some cases no ledger account was found in tfgld4200s000 ("Post IntegrationTransactions to Finance"). This was caused by the fact that an internal buffer was updated too late.
SITUATION DESCRIPTION:Not all subcontracting invoices were composed correctly.
SOLUTION DESCRIPTION:This solution solves defect number 17781.Subcontracting invoices of more then one supplier are now all composed in the payment batch correctly.
SITUATION IDENTIFIED IN: tfgld01017m000 (Maintain Period Status)
SITUATION DESCRIPTION:The period status allowed are "Open, Closed and Finally Closed".But if the user press Ctrl[X], the session was allowing tosave periods with blank status also.
SOLUTION DESCRIPTION:This solution solves defect 19020.No check was present to see if the period status is blank or not.Now a check is done.So periods with blank status are nomore allowed.
VERSION tf3.1_b, tfB40_b, tfB40_c, tfB40L_c_mcr0, tfB50_b
SITUATION IDENTIFIED IN: Select Invoices for Reminding (tfacr3210m000)
SITUATION DESCRIPTION: When "select invoices for Reminding" the payment schedule was not accessed at all times, tocalculate "Amount Overdue". The problem only occurred for the last record per customer/per transactiontype.
SOLUTION DESCRIPTION:This solution solves defect number 18823. The payment schedule is always accessed now.
SITUATION DESCRIPTION: When in the correction session (tfacp2110m000) the supplier(group) , amount or VATcode ischanged, transactions (new and contra) on G.L. account "Registered Invoices" are posted, even when the invoice is notorder-related ( so does not have postings on that GL account in the first place).
SOLUTION DESCRIPTION:This solution solves defect number 18595.Those transactions are only posted now, when the purchase invoice is order related.
SITUATION DESCRIPTION:When Inserting more than one batch without saving and exiting from the session Maintain Transactions , the Batch Status in table tfgld100 ( Batch Status ) is not getting updated to ready ( it remains as empty ) . Also on exiting from the sessiononly the latest batch's status is getting updated. When an error occurs in a batch and subsequently another batch is addedwithout exiting , the Display Error Log is not being displayed.
SOLUTION DESCRIPTION:This solution solves defect number 19051 . Now the Batch Status in table Batch Status ( " tfgld100 " ) is getting updatedeven when another batch is added without exiting from the session Maintain Transactions ( " tfgld1101m000 " )
SITUATION DESCRIPTION: While printing the details of unallocated receipt/payment using ageing analysis code for which the field "selection by" isset to "due date" the amount was getting printed in wrong period .
SOLUTION DESCRIPTION:This solution solves defect 18984.For unallocated receipts/payments due date is not present.So when the field "selection by" is set to " due date", it wastaking value 0 for due date and hence the no.of days was calculated wrongly. .Now it picks up the document date in the caseof unallocated receipts/payments and printing is done in the correct period.
SITUATION IDENTIFIED IN: Maintain Direct Debit Advice (tfcmg4120m000)Select Invoices for Direct Debits (tfcmg4220m00)
SITUATION DESCRIPTION:In session tfcmg4120m000 or tfcmg4220m000, it's not possible to reselect the document which has been rejected at the timeof reconciliation.
SOLUTION DESCRIPTION:This solution solves defect number 18257. Software has been fixed and now it's possible to reselect the rejected document.
SITUATION DESCRIPTION:The search button was not working fine in sessions tfgld3526s000 and tfgld3527s000 in GUI. The find window was gettingopened only when we press the find button and then some other button.
SOLUTION DESCRIPTION:This solution solves defect number 19125. Now the find window is opening as soon as we press the find button in GUI.
SITUATION DESCRIPTION:. If you have a payment method for cheques and if cheque master is set to yes. and the report 126032000 is used, the
payments cannot be processed allthough it is possible to print the cheques . The message tfcmgs0142 "Not all paymentsprocessed" is displayed at the end.
SOLUTION DESCRIPTION:This solution solves defect number DF 19102 .Now the processing is done correctly for the above situation
SITUATION DESCRIPTION:When assigning a credit sales note to a sales invoice, using tfacr4100m000 (maintain sales invoice header), the fieldstfgld102.ctyp and tfgld102.cdoc are wrongly filled. Hence, the fields tfgld106.ctyp and tfgld106.cdoc show the same error.Theresult is that in facr2415m000 (print control account checklist) mistakenly a difference is shown.In the process of assigning asales credit note to a sales invoice, the accounts receivable control account is debited for the amount of the sales credit noteand credited for the amount of the original sales invoice. This latter transaction line should contain a relation to the originalsales invoice document number. Instead, this cross-reference is filled in the other transaction line.
SOLUTION DESCRIPTION:This solution solves the defect number 19081.Finalized transactions and non-finalized transactions now pick up correct transaction type and document number and hencethe report is generated properly.
SITUATION DESCRIPTION:When selecting in the form the flag: accounts without transactions with "yes", the report prints balances for accounts whichhave no balance.For accounts with no balances, by error the last transaction of the account before is printed.
SOLUTION DESCRIPTION:
This solution solves the defect number 18631. The problem was solved by entering default blank values for transactiondata, when accounts with no transactions were being printed.
SITUATION DESCRIPTION:When booking in tfcmg2105s000 manually the message " NO DISCOUNT ACCOUNT DEFINED IN FINANCIAL CUSTOMERGROUPS " was being flashed. However when booking were being done Automatically, the problem was not occuring.
SOLUTION DESCRIPTION:This solution solves defect number 19087. The defect was due to the fact that in the session "Maintain CMGParameters", the field "LEDGE ACCOUNT FOR DEDUCTIONS BY: " was having an entry Tax Code. So it should have picked upthe discount ledger account from the session " Maintain Posting Data by Tax Code ". But instead it was checking whetherthere is a discount ledger account for the Customer Group. This check was removed.
SITUATION DESCRIPTION:When a rounding difference was posted with a transactiontype with updatemode Finalization the history record was updatedrealtime instead of updating during finalization.
SOLUTION DESCRIPTION:This solution solves defect number 18997 . Update of history tables will now only be executed in case a transactiontype has an updatemode set on Real - time or on Endof Session.
SITUATION IDENTIFIED IN:Post FAS Transactions to Finance-tffas1201m000
SITUATION DESCRIPTION: For fixed assets whose investment records are corrected (for eg. the fiscal year might be changed to 3 from 4) , theprogram attimes misses these assets while posting the FAS transactions to finance.
SOLUTION DESCRIPTION:This solution solves defect number19191 .The situation arised because those two assets were corrected. Because of the
correction the first investment record as picked up by the program was not correct.Due to that these assets were missed.Now the assets would not be missed.
SITUATION IDENTIFIED IN: tfcmg1113s000 (Maintain Posting Data of Standing Orders/Stand-alone payment)
SITUATION DESCRIPTION:Although "Units" are maintained for the ledger account used in the session tfcmg1113s000, the system was skipping the"quantity fields" in this session.This is wrong.
SOLUTION DESCRIPTION:This solution solves defect 19320.Now if units are maintained for the ledger account, control goes to the quantity fields in session tfcmg1113s000
SITUATION DESCRIPTION:If the user press the Cancel Button in the session Automatic Matching of Purchase Orders ( tfacp1230s000 ) , thecontrol should go to the session Maintain Purchase Invoices ( "tfacp1110s000" ) instead of Match/Approve PurchaseInvoices with Orders (tfacp1130s000 )
SOLUTION DESCRIPTION:This solution solves defect number 19208 . Since going to the session Maintain Purchase Invoices ( "tfacp1110s000" ) is not possible after pressing the cancel button the cancel button has been removed.
VRC package component comp_type comp_codeB40 c4 tf tfacp1230s000 Form acp1230s0001
SITUATION DESCRIPTION:When a Manual payment of a purchase invoice is done and the supplier balances are printed, the report generated for thepayment done had the amount in the invoice currency. However it had to be in the payment currency.
SOLUTION DESCRIPTION:This solution solves defect number 19100. The problem was due to the fact that the computations involved were usingInvoice currency instead of payment currency. This was solved by using payment currency instead of invoice currency.
SITUATION DESCRIPTION: Batchstatus in tfgld100-table is not update correctly.When in a company no batches are open (status of all batches is 'Finalized') and session tfgld1101m000 is started, the statusof a finalized batch is falsely changed to 'Ready' . The same error occurs when a batch is opened in session tfglds1101m000and the batch is finalized while session tfgld1101m000 is still open. The batchstatus is set to 'Finalized' when finalizing thebatch, but after closing session tfgld1101m000 it is falsely changed to 'Ready' again.
SOLUTION DESCRIPTION:
This solution solves defect number 19207.The batchstatus in tfgld100 is not updated when the session Maintain Transactions (tfgld1101m000) is closed. The status ofa finalized batch will not be changed to 'ready' anymore.
SITUATION DESCRIPTION:When the user prints the customer transactions for only control accounts , some times wrong ledger accounts are printed on the reports and thus lead to wrong opening balances .
SOLUTION DESCRIPTION:This solution solves defect number 19038 . Now the correct ledger accounts are picked up and the correct opening balances are printed on the reports.
SITUATION DESCRIPTION: When report option ""Order Receipt Account" is specified, orders which are invoiced areprinted anyway.
SOLUTION DESCRIPTION: This solution solves defect number 18891. When using the full range:The program shows the orders that are delivered, not yet invoiced. It calculates the outstanding amount, regardless whichledger accounts are used.When you apply for a specific ledger account: The program calculates per order /per ledger account the outstanding amount.
SITUATION DESCRIPTION:The session tfacp1120s000 /tfacr1111s000 used to start up at the filed Ledger Account.In the case of inter companytransactions, the user has to go to the company number field using arrow key and then change the target company.
SOLUTION DESCRIPTION:This solution solves the defect 19160.Now in the case of multifinance company structure, the session tfacp1120s000/tfacr1111s000 starts up at the Target Companyfield instead of Ledger Account field.In the case of single finance company structure, the session still starts up at fieldLedger Account .
SITUATION DESCRIPTION:Within a range of reminders, find key (ctrl-f) does not selects the desired customer. This happens when the previouslyselected customer invoice key is bigger than the invoice keys available for the selected customer.
SOLUTION DESCRIPTION:This solution solves defect number 18879. Now the correct customer gets selected with the find key.
SITUATION DESCRIPTION: Finding the available statement of methods was difficult in the session Display Statement of Account Methods (tfacr3521s000 ) , especially in the GUI version , due to the form being single occurence.
SOLUTION DESCRIPTION:This solution solves defect number 19357 . Now it is possible to zoom to the available statement methods , in the sessin Display Statement of Account Methods ( tfacr3521s000 ) .
VRC package component comp_type comp_codeB40 c4 tf tfacr3521s000 Form acr3521s0001
SITUATION IDENTIFIED IN:Select Invoices for Payment ( tfcmg1220m000)
SITUATION DESCRIPTION:When selecting invoices for payment, the session would calculate discounts even if the payment was being made after thediscount period.
SOLUTION DESCRIPTION:This solution solves defect number 19298. Now the session calculates discounts only if the payment date falls within thediscount period.
SITUATION IDENTIFIED IN: Display Chart of Accounts (tfgld0551s000)
SITUATION DESCRIPTION:When a record is marked in the ASCII-userinterface and Ctrl-Z was pressed, the system came up with the message 'No recordmarked'. This is wrong, because the record is marked.
SOLUTION DESCRIPTION:Now the zoom in the session tfgld0551s000 works fine. When you are on the choicefield in ASCII you press 'M' to mark arecord. If you have done this you press 'Y' to confirm the mark and then Ctrl-Z. You will now enter session tfgld0508s000.
SITUATION DESCRIPTION:Table tfgld106 is growing very rapidly and needs compression.
SOLUTION DESCRIPTION:This solution solves defect number 19370.New session has been created for compressing 'Finalized Transactions' (table tfgld106).If integrations are involved then also the reference to gld106 is updated.
SITUATION DESCRIPTION:When the payment and invoice currencies are different and the payment amount falls short of the invoice amount , then, while allocating the payments to invoice automatically, the invoice balance was not calculated correctly.
SOLUTION DESCRIPTION:This solution solves defect number 19388 . Now the invoice balance is calculated after taking into account the paymentcurrency.
SITUATION DESCRIPTION:When running session Remove Fully Paid Invoices (tfacp2250m000) an errormessage comes up:ERROR: Illegal type assigned to hold.ttyp, expected [STRING].
SOLUTION DESCRIPTION:This solution solves defect number .19294This error is caused by using the wrong index for table Authorizations for Received Purchase Invoices (tfacp102). Now theReceived Invoice from table tfacp100 will also be archived, and the errormessage won't come up anymore.If a record is read in table Open Items (tfacp200) the reference in table Received Purchase Invoice (tfacp100) will be readalso. From table tfacp100 the reference in table Authorizations for Received Purchase Invoices (tfacp102) will also be read. So, if you created an invoice from a received purchase invoice the record from tfacp100 and tfacp102 will also bearchieved.
SITUATION IDENTIFIED IN: Select Invoices for Direct Debits (tfcmg4220m000)
SITUATION DESCRIPTION:Label on the form was not printed.
SOLUTION DESCRIPTION:This solution solves defect number 19536 .Label was not printed because it was too long for the form. After text adjustment, Label now does appear on the form.
SITUATION IDENTIFIED IN:Session "Reconciliation of anticipated receipts - tfcmg2103s000"
SITUATION DESCRIPTION:The stand-alone bank transaction did not contain the same amounts as the banktransaction booked on theunallocated anticipated receipts.
SOLUTION DESCRIPTION:This solution solves defect number 18972.Customer Reconciliation (in GLD) for an unallocated anticipated receipts in a foreign currency (GBP) works good now.
SITUATION IDENTIFIED IN: tfacr2420m000 (Print Aging Analysis By Customer)
SITUATION DESCRIPTION:
While printing the aging analysis report based on Sales Representative, payments were placed on Sales Representative 0eventhough the inovice has got a sales representative.
SOLUTION DESCRIPTION:This solution solves the defect 19254.Now payments are placed on the sales representative of the corresponding sales inovice.
SITUATION DESCRIPTION:During year_end a batch is created with opening balances of the new year. The vat period and year are wrongly filled.They
are filled with the last period of the year that is closed during year end. They should have been filled in with the year andfirst open vat period of the new year.
SOLUTION DESCRIPTION:This solution solves defect number DF 18983.Now the Vat year anf Vat period are filled correctly.
SITUATION IDENTIFIED IN: Post Integration Transactions (tfgld4200m000)
SITUATION DESCRIPTION:The Sales/Revenue transactions will only be posted to finance when the project is closed.The document date of the integration document created reamains the same 31-12-9999 even if the document has been postedin the actual periods.
NOTE: when the project is closed in the PCS module in the session tipcs2250m000, you can overwrite the Booking DteCst/Turnover Sls defined in the session tipcs2101m000. In this case, the date registered in this session will be overwrittenwith the actual date (date of completion of the project).
SOLUTION DESCRIPTION:This solution solves defect number 17944. Document Date will also be overwritten by the actual Book Date.
SITUATION IDENTIFIED IN: tfacp2434m000 ( Print Supplier's Total Balance by Company ) tfacr2434m000 ( Print Customer's Total Balance by Company )
SITUATION DESCRIPTION:When two suppliers/customers are having the same search key, and the report is printed based on search key, thesupplier/customer balance for only one supplier/customer was getting printed.
SOLUTION DESCRIPTION:This solution solves defect 19314.Now the supplier/customer balances are printed correclty for suppliers/customers having the same search key.
SITUATION DESCRIPTION:Printing with a range of cheques specified from "0" gives message "No Data within Selection"This means you wish to leave the range for cheques open, so cheque number is irrelevant.
SOLUTION DESCRIPTION:This solution solves defect number 19575.The program domain for cheques is of type 'string'. So if no cheque number is filled searching tables starts with "0" andtherefore will not find any anticipated payments in table tfcmg110 with cheque number 'empty'.
SITUATION IDENTIFIED IN: Transfer Payments (tfcmg1260s000)
SITUATION DESCRIPTION:The layout for the BACS-file was in a wrong format. The file.ident specified on the form of tfcmg1260s000 "TransferPayments",was printed instead of the senders.ident string.
SOLUTION DESCRIPTION:This solution solves defect number 19524.The file.ident strings in the BACS report-layout have been replaced by a senders.ident string of six characters long.For those six characters also the form of session tfcmg1260s000 and the script needed to be changed.
SITUATION DESCRIPTION:For the fiscal Period , only the 'to' option is present ,so the user is not able to select transactions with in a paricularperiod. All the transactions are being printed .
SOLUTION DESCRIPTION:This solution solves defect number 19707 . Now the user can print transactions of a particular period also .For the fiscal period, 'From' field is provided on the form.
SITUATION IDENTIFIED IN : Approve Purchase Invoices "tfacp1140s000"
SITUATION DESCRIPTION: When approving an invoice with an matched amount of 0,- , the system gave came up witherror message: "Fatal Error: Float exception".
SOLUTION DESCRIPTION: This solution solves defect number 19705.The error occurred due to deviation of the matched amount which in this case was zero.
The calculation has been changed so deviding through zero is not possible anymore.
SITUATION IDENTIFIED IN:tfcmg2109s000 "Assign Invoices based on aging"
SITUATION DESCRIPTION:When entering a range of transaction types in session tfcmg2109s000, the system did not take this range into account.It always selected for all transaction types.
SOLUTION DESCRIPTION:This solution solves defect number 19459.Range of transaction types is now taken into account.Selection extended.
SITUATION DESCRIPTION:When a document in table Non-Finalized Transactions (tfgld102) is generated with more then 32767 lines on it. The linenumber will get negative. This is not correct. Instead of this a new document should be created.
SOLUTION DESCRIPTION:This solution solves defect number .19620The correction program delivered by this solution will make it possible to correct negative lines in tfgld102. On the formof the correction program you must enter the year, the batchnumber, the transaction type and the document. For thisdocument all negative lines will be transvered to a new document in the same batch.It is possible to run the correction program in test-mode. If you do this you will ge a report with the number of lineswhich have negative linenumbers and you will get the new documentnumber where the transaction will be moved to.The same report is printed when you run the correction program not in test-mode, the only difference is that f thetest-modeis of the table concerned will be updated.This correction program will of course only work for record which are present in tfgld102. This is the only table which isupdated. The ledger account which is used to post on is the ledger account 'Interim Closing Account'. This is the ledger accountwhich you can define in session tfgld0103m000 on the third form.
SITUATION DESCRIPTION:When a purchase or sales invoice is entered in the system and the invoice is written to the table. After that you are going tochange or add a reference on the invoice. While doing this the field tfacp200.vati/tfacr200.vati is not updated correctly. Thisfield should stay 0 when you are a tax code of type 'shifted' on this invoice.
SOLUTION DESCRIPTION:This solution solves defect number .19579The mentioned problem is corrected by building this solution. The field tfacp200.vati and tfacr200.vati will not be updatedwhen you are using shifted vat and you are changing you reference of the invoice.
SITUATION DESCRIPTION:When the data is entered in this session you have to type 4 characters of the enumvalue 'debit/credit' before the programaccepts the enumvalue. This is very annoying when a lot of data entry must be done.
SOLUTION DESCRIPTION:This solution solves defect number .19824The problem described in the situation description only occured in the ASCII-mode. It is now possible to enter the firstcharacter of the word 'Debit' or 'Credit' and press enter.
VRC package component comp_type comp_codeB40 c4 tf tfgld1115s000 Form gld1115s0001
Solution : 15207
VERSION: tf3.1_b tfB40_b, tfB40_c, tfB40L_c_mcr0
SITUATION IDENTIFIED IN:Assign Credit Notes to Invoices (tfacr2121s000)
SITUATION DESCRIPTION:1. It is not possible to zoom on the field 'Contract/Order'.2. Not all additional data is filled when zooming on the field 'Packing Slib'3. No message is given when you enter a supplier on the invoice that differs from the supplier on the order.
SOLUTION DESCRIPTION:This solution solves defect number . 196881) When you are now zooming on the field 'Packing Slib, the fields Supplier, Contract/Order and Receipt Date will be filledas well. 2 ) Enabled to zoom on the field 'Contract/Order'. The fields Supplier and Receipt Date will be filled when you return tosession tfacp1110s000.3) A message is build in. The message will show when then supplier on the invoice differs from the supplier on the order.