Disclosure Management Financial Consolidation. Troubleshooting Data Import Interface

Transcription

1 Disclosure Management Financial Consolidation Troubleshooting Data Import Interface

2 TABLE OF CONTENT Introduction... 3 Process... 4 Troubleshooting... 5 Connectivity... 5 Financial Consolidation Financial Consolidation Further analysis Disclosure Management Useful Notes/KBAs

3 Introduction You can run a report bundle task with the express goal of sending Financial Consolidation data to SAP Disclosure Management. In this case, your report bundle contains reports designed specifically to retrieve the same structure expected by the Disclosure Management data cache. In the report bundle task, you map Financial Consolidation metadata to the specified Disclosure Management metadata 3

4 Process The process between FC and DM can be represented as follows: Within each application, you should see this on a successful run. 1. In FC, the log of the task 2. In DM, the import monitor 3. In DM, the Task Engine monitor 4. In DM, the report/chapter 4

5 Troubleshooting Connectivity FC connects to DM via the Disclosure Management Webservices DM has a DataImport.svc (ServiceHost instance hosted by IIS) file which provides all required methods for importing data. NOTE: these Web-services are installed by default when installing the DM application server. No additional steps are needed You can test the WS, by simply browsing the page; you should see this 5

6 If you click on the first URL (next to svrcutil.exe) you will see all available methods: 6

7 For the import process to complete, you also need to have the DM Task Engine Please refer to SAP Disclosure Management Installation / Configuration of Task Engine In FC, the URL is defined (General option > External link) and needs to have this format http(s)://dm_server:port/webservices/publicapi/ Provide a user/password and click Check URL This should be the response. Possible errors -Typo in the URL 7

8 DNS cannot resolve host try it with FQDN or IP address wrong user and/or password user has no rights (profile) in DM Typo no / after port Typo 8

9 You specified the URL as The correct syntax is If you are using HTTPS The file C:\inetpub\wwwroot\SAP\SAP Disclosure Management\Web.config needs to be adjusted for DM Webservices to work correctly <endpoint address="mex" binding="mexhttpbinding" contract="imetadataexchange"></endpoint> <endpoint address="mex" binding="mexhttpsbinding" contract="imetadataexchange"></endpoint> <servicemetadata httpgetenabled="true"></servicemetadata> <servicemetadata httpgetenabled="true" httpsgetenabled="true"></servicemetadata> Web-services can be reached, but main DM application is down Try restarting IIS (on DM server) 9

10 No network A useful tool to troubleshoot is Fiddler ( ) If you run Fiddler and in FC use the Check URL you see the request/response in Fiddler Note: FC actually calls and then the method GetMasteData and the return set are all the reports/chapters this user has access to. This explains why you get a 401 on a user that exists, but has no access to anything 10

11 If you get any other error message like these: 11

12 It indicates some issue with setup/configuration of the Webservices /DM website First, always check by simply browsing to: If you get this type of response, the issue is at IIS level. 12

13 Some possible issues that can cause this type of error: 1) Missing IIS components (e.g. WCF activation) See also Failed to connect to Disclosure Management server 2) The.svc has been turned into an application in IIS as a virtual path to the physical file C:\inetpub\wwwroot\SAP\SAP Disclosure Management\WebServices\PublicAPI\DataImport.svc 13

14 3) Main DM website down 14

15 Financial Consolidation The interface to DM makes use of Report Bundles. There are some restrictions on what can be done in the Bundles when used with DM This is described in section Sending data to SAP Disclosure Management of the SAP BusinessObjects Financial Consolidation User Guide Some setup of the reports can lead to the bundles not running For example, aggregated RUs on the report axis would lead to a required user action during execution (which in a bundle run is not possible) Also, no data being available for the report would lead to an issue 15

16 Also, task related issue (the bundle runs as a Task on FC) can cause the interface to fail E.g. a lock The first 2 tests that always needs to be done: 1. Test the bundle 2. Run the bundle as a print job 16

17 If any of these fail, it is purely a FC issue NOTE: typically, these FC issues would show as this in the log (of the bundle) Nothing is logged in the evaluating formula step, as this is never reached These issues have nothing to do with the DM interface and are pure FC problems (configuration) If the report bundle has no issues, it will run and at the final step map to the 4 identifiers in DM that uniquely define the target - Period - Report - Chapter - Worksheet Note: you can only map to an Excel chapter and if worksheet is not defined, it will map to Sheet1 (Excel default) 17

18 Within the log (either in Logs view, or in tab Log of the task) the process will go through these steps 1. Check connectivity to DM 2. Check the formula syntax 3. Evaluating formula this means, does the mapping defined result in a period/report/chapter/sheet that exists in DM 4. Sending the data (call to API) 1. Connectivity This has already been discussed in first section 18

19 2. Formula syntax You will rarely see an error in the syntax, as in the setup the system already checks the syntax and will not allow a save if there is an error 3. Evaluating formula The log will show 2 steps The first shows the FC report and variables (report name, entity, period) that were used The second shows what the result was of the mapping, and if this could be found in DM The line will always have the 4 identifiers. If one (or more) has no values, it means that the mapping resulted in something that could not be resolved E.g. use [QUARTER] in the mapping but do not define any quarters in the setup If all 4 values are set, but there was still no result, it means that this period/report/chapter does not exist, or user has no access to it, or it is not an Excel (CSV) type. 19

20 The best way to verify, is to run Fiddler. FC will make a call to and then uses the method GetMasteData. DM returns all the periods/reports/chapters this user has access to. If the mapped values are not in this response, FC will error with The formula evaluation [] generates an invalid combination of Disclosure Management master data. 20

21 Financial Consolidation Further analysis In case further analysis is required for example, if you need to see what FC actually sent to DM, you would first need to enable the FC technical logs See: How to implement CtServer log on Financial Consolidation? [VIDEO] Once you have generated the log, you can see the data that FC sent to DM In log :45:38 PID=1664 THD=2348 USR=ADMIN MSG=0 DEBUG reportbundles.task - Generated CSV : "";"";"";"F99 Closing";"";"F00 Opening"; "";"";"";"";"";""; "";"";"";"01/04/15 ";"";"04/01/2015"; "Property, plant and equipment";"";"";3,847,667;"";3,117,584; "Investment property";"";"";103,004;"";103,827; "Goodwill";"";"";1,099,512;"";472,120; "In tangible assets";"";"";1,209,491;"";1,122,942; "Investments accounted for using equity method";"";"";85,788;"";83,188; "Biological assets";"";"";6,428;"";6,753; "Non-current receivables";"";"";295,493;"";367,956; "Deferred tax assets";"";"";243,060;"";3,060; "Other non-current financial assets";"";"";111,032;"";110,440; "Other non-current assets";"";"";"";"";""; "Non-current assets";"";"";7,001,474;"";5,387,871; "Inventories";"";"";347,154;"";29,334; " Trade and other current receivables";"";"";4,994,695;"";4,213,243; "Current tax assets";"";"";3,100;"";""; "Current biological assets";"";"";"";"";""; "Other current financial assets";"";"";71,032;"";74,190; [..] 21

22 Disclosure Management As described in first section, DM will go through 2 steps. The API call and then the Task Engine (import job) First, is to determine which step failed. 1. Check the import monitor The common statuses that will show are: - Import in progress (the import is running) - Import successfully finished - Import finished with errors Always check the log (click on the download link) This Excel file will show the error (if any) 22

23 In case the import could not create the task (so the call to API from FC works ok, but not task could be created), you see this - Could not create import task Note: an import in progress where the end-time remains empty (effectively a hang ) also indicates some problem Check logs in: C:\inetpub\wwwroot\SAP\SAP Disclosure Management\Logs\StagingArea NOTE: these logs cannot be accessed via UI. You need to get them directly of the DM application server, The most common issue is that the Task Engine is not running 2) Check the Task Engine monitor 23

24 Within the Task Monitor, check the Import type Any errors need to be checked in the usual Task Engine logs 24

25 Known limitations Date formats In case you have the following setup FC application server in European date format DM server in US format The FC report (and bundle) uses a date with the format dd/mm/yy 25

26 When executing, date appears as 01/04/15 (April 1 st ) After sending this to DM and opening the chapter, Excel will be ambiguous on this date. If automatically accepted, it will be interpreted as Jan 4, 2015 NOTE: it can also lead to empty cell, if the month > 12 26

27 The solution is to create reports in FC that do not have this date format that may cause ambiguity. Non-Unicode characters (RESOLVED) See: For a full overview of the interface definition, please refer to: +Data+Import#DisclosureManagementintegration-DataImport-2.2.3CSV-Format 27

28 Useful Notes/KBAs TaskEngine error: Login failed for user [username]\[password] - Unable to transfer data from Financial Consolidation to Disclosure Management: DM - Data push from FC to DM issue with multiple chapter DM - Data push from FC does not find report/chapter Failed to connect to Disclosure Management server 28

29 SAP AG. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ( SAP Group ) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.