DocManager

the below badi’s/enhancement spots are available within the docmanager add on /dflow/docmanger crm bo detail badi /dflow/badi docmgr crm bo dtl allows custom manipulation of crm store new processing business object, sap object, doctype, object id, and filename details /dflow/docmanger sfo status badi /dflow/badi docmgr sfo status allows custom determination of whether to enabled or disable the docmanager sfo menu option in the code, leverage the input parameter is lporb to determine the sap object and archivelink document type set the parameter cv ep status with one of the following values 0 active 1 inactive 2 invisible note that you do not have to set to 0 active, as this is the default /dflow/docmanger storeandlink badi /dflow/badi docmgr store link allows custom processing of the store new process prior to the content api “create” call with iv caller 'b' one of the most common reasons to implement this badi under iv caller 'b' is to create a folder structure during the document creation process to do so, you two options 1 1 parent with \<n> flat folders 2 all folders as nested folders in this case, set the variable cv nested folders to "x" note you can pass the folder name each time you create a document link enterprise will first check to see if that name exists under the configured location/folder id in the docmanager rule if it does not exist, it will create it if it exists, no action is performed for a folder creation when you create a multi level folder structure, you will be able to indicate which folder to store the document in by default, the document is stored in the top level sub folder to place the content (if you are storing content, which is optional) in a folder other than the top parent folder, indicate this with a tild example of ct custom to create 4 folders, and place content in parent folder sap 4500017723 sap subfolder1 subfolder2 subfolder3 or sap 4500017723 sap subfolder1 subfolder2 subfolder3 example of ct custom to create 4 folders, and place content in lowest sub folder sap 4500017723 sap subfolder1 subfolder2 subfolder3 below is an example to create 1 sub folder showing the abap debugger allows custom processing of the store new process after the content api “create” call and also the archivelink create link with iv caller 'a' this is called in both success and error occurrences which is indicated by the entries in the return table in the case of success, iv arc doc id will be populated some customers implement this to interpret the return table ct return when creating folders in some scenarios the folder id's created are useful to know when you use the it custom folder to create folders, the return table will also pass back the folder id's created the parent folder is indicated by a ! exclamation point, all sub folders are indicated by a tild example of return table when folders are created !sap 4500017723,147811962292 sap subfolder1,938382828 sap subfolder2,938382829 sap subfolder3,938382830