SBIS SAPPER - integration module for SAP — различия между версиями
Строка 13: | Строка 13: | ||
* create SAP electronic documents using SBIS incoming electronic documents. | * create SAP electronic documents using SBIS incoming electronic documents. | ||
− | = | + | = Sending a document = |
+ | |||
+ | == Sending a document via SAPPER interface== | ||
SBIS SAPPER contains ABAP program \SBIS\SAPPER with the help of which user can work with electronic documents in SAP interface. | SBIS SAPPER contains ABAP program \SBIS\SAPPER with the help of which user can work with electronic documents in SAP interface. |
Версия 16:55, 12 декабря 2016
Содержание
General information
SBIS SAPPER is an integration module for SAP for the exchange of legal electronic documents via SBIS system.
SBIS SAPPER can:
- send any XML electronic documents package from SAP;
- check the status of sent electronic documents;
- review and process incoming electronic documents;
- create SAP electronic documents using SBIS incoming electronic documents.
Sending a document
Sending a document via SAPPER interface
SBIS SAPPER contains ABAP program \SBIS\SAPPER with the help of which user can work with electronic documents in SAP interface.
User scenario (ideally, only two clicks):
- start the program
- select the document package type
- check the document packages to send
- click “Send”
Optional settings:
- document packages alternatives and their contents;
- document appearance (visualization);
- data acquisition method: printing program/ XML from Invoice Journal Russia / BAPI;
- shipping method: SDK, SBIS Connect, API, solution architecture allows sending via any EDM operator.
How it works:
You may set up the whole SBIS SAPPER menu without a change in ABAP code. Sales menu items describe options of document packages to send. Each item in this section describes the contents of a specific document package type. When user selects a menu item in Sales section, SBIS SAPPER receives a document list request from module settings and runs it. The request is written in a proper way to collect the relevant documents. As a result, user will see a list of packaged documents in the screen (for example, TORG-12 and tax invoice).
When you open a document package card (double click) or click to send, SBIS SAPPER calls a usual print program for each document package in electronic document generation mode.
Further, on the basis of the printing programs calculated data and mapping tables, it generates XML files of required formats. After the document package generation, it connects to SBIS COM object and sends and signs the documents (there are signature and no signature options).
This method works at any SAP with all types of documents and reports (does not depend on Invoice Journal functionality from Russian Add-on).
Sending via SBIS interface
If you use confirmations in SBIS (for example, incoming documents), then it will be more convenient for you to upload SAP documents from SBIS interface. The same for sending documents. It’s enough to click “upload to SAP” (or from SAP) when you work in SBIS, then the situation goes the same way as if you were working in SAP.
How it works:
Your browser connects to SBIS Plugin installed on user's computer via WebSocket. SBIS Plugin converts the request into appropriate RFC formats and calls them.
Sending via Invoice Journal (Russia)
/SBIS/EJOURNAL package as a part of SBIS SAPPER is designed to work with Invoice Journal of SAP Russian Add-on. Additionally, it provides with a program that allows sending of document packages, generated of standard journal entries, in three clicks. Specially made for standard functionality followers. This functionality is limited by options and defaults of Invoice Journal.
FAQ
Question: Some employees don’t have to see all documents of a special type, so is it possible to hide the documents out of his responsibility area?
Answer: Yes, possible, a list of documents is built with a simple request from settings table, you can modify it due to your specifications.