sap financial services network corporate enablement...

SAP FINANCIAL SERVICES NETWORK CORPORATE ENABLEMENT GUIDE Applies to: SAP Financial Services Network

Summary This document outlines general enablement and troubleshooting steps relevant to the SAP FSN corporate customer, including general troubleshooting in AR/AP processes, the SAP FSN Connector, and basic message throughput. Author: Ross Doherty Company: SAP AG Created on: 01 December 2015

Author Bio

Ross Doherty is the Team and Technical Lead (Onboarding and Delivery) for the SAP Business Network (which includes the SAP Financial Services Network). His primary area of focus is Onboarding (Corporate and Bank Customers) for FSN, and most recently with the delivery and onboarding of the developing SAP Business Network.

1

Table of Contents

Method A: Customer Ticket ............................................................................................................................ 3 Method B: SAP FSN Hotline (24X7 Support) ................................................................................................. 3 Issue: Outbound Payment Instruction in FSN Connector Monitor shows status of “File Created” ................. 3

Symptoms .................................................................................................................................................................... 3 Context......................................................................................................................................................................... 3 Troubleshooting ........................................................................................................................................................... 4 Resolution .................................................................................................................................................................... 4

Issue: FSN Connector Monitor shows status of “File Sent” but I cannot see the payment instruction in the FSN Business Cockpit .................................................................................................................................... 5


Issue: SAP FSN Connector Monitor shows status of “File Sent” but the bank indicates they have not received the payment instruction .................................................................................................................... 6


Issue: I cannot see any messages in the FSN Connector Monitor. ................................................................ 7 Symptoms .................................................................................................................................................................... 7 Context......................................................................................................................................................................... 7 Troubleshooting ........................................................................................................................................................... 8 Resolution .................................................................................................................................................................... 8

Issue: Recently created payment instructions (Payment Runs) are not visible in the FSN Connector Monitor ............................................................................................................................................................ 8


Issue: The “Create FSN Message” report shows an error of “No profile found for Sender / Receiver ID XXX” 9

Symptoms .................................................................................................................................................................... 9 Context....................................................................................................................................................................... 10 Troubleshooting ......................................................................................................................................................... 10 Resolution .................................................................................................................................................................. 10

Issue: Messages created using the “Create FSN Message” report are not being assigned a Message ID . 10 Symptoms .................................................................................................................................................................. 10 Context....................................................................................................................................................................... 11 Troubleshooting ......................................................................................................................................................... 11 Resolution .................................................................................................................................................................. 11

2

Section A: Support The corporate customer can contact SAP FSN Productive Support using the following methods:

Method A: Customer Ticket Component Purpose / When Used

LOD-FSN-AGT For all issues relating to the SAP FSN Connector module.

LOD-FSN-BC For all issues relating to the SAP FSN Business Cockpit.

LOD-FSN-INT For all issues relating to general integration.

Method B: SAP FSN Hotline (24X7 Support) A list of regional support numbers for the SAP FSN Support Hotline is maintained at:

https://websmp208.sap-ag.de/~sapidp/011000358700000143982014E

Section B: Troubleshooting and Resolving Common Issues This section considers and documents basic troubleshooting activities which allow the corporate customer to diagnose and rectify issues quickly.

Issue: Outbound Payment Instruction in SAP FSN Connector Monitor shows status of “File Created”

Symptoms The SAP FSN Connector Monitor (report /BSNAGT/FILES_MONITOR) displays a message status of “Message Created” for a recently created payment instruction.

Context After payment run processing, the SAP FSN Connector will retrieve the outbound message, will apply the SAP FSN message header to the payload (for SAP FSN routing purposes), base64 encode the data, digitally sign and encrypt the data and create a new line item visible in the SAP FSN Connector Monitor.

A successfully processed message will enter two consecutive states; those being:

1. File Created (The message has been written in the monitor) 2. File Sent to SAP FSN (The message header has been successfully added to the message, the

payload has been encoded, signed and encrypted, and the message has been passed to the outbound message queue).

A message which stays in the connector with the status “File Created” indicates that an issue has been encountered during processing in the SAP FSN Connector, and as such, cannot be sent to the outbound message queue.

In order to process a message correctly, the following prerequisites must be configured on the system:

1. A Sender ID for the SAP ERP System. 2. A Receiver ID configured in House Bank Master Data, identifying the recipient of the payment

instruction.

3

https://websmp208.sap-ag.de/%7Esapidp/011000358700000143982014E

3. A valid external message type assigned for the payment instruction (set in “External Format Description” within the Format Information section. This is configurable in FBZP » “Pmnt Methods In Country”, and then validating the payment method.

4. An entry in SPRO » SAP Reference IMG » “Financial Services Network Connector” » “Maintain Secure Store and Forward (SSF) Profile Data” aligning a Receiver ID to a STRUST Keystore for MLS purposes.

Troubleshooting Step 1: Reload the SAP FSN Connector Monitor (that means, move back a screen and restart the connector monitor) and validate if the message status has moved to “File Sent to FSN”.

SAP FSN Connector Monitor also contains error messages related to the message if sending failed. Please review these messages before continuing.

Step 2: If Step 1 was unsuccessful, check the line item in the SAP FSN Connector Monitor, specifically checking if the following parameters are visible (and correct):

• Sender ID (The identifier of the corporate system). This value would have been assigned and configured during the TEST onboarding with SAP FSN.

• Receiver ID (the identifier of the recipient bank). This value would have been assigned and configured during the TEST onboarding with SAP FSN.

• Message Type (Message type of the outbound message). This value would align with the in-scope outbound message type as configured and validated during onboarding.

Resolution

Resolution – Sender ID Missing Step 1: Navigate to an entry in SPRO » SAP Reference IMG » “Financial Services Network Connector” » Maintain Custom Sender IDs. Validate that an appropriate Sender ID is maintained here for a given message type.

Step 2: If the Sender ID is not maintained, please contact your BASIS / Implementation team to correct the problem. If the Sender ID is missing, it is indicative that an unplanned configuration change was carried out to this setting.

Step 3: Reprocess the payment instruction from F110.

Resolution – Receiver ID Missing Step 1: Check with the Accounts Payable Team and validate which vendor was used for this payment instruction. A missing Receiver ID is indicative of a vendor being selected during payment run whose associated House Bank Master data is not configured correctly.

Step 2: After validating the associated House Bank, check the House Bank Master Data in: SPRO » SAP Reference IMG » Financial Accounting (New) » Bank Accounting » Bank Accounts » Define House Banks.

Ensure that the “Customer Number” field contains the relevant Bank Identifier as configured during onboarding.

Step 3: Reprocess the payment instruction from F110.

Resolution – Message Type Missing Step 1: Check with the Accounts Payable team and validate that the correct payment method was used for the associated payment run.

Step 2: If the correct payment method was used for the payment run, validate that the valid (as configured during onboarding) external message type is assigned for the payment method (set in “External Format Description” within the Format Information section. (If the “External Format Description” value is missing, it is indicative that an unplanned configuration change was carried out to this setting).

4

This is configurable in FBZP » “Pmnt Methods In Country”, » (Select the payment method) » Format Settings » Standard Settings.

Step 3: If the entry was missing, update and save the configuration and reprocess the payment instruction from F110.

Issue: FSN Connector Monitor shows status of “File Sent” but I cannot see the payment instruction in the SAP FSN Business Cockpit

Symptoms You observe that a payment instruction is visible in the SAP FSN Connector Monitor. You observe that the status is set to “File Sent”. However, this message is not visible in the SAP FSN Business Cockpit.

Context The status “File Sent” in the SAP FSN Connector Monitor technically means that the message has been fully processed by the SAP FSN Connector (payment medium is encoded, signed and encrypted, an SAP FSN Message Header has been formed, and the SAP Connector has passed the message to the outbound message queue).

In some cases, where the SAP ERP system has lost connectivity to the internet, for example, or when a message queue becomes locked, that message will remain in the queue and as such, will not be received by SAP FSN.

Troubleshooting Step 1: Identify the message which reports a status of “File Sent” in the SAP FSN Connector Monitor. Note the “Creation Date” and “Create Time” values for this message, as illustrated below:

Step 2: Execute transaction SXMB_MONI, and execute “Monitor for Processed XML Messages”.

Step 3: In the “Standard Selection Criteria” specify a date and time range which is in alignment with the “Creation Date” and “Create Time” values captured in Step 1 above.

Step 4: Locate the message in the subsequent result set.

Step 5: Validate the processing status of this message, which is indicated in the form of flags. A chequered flag indicates that the message has left the system correctly. A green flag indicates that the message has not left the message and is still located in the outbound queue.

5

Note: Alternatively, you navigate directly from the SAP FSN Connector Monitor to transaction SXMB_MONI. To do that, choose and highlight the message line item in the monitor and select “Send / Receive Details” as shown below.

Resolution

Resolution – Message is visible in the SXMB_MONI results set – processing flag displayed as chequered Step 1: Contact SAP FSN Support either via customer ticket or using the SAP FSN Support Hotline, having the Message ID, along with the “Creation Date” and “Create Time” values from SAP ERP.

Resolution – Message is visible in the SXMB_MONI results set – processing flag displayed as Green Step 1: Contact your BASIS team and indicate that there is an issue with the outbound message queue – quoting the time and date stamp already captured. The BASIS team will attempt to restart or unlock the queue.

Step 2: In this case, and once the activity is finished, the message should now be visible in the SAP FSN Business Cockpit.

Issue: SAP FSN Connector Monitor shows status of “File Sent” but the bank indicates they have not received the payment instruction

Symptoms You observe that a payment instruction is visible in the SAP FSN Connector Monitor. You observe that the status is set to “File Sent”. However, the bank indicates that they have not received the payment instruction.

Context The status “File Sent” in the SAP FSN Connector Monitor technically means that the message has been fully processed by the SAP FSN Connector (payment medium is encoded, signed and encrypted, an SAP FSN message header has been formed, and the SAP FSN Connector has passed the message to the outbound message queue).

In some cases, where the SAP ERP system has lost connectivity to the internet, for example, or when a message queue becomes locked, that message will remain in the queue and as such, will not be received by SAP FSN, and subsequently, the bank partner.

Troubleshooting Step 1: Identify the message which reports a status of “File Sent” in the SAP FSN Connector Monitor. Note the “Creation Date” and “Create Time” values for this message, as illustrated below:

6

Step 2: Execute transaction SXMB_MONI, and execute “Monitor for Processed XML Messages”.

Step 3: In the “Standard Selection Criteria” specify a date and time range which is in alignment with the “Creation Date” and “Create Time” values captured in Step 1 above.

Step 4: Locate the message in the subsequent result set.

Step 5: Validate the processing status of this message, which is indicated in the form of flags. A chequered flag indicates that the message has left the system correctly. A green flag indicates that the message has not left the message and is still located in the outbound queue.

Resolution

Resolution – Message is visible in the SXMB_MONI results set – processing flag displayed as chequered Step 1: Contact SAP FSN Support either via customer ticket or using the SAP FSN Support Hotline, having the Message ID, along with the “Creation Date” and “Create Time” values from ERP.

Resolution – Message is visible in the SXMB_MONI results set – processing flag displayed as Green Step 1: Contact your BASIS team and indicate that there is an issue with the outbound message queue – quoting the time and date stamp already captured. The BASIS team will attempt to restart or unlock the queue.

Step 2: In this case, and once the activity is finished, the message should now be sent to SAP FSN.

Step 3: Contact SAP FSN Support either via customer Ticket or using the SAP FSN Support Hotline to confirm with the SAP FSN Team who can trace the message and validate that the payload has been received correctly in this instance.

Issue: I cannot see any messages in the SAP FSN Connector Monitor.

Symptoms Upon execution of the “FSN Connector Monitor” from either your SAP Easy Access menu or directly via the /BSNAGT/FILES_MONITOR report, you will be presented with a set of filter parameters, allowing you to refine the presented result set of inbound / outbound processed messages.

After entering search criteria and executing the report, no messages are visible.

Context Generally, the root cause of this issue relates to the entering of incorrectly formed or illogical search criteria before the report is executed. The search criteria fields are illustrated below:

Common mistakes during the entering of search criteria would be:

7

• Entering a TemSe Object name which is either misspelt, or does not exist on the system. • Attempting to filter based on a message type which is either misspelt or not considered in the

corporate message exchange with the bank partner(s). • Entering a File Name in the File System which is either incorrectly spelt, or does not exist on the file

system. • Choosing a File Direction (available options would be {IN, OUT}, which is incorrect for the scenario.

Note that “IN” relates to those messages which are inbound to the Corporate, such as bank statements and statuses. “OUT” relates to those messages which are sent to the bank, that means, payment instructions, and so forth.

• Entering a Receiver ID / Sender ID which is either misspelt or which is not configured on the SAP ERP system.

• Entering a User Name which is misspelt or does not exist on the system. • Entering a creation date range which either predates the installation of the SAP FSN Connector on

the system, or is set to a range which refers to a date in the future.

Troubleshooting Step 1: Validate that the search criteria parameters which have been entered are correct and reflective.

Step 2: If the search criteria parameters are validates as being correct, ensure that you are viewing the correct tab after executing the search. One tab exists for all outbound messages (Payment instructions etc), and one tab exists for all inbound messages (Bank Statements, Bank Statuses), as shown below:

Resolution

Resolution - All troubleshooting steps have been completed Step 1: Leave all SAP FSN Connector Monitor screens and return to the SAP Easy Access Menu. Execute the report again.

Issue: Recently created payment instructions (Payment Runs) are not visible in the SAP FSN Connector Monitor

Symptoms After payment run, the recently created payment instruction is not visible in the SAP FSN Connector Monitor after you input valid search filter criteria.

Context During onboarding, a set of payment methods (per company code / country) are defined and often created, and those payment methods, once considered in a payment run, will be associated with the SAP FSN Connector, and as such, will be output via the SAP FSN Connector.

During Payment Proposal and Payment Run, a payment method or range of payment methods are specified; those payment methods associated to the SAP FSN connector will output the payment medium normally (that means, to the SAP ERP file system) and then the payment medium / file is passed to the SAP FSN Connector for processing.

8

As such, every payment, where payment methods aligned with the SAP FSN Connector are included, will result in an entry in the SAP FSN Connector Monitor (unless some exceptions or errors are found in the Payment Run log).

Generally, failure to create the payment medium (and the resultant entry in the FSN Connector Monitor) is generally down to incorrect parameters being set during Payment Run (such as the wrong payment method being chosen), which will result in errors in the Payment Run Log.

Alternatively, this issue can also manifest if the checkbox “Create Payment Medium” is left unchecked during payment run.

Troubleshooting Step 1: Validate that the payment methods used in the previous payment run are those which are aligned with the SAP FSN Connector. This can be validated in transaction F110, after inputting the correct Payment Run ID and Date combination.

Step 2: If the payment methods validated in Step 1 are correct, validate that the Payment Run was fully executed (that means, that a payment medium was created).

Step 3: If the payment medium was validated to have been created in Step 2, validate that no errors have been experienced in the Payment Run Log. Any errors observed here which prevent the full creation of the payment medium will cause the message not to appear in the SAP FSN Connector Monitor.

Resolution

Resolution – Payment Run Log shows errors Step 1: Note the payment run log errors and pass this information to your FI Team.

Resolution – Payment Medium evaluated not to have been created Step 1: Reprint the payment run, ensuring that “Create Payment Medium” is checked.

Issue: The “Create FSN Message” report shows an error of “No profile found for Sender / Receiver ID XXX”

Symptoms During the creation of a message, using the “Create FSN Message” report, an error is thrown after the parameters have been entered, and the report executed, indicating “No profile found for Sender/Receiver ID….”.

This is illustrated below:

9

Context In order to process a message correctly using this report, a profile needs to be established and correctly configured for the following: {Message Type + Receiver ID + DN String + Security Operations instructions}.

Troubleshooting Step 1: Note the parameters which were entered which caused the report to throw an error.

Step 2: Navigate to SPRO » SAP Reference IMG » Financial Services Network Connector » Maintain Secure Store and Forward (SSF) Profile Data. Validate that an appropriate profile exists for the parameters captured in Step 1 above.

Resolution Resolution – Having validated that a profile exists in “Maintain Secure Store and Forward (SSF) Profile Data:

Step 1: Reprocess the message again using the “Create FSN Message” report.

Issue: Messages created using the “Create FSN Message” report are not being assigned a Message ID

Symptoms You notice that the “Create FSN Message” report appears to have created the SAP FSN message without issue. You check the message in the SAP FSN Connector Monitor and you notice that no Message ID has been assigned. This is illustrated below:

10

Context When a payment instruction / batch is generated using the standard method (PMW / Classic Report) and processed in F110, the FI System will assign a message ID to the instruction / batch. This message ID will be visible in the Payment Run Log, and will be used by the SAP FSN Connector Monitor in identifying the message. Subsequently, the SAP FSN Connector will also use this identifier to form the <MessageID> in the SAP FSN message header.

However, when the “Create FSN Message” is used, an alternative source for Message IDs will be used.

This alternative source for message ID would be configured during onboarding, and each message which is created using the “Create FSN Message” will use a unique message ID (incremented every time).

The Message ID is an important facet in the SAP FSN message lifecycle and should be unique for every message exchange within a Corporate «» Bank scenario.

Troubleshooting Step 1: Navigate to SPRO » SAP Reference IMG » Financial Services Network Connector » Maintain Number Range for Message ID.

Step 2: Click on the “Intervals” button and observe that an interval should be persisted therein (illustrated below):

Should no interval exist on the system; this is indicative that a configuration change may have happened. Proceed to resolution below.

Resolution

Resolution – Numeric Range Interval does not exist on system: Step 1: Create a new interval on the system as shown above with the following parameters:

No.: N2

From Number: “0000000001”

To Number: “9999999999”

Step 2: Reprocess the message using the “Create FSN Message” report, observing that a Message ID is correctly applied in this instance.

11

Related Content SAP FSN Product Documentation

SAP FSN Support Information

SAP FSN – “What’s New”

12

https://proddps.hana.ondemand.com/dps/d/preview/08ebbd5943bc44b7af2d22b218ceea14/1/en-US/10ec9fd7693746dbbf15cc41da936e57.html

https://proddps.hana.ondemand.com/dps/d/preview/bf9ff537695d43c9b61619c458b57dda/2015.10https:/proddps.hana.ondemand.com/dps/d/preview/bf9ff537695d43c9b61619c458b57dda/2015.10/en-US/frameset.html?fb76d5f38c06404492508dfb4714f73f.html/en-US/frameset.html?fb76d5f38c06404492508dfb4714f73f.html

https://proddps.hana.ondemand.com/dps/d/preview/bf9ff537695d43c9b61619c458b57dda/2015.10/en-US/frameset.html?9077ba3e803e4f098fe6d37081f1fa7d.html

Copyright © 2015 SAP SE or an SAP SE affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE and its affiliated companies (“SAP SE Group”) for informational purposes only, without representation or warranty of any kind, and SAP SE Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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. SAP SE and other SAP SE products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

13

sap financial services network corporate enablement...

Documents