Transport & Installation

Transport request, abapGit, manual installation, and post-installation.

10 – Transport & Installation

Overview

All Bilendo ABAP objects are installed in the SAP system using one of two mechanisms. Because Bilendo does not operate its own SAP systems, we cannot provide SAP transport files (.data/.cofile). Instead, the source code is provided through an abapGit repository or as manual instructions.

This chapter is intended for SAP consultants and Basis administrators.

Object Catalog

All ABAP objects to be installed:

Installation order: Structures → Table types → Class → Reports

1. abapGit Installation (Recommended)

Suitability

abapGit is the recommended installation method. It offers:

• Automatic object creation in the correct order

• Version control and easy updates

• No manual copy-paste errors

• Works on any SAP NetWeaver ≥ 7.40 SP08

Prerequisites

• SAP NetWeaver ≥ 7.40 SP08 (recommended: 7.52+)

• abapGit installed (transaction ZABAPGIT or /ui2/cl_abapgit)

• Developer key for the user

• Package ZBILENDO created in SE80 (local package or transport package)

• Optional: Network access for the online repository; otherwise, use offline import

Install abapGit (if not already installed)

If abapGit is not yet installed in the system:

1. SE38 → Create a report: ZABAPGIT_STANDALONE

2. Download the current standalone source code from github.com/abapGit/abapGit → Releases → abapgit-standalone.prog.abap

3. Paste the entire source code into the report

4. Activate and run it

After installation, abapGit is available via transaction ZABAPGIT.

Option A: Online repository (with network access)

1. Call transaction ZABAPGIT

2. Click + Online

3. Enter the following:

1. Create Online Repo → abapGit loads all objects automatically

2. Click Pull → the objects are created in the SAP system

3. Check the activation log – all objects must be green

Option B: Offline Repository (without network access)

If the SAP system does not have internet access:

1. Pack the abapGit/ folder from the Bilendo documentation into a ZIP file

2. Call transaction ZABAPGIT

3. Click + Offline

4. Entries:

1. Click Import zip → upload the ZIP file

2. abapGit creates all objects automatically

3. Activate

Applying Updates

For future versions:

1. ZABAPGIT → Select the Bilendo repository

2. Pull (online) or Import zip (offline) with the new version

3. abapGit shows a diff of the changes

4. Only changed objects are updated

5. If there are conflicts with local modifications: use the merge dialog

abapGit Repository Structure

The provided repository has the following structure:

abapGit/
├── .abapgit.xml                           (Repository configuration)
├── README.md                              (Installation notes)
└── src/
    ├── package.devc.xml                   (Package definition ZBILENDO)
    ├── zfi_s_bilendo_bseg.tabl.xml        (Structure: Document line items)
    ├── zfi_s_bilendo_kna1.tabl.xml        (Structure: Customer master)
    ├── zfi_s_bilendo_vbak.tabl.xml        (Structure: Orders)
    ├── zfi_t_bilendo_bseg.ttyp.xml        (Table type BSEG)
    ├── zfi_t_bilendo_kna1.ttyp.xml        (Table type KNA1)
    ├── zfi_t_bilendo_vbak.ttyp.xml        (Table type VBAK)
    ├── zfi_adr6.ttyp.xml                  (Table type ADR6)
    ├── zcl_fi_bilendo_assist_v2.clas.xml   (Class: Metadata)
    ├── zcl_fi_bilendo_assist_v2.clas.abap  (Class: Source code)
    ├── zfi_bilendo_export_v2.prog.xml      (Extractor: Metadata)
    ├── zfi_bilendo_export_v2.prog.abap     (Extractor: Main report)
    ├── zfi_bilendo_export_v2_d01.prog.xml  (D01: Metadata)
    ├── zfi_bilendo_export_v2_d01.prog.abap (D01: Data declaration)
    ├── zfi_bilendo_export_v2_f01.prog.xml  (F01: Metadata)
    ├── zfi_bilendo_export_v2_f01.prog.abap (F01: Processing logic)
    ├── zfi_bilendo_import_v2.prog.xml      (Import: Metadata)
    ├── zfi_bilendo_import_v2.prog.abap     (Import: Main report)
    ├── zfi_bilendo_import_f01.prog.xml     (Import F01: Metadata)
    └── zfi_bilendo_import_f01.prog.abap    (Import F01: Logic)

2. Manual Installation (SE11 / SE24 / SE38)

Suitability

Manual installation is the fallback mechanism when:

• abapGit is not available in the system and cannot be installed

• Organizational requirements call for manual creation

• Only individual objects need to be modified afterward

Time required: 2–4 hours (depending on experience)

Step 1: Create DDIC Structures (SE11)

Complete field definitions → 02 - DDIC Structures

Procedure for each structure:

1. SE11 → Data type: Enter structure name → Create

2. Assign a short description

3. Enter components according to 02 - DDIC Structures

4. Activate (Ctrl+F3)

Step 2: Create Table Types (SE11)

Procedure for each table type:

1. SE11 → Data type: Enter the table type name → Create

2. Enter the row type (e.g., ZFI_S_BILENDO_BSEG)

3. Access type: Standard Table, Key: Default

4. Activate

Step 3: Create the Class (SE24)

Complete source code → 03 - Assist Class

1. SE24 → Class: ZCL_FI_BILENDO_ASSIST_V2 → Create

2. Description: Bilendo SAP Integration - Assist Class v2

3. Instantiation: Public, Final: Yes

4. On the Attributes tab: Enter all attributes from the class definition

5. On the Methods tab: Create all methods (parameters as specified in the class definition)

6. In each method: Source Code → Paste the ABAP code from 03 - Assist Class

7. Activate

The class has approximately 2,200 lines of code in 19+ methods. Alternatively, you can paste the class definition and implementation as a single contiguous block into the source code editor (SE24 → source code-based view).

Step 4: Create Reports (SE38)

Extractor Report

Complete source code → 04 - Extractor Report

Procedure:

1. SE38 → ZFI_BILENDO_EXPORT_V2 → Create → Type: Executable Program

2. Paste the source code (contains INCLUDE statements)

3. SE38 → ZFI_BILENDO_EXPORT_V2_D01 → Create → Type: Include

4. Paste the source code

5. SE38 → ZFI_BILENDO_EXPORT_V2_F01 → Create → Type: Include

6. Paste the source code

7. Be sure to activate all three programs

Re-Integrate Report

Complete source code → 05 - Re-Integrate Report

Follow the same procedure as for the Extractor Report.

3. Post-Installation

3.1 Verify Activation

All objects must be visible and activated in SE80 under the package ZBILENDO (or the local package you selected):

SE80 → Package → ZBILENDO
  ✓ ZFI_S_BILENDO_BSEG   (Struktur)
  ✓ ZFI_S_BILENDO_KNA1   (Struktur)
  ✓ ZFI_S_BILENDO_VBAK   (Struktur)
  ✓ ZFI_T_BILENDO_BSEG   (Tabellentyp)
  ✓ ZFI_T_BILENDO_KNA1   (Tabellentyp)
  ✓ ZFI_T_BILENDO_VBAK   (Tabellentyp)
  ✓ ZFI_ADR6             (Tabellentyp)
  ✓ ZCL_FI_BILENDO_ASSIST_V2  (Klasse)
  ✓ ZFI_BILENDO_EXPORT_V2     (Report + 2 Includes)
  ✓ ZFI_BILENDO_IMPORT_V2     (Report + 1 Include)

If an object is not activated: Right-click → Activate. If activation errors occur, check the dependency order (structures before table types before class before reports).

3.2 Adjust the D01 Include

The include ZFI_BILENDO_EXPORT_V2_D01 contains system-specific constants that must be adjusted:

" --- ADJUST: Directory paths per system ---
CONSTANTS: gc_dir_hed TYPE string VALUE '/usr/sap/<DEV-SID>/Bilendo_OUT/',
           gc_dir_heq TYPE string VALUE '/usr/sap/<QA-SID>/Bilendo_OUT/',
           gc_dir_hep TYPE string VALUE '/usr/sap/<PRD-SID>/Bilendo_OUT/'.

" --- ADJUST: System IDs in CASE branch (FORM get_filenames) ---
WHEN '<DEV-SID>'.   " e.g., 'D01'
WHEN '<QA-SID>'.    " e.g., 'Q01'
WHEN '<PRD-SID>'.   " e.g., 'P01'

The paths must exist on the application server (→ Step 3.3).

3.3 Create Directories on the Application Server

Use transaction AL11 or the OS command line:

# Log in as <SID>adm
su - <SID>adm
mkdir -p /usr/sap/<SID>/Bilendo_OUT
mkdir -p /usr/sap/<SID>/Bilendo_IN
chmod 755 /usr/sap/<SID>/Bilendo_OUT /usr/sap/<SID>/Bilendo_IN

3.4 Checking Authorizations

The following authorization objects must be assigned to the executing user (batch user or dialog user):

3.5 Test Run in Dialog Mode

Manually test each report before scheduling the job:

1. SE38 → ZFI_BILENDO_EXPORT_V2 → F8

2. Fill in the selection screen:

   • P_KNA1 = X, P_BSID = X, P_BSAD = X

   • P_ALL = X (for the initial test)

   • S_BUKRS = one test company code

3. F8 (Execute)

4. Expected result: Files on the application server in Bilendo_OUT/

5. Check the files in AL11: content, field separator, encoding

Only after a successful test run → schedule variants and jobs (→ 07 - Variants & Job Scheduling)

4. Troubleshooting

abapGit Errors

Manual Installation – Errors

Runtime Errors

Checklist

INSTALLATION
[ ] Installation method selected (abapGit or manual)
[ ] Package ZBILENDO created in SE80
[ ] All 13 objects present and activated (SE80)

CONFIGURATION
[ ] D01 include: directory paths adjusted
[ ] D01 include: system IDs in CASE branches adjusted
[ ] Directories Bilendo_OUT and Bilendo_IN created (AL11)
[ ] Authorizations for batch user checked

TEST
[ ] Export report tested in dialog (SE38, p_all = X)
[ ] Files visible on application server (AL11)
[ ] Import report tested in dialog (SE38)
[ ] Variants created (→ Doc 07)
[ ] Job scheduled (→ Doc 07)