Introducing Format DefinitionPart 2: detailed demo with a real-life sample (CSB43)

Chris ChenRollout Services TeamSmall Business GTM Sales + Indirect Channels Team

Nov, 2007

SAP 2007 / Page 2

At the end of this session, you will be able to:

? Define a bank format file with Format Definition

? Acquire advanced skills of using Format Definition

Objectives

SAP 2007 / Page 3

As an audience of this session, you are supposed to:

? Know SAP Business One

? Know BSP* functions

? Know electronic bank statements processing

? Have reviewed the previous ETS Introducing Format Definition

Prerequisites

*BSP Bank Statement Processing, a new function introduced since 2007 releases.

SAP 2007 / Page 4

1. Define bank format2. References

Agenda

General process of using Format Definition

SAP 2007 / Page 5

Bankstatement

format(.bfp)

1. Studybank file

spec.

2. Createformat

tree withsegments

3. Insertfields

4. Map toB1

5. Verifywith

samples

Step 1. Study bank file specification andsamples

During the customer project, consultants will receive a specificationof certain bank statement format and several sample files, whichrequire to be supported by BSP in SAP Business One.

Examples:

Spanish CSB43 electronic bank statement

?Bank file format specification issued by banks

?Samples electronic bank files (flat text file)

SAP 2007 / Page 6

Format_es-csb43_en.doc

csb_53947.txt

Hint: Try to read the specification while referring to the sample file time by time!

Bank Statement

Header

Trailer

Transaction Group

Transaction

Description

Step 1. Study bank file objective

1. A good understanding of the bank file format

2. Can abstract the flat text data file into a segmented structure(header, transactions, trailer)

Step 2. Create the segment structure offormat tree

1. Create a new bank format and set thefile level attributes like line breaks, fieldseparators.

2. Determine if there will be multiple bankstatements in one bank file. If yes,create a segment group under root ofthe format tree; otherwise, go on withoutactions.

3. Create the next level segments from thebank format definition, e.g.: header,transactions and trailer (the typicalstructure of a bank statement format).

4. Adjust segments: position, names,mandatory, repetitive, etc

SAP 2007 / Page 8

Step 3. Fill the format tree with fields

Field is a minimum meaningful content defined in the format tree, which is eithermapped to B1 database or used to validate other fields in the bank statement.

Standard Field A field existing in bank file, which will be mapped to a single target in B1database

Conditional Field A field existing in bank file, which will be mapped to targets in B1 databasebased on certain conditions

Result Field A result field corresponding to one mapping condition of the Conditional Field.Conditional Field and Result Field are always combined to use.

12340000000025932020

Std. Field: amount sign Con. Field: amount

Res. Field: credit amount

Res. Field: debit amountReference id: sign

Std. Field: account

Step 4. Mapping to B1 database

1. Map segments to database table

2. Map standard/result fields to database fields

3. Mapping method refer Format Definition online help? When source data needs re-format before mapped to target data? Constant, Reference No., System parameter? XSLT functions, Format Definition functions

4. Bank Statement database table refer SDK online help? OBNH Bank Statement header? OBNK Bank statement rows? BNK1 list of invoices\checks details

SAP 2007 / Page 10

Step 5 Verify .bfp with real sample

SAP 2007 / Page 11

? Menu->view->Expand file view

? Data preview

? Import to Business One and use it in BSP

SAP 2007 / Page 12

1. Define bank format2. References

Agenda

References

SAP 2007 / Page 13

? Format Definition landing page:

https://websmp102.sap-ag.de/~sapidb/011000358700000940822007E.htm

? Both sessions of Introducing Format Definition can be found there

? SDK online help bank statement tables schema

?Regular expression tutorial: http://www.regular-expressions.info/tutorial.html

? Appendix glossary

SAP 2007 / Page 14

Appendix Glossary

Term DefinitionBank File Electronics files, which is the data medium used to transfer payment information between Banks

and CompaniesBank Format Definition The specification of bank file issued by banks or institutionsIncoming Bank files Bank Files, which are received from a Bank and need to be interpreted. The containing

documents may need to be posted in the system. Also called Bank StatementOutgoing Bank files Bank Files, which are generated from system data and sent to a BankPayment Engine a tool to import incoming bank files or create outgoing bank filesPayment Engine Add-on One of SAP Business One add-ons, a tool to import incoming bank file or create outgoing bank

file.

It is not included Cash & Bank Add-on.

All plug-ins are included in this add-on.Cash & Bank Add-on One of SAP Business One add-ons, packaged together with Payment Engine Add-on. With Cash

& Bank functionality, several transactions of a bank statement can be processed and reconciledin one step.

Payment Engine Add-on (Inbound) Part of the PE add-on, a tool to import incoming bank files, which starts from the moduleProcess External Bank Statement

All plug-ins for incoming bank file are included in this part.Payment Engine Add-on(Outbound) Part of the PE add-on, a tool to create outgoing bank files, which starts from the module

Payment Wizard and Bill of Exchange Management module in SAP Business One.

All plug-ins for outgoing bank file are included in this part.Bank Statement Processing A module introduced in SAP Business One 2007, which provides automatic payment processing

based on the incoming bank filesFormat Definition A tool that allows the configuration of file format for incoming bank files and outgoing bank files.Plug-in .dll for interpreting incoming bank files and creating outgoing files.Bank Format Project The function is similar to Plug-in, the output of FD in .bfp formatSAP Business One IntegrationTechnology

Runtime platform for XML based message processing

B1i Application Program to carry our certain business logic, e.g. mapping bank file into B1 table, running in B1iplatform written in XML

Conversion First step of importing a bank statement, extracting information from the flat file and converting itto XML according to conversion rule

SAP 2007 / Page 15

Appendix Glossary 2

Term Definition

Mapping Second step of importing a bank statement, transforming the conversion result to BusinessOne bank statement business object (OBNK) according to mapping rule

Mapping Rule The rule used in mapping phase (run time), standard XSLT 1.0 file, generated by FD indesign time

Conversion Rule The rule used in conversion phase (run time), generated by FD in design timeFormat Tree A tree to describe the structure of the bank file in FDRoot The root node of the treeSegment A logical block in the bank file; the lowest-level segment corresponds to a record

Segment Group A segment containing other segments, either segment group or normal segment

Standard Segment A segment containing only fieldsField A meaningful string in the recordStandard Field A field existing in bank file, which will be mapped to a single target in B1 database

Conditional Field A field existing in bank file, which will be mapped to targets in B1 database based oncertain conditions

Result Field A result field corresponding to one mapping condition of the Conditional Field. ConditionalField and Result Field are always combined to use.

Encoding standard for the representation of texts in digital form, e.g. ASCII, UTF-8, UTF-16, etc

Node ID The internal number representing a nodeReference No. A readable character string could be used to identify a node to which it is assigned when

defining a condition or mapping method.Tree Type Type of format tree; Only permitted value here is Bank Statement.

Node Type Type of nodes in format tree.Mandatory New segment is a mandatory part of the higher-level segment

Repetitive Higher-level segment can have multiples of this segment

SAP 2007 / Page 16

Thank you!

SAP 2007 / Page 17

Copyright 2007 SAP AGAll 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 AG. The information contained herein may be changedwithout prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, orother items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden.Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte knnen Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwhnte SAP-Produkte und Servicessowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts und ist fr SAP nicht bindend, einen bestimmtenGeschftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP bernimmt keine Verantwortung fr Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollstndigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewhr, wederausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zwecksowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts.SAP bernimmt keine Haftung fr Schden jeglicher Art, einschlielich und ohne Einschrnkung fr direkte, spezielle, indirekte oder Folgeschden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit.Die gesetzliche Haftung bei Personenschden oder die Produkthaftung bleibt unberhrt. Die Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen berInternetseiten Dritter ab.Alle Rechte vorbehalten.