SAPLink / Inbound to SAP Processing

unsupported in s3 saplink is the inbound processing from your content repository to sap this can be leveraged to execute a number of docuflow delivered functions in sap or your own custom logic thus, why we call saplink the "do anything pipe" into sap there are three components involved in saplink processing ensure the cms document class/object type/metadata template has the required fields for saplink processing configuration a "rule" in the enterprise connector middleware this determines what content is to be processed, when, and what (if any) metadata is to be transferred what is processing is dependent on the cms system being used (outline more below) configuration of a corresponding docmanager rule in sap that matches the document type configured in step 2 this determines what action is to be performed in sap (link a document, trigger custom code, start accounts payable workflow, etc ) note the docuflow system account specified in the middleware must have access to the transaction /dflow/docuflowgtw in its security profile to execute inbound to sap jco calls please refer to the section "create sap system account" in the base installation and configuration guide the inbound processing rule determines what is to be processed what metadata is to be sent to sap how to configure a saplink rule in enterprise connector load up in the browser the onfigurator https //localhost 82/box under "mappings" click inbound to sap hover over each of the input boxes in the ui to look at sample values for each input box click save restart the docuflow service notes the docmanager rule in sap determines what action is to be performed in sap for each item "found" from a saplink rule in the connector each request is processing and calls a docuflow bapi within the sap, which then reads the docmanager rule configuration found for that doctype there can only be one archivelink document type and sap business object combination ever configured in the docmanager configuration, thus avoid sharing document types across sap object (to avoid an inbound collision) docuflow will then execute the configured action and pass back a return, either an error or success in the case of a success, the trigger property is set too false to prevent a re processing of that item found in the case of an error, the error property, if relevant to your cms system, will be updated in both scenarios, the docuflow username and time stamp fields are updated upon a success saplink, metadata can also be enabled to be transferred back to your cms system rule config what is to be processed inbound to sap entries search for documents that meet specific criteria and send the information to sap for processing if processing completes successfully, the trigger property is adjusted so that the document is not processed again if the processing were to fail by default, the processing is tried again in order to not retry failed documents, adjustments can be made to the filter string to omit documents that were in error 0,307 unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type left unhandled content type rule config what metadata is to be sent to sap what metadata is sent from your repository to sap is determined by the metadata column setting description sample value(s) metadata the comma separated list of metadata to send to sap in the specified order title,contract,name rule config sign task sign task config setting description sample value(s) sourcetriggerproperty the content management system property or attribute associated to trigger when the sign task is completed middlewareoriginaldocid