SQL2APE is a simple command line tool written in C# to extract data from a SQL database and transfer them to AP Essentials via their REST API. It is configurable using a JSON config file (empty template can be found in sql2ape_config.json).

SQL2APE is a simple command line tool written in C# to extract data from a SQL database and transfer them to AP Essentials via their REST API. It is configurable using a JSON config file (empty template can be found in sql2ape_config.json).

 

Configuration

Configuration is done via a JSON file which requires the following values:

• ApiKey : This holds the AP Essentials API Key for your tenant
• ServiceUri : String, the URI to the AP Essentials Service you wish to use, e.g. "https://readsoftdemo.readsoftonline.com"
• Username : String, the username of an admin user who has the necesary privileges to edit masterdata
• Password : String, the password for said admin user
• SqlBuyersQuery : String, the SQL query to retrieve all buyers you wish to upload/update. Can be left empty if masterdata is on the customer level instead of buyer level. The column names need to follow this template:
  • Name : Required, String, the unique name of the buyer
  • ExternalId : Required, String, the unique ID of the buyer (Name and ExternalId are independantly unique)
  • VatNumber : Optional, String, the VAT number, e.g. "ATU123456789"
  • AddressCountry : Optional, String, the country code, e.g. "AT"
  • AddressStreetAddress : Optional, String, the street address including house number, e.g. "Example Street 10"
  • AddressPostcode : Optional, String, the postal code, e.g. "1234"
  • AddressCity : Optional, String, The name of the city, e.g. "Vienna"
  • PhoneNumber : Optional, String, A phone number
  • Fax : Optional, String, A fax number
  • AlternativeName1 : Optional, String, an alternative name as it might be printed on an invoice by some suppliers, e.g. if "Name" is "Some Company GmbH" then ""AlternativeName1" could be "Some Company Ges.m.b.H" if some suppliers tend to write the name like that
  • AlternativeName2 : Optional, String
  • AlternativeName3 : Optional, String
  • OrganizationNumber : Optional, String
• SqlSuppliersQuery : String, the SQL query to retrieve all suppliers you wish to upload/update. The column names need to follow this template:
  • BuyerId : String, only required if masterdata is on the buyer level. The ExternalID of a buyer the given suppliers should be assigned to
  • SupplierNumber : Required, String, the unique ID of the supplier. If masterdata is on buyer level then the ID must only be unique within each buyer
  • Name : Required, String, the name of the supplier (not unique)
  • Description : Optional, String, a description for the supplier
  • TaxRegistrationNumber : Optional, String, the VAT number
  • OrganizationNunmber : Optional, String, (the typo is supposed to be like that)
  • Street : Optional, String
  • PostalCode : Optional, String
  • City : Optional, String
  • CountryName : Optional, String
  • PaymentTerm : Optional, String
  • PaymentMethod : Optional, String
  • CurrencyCode : Optional, String, the currency code this supplier uses, e.g. "EUR"
  • Blocked : Optional, Bool, whether this supplier should be blocked or not
  • TelephoneNumber : Optional, String
  • FaxNumber : Optional, String
  • TaxCode : Optional, String
• MaxThreads : Integer, how many threads should be used to run API requests simultaneously. Generally this should be maximum the number of threads the CPU provides
• LogFile : String, the path to the log file. The logfiles are daily rollover, the current date will be appended to the end of the name, e.g. "sql2ape-[yyyyMMdd].log"
• LogMaxFiles : Integer, how many log files should be kept. Once that number of log files is reached all files that are older than the newest X files will be deleted

Syncronizing of the Master data ( Buyer and Supplier only)  without the customer having to configure their system for this

For a seemless Masterdata import from any Customer Database System to the AP Essentials Cloud. It is not necessary for the customer to be responsible for generating the master data XML. Also, the customer's system does not have to have a REST API functionality.

 

Our Tool queries the Database of the Customer and convert this Data for an seemless AP Essentials upload.