HVS32 SAP RFC Interface (Interactive): Unterschied zwischen den Versionen
(2 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
Zeile 27: | Zeile 27: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
− | ! Parameter !! | + | ! Parameter !! Description |
|- | |- | ||
− | | jco.client.ashost || SAP | + | | jco.client.ashost || SAP application server on which the structure of the RFC module is located |
|- | |- | ||
− | | jco.client.sysnr || SAP | + | | jco.client.sysnr || SAP system no. |
|- | |- | ||
− | | jco.client.client || | + | | jco.client.client || Client ID (SAP) |
|- | |- | ||
− | | jco.client.user || SAP | + | | jco.client.user || SAP user with rights to execute RFC |
|- | |- | ||
− | | jco.client.passwd || | + | | jco.client.passwd || Password |
|- | |- | ||
− | | RFCFunctions || | + | | RFCFunctions || List of RFC modules to be called by DataGatewayServer |
|} | |} | ||
− | = | + | = Available HVS32 functions = |
− | + | Item data and dangerous goods information must be defined in the RFC module as Table or Struct, since they have a 1:n relationship to the package data.<br> | |
− | + | The HVS32 sends the data in the import parameters - all parameters which should be transmitted to the HVS32 must be written in the export parameters. The communication is bidirectional, i.e. the feedback from SAP is synchronously in the same transaction as the request.<br><br> | |
− | + | Please note that the field descriptions refer only to a standard, which should serve as a suggestion for the interface. Function names, field names /-lengths /-formats may differ in principle, but in this case must be considered/analyzed individually.<br> | |
− | |||
<br> | <br> | ||
'''[[HVS32_Funktionen_Interaktiv|Verfügbare HVS32 Funktionen]]''' | '''[[HVS32_Funktionen_Interaktiv|Verfügbare HVS32 Funktionen]]''' | ||
− | = | + | = Examples = |
<div class="toccolours mw-collapsible mw-collapsed" style="width:60%; overflow:auto;"> | <div class="toccolours mw-collapsible mw-collapsed" style="width:60%; overflow:auto;"> |
Aktuelle Version vom 7. September 2021, 11:58 Uhr
Prerequisites
DGS-Version | 3.6.0.550 or higher |
DGS-Plugins | HVS32Server, SAP RFC Client |
Function description
The DataGatewayServer (DGS) uses the SAP library "JCo" for the connection via RFC protocol with an ABAP application server. In case of interactive processing, requests are sent from the dispatch system to the SAP system. Here, the DGS acts as an RFC client program, which explicitly addresses a specific SAP application server for processing the request.
The DGS is the central communication unit through which all data is exchanged between the shipping system and the SAP system. It runs in the form of a service on a Windows server.
Required SAP components/parameters
- latest version 3 of SAP library Java Connector "JCo" in 64Bit.
- SAP GUI installation on the server where the DataGatewayServer is installed - alternatively a manual adjustment of %SystemRoot%\system32\drivers\etc\services und %SystemRoot%\system32\drivers\etc\hosts
the following parameters are required by the DGS to call RFC modules on an SAP system:
Parameter | Description |
---|---|
jco.client.ashost | SAP application server on which the structure of the RFC module is located |
jco.client.sysnr | SAP system no. |
jco.client.client | Client ID (SAP) |
jco.client.user | SAP user with rights to execute RFC |
jco.client.passwd | Password |
RFCFunctions | List of RFC modules to be called by DataGatewayServer |
Available HVS32 functions
Item data and dangerous goods information must be defined in the RFC module as Table or Struct, since they have a 1:n relationship to the package data.
The HVS32 sends the data in the import parameters - all parameters which should be transmitted to the HVS32 must be written in the export parameters. The communication is bidirectional, i.e. the feedback from SAP is synchronously in the same transaction as the request.
Please note that the field descriptions refer only to a standard, which should serve as a suggestion for the interface. Function names, field names /-lengths /-formats may differ in principle, but in this case must be considered/analyzed individually.
Verfügbare HVS32 Funktionen
Examples
'Z_HVS_VERSANDDATENANFRAGE'.
IMPORTING
REFERENCE_NO CHAR(40)
EXPORTING
PACKSTUECK STRUCTURE
KUNDEN_NR CHAR(20)
ZIEL_ADR_NAME1 CHAR(50)
ZIEL_ADR_NAME2 CHAR(50)
ZIEL_ADR_NAME3 CHAR(50)
ZIEL_ADR_STRASSE CHAR(50)
ZIEL_ADR_LKZ CHAR(5)
ZIEL_ADR_PLZ CHAR(10)
ZIEL_ADR_ORT CHAR(50)
ZIEL_ADR_REGION CHAR(20)
ZIEL_ADR_BAHNHOF CHAR(30)
AUFTRAGGEBER_ID CHAR(10)
VERSANDART_ID CHAR(10)
LIEFERSCHEIN_NR CHAR(40)
AUFTRAG_NR CHAR(20)
BESTELL_NR CHAR(20)
NEUTABSENDER_NAME1 CHAR(30)
NEUTABSENDER_NAME2 CHAR(30)
NEUTABSENDER_NAME3 CHAR(30)
NEUTABSENDER_STRASSE CHAR(30)
NEUTABSENDER_LKZ CHAR(3)
NEUTABSENDER_PLZ CHAR(10)
NEUTABSENDER_ORT CHAR(30)
TABLE DGPOSITIONS
UNNR CHAR(4)
KLASSE CHAR(6)
VPG CHAR(5)
K_CODE CHAR(5)
BEZEICHNUNG CHAR(110)
MENGE CHAR(9)
BEGRENZTE_MENGE CHAR(1)
VERP_ANZAHL CHAR(10)
VERPACKUNGSART CHAR(8)
NEBEN_GEFAHR CHAR(20)
BUCHST640 CHAR(1)
MENGEN_EINHEIT CHAR(2)
BEFOERD_KAT CHAR(10)
FAKTOR CHAR(10)
NETTO_EXPL_MASSE CHAR(9)
TUNNEL_B_CODE CHAR(10)
FREIGEST_MENGE CHAR(1)
FF_CODE CHAR(20)
'Z_HVS_PAKETSCHEINDRUCKMELDUNG'.
IMPORTING
PACKSTUECKRUECK STRUCTURE
LIEFERSCHEIN_NR CHAR(40)
PACK_STK_GES CHAR(10)
PACK_STK_NR CHAR(10)
GEWICHT CHAR(9)
PACKSTUECK_LAENGE CHAR(10)
PACKSTUECK_BREITE CHAR(10)
PACKSTUECK_HOEHE CHAR(10)
TRACKING_NR CHAR(35)
VERSAND_SENDUNGS_NR CHAR(20)
DRUCK_DATE_TIME CHAR(10)
AUSGANG_DATE_TIME CHAR(10)
GEBUEHR CHAR(19)
GEBUEHR_WAEHRUNG CHAR(3)
EXPORTING
FEHLERTEXT1 CHAR(200)
FEHLERTEXT2 CHAR(200)
'Z_HVS_AusgangslistenRueckMeldung'.
IMPORTING
AUSGANGSLISTENR (20)
PACKSTUECKRUECK TABLE
LIEFERSCHEIN_NR CHAR(40)
TRACKING_NR CHAR(35)
GEBUEHR CHAR(19)
GEBUEHR_WAEHRUNG CHAR(3)
oder
'Z_HVS_AusgangslistenRueckMeldung'.
IMPORTING
AUSGANGSLISTENR (20)
TABLE PACKSTUECKRUECK
LIEFERSCHEIN_NR CHAR(40)
TRACKING_NR CHAR(35)
GEBUEHR CHAR(19)
GEBUEHR_WAEHRUNG CHAR(3)