Diese Seite (Version-1) wurde zuletzt am 13-Aug.-2018 03:11 von Administrator geändert.

Du bist nicht autorisiert, diese Seite umzubenennen.

Du bist nicht autorisiert, diese Seite zu löschen.

Versionsgeschichte der Seite

Version Zuletzt geändert Größe Autor Änderungen Kommentar

Links

Eingehende Links Ausgehende Links

Versionsunterschiede

Unterschiede zwischen Version und .

Zeile 1: 143 Zeilen hinzugefügt.
[{ALLOW view All}]
[{ALLOW edit Authenticated}]
See [SAP help|http://help.sap.com/saphelp_nw04/helpdata/en/b4/3f9e64bff38c4f9a19635f57eb4248/frameset.htm]
[SAP Crypto]
[ABAP Connectivity Home
|https://wiki.sdn.sap.com/wiki/display/ABAPConn/ABAP%20Connectivity%20Home]
! Classical SAP Technologies (ABAP)
||Keyword||Description||SAP help
|[RFC]|__R__emote __F__unction __C__all|[SAP help|http://help.sap.com/saphelp_nw04/helpdata/en/b4/3f9e64bff38c4f9a19635f57eb4248/frameset.htm]
|[ALE]/EDI|__A__pplication __L__ink __E__nabling / __E__lectronic __D__ata __I__nterchange|see IDoc
|[BAPI]|__B__usiness __A__pplication __P__rogramming __I__nterface|[SAP help|http://help.sap.com/saphelp_nw70/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm]
|IDoc Interface|__I__ntermediate __Doc__ument (used with ALE & BAPI)|[SAP help|http://help.sap.com/saphelp_nw04/helpdata/de/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm]
|[BDoc]|Business document|
|[Gateway|Netweaver Gateway]|Netweaver Gateway (OData)
! Communication Between ABAP and Non-ABAP Technologies
||Keyword||Description||SAP help
| |SAP Business Connector
|[JCo]|SAP __J__ava __Co__nnector|[SAP Help|http://help.sap.com/saphelp_nwpi711/helpdata/en/48/707284872c1b5ae10000000a42189c/frameset.htm]
| |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 Collection \\
[SAP Help|http://www.sdn.sap.com/irj/sdn?rid=/webcontent/uuid/c1fb3173-0501-0010-74a0-eb7b8ca4842f]
!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
The upload (message CONF11) is done from the transceiver and not reflected here!\\
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 transactional RFC port (x.WE21) needs to be set on "IDoc rec.types SAP Release 3.0/3.1".\\
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 01000SAPCLNT100
}}}
Generally 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
[XI|http://help.sap.com/saphelp_nw70/helpdata/de/e1/8e51341a06084de10000009b38f83b/frameset.htm]
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
1x Auftragssatzdatei und 1x Nutzdatendatei (Nutzdatendatei wird vor dem Verschicken via E-Mail signiert und verschlüsselt, zwei verschiedene Verfahren zugelassen:
** 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
[SAP help|http://help.sap.com/saphelp_nw04/Helpdata/de/2a/90d038f58f863de10000000a11402f/frameset.htm]
! [sapftp]