DMS Objectlink Requesition / P.O.
Hello,
I create new document type for supplier documents and included a object link to requestion and Purchase order. On ME53N/ME23N screen there is a docuemnt icon, but this is only generell. Have somebody any idea (BADI or User-Exit) to include an icon in the position overview of ME53N and also ME23N and show only, if there is a DMS document linked.
Thanks.
Markus
Hi Markus,
to achieve this behavior you have to maintain the dynpro for ME53N/ME23N itself I think. I'm not sure if this will really work as the button is inlcuded in the standard
behavior. But I'm quite sure that you can remove this button on the screen in SE80 transaction. Maybe you can also add some condition to made the button
visible or not.
Best regards,
Christoph
Similar Messages
-
DMS: Objectlink to more than 50 inspection methods(QMBDOC) gives dump
Dear All,
I have a requirement of attaching more than 50 objectlink for inspection methods to one document info records.
So when i attach 40 to 50 inspection methds by BDC program or manualy & then i again try to attach one more inpection method object by clicking on F4 it gives a Runtime error RAISE_EXPECTION
Short Text: Exception condition "INVALID_DYNPROFIELD" raised.
A RAISE statement in the program "SAPLSHL2" raised the exception
condition "INVALID_DYNPROFIELD".
Since the exception was not intercepted by a superior
program, processing was terminated.
Is there any note to be applied for this.
I got a note:896655, which says i can attach upto 100 object links to a DIR, but this is giving a error after 40-50 object links when ever i click F4 for attaching more.if i manually put value in the inspection method name it takes it & also saves it.
Please advice.
Regards
Nishant..Dear Nishant,
please check if the notes 880077 and 885977 are implemented. These notes solve several object link related issues too.
Further please check the settings for object links in your customizing.
First of of it is necessary to maintain the correct screen numbers for all needed objects within the customizing. Therefore go to transaction SPRO and select
Cross-Application Components
> Document Management
> Control Data
> Maintain Screen for Object Link
Here you can enter all needed SAP objects with the name and
the related screen number. If you do not know the object or the screen number you can display a list of all SAP standard objects in transaction SE80 under function group CV130 ("Screens").
So for material master you maintain the following entry:
SAP object Screen Description Auth.
MARA 201 material master 1
Please note that the system automatically adds the leading "1" which is displayed in function group CV130 under
"Screens". So for object MARA you just have to enter 201 instead of 1201.
The value "1" in the column "Auth." is necessary to grant that always the latest dynpros and authorizations were used when linking this object to an document info record. This will avoid different problems by displaying linked documents from the object side.
The next step is to decide which objects should be used in the different document types. Therefore please go to transaction DC10 and choose the relevant document type. Afterwards please select "Define object links". Here you can
add all needed objects only by entering the object. The correct screen number is taken automatically. Also note the blue information buttons in the upper right corner which contain further necessary informations about the possible settings of the current screen.
After doing these settings in customizing you should be able to link the maintained objects to document info records and oppositely.
Important notes regarding the object link functionalities are:
880077: Performance problem using object links
885977: Extension to note 867241 on object links
926060: Extension of note 885977 for object link Purchase Order
960202: Object Links Deleted While Adding New Objects
1002648: Wrong behaviour while using RFC_CHANGE_DOCUMENT_MASTER
Best regards,
Christoph -
DMS:Object link to Purchase requesition item giving error
Dear All,
I have a requirement to attach documents in Purchase requesition item, but if i try to attach the object link in DIR from CV01N, it gives ma an error "The status RL cannot be set because no objects exist to the following links"Purchase req. item 001000399200000
But if attach a document from me51 it is attached & also can be seen from CV02N.
I have maintained the object link 'EBAN' & screen no 247 to my document type.
So where should be the problem.
Help will be Appreciated.Thanks rehman,
i have tried the 'object check' tick removing process it works but when ever i select a purchase requestion as a object link in my DIR, it only selects the purchase req. number but the item no is not selected, if i don't put the item no manually the DIR is saved with the objectlink but if u go & see in the purchase req. transaction there is no document attached to it.
When u select a purchase req. number & put the item number manually in DIR, then the document is attached in the PUR .REQ.
What would be the reason that the Pur. Req. & item no both donot appear when i select them in my DIR object link tab.
And i had four status for my Document type all had the problem of objet check, so i have removed that tick.
Regards
Nishant.... -
Hi, I am downloading DMS file using following code and the file contents are getting damaged and cannot be retieved back. I am also getting hard time to open a DMS file in seperate browser.
Can anybody please help me.
TYPES : BEGIN OF ty_ts_raw_line,
* line TYPE sdokcntbin ,
line(2550) TYPE x,
END OF ty_ts_raw_line.
DATA: ls_documentdata TYPE bapi_doc_draw2,
lv_doctype TYPE bapi_doc_aux-doctype,
lv_docnumber TYPE bapi_doc_aux-docnumber,
lv_documentpart TYPE bapi_doc_aux-docpart,
lv_documentversion TYPE bapi_doc_aux-docversion,
ls_return TYPE bapiret2,
gt_bapi_doc_files2 TYPE TABLE OF bapi_doc_files2,
gs_bapi_doc_files2 LIKE LINE OF gt_bapi_doc_files2,
lo_nd_nd_cost_rate TYPE REF TO if_wd_context_node,
lt_nd_cost_rate TYPE wd_this->elements_nd_cost_rate,
ls_nd_cost_rate TYPE wd_this->element_nd_cost_rate,
lv_string TYPE string,
lv_temp TYPE string,
lv_input_file_name TYPE string,
lv_size TYPE i ,
lt_bindata TYPE STANDARD TABLE OF ty_ts_raw_line," STANDARD TABLE OF zst_ts_raw_line,
ls_bindata TYPE sdokcntbin,
ls_drao TYPE drao,
lt_drao TYPE TABLE OF drao,
lt_files TYPE cvapi_tbl_doc_files,
ls_files TYPE cvapi_doc_file,
ls_api_ctrl TYPE cvapi_api_control,
ls_message TYPE messages,
lv_dappl TYPE draw-dappl,
lv_filename TYPE char200,
lv_filename_draw_filep TYPE draw-filep,
lv_doc_succ TYPE c,
lv_tabix TYPE sy-tabix,
lv_char_tabix(5) TYPE c,
* get message manager
lo_api_controller TYPE REF TO if_wd_controller,
lo_message_manager TYPE REF TO if_wd_message_manager,
lv_text TYPE string,
lt_tabix TYPE STANDARD TABLE OF sytabix,
lv_api_ctrl TYPE cvapi_api_control VALUE 'CV01N',
lv_documentnumber TYPE draw-doknr,
lt_drat TYPE TABLE OF dms_db_drat,
ls_drat TYPE dms_db_drat.
CONSTANTS: lc_cst(3) TYPE c VALUE 'CST',
lc_000(3) TYPE c VALUE '000',
lc_00(2) TYPE c VALUE '00',
lc_zng_test(8) TYPE c VALUE 'ZNG-TEST',
lc_desc(11) TYPE c VALUE 'Cost Rate',
lc_test(4) TYPE c VALUE 'Test',
* lc_file_path(31) TYPE c VALUE 'C:\FAKEPATH\COST_RATE_TABLE.TXT',
lc_x TYPE c VALUE 'X',
lc_blank TYPE c VALUE '',
lc_nd(2) TYPE c VALUE '&1'.
FIELD-SYMBOLS <ls_wd_assist_mt_input> LIKE LINE OF wd_assist->mt_input.
lo_api_controller ?= wd_this->wd_get_api( ).
CALL METHOD lo_api_controller->get_message_manager
RECEIVING
message_manager = lo_message_manager.
* navigate from <CONTEXT> to <ND_COST_RATE> via lead selection
lo_nd_nd_cost_rate = wd_context->get_child_node( name = wd_this->wdctx_nd_cost_rate ).
* @TODO handle non existant child
IF lo_nd_nd_cost_rate IS NOT INITIAL.
lo_nd_nd_cost_rate->get_static_attributes_table( IMPORTING table = lt_nd_cost_rate ).
ENDIF.
ls_documentdata-documenttype = lc_cst.
ls_documentdata-documentnumber = lc_cst.
ls_documentdata-documentversion = lc_00.
ls_documentdata-documentpart = lc_000.
ls_documentdata-description = lc_desc.
* ls_documentdata-
* ls_drat-dktxt = lc_desc.
* append ls_drat to lt_drat.
* clear ls_drat.
* lv_api_ctrl = 'CV01N'.
LOOP AT lt_nd_cost_rate INTO ls_nd_cost_rate WHERE row_index IS NOT INITIAL.
lv_tabix = sy-tabix.
* CALL FUNCTION 'CVAPI_DOC_CREATE'
* EXPORTING
* ps_draw = ls_documentdata " wa_documentfiles
* ps_api_control = lv_api_ctrl
* IMPORTING
* psx_message = ls_message
* pfx_doknr = lv_documentnumber.
** TABLES
** pt_drat_x = it_drat.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
documentdata = ls_documentdata
defaultclass = 'X'
IMPORTING
documenttype = lv_doctype
documentnumber = lv_docnumber
documentpart = lv_documentpart
documentversion = lv_documentversion
return = ls_return.
IF ls_return-type CA 'EA'.
ROLLBACK WORK.
ELSE.
COMMIT WORK.
ENDIF.
LOOP AT wd_assist->mt_input ASSIGNING <ls_wd_assist_mt_input> WHERE row_index = ls_nd_cost_rate-row_index.
CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
EXPORTING
buffer = <ls_wd_assist_mt_input>-file_data
IMPORTING
output_length = lv_size
TABLES
binary_tab = lt_bindata.
lv_filename_draw_filep = <ls_wd_assist_mt_input>-filename.
WHILE lv_filename_draw_filep CA '\'.
SPLIT lv_filename_draw_filep AT '\'
INTO lv_temp lv_filename_draw_filep.
ENDWHILE.
LOOP AT lt_bindata INTO ls_bindata.
CLEAR ls_drao.
ls_drao-orblk = ls_bindata-line.
ls_drao-orln = lv_size.
ls_drao-dokar = lv_doctype.
ls_drao-doknr = lv_docnumber.
ls_drao-dokvr = lv_documentversion.
ls_drao-doktl = lv_documentpart.
ls_drao-appnr = '1'.
APPEND ls_drao TO lt_drao.
CLEAR ls_drao.
ENDLOOP.
CONDENSE lv_input_file_name.
* lv_input_file_name = 'Test.txt'.
CALL FUNCTION 'CV120_DOC_GET_APPL'
EXPORTING
pf_file = lv_filename_draw_filep
IMPORTING
pfx_dappl = lv_dappl.
ls_files-appnr = '1'.
ls_files-dappl = lv_dappl.
ls_files-filename = lv_filename_draw_filep.
ls_files-updateflag = 'I'.
ls_files-langu = sy-langu.
ls_files-storage_cat = 'SAP-SYSTEM'.
ls_files-description = lv_filename_draw_filep..
APPEND ls_files TO lt_files.
CLEAR ls_files.
ls_api_ctrl-tcode = 'CV01N'.
CALL FUNCTION 'CVAPI_DOC_CHECKIN'
EXPORTING
pf_dokar = lv_doctype
pf_doknr = lv_docnumber
pf_dokvr = lv_documentversion
pf_doktl = lv_documentpart
ps_api_control = ls_api_ctrl
pf_content_provide = 'TBL'
pf_http_dest = 'SAPHTTPA'
pf_ftp_dest = 'SAPFTPA'
IMPORTING
psx_message = ls_message
TABLES
pt_files_x = lt_files
pt_content = lt_drao.
IF ls_message-msg_type CA 'EA'.
lv_doc_succ = lc_blank.
ELSE.
COMMIT WORK.
lv_doc_succ = lc_x.
CLEAR lv_text .
lv_text = <ls_wd_assist_mt_input>-comments.
ENDIF.
CLEAR: ls_api_ctrl,ls_message,lt_files[],lt_drao[].
ENDLOOP.
IF lv_doc_succ = lc_x.
ls_nd_cost_rate-dokar = lv_doctype.
ls_nd_cost_rate-doknr = lv_docnumber.
ls_nd_cost_rate-doktl = lv_documentpart.
ls_nd_cost_rate-dokvr = lv_documentversion.
ls_nd_cost_rate-comments = lv_text.
MODIFY lt_nd_cost_rate FROM ls_nd_cost_rate INDEX lv_tabix TRANSPORTING dokar doknr doktl dokvr comments.
ELSE.
APPEND lv_tabix TO lt_tabix.
ENDIF.
CLEAR ls_nd_cost_rate.
ENDLOOP.
I am also having hardtime to show DMS file on browser.Hi I've done DMS Creation like below code. Just check it .
LS_DOC-DOCUMENTTYPE = LW_DMS_APP-DOCUMENTTYPE.
LS_DOC-DOCUMENTVERSION = LW_DMS_APP-DOCUMENTVERSION.
LS_DOC-DOCUMENTPART = LW_DMS_APP-DOCUMENTPART.
LS_DOC-STATUSEXTERN = LW_DMS_APP-STATUSEXTERN.
LS_DOC-LABORATORY = ' '.
CONCATENATE WD_THIS->LW_REQ-BUKRS LS_DMS-REQ_NO LS_DMS-CR_YR INTO LW_OBJKEY SEPARATED BY '\'.
LW_DRAD-OBJECTKEY = LW_OBJKEY.
LW_DRAD-OBJECTTYPE = 'ZAPR_REQ'.
APPEND LW_DRAD TO LT_DRAD.
LW_DRAT-LANGUAGE = SY-LANGU.
LW_DRAT-DESCRIPTION = LS_STRIPPEDNAME.
APPEND LW_DRAT TO LT_DRAT.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
DOCUMENTDATA = LS_DOC
IMPORTING
DOCUMENTTYPE = LF_DOCTYPE
DOCUMENTNUMBER = LF_DOCNUMBER
DOCUMENTPART = LF_DOCPART
DOCUMENTVERSION = LF_DOCVERSION
RETURN = LS_RETURN
TABLES
DOCUMENTDESCRIPTIONS = LT_DRAT
OBJECTLINKS = LT_DRAD.
*--------Creating DMS Document Using BAPI-----------------*
IF LS_RETURN-TYPE NA 'EA'.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT = 'X'.
LS_DRAW-DOKAR = LW_DMS_APP-DOCUMENTTYPE.
LS_DRAW-DOKVR = LW_DMS_APP-DOCUMENTVERSION.
LS_DRAW-DOKTL = LW_DMS_APP-DOCUMENTPART.
LS_DRAW-DWNAM = SY-UNAME.
LS_DRAW-DOKST = LW_DMS_APP-STATUSEXTERN.
LV_STORAGE_CAT = LW_DMS_APP-STORAGECATEGORY.
LS_API_CONTROL-TCODE = 'CV01N'.
IF LF_DOCNUMBER IS NOT INITIAL.
CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
EXPORTING
BUFFER = LS_DMS_FILE-FILE_CTGRY
IMPORTING
OUTPUT_LENGTH = LV_SIZE
TABLES
BINARY_TAB = LT_BINDATA.
LOOP AT LT_BINDATA INTO LS_BINDATA.
CLEAR LS_DRAO.
LS_DRAO-ORBLK = LS_BINDATA-LINE.
LS_DRAO-ORLN = LV_SIZE.
LS_DRAO-DOKAR = LS_DRAW-DOKAR.
LS_DRAO-DOKNR = LF_DOCNUMBER.
LS_DRAO-DOKVR = LS_DRAW-DOKVR.
LS_DRAO-DOKTL = LS_DRAW-DOKTL.
LS_DRAO-APPNR = '1'.
APPEND LS_DRAO TO LT_DRAO.
ENDLOOP.
CALL FUNCTION 'CV120_DOC_GET_APPL'
EXPORTING
PF_FILE = LS_STRIPPEDNAME
IMPORTING
PFX_DAPPL = LS_FILES-DAPPL.
LS_DRAW-FILEP = LS_STRIPPEDNAME.
LS_DRAW-DAPPL = LS_FILES-DAPPL.
LS_FILES-APPNR = '1'.
LS_FILES-FILENAME = LS_STRIPPEDNAME.
LS_FILES-UPDATEFLAG = 'I'.
LS_FILES-LANGU = SY-LANGU.
LS_FILES-STORAGE_CAT = LW_DMS_APP-STORAGECATEGORY. "'ZDMS_DI'.
LS_FILES-DESCRIPTION = LS_STRIPPEDNAME.
APPEND LS_FILES TO LT_FILES.
CALL FUNCTION 'CVAPI_DOC_CHECKIN'
EXPORTING
PF_DOKAR = LS_DRAW-DOKAR
PF_DOKNR = LF_DOCNUMBER
PF_DOKVR = LS_DRAW-DOKVR
PF_DOKTL = LS_DRAW-DOKTL
PS_API_CONTROL = LS_API_CONTROL
PF_CONTENT_PROVIDE = 'TBL'
IMPORTING
PSX_MESSAGE = LS_MESSAGE
TABLES
PT_FILES_X = LT_FILES
PT_CONTENT = LT_DRAO.
IF NOT LS_MESSAGE-MSG_TYPE CA 'EA' AND
LF_DOCNUMBER IS NOT INITIAL.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ENDIF.
Regards,
Jack. -
DMS document attachment with Incoming Invoice
Hi All,
We are creating one DMS document and want to attach it to an Incoming Invoice (MIRO).
We are using the bapi BAPI_DOCUMENT_CREATE. What are the fields to pass in Objectlink.
Please help us to achieving it.
ThanksWe have created an Incoming Invoice already using 'BAPI_INCOMINGINVOICE_CREATE'. We are now creating a DMS document using 'BAPI_DOCUMENT_CREATE' and want it to be linked to the existing Invoice. For this we are trying to use the 'OBJECTLINKS' table.
The linked document should be visible in T-Code FBL1N. Can you please throw some light on how to do this?
Edited by: Himansu.P on Jun 14, 2011 3:06 PM -
Hi , I am Trying to upload file into DMS Through my module pool application Using BAPI_DOCUMENT_CREATE2 i am getting no Error message and the document number is also getting genrated but my files are not being uploded in DMS.
I am writing code below that i m using to upload file.
LOOP AT IT_FILES INTO WA_FILES.
DATA : P_FILE TYPE FILEP,
P_FILEEXT TYPE DAPPL.
DATA IT_DOCUMENT TYPE BAPI_DOC_DRAW.
DATA MESG TYPE STRING.
DATA WA_DOCUMENTDATA TYPE BAPI_DOC_DRAW2.
DATA WA_RETURN TYPE BAPIRET2.
DATA IT_DOC_FILES TYPE STANDARD TABLE OF BAPI_DOC_FILES2.
DATA WA_DOC_FILES TYPE BAPI_DOC_FILES2.
P_FILE = WA_FILES-TAB_FILE.
CALL FUNCTION 'CV120_DOC_GET_APPL'
EXPORTING
* PF_DIALOG =
* PF_DISPLAY =
PF_FILE = P_FILE
* PF_TYPDT =
IMPORTING
PFX_DAPPL = P_FILEEXT
* TABLES
* PTX_TDWP =
WA_DOC_FILES-WSAPPLICATION = P_FILEEXT.
WA_DOC_FILES-DOCFILE = WA_FILES-TAB_FILE.
APPEND WA_DOC_FILES TO IT_DOC_FILES.
CLEAR WA_DOC_FILES.
ENDLOOP.
WA_DOCUMENTDATA-DOCUMENTTYPE = 'OHD'.
WA_DOCUMENTDATA-DOCUMENTVERSION = '00'.
WA_DOCUMENTDATA-DOCUMENTPART = '000'.
WA_DOCUMENTDATA-STATUSEXTERN = 'RL'.
CONCATENATE TEXT-001 WA_ZAPPNOTE-APP_NOTE_NO INTO WA_DOCUMENTDATA-DESCRIPTION.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
DOCUMENTDATA = WA_DOCUMENTDATA
* HOSTNAME =
* DOCBOMCHANGENUMBER =
* DOCBOMVALIDFROM =
* DOCBOMREVISIONLEVEL =
* CAD_MODE = ' '
* PF_FTP_DEST = ' '
* PF_HTTP_DEST = ' '
* DEFAULTCLASS = 'X'
IMPORTING
* DOCUMENTTYPE =
DOCUMENTNUMBER = WA_ZAPPNOTE-ATTACHMENT
* DOCUMENTPART =
* DOCUMENTVERSION =
RETURN = WA_RETURN
TABLES
* CHARACTERISTICVALUES =
* CLASSALLOCATIONS =
* DOCUMENTDESCRIPTIONS =
* OBJECTLINKS =
* DOCUMENTSTRUCTURE =
DOCUMENTFILES = IT_DOC_FILES
* LONGTEXTS =
* COMPONENTS =
MODIFY ZAPPNOTE FROM WA_ZAPPNOTE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT = 'X'
* IMPORTING
* RETURN =It was some configuration problem.
-
Not able to upload file in DMS(Document Mang. system) using Web dynpro ABAP
Hi All,
I am facing a problem while uploading the file into the DMS ( Document Management System ) from Webdnrpo .
I am using the BAPI - BAPI_DOCUMENT_CREATE2 to create the document .
CASE - 1
when i am providing the storage category mention below and no data carrier1
ls_documentfiles-storagecategory = 'ZHMEL_CS'. it is not able to upload the document in the DMS system and when i check
in the debugg mode it giving error as ""Error while checking in and storing: C:\TEST.TXT "" .
CASE - 2
When i am not using the storage category and providing the the data carrier as default
ls_documentdata-DATACARRIER1 = 'DEFAULT'. It is able to create the document in the DMS but i am not able to read that document .
I checked with DMS Consultant that DMS is configured for ZOL ( documenttype) with a storage category as 'ZHMEL_CS'.
The code which i have used is below :
ls_documentdata-documenttype = 'ZOL'.
ls_documentdata-documentversion = '00'.
ls_documentdata-documentpart = '000'.
ls_documentdata-description = 'Test Document'.
ls_documentdata-laboratory = '001'.
ls_documentdata-WSAPPLICATION1 = 'TXT'.
ls_documentdata-DOCFILE1 = 'C:\TEST.TXT'.
ls_documentdata-SAVEDOCFILE1 = 'C:\TEST.TXT'.
*ls_documentdata-FILESIZE1 = 000000000000.
*ls_documentdata-FILESIZE2 = 000000000000.
ls_documentdata-WSAPPLICATION1 = 'TXT'.
ls_documentfiles-DOCUMENTTYPE = 'ZOL'.
ls_documentfiles-DOCUMENTPART = '000'.
ls_documentfiles-DOCUMENTVERSION = '00'.
ls_documentfiles-storagecategory = 'ZHMEL_CS'.
ls_documentfiles-WSAPPLICATION = 'TXT'.
ls_documentfiles-DOCPATH = 'C:\'.""lv_filename.
ls_documentfiles-DOCFILE = 'TEST.TXT'."lv_filename.
ls_documentfiles-description = 'Test Document'.
ls_documentfiles-language = 'EN'.
ls_documentfiles-CHECKEDIN = 'X'.
APPEND ls_documentfiles to lt_documentfiles .
*&----Fill Descriptions
w_descr-language = 'EN'.
w_descr-language_iso = 'EN'.
w_descr-description = 'Test'.
append w_descr to lt_descr.
clear w_descr.
**w_hostname = 'HMEL-DV1R3_DR3_00'.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
documentdata = ls_documentdata
*hostname = 'content-srv'
*pf_http_dest = 'SAPHTTPA'
*pf_ftp_dest = 'SAPFTPA'
IMPORTING
DOCUMENTNUMBER = lv_DOCUMENTNUMBER
return = gv_return
TABLES
documentdescriptions = lt_descr
documentfiles = lt_documentfiles.
Please let me know your valuable inputs on the same ..
Edited by: Omm Awasthi on Dec 30, 2010 12:22 AM
Edited by: Omm Awasthi on Dec 30, 2010 12:25 AMHi omm , from functional side your require a document type and content repository
I have used below code in a function module to create document , we have create object link as PO to the doc.
FUNCTION ZFM_SR_CREATE_FROM_EXTERNAL .
""Local Interface:
*" IMPORTING
*" VALUE(IV_DOCUMENTNUMBER) TYPE DOKNR OPTIONAL
*" VALUE(IV_DOCUMENTTYPE) TYPE DOKAR OPTIONAL
*" VALUE(IV_DOCUMENTVERSION) TYPE DOKVR OPTIONAL
*" VALUE(IV_DOCUMENTPART) TYPE DOKTL_D OPTIONAL
*" VALUE(IV_STORAGE_CAT) TYPE CV_STORAGE_CAT OPTIONAL
*" VALUE(IV_DOKST) TYPE DOKST OPTIONAL
*" VALUE(IT_DM_FILES) TYPE ZDM_TT_FILES OPTIONAL
*" VALUE(IV_EBELN) TYPE EBELN
*" EXPORTING
*" VALUE(EV_DOCUMENTNUMBER) TYPE DOKNR
*" VALUE(ES_RETURN) TYPE BAPIRET2
V00.00 DD.MM.YYYY *
*********************New Method of Uploading File*********************************
CONSTANTS path_name TYPE dms_path
VALUE '/tmp/'.
CONSTANTS log TYPE dms_path VALUE '/tmp/logFO.txt'.
DATA: ls_draw TYPE bapi_doc_draw2,
lt_documentfiles TYPE TABLE OF bapi_doc_files2,
ls_documentfiles TYPE bapi_doc_files2,
ls_dm_files TYPE zdm_files,
lv_filename TYPE string,
lv_ext TYPE string,
lv_file_type TYPE draw-dappl,
lv_file_name TYPE dms_path,
lv_msg(80) TYPE c,
lt_objectlinks TYPE TABLE OF bapi_doc_drad,
ls_objectlinks TYPE bapi_doc_drad,
lv_ebelp TYPE ebelp
Prepare Data
MOVE iv_documentnumber TO ls_draw-documentnumber.
MOVE iv_documenttype TO ls_draw-documenttype.
MOVE iv_documentversion TO ls_draw-documentversion.
MOVE iv_documentpart TO ls_draw-documentpart.
ls_draw-statusextern = iv_dokst.
ls_draw-statusintern = iv_dokst.
ls_draw-username = sy-uname.
LOOP AT it_dm_files INTO ls_dm_files.
SPLIT ls_dm_files-filepath AT '.' INTO lv_filename lv_ext.
CALL FUNCTION 'CV120_DOC_GET_APPL'
EXPORTING
pf_file = ls_dm_files-filepath
IMPORTING
pfx_dappl = lv_file_type.
TRANSLATE lv_file_type TO UPPER CASE.
OPEN DATASET log FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
TRANSFER lv_ext TO log.
ls_documentfiles-wsapplication = lv_file_type.
TRANSLATE ls_documentfiles-wsapplication TO UPPER CASE.
CONCATENATE path_name
lv_filename
lv_ext
INTO lv_file_name.
CONDENSE lv_file_name NO-GAPS.
TRANSFER lv_file_name TO log.
OPEN DATASET lv_file_name FOR OUTPUT IN BINARY MODE MESSAGE lv_msg.
*Transfer Attachment Content to Application Server
TRANSFER ls_dm_files-content TO lv_file_name.
CLOSE DATASET lv_file_name.
TRANSFER 'move data to lt_files' TO log.
ls_documentfiles-storagecategory = iv_storage_cat.
ls_documentfiles-docfile = lv_file_name.
ls_documentfiles-DOCUMENTVERSION = IV_DOCUMENTVERSION.
APPEND ls_documentfiles TO lt_documentfiles.
CLEAR lv_file_name.
CLOSE DATASET log.
ENDLOOP.
IF iv_ebeln IS NOT INITIAL.
ls_objectlinks-objecttype = 'EKPO'.
SELECT SINGLE ebelp INTO lv_ebelp FROM ekpo WHERE
ebeln = iv_ebeln
AND loekz eq space.
CONCATENATE iv_ebeln lv_ebelp INTO ls_objectlinks-objectkey.
APPEND ls_objectlinks TO lt_objectlinks.
ENDIF.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
documentdata = ls_draw
pf_ftp_dest = 'SAPFTPA'
pf_http_dest = 'SAPHTTPA'
IMPORTING
documentnumber = ev_documentnumber
return = es_return
TABLES
objectlinks = lt_objectlinks
documentfiles = lt_documentfiles.
DATA: ls_doc_data type bapi_doc_draw2,
ls_doc_datax type bapi_doc_drawx2,
ls_return type bapiret2.
Set value for document data
ls_doc_data-statusextern = 'IW'.
ls_doc_data-statusintern = 'IW'.
Set value for document data check
ls_doc_datax-statusextern = 'X'.
ls_doc_datax-statusintern = 'X'.
CALL FUNCTION 'BAPI_DOCUMENT_CHANGE2'
EXPORTING
DOCUMENTTYPE = 'ROS'
DOCUMENTNUMBER = IV_DOCUMENTNUMBER
DOCUMENTPART = IV_DOCUMENTPART
DOCUMENTVERSION = IV_DOCUMENTVERSION
DOCUMENTDATA = ls_doc_data
DOCUMENTDATAX = ls_doc_datax
HOSTNAME =
DOCBOMCHANGENUMBER =
DOCBOMVALIDFROM =
DOCBOMREVISIONLEVEL =
SENDCOMPLETEBOM = ' '
pf_ftp_dest = 'SAPFTPA'
pf_http_dest = 'SAPHTTPA'
CAD_MODE = ' '
ACCEPT_EMPTY_BOM = ' '
IMPORTING
RETURN = ls_return
TABLES
CHARACTERISTICVALUES =
CLASSALLOCATIONS =
DOCUMENTDESCRIPTIONS =
OBJECTLINKS =
DOCUMENTSTRUCTURE =
DOCUMENTFILES = lt_documentfiles.
LONGTEXTS =
COMPONENTS =
move es_return to ES_RETURN.
IF es_return-type CA 'EA' ."NE 'E' AND es_return-type NE 'A'.
"do nothing
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
ENDIF.
LOOP AT lt_documentfiles INTO ls_documentfiles.
DELETE DATASET ls_documentfiles-docfile.
ENDLOOP.
ENDFUNCTION. -
Link DMS document to Sales Order
Hello -
Currenlty, our Quality Department manually opens each applicable sales order and manually attaches a required document via the "Extras/Documents" path from within VA02 menu bar. It is extremely time consuming.
I want to know if it is possible to automatically attach a "linked document" to a sales order after it has been saved? I'd like to create/run a batch job that loops through these sales orders, and if applicable, attaches the "linked document". DMS is setup and working and the document that I need to attach is ready. I don't know where I need to put the record of this "link". I can see all of the "links" via CV03N (Object Links/Sales Document Item), but I don't know how they get there.
Any advice or link to documentation would be greatly appreciated.
Thanks,
BryanBenakaraj ES -
A few more questions with BAPI_DOCUMENT_CREATE2.
Here is the FM. Can you assist in helping me establish which parameters I need to provide?
Example:
Sales Order: 2142342 with one line item.
Document:
TYPE: ZQN (DRAW-DOKAR)
DOC: QZ6 (DRAW-DOKNR)
PART: 000 (DRAW-DOKTL)
VER: 00 (DRAW-DOKVR)
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
documentdata = ls_doc
HOSTNAME =
DOCBOMCHANGENUMBER =
DOCBOMVALIDFROM =
DOCBOMREVISIONLEVEL =
CAD_MODE = ' '
PF_FTP_DEST = ' '
PF_HTTP_DEST = ' '
IMPORTING
documenttype = lf_doctype
documentnumber = lf_docnumber
documentpart = lf_docpart
documentversion = lf_docversion
return = ls_return
TABLES
CHARACTERISTICVALUES =
CLASSALLOCATIONS =
DOCUMENTDESCRIPTIONS =
OBJECTLINKS = lt_drad
DOCUMENTSTRUCTURE =
DOCUMENTFILES =
LONGTEXTS =
COMPONENTS =
I see that there is an objectlinks table which I assume is used to create the link between the document and VA02/VA03. The underlying structure for the objectlinks table is BAPI_DOC_DRAD. I'm not clear on what values I need to add to this table when calling the BAPI_DOCUMENT_CREATE2. FM.??
Any advice on how to fill stucture BAPI_DOC_DRAD?
Also, I don't want to create any documents. The document already exists. I just want to establish a link. Can I do that without creating a document that already exists?
Thanks,
Bryan -
DMS-Object link to business partner (ISU-Module) required. Plz help.
Hi all,
I require to give an object link from DMS to Business partner of ISU module t code BP.
So checked up in SPRO- Control data- maintain key feilds, & i found that BUT001 is the transparent table which is used here. so i inserted the same in object link for my document type, but there was no screen no defined to it so i gave the screen no as 500, the tab has appeared under the objectlink tab in DIR, but the screen is not appearing, it is blank, also in the business partner Transaction the DIR table is not appearing.
What should i do? is there any other setting required, or the table which i have found is wrong. Plz help.
Regards
Tushar.Hi,
Have you solved your issue? I want to have the same link. If you have please give me a step by step description.
I saw the screen number for general business partner is 1249, maybe you can use this.
Regards Camilla -
DMS Object link for PRT Couldnot Display in CV02N
Hi PLM DMS Gurus ,
I have been investigating adding an object link for PRT which is CRVS_B screen 214. I have added this to the one document type. However, when I attempt to see the object link from the CV02N transaction, it does not appear to recognize the PRT assignment from the IA06 Change General Task List PRT Overview screen. Do any one have any idea of why this may be behaving in this way? Any feedback you can provide will be appreciated.
When I add the Documents through transaction CF02/01 then it is showing in the CV02N transaction Object link , But if I attach the same Document# through IA06 then it is not showing it.
steps to attach the document .
1. Go to IA06 select a group
2. Double click the task list and create an Operation
3. Choose the Operation and click into the PRT button in the bottom of the screen.
4 . Here you can find an option to attach your Document .
5. Once you attach note down the document number and goto CV02N and see the object Link . You will not find that .
I am doubted whether I am using the right screen number or not (CRVS_B screen 214) . Do we have any other way or anyother program & screen to show the Object link to the PRT created through IA06 .
How do we find the program and screen which is not listed in the developement class CV ?.
Any Inputs are highly appreciable and rewardable.
Thanks & regards,
Ramesh babu .PWhat you do in IA06 is using a document as an PRT. This is not the same as a objectlink between a PRT and a document. Thats why you dont see the use of the document in a tasklist in CV02n.
Regards,
Robert -
Hii Experts..
I have given one scenario.. in which i have to create one webdynpro application in which the user can upload files from the page and that files should store in the DOCUMENT MANAGEMENT SYSTEM (DMS) IN ECC. As well as the user can view the files also which is present in DMS and can when the user click on that file it will download into the local hardrive of PC.
So, If anyone knows anything regarding this, it will be really helpful to me.. kindly give ur suggestions from where should i start and what should be the logic behind this..
Thanks In advance...hi Jhings,
follow these steps
1 you need to create a document type in DMS , specific to your requrement
2 you need to write a custom function module to upload file data to application server since gui_upload will not work in case of webdynpro . inside you z function module use bapi BAPI_DOCUMENT_CHANGE2 to create document
3 to download your file to local system use function module C_DESK_DOC_GET_URL , with document number and doc type as parameter . it will generate an URL for your file , use this URL and open it in a new window using lo_window_manager->create_external_window
sample code for z function module for file upload
CONSTANTS path_name TYPE dms_path
VALUE '/tmp/'.
CONSTANTS log TYPE dms_path VALUE '/tmp/logFO.txt'.
DATA: ls_draw TYPE bapi_doc_draw2,
lt_documentfiles TYPE TABLE OF bapi_doc_files2,
ls_documentfiles TYPE bapi_doc_files2,
ls_dm_files TYPE zdm_files,
lv_filename TYPE string,
lv_ext TYPE string,
lv_file_type TYPE draw-dappl,
lv_file_name TYPE dms_path,
lv_msg(80) TYPE c,
lt_objectlinks TYPE TABLE OF bapi_doc_drad,
ls_objectlinks TYPE bapi_doc_drad,
lv_ebelp TYPE ebelp
Prepare Data
MOVE iv_documentnumber TO ls_draw-documentnumber.
MOVE iv_documenttype TO ls_draw-documenttype.
MOVE iv_documentversion TO ls_draw-documentversion.
MOVE iv_documentpart TO ls_draw-documentpart.
ls_draw-statusextern = iv_dokst.
ls_draw-statusintern = iv_dokst.
ls_draw-username = sy-uname.
LOOP AT it_dm_files INTO ls_dm_files.
SPLIT ls_dm_files-filepath AT '.' INTO lv_filename lv_ext.
CALL FUNCTION 'CV120_DOC_GET_APPL'
EXPORTING
pf_file = ls_dm_files-filepath
IMPORTING
pfx_dappl = lv_file_type.
TRANSLATE lv_file_type TO UPPER CASE.
OPEN DATASET log FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
TRANSFER lv_ext TO log.
ls_documentfiles-wsapplication = lv_file_type.
TRANSLATE ls_documentfiles-wsapplication TO UPPER CASE.
CONCATENATE path_name
lv_filename
lv_ext
INTO lv_file_name.
CONDENSE lv_file_name NO-GAPS.
TRANSFER lv_file_name TO log.
OPEN DATASET lv_file_name FOR OUTPUT IN BINARY MODE MESSAGE lv_msg.
*Transfer Attachment Content to Application Server
TRANSFER ls_dm_files-content TO lv_file_name.
CLOSE DATASET lv_file_name.
TRANSFER 'move data to lt_files' TO log.
ls_documentfiles-storagecategory = iv_storage_cat.
ls_documentfiles-docfile = lv_file_name.
ls_documentfiles-DOCUMENTVERSION = IV_DOCUMENTVERSION.
APPEND ls_documentfiles TO lt_documentfiles.
CLEAR lv_file_name.
CLOSE DATASET log.
ENDLOOP.
IF iv_ebeln IS NOT INITIAL.
ls_objectlinks-objecttype = 'EKPO'.
SELECT SINGLE ebelp INTO lv_ebelp FROM ekpo WHERE
ebeln = iv_ebeln
AND loekz eq space.
CONCATENATE iv_ebeln lv_ebelp INTO ls_objectlinks-objectkey.
APPEND ls_objectlinks TO lt_objectlinks.
ENDIF.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
documentdata = ls_draw
pf_ftp_dest = 'SAPFTPA'
pf_http_dest = 'SAPHTTPA'
IMPORTING
documentnumber = ev_documentnumber
return = es_return
TABLES
objectlinks = lt_objectlinks
documentfiles = lt_documentfiles.
DATA: ls_doc_data type bapi_doc_draw2,
ls_doc_datax type bapi_doc_drawx2,
ls_return type bapiret2.
Set value for document data
ls_doc_data-statusextern = 'IW'.
ls_doc_data-statusintern = 'IW'.
Set value for document data check
ls_doc_datax-statusextern = 'X'.
ls_doc_datax-statusintern = 'X'.
CALL FUNCTION 'BAPI_DOCUMENT_CHANGE2'
EXPORTING
DOCUMENTTYPE = 'ROS'
DOCUMENTNUMBER = IV_DOCUMENTNUMBER
DOCUMENTPART = IV_DOCUMENTPART
DOCUMENTVERSION = IV_DOCUMENTVERSION
DOCUMENTDATA = ls_doc_data
DOCUMENTDATAX = ls_doc_datax
HOSTNAME =
DOCBOMCHANGENUMBER =
DOCBOMVALIDFROM =
DOCBOMREVISIONLEVEL =
SENDCOMPLETEBOM = ' '
pf_ftp_dest = 'SAPFTPA'
pf_http_dest = 'SAPHTTPA'
CAD_MODE = ' '
ACCEPT_EMPTY_BOM = ' '
IMPORTING
RETURN = ls_return
TABLES
CHARACTERISTICVALUES =
CLASSALLOCATIONS =
DOCUMENTDESCRIPTIONS =
OBJECTLINKS =
DOCUMENTSTRUCTURE =
DOCUMENTFILES = lt_documentfiles.
LONGTEXTS =
COMPONENTS =
move ls_return to ES_RETURN.
if ls_return-ID = '26' and LS_RETURN-NUMBER = '003'.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
documentdata = ls_draw
pf_ftp_dest = 'SAPFTPA'
pf_http_dest = 'SAPHTTPA'
IMPORTING
documentnumber = ev_documentnumber
return = es_return
TABLES
objectlinks = lt_objectlinks
documentfiles = lt_documentfiles.
move es_return to ES_RETURN.
endif.
IF es_return-type CA 'EA' ."NE 'E' AND es_return-type NE 'A'.
"do nothing
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
ENDIF.
LOOP AT lt_documentfiles INTO ls_documentfiles.
DELETE DATASET ls_documentfiles-docfile.
ENDLOOP. -
Dear team,
We have written one Zprogram for linking some vendor codes to DMS conraol number ,my Zprogram is working fine,
when i execute that report vendors are sitting in objects of Document contraol number , But When I go to vendor screen XK03 the same dcouemnt number is not appearing ( message is No assignments found).
I have used below 2 function modules
wa_objectlinks-objecttype = 'LFA1'.
wa_objectlinks-objectkey = wa_final-lifnr.
APPEND wa_objectlinks TO it_objectlinks.
CALL FUNCTION 'BAPI_DOCUMENT_CHANGE2'
EXPORTING
documenttype = 'VEN'
documentnumber = wa_final-doknr
documentpart = '000'
documentversion = '00'
documentdata = ls_doc_data
documentdatax = ls_doc_datax
IMPORTING
return = ls_return
TABLES
characteristicvalues = lt_chr_val
classallocations = lt_cls_aloc
objectlinks = it_objectlinks.
IF sy-subrc = 0.
IF ls_return IS INITIAL.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
iuuse is why documents are not appearing in XK03.
SivaHi Siva,
based on your description I would kinldy ask you to check if there is an entry created in table DRAD for this document info record. Because in this table the link data is stored for each link between a document info record and the linked object.
To grant that allways the currenct screens and authorizations were
called please maintain also the value "1" into the "Authorization"
column. For further informations on this maintainance please see the
SAP note 1066915. It's important that you not enter the mentioned
screen number wihtout the leading "1" as this number is added
automatically by the system (e.g. object MARA 1201 maintain like MARA
201). You can do this in customizing under:
Transaction SPRO
> Cross-Application-Component
> Document Management
> Control Data
> Define screen for object links
If you need the dynpro number or object you will find all standard SAP
objects and their screen number in function module CV130 (Screens) by
transaction SE80. Please maintain all necessary SAP objects.
Best regards,
Christoph -
DMS interface program required
Dear all,
We are implenting DMS in our organisation for which , I have a requirement where in I need to make a program (interface) which can attach & send the scanned image of objects (Ex: Invoice) to a specific location on DMS server.
The data on DMS will be archived data.
Any help in the designig of the program will be of great help from any of you.
Regards
AnkurHi,
In the DMS interface I did, I used FM: 'BAPI_DOCUMENT_CREATE2'.
And there is a Note: Note 504692, you could check it out, in this Note, you can find the sample code below:
CALL FUNCTION 'BAPI_DOCUMENT_CHANGE2'
EXPORTING
DOCUMENTTYPE = ls_draw-dokar
DOCUMENTNUMBER = ls_draw-doknr
DOCUMENTPART = ls_draw-doktl
DOCUMENTVERSION = ls_draw-dokvr
DOCUMENTDATA = ls_Doc
DOCUMENTDATAX = ls_docx
HOSTNAME =
DOCBOMCHANGENUMBER =
DOCBOMVALIDFROM =
DOCBOMREVISIONLEVEL =
SENDCOMPLETEBOM = ' '
PF_FTP_DEST = 'SAPFTPA'
PF_HTTP_DEST = 'SAPHTTPA'
CAD_MODE = ' '
IMPORTING
RETURN = ls_return
TABLES
CHARACTERISTICVALUES =
CLASSALLOCATIONS =
DOCUMENTDESCRIPTIONS =
OBJECTLINKS =
DOCUMENTSTRUCTURE =
DOCUMENTFILES = lt_documentfiles_new
LONGTEXTS =
COMPONENTS =
IF ls_return-type CA 'EA'.
ROLLBACK WORK.
MESSAGE ID '26' TYPE 'I' NUMBER '000'
WITH ls_return-message.
ELSE.
COMMIT WORK and wait.
ENDIF.
Cheers -
GOS 'Create Attachment' - Can we archive it to DMS?
Greetings All!
I know for sure that if we store using 'create attachment', these are stored in the database. If you store using "store business document" these can be stored in the content server. Is there anyway we can route create attachments to DMS instead of DB?
NOTE - Currently we have greyed out create attachments to stop users from using create attachments as our SOC3 and SOFTCONT1 tables are rapidly increasing.
All your help is much appreciated.
Regards
SriHello Travis,
If I understood Sri Latha posting correctly she wanted to store the documents in the DMS rather than in DB(SOC3 table) whenever a document is attached.
I have very limited knowledge SAP DMS as I am more into ABAP & OT. So it is because of you I took 2 days to understand & configure SAP DMS and 2 hours to code for possibility check for storing the documents in the DMS. For which I am happy .
Before going a ahead I checked SOC3 table enteries to be "587.055".
In had take "SGOSATTR" to SM30 to see what is the class that responsible for attaching and displaying the documents and found
Now I copied them to ZCL_GOS_SRV_ATTACHMENT_CREATE & ZCL_GOS_SRV_ATTACHMENT_LIST respectively. To comment their "Execute" method code and placed the custom code.
I had hard coded the location from where the document needs to picked up from.
I had put code such a way that document once stored get's display CV02n
Now I want to see the attachment(yet to adjust code to display as attachment currently displaying in other window).
In my previous posting I though referring the other answer would give a clue of modifying the respective class of the GOS menu's. Sorry, for confusing.
Now when I checked for the SOC3 table entries they are still "587.055". Which means they are not storing any more in DB(as per my limited knowledge )
Below is the raw code just checking the possibility :
ZCL_GOS_SRV_ATTACHMENT_CREATE(EXECUTE method)
DATA: ls_doc type bapi_doc_draw2,
ls_return type bapiret2.
DATA: lf_doctype Type bapi_doc_draw2-documenttype,
lf_docnumber Type bapi_doc_draw2-documentnumber,
lf_docpart Type bapi_doc_draw2-documenttype,
lf_docversion Type bapi_doc_draw2-documenttype.
DATA: lt_files Type table of bapi_doc_files2 ,
lt_drat Type table of bapi_doc_drat ,
lt_drad Type table of bapi_doc_drad ,
ls_files Type bapi_doc_files2,
ls_drat Type bapi_doc_drat,
ls_drad Type bapi_doc_drad.
ls_doc-documenttype = 'YBO'.
ls_doc-documentversion = '00'.
ls_doc-documentpart = '000'.
ls_doc-statusextern = 'IA'.
ls_doc-laboratory = '002'.
REFRESH lt_files.
CLEAR lt_files.
ls_files-sourcedatacarrier = '%COMPUTERN'.
ls_files-storagecategory = 'DMS_C1_ST'.
ls_files-docfile = 'C:\Users\Administrator\Documents\MARK_TRAVIS\TESTING_of_ MARK_TRAVIS_request.doc'.
ls_files-wsapplication = 'DOC'.
APPEND ls_files to lt_files.
CLEAR lt_drat.
REFRESH lt_drat.
ls_drat-language = 'EN'.
ls_drat-description = 'TESTING_of_ MARK_TRAVIS_request'.
APPEND ls_drat to lt_drat.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
documentdata = ls_doc
IMPORTING
return = ls_return
TABLES
documentdescriptions = lt_drat
documentfiles = lt_files.
IF ls_return-type CA 'EA'.
ROLLBACK WORK.
WRITE : ls_return-message.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = '9'.
DATA: doknr TYPE doknr.
GET PARAMETER ID 'CV1' FIELD doknr.
CALL TRANSACTION 'CV02N' AND SKIP FIRST SCREEN.
ENDIF.
ZCL_GOS_SRV_ATTACHMENT_LIST(EXECUTE method)
data: lt_stdokar type STANDARD TABLE OF CV100_RANGESDOKAR ,
ls_stdokar type CV100_RANGESDOKAR,
lt_stdoknr type STANDARD TABLE OF CV100_RANGESDOKNR ,
lt_stdokvr type STANDARD TABLE OF CV100_RANGESdokvr ,
lt_stdoktl type STANDARD TABLE OF CV100_RANGESdoktl ,
lt_stdwnam type STANDARD TABLE OF CV100_RANGESdwnam ,
lt_stbegru type STANDARD TABLE OF CV100_RANGESbegru ,
lt_staennr type STANDARD TABLE OF CV100_RANGESaennr,
lt_stlabor type STANDARD TABLE OF CV100_RANGESlabor ,
lt_stdktxt type STANDARD TABLE OF CV100_RANGESDKTXT .
DATA dttrg TYPE draw-dttrg.
DATA dappl TYPE draw-dappl.
DATA status TYPE tdwst-stabk.
DATA stseit TYPE mcdok-stseit.
DATA stbis TYPE mcdok-stbis.
DATA slng TYPE rsfin-langu.
DATA restrict TYPE anzhl_s.
DATA gf_cs_active TYPE sy-datar.
DATA cklah TYPE klah.
DATA g_folder_key TYPE bapi_doc_keys.
DATA srcdrad TYPE STANDARD TABLE OF seldrad.
DATA ls_srcdrad TYPE seldrad.
DATA searchtab_orig TYPE STANDARD TABLE OF fist .
DATA ls_searchtab_orig TYPE fist .
DATA lt_loedk_ranges TYPE TABLE OF cv100_rangesloedk.
DATA ls_loedk_ranges TYPE cv100_rangesloedk.
DATA lt_cadkz_ranges TYPE TABLE OF cv100_rangescadkz.
DATA ls_cadkz_ranges TYPE cv100_rangescadkz .
DATA lt_tdraw TYPE STANDARD TABLE OF draw .
DATA ls_tdraw TYPE draw.
DATA lt_ccomw TYPE STANDARD TABLE OF comw.
DATA ls_ccomw TYPE comw .
stseit = 00000000.
slng = 'E'.
restrict = 100.
gf_cs_active = 'X'.
ls_stdokar-sign = 'I' .
ls_stdokar-option = 'EQ'.
ls_stdokar-low = 'YBO'.
APPEND ls_stdokar to lt_stdokar .
ls_loedk_ranges-sign = 'I'.
ls_loedk_ranges-option = 'EQ'.
ls_loedk_ranges-low = ' '.
APPEND ls_loedk_ranges to lt_loedk_ranges.
ls_loedk_ranges-sign = 'I'.
ls_loedk_ranges-option = 'EQ'.
ls_loedk_ranges-low = 'X'.
APPEND ls_loedk_ranges to lt_loedk_ranges.
ls_cadkz_ranges-sign = 'I'.
ls_cadkz_ranges-option = 'EQ'.
ls_cadkz_ranges-low = ' '.
APPEND ls_cadkz_ranges to lt_cadkz_ranges.
ls_cadkz_ranges-sign = 'I'.
ls_cadkz_ranges-option = 'EQ'.
ls_cadkz_ranges-low = 'X'.
APPEND ls_cadkz_ranges to lt_cadkz_ranges.
CALL FUNCTION 'DMS_DOCUMENT_RETRIEVAL_ALV'
EXPORTING
sdttrg = dttrg
sappli = dappl
sdoksa = status
sdatum1 = stseit
sdatum2 = stbis
slanguage = slng
restrict = restrict
pf_cs_active = gf_cs_active
classno = cklah-class
classtype = cklah-klart
folder_key = g_folder_key
TABLES
objectlinks = srcdrad
searchtext = searchtab_orig
stdokar = lt_stdokar
stdoknr = lt_stdoknr
stdokvr = lt_stdokvr
stdoktl = lt_stdoktl
stloedk = lt_loedk_ranges
stcadkz = lt_cadkz_ranges
stdwnam = lt_stdwnam
* stbegru = lt_stbegru
** staennr = lt_staennr
* stlabor = lt_stlabor
* stdktxt = lt_stdktxt
* tdraw = lt_tdraw
clsc_class_selection = lt_ccomw
EXCEPTIONS
parameter_insufficient = 2.
Hope this help's you understand this time. Please feel free to comment on any thing.
Thanks,
Kolusu -
QM certificate object can be link with DMS?
Hello guys!
I have the requirement to have the quality certificates available in DMS.
I am looking the DMS customizing, but I cannot find any standard object link for that purpose.
I was trying to create my own object link, I defined my own screen in SE51 but now I don't know how to implement it like subscreen of SAPLCV130 Screen1500.
Any one can tell me if there is an standard object or how I can link my screen to the program SAPLCV130?
Thanks in advance for your helpHi Ravindra,
Thanks for your question, this clarify part of my problem.
Now I am trying to link it myself creating an objectlink and a screen in abap.
I know 3 part have to be implemented:
1. Create the object
2. Create the subscreen
3. Develop the Badi.
The 1st and the 3rd are already done....but I don't how how to create the subscreen and the link it to SAPLCV130.
If I create a subscreen 9001 with program SAPLCV130 a reparing code is needed, so I don't know if this is the correct way or if there is another way to do it without touching the standard program.
Thanks and Best Regards
Maybe you are looking for
-
Error message while displaying a Workbook in Portal
Hello, We have a Workbook with 5 Queries in ech sheet. When we open the Query from Portal it displays the error message that 1. Query was changed! Characterisitc no longer exists 2. Invalid filter on CUST_SD: Filter changed I opned the Workbook direc
-
How to render animation to a MP4 format or something else?
Hello. I usually render my animation to uncompressed AVI because after it I have to render it again with different software for video motage. So there wasn't any problem. But today I have to render my animation directly from After Effects. So I can't
-
Airport Express as travel router?
Going to Europe for an extended stay. The apartment has ethernet but no wireless. I'm looking for a small wireless router to take and use. Of course, it would need to work on 220V (and 110 when I get back home). It would need to be secured (WAP?) and
-
Oracle ERP Application Security
One of my clients said he want to move Oracle ERP Applications to the Internet. So what security issues should I think about?
-
"Unable to connect to iTunes Store" 90% of the time
I have a 3rd Gen iPad with wifi only that I bought about 40 days ago. Initially I had no problem downloading and updating apps but in the past few weeks I get "unable to connect to iTunes Store" over 90% of the time. I always verfity the Internet