Solution : https://service.sap.com/sap/support/notes/1580663 (Connexion à SAP Service Marketplace requise)
Mots Clés :
/saphelp_nw04/helpdata/en/52/a21f407b402402e10000000 a1550b0/frameset, support package stack 28 solution support package 28, support package stack guide, import support package stack 28, import sap exchange infrastructure, terms sap exchange infrastructure, sap exchange infrastructure, service market place, attached xi corrections, 0 support packagestack 28
Notes associées :
1613613 | Messages that were edited manually are not archived |
1612129 | Result output in RSXMB_CHECK_MESSAGE_CONSIST is incomplete |
1610873 | BPE-RUN:Non 'UTF-8' Payload sent to BPE |
1609121 | Activate Queues functionality in transaction SXMB_ADM |
1605006 | Optimizing evaluation of interfaces for archiving |
1599712 | Messages not completely deleted after archiving |
1591899 | Input values for the report SXMS_PF_REORG_RAW are ignored |
1579370 | Long runtime of report RSXMB_DEL_TO_ARCH |
1567389 | Missing authorization checks in Runtime Workbench |
1557658 | Configuration of timeout for our Web-Modules |
1533195 | Receiver SOAP adapter in no-soap mode: target system faults |
1533004 | Authentication bypass vulnerability in ESR |
1532319 | Keep FTP connection alive when servernode can't acquire lock |
1528827 | Missing authorization check in Partner Connectivity Kit(PCK) |
1528390 | RFC Adapter: Principal Propagation issue with RFC Receiver |
1528358 | Monitored services do not appear on all server nodes |
1518273 | |
1512577 | CCMS status of Mapping Runtime in XI/PI Runtime Workbench |
1509477 | Receiver file adapter messages fail with 'Already Exists' er |
1505443 | SOAP Receiver with SSL offers too weak cipher suite |
1496756 | XI runtime: Archiving IDoc messages if partner type not LS |
1483974 | File and JDBC sender adapter's retry not working after error |
1459995 | Soap Sender Adapter HTTP 202 response for asynchronous call |
1381198 |