SBIS SAPPER overview
Overview
SBIS SAPPER - is SAP integration module exchange system of legally relevant electronic documents of SBIS.
Using SBIS SAPPER, you can:
- send any packages from SAP any electronic documents in xml format in several ways
- take any xml documents SAP (SAP to create a document on data from XML) in several ways
- organize local archive electronic documents in SAP or on a separate local service
- SBIS use opportunities in SAP:
- internal document - approval of documents prior to loading / dispatch
- mapping provider nomenclature
- EGAIS - work in accordance with alcohol legislation
Sending Documents
SBIS SAPPER can generate and send electronic documents in several ways:
Sending via the SAP interface
As part of SBIS SAPPER have a special program (/ SBIS / SEND), with which the user interface of the SAP may send any electronic documents. user scenarios (optimally after the launch of two mouse clicks): :
- call program
- select the type of documents (this item may be deleted)
- We tick packages of documents that we want to send
- press the send button
How it works:
SBIS SAPPER designed so that the user did it (the code) a minimum of changes. All adaptation to the customer is done by editing the settings of the table.
When a user runs a program to send (/ SBIS / SEND), the module depends on the type of package looks in the table the query text settings to build a list of documents and executes it. The result is a user sees on the screen.
After the user has said the package of documents that it wants to send, / SBIS / SEND looking table settings, which print program is used to print the document and causes it, but instead of the output to the printer, it all calculated print program value is saved in xml universal file format. When / SBIS / SEND received xml files of a package of documents, it converts side operator universal xml files in the current FTS formats, signs and sends them.
Using the universal format xml allows electronic documents of any type from any SAP documents, and not to do any changes in SAP by changing the format of the Federal Tax Service (two years there were already 4).
Using the program allows you to print an electronic document with all the features of the client, such a method is used in a standard EDI module from SAP CIS, for the only difference being that in xml conversion is not rigid, and customizable settings through the table.
In the simplest case refinement limited to adding to the printing program (or a copy) method call SBIS SAPPER which completes printing program after the formation of the electronic document.
Example SBIS SAPPER call for the formation of an electronic document. This code should be added immediately before the challenge form.
DATA lv_not_print TYPE c VALUE 'X'.
DATA cl_mapping TYPE REF TO /sbis/cl_mapping.
CREATE OBJECT cl_mapping.
CALL METHOD cl_mapping->calc_doc
IMPORTING
ev_not_print = lv_not_print.
IF lv_not_print = 'X'.
EXIT.
ENDIF.With the integration module supplied examples of standard print programs are added to the call SBIS SAPPER.
In some cases this may not be enough.
Generation of the electronic document used as a data value calculated by the print program. Sometimes the name of the contractor, his TIN and CRR are displayed in printed form a single line and is usually in the print program, they are stored in a single variable, and to generate an electronic document they need separately. Therefore, for each print program are analyzed, what data it is not enough, then the appropriate changes are made to the text of the program.
For signing and sending can be optionally used with either the SDK SBIS (direct shipping) or SBIS Connect (exchange through the catalog).
Sending a SBIS interface
If you prefer to work from SBIS interface (this is normal). You may be in SBIS click on the button to download from SAP, and then everything will be exactly the same as if you send documents from SAP, it will be only a little more beautiful and maybe a little bit faster.
How it works:
For convenient operation in SBIS office on the user's computer must be set SBIS the Plugin, which is responsible for a comfortable user experience: the issuance of the notification pop-up, signing documents, work with scanners and other devices, as well as interaction with the information systems directly from the interface SBIS personal account.
So, when the user clicks the "Upload from SAP", the browser through SBIS Plugin requests in the SAP list of specific types of documents.
SBIS Plugin incorporates standard SAP Net connector 3, by which, via the RFC interface it receives information in the same way as / SBIS / SEND.
Such a decision can not be used to access SAP from the Internet, access is only possible from the user's browser on his initiative and limited rights within SAP.
Sending through standard SAP CIS EDI interface module (not recommended)
As part of SBIS SAPPER have EJOURNAL package that implements a job (including BADI) with standard electronic journals SAP documents.
In addition to this it offers a program that allows three clicks to send packages of documents generated from recordings of standard magazines. It made specifically for the standard functionality of adherents.
The functional capabilities of this method is limited to the standard module and all its disadvantages .
How it works: The SBIS SAPPER implemented all BADI SAP CIS and a little larger than a standard module of electronic documents. Как это работает: В SBIS SAPPER реализованы все BADI стандартного модуля электронных документов SAP CIS и немного больше.
FAQ
Q: We have an employee should not see all documents of a certain type, whether the display of documents is possible only by its area of responsibility?
Answer: Yes, perhaps, the list of documents before sending constructed using a simple query of the table settings, it can be changed based on your specifics.
Loading documents
Loading via the SAP interface
As part of SBIS SAPPER have a special program (/ SBIS / INBOX), with which the user interface in SAP can view, process and upload incoming documents.
user scenarios:
- call program
- the software automatically generates a notification of receipt of documents available to the user (subject to availability of EDS without it is not possible to view them)
- the user can see a list of incoming documents available to him (SBIS limit set in the private office)
- any document the user can see them perform on the available actions (the default is to accept / reject)
- download in SAP (maybe it will take to match the nomenclature)
How it works:
When a user runs a program to send (/ SBIS / INBOX), it is authorized through the SDK in SBIS private office, requests a list of incoming documents (the same can be seen in the section Incoming personal account). Then, for each incoming document whether it is checked loaded into SAP and compares the amount of documents, and this information is added to the list. The result is a user sees on the screen.
When you click upload to SAP, the user if there are several options for loading the XML file will be asked exactly where he wants to upload a file, after converted into an XML file which XML universal format, which is using the setting of the table is serialized into a structure that is passed to the appropriate SAP BAPI. At the time of loading on request in the SAP tables can be provided with information about the signatory, XML original documents, PDF representation of the document with the stamp of the EDC.
System Architecture
This section shows a diagram of the interaction of the main components. The chart reflects the key program components and logic subsystem solutions.
SBIS SAPPER The software component is designed to integrate SAP ERP accounting system SBIS. MI has several user interfaces:
- SBIS GUI - set of screens performed in the SAP interface for user interaction.
- Data interface - a set of classes implementing the interface receiving the list, upload and download documents from different data sources, such a program may be printing, a BAPI, magazines.
- Exchange interface - a set of classes implementing data exchange interface with SBIS, the default is SBIS SDK, in some cases, can be used to communicate via the catalog.
- User settings - base module is a table setting is responsible for the exchange of parameters, mapping fields. Due to her decision derives its flexibility.
SBIS Plugin Object to provide functional personal SBIS office (for the generation of standardized electronic digital signature, which is based on the PKCS # 7 format output informational notifications for incoming documents / tasks at the manual loading and unloading operations documents). The object is installed on user workstations. Integration with the SAP system implemented by SAP NET Connector 3, part of the core components of the product.
It requires the operating system Windows XP SP3 or higher, as well as the NET Framework 2.0 or 4.0. Does not support NET Framework 4.0 Client profile.
SBIS SDK Object is intended to communicate with the API SBIS, and generating standardized digital signature, which is based on a PKCS # 7 format. The object is installed on user workstations. Integration with the SAP system is made via OLE2 technology. For more information about the SDK SBIS.
SBIS Connect Windows application to integrate SBIS users with information systems via catalog. For more information about the SBIS Connect
