DocManager Metadata maps
As a more powerful option to using the metadata map configuration, class/method metadata maps allow you to compile the SAP data via ABAP that will update your CMS documents (if configured) for outbound Gimmal Link storage and mass metadata push/updates.
The below example is provided with the Gimmal Link Enterprise product.
Signature:
Type | Parameter | Description | Sample Value |
|---|---|---|---|
Importing | IV_SAP_OBJECT | The SAP business object associated with this process | BKPF |
Importing | IV_DOCTYPE | The ArchiveLink document type to use for linking documents with this process | ZINVOICE01 |
Importing | IV_SAPKEY | The unique identifier of the SAP records the link will be created to | 300019000000002013 |
Importing | IV_ARC_DOC_ID | The unique identifier of the CMS document | {83281172-DD17-4B8A-8913-9E5E69BA3125} |
Exporting
| ET_METADATA
| This is the resulting table of key (case sensitive CMS property name) value (SAP data) pairs of the SAP data to update the CMS document with that you must fill with your ABAP code | |
Notes:
- If you want to update a multi-line property (only supported in Documentum and FileNet CMS systems), place an X in the field ZMULTI
- For Box CMS systems where a date field is part of the metadata being sent, the format must be MM/dd/yyyy hh:mm:ss a z, where a z = the AM/PM and TIMEZONE
- example: 12/31/9999 12:00:00 PM MST
- To assist with the date format for Box, you may choose to utilize the Gimmal Link Enterprise helper method ‘/dflow/cl_utilities_helper=> format_date_plus_sys_timezone’ to format a system date field to the format desired and also appending the system timezone
- To assist with the date format for FileNet and Documentum, you may choose to utilize the Gimmal Link Enterprise helper method ‘/dflow/cl_utilities_helper=>format_date’ to format a system date field to the format desired