DBS to 5.0 Delta Presentation

DBS 2.3.4 to 5.0 Delta Presentation
This presentation will cover the Finance Integration process FN/F4 DBS to 5.0 Delta Presentation Finance Integration

Agenda Retired functionality Changes to existing functionality
IAS Menus and functions Changes to existing functionality IAS Menus DBS Menus DBSi functions For our agenda, we will be covering retired functionality, changed functionality and….

Agenda New functionality System Menu functions New functionality

IAS Menus and functions Changes to existing functionality IAS Menus DBS Menus DBSi functions For the retired functionality, we will cover menus and functions that are being removed

2.3.4 Retired functionality
The TFRAAIAS function on the FNMENU has been removed: Access to CODA V4 through the TFRAAIAS function is no longer available. CODA V10 will be accessed through a URL CODA V10 will be accessed via a URL and not through DBSi.

2.3.4 Retired functionality
Main IAS Menu has been removed. All IAS menus have been removed Much of the functionality has been moved to DBSi screens. We will cover those functions under “Changes” All IAS functions have been either moved to other DBSi screens or to CODA V10.

IAS Menus and functions Changes to existing functionality IAS Menus DBS Menus As per the agenda, we will now cover changes to existing functionality, beginning with IAS menus.

Changes – IAS functions
Where have all the functions gone? Lettered functions from the Main IAS (CODA V4) screen will now be done within CODA V10. The lettered functions with IAS are CODA functions and will still be done within CODA.

Where have all the functions gone? The D1 through D4 screens and their functions have been moved to other DBSi screens, The D1 – D4 screen functions have moved to other DBSi screens.

Changes – DBS/IAS Integration Parameters (D1)
D1 – DBS/IAS Integration Parameters: The functions on the D1 menu that are indicated by the red boxes have been moved to a new 5.0 menu, Accounting Menu (ATMENU), The functions above have been moved to a new menu called the Accounting Menu (ATMENU).

Changes – Accounting Menu (ATMENU)
This display is of the 5.0 Accounting Menu. The outlined functions come from the D1 (DBS/IAS Integration parameters) menu. The outlined transactions on the Accounting Menu are the IAS functions from D1.

2.3.4 D1 – DBS/IAS Integration Parameters: Other functions on the D1 menu have been moved to the Entry Code Set Up Menu. The above outlined functions have been moved to the Entry Code Menu (ECMENU).

Changes – Entry Code Set Up Menu (ECMENU)
The outlined functions have been moved from the D1 menu (DBS/IAS Integration Parameters). The above outlined functions are from the IAS D1 Menu.

2.3.4 D1 – DBS/IAS Integration Parameters: The Credit Check Parms and Cust Account Balance functions have been moved to the Finance Menu (FNMENU). The above outlined functions have been moved to the Finance Menu (FNMENU).

Changes – Finance Menu (FNMENU)
The two outlined functions have been moved from the D1 (DBS/IAS Integrations parameters) menu in IAS (CODA V4). The above outlined functions are from the IAS D1 Menu.

2.3.4 D2 – Finance Conversion Programs: From the D2 (Finance Conversion Programs, Customer and Vendor have been removed. Company Code has been moved to the Accounting (ATMENU). The above outlined function has been moved to the Accounting Menu (ATMENU).

5.0 Finance Menu (ATMENU): The DBSi 5.0 Accounting Integration Menu shows the Update Company Code (MNTFNCOUP). The above outlined function has been moved to the Accounting Menu (ATMENU).

2.34 D3 – DBS/IAS Batch Job Submission: Several functions from the D3 (DBS/IAS Batch Job Submission) screen have been moved to the Finance Menu (FNMENU). The above outlined functions have been moved to the Finance Menu (FNMENU).

5.0 Finance Menu (FNMENU), page 2: The afore mentioned functions can now be accessed from the DBSi 5.0 Finance Menu (FNMENU). The above outlined functions are from the IAS D3 Menu.

D3 – DBS/IAS Batch Job Submission: On the D3 (DBS/IAS Batch Job Submission Screen), the Update EMS (option 60) has been moved to the Finance Menu (FNMENU), function LSTFNDALY. The above outlined function has been moved to the Finance Menu (FNMENU), function LSTFNDALY.

This screen show the Finance Menu and the LSTFNDALY function. LSTFNDALY function lists various daily jobs for submission.

LSTFNDALY, page 2: When the LSTFNDALY function is selected, a list of jobs is displayed. Page down to page two of the list. The FNJN2500S job for EMS-FI Transaction Update replaces the option 60. FNJN2500S – EMS – FI Transaction Update replaces option 60

D3 – DBS/IAS Batch Job Submission Cat Reporting – FMRG Report Maintenance

D4 – Caterpillar Purchase Analysis System All functions from the D4 (Caterpillar Purchase Analysis System) have been moved to the 5.0 Finance Menu (FNMENU), page 2. All functions from the D4 IAS Menu have been moved to the Finance Menu (FNMENU), page 2.

5.0 Finance Menu (FNMENU), page 2: This slide displays the Cat Financial Reporting functions from the D4 menu. The above outlined functions are from the IAS D4 Menu.

Changes – IAS/DBSi function cross-reference
IAS MENU IAS Function IAS FUNCTION DBSi MENU DBSi FUNCTION D1 01 Integration Parms ATMENU MNTFNCOCD 02 System Codes MTNFNSYCD 03 Program Numbers MNTFNPGNO 04 Transaction Codes MNTFNTRCD 05 DBS to IAS Updates MNTFNTRIN 06 Document Type X Ref FNMENU MNTFNCRDP 07 Credit Check Parms 08 Cust Account Balance MNTFNDIST, pg 2 09 Invoicing Entry Code ECMENU MTNFNCREC 10 Entry Code Desc 11 Entry Distribution MNTFNDIST 12 Information Codes MNTFNINFO 13 Statistics Codes 14 Sequence Numbers MNTFNDSEQ 15 EC Access Search MTNFNECAC 16 Store Reporting Lvl MNTFNRLVL This is a cross-reference table showing the IAS menus and functions and their associated DBSi menu and function.

Changes – IAS/DBSi function cross-reference
IAS MENU IAS Function IAS FUNCTION DBSi MENU DBSi FUNCTION D2 92 Customer NA 94 Vendor 99 Company Code ATMENU MNTFNCOUP D3 60 Update EMS FNMENU LSTFNDALY 61 Maintain Dist Recs FNMENU, pg 2 MNTFNDREC 62 PI Transactions FNMENU, pg2 CRTFNPITR 63 Purge Invoices CRTFNPAPI 64 Match MNTFNMINV 65 Parts Acct Purge CRTFNPPTA 66 Cat Reporting ?? D4 20 Dealer Code MNTFNPADC 21 PSO Store MNTFNPAPS 22 Major Charge Code MNTFNPACC 23 Misc. Charge Code MNTFNPAMC 24 Invoice MNTFNPAIN 25 Invoice PSO Store MNTFNPAIP 26 Invoice Item MTNFNPAIM Page 2 of the table

IAS Menus and functions Changes to existing functionality IAS Menus DBS Menus DBS functions Next we will cover the changed functionality, beginning with the changes to the DBS menus.

Changes in DBSi menus: TRFAAIAS replaced with URL for 5.0 CODA
Finance Menu (FNMENU): The changes to the Finance Menu are: Removal of the TFRAAIAS.function Removal of the GLMENU option And the removal of the MNTGLREAC function TRFAAIAS replaced with URL for 5.0 CODA GLMENU and MNTGLREAC functions done within CODA V10

Changes in DBSi menus: 2.3.4 General Ledger Menu (GLMENU):
The MNTFNDIV function that was displayed on the General Ledger menu will now be displayed on the 5.0 Finance Menu. The General Ledger (GLMENU) no longer exists in DBSi 5.0. MNTFNDIV has been moved to the Finance Menu (FNMENU), otherwise the rest of the functions are performed in CODA.

Changes in DBSi menus: 5.0 Finance Menu (FNMENU): The slide shows the location of the MNTFNDIV function It also shows additional functions new to 2.3.4 MNTFNDIV Division Codes is now located on the FNMENU for 5.0. The other five outlined functions have also been added to the FNMENU.

Changes in DBSi Menus: The FNMENU now has a second page
5.0 FNMENU, page 2: The Finance Menu now has a second page. The FNMENU now has a second page

Changes in DBSi Menus: 5.0 Accounting Menu (ATMENU): The Accounting Menu is new to the DBS users. The functions came from the CODA D1 (DBS/IAS Integration parameters) and D2 (Finance Conversion programs) screens. The ATMENU is new to the DBS users. These functions come from the CODA D1 and D2 screens.

Changes in DBSi Menus: 2.3.4 Entry Code Set Up (ECMENU): MNTCINAA has been removed from the 5.0 Entry Code Set up menu. It has been combined with the MNTCICUS function on the CIMENU. The Customer Financial Information is primarily located on screen 3 of this function There are two finance related fields on page 2 of this function as well. MNTCINAA has been combined with MNTCICUS. The customer financial information is now screen 3 of the customer maintenance function .

Changes in DBSi Menus: 5.0 Entry Code Set Up Menu (ECMENU):
The functions in the right column on the Entry Code Set Up screen are from the Coda D1 screen. MNTEMACL was moved from the right column to the left column,. Functions from the CODA D1 screen have been moved to the Entry Code Set Up screen (ECMENU). MNTEMACL has been moved from the right to the left column.

IAS Menus and functions Changes to existing functionality IAS Menus DBS Menus DBSi functions Next we will cover changes to DBSi functionality

Changes to DBSi functionality:
5.0 Accounting (ATMENU): Changes have been made to the Company Integration (MNTFNCOCD) function. Changes have been made to the Company Integration (MNTFNCOCD) function for DBSi 5.0.

DBS Maintain Company Integration Parameters (01): Password and Data library have been removed Error processing account has been removed Credit check at open/close has been moved to the Credit Check Parms function (MNTFNCRDP) on the Finance Menu. Password and Data Library have been removed. Error processing account has been removed Credit check at open/close has been moved to the Credit Check Parms (MNTFNCRDP) on the Finance Menu

5.0 Company Integration (MNTFNCOCD): Web server path has been added Child, instead of Vendor is assigned to an element Allowing posting to EMS previous/future periods has been added. Web Server Path has been added. Child instead of Vendor is assigned to an element EMS Previous/Future posting periods has been added

Company Integration Parameters Operator: This is a name used for all interface access to CODA from DBSi. Capability Group: Usually same as operator Web Server Path: This is the server address to access CODA from DBSi Element No and Account Template for Customer: This is the Element Template setup in CODA for customer. This template is accessed by DBSi for specific information when DBSi sends new customers to CODA. Element No and account template for CHILD: Level and Account Template for Child Customer – This is the Element Template setup in CODA for child customer. This template is accessed by DBSi for specific information when DBSi sends new child customers to CODA. This information is required only if parent/child functionality is being used and the child is being sent to CODA as an element. Transaction Update Error Processing: Posting Option (I:Intray P:Books) – If Intray is specified then DBSi will always send transactions there. If Books is specified then DBSi will send transactions to the books. Posting options established on specific CODA document masters will determine if there is a posting to the intray if errors occur. Tax code: If this field is populated, special processing takes place for VAT tax EMS Posting Periods: Determines if EMS transactions can post to previous periods (how many periods) and if EMS transactions can post to future periods (how many. This slide gives more detail of the fields on the MTNFNCOCD function.

2.3.4 Document type X ref (option 06): Option 06 from is now function MNTFNDTCR on the ATMENU in 5.0. Options 5, 6, and 7 have been added to the Customer Invoice Type options. Now MNTFNDTCR on the ATMENU in DBSi 5.0 Customer invoice type has had options 5, 6 and 7 added for VAT tax customers.

2.3.4 Store Reporting LVL (option 16): DBSi 5.0 Store Reporting level for was option 16 from the D1 screen. It is now MNTFNRLVL from the ATMENU. Store Next and Next Level are no longer needed Parts has moved to the last item on the list of system names MNTFNRLVL on the ATMENU in DBSi 5.0 Store Next and Next Level have been removed Parts has changed position, it is now listed last

5.0 Accounting Integration (ATMENU): Two new functions, not previously existing in DBS are on the Accounting Menu. These two functions will be discussed in detail under New functionality Two new functions have been added: MNTFNCURR and MNTFNIFSP These functions will be covered in more detail under the New Functionality of 5.0

5.0 Customer Information Menu (CIMENU): To view or update customer finance information, formerly MNTCINAA on the Entry Code Set up Menu, use function MNTCICUS on the CIMENU. To view or update customer financial information, formerly MNTCINAA on the Entry Code Set up Menu, use function MNTCICUS on the CIMENU.

5.0 Customer Information (MNTCICUS): When the key screen displays, use option 1 for Name and Address Once the customer number has been entered, select option 1 for Name and Address

5.0 Customer Information (MNTCICUS): Credit Manager field must be a set up in MNTFNCRAL as a credit manager Look up capability is available for this field Financial Parent is available for a customer number of another customer who assumes financial responsibility for this customer. On page 2 of MNTCICUS, there are two finance fields that you should be aware of: Credit Manager Financial Parent

5.0 Customer Information (MNTCICUS): Here is where the credit limit and credit category is set up for each credit area being used by the dealership. This is also where any special payment terms will be set up the customer. On page 3 of MNTCICUS, you set: Credit limit and credit category for each credit area being used by your dealership Special payment terms that will apply for this customer

i 5.0 Entry Code Distribution (MNTFNDIST): 2.3.4 Option 11 Maintain entry distribution was formerly option 11. The element string is now displayed on the list screen. Formerly option 11 Element string has been added to the List of Entry distributions

5.0 Entry Code Distribution (MNTFNDIST): 2.3.4 option 11 details For 5.0, there are now eight elements available instead of the four elements of 2.3.4 The screen is arranged a little differently, but the rest of the functionality remains the same In 5.0 there are now 8 elements instead of 4. The rest of the functionality remains the same.

Elements for 5.0: There will be eight elements instead of four Each element will have a limit of 24 characters It will be possible to concatenate a maximum of four info codes per element. Translated element strings cannot exceed 79 characters. Elements for CODA V10 have returned from CODA V4 in There are four changes: There will eight instead of four Each element will have a limit of 24 characters It will be possible to concatenate a maximum of four info codes per element Element strings cannot exceed 79 characters

5.0 Entry Code Distribution (MNTFNDIST): 2.3.4 F11=Variables The F11=Variables screen has changed a lot from 2.3.4 The Entry code description is entered here. It was formerly option 10 in 2.3.4 6 external references per element can be entered for a total of 48. This is any additional information in for form of an information code that you may want to send with the transaction to the financial system. Four quantities can be added per element for a total of 32. These are numeric information codes and were formerly known as statistic codes in The F11=Variables screen offers: An entry code description (option10 in 2.3.4) 6 external references per element 4 quantities (formerly known as statistic codes) per element

External References for 5.0: There will be six external references instead of three. External references will be 32 characters. External references will be assigned by entry code/sequence in DBSi in function MNTFNDIST. Document prototypes in CODA V10 will determine whether or not external references will be allowed at the line item level for the document code/type in question. External References are assigned to entry codes to carry additional information to CODA There can now be 6 instead of 3 as was in CODA V4 There is 32 characters allowed for each reference External references are assigned by entry cods/sequence in MNTFNDIST Document prototypes in CODA V10 will determine if external references will be allowed at the line item level for the document code/type in question.

5.0 Quantity codes (formerly statistic codes in 2.3.4) Quantity fields are assigned by entry code/sequence/element in MNTFNDIST in DBSi All quantity fields will need to be set up in CODA V10 as well as DBSi Quantity fields contain numeric info codes There can be up to 32 quantity codes set up, 4 for each of the 8 elements Variables are no available in DBSi 5.0 Quantity fields are available to replace variables Quantity fields are assigned by entry code/sequence/element in MNTFNDIST Quantity fields will need to be set up in CODA as well as DBSi Quantity codes will contain numeric info codes There can be up to 32 quantity codes set up, 4 for each of the 8 elements

Information Codes (MNTFNINFO) (Option 12 in 2.3.4): There are seven new information codes for 5.0: CCTR – Cost Center CHLD – Child Customer number CRAR – Credit Area DIVI – Division Indicator 2 MSEG – Market Segment MSSG – Market Subsegment PCTR – Profit Center Specific data fields in DBSi can be passed through to CODA on accounting transactions. Each data field is given a 4-character code known as an information code. These info codes are specified within each entry code to be passed either as an element or an external reference. Two new info codes have been added for 5.0, CHLD-child customer number and CRAC-credit area

2.3.4 Store Reporting LVL (option 16) 5.0 Store Reporting LVL Three fields were removed from the Store/Reporting Level screen : Store Next level Last Maintenance date The following fields have been removed from the 5.0 screen: Store (ST) Next lvl Last Maintenance

5.0 Customer Account Balance (option 08 in 2.3.4) Customer Account Balance simply associates a credit area to a CODA ledger for each store used. Document Source has been replaced by Credit Area Sequence and elements have been replaced by a CODA ledger name.

5.0 PI Transactions (option 62 in 2.3.4) In 5.0 for PI transactions, User reference 1, now replaces User Reference 2. In 5.0, User reference 1 replaces User Reference 2

5.0 List of Parts Movement entry codes (MNTFNMOVE) MNTFNMOVE exists in both and 5.0 on the Finance Menu The only change is that User Ref 1 now replaces User Ref 2 in 2.3.4 In 5.0 User Ref 1 replaces User Ref 2 in 2.3.4

5.0 Submit Daily jobs (option 30 in 2.3.4): On page 2 of the Finance Menu, function LSTFNDALY replaces Submit Daily Jobs (option 30 in 2.3.4) LSTFNDALY is available on page 2 of the Finance Menu (FNMENU).

5.0 Submit Daily Jobs: In 5.0, Submit Daily Jobs, Rental and RMS have been added to the list of systems to select to include in the FNJN5200S job. Of the jobs listed, Customer EFT Payments has been removed. Rental and RMS have been added as systems to be selected for the FNJN5200S job. Customer EFT Payments has been removed

5.0 Submit Daily Job Reports: FNJN5200S generates a report that displays the job submission parameters Rental and RMS have been added Customer EDT payments has been removed. No action is required for this report FNJN5200S generates a report: It displays the submission parameters to the job. Rental and RMS have been added Customer EFT Payments has been removed

5.0 Submit Daily Job Reports: The only change to the FNJN5300S job, Transaction Distribution Error Report is: IAS Document has been changed to Reference Document. Several new error messages have been added to the program. FNJN5300S generates Transaction Distribution Error Report IAS Document has been changed to Reference Document Several new errors have been added to the program. Usually the same corrective actions are done in 5.0 as was in 2.3.4

5.0 Submit Daily Job Reports: The first of the reports generated from the FNJN5400S job is the Details of Documents Posted to Finance Intray This could include errors such as: Out of balance condition Account combination Four reports are generated from FNJN5400S The first is “Details of Document Posted to Finance Intray” ,errors such as: Out of balance condition Account combination

5.0 Submit Daily Job Reports: The second report is “Documents Ineligible for Posting to Finance”. DBSi transactions which failed the CODA edits Invalid accounting period External references or quantities that failed edits These are fatal errors and are not posted to CODA or to Intray. Require manual booking to finance system The second report generated from the FNJN5400S job is the Documents Ineligible for posting to Finance. This could include errors such as: Invalid accounting period External references or quantities do not match the CODA master setup These are fatal errors and are not posted to CODA or to Intray. They require manual posting within the finance system

5.0 Submit Daily Job Reports: The third report is ”Results of Documents Processed”. Number of documents processed Number of documents not sent to Finance Duplicate document type and sequence Number sent to Finance The third report is a control report that gives counts and a breakdown of the documents processed

5.0 Submit Daily Job Reports: The forth and final report is ”Details of Documents Failed in Posting to Finance”. Before sending a transaction to CODA, the processing indicator on the FNPTRHD0 file is set to “6”. If a Document is successfully posted to Intray, the processing indicator on the FNPTRHD0 file is set to “5”. If a document is not successfully posted to the finance system, the processing indicator on the FNPTRHD0 file is set to “4”. The forth and final report is the Details of Documents Failed in Posting to Finance. If a document is posted to intray, the processing status is set to “5” on the FNPTRHD0 file. If a document failed to post at all, the processing status indicator is set to “4”. Status 4 transactions will need to be manually corrected and set back to “3” to be reprocessed. Status 5’s can be corrected in CODA in Intray. Otherwise the processing status indicator is set to “6” as successful.

5.0 Submit Daily Jobs (LSTFNDALY), page 2: The Submit Daily Jobs screen now has a second page FNJN2500S updates the EMS transaction register (EMPTREG0 file) with AP invoice transactions and AR payment transactions made in CODA The other three jobs are new and will be covered in the New functionality portion of this presentation FNJN2500S – EMS – FI Transaction Update takes the place of option 60 (Update EMS invoice payments in DBS The three other jobs are new to 5.0

5.0 Submit Monthly jobs (option 34 in 2.3.4): Monthly jobs, formerly option 34 in 2.3.4, are now submitted using function LSTFNMONT on the second page of the Finance Screen in 5.0 LSTFNMONT is available on page 2 of the Finance Menu (FNMENU).

5.0 LSTFNMONT – Submit Monthly Jobs: On the parameters screen for LSTFNMONT, sort code and vendor account have been removed Options to Report Only or Both has been added. This allows generating a report with no posting, or posting and generating a report as well. Valid entries are R for report only, or B for both. Post Non-current transactions has been added to include posting transactions from other posting periods to post. Valid entries are “Y” for Yes to post transactions from other periods or blank to not post transactions from other periods The Sort Code and Vendor Account parameters have been removed The Report Only or Both and Post Non-Current Transactions parameters have been added

Agenda New functionality System Menu functions
We will now cover New functionality from to 5.0 First, we will cover the change in the CODA system

New functionality in DBSi 5.0
System The CODA Financials system will run on a Microsoft Windows platform using Microsoft SQL Server. Financials will use XMLi, CODA’s integration tool to inquire from or update the Financials tables. Each call to CODA Financials using XMLi is made up of a request (information being sent to CODA) and a response (receiving information from CODA) call. All programs handling XMLi calls are named FNC7nnn (nnn being any number). CODA will resided on a server running on Windows Microsoft SQL Server 2005.

Agenda New functionality System Menu functions
Next, under New functionality, we will cover the new menu functions

5.0 LSTFNDALY – Submit Daily Jobs LSTFNDALY – Submit Daily Jobs screen now has a second page. The new jobs are: FNJN2500S – EMS-FI Transaction Update. This pulls the AR payments made in CODA to update the EMS transaction register. FNJN2560S - Exchange Rate Update. This job pulls the most current currency rates from CODA to DBSi. FNJN0409S – Purge Blocked Orders Documents. This job purges all qualifying records from the blocked order file (FNPBLKO0). FNJN0406S – Update Blocked Orders Days Outstanding. This job calls CODA to update the past due aging buckets on the blocked order file (FNPBLKO0). There are three new jobs on the LSTFNDALY screen: Exchange Rate Update Purge Blocked Orders Documents Update Blocked Orders Days Outstanding

5.0 FNJN2560S – Exchange Rate Update FNJN2560S updates the exchange rate file (FNPEXRT0) with current rates from CODA This job updates the exchange rate file (FNPEXRT0) with current rates from CODA.

Exchange rate update If a translation is needed between currencies there is a program that is called in DBSi that will handle the conversion. This job interfaces with CODA to pull over the new rates and update the exchange rate file (FNPEXRT0). Only exchange rates set up in DBSi (FNPEXDD0 file, function MNTFNCURR on the ATMENU) are retrieved and updated. So if a new currency code is set up in CODA, the new code must also be set up in DBSi. If a translation is needed between currencies in DBSi, DBSi will handle the conversion. FNJN2560S interfaces with CODA to pull over the most current rates to update the FNPEXRT0 file in DBSi. Only rates set up in DBSi (set up in MNTFNCURR) that are on the FNOEXDD0 file, will be updated with rates. For example, if a new currency and rate were added in CODA, but not in DBSi, this job will not add the new currency or rate to the FNPEXRT0 file. In this scenario, no error will be listed on the error report either because no error was encountered in the retrieval of the currency rates.

5.0 FNJN0409S – Purge Blocked Orders Documents This job purges transactions from the blocked orders file (FNPBLKO0). The prerequisite for purging records is: Part - not on the PCLCODB0 file or on the file and the status is “C”, closed SRVC – not on the WOPHDRS0 file or on the file and the document is 6 months old Rent - Not on the EMLCTRH0 file or on the file but the activity indicator is “N” Others – Document status of “C” or “R” This job purges transactions from the blocked orders file (FNPBLKO0).

This job purges transactions from the blocked orders file (FNPBLKO0). Orders become blocked when a customer fails credit check The prerequisite for purging records is: Part - not on the PCLCODB0 file or on the file and the status is “C” (Closed) SRVC – not on the WOPHDRS0 file or on the file and the document is 6 months old Rent - Not on the EMLCTRH0 file or on the file but the activity indicator is “N” (not active) Others – Document status on FNPBLKO0 file is “C” (Closed) or “R” (Rejected) FNJN0409S purges transactions from the FNPBLKO0 file. Orders are written to this file when the customer fails credit check The prerequisites for purging an order on the blocked orders file are: If the order is a parts order – if it is not on the parts header file and the status is closed If the order is a service work order – if the work order is not on the work order header and it is more than 6 months old If the order is a rent – if it is not on the contract header and it is not active If the status of the order on the blocked order file is C for close or R for reject.

5.0 FNJN0406S – Update Blocked Orders Days Outstanding The job updates the blocked orders file aging buckets with current information from CODA Therefore, when a credit approver views blocked orders, the aging buckets will have been updated from night before (or whenever this job was last run). It is possible that a customer could pass credit check once an order is already on the blocked orders file. The approver could go ahead then and approve an order at this point This job updates the blocked orders file (FNPBLKO0) aging buckets with the most recent information for CODA.

5.0 Maintain Currency Code (MNTFNCURR): MNTFNCURR is a new function to 5.0 A new function, Maintain Currency Code has been added This function is used to list valid currency codes in DBSi.

5.0 Maintain Currency Code (MNTNFCURR): Currencies that should be valid to use in DBSi are entered here The default company currency is indicated with a “Y”. Valid currency codes for DBSi are entered here. The default company currency is indicated with a “Y” in the Default column.

DBSi 5.0 Maintain Currency Code (MNTNFCURR): These currency codes are used to validate currencies entered in DBSi screens These currency codes must also be set up in the financial system Rates are maintained within the financial system A job exists in DBSi on the LSTFNDALY batch job submission screen. When run, it pulls the currency rates from the finance system into DBSi Only the rates listed in the DBSi function MNTFNCURR will be updated with this job. For example, if a new currency was added to the finance system and the batch update was run, it will not add the new currency to DBSi. Nor will it generate an error on the error report.

Exchange Rate Extraction Error Report: An error report is generated from FNJN2560S: The number of exchange rate records sent to CODA (the number in the FNPEXDD0 file) The number of exchange records processed successfully The number of failed exchange rate records The error report generated from this job lists: The number of exchange rate records sent to CODA (same number as in the FNPEXDD0 file) The number of exchange rate records processed successfully The number of failed exchange rate records If a new currency was added to the finance system and not to DBSi, the batch update job is run, it will not add the new currency to DBSi.

MNTFNRMSE- Maintain RMS Entry Codes: There is one additional menu option on the ECMENU: MNTFNRMSE - Maintain RMS Entry Codes One new function has been added to the ECMENU

5.0 MNTFNRMSE – Maintain RMS Entry Codes MNTFNRMSE Maintain RMS Entry Codes is a new function on the ECMENU. This is used to store entry code, company code, and document type code for each dealer code and statement type (i.e. charge vs. credit). The RMS statement load job reads the mailbox file and generates accounting transactions according to these entry codes.

5.0 MNTFNRMSE – Maintain RMS Entry Codes You can specify the external reference to be used to pass the invoice number on the accounting transaction. It is very important that the entry code specified here has not been set up to pass different information in this external reference in function MNTFNDIST. It will override this setup Creates accounting transactions in the RMPTRGL0 file You can also specify the external reference to be used to pass the invoice number on the accounting transaction. Creates accounting transactions in the RMPTRGL0 file. You can specify the external reference number that will include the invoice number to be sent to CODA It is very important that the entry code specified here has not been set up to pass different information in this external reference in function MNTFNDIST. It will override this setup.

5.0 Accounting Menu (ATMENU): MNTFNIFSP – Maintain IFS Parameters have been added to the Accounting Menu. MNTFNIFSP has been added to the Accounting Menu.

5.0 MNTFNIFSP – Maintain IFS Parameters The IFS File Transfer Parameter screen is used for setting up all programs that will interact with CODA. To add an entry type 1 of the top input line and the process name. Otherwise, simply type the number of the function you want to perform on the input line of the program you want to change All programs that will interact with CODA will need to be set up on this screen.

5.0 Maintain IFS Parameters (MNTFNIFSP): For each program that interacts with CODA, a request and response directory ,streamfile and file name must be entered to be used by the XML processing to take place. The set up will be done at conversion time This set up by program, names a request and response streamfile used by XML when sending information back and forth to CODA.

Where to Get More Information
ADMS Website ( DBSi 5.0 Significant Changes Technical  DBSi 5.0 Self Study Finance  DBSi 5.0 Application Service Packs Technical  5.0 Application Service Packs CODA Help from CODA main menu Another idea for a graphic and bullet-point slide

Questions? Here is another idea for placement of an image on a slide

Application Service Packs
March 2008 Finance

List of All Improvements
4. Submit Ledger Update or IFS Cleanup Submit Ledger Update Today the way to initiate the eFinance ledger maintenance functionality is to go into CODA and manually select the ledger maintenance function. These ledgers are used for customer statements and credit checking. They can also take some time to run and should be run after the master update to finance is completed. This makes it difficult to submit them with the proper timing to pick up the invoices and payments from the current day and complete before the next day. FNJN7650S is accessed from the second page of the LSTFNDALY - Submit Daily Jobs IFS Cleanup Purges old CODA temporary transaction files, based on age parameter. FNJN7994S is accessed from the second page of the LSTFNDALY - Submit Daily Jobs Submit Ledger Update When a Dealer is utilizing CODA e-Finance as their Finance Package FNJN7650S batch job can now be scheduled to run on a regular basis (through ROBOT). This batch job will cause maintenance to be run on all Ledgers in CODA e-Finance. (without this enhancement maintenance needed to be initiated manually from CODA e-Finance). IFS Cleanup When a Dealer is utilizing CODA e-Finance as their Finance Package IFS cleanup needs to be run regularly (recommended daily) to clear out the temporary communication transactions between DBSi and CODA e-Finance. If this is not run then eventually the transaction file will fill up and likely cause transaction failures between DBSi and CODA e-Finance.

Application Service Packs
May 2008 Finance

List of All Improvements
Finance Systems Switch to Identify Dealers on Stand-alone Version Today customer maintenance program prevents the use of specific characters that CODA cannot handle. Stand-alone dealer are not using CODA and there is no value added for them to cleanup there customer files to remove these characters not allowed in the customer maintenance program. Therefore, we have provided a new switch to identify that they are a stand-alone dealer. This switch will be maintain by going into the MNTFNDLRP screen found on the FNMENU. There will be a new CF key labeled “F10=Add’l Parms”. When pressing that key the new parameter function will display any finance switch available. At this time the stand-alone switch is the only parameter switch available using this function. Use can change the setting by entering a “C” in the option field and “Y” or “N” on the switch. The default is “N”. The key to this switch is called STANDALONE. When switch is set to “Y” the customer maintenance function will not go through the process of validate the field for invalid characters. If the switch is set to “N” or the switch record is not found, the customer maintenance function will validate that no invalid character have been used and an error message will display if one is found.

DBS to 5.0 Delta Presentation

Similar presentations

Presentation on theme: "DBS to 5.0 Delta Presentation"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

DBS to 5.0 Delta Presentation

Similar presentations

Presentation on theme: "DBS to 5.0 Delta Presentation"— Presentation transcript:

Similar presentations

About project

Feedback