SAP Netweaver Enterprise Controlling

Symptom

You want to use the current version of the offline data entry with Microsoft Access 97 including all corrections.
Other terms

In the current version of the offline data entry, the following errors are corrected, among other things:
The long text for partners is now displayed in the detailed form of the data entry.The list of values for partners in the detailed form of the data entry was corrected.The ‘Initialize form’ function does not delete any FS items or subitems that are locked for data entry.Build from 07.07.00
In the audit trail for reported financial data, the lengths of the fields for consolidation units and FS items were increased.In the detailed form of the data entry, you can set for each field whether the text and key or only the key are displayed.In the audit trail for reported financial data, the restriction to one consolidation unit was corrected.In the audit trail for reported financial data, you can also use forms for quantities.When you branch from the data entry to the generation, the system displays the ‘Please wait’ window.You can use F8 to navigate from the overview screen of the data entry to the detail screen.In the overview screen, the system displays the row you have selected graphically.The “Entry in group currency” option was removed. For consolidation units, for which the data entry is set in group currency in the master record, the data entry is carried out in group currency automatically.When you enter FS items with a subassignment by partner, the partner unit can now be equal to the consolidation unit. The system then issues a warning message.The validation issues error messages for the comparison operator = although the difference is reported with zero.The currency translation no longer terminates.Build from 11-Jul-00
The runtime for the generation of reported financial data was optimizedThe validation now also permits access to up to 12 prior periods and the prior year. For this purpose, you must also implement the corrections contained in Note 314378. Note that the data model in the offline data entry is different from the data model in the SAP system. In the SAP system, for example, there can be balance carryforward values in period 0. In the offline data entry, period 0 is always empty. Furthermore, the offline data entry recognizes accumulated values only. The validation also allows an absolute specification of a certain period or a certain fiscal year.Build from 23.08.00
Key figures for standardizing entries and standardized financial data are now available again in Interactive Excel.In Interactive Excel, the local currency is determined correctly after a currency change.When data is written from Interactive Excel, the system now runs checks again to ensure that there is no data written to totals items.When data is written from Interactive Excel to an offline data entry based on Microsoft Access 2000, the generation can now also be carried out automatically.When data is written from Interactive Excel, the totals items are now updated.When data is updated from Interactive Excel, the system can now correctly overwrite existing data records.User GADMIN can set how the proposal for the file name is determined during the export of the reported financial data and additional financial data from the parameters. In this process, you can combine the values for view, version, consolidation group, consolidation unit, consolidation chart of accounts fiscal year and period in any sequence. In addition, you can also use fixed character strings and a type indicator, which indicates the type of the data contained in the file (reported financial data, inventory data, supplier data). You can define a maximum length for each part of the file name. If you enter a positive number, the system uses the last n characters. If you enter a negative number, the system uses the first n characters. If you enter zero, the system always uses the whole value. The file name extension “.TXT” is added automatically. The setting in the delivery corresponds to the current logic.Various errors in the usage of Interactive Excel in a Japanese version of Microsoft Access were corrected (1).During the first import of control parameters to a new mdb file, the Microsoft Access system sometimes issued an error message stating that the data was too long for the field. This error was corrected.Build from 25-Sep-00
If you restricted the reported financial data and copied it to the carryforward subitems, the system issued a message stating that there is no generated reported financial data when you called the data entry with the target parameters. This error was corrected.For the export of inventory and supplier data, the values may have been exported too large or too small by a factor of 100. This error was corrected.Build from 10-Oct-00
When you called the audit trail of reported financial data (Data entry – Audit trail – Reported Financial Data), the program terminated if you called the selection list for the data entry layout before specifying a group or a consolidation unit. Instead of terminating, the system now requests you to specify the required parameters.When you entered reported financial data, you were able to delete rows in the overview form. You could no longer enter the relevant FS items in this form, even after regenerating the entry forms. You can now no longer delete rows in the overview form. A menu option for initializing a form is available, as was the case previously. To delete individual FS item values, overwrite the value entered with zero.If you delete all rows in the detail screen of the reported financial data entry, the relevant summarized value in the overview form is now also updated to zero.The system sometimes did not display anything in the detailed form for FS items with a breakdown by subitem. In particular, this problem occurred for large databases or slow computers. This error was corrected.If you added new rows to the detailed form for FS items without a breakdown by subitems, the system did not display these rows after you called the detailed form again. However, the rows were displayed in the audit trail of the reported financial data. Furthermore, they were validated and exported. This error was also corrected.The speed of the reported financial data import was improved.If there is no message in the logon language during the validation, the system now searches for and displays the message in any other language. The system only continues to display ‘Text missing’ if the message is not available in any language.Build from 02-Nov-00
If you created a new row in the detailed form of an FS item with a breakdown by subassignment, the subitem debit/credit sign was only taken into account when you saved the entire row. When you entered the row, the system may still have displayed an incorrect debit/credit sign. The system now immediately takes the subitem debit/credit sign into account when the debit/credit sign is displayed. Previously, the entered value was also saved with the correct debit/credit sign and the debit/credit sign was displayed correctly after you entered it. The error occurred in the display during the data entry only.If you select the “Suppress zeroes” option in an audit trail of the reported financial data with a subassignment, the system displays the totals row for an FS item with values that balance to zero even though the value is zero. This should not happen. Previously, the system only displayed the rows with the individual subassignments. However, these subassignments do not contain any FS item name. This means that the system could not assign the rows.Build from 17-Nov-00
If you used a consolidation version that refers to another structure version, the system could not display the CI or CU (consolidation of investments or consolidation unit) hierarchy for this version.During the import of reported financial data to an FS item with an optional breakdown, the system replaced the initial value with “NNNN” for data records for which the breakdown was not specified. These fields are now empty, as should be the case.During the import of reported financial data to an FS item without a breakdown by unit of measure, the system created duplicate data rows. One row had the imported value, the other row had the value zero. The system now creates a single row.The validation result was not reset during the import of reported financial data and during the generation. As a result, the system could execute the export without a new validation immediately after the import of the potentially incorrect data if the data was validated without errors.Build from 29-Nov-00
When you entered standardizing entries for FS items with a breakdown, the value for the reported financial data was changed in the overview form, and this should not have been the case. However, the reported financial data in the detailed form that are relevant for further processing remained unchanged so that there was no data loss despite the error.The options to create reports using the entered reported financial data and standardizing entries were enhanced. For more information, see Note 362705.Build from 08-Dec-00
The authorizations for consolidation groups were deleted during the import of the control parameters.If you specified maximum sets for partners, the system did not provide partners for the selection on the detail screen of the data entry.In the options, user GADMIN can set up that the system can only close certain data entry layouts if the balance in this layout is zero.It is now possible to add additional program functions (created during modifications) to the menu of the offline data entry. For this purpose, there is a (usually hidden) menu left to the menu option “Info…”. To display the menu items, define texts for the keys YM9 to YM0 in the table ProgrammTexts_DE. YMO is the name of the entire menu, YM1 to YM9 are the names of the suboptions. You must import the control parameters again and change the logon language. The menu options are available to all users. Update functions are defined in the module Z_Customer_Extensions. These functions are executed when you select a menu option.
SAP does not provide any support for modifications of the offline data entry. However, due to the structure of the offline data entry, the customer cannot add menu options. The only purpose of this function is to enable customers (who require modifications) to carry out modifications themselves. However, SAP strongly recommends that you do not carry out modifications in the offline data entry.Build from 27-Dec-00
During the import of reported financial data, the system now checks whether the user also has an authorization for the imported units. If a user tries to import data for a consolidation unit for which he does not have the relevant authorization, the system issues an error message and the data for this company is ignored. If the file contains data for units with and without authorization, the system imports the data for units with authorization only. This check does not occur for users ADMIN and GADMIN since these users have authorizations for all units anyway.In the detailed form of the data entry, if a data record was deleted or if the debit/credit sign was changed by another subitem, all key figures (local currency, quantity, adjustments) are affected. However, the change was only transferred to the overview form for the key figure that was entered in this detailed form. The change is now correctly transferred to the overview form for all key figures. However, the totals items (as it is usually the case for the offline data entry) are not adjusted automatically for system performance reasons.In the detailed form for the entry of standardizing entries, the headings for the columns “Standardized financial data local currency” and “Standardized financial data quantities” were missing.In the overview form for the entry of standardizing entries, the headings of the value columns were not legible in English.In the detailed form for the entry of standardizing entries, the number of decimal places was not adjusted according to the currency in the display column for standardized financial data.If you repeatedly imported control parameters, the CI or CU hierarchy was sometimes displayed incorrectly under Master data – Hierarchy. After you import the control parameters again, the display is correct.When you entered quantities, the system always displayed three decimal places in the overview form. In the overview form, you can generally enter various units of measure with different numbers of decimal places. Access only allows you to define the same number of decimal places for all FS items in the layout. If you enter quantities with different numbers of decimal places in a layout, the highest possible number of decimal places (that is, three decimal places) is deliberately set. However, you often only enter one unit of measure in a layout. The offline data entry was enhanced so the correct number of decimal places is set in the overview form if all units of measure have the same number of decimal places in the layout. The entry was also checked for the correct number of decimal places prior to the enhancement. In the detailed form, the system always used the correct number of decimal places for the display.When you enter values with an optional breakdown, the system now specifies the initialized value for the optional breakdowns by default.Build from 19-Jan-01
In the detailed form, you could change a subitem locked for entry by selecting another subitem from the dropdown list. The system now issues an error message to prevent this.Build from 31-Jan-01
In the overview screen of the data entry, if you displayed comparison values from another period or year and if the control parameters had changed since the comparison values had been entered, the system only displayed FS items that were contained in the new as well as the old control parameters. This was changed: The system now always displays FS items that were active at the time of the generation of the period for which the data entry was made.In the entry, if you specified a comparison period or comparison year for which no data was generated, you were requested to generate data. If you confirmed this request, the system deleted the data of the entry period or entry year. This error was corrected so that comparison values are no longer displayed in this case.If the text file during the import of the reported financial data contained several rows with the same key, the system only updated the last row. The values are now totaled in all rows with the same key. This is not the case if the data was exported with the SAP standard programs from an SAP system with the control parameters supplied for offline data entry. This is only the case if:The data does not come from an SAP system orThe SAP system from which the data was exported contains other user-defined characteristics.
These cases are not supported by SAP. The relevant enhancement was easy to implement and did not have a negative impact on the runtime or stability of the offline data entry. However, SAP cannot guarantee that this function will also be contained in future versions.The offline data entry analyzes a great part of the control parameters during the generation. This includes, for example, the FS items to be entered and the breakdown categories of these FS items, in particular the breakdown type and the default sets. If you import new control parameters, the existing reported financial data is not adjusted. You can currently only carry out this adjustment by exporting the reported financial data and importing it again. This is only possible if the reported financial data can be validated without errors. To simplify this process, the offline data entry now provides a new menu option “Adjust reported data”. In this process, the consolidation units are regenerated using the new control parameters and the values entered on the value items are updated again, including all the checks that also ensure data consistency during the import of reported financial data. This ensures, for example, thatthe system provides the FS items for the data entry for which you want to make entries according to the new control parameters.the system takes changed breakdown categories into account.the system takes changed maximum sets and proposal sets into account.characteristic values are valid according to the changed master data.
This adjustment is also possible if the reported financial data cannot be validated without errors. After the adjustment, you have a list of the data that was inconsistent with regard to the new reported financial data. Use this function with caution.If old reported financial data is no longer consistent with the new control parameters, these parameters are deleted.If you have entered a total value for an FS item with subassignments that is not distributed to the individual subassignments, the value is lost.There is no test run to check the changes and reverse them if necessary. For this reason, SAP strongly recommends that you create a backup of the database.During the start, the offline data entry now checks whether all required external update references exist. If a reference is missing, the system issues a message. The offline data entry then usually no longer works without errors. This check is carried out every 30 days. In rare cases, the Access installation is incorrect or Access libraries are damaged due to system crashes or similar problems. As a result, the offline data entry no longer works. This check is to help you to recognize such cases.Build from 16-Feb-01
In the detailed form, you were able to delete rows with subitems even though the posting lock and data entry lock indicator was set. However, the system now issues an error message when you try to do this.Build from 06-Mar-01
If the alpha conversion for consolidation units is set in the SAP system, the entry with numeric organizational units is converted accordingly, that is, any missing leading zeros are added. The units are still displayed with leading zeros. An automatic conversion for other characteristics with conversion exits (period, FS item, version …) is not provided. This conversion is carried out for consolidation units, consolidation groups and partner units.You can now only enter a valid dimension and version for the global parameters. Previously, there was no check for manual entries.In the initial screen for copying reported financial data, the input field was increased for the consolidation unit so that numeric values with leading zeros are also displayed completely.The initial screen for the audit trail of the reported financial data was optimized so that you no longer need to scroll down to see the options for selecting the subassignments that you want to display.In the overview screen of the data entry, you could still enter values with decimal places for currencies without decimal places. The system now issues an error message to prevents this.If you selected another consolidation unit in the data entry overview screen, this consolidation unit was also transferred to the initial screen. However, the relevant text was not adjusted. The text is now adjusted as well.If you select another consolidation unit (for which no generation has been carried out) in the data entry overview screen, the offline data entry now queries whether the generation is to be carried out. If you do not confirm the query, the system switches to the old consolidation unit again. Otherwise the generation is executed.In the data entry of the inventory data, the lengths of the fields for the inventory-managing consolidation unit and the supplying consolidation unit were increased so that the key is also displayed completely for numeric values with leading zeros. In addition, when you create the first data record, the system now not only displays the key but also the text of the inventory-managing consolidation unit.In the data entry of the supplier data, the lengths of the fields for the inventory-managing consolidation unit and the supplying consolidation unit were increased so that the key is also displayed completely for numeric values with leading zeros.When you used offline data entry in a Unicode system (Japan, China, and so on) in Windows 95, 98 or ME, the system issued various ActiveX error messages. The system issued these error messages since the standard names of the German Microsoft Access version contained German umlauts in some Access objects. These objects were renamed.Build from 23-Mar-01
The setting of the field lengths was improved for the audit trail of the reported financial data. Previously, you could adjust the lengths of the fields for subassignments and value fields by changing the column size in the detailed form of the data entry. As reported by various customers, this is not always immediately obvious. In addition, you may require different field lengths for the data entry than for the report (which should fit on one sheet of paper). The audit trail of the reported financial data now has a new menu option “Layout”. You can use this option to manually adjust the width of the individual fields. If you set the “As with entry” indicator, the system automatically uses the same width as in the detailed form of the entry, as was previously the case. If you deselect the indicator, the system uses the current length of the key and text field or value field for the display. You can now change these as required. Some fields do not have a text field, for example, the field for the acquisition year or the value fields. For these fields, the entry in the text width column is not important.In the validation, calculation inaccuracies can add up to a larger difference. If this difference resulted in a difference in the fifth decimal place, the system issued a message even though the rule was actually fulfilled. Even though you cannot avoid such difficulties entirely, the system is now more tolerant with regard to differences, and the calculation accuracy has been increased due to additional rounding steps. As a result, the calculation inaccuracy should always be below the smallest currency unit or unit of measure and the validation should be processed correctly.During the export of the reported financial data, the system in rare cases issued a message stating that there was an invalid procedure call or invalid argument and the data was not exported. This error was corrected.When data was written from Interactive Excel to the offline data entry, amounts on subitems with posting and entry locks were deleted if amounts were written to the relevant FS item.In the Transfer – Import – Database function, the system did not check the consistency of the imported reported financial data. If you imported reported financial data from a version of the offline data entry for an error correction and if the reported financial data had been saved with errors, the error was transported to the new database, even if the cause of the error was corrected in the new database. This could result in various followup errors (for example, duplicate data records). The Transport – Import – Database function was enhanced so that a technical consistency check is carried out and errors are corrected. This is a technical check; the system does not check whether the data corresponds to Customizing.Build from 20-Apr-01
The “Initialize form” function did not work when you entered standardizing entries.When data was written from Interactive Excel, the system duplicated FS items that had a quantity as a subassignment.You now have more options for copying reported financial data. Furthermore, various errors were corrected. The following section contains information about additional options and errors that were corrected.You can now copy additional financial data.If you copy the balance carryforward subitems only, the system now calculates the total value of the FS item correctly for the overview form of the data entry.If you copied balance carryforward subitems only, the check could state that the value of individual FS items with the “Subitem” subassignment was not equal to the total value of the FS item in the detailed form. This should not have been the case.If you copied balance carryforward subitems only, the system sometimes created duplicate values in the database.If you copied balance carryforward subitems only, the system so far always copied FS items without subitems as well. You can now make a relevant setting.If you entered large values in the overview form or if you returned from a detailed form to the overview form and if the total of the detailed value was large, the system sometimes issued an error message stating that the value has too many decimal places. This should not have been the case.Build from 22-Jun-01
The audit trail for the import of reported financial data was changed so that the individual columns now have more space and are more legible. Note that the audit trail is too wide for one page. For this reason, one row is displayed over two pages.When you imported reported financial data, the system did not display the characteristic texts of the custom characteristics. The system now displays the correct characteristic description. For custom characteristics that are not used, it does not display any column header.A new import function for reported financial data was added. Using the menu option Transfer – Import – Consolidate Data Slices, you can now import reported financial data without deleting existing reported financial data. If you use the menu options Transfer – Import – Reported Financial Data and Transfer – Import – Database, the system deleted existing data. As a result, the database contains the same reported financial data that is contained in the imported file after the import. With the new function, the existing reported financial data remains the same. In addition, the downloaded reported financial data is added. The system does not check whether there are data records with the same key for the downloaded reported financial data. If there are such data records, new (downloaded) values are added to the existing values. As a result, you cannot repeat the function.Build from 12-Jul-01
After you adjusted the reported financial data to new control parameters, the system did not display values without a breakdown. The system now displays these values.After you transferred data from an existing offline data entry, the transferred users could no longer set their global parameters. The system now transfers the global parameters of the users and users can change the parameters as usual.If you maximized the audit trail of the reported financial data import and then closed it, the system incorrectly displayed the program menu. This error was corrected.If you made changes to consolidation units or consolidation groups immediately after the entry date, the system sometimes did not provide any consolidation units for the export or the data entry.During the consolidation of data slices from another database, the system displayed errors in the audit trail. With this error, the system displayed rows in which the value XXXX stood for individual subassignments. Nonetheless, the data was imported correctly. The system no longer displays these messages in the audit trail.In the detail screen of the data entry, the size of the dropdown lists matches the width of the input columns and text columns. However, you may require smaller columns in the form than in the dropdown list due to a limited amount of space. For this reason, there is a new menu option “Field length” under Layout. You can use this option to manually adjust the width of the individual fields. If you select “As with entry”, the system automatically sets the same width as in the used columns, as was previously the case. If you deselect the indicator, the system uses the current length of the key and text field or value field for the display. You can change these as required. Some fields do not have a text field, for example, the field for the acquisition year or the value fields. For these fields, the entry in the text width column is not important. Changes do not take effect until you exit the detailed form and call it again.Build from 21-Aug-01
When data was written from Interactive Excel to the offline data entry, the system issued the error message “Error with database access in query …: Field ‘….’ cannot be a zero length string”. This error was corrected.When data was written from Interactive Excel to the offline data entry using Access, the system sometimes issued an error message stating that the data record was entered several times. The system issued this error message if you entered several values for the same assignment. However, the system did not issue this message if all values were zero when data records were written to the SAP system. The system behavior was adjusted to the standard system and the system does not issue an error message if all values that have been entered with the same key are zero.In Access 2000 you cannot correctly adjust the size of the columns in the dropdown lists. Until Microsoft solves the error, only the entire width of the dropdown list will be set by default in Access 2000. Access optimizes the size of the individual columns. Generally, these sizes do not correspond to the selected column widths, but this ensures that most of the columns are legible.Build from 21-Aug-01
If the database had a long file name (does not correspond to the old MS Dos 8+3 convention for file names), the system issued the error message “The expression you entered has a field, control or property name that Microsoft Access can’t find” when you chose a menu option. This error occurred in Access 97 only.Build from 17-Sep-01
FS items with a breakdown by transaction currency that do not have any additional subassignment triggered error messages in the validation.If you defined a ledger version that differed from the consolidation version, the group currency was not defined or not defined correctly.The definition of a default value for a subassignment did not affect the offline data entry. For this reason, you must implement the corrections contained in Note 435497.When you imported data from an offline data entry of Release 4.0 and 4.5, the import terminated with an error message.Build from 29-Sep-01
When you imported data from an offline data entry of Release 4.0, the reported financial data was not transferred.Build from 02-Oct-01
Validation rules with constants now work.Build from 09-Oct-01
In Interactive Excel, you could not report standardized financial data.If you deactivated the alpha conversion for consolidation units or consolidation items in Customizing of the SAP system, you could not report values for numeric consolidation units or consolidation items in Interactive Excel.Build from 13-Nov-01
In the detailed form of the data entry, you could enter the initial value “” (space) for subassignments, even if the initial value was not allowed for this subassignment according to the breakdown category. This is no longer possible.If you manually entered a partner with a numeric key in the detailed form of the data entry without entering the leading zeros, one of the following errors could occur in the subsequent field:A value that had already been entered was deleted.When you manually entered a value, the system issued a message stating that this value was not in the list of valid values. However, if you opened the list, the value was contained in the list.Build from 12-Dec-01
If you defined validation rules for custom additional fields, the system issued a message stating that the field was too small for the data during the import of the validations.After the build from August 21, 2001, the “Set field lengths” menu option in the detail screen of the data entry and in the reported financial data audit trail no longer works.Build from 07-Jan-02
When you entered inventory data, you could only specify a consolidation unit as a supplier unit for which the user had authorization to enter reported financial data. You can now enter all consolidation units.Build from 19-Feb-02
In the entry screens of the inventory data and supplier data and in the relevant audit trails, the fields for the consolidation units were too short for units with long or numeric keys. The field lengths were increased accordingly.The settings for the color selection in the audit trails were not taken into account for some audit trails (in particular for audit trails for inventory and supplier data) if you did not select a different font at the same time. The color settings are now always taken into account.When you imported control parameters, an error could occur with certain settings in the breakdown categories. You later imported the control parameters again. During the import of the master data for the custom fields, the system then issued an error message stating that the field was too small for the information. You were not able to correct this error even by importing the control parameters again. The original error during the import of the breakdown categories was corrected so that the followup error no longer occurs either.Build from 04-Mar-02
When you imported additional financial data in the offline data entry, several values were imported too small by a factor of 100.Build from 22-Mar-02
The size of the fields for the audit trail of the supplier and inventory data was changed.If you used three or more custom additional fields, the system displayed several FS items twice in the overview screen of the data entry after you imported reported financial data. This error was corrected.If you selected FS items without a breakdown in the overview screen of the dat entry, the debit/credit sign of the entered value was reversed for FS items with negative signs. This error was corrected.Build from 15-Aug-02
When you generated data for several periods in Microsoft Access 2000, the data may not have been completely generated for large data volumes.You can now use the offline data entry with Microsoft Access XP or Microsoft Access 2002. if you use the offline entry in Microsoft Access XP or Microsoft Access 2002, the system still does not support access to the offline data entry in Interactive Excel.Build from 02-Oct-02
When you entered quantities, the system only displayed totals and text items with a breakdown by quantity. However, this is usually not the case. The system now always displays all totals and text items from the layout. However, note that the displayed total is only useful if a standard unit of measure has been assigned to the breakdown category of all lower-level value items. This condition is not checked for performance reasons. The system only displays the unit of measure in the text or totals item if the item is drilled down by this unit of measure as well.When you enter quantities, the system displayed the unit of measure in the internal format in the overview screen of the data entry. In the detail screen of the data entry, the unit of measure is displayed in the external format. The unit of measure is now displayed uniformly in the external format in the data entry.Build from 12-Dec-02
If you delete the last row in the detail screen, that is, if there are no data rows left in the subassignment screen, the system does not update the total of the FS item when you exit the detail screen. The total is only updated again when you access the detail screen again.In the overview screen of the data entry, the system accepts entries as of the fourth position after the decimal point, even if the unit of measure or currency has fewer than four decimal places.When you logged on to the offline data entry from Interactive Excel, the PRACQ characteristic (acquisition period) was missing. Changes to the option “Possible entries for trading partners: Sort by partner name” were effective after you restarted the offline data entry only.Build from 30-Jan-03
When you returned from a detailed form to the overview form, the system issued a message stating that the total of the breakdown does not equal the value of the FS item and that you must maintain the breakdowns.When you imported reported financial, the totals items were not updated. In the user-specific settings, you now have the option to calculate the totals items during the import of reported financial data. This option is deactivated by default. You can activate this option under Tools – Settings – Options. The calculation of totals items is deactivated by default as this function is rather time-consuming; the system can take several minutes or hours to import a large amount of reported financial data. If you do not calculate totals items during the import, the relevant function is available in the overview screen of the data entry. The system always recalculates the value column to be entered only.Build from 28-May-03
If you did not have authorizations for all consolidation units in a consolidation group, you did not have the authorization for the group itself. This caused problems in a currency translation. You had the authorization for a unit, but not for the higher-level group. As a result, you could not select the group in the form. As the group determines the group currency, you could not carry out the currency translation.In the currency translation, the system used the date with the calendar month equal to the period for the current exchange rate. This was incorrect for a non-calendar fiscal year. In the form for the currency translation, an input field that allows you to enter a correct date was added. If the field is empty, the system uses the current period.Build from 11-Jun-03
In the audit trail, the system does not display transaction amounts, even though the “Transaction currency values” field is set in the request screen.Build from 19-Jun-03
In a conversion to Version 2000 or 2002(XP), the database is damaged. After you log on, the system displays numbers instead of descriptions (user ID, password and so on) in the logon window.If you have not defined a printer in Microsoft Windows, the import of reported financial data is stuck.Build from 14-Jul-03
If you set an initial data entry (Customizing -> Options -> Initial entry) for a consolidation unit, the program should ignore the posting lock or the data entry lock. However, despite the initial data entry, the system issues an error message stating that the opening balance &1 may not be changed if you want to delete an entry in a locked subitem.Build from 24-Jul-03
When you enter reported financial data, you post values for subassignments in the “Data entry to items with subassignments” entry screen. If you print the form (”Form -> Print”) and if the current FS item has several subassignments, the system displays entries several times.
Instead, use audit trails for reported financial data in the main program menu. The instruction for the printing the form is removed.Build from 24-Sep-03
In the “Data entry to items with subassignments” entry screen, the system ignores maximum sets for certain FS items. For the following characteristics, the system displays all characteristics defined in the SAP system in the selection list:Transaction currenciesCustom characteristicsBuild from 26-Sep-03
When you upload data from interactive Excel to MS Access, the system does not transfer customer characteristics. Instead, the fields in the Access database are filled with “NNNN”.Build from 30-Sep-03
When you copy reported financial data, the system does not correctly create data in the target area if you copy FS items with subitems.
After you copy the reported financial data with a summarization of the subitem to the carryforward items, the system requests you to create a data entry layout again, which initializes the target data again.
When you copy the balance carryforward items, entries are duplicated. The system creates values for one FS item only. The values in the breakdown are empty.Build from 10-Oct-03
When you upload master data, the system issues the error message “2176: The setting for this property is too long”, if a path to the directory with data is too long.When you upload master data, the system sometimes issues the error message “3163: field length is too small to accept the imported data, please try to import or paste lesser data”.When you copy reported financial data, the system incorrectly copies subitem values. If you select the indicators “Copy with summarization to carryforward item” and “Copy balance carryforward items only”, the system also copies values of the subitems to which no carryforward subitem has been assigned.When you enter reported financial data in FS items with subassignments, the system displays the totals of the values without decimal places.Build from 24-Oct-03
When you enter reported financial data in FS items with subassignments, the currency that is set as the local currency of the entered unit is sometimes not displayed in the F4 help for the transaction currency field.Build from 08-Dec-03
You cannot execute the validation. The system issues the message “No data exists for the report.”. This is a followup error to the corrections from October 10, 2003.Build from 07-Jan-04
In the R/3 system, when you use transaction CX3D1 to download reported financial data in group currency, the reported financial data is not imported correctly to MS Access consolidation units with the “Entry in group currency” indicator. In the data entry layout in MS Access, the system displays the value 0.00, although the file contains GC (group currency) values that do not equal zero.Build from 03-Mar-04
An FS item was defined with a breakdown by subassignment. However, in the “Data entry to items with subassignments” form, the system does not display any characteristic values in the selection list for this subassignment. The system displays their descriptions only. If you select a row in the list, the system does not transfer any value for the characteristic value to the input field.Build from 24-Mar-04
When you import reported financial data from an R/3 system to the Access database, reported financial data in local currency is only partially uploaded and the entries are initialized if reported financial data is imported from consolidation units that are entered in group currency at the same time.
If the data was imported before, the error does not affect the system.Build from 29-Mar-04
When you import reported financial data from an R/3 system to the Access database, the system does not upload all reported financial data.
If the data was imported before, the error does not affect the system.Build from 31-Mar-04
The display factor does not work.Build from 24-May-04
When you copy reported financial data, custom characteristics are truncated to four characters.Build from 10-Jun-04
You make an entry to FS items with subassignments:You want to set a consolidation unit as your partner when you make a posting. However, this is not possible since the consolidation unit is not displayed in the list of the possible values for the partner subassignment.You post to an FS item that has a subitem of breakdown type 2 (Required breakdown: If you do not make an entry, the default value is set). However, the system never proposes the default value. Instead, the field remains empty and you must set the value explicitly, as with breakdown type 3 (Required breakdown: Value entry is forced, default value allowed).Build from 29-Jul-04
When you export data from Interactive Excel to the data entry tool, the system rejects partner units as invalid if they are not attached to the consolidation group hierarchy or consolidation unit hierarchy. Interactive Excel issues an error message stating that the partner unit is invalid.Build from 26-Aug-04
You make an entry to an FS item with partner breakdown. The system does not list all partners in the detail screen, even though you did not define a maximum set. The system only permits consolidation units as partners for which a text was transferred from the R/3 system.Build from 10-Sep-04
When you import control parameters, the system issues the error message “Error no. 13 occurred during file import: Types incompatible” if the master data was exported from a Unicode system.
You must have implemented Note 772413 in the R/3 system. If you use SAP Basis Release 6.20, Basis Support Package 20 must be active.Build from 01-Oct-04
You want to use a validation rule that contains more than 1000 individual rows (see Note 740540 – supplement from September 14, 2004). 2004).
However, the offline data entry cannot process such a large rule.Build from 08-Oct-04
There is an inconsistency in the correction from October 08, 2004. A syntax error has been reported in some validation rules even though the validation rules are correct.Build from 10-Nov-04 (CS2003_46.EXE only)
You have installed Windows XP and Access 2003 on your PC. In the offline data entry, the data lists flicker in some layouts. You cannot make an entry in the call-up point. If you minimize the window and then maximize it again, you can make an entry in this screen.
Due to an inconsistency in MS Access 2003, the error is only eliminated if the system does not highlight any totals items in the data entry layout.The new database is signed digitally. This causes errors if you use the database in Excel 97. To use the database in Excel 97, use the template in file CS97_46.EXE.Build from 15-Dec-04
This is a supplement to the correction from November 10, 2004. The flickering of the layout in Access 2003 has been eliminated. The totals items are highlighted again.
Both files on sapservX (CS97_46.EXE and CS2003_46. EXE) contain databases with the same functions.Build from 15-Jun-05
The dialog box with global parameter is displayed in German even though you logged on in another language. All other texts were translated correctly.If you wanted to display comparison values in the data entry layout, you had to set the period with three digits, for example, 003 for period 3. Otherwise no comparison dates were selected.Build from 23-Jun-05
After you implement Note 852321 in the general download of the control parameters, error 3421 occurred when you imported file AXCHARDF.TXT to the offline data entry.Build from 24-Aug-05
In the data entry audit trail, the system did not display column headers for custom characteristics.The column with the entry lock is added to the consolidation chart of accounts list.Build from 17-Oct-05
In the data entry audit trail without subassignments, displayed FS items were not sorted.You could set parameters of a data entry audit trail without subassignments to inconsistent. You could also select several key figures. Therefore, no data records were selected, although the data records are in the database.Build from 21-Nov-05
The “Export fiscal year” checkbox was displayed again in the form for the export of reported financial data. The indicator enables you to export reported financial data of all periods of the current fiscal year simultaneously to the same file. Therefore, you no longer need to execute an individual export for each period. However, you must always validate the data of all periods before the export.
The option was active in former releases, but was hidden for Release 4.6C.Build from 09-Dec-05
When you copied transaction data using the “Copy with compressing of subitem into carryforward subitems” option, the system transferred values depending on the subitem debit/credit sign with reversed debit/credit sign.Build from 19-Apr-06
If you set the “Comparison values” option when calling the data entry, the values of the comparison period were displayed in the overview window only. In the detail entry for FS items with subassignments, the system displayed data of the current period only.
The function was installed in Version 2003 only.Build from 21-Sep-06
The summarized value of the overview layout is calculated with an incorrect debit/credit sign if you enter values for a subitem in the detailed form.
This is a followup error to the build from April 19, 2006. The error was corrected in Version 2003 only.Build from 31-Oct-06
The debit/credit sign of the subitems is not yet always taken into account correctly. Therefore, the summarized value of an FS item is not always correct.Build from 27-Jun-07
If you download (CX30, CX31) the control parameters in a language for which there are no texts available in the R/3 system, the termination “3315 – Field ‘Hrchy_T.Langu’ cannot be a zero-length string” occurs. Furthermore, you cannot set a version in the global parameters.Build from 21-Nov-07
When you called the offline data entry in MS Access 2007, the system did not display any consolidation menus.
As a workaround, you had to set the SAP_main menu as the default menu in the startup settings for the database.Build from 17-Dec-07
In the audit trail of the reported financial data, values in transaction currency were totaled despite different currency keys.
In the future, the system will total transaction currency values only if the FS item does not have a breakdown by transaction currency.

Build from 03-Jan-08
You imported Support Package 3 for MS Office 2003. The system now displays key fields in drill down lists. If, for example, you open the drill down list “Layout” in the entry, the column with the technical name “Layout” is empty. If you select a row, the name is transferred correctly to the field.
This is due to an error in Office 2003, Support Package 3. The current offline entry version tolerates the error. The DET function is not affected.Build from 20-Jun-08
If you open the detail screen for subassignments in the data entry using comparison values, lines of individual subassignments may be duplicated. After you close and then reopen the screen, the display is correct.Build from 15-May-09
When you import the control parameters in a Unicode system (Japan, China, and so on), the system issues an error message stating that a maximum of eight customer-defined characteristics can be used.Build from 16-Jun-09
The menu statement for compressing the database was removed because it could cause a dump. As of MS Access 2003, only an inactive database can be compressed. If you want to compress the database, open MS Access without the offline data entry and use the menu statement “Tools -> Database Utilities -> Compact and Repair Database/Project” to compress the database.Reason and Prerequisites
for (1): Microsoft Access always uses the local language of the Access installation to assign names to objects created by the system. In the German Access version, there are different objects that contain German umlauts, for example, the table “Einf黦efehler” (”Insertion error”), which is created automatically, or the form elements “Formularfu? (”Form footer”) and “Schaltfl鋍he” (”Button”). If you open an Access database that contains object names with German umlauts in a Japanese Access installation, Access cannot interpret these name (which were assigned by Access) and generates different error messages. These objects have been renamed, deleted or are no longer used.Solution

The corrected version of the offline data entry with Microsoft Access is available on sapservX under /general/R3server/abap/note.0169887/CS97_46.EXE. This file is a self-extracting ZIP archive which contains the latest version of the Access database. Download the file to your PC. Start the file and use it to unpack the new database cs97_46.mdb. Use this database instead of your existing version.
Since the build from November 10, 2004, the installation file /general/R3server/abap/note.0169887/CS2003_46.EXE, which contains a database in the Access 2003 format, is still available on sapservX. The database has been provided with a digital signature.
For more information about how to download a file from sapservX, see Note 96885.
Since the build on 03-Jan-08, the latest version of the offline data entry has been available as an attachment to this note (see “Attachments”).