SAPLink / Inbound to SAP Processing (Not supported S3)
SAPLink is the inbound processing from your content repository to SAP. This can be leveraged to execute a number of Link Enterprise 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 Link Enterprise SAP system account specified in the middleware must have access to the transaction /DFLOW/GTW in its security profile to execute inbound to SAP Jco calls. Please refers 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
- 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 Link Enterprise windows service.
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 Link Enterprise 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).
Gimmal Link Enterprise 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 to 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 doucflow user name and time stamp fields are updated.
Upon a success SAPLink, metadata can also be enable to be transferred back to your CMS system.
Inbound to SAP entries search for documents that meet a 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.
Setting | Description | Sample Value(s) |
|---|---|---|
Enable Inbound to SAP | If checked configuration for Inbound to SAP is enabled and can be configured for inbound to SAP processing. |
|
SAP | The SAP system to send document metadata too. | SAP DEV ED1 |
CMS | The CMS system to get document metadata from. | |
Trigger data Type | Data type by which the saplink rule is triggered. Task and Sign task type only applicable for Box workflow tasks. | Boolean, TimeStamp, task and signtask. |
SAP Repo. | The SAP ArchiveLink repository that should be associated with this metadata being passed. | ZC |
SAP Type | The SAP ArchiveLink document type associated with this metadata being passed. | ZCONTRACT |
CMS Repo. | The content management system object store or repository. | |
CMS Type | The content management system document class, object type or metadata template to look for the requested metadata in. | scmContracts |
Interval | The Inbound to SAP process searches for documents matching the configured criteria and then sends the information to SAP. This interval determines how often the underlying content management system is searched. | 10 |
Trigger Prop. | The content management system property or attribute associated with when to trigger sending information to SAP. By default, Link Enterprise sets this property to True or False based on the result of a SAPLink call to SAP. These values can be manipulated via the Config.properties file with the below entries: saplinkfalse.value=<value> (for success) saplinkerror.value=<value) (for error) | LinkEnterpriseSaplinkTrigger saplinkfalse.value=DoNotProcessSuccess saplinkerror.value=DoNotProcessError |
Type | Currently M365 implementations only support Boolean trigger types. | Boolean |
Error Prop. | If an error happens while trying to process a particular file you can optionally store the error information in the content management system. | LinkEnterpriseSaplinkError |
Type | Currently M365 implementations only support String (single line of text) Error Property types. | String |
Max | An optional setting to limit the number of entries returned when searching for documents.
A setting of 0 has no limit. | 0 |
Filter | For SharePoint: this is not applicable | |
Location | For SharePoint: this is not applicable |
|
Order By | For SharePoint: this is not applicable |
|
Sub. | For SharePoint: this is not applicable |
|
lineItemColumn | The line item column name which is referred to the csv files containing the line item information. | |
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. These must match the SharePoint column names with exact casing. | title,contract,name |
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 |