Not all systems use XI/PI, and it is not required to use Connector for use with SAP ArchiveLink.
In addition to setting up an HTTP destination for SAP XI, there are a few things that need to be configured. First, BAPIs need to be exposed in SAP XI in order for OnBase to interact properly with the SAP system. Secondly, the following parameters should be used when configuring XI/PI:
|
Web Method Name |
Sender CC |
Interface/BAPI |
|---|---|---|
|
MI_NONPOInvoice_os |
Sender_SOAP_ NONPOInvoice |
BAPI_ACC_INVOICE_RECEIPT_ POST |
|
MI_ArchivConnectionInsert_os |
Sender_SOAP_ ArchiveInsert |
ARCHIV_CONNECTION_INSERT |
|
MI_ArchiveProcess_os |
Sender_SOAP_ ArchiveProcess |
Archiv_Process_Rfcinput |
|
MI_POInvoice_os |
Sender_SOAP_ POInvoice |
BAPI_INCOMINGINVOICE_ CREATE |
|
MI_InvoiceParking_os |
Sender_SOAP_ ParkInvoice |
BAPI_INCOMINGINVOICE_ PARK |
|
MI_POGetDetail_os |
Sender_SOAP_ POGetDetail |
BAPI_PO_GETDETAIL |
|
MI_InternalOrderGetDetail_os |
Sender_SOAP_ InternalOrderGetDetail |
BAPI_INTERNALORDER_ GETDETAIL |
|
MI_IncomingInvoiceGetDetail_os |
Sender_SOAP_ IncomingInvoiceGetDetail |
BAPI_INCOMINGINVOICE_ GETDETAIL |
|
MI_BarcodeSendList_os |
Sender_SOAP_ BarcodeSendList |
BAPI_BARCODE_SENDLIST |
|
MI_ArchivBarcodeGlobal_os |
Sender_SOAP_ ArchivBarcodeGlobal |
ARCHIV_BARCODE_GLOBAL |
|
MI_InternalOrderCreate_os |
Sender_SOAP_ InternalOrderCreate |
BAPI_INTERNALORDER_CREATE |
|
MI_RFCReadTable_os |
Sender_SOAP_ RFCReadTable |
RFC_READ_TABLE |
All of the objects for these methods must be kept as the default names given by XI when you map them from the BAPIs. Any create method must implicitly assume a commit call.