ASCII Object

I have a device (video switcher) that will accept ASCII commands. One of the acceptable commands is used to set date and time. In order execute this command it must be in the proper format "ZaMM/DD/YY/HH:MMSa". Lookout uses a floating point number (implicit data member) that represents date/time. How can I change this to a numeric format and connect it to my "RQV" data member?
Solved!
Go to Solution.

Hi chiphowell,
Lookout stores all absolute dates and times as numeric signals. It uses the 1900 date system in which the number 1 corresponds to midnight January 1, 1900. The number 2 corresponds to midnight January 2, 1900. For example, the number 34491.5 represents noon on Jun 6, 1994. If you are using an older version of Lookout and would like to force your time to stay in the time format, you can convert it to text using the TEXT function. The syntax for the TEXT function is TEXT (numeric, text). If you wanted to format your time value, you would use TEXT (time value, "HH:MMS"). You can also use the NumericFormat Object to select the numeric format to use with Lookout.
Regards,
S. Bassett

Similar Messages

Response format error when using the ASCII object to communicate with a Dart ASPII motor controller.

I can't seem to get Lookout to work using a COMM RS232 connection to our Dart controller. When using a term program, i'll send the command RV1,0,6 and get the response 1000,0005. I set up the ASCII object in Lookout with the following:
SEND=Pb5
RequestFormat="%s"
ResponseFormat="%s" (and many other combinations)
RQV1.TXT=TextEntry1
for TextEntry1 I enter RV1,0,6 and I always get that dang response format error!
Any suggestions? Obvious goofs?

What's the Expression you're inserting to read back the response? If you're using just RSV1, you'll get the error. Try RSV1.txt.
For troubleshooting purposes, delete all RSV expressions and the ResponseFormat connection and insert just an Expresssion on ASCII1.Response (where ASCII1 is your Object). This will give you the raw ASCII frame coming in. Then you can start formatting this raw response with appropriate ResponseFormat and RSVs.
Hope this helps,
Khalid

UNSOLICITED ASCII OBJECT RECEPTION

Lookout allows reception of unsolicited serial data using the ASCII object but doesn't seem to provide any method of telling us that New ASCII data has arrived on the serial port to allow us to start processing that data?
I have an application where Lookout needs to recieve randomly timed, un-solicited serial ASCII data about once every 3 to 6 seconds and log the data values for SPC processing and historical data viewing.
How can I know that the serial data has arrived at the ASCII serial port to process the serial dat string and to extract and log the data - without using the ASCII SEND data member in the UNSOLICITORED MODE ? (Using lookout version 4.5)
thanks

Thanks All,
Comparing recieved data values for changes is not helpful because the data is latched by the lookout object and on many occasions the recieved data may be exactly the same - yet still needs to be sampled and logged for SPC control processing.
However after further investigation I have found that the "UPDATE" flag immediately pulses LOW and remains HIGH after unsolicited reception while under normal operation it goes LOW and remains LOW until a data response is recieved when using the SEND command.
Therefore monitoring this flag for a POSITIVE transition rather than a Negative transition (as per manual) when recieving unsolicated data seems to work OK.
Many thanks again for all the responses.

ASCII closes COM port randomly during long periods of unsolicited response monitoring

I have lots of serial ASCII objects monitoring for unsolicited responses (every two seconds, from 20 different COM ports). Randomly, sometimes a few times a day, sometimes no problem for 2-3 days....but the ASCII object somehow lets the COM ports close or it loses contact with the COM port occasionally. All I have to do is go into edit mode and "touch" the properties....such as changing the "Retry Attempts" setting and the communication returns.
There are no alarms logged when this happens!
Ed

Ryan,
I currently use 6 Ascii objects from 6 ports and plan to use 2 more. Unsolicited data arrives every two minutes (as measured by the sending end). I have a button on the panel for each object that I can press to send a request to the sending end. Each of the senders connects to a digi portserver II and is delivered to lookout via an ethernet connection (as a virtual com port). The ethernet connection is routed over various paths including micowave, which could have an occasional traffic interupting fade. One or more of the Ascii objects may fail to respond at any time, but several days may pass without a problem. When a failure is noticed, you can usually select the properties for that object and the problem clears. If instead, you send a request to any of the other Ascii objects , Lookout may just hang (permanet hour glass). When a failure is noticed, if Lookout is then turned off and the offending port is monitored with hyperterminal, the data from the sending port is on time and correctly formatted. The help file has a section "Ascii alarm and error messages" with a section named "Early temination when parsing the response frame". There are a bunch of reasons listed there as to why the Ascii object might not function properly. I've tried everything that I can think of to make this work reliably. Any ideas? See the link for response format information. http://jrcamenzind.googlepages.com/lookout

A temporary solution for issue of excel sheet for SO_NEW_DOCUMENT_ATT_SEND_

Hi,
we all sometime or the other have faced the problem with SO_NEW_DOCUMENT_ATT_SEND_API1, it passes all the data into a single excel sheet. the following is the code i have written using the same standard FM to resolve the issue.
Problem's Facing     : To send the output of a report as mail attachment (Excel sheet) from SAP, to the User's outlook or TCP/IP
What is happening     : All the data which is being passed to the excel is being put in a single cell of the excel sheet.
Cause               : the difficulty lies in getting the internal table from SAP report, passing it to email Function Module If the structure of the internal Table is unknown .
Solution:
if the user while sending data to the Function module ( created using the following code) puts a '#' between field values, all the fields gets separated into individual cells and the data gets printed as required.
<b>advantages</b> of the following code are:
1) User just need to type userid or multiple userid's separated by comma.
2) Performs multiple tasks with one function module.
3) It can be used to send file with subject only
4) It can be used to send file with subject and body
5) It can be used to send file with subject, body, and attachment
6) Attachment can be of 'TXT' format or 'XLS' format depending upon the choice of the user.
7) User specific parameters for EMAILID, subject, body and attachment type avoiding the dump error of "Type conflict"
8) If the user requires to send output of a report as an excel file, then a single internal table will store the total output separating the field values by ' # ' and the data gets printed evenly. the ' # ' symbol is used as Tab delimiter.
FUNCTION zemail_attachment.
""Local Interface:
*" IMPORTING
*"     REFERENCE(EMAILID)
*"     REFERENCE(SUBJECT)
*"     REFERENCE(ATYPE)
*" TABLES
*"      ATTACH_FILE STRUCTURE SOLISTI1
*"      BODY OPTIONAL
*" EXCEPTIONS
*"      INCORRECT_PARAMETERS
This table requires information about how the data in the
tables OBJECT_HEADER, CONTENTS_BIN and CONTENTS_TXT are
to be distributed to the documents and its attachments.
DATA it_objpack LIKE sopcklsti1 OCCURS 2 WITH HEADER LINE.
This table must contain the summarized data dependent on each object type.
SAPscript objects store information here about forms and styles,
for example. Excel list viewer objects store the number of rows and columns
amongst other things and PC objects store their original file name.
DATA it_objhead LIKE solisti1   OCCURS 1 WITH HEADER LINE.
This table must contain the summarized content of the objects identified as binary objects.
DATA   it_objbin TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0
                 WITH HEADER LINE.
This table must contain the summarized content of the objects identified as ASCII objects.
DATA it_objtxt LIKE solisti1   OCCURS 10 WITH HEADER LINE.
This table must contain the document recipients.
DATA it_reclist LIKE somlreci1 OCCURS 5 WITH HEADER LINE .
This structure must contain the attributes of the document to be sent.
DATA: doc_ching LIKE sodocchgi1.
DATA: tab_lines LIKE sy-tabix.
Create the internal table for body , subject
DATA: it_body LIKE solisti1 OCCURS 10 WITH HEADER LINE.
*creation of internal table for Email-id.
DATA: BEGIN OF it_mailid OCCURS 0,
        email LIKE kna1-name1 ,
        END OF it_mailid.
*VARIABLES
DATA : v_hash(1) TYPE c VALUE '#'.
DATA: v_string1 LIKE kna1-name1,
        v_string2 LIKE kna1-name1,
        v_string3(12) TYPE c VALUE '@GMAIL.COM'.
*CONSATNTS
CONSTANTS: c_con_cret TYPE c VALUE cl_abap_char_utilities=>horizontal_tab,
             c_con_tab TYPE c VALUE cl_abap_char_utilities=>cr_lf,
             c_raw(3)   TYPE c VALUE 'RAW',
             c_comma(1) TYPE c VALUE ',',
             c_rec_type(1) TYPE c VALUE 'U',
             c_space(1)    TYPE c VALUE ''.
Move Body to Internal Table (body into it_body)
LOOP AT body .
    MOVE body TO it_body .
    APPEND it_body .
ENDLOOP.
doc_ching-obj_descr = subject.   "Subject of the Email
Move the Subject and Body to OBJTXT
it_objtxt[] = it_body[].
DESCRIBE TABLE it_objtxt LINES tab_lines.
READ TABLE it_objtxt INDEX tab_lines.
doc_ching-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( it_objtxt ).
CLEAR it_objpack-transf_bin.
it_objpack-head_start = 1.
it_objpack-head_num   = 0.
it_objpack-body_start = 1.
it_objpack-body_num   = tab_lines.
it_objpack-doc_type   = c_raw.
APPEND it_objpack.
Convert to Excel format
IF NOT attach_file[] IS INITIAL.
IF atype IS INITIAL.
RAISE INCORRECT_PARAMETERS.
ELSEIF atype = 'XLS' .
    LOOP AT attach_file .
      CONCATENATE attach_file v_hash INTO attach_file.
      REPLACE ALL OCCURRENCES OF v_hash IN attach_file WITH c_con_cret.
      IF sy-tabix = 1.
        MOVE attach_file TO it_objbin.
      ELSE.
        CONCATENATE c_con_tab attach_file INTO it_objbin.
      ENDIF.
      APPEND it_objbin.
    ENDLOOP.
ELSEIF atype = 'TXT' .
Convert to Text format
    LOOP AT attach_file .
      REPLACE ALL OCCURRENCES OF v_hash IN attach_file WITH c_con_cret.
      CONCATENATE attach_file c_con_tab INTO it_objbin .
      APPEND it_objbin .
    ENDLOOP.
ENDIF.
DESCRIBE TABLE it_objbin LINES tab_lines.
it_objhead = subject. APPEND it_objhead.
Creating the entry for the compressed attachment
it_objpack-transf_bin = 'X'.
it_objpack-head_start = 1.
it_objpack-head_num   = 1.
it_objpack-body_start = 1.
it_objpack-body_num   = tab_lines.
*check for XLS ,TXT files
IF atype = 'XLS'.
    it_objpack-doc_type   = atype.
ELSEIF atype = 'TXT'.
    it_objpack-doc_type   = c_raw.
ENDIF.
it_objpack-obj_name   = 'ATTACHMENT'.
it_objpack-obj_descr = 'ATTACHMENT'. "Attachment File Name
it_objpack-doc_size   = tab_lines * 255.
APPEND it_objpack..
ENDIF.
Entering names in the distribution list
Concatenating the email with '@GMAIL.COM if the user doesnot specify any mail extension
recipent type as U - for internet usage
SPLIT emailid AT c_comma INTO TABLE it_mailid.
APPEND it_mailid.
LOOP AT it_mailid.
    SHIFT it_mailid-email LEFT DELETING LEADING c_space.
    SPLIT it_mailid-email AT '@' INTO: v_string1 v_string2.
    IF v_string2 IS INITIAL AND NOT it_mailid-email IS INITIAL.
      CONCATENATE v_string1 v_string3 INTO it_reclist-receiver.
      it_reclist-rec_type = c_rec_type.
      APPEND it_reclist.
      CLEAR: v_string1,v_string2.
    ELSE.
      it_reclist-receiver = it_mailid-email.
      it_reclist-rec_type = c_rec_type.
      APPEND it_reclist.
    ENDIF.
ENDLOOP.
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
    EXPORTING
      document_data              = doc_ching
      put_in_outbox              = 'X'
      commit_work                = 'X'
    TABLES
      packing_list               = it_objpack
      object_header              = it_objhead
      contents_bin               = it_objbin
      contents_txt               = it_objtxt
      receivers                  = it_reclist
    EXCEPTIONS
      too_many_receivers         = 1
      document_not_sent          = 2
      operation_no_authorization = 4
      OTHERS                     = 99.
ENDFUNCTION.
If anyone, has a better solution, please share
Cheers
Ajay

issue resolved

Problem with attachtment XLS (last column of the xls)

Hi,
iam working on interface in which i will be sending an email along with attachtment where my email along with attachtment are working perfectly ,the problem is with the XLS where the last column of the XLS is taking 255 char which is the length of the field .
How i have to restrict it ?
solution on this would be helpfull .
Thanks ,
shankar.
I have attached the sample code too.
FUNCTION zemail_send_attachment.
""Local Interface:
*" IMPORTING
*" VALUE(EMAILID)
*" VALUE(SUBJECT)
*" VALUE(ATYPE)
*" TABLES
*" ATTACH_FILE STRUCTURE SOLISTI1
*" BODY OPTIONAL
This table requires information about how the data in the
tables OBJECT_HEADER, CONTENTS_BIN and CONTENTS_TXT are
to be distributed to the documents and its attachments.
DATA objpack LIKE sopcklsti1 OCCURS 2 WITH HEADER LINE.
This table must contain the summarized data dependent on each object type.
SAPscript objects store information here about forms and styles,
for example. Excel list viewer objects store the number of rows and columns
amongst other things and PC objects store their original file name.
DATA objhead LIKE solisti1 OCCURS 1 WITH HEADER LINE.
This table must contain the summarized content of the objects identified as binary objects.
DATA objbin TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0
WITH HEADER LINE.
This table must contain the summarized content of the objects identified as ASCII objects.
DATA objtxt LIKE solisti1 OCCURS 10 WITH HEADER LINE.
This table must contain the document recipients.
DATA reclist LIKE somlreci1 OCCURS 5 WITH HEADER LINE .
This structure must contain the attributes of the document to be sent.
DATA: doc_ching LIKE sodocchgi1.
DATA: tab_lines LIKE sy-tabix.
Create the internal table for body , subject
DATA: it_body LIKE solisti1 OCCURS 10 WITH HEADER LINE.
CONSTANTS: con_cret TYPE c VALUE cl_abap_char_utilities=>horizontal_tab,
con_tab TYPE c VALUE cl_abap_char_utilities=>cr_lf.
Move Body to Internal Table (body into it_body)
LOOP AT body .
MOVE body TO it_body .
APPEND it_body .
ENDLOOP.
doc_ching-obj_descr = subject. "Subject of the Email
Move the Subject and Body to OBJTXT
objtxt[] = it_body[].
DESCRIBE TABLE objtxt LINES tab_lines.
READ TABLE objtxt INDEX tab_lines.
doc_ching-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( objtxt ).
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.
Convert IT to Excel format
IF atype = 'XLS' .
LOOP AT attach_file .
REPLACE ALL OCCURRENCES OF '#' IN attach_file WITH con_cret ."INTO objbin.
IF sy-tabix = 1.
MOVE attach_file TO objbin.
ELSE.
CONCATENATE con_tab attach_file INTO objbin.
ENDIF.
APPEND objbin.
ENDLOOP.
ELSEIF atype = 'TXT' .
Convert IT to Text format
LOOP AT attach_file .
REPLACE ALL OCCURRENCES OF '#' IN attach_file WITH con_cret. " INTO objbin.
CONCATENATE attach_file con_tab INTO objbin .
APPEND objbin .
ENDLOOP.
ENDIF.
DESCRIBE TABLE objbin LINES tab_lines.
objhead = subject. 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.
IF atype = 'XLS'.
objpack-doc_type = atype.
ELSEIF atype = 'TXT'.
objpack-doc_type = 'RAW'.
ENDIF.
objpack-obj_name = 'ATTACHMENT'.
objpack-obj_descr = 'TEST'. "Attachment File Name
objpack-doc_size = tab_lines * 255.
APPEND objpack..
reclist-receiver = emailid.
reclist-rec_type = 'U'.
APPEND reclist.
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
document_data = doc_ching
put_in_outbox = 'X'
commit_work = 'X'
IMPORTING
SENT_TO_ALL =
NEW_OBJECT_ID =
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 .
ENDFUNCTION.

I had this problem after migrating to JDeveloper 10.1.3. Problem was with inconsistent DB column types. In our case, the DB column was CHAR containing only numbers, but VO defined it as NUMBER. This caused no problem in 9.0.3 we used before.
   <ViewAttribute
      Name="ParentFlagNew"
      IsPersistent="false"
      Precision="1"
      Type="oracle.jbo.domain.Number"
      ColumnType="NUMBER"
      AliasName="PARENT_FLAG_NEW"
      Expression="PARENT_FLAG_NEW"
      SQLType="NUMERIC" >
      <Properties>
         <Property Name ="DISPLAY_LIST" Value ="1=Yes,0=No" />
         <Property Name ="DISPLAY_LIST_sk" Value ="1=Áno,0=Nie" />
         <Property Name ="Renderer" Value ="sk.transacty.cm_iface.bc4j_common.ListFieldRenderer" />
      </Properties>
      <DesignTime>
         <Attr Name="_DisplaySize" Value="1" />
      </DesignTime>
   </ViewAttribute>

How to do multiple requests/responses sequentially to same COM port?

I can read 5 different values from my instrument. Each have their own command letter for sending over the value.
How do I read these values sequentially?

I am attaching an example which demos this using the ASCII Object. The example, for simplicity, uses a loop-back on COM1. I suggest you do the same while studying the example: short pins 2 and 3 on your COM1.
In the example, values from Column A and Column B of the DataTable are packed and sent out as the "command." So, you would replace this with your intrument commands. The response (which is the same as "command" in this case because of the loop-back) is read, parsed (the number from the text) and then stored in Column C of the DataTable.
This can be easily made to run automatically using a Timer/Counter.
Hope this helps.
Regards,
Khalid :
Attachments:
simpleserdriver.lks ‏10 KB

Bug sending email with Excel file (immediate reply would he helpfull)

Hi ,
   Below is have pasted a sample code where it will sends a email along with an attachtment (xls) .where the email is working perfectly but the xls file attachtment has a blank space in the first line .
where iam facing the problem ,
ie there should not be any blank lines at the top .
Please run the code one i have pasted below .u can find the bug .
can any one help me on this .
please have ur mail id in ( reclist-receiver ) so that u can check for the output.
This table requires information about how the data in the
tables OBJECT_HEADER, CONTENTS_BIN and CONTENTS_TXT are
to be distributed to the documents and its attachments.
DATA: objpack LIKE sopcklsti1 OCCURS 2 WITH HEADER LINE.
This table must contain the summarized data dependent on each object type.
SAPscript objects store information here about forms and styles,
for example. Excel list viewer objects store the number of rows and columns
amongst other things and PC objects store their original file name.
DATA: objhead LIKE solisti1   OCCURS 1 WITH HEADER LINE.
*CREATION OF INTERNAL TABLE
DATA : BEGIN OF itobjbin OCCURS 10 ,
       vbeln type vbrp-vbeln,
       matnr type vbrp-matnr,
       werks type vbrp-werks,
       fktyp like vbrk-fktyp,
       END OF itobjbin .
This table must contain the summarized content of the objects identified as binary objects.
*DATA: OBJBIN LIKE SOLISTI1   OCCURS 10 WITH HEADER LINE.
DATA:   objbin TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0
               WITH HEADER LINE.
DATA: wa_itobjbin LIKE itobjbin .
This table must contain the summarized content of the objects identified as ASCII objects.
DATA: objtxt LIKE solisti1   OCCURS 10 WITH HEADER LINE.
This table must contain the document recipients.
DATA: reclist LIKE somlreci1 OCCURS 5 WITH HEADER LINE.
This structure must contain the attributes of the document to be sent.
DATA: doc_chng LIKE sodocchgi1.
DATA: tab_lines LIKE sy-tabix.
DATA : V_FKTYP LIKE VBRK-FKTYP.
Creating the document to be sent
doc_chng-obj_name = 'OFFER'.                      " input contains the attributes of the document to be sent
doc_chng-obj_descr = 'EMAIL WITH EXCEL DOWNLOAD'.   "input contains title/subject of the document
*BODY OF THE MAIL
OBJTXT = 'Hi'.
APPEND OBJTXT .
OBJTXT = 'Test for excel download'.
APPEND OBJTXT.
OBJTXT = 'Below is the attachment with Billing Document Details'.
APPEND OBJTXT.
OBJTXT = 'Regards'.
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)
select vbeln matnr werks
        from vbrp into table itobjbin
        up to 10 rows
        where werks GE '1000'.
loop at itobjbin.
select single fktyp into v_fktyp from vbrk where vbeln = itobjbin-vbeln.
move v_fktyp to itobjbin-fktyp.
modify itobjbin.
endloop.
PERFORM build_xls_data_table .
DESCRIBE TABLE objbin LINES tab_lines.
objhead = 'ABC.XLS'. 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   = 'XLS'.
objpack-obj_name   = 'ATTACHMENT'.
objpack-obj_descr = 'XLS'.
objpack-doc_size   = tab_lines * 255.
APPEND objpack..
Entering names in the distribution list
reclist-receiver = ''.
reclist-rec_type = 'U'.
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.
*&      Form build_xls_data_table
      text
--> p1        text
<-- p2        text
FORM build_xls_data_table .
CONSTANTS: con_cret TYPE x VALUE '0D', "OK for non Unicode
           con_tab TYPE x VALUE '09'.   "OK for non Unicode
CONCATENATE 'Billing Document' 'Material Number' 'Plant' 'Billing category' ' ' INTO objbin SEPARATED BY con_tab.
CONCATENATE con_cret objbin INTO objbin.
APPEND objbin.
LOOP AT itobjbin .
   CONCATENATE itobjbin-vbeln itobjbin-matnr itobjbin-werks itobjbin-fktyp' '
          INTO objbin SEPARATED BY con_tab.
   CONCATENATE con_cret objbin INTO objbin.
   APPEND objbin.
ENDLOOP.
thanks in advance,
vinay .

Hi ravi ,
     Thanks ,for your help .now xls is working fine .
but now iam facing a problem with the same function module .for txt files .where all the records are formated in asingle line .
can u provide a solution for this ,which would be very helpfull.
below is have attached the sample code .
Thanks,
vinay.
FUNCTION Z_KAILASH_ATTACHMENT1.
""Local Interface:
*" IMPORTING
*"     VALUE(EMAILID)
*"     VALUE(SUBJECT)
*"     VALUE(ATYPE)
*" TABLES
*"      ATTACH_FILE STRUCTURE SOLISTI1
*"      BODY OPTIONAL
This table requires information about how the data in the
tables OBJECT_HEADER, CONTENTS_BIN and CONTENTS_TXT are
to be distributed to the documents and its attachments.
DATA OBJPACK LIKE SOPCKLSTI1 OCCURS 2 WITH HEADER LINE.
This table must contain the summarized data dependent on each object type.
SAPscript objects store information here about forms and styles,
for example. Excel list viewer objects store the number of rows and columns
amongst other things and PC objects store their original file name.
DATA OBJHEAD LIKE SOLISTI1   OCCURS 1 WITH HEADER LINE.
This table must contain the summarized content of the objects identified as binary objects.
DATA   OBJBIN TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0
                 WITH HEADER LINE.
This table must contain the summarized content of the objects identified as ASCII objects.
DATA OBJTXT LIKE SOLISTI1   OCCURS 10 WITH HEADER LINE.
This table must contain the document recipients.
DATA RECLIST LIKE SOMLRECI1 OCCURS 5 WITH HEADER LINE .
This structure must contain the attributes of the document to be sent.
DATA: DOC_CHING LIKE SODOCCHGI1.
DATA: TAB_LINES LIKE SY-TABIX.
Create the internal table for body , subject
DATA: IT_BODY LIKE SOLISTI1 OCCURS 10 WITH HEADER LINE.
CONSTANTS: con_cret TYPE C VALUE cl_abap_char_utilities=>horizontal_tab,
           con_tab TYPE C VALUE cl_abap_char_utilities=>cr_lf.
Move Body to Internal Table (body into it_body)
LOOP AT BODY .
    MOVE BODY TO IT_BODY .
    APPEND IT_BODY .
ENDLOOP.
DOC_CHING-OBJ_DESCR = SUBJECT.   "Subject of the Email
Move the Subject and Body to OBJTXT
OBJTXT[] = IT_BODY[].
DESCRIBE TABLE OBJTXT LINES TAB_LINES.
READ TABLE OBJTXT INDEX TAB_LINES.
DOC_CHING-DOC_SIZE = ( TAB_LINES - 1 ) * 255 + STRLEN( OBJTXT ).
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.
Convert IT to Excel format
IF ATYPE = 'XLS' .
*CONSTANTS: con_cret TYPE C VALUE cl_abap_char_utilities=>horizontal_tab,
          con_tab TYPE C VALUE cl_abap_char_utilities=>cr_lf.
LOOP AT ATTACH_FILE .
    REPLACE ALL OCCURRENCES OF '#' IN ATTACH_FILE WITH con_cret. " INTO objbin.
    CONCATENATE ATTACH_FILE con_tab INTO objbin.
    APPEND objbin.
ENDLOOP.
ELSEIF ATYPE = 'TXT' .
LOOP AT ATTACH_FILE .
    REPLACE ALL OCCURRENCES OF '#' IN ATTACH_FILE WITH con_tab. " INTO objbin.
    CONCATENATE ATTACH_FILE ' ' INTO OBJBIN .
    APPEND OBJBIN .
ENDLOOP.
ENDIF.
****End-Code Excel Format .
DESCRIBE TABLE objbin LINES tab_lines.
objhead = subject. 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   = ATYPE.
objpack-obj_name   = 'ATTACHMENT'.
objpack-obj_descr = 'TEST'. "Attachment File Name
objpack-doc_size   = TAB_LINES * 255.
APPEND objpack..
reclist-receiver = EMAILID.
reclist-rec_type = 'U'.
APPEND reclist.
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
   DOCUMENT_DATA                    = DOC_CHING
   PUT_IN_OUTBOX                    = 'X'
   COMMIT_WORK                      = 'X'
IMPORTING
SENT_TO_ALL                     =
NEW_OBJECT_ID                   =
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 .
ENDFUNCTION.

Query on downloading to XLS file

Hi ,
Iam facing some problem in downloading into xls format .
Here is an example of the query ,
data : OBJBIN LIKE SOLISTI1 OCCURS 10 WITH HEADER LINE
OBJBIN = 'ABC'.
APPEND OBJBIN.
OBJBIN = 'XYZ'.
APPEND OBJBIN.
OBJBIN = 'LMNO'.
APPEND OBJBIN.
using the fm SO_NEW_DOCUMENT_ATT_SEND_API1 iam trying to send the file as an attachtment .
but in the attachtment file all the three values displaying on a single cell .but need to be displayed in different cells.
can some one give a solution for this
Thanks ,
vinay .

Hi
Have you taken care ( passed ) of all these table parameter's properly . please check.
PACKING_LIST
This table requires information on how the data from tables OBJECT_HEADER, CONTENTS_BIN and CONTENTS_TXT should be distributed to the document and its attachments. The first line stands for the document and each of the following lines for one attachment.
TRANSF_BIN
If this flag is set ('X'), the table entry indicates an object stored in binary format. The corresponding object contents are located in table CONTENTS_BIN. If the flag is not set, the object contents are located in table CONTENTS_TXT in ASCII format.
HEAD_START
Requires the starting line of table OBJECT_HEADER, starting from which the specific header data of the object is stored.
HEAD_NUM
Requires the number of lines in table OBJECT_HEADER which are used for the specific header data of the object. The lines involved are arranged in a block and uniquely defined together with the specification in HEAD_START.
BODY_START
Requires the starting lines of the tables dependent on the flag TRANSF_BIN, starting from which the object contents are stored.
BODY_NUM
Requires the number of lines of the table dependent on flag TRANSF_BIN which are used to store the object contents. The lines involved are arranged in a block and uniquely defined together with the specification in HEAD_START.
DOC_TYPE
Attachment type. This field is not used in the first line of the table.
OBJ_NAME
Attachment name. This field is not used in the first line of the table.
OBJ_DESCR
Title (short description) of the attachment. This field is not used in the first line of the table.
OBJ_LANGU
Attachment language. This field is not used in the first line of the table.
DOC_SIZE
Size of the attachment in bytes. The size of PC object files should be entered here, and the size of RAW and SCR objects is calculated by "length of last line" + "number of remaining lines multiplied by 255". This field is not used in the first line of the table.
MESS_TYPE
This field is not used.
OBJECT_HEADER
This table must contain the summarized data dependent on the respective object type. SAPscript objects save here, for example, information about layout sets, styles, and Excel Listviewer objects, including the number of lines and columns and the original file names of PC objects.
LINE
Requires the type-dependent data of the object for each line. Which section belongs to which object is determined by the fields HEAD_START and HEAD_NUM in table PACKING_LIST.
CONTENTS_BIN
This table must contain the summarized contents of objects flagged as binary objects.
LINE
Requires the contents of the objects for each line. Which section belongs to which object is determined by the fields BODY_START and BODY_NUM in table PACKING_LIST.
CONTENTS_TXT
This table must contain the summarized contents of the objects flagged as ASCII objects.
LINE
Requires the contents of the objects for each line. Which section belongs to which object is determined by the fields BODY_START and BODY_NUM in table PACKING_LIST.
OBJECT_PARA
This table is only needed if the document to be sent should be processed. It must contain the SET/GET parameters which are passed on to the processing element during processing.
It is not possible to assign processing parameters to attachments to documents.
NAME
Name of the SET/GET parameter. Only the first three characters are used.
OPTION
This field is not used.
LOW
Contains the value of the parameter in NAME.
HIGH
This field is not used.
OBJECT_PARB
This table is only needed if the document to be sent is assigned to a specific processing type. Its meaning changes depending on the type. If the processing element is a report or transaction which passes values to the global memory, then the table contents are interpreted as a quantity of parameters with corresponding values and transported to the memory ID listed on the first line. If the processing element is a function or dialog module, then the table is passed to these as table parameter MSGDIAL.
It is not possible to pass processing parameters to the attachments to documents.
NAME
If the processing element is a report or transaction which passes values to the global memory, then the field in the first table line must contain the name of the memory ID used for exporting. The fields in the remaining lines are used for the names of the parameters. If the processing element is a function or dialog module, then the fields must be filled accordingly.
VALUE
If the processing element is a report or transaction which passes values to the global memory, then the field in the first table line must remain empty. The fields in the remaining lines are used for parameter values belonging to NAME. If the processing element is a function or dialog module, then the fields must be filled accordingly.
RECEIVERS
This table must contain the recipients of the document.
RECEIVER
Name of the recipient.
The following entry types are possible:
the SAP user name of the recipient
the SAPoffice name of the recipient
a shared distribution list
a fax number in form of the structure SADRFD
an Internet address in form of the structure SADRUD
a remote SAP name in form of the structure SADR7D
an X.400 address in form of the structure SADR8D
ADR_TYPE
Type of RECEIVER entry.
The following values are allowed:
'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, then the ID of the user can be entered in this field instead of the recipient name in RECEIVER.
REPLY_DOC
If this field is filled, then the document sent represents a reply to the folder entry flagged with the ID specified. A correspondence history is automatically created and maintained.
REC_DATE
Date on which the document should reach the recipient. No guarantee can be made that the date will be met for external recipients, as this depends on the performance of the products involved.
PROXY_ID
If the document recipient has the automatic forwarding function active, then this field contains the SAP user ID or the address ID of the external address to which this document was sent in the end.
RETRN_CODE
If the document recipient successfully receives the document, then the function module fills this field with the value '0', otherwise a value unequal to '0' is entered.
EXPRESS
If this flag is set ('X'), then the document is sent with the attribute 'Express'. If the recipient is a SAPoffice user who is logged on at the time, then this user immediately receives a message informing him/ her of the express mail.
COPY
If this flag is set ('X'), then the document is sent with the attribute 'Copy'.
BLIND_COPY
IF this flag is set ('X'), then the document is sent with the attribute 'Blind copy'. If the recipient is a SAPoffice user, then the recipient can neither print nor forward the document.
NO_FORWARD
If this flag is set ('X') and the recipient is a SAPoffice user, then the recipient cannot forward the document.
NO_PRINT
If this flag is set ('X') and the recipient is a SAPoffice user, then the recipient cannot print the document.
TO_ANSWER
If this flag is set ('X') and the recipient is a SAPoffice user, then the recipient has to send a reply to the document before he/she can delete it from his/her inbox.
TO_DO_EXPL
If this flag is set ('X') and the recipient is a SAPoffice user, then he/she has to process the document and set its status to 'Done' before it can be deleted from from his/her inbox.
TO_DO_GRP
If this field has a value between '1' and '9', then a SAPoffice user belonging to one of the recipient groups defined by these numbers has to process the document before the affected persons can delete it from their inboxes. If the value '0' is entered, then processing is not required.
COM_TYPE
Communication method with which the document should be sent. This field is only relevant when the recipient is an address number, that is, when the document is being sent via external address management. If the field is not filled in this case, then the standard communication method defined in address management will be used.
The followig values are allowed:
'INT' : Send via Internet
'FAX' : Send as fax
'X40' : Send via X.400
'RML' : Send in another SAP system
LFDNR
Serial number from address management. This field is only relevant when the recipient is an address number, that is, when the document is being sent via external address management. If the field is not filled in this case, then the serial number defined in external address management will be 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 set ('X'), then the sender receives confirmation as soon as the document is delivered to the recipient. The sender also receives a message if the document could not be delivered. It is only logical to set this flag when sending externally because the internal send process runs synchronously. Confirmation, however, is only supported by a few mail systems, including X.400 and SAP SAP.
NOTIF_READ
If this flag is set ('X'), then the sender is informed as soon as the recipient reads the document. Setting this flag is only logical when sending externally because the internal send process runs synchronously. The read confirmation, however, is only supported by a few mail systems, including X.400 and SAP SAP.
NOTIF_NDEL
If this flag is set ('X'), then the sender receives a message if the document could not be sent to a recipient. It is only logical to set this flag when sending externally because the internal send process runs synchronously. The message, however, is only supported by a few mail systems, including X.400 and SAP SAP.
SAP_BODY
If this flag is set ('X'), then the SAP specific data is included with the document in an external body part when sending via X.400. This is only logical when the target system is an SAP system.
Exceptions

Can we join a table structure and a transparent table?

Pls let me know, whether we can join a table structure and a transparent table and how?

Hi rich,
     Since i dont have ur id ,iam posting my issue on this ,can u please help me on the below issue.
below i have a set of code which would sends email along with attachtment .
iam getting the XLS attachtment perfectly ,but for TXT attachtment there was problem with formating all the records are formated in single line .
a solution on this would be helpfull.
Thanks,
vinay .
FUNCTION Z_SHANKAR_ATTACHMENT.
""Local Interface:
*" IMPORTING
*"     VALUE(EMAILID)
*"     VALUE(SUBJECT)
*"     VALUE(ATYPE)
*" TABLES
*"      ATTACH_FILE STRUCTURE SOLISTI1
*"      BODY OPTIONAL
This table requires information about how the data in the
tables OBJECT_HEADER, CONTENTS_BIN and CONTENTS_TXT are
to be distributed to the documents and its attachments.
DATA OBJPACK LIKE SOPCKLSTI1 OCCURS 2 WITH HEADER LINE.
This table must contain the summarized data dependent on each object type.
SAPscript objects store information here about forms and styles,
for example. Excel list viewer objects store the number of rows and columns
amongst other things and PC objects store their original file name.
DATA OBJHEAD LIKE SOLISTI1   OCCURS 1 WITH HEADER LINE.
This table must contain the summarized content of the objects identified as binary objects.
DATA   OBJBIN TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0
                 WITH HEADER LINE.
This table must contain the summarized content of the objects identified as ASCII objects.
DATA OBJTXT LIKE SOLISTI1   OCCURS 10 WITH HEADER LINE.
This table must contain the document recipients.
DATA RECLIST LIKE SOMLRECI1 OCCURS 5 WITH HEADER LINE .
This structure must contain the attributes of the document to be sent.
DATA: DOC_CHING LIKE SODOCCHGI1.
DATA: TAB_LINES LIKE SY-TABIX.
Create the internal table for body , subject
DATA: IT_BODY LIKE SOLISTI1 OCCURS 10 WITH HEADER LINE.
*changes added to the code by shankar.
constants: x(1) type X value '0A'.
*End of changes to the code
CONSTANTS: con_cret TYPE C VALUE cl_abap_char_utilities=>horizontal_tab,
           con_tab TYPE C VALUE cl_abap_char_utilities=>cr_lf,
           con_new type c value CL_ABAP_CHAR_UTILITIES=>NEWLINE.
Move Body to Internal Table (body into it_body)
LOOP AT BODY .
    MOVE BODY TO IT_BODY .
    APPEND IT_BODY .
ENDLOOP.
DOC_CHING-OBJ_DESCR = SUBJECT.   "Subject of the Email
Move the Subject and Body to OBJTXT
OBJTXT[] = IT_BODY[].
DESCRIBE TABLE OBJTXT LINES TAB_LINES.
READ TABLE OBJTXT INDEX TAB_LINES.
DOC_CHING-DOC_SIZE = ( TAB_LINES - 1 ) * 255 + STRLEN( OBJTXT ).
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.
Convert IT to Excel format
IF ATYPE = 'XLS' .
LOOP AT ATTACH_FILE .
    REPLACE ALL OCCURRENCES OF '#' IN ATTACH_FILE WITH con_cret. " INTO objbin.
    CONCATENATE ATTACH_FILE con_tab INTO objbin.
    APPEND objbin.
ENDLOOP.
ELSEIF ATYPE = 'TXT' .
LOOP AT ATTACH_FILE .
    REPLACE ALL OCCURRENCES OF '#' IN ATTACH_FILE WITH con_tab. " INTO objbin.
    CONCATENATE con_new ATTACH_FILE-line INTO OBJBIN-line .
*changes done by shankar
*CONCATENATE ATTACH_FILE-line con_new INTO OBJBIN-line .
    APPEND OBJBIN .
ENDLOOP.
ENDIF.
****End-Code Excel Format .
DESCRIBE TABLE objbin LINES tab_lines.
objhead = subject. 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   = ATYPE.
objpack-obj_name   = 'ATTACHMENT'.
objpack-obj_descr = 'TEST'. "Attachment File Name
objpack-doc_size   = TAB_LINES * 255.
APPEND objpack..
reclist-receiver = EMAILID.
reclist-rec_type = 'U'.
APPEND reclist.
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
   DOCUMENT_DATA                    = DOC_CHING
   PUT_IN_OUTBOX                    = 'X'
   COMMIT_WORK                      = 'X'
IMPORTING
SENT_TO_ALL                     =
NEW_OBJECT_ID                   =
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 .
ENDFUNCTION.

Is it possible to control the parallel port with Lookout 5.0

I want a simple demo setup on a PC, so I can control the 8 data bits of the parallel port. Example, to use START p/b that would toggle bit 0 and data returned on bit 1.

It is possible to send bytes to the parallel port using the ASCII object within Lookout. However, it is presently not possible to control the state of the individual bits on the parallel port with Lookout.
If you need to control the individual bits on a parallel port, consider using LabVIEW. It is much more powerful when programming serial and parallel ports.

How do I activate a mobile phone when say a level in lookout goes high and sets off alarm.

I require to alert a user to an alarm condition both by web and mobile phone. I am not using a network just standalone PC

If you're using a standalone PC, then you can send SMS messages to cell phones using the ASCII Object when an alarm occurs. You'll connect a modem to your Lookout PC and use the ASCII Object.
You'll need to implement the SMS protocol in the ASCII Object.
I am not sure how you can update a web page from a stanalone PC tho'.
Hope this helps!
Rgds,
Khalid

Printer status in lookout

how can I Programmatically get the status of a printer connected to the LPT port.
what I need to do, is to confirm is that a page has been printed and if the printer has run out of paper or has a error

Hi,
There is no way to programmatically get the status of a printer in Lookout directly. What you could try to do though, would be to use the ASCII object and try to implement this communication yourself, you might be able to find a way to.
Best Regards
Andre Oliveira
Applications Engineer
National Instruments

Parallel port use Lookout

Does anybody know how to read/write through the parallel port with Lookout 5.0? Is there any example code for this?

Hi,
It is possible to send bytes to the parallel port using the ASCII object within Lookout. However, it is presently not possible to control the state of the individual bits on the parallel port with Lookout.
If you need to control the individual bits on a parallel port, consider using LabVIEW. It is much more powerful when programming serial and parallel ports.
Remzi A.
National Instruments

6B AND lookout

Are there any Lookout drivers available for the old Analog Devices 6B modules?

I could not find any native Lookout drivers (CBXs) for the 6B. However, there are couple of OPC Servers available by third-party vendors:
6b OPC Server from Kepware Technologies
6B TOP Server from Software Toolbox
Alternatively, we could write our own "driver" using the ASCII Object. I faintly remember the 6B command set to be very simple (you will however need their manual; they don't publish the protocol freely). Here's a good tutorial on communicating with devices using ASCII Object.
Hope this helps,
Khalid

ASCII Object

Similar Messages

Maybe you are looking for