Query on downloading to XLS file

Question

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 .

Answer 1

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