SBIS SAPPER - Installation

Provide with questionnaire

Company information

Company name: Paradigma, ltd

Company INN/KPP: 7604200936 / 760101001

SAP system: SAP ERP 6.0 EHP7

SAP BASIS version: 7.40

Send documents

Either print programmes or XML files of standard electronic document journals can be used to generate XML files. This instruction is about the first variant, the other one isn’t under consideration, as it’s a fairly rare case and does not require any settings. First of all we need to decide how many variants of document packages you need to upload from SAP and what print programme is used. For each package of documents you should provide the samples of printed forms and the following information to Tensor Company (here’s an example):

• Package name: Finished product realization
• Dispatch mode: multiple launch (>50) or item-by-item
• Confirmation is required before shipment: Yes / no
• Document package contents:
  • Packing list
    • File name with a printed form example: Example_TORG12.pdf
    • Print programme name: ZJ_3RV_TORG12_BIL
    • Input parameter values to print an example: (for J programs this section can be omitted)
      • Programme entry point: ENTRY
      • nast-kappl: V2
      • nast-kschl: LD00
      • nast-parvw: WE
      • nast-objtype: LIKP
      • tnapr-sform: J_3RV_T12_PDF
  • Tax Invoice
    • File name with a printed form example: Example_Invoice.pdf
    • Print programme name: ZJ_3RV_INV_A
    • Input parameter values to print: (for J programs this section can be omitted)
      • Programme entry point: ENTRY
      • nast-kappl: V3
      • nast-kschl: RD00
      • nast-parvw: RE
      • nast-objtype: VBRK
      • tnapr-sform: J_3RVINVOICE

Examples of printed forms must be created from the same mandant as the SBIS SAPPER set up.

Create SAP-documents

To create documents in your SAP system you should decide how many variants of document types you want to create and what way is used (BAPI, batch input). If you use z-fields in your documents you should provide the list of z-fields in the following format : 'structure-zfield'. You should add z-fields to BAPI structures in case of BAPI.

Example:

• Purchase order. Loading method - 'BAPI_PO_CREATE1'. Document source: TORG-12 xml document.
  • ekko-zcontract - contract number
  • bapimepoheader-zcontract - contract number
  • ekpo-zсontainer - container number
  • bapimepoitem-zсontainer - container number
  • ekkn-zfipos - Commitment Item
  • bapimepoaccount-zfipos - Commitment Item
• Goods receipt. Loading method - batch input, transaction code - MB01. Document source: TORG-12 xml document.
  • mkpf-zcontract - contract number
  • bapi2017_gm_head_01-zcontract - contract number
  • mseg-zсontainer - container number
  • bapi2017_gm_item_create-zсontainer - container number

Budget preparation

We create a preliminary budget according to the questionnaire answers. If it’s ok with the customer, than we sign a contract. After that our client gets a SBIS SAPPER integration module.

Install SBIS SAPPER module

Executive: Customer

Frequency: for BASIS 7.40 and up - once

Required rights to SAP: transport requests import (SE01, STMS).

The module is provided as several transport requests, the final list of transport requests is determined according to the client’s needs and the SAP version. Transport requests are imported into SAP by the Customer’s specialists and done in a specific order. The full SBIS SAPPER transport requests list is presented in order of import:

1. /SBIS/CORE - module basic core
2. /SBIS/CORE700 - implementation features for BASIS 7.00
3. /SBIS/CORE740 - implementation features for BASIS 7.40
4. /SBIS/GUI - graphic user interface of the module
5. /SBIS/EJOURNAL – functionality responsible for SAP CIS electronic documents standard journals work
6. /SBIS/ARCHIVE_EJOURNAL - functionality responsible for SAP CIS electronic documents standard journals work
7. ZSBIS- transactions for quick access from the menu.

SBIS SAPPER efficiency was checked for SAP BASIS 7.02 and 7.40. We are ready to discuss and test the compatibility with other versions of SAP, including earlier versions of SAP.

Migrated data filling check

Executive: Customer or Tensor

Frequency: once

Required rights to SAP: data review (SE16).

Check tables completion /SBIS/XSLT, /SBIS/STATUS. The tables should not be empty.

Add electronic document formation to print mode

Executive: Customer or Tensor

Frequency: once

Required rights to SAP: ABAP developer rights.

SBIS SAPPER module uses the print programmes to generate XML documents. This technique allows avoiding duplication of document formation algorithm.

Please make a copy of the print programmes specified in the questionnaire. Recommended template name of the programme copy is [ZSBIS_][Programme old name].

In the simplest case, the rework is to add a termination method after electronic document formation to the print program (or its copy).

Code example to be added to each print programme before calling the form:

TRY
  DATA lv_not_print TYPE c VALUE ''.
  DATA cl_mapping TYPE REF TO /sbis/cl_mapping.
  CREATE OBJECT cl_mapping.
  CALL METHOD cl_mapping->calc_doc
    EXPORTING
      is_nast      = nast
    IMPORTING
      ev_not_print = lv_not_print.
  IF lv_not_print = 'X'.
    EXIT.
  ENDIF.
ENDTRY.

If the print forms have the document data calculation logics then they are desirable to be transferred to the print program.

Fill the settings table /SBIS/SETTINGS

Executive: Tensor or Customer

Frequency: many times during the setting period.

Required rights to SAP:

• The rights to change SAP documents, create output documents and launch the programme (SA38), launch the FM (SE37), download files, debug the programmes, view objects in ABAP repository, rights to the authorization object /SBIS/0001 operation 01.
• Additional rights are only for BASIS 7.0x: ABAP developer rights are additionally required to write and debug queries, list building, as dynamic queries are missing in BASIS 7.0x.
• If you use only J print: No rights required if Tensor specialists have ready tunings for the print programmes.

The executive edits a text file which describes the table fields /SBIS/SETTINGS in a more convenient representation in the process of SAPPER module setting. Settings table filling order is described below. Text file .csv with settings is imported into the table /SBIS/SETTINGS using the programme /SBIS/UPDATE_SETTINGS.

Menu item for documents sent

You have to fill /SBIS/SETTINGS table fields responsible for the menu item names (ACCORDION section).

Write a document list building request for each menu item

You have to fill /SBIS/SETTINGS table fields responsible for list building.

Describe the field mapping for each print programme

You have to fill /SBIS/SETTINGS table fields responsible for specific document creation. The print programme logbook determines the data fields names. The primary setting of the mapping fields is performed. For the final configuration the executive has to start the module in debug mode and check the settings accuracy, he also has to understand which fields are missing data and to check the work accuracy.

Preparation of local computer

You should install SBIS SDK to your local computer. It is a component to connect to SBIS system.

Testing

Executive: Tensor or Customer

Frequency: once.

Required rights to SAP: Rights to create, modify, and print documents. Rights for ZSBIS transaction.

SAPPER module needs testing after its installation:

1. Create test accounts in SBIS for Company Codes (CC) and a test buyer.
2. Create test documents for CC in SAP.
3. Launch ZSBIS transaction. Perform a test sending of documents from your CC.
4. Create test documents in the buyer’s account and send them to your CC.
5. Launch ZSBIS transaction. Test the document reception. Test the document confirmation and rejection.

Move SBIS SAPPER module to production system

Executive: Customer

Frequency: once.

Required rights to SAP: Rights for transport requests transfer.

After eliminating of all remarks, customer’s specialists transfer SAPPER module to production system.

It’s necessary to include /SBIS/SETTINGS table data into transport request.

The best test variant is sending of the documents for the previous period, it will reveal the situations undetermined at module setting, and test the system performance.