See SAP help
Classical SAP Technologies (ABAP)#
| Keyword | Description | SAP help |
|---|---|---|
| RFC | Remote Function Call | SAP help |
| ALE/EDI | Application Link Enabling / Electronic Data Interchange | see IDoc |
| BAPI | Business Application Programming Interface | SAP help |
| IDoc Interface | Intermediate Document (used with ALE & BAPI) | SAP help |
| BDoc | Business document | |
| Gateway | Netweaver Gateway (OData) |
Communication Between ABAP and Non-ABAP Technologies#
| Keyword | Description | SAP help |
|---|---|---|
| SAP Business Connector | ||
| JCo | SAP Java Connector | SAP Help |
| SAP Java Resource Adapter | ||
| SAP .NET Connector | ||
| Internet Communication Framework | ||
| SOAP Runtime for SAP Web AS | ||
| Web Service Technologies in SAP Web AS |
HR-PDC#
Plant Data CollectionSAP Help
PP-PDC#
Here there is a section for transferring HR data, called CC1. It was used long ago on SAP version 3.0. The foreign time management system is called transceiver.You need to create a model (x.BD64) "SUBSYSTEMS" where the SAP system (sender) has messages to the logical system "SUB_CC1" (receiver) with following messages:
- ABSEN1
- DWLOAD
- EXTWA1
- PERSO1
- REQUI1
- UPLOAD
You cannot generate the partner profile automatically, because a "message function" (x.WE20) is needed, so create manually:
- ABSEN1 UPD
- DWLOAD CFG
- EXTWA1 UPD
- PERSO1 UPD
- REQUI1 REQ
- UPLOAD CFG
The RFC-connection (TCP/IP) needs to "start on Explicit Host" the external program like "d:\pcs\sap\codownld.cmd" on the external "target host". SAP acts as client here, so it will connect to the Gateway from the subsystem which need to be added at the "Gateway Options", where "Gateway Host"="Target Host" and "Gateway service"=sapgw00 (assumed). Again, the upload is done from the transceiver, so the RFC-destination is just for SAP=>Subsystem communication.
The transceiver has certain folders and a config file "COUPLD.CFG" for the upload which needs to have a line with following fields and lengths (see x.WE31 > E1UPLD1)
No filed len description 1 MANDT 3 Client 2 LDEST 32 RFC-Destination 3 KKANA 10 Communication channel (="SUB_CC1") 4 UPLDA 8 Upload-Message (="CONF11") 5 EUSER 12 RFC-User in SAP system 6 PASSW 10 RFC-User Password 7 LANGU 1 Language (E,D,...) 8 SAPSY 3 SAP SysID 9 APSER 30 Application server (see SapLogon) 10 SAPSE 2 System number (see SapLogon) 11 FUNCT 30 Upload function (=TRAR_GET_DATA_FROM_CC1_CONF11) 12 SEGANZ 5 Maximum segments in idoc 13 LOGSYS 10 Logical system name of SAP system (see table T000) Example: 100SYSKK1_XX_RFC SUB_CC1 CONF11 RFCCPIC 12ab12ab DSAPMYSAPAPPSERVER 12TRAR_GET_DATA_FROM_CC1_CONF11 01000SAPCLNT100Generally this config file is created manually. But they can be distributed (SAP=>subsystem) via:
| x.BA10 | Subsystem Configuration |
| x.BA11 | Config. Transceiver / Upload Files (here the values are appended to the subsystem's config file) |
To communicate use x.PT4x or following reports
| r.SAPCDT42 | Transfer HR Mini-Master to PDC System |
| r.SAPCDT43 | Transfer Master Data to PDC System |
| r.SAPCDT44 | Send a request (IDoc REQUI1) to Upload Time Events from the Subsystem |
| r.SAPCDT45 | Process upload (IDoc CONF11) |
Tools#
Compare and syncronize Tables- SM30: <any table/view>, View ( or SCMP )
- Menue > Hilfmittel > Vergleich
- Choose destination > Login
- white/blue are identical
- Filter > uncheck "Identische"
- L = only in left side (see header)
- R = only in right side
- MR/ML = Modified , right and left side
- To syncornize, use Menu > Bearbeiten > Abgleichen
XI / PI#
Kommunikationsserver
B2A Manager (Steuer, SV, Bescheinigungswesen etc.)#
see Personalabrechnung > Deutschland > Behördenkommunikation (B2A)| RPCTAZD0 | HR-DST: Lohnsteueranmeldungen verwalten |
- Report H99_B2AManager erstellt Datensätze (hier die Doku lesen!)
- B2A verwaltet und verschickt oder fordert an
- ggf. Verschlüsselung (Drittanbieter) nötig
- unterschiedliche Formate möglich (XML, Strings)
- unterschiedliche Protokolle möglich (email + attachment, HTTPS)
- unterschiedliche Verschlüsselungsmethoden, wie PEM (Privacy Enhanced Mail) oder PKCS#7 (Public-Key Cryptography Standard No.7)
- Krankenkassen benutzen: email + attachment + PEM
- PKCS#7 mit SAPCryptolib
- PEM - Nur für DEÜV-Meldungen, Beitragsnachweis und Entgeltbescheinigung Krankenkassen (jeweils nur Ausgang via E-Mail)
Hinweis: Zum Testen in der Sicht V_T50BK (HR-B2A: Konstanten) die Konstante Mode setzen:
| SV | IENA | MODE | T (Test) oder P |
| SV | IENR | MODE | T (Test) oder P |
| SV | OENA | MODE | T (Test) oder P |
| SV | OENR | MODE | T (Test) oder P |
Durch diese Einstellung wird beim E-Mail-Verfahren der Empfänger auf die E-Mail-Adresse des Benutzers gesetzt. Im Produktivsystem setzen Sie die Konstante MODE auf P (Produktiv).
- manche Behörden: HTTPS + XML (direkt an/von Server)
- Report H99_B2ACHECK: Einstellungen prüfen
| PB2A | B2A Manager |
| SNRO / SNUM | Nummernkreisobjektpflege "HRB2A" |
SAP Gateway#
| SMGW | Administration |