DMS originals distribution by fax

Hello!
When I try to distribute DMS (CVI8) using fax as distribution type, no originals are distributed - only cover page is received.
I tried different file formats.
I put * as "workstation application".
I didn't find any relevant SAPNotes or Help topics.
Does anyone have an idea what can be wrong?
Thank you in advance!
Message was edited by: Michael Khalemsky

Hi,
Kindly refer to the following link for document distribution.
http://wiki.sdn.sap.com/wiki/display/PLM/DocumentManagement(CA-DMS)
Regards
Abhishek

Similar Messages

DMS Originals

Hi
I'm hoping someone can help me.
I've read through hundred's of posts now and spent all day trying to solve this issue.
I know it's something stupid I'm missing but just can't find it.........
I have two Document Types SPC (Specifications) and HAS (Health and Safety).
SPC is setup and working with no issues, I can check documents in and send them out on review with no workflow issues. However I've used SPC as a template for HAS and on creation of document type HAS everything looks fine apart from the Originals section/tab is not available on document type HAS.
Can someone please tell me what it is I'm missing that makes the oringials tab or section at the bottom of the screen on CV01N not appear.
Thanks in advance.
Chris

Hi Chris,
You have missed the "WS Application 1" & "WS Application 2" while configuring document types. Keep these two fields blank and you will get these fields in dms screen for attaching originals.
I hope this will resolve the query.
Regards,
Ravindra

DMS Document Distribution Problem Pls, Help Will be appreciated

When executing T-Code CVI8(Document Distribution), there is a system message that the order was successfully created. But when we looked at the distribution log using T-Code CVI9, the status of the document remains as SY and the processing of the distribution stops. We already finished the settings for document distribution and still this error persists. What could have been wrong? Pls advice.
Mail Me On:- [email protected]
Regards,
Akshit A. Patel

Hi Athol,
i have checked the workflow config accordingly,
workflow templates 20000104 and 20000137. are active.
a. 20000104 BUS1082 x 2 (Initiated and Resend)
b. 20000137 BUS1082002 x 1 (Resend)
But the Release status for these templates is NOT DEFINED, should it be RELEASED & the container tab for 20000104 shows a warning icon(Mandatary import parameter)on partial order & intial value not set & same for 20000137 shows warning icon on distribution order package & initial value not set.
what does this mean, is there any setting required for this?
2. Transaction SWU3 ensure that all has been generated (activated). Pay special attention to Maintain Runtime Environment -> Configure RFC destination.
I HAVE checked the above all are active except Configure RFC destination, what is the setting required for the same.
the 3, 4,& 5 setting what u have suggested are ok,i have checked them.
Please suggest for the 1 & 2 points.
thanks in advance.

DMS-Document Distribution Setup

Hello ,
I would appreciate if any one can give me some idea's on config part of Document Distribution in Document management system.
I maintained recipeint list and in CVI8 i started document distribution which gave me back an internal order number later i went to CVI9 to execute the initial order number which took me to Distribution log screen .
There i get message like Not assigned to distr. order package,i selected the Box highlighted pertiaing to that document and i executed for document distribution i received a message like Only partial orders with status AS, MA, ER, WO, or WR are allowed.
Guys sorry i may be wrong with the approach on the above step i carried out but can u breif me up what i should have to config and acheive my document distribution succesfull.
Regards,
Murali.S
Points will be awarded for sure.

Hi Murali,
please implement the attached note 1008281 which should solve this
behaviour.
Further please go to the swdd transaction and enter the following worklow
templates (WS20000104 and WS20000137).Go to the edit mode and activate
them once again.
Best regards,
Christoph

DMS - need to check out originals using BSP

Hi,
I am trying to check out DMS originals through a BSP application. For this purpose, I use the function module 'BAPI_DOCUMENT_CHECKOUTVIEW2'. When this FM is used in a SAP GUI report program, the originals are checked out into the TEMP directory. But when the same FM is used in a BSP application, the FM fails with the exception 'Document Program not started via RFC. No return possible'.
Alternatively, I tried using the method 'checkoutview' (in the class 'cl_incl_doc_files'). The method executes without any error, but it does not check out the originals. The original is not available in the 'TEMP' directory. Will this method check out originals to the 'TEMP' directory?? If so, is there any specific thing that needs to be set? Have anyone tried using this?
My requirement is that the originals need to be downloaded to the local machine.
Any help is highly appreciated.
Regards,
Vidhya.

Dear Pranav,
I checked these settings. They are already maintained in SM59. Still it is not working out. I tested the connection also and it is fine. What else could be the reason??
I am also trying an alternate method. I am first downloading the contents of the file (in binary format) into an internal table using the function module 'SDOK_PHIO_LOAD_CONTENT'. Then, by calling the function module 'GUI_DOWNLOAD', I try to download it as a PDF file. Again, when I try this in a report program, it is successful .When the function 'GUI_DOWNLOAD' (or the method 'cl_gui_frontend_services=>gui_download') is called from a BSP application, it throws the exception 'CONTROL_FLUSH_ERROR'. Is it because through BSP application we cannot download to the local machine?? Is there any other way to achieve this?? I tried all possible ways. In no method, I get full solution.
This is urgent. Highly appreciate your help.
Regards,
Vidhya.

Business Objects Demo documents

Hi All,
Client has requested for a demo on Business object reporting features. Due to system constraints and short time frame, we are looking for demo of Business Objects reporting features that can be presented to the client.
Architecture
Proposed solution features BOBJ XI 3.1 SP2 as a front End Reporting Tool with SAP BW 7.0 as the back end data warehouse tool. SAP ECC 6.0 acts as the source system for SAP BW for all the data requirements.
ECC 6.0 -SAP BW 7.0-SAP BOBJ XI 3.1- EP
Reports are created on top of SAP BW 7.0 using SAP Business Objects XI 3.1 SP2 tools ( Xcelsius, Web Intelligence and Crystal reports) as front end reporting tool . User will be accessing the reports from Enterprise Portal.
Do we have any demo representation of the BOBJ reporting features (reports are accessed from EP) on a end user perspective? The demo would feature the following scenario
1) User logging into Enterprise portal and accessing the reports created and published using Business Objects tools ( Single Sign On).
2) Report opens up with different I-views in one web page. The different I-views shall be based on reports created using different BOBJ tools ( Xcelsius, Web Intelligence and Crystal reports) .
3) Possible navigational features possible in these reports . Example can be
a.     Switch to graphical representation from table format
b.     Save data into excel format
c.     Drill down/Slice and Dice in reports
d.     Summarized and detail level of data
e.     Insert calculations
f.     Add rows and columns to tables
g.     Formatting report
h.     Other navigation features
4) Create ad hoc reports using WebI and publishing the reports in Portal Favorites?
5) Distribution of reports
If you have any related documents, would you be able to share with us.
Regards,
Manesh

Hi Nicolai,
in this case you have to implement within ABAP a class for the SES interface.
Within this class you have to fetch the document content and store it in an attribute for SES.
This class implementation will be used by SES Framework to send it to TREX for indexing and searching.
So this is a customer ABAP development project based on SES Framework.
This is also done within the SAP Consulting Solution mentioned in Hinweis 1332745 - trex based document search with classification support.
Here the DMS originals are indexed with the DRAW data within SES.
So have a closer look how to use and implement own classes for SES in help.sap.com.
Best regards
Frank

Cc in work flow mail is required..

Hi,
cc in work flow mail is required.Please help me..
Balaji.T

In the function module SO_NEW_DOCUMENT_SEND_API1 if you see the table parameter RECEIVERS you have field COPY, you can mark it as 'X' for the user who should be copied to. Now since user can belong to any of the following categories. If you are using SAP inbox then use the first category.
SAP user name of the recipient
SAPoffice name of the recipient
Shared distribution list
Fax number in the form of structure SADRFD
Internet address in the form of structure SADRUD
Remote SAP name in the form of structure SADR7D
X.400 address in the form of structure SADR8D
You can directly invoke the function module whenever you want to send an eamil. I hope this answers your question.
Regards,
Kartik Nayak
Message was edited by:
KARTIK Nayak

EasyDMS and Archive Link

Hi,
any idea, if it is possible to Checkin documents to Archive Link via easyDMS?
Thanks for any answer!
best regards
Dieter

Hi Dieter,
as I know there are no restrictions for a specific storage type. Each storage type which is available in the backend system should also work with EasyDMS too.
However I would recommend you to use the Content Server for storing DMS originals.
Best regards,
Christoph

Send mail (Urgent)

HI guys,
Please look at the coding below..
l_wa_recieve-receiver = '[email protected]'. " this is the distribution list id "with number of mail ids inside it
l_wa_recieve-rec_type = 'C'. "shared dis list
APPEND l_wa_recieve TO l_it_recieve.
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
EXPORTING
document_data = "ERROR'
document_type = 'DLI'
put_in_outbox = c_x
commit_work = c_x
TABLES
object_content = l_it_content "this table contains the body of email
receivers = l_it_recieve " this is above
EXCEPTIONS
too_many_receivers = 1
document_not_sent = 2
document_type_not_exist = 3
operation_no_authorization = 4
parameter_error = 5
x_error = 6
enqueue_error = 7
OTHERS = 8.
Can you just tell me whether it works fine.. And if it is correct how much time will it take to get email in my respective email address..
I have run this FM by just giving my mail id (not distribution list just giving doctype = 'RAW instead of DLI)
The FM ran sucessfully without any errors , But I didnot receive any mail in my mail Inbox..
Can you please help me how to sort it out getting mail in less time..
Points will be rewarded
regards,
nazeer

Hi Nazeer,
 This will work fine.but If u are not getting mail just go through this documentation.This will help u find out the error.
Functionality
This function module enables you to send a new document, which has not yet been created, internally and externally. During the send process the document is created, along with the attributes and content that are to be transferred.
Import parameters
DOCUMENT_TYPE
Default = 'RAW'.
Document class. All classes are possible except for folders ('FOL') and distributions lists ('DLI').
PUT_IN_OUTBOX
Default = ' '.
If this flag is activated ('X'), the newly created document is also placed in the outbox of the active user when it is sent.
DOCUMENT_DATA
This structure must contain the attributes of the document to be sent.
OBJ_NAME
Name of document.
OBJ_DESCR
Title (short description) of document.
OBJ_LANGU
Language of document.
OBJ_SORT
Sort field of document. You can search for this term using attribute search.
OBJ_EXPDAT
Expiry date of document. The document itself cannot expire, but each time the document is entered in a folder, this date is used as the default for the expiry date of the entry (field EXPIRY_DAT).
SENSITIVTY
Document sensitivity.
A private document can have the following levels of sensitivity:
'O' : Standard, normal sensitivity
'F' : Functional, can be forwarded functionally
'P' : Confidential, not visible to substitutes
For documents in shared folders, only sensitivity level 'O' is permitted.
OBJ_PRIO
Recipient priority. The document itself does not have a priority level, but each time the document is entered in a folder, this value is used as the default for recipient priority for the entry (field PRIORITY).
NO_CHANGE
If this flag is activated ('X'), documents in shared folders can only be changed by the author. The author can change documents in private folders after they have been sent.
PRIORITY
Recipient priority for the folder entry. This value gives the priority, which was assigned to the document by the owner, after receipt.
EXPIRY_DAT
Expiry date of the folder entry. When the expiry date has been reached or passed, the entry is placed in private trash and can be retrieved from there if needed, up until the next time the trash is emptied. A new folder entry is initially given the expiry date of the document from field OBJ_EXPDT.
PROC_TYPE
If this field does not contain the default value (default is ' '), the document can be processed.
The following entries are permitted:
'D' : Dialog module
'F' : Function module
'R' : Report
'S' : Report with transfer of values to global memory
'T' : Transaction
'U' : Transaction with transfer of values to global memory
PROC_NAME
Processing element. You must enter the name of the dialog module, function module, report or transaction in accordance with the entry in the field PROC_TYPE.
PROC_SYST
Name of sytem in which the document is to be processed. If no system is specified or '*' is entered, processing is possible in all systems.
PROC_CLINT
Client in which the document is to be processed. If no client is specified or '*' is entered, processing is possible in all clients.
SKIP_SCREN
If this flag is activated ('X'), the first screen is skipped during processing.
TO_DO_OUT
If this flag is activated ('X'), the document cannot be processed from the SAPoffice interface. You must use the API function module SO_DOCUMENT_SET_STATUS_API1.
FREE_DEL
If this flag is activated ('X'), you can delete the document from external folders using the API.
DOC_SIZE
Size of the document in bytes. For PC documents, the size of the relevant file should be entered, for RAW and SCR documents the size is the "length of the last line" + "number of other lines multiplied by 255".
Export parameters
NEW_OBJECT_ID
Object ID of the document created during the send process.
SENT_TO_ALL
If this flag is activated ('X'), the document was sent to all specified recipients or, in the case of external forwarding, the corresponding send requests were delivered to the subsystem. If sending or delivery failed in one or more cases, the flag is not activated.
Table parameters
OBJECT_HEADER
This table must contain the document class-relevant data. For example, SAPscript documents store information here about forms and styles, Excel list viewer documents store, amongst other things, the number of rows and columns and PC documents store their original file names.
LINE
Requires class-relevant document information line by line.
OBJECT_CONTENT
This table must contain the actual content of the document.
LINE
Requires the content of the document line by line.
OBJECT_PARA
This table is used only by documents that are to be processed. It must contain the SET/GET parameter that is transferred to the processing element.
NAME
Name of the SET/GET parameter. Only the first three characters are used.
OPTION
This field is not used.
LOW
Requires the value of the parameter in NAME.
HIGH
This field is not used.
OBJECT_PARB
This table is only used by documents to which a particular processing type is assigned. The meaning of the table depends on the processing type. If the processing element is a report, or transaction with transfer of values to the global memory, the table content is interpreted as the quantity of parameters with the relevant values and exported to the memory ID taken from the first row. If the processing element is a function module or a dialog module, the table is transferred to this as table parameter MSGDIAL.
NAME
If the processing element is a report or a transaction with transfer of values to the global memory, the field of the first row of the table must contain the name of the memory ID used for the export. The fields of the other rows accommodate the parameter names. If the processing element is a function module or a dialog module, the fields must contain values corresponding to the use of the module.
VALUE
If the processing element is a report or a transaction with transfer of values to the global memory, the field for the first row of the table must remain empty. The fields for the other rows accommodate the values belonging to the parameters in NAME. If the processing element is a function or dialog module, the fields must contain values corresponding to the use of the modules.
RECEIVERS
This table must contain the document recipients.
RECEIVER
Name of recipient.
The following entry categories are possible:
SAP user name of the recipient
SAPoffice name of the recipient
Shared distribution list
Fax number in the form of structure SADRFD
Internet address in the form of structure SADRUD
Remote SAP name in the form of structure SADR7D
X.400 address in the form of structure SADR8D
ADR_TYPE
Type of RECEIVER entry.
The following values are permitted:
'B' : SAP user name
' ' : SAPoffice name
'C' : Shared distribution list
'F' : Fax number
'U' : Internet address
'R ' : Remote SAP name
'X' : X.400 address
REC_ID
If the recipient is a SAPoffice user, the user ID, instead of the recipient name in RECEIVER, can be entered in this field.
REPLY_DOC
If there is a value in this field, the document is a reply to the folder entry identified by the specified ID. A correspondence history is automatically created/continued.
REC_DATE
The date on which the document is to reach the recipient. This date cannot be guaranteed for external recipients as it depends on connected products.
PROXY_ID
If automatic forwarding is active in the recipient's system, this field contains the SAP user ID or the address ID of the external address to which the document was ultimately sent.
RETRN_CODE
When the recipient has received the document, the function module enters the value '0' in this field. If the document is not successfully received, a value unequal to '0' is entered in the field.
EXPRESS
If this flag is activated ('X'), the document is sent with the attribute 'express'. If the recipient is a SAPoffice user who is logged on, he or she receive a message immediately, saying that he or she has received an express mail.
COPY
If this flag is activated ('X'), the document is sent with the attribute 'copy'.
BLIND_COPY
If this flag is activated ('X'), the document is sent with the attribute 'secret copy'. If the recipient is a SAPoffice user, he or she can neither print nor forward the document.
NO_FORWARD
If this flag is activated ('X') and the recipient is a SAPoffice user, he or she cannot forward the document.
NO_PRINT
If this flag is activated ('X') and the recipient is a SAPoffice user, he or she cannot print the document.
TO_ANSWER
If this flag is activated ('X') and the recipient is a SAPoffice user, the user must reply to the document before he or she can delete it from his or her inbox.
TO_DO_EXPL
If this flag is activated ('X') and the recipient is a SAPoffice user, the user must process the document before he or she can delete it from his or her inbox.
TO_DO_GRP
If this field contains a value between '1' and '9', a SAPoffice user in the recipient group indicated by this number must process the document before the recipients can delete it from their inboxes. If the value '0' is entered, the document does not need to be processed.
COM_TYPE
Communication method used to send the document. This field is only relevant if the recipient is an address number, that is, if the document is sent externally via address management. If the field is empty, the standard communication type specified in address management is used.
The following values are permitted:
'INT' : Send via Internet
'FAX' : Send as a fax
'X40' : Send via X.400
'RML' : Send in another SAP system
LFDNR
Current number from address management. This field is only relevant if the recipient is an address number, that is, if the document is sent via address management. If the field is empty, the default current number in address management is used.
FAX
This field is not used.
COUNTRY
This field is not used.
SPOOL_ID
This field is not used.
NOTIF_DEL
If this flag is activated ('X'), the sender receives confirmation when the recipient receives the document. He or she also receives a message if the document could not be delivered. This flag should only be activated for external sending, since internal sending is synchronous. Confirmation is only supported by a small number of mail systems, however. For example: X.400 and SAP SAP.
NOTIF_READ
If this flag is activated ('X'), the sender is notified as soon as the recipient has read the document. This flag should only be activated for external sending, since internal sending is synchronous. Read notification is only supported by a small number of mail systems, however. For example: X.400 and SAP SAP.
NOTIF_NDEL
If this flag is activated ('X'), the recipient receives a message if the document could not be delivered to the recipient. This flag should only be activated for external sending, since internal sending is synchronous. The message is only supported by a small number of mail systems, however. For example: X.400 and SAP SAP.
SAP_BODY
If this flag is activated ('X'), SAP specific data is transferred to the document in an external body part when sending via X.400. This flag should only be activated if the target system is an SAP System.
Exceptions
TOO_MANY_RECEIVERS
Too many recipients were specified. The active user does not have authorization to send to this number of recipients.
DOCUMENT_NOT_SENT
The document could not be sent. It was not delivered to any of the specified recipients.
DOCUMENT_TYPE_NOT_EXIST
The document class specified does not exist or is not permitted.
OPERATION_NO_AUTHORIZATION
The document was not allowed to be sent because one of the required authorizations did not exist.
PARAMETER_ERROR
The combination of parameter values transferred to the function module was not a permitted combination.
X_ERROR
Am internal error or a database inconsistency has occurred.
ENQUEUE_ERROR
A lock required for the send process could not be set. It is probable that another user is processing.
Example
Sending a confidential RAW document to an internal user and an Internet address. The new document is also placed in the sender's outbox.
DATA: OBJCONT LIKE SOLISTI1 OCCURS 5 WITH HEADER LINE.
DATA: RECLIST LIKE SOMLRECI1 OCCURS 5 WITH HEADER LINE.
DATA: DOC_CHNG LIKE SODOCCHGI1.
DATA: ENTRIES LIKE SY-TABIX.
DATA: NAME(15).
Fill the document
DOC_CHNG-OBJ_NAME = 'URGENT'.
DOC_CHNG-OBJ_DESCR = 'Read at once !'.
DOC_CHNG-SENSITIVTY = 'P'.
OBJCONT = 'Hey guys, time for lunch !!!'.
APPEND OBJCONT.
OBJCONT = 'Lets get going !'.
APPEND OBJCONT.
DESCRIBE TABLE OBJCONT LINES ENTRIES.
READ TABLE OBJCONT INDEX ENTRIES.
DOC_CHNG-DOC_SIZE = ( ENTRIES - 1 ) * 255 + STRLEN( OBJCONT ).
Fill the receiver list
CLEAR RECLIST.
RECLIST-RECEIVER = SY-UNAME. " replace with <login name>
RECLIST-REC_TYPE = 'B'.
RECLIST-EXPRESS = 'X'.
APPEND RECLIST.
CLEAR RECLIST.
RECLIST-RECEIVER = '[email protected]'.
RECLIST-REC_TYPE = 'U'.
APPEND RECLIST.
Send the document
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
 EXPORTING
 DOCUMENT_TYPE = 'RAW'
 DOCUMENT_DATA = DOC_CHNG
 PUT_IN_OUTBOX = 'X'
 TABLES
 OBJECT_CONTENT = OBJCONT
 RECEIVERS = RECLIST
 EXCEPTIONS
 TOO_MANY_RECEIVERS = 1
 DOCUMENT_NOT_SENT = 2
 OPERATION_NO_AUTHORIZATION = 4
 OTHERS = 99.
 CASE SY-SUBRC.
 WHEN 0.
 LOOP AT RECLIST.
 IF RECLIST-RECEIVER = SPACE.
 NAME = RECLIST-REC_ID.
 ELSE.
 NAME = RECLIST-RECEIVER.
 ENDIF.
 IF RECLIST-RETRN_CODE = 0.
 WRITE: / NAME, ': succesfully sent'.
 ELSE.
 WRITE: / NAME, ': error occured'.
 ENDIF.
 ENDLOOP.
 WHEN 1.
 WRITE: / 'Too many receivers specified !'.
 WHEN 2.
 WRITE: / 'No receiver got the document !'.
 WHEN 4.
 WRITE: / 'Missing send authority !'.
 WHEN OTHERS.
 WRITE: / 'Unexpected error occurred !'.
 ENDCASE.
Notes
To send an existing document, you must use the function module SO_OLD_DOCUMENT_SEND_API1.
If the active user is still to be able to process the document after it has been sent, it must be moved to the outbox when sent using the flag PUT_IN_OUTBOX. You can use the function module SO_FOLDER_READ_API1 to read the contents of the outbox and the object ID to find the document sent.
It is not possible to use a user address name as the recipient since this may not be unique. To get around this problem, you can use the function module SO_NAME_CONVERT_API1. This provides a hit list in response to a specified name, for which a dialog is constructed with a choice of required values.
Parameters
DOCUMENT_DATA
DOCUMENT_TYPE
PUT_IN_OUTBOX
COMMIT_WORK
SENT_TO_ALL
NEW_OBJECT_ID
OBJECT_HEADER
OBJECT_CONTENT
CONTENTS_HEX
OBJECT_PARA
OBJECT_PARB
RECEIVERS
Exceptions
TOO_MANY_RECEIVERS
DOCUMENT_NOT_SENT
DOCUMENT_TYPE_NOT_EXIST
OPERATION_NO_AUTHORIZATION
PARAMETER_ERROR
X_ERROR
ENQUEUE_ERROR
U can use other FM also
SO_DOCUMENT_SEND_API1
SO_NEW_DOCUMENT_ATT_SEND_API1
SO_OLD_DOCUMENT_SEND_API1
Reward points if helpful.
Regards,
Hemant

Error while distributing document

I have one querry in SAP-DMS Document Distribution
--While i am distributing the document to single recipient it is working fine without any error and document is received by end recipient
--While i am trying to distribute same document to multiple document it doesn't delivers the document and in distribution log i can see the status as "ER" and when i am restarting distribution from log screen manually the documents are distributed....
If any one has idea about it please reply...
I want to distribute document to multiple recipient automatically.....without restarting the distribution manually from distribution log screen
Regards,
Tushar Dave

Thanks christoph,
i applied the note 1008281, & it worked
thanks & regards
Tushar.

Workflow for notifying "User Responsible"

Hi
Scenario : When the DIR status is changed, the "User Responsible" should be notified
I have done the following settings
1) Activated Event linkages
2) Activated workflows WS20000104 and WS20000137
3)Activated Task TS0007842 in CA-DMS-Document Distribution-General-SAP Business workflow-Allocate Tasks to Person Responsible.
4) Assigned task to Doc type / Status combination in dc10
Normal Document Distribution is successful.. But mail is not triggered to "User Responsible" when status or any changes are made to the DIR
Anymore settings to be done..?? Is the above method correct??
Regards
Aby

Hi Bhuwan
I require some more details
Can u please tell me where to assign EDIT for BO DRAW, as I could see only CREATED and CHANGED and some statuses for BO DRAW
Where to assign Event for Object type DRAW, where is that settings??
Also by anyway is it possible, just to incluide the DIR link in the standard task TS 0007842 ??
Regards
Aby

Can I play a piece of content locally if network was to do down?

My boss has asked me to get our DMS system up and running for our company. Right now I am in the testing phase and am very new to this. I have our DMM 5.2.2 setup and one DMP connected a TV. I have been able to upload video and push it out to the DMP through the schedualer. I have played around with creating presentations and pushing them out to the DMP via the schedualer. Now my boss has asked me to come up with a way to either get content on locally eitehr actually local to the dmp or through a thumb drive so that in the case that the network cable was unpluged or the network went down it would switch over to the local content. Can anyone assist me in getting this DMP setup this way?
As always any help is greatly appreciated!

Hi Glen,
In order to deploy and play content locally on the DMP memory, you can use the DMS Content Distribution (DMS-CD) feature. This is documented at the following link:
http://www.cisco.com/en/US/docs/video/digital_media_systems/5_x/5_2/dmm/user/guide/dmp/cds.html#wp2182544
However keep in mind that if you use this, the content will always be played from the local storage, not only when the DMP cable is disconnected.
Hope this helps,
Marco

Sbwp create new document

Hi all experts,
i want to create a new document via a function or method in the inbox of a receiver. I already looked for SO_DOCUMENT_SEND_API1 or SO_DOCUMENT_INSERT but it seems that these function are just for creating a email to an external partner.
I also try to use the method "cl_bcs=>short_message" but with this thing i have problems creating the right receiver table, because it is a deep structure.
DATA: it_send_text TYPE BCSY_TEXT,
 wa_send_text TYPE soli,
 it_rec TYPE BCSY_RE3,
 wa_rec LIKE LINE OF BCSY_RE3
wa_send_text-line = 'some text for the message body'.
append wa_send_text to it_send_text.
*wa_rec-recipient = CL_SAPUSER_BCS=>CREATE( SY-UNAME ).
wa_rec-recipient = 'USER_NAME'.
append wa_rec to it_rec.
CALL METHOD cl_bcs=>short_message
EXPORTING
 I_subject = 'doc_title'
 I_TEXT = it_send_text
 I_RECIPIENTS = it_rec
can anybody help me? I though this is an easy one to create a document?!
Regards,
Steffen

hi You can send the Document to SBWP also using this Fm
check this Program
In this just look at the parameter
RECEIVER
Name of recipient.
The following entry categories are possible:
SAP use name of the recipient
SAPoffice name of the recipient
Shared distribution list
Fax number in the form of structure SADRFD
Internet address in the form of structure SADRUD
Remote SAP name in the form of structure SADR7D
X.400 address in the form of structure SADR8D
ADR_TYPE
Type of RECEIVER entry.
The following values are permitted:
'B' : SAP user name
' ' : SAPoffice name
'C' : Shared distribution list
'F' : Fax number
'U' : Internet address
'R ' : Remote SAP name
'X' : X.400 address
REC_ID
If the recipient is a SAPoffice user, the user ID, instead of the recipient name in RECEIVER, can be entered in this field.
[code]REPORT ZSSO_DOCUMENT_SEND_API1.
DATA: OBJPACK LIKE SOPCKLSTI1 OCCURS 2 WITH HEADER LINE.
DATA: OBJHEAD LIKE SOLISTI1 OCCURS 1 WITH HEADER LINE.
DATA: OBJBIN LIKE SOLISTI1 OCCURS 10 WITH HEADER LINE.
DATA: OBJTXT LIKE SOLISTI1 OCCURS 10 WITH HEADER LINE.
DATA: RECLIST LIKE SOMLRECI1 OCCURS 5 WITH HEADER LINE.
DATA: DOC_CHNG LIKE SODOCCHGI1.
DATA: TAB_LINES LIKE SY-TABIX.
Creating the document to be sent
DOC_CHNG-OBJ_NAME = 'OFFER'.
DOC_CHNG-OBJ_DESCR = 'Auction of a Picasso jr'.
OBJTXT = 'Reserve price : $250000'.
APPEND OBJTXT.
OBJTXT = 'A reproduction of the painting to be auctioned'.
APPEND OBJTXT.
OBJTXT = 'is enclosed as an attachment.'.
APPEND OBJTXT.
DESCRIBE TABLE OBJTXT LINES TAB_LINES.
READ TABLE OBJTXT INDEX TAB_LINES.
DOC_CHNG-DOC_SIZE = ( TAB_LINES - 1 ) * 255 + STRLEN( OBJTXT ).
Creating the entry for the compressed document
CLEAR OBJPACK-TRANSF_BIN.
OBJPACK-HEAD_START = 1.
OBJPACK-HEAD_NUM = 0.
OBJPACK-BODY_START = 1.
OBJPACK-BODY_NUM = TAB_LINES.
OBJPACK-DOC_TYPE = 'RAW'.
APPEND OBJPACK.
Creating the document attachment
(Assume the data in OBJBIN are given in BMP format)
OBJBIN = ' \O/ '. APPEND OBJBIN.
OBJBIN = ' | '. APPEND OBJBIN.
OBJBIN = ' / \ '. APPEND OBJBIN.
DESCRIBE TABLE OBJBIN LINES TAB_LINES.
OBJHEAD = 'picasso.bmp'. APPEND OBJHEAD.
Creating the entry for the compressed attachment
OBJPACK-TRANSF_BIN = 'X'.
OBJPACK-HEAD_START = 1.
OBJPACK-HEAD_NUM = 1.
OBJPACK-BODY_START = 1.
OBJPACK-BODY_NUM = TAB_LINES.
OBJPACK-DOC_TYPE = 'BMP'.
OBJPACK-OBJ_NAME = 'ATTACHMENT'.
OBJPACK-OBJ_DESCR = 'Reproduction object 138'.
OBJPACK-DOC_SIZE = TAB_LINES * 255.
APPEND OBJPACK..
Entering names in the distribution list
RECLIST-RECEIVER = '[email protected]'.
RECLIST-REC_TYPE = 'U'.
APPEND RECLIST.
RECLIST-RECEIVER = 'DLI-NEUREICH'.
RECLIST-REC_TYPE = 'P'.
APPEND RECLIST.
Sending the document
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
 EXPORTING
 DOCUMENT_DATA = DOC_CHNG
 PUT_IN_OUTBOX = 'X'
 COMMIT_WORK = 'X'
 TABLES
 PACKING_LIST = OBJPACK
 OBJECT_HEADER = OBJHEAD
 CONTENTS_BIN = OBJBIN
 CONTENTS_TXT = OBJTXT
 RECEIVERS = RECLIST
 EXCEPTIONS
 TOO_MANY_RECEIVERS = 1
 DOCUMENT_NOT_SENT = 2
 OPERATION_NO_AUTHORIZATION = 4
 OTHERS = 99.
CASE SY-SUBRC.
WHEN 0.
 WRITE: / 'Result of the send process:'.
 LOOP AT RECLIST.
 WRITE: / RECLIST-RECEIVER(48), ':'.
 IF RECLIST-RETRN_CODE = 0.
 WRITE 'sent successfully'.
 ELSE.
 WRITE 'not sent'.
 ENDIF.
 ENDLOOP.
WHEN 1.
 WRITE: / 'no authorization to send to the specified number of' 'recipients!'.
WHEN 2.
 WRITE: / 'document could not be sent to any of the recipients!'.
WHEN 4.
 WRITE: / 'no authorization to send !'.
WHEN OTHERS.
 WRITE: / 'error occurred during sending !'.
ENDCASE.[/code]
Regards Rk

Playlist with DMP locally stored content ?

Hi everyone
I am new with DMP and have two questions. DMS system in my LAB contains DMS 5.2 and couple DMPs 4400. I was able to upload java script along with required content into DMP (using FTP) and start presentation from DMP. Requirement is to change that DMP content every day !
Q1: Is it possible to upload content to DMP using scheduler or any other application or every time I need to manually change locally stored files?
Q2: Is it possible to create playlist or scheduler to play DMP locally stored assets (html, flash…)?
Thanks,
O

Good afternoon,
What you are looking for is the "Cisco DMS Content Distribution" mechanism (check
http://www.cisco.com/en/US/docs/video/digital_media_systems/5_x/5_2/dmm/user/guide/dmp/cds.html#wp2183551 for details)
In short, the way this works is the following:
You create a normal playlist on the DMM
With a Content Deployment task launched from the DMM you upload all the required content (in fact, only the files that changed since last deployment) to a group of DMP
Once the deployment has finished, you start they playlist from an automatically generated "Go to Url" task
If you need further clarification on any of the points mentioned in the documentation link I sent you, please, do not hesitate to contact me again.
Best regards
Daniel

Migrate DMS DIRS with originals from SAP R/3 4.6 C to ECC6

Dear All,
I have a requirement to transfer all DMS master data with originals from SAP R/3 4.6C to ECC6. Presently the R/3 4.6 c has 3 instances with 3 different content servers. I have to transfer the master data of all 3 instances in one on ECC6 along with the originals from all 3 content servers.
One way i know is through BDC, but the originals are on the content servers not on the local machine. So kindly suggest me if this can be done through any other method easily.
Expecting your kind attention.

Hi Nishant,
http://help.sap.com/saphelp_erp2005vp/helpdata/en/5c/c1c590445f11d189f00000e81ddfac/frameset.htm
This link provides you with the various methods by which you can transfer the DIR's to ECC6.0
Regards
Rehman

DMS originals distribution by fax

Similar Messages

Maybe you are looking for