Reg : The functionality of WMMBID02 Basic type in SAP.
Hi All,
Can anyone give me the functionality of WMMBID02 Basic type in SAP. Mean, not the structure of the Idocs i am talking about. But to which Module of SAP is it related to and what kind of inventory data it carries? what the significance of this data. which table get updated when this idocs gets posted successfully.
And also that, From table /GLB/RGTTPLANHED, we can get the trip status. So wat exactly this trip status indicates?... can anyone explain this in detail?
The message typer for this is WMMBXY and its used for Goods movement between storage location. This would internally calls MB01 transaction and related to MM module.
Similar Messages
-
How to find IDOC Function Module for Basic Type:ORDERS05
Hi,
What is the Transaction Code to locate the Function Module linked to the IDOC Basic Type & IDOC Message Type?
Appreciate Your Help.
Thanks,
Kannan.Hi Seshu,
Thanks for your reply. While creating a Custom IDOC, How do I link the IDOC Function Module and Basic Type. Appreciate Your Help.
Thanks,
Kannan. -
Reg. the creation of new data type in ECC 6.0
Hi All,
I have a requirement wherein I need to create a new data type INT with length as 4. Is there any way that we can add create a new data type.
Thanks in advance,
Durga.I have tried using t-code SE11 but i am unable to create.
-
What is the functionality of &VBDKR-NETWR( 10)& in sap script and smartform
Dear All,
I came across this &VBDKR-NETWR(<10)& when I was migrating the script as smartform. I would like to know wht is functionality of &VBDKR-NETWR(<10)& i.e. <10's meaning. I am facing problem in printing the amount. So many alignment problems are coming.
Please help me on this.
Thanks in Advance.
J.hi,
&VAR(<10)& means output will be printed with sign to tjhe left (<) and output length is 10 (10)
here an overview with the most use formating symbols
&VAR(En)& Exponent number (n)
&VAR(Ff)& Fill character
&VAR(K)& Ignore conversion rules
&VAR(<)& sign to the left
&VAR(>)& sign to the right
&VAR(.n)& number of decimals
&VAR(+n)& offset
&VAR(Z)& omit leading zeroes
&VAR(S)& omit leading sign
&VAR(T)& omit thousand sepearator
&VAR(n)& outputlength n
&VAR(R)& right justified
&VAR(C)& condensed
&VAR(I)& suppress initial value
success,
Gr,. Frank -
What is the process code for message type FIXEDASSET_CREATE?
Hi all
please tell me that what is the process code for
MESSGAE TYPE = FIXEDASSEt_CREATE,
FUNCTION MODULE = IDOC_INPUT_FIXEDASSET_CREATE,
BASIC TYPE = FIXEDASSET_CREATE01 ?
thanx in advance.......
Edited by: Prachi Sharma on Jan 11, 2008 7:45 AM
Edited by: Prachi Sharma on Jan 11, 2008 8:03 AMHi,
Check the Tcodes WE41 and WE42 for Outbound and Inbound process codes
Check below Tables as well
EDE1T
EDE2T
EDE5T
EDE6T
TEDE5
TEDE6
Regards,
Satish -
Prob wth Extending HRMD_A06 basic type
Hi All,
I have some custom fields in PA0002 table. So i extended HRMD_A06 and in user-exits i am populating custom fields. Out bound side everything is OK. But it is giving 51 error in inbound side. Probelm with read_namtb subroutine. it is chking the custom segment in T777D table...
I am unable to solve the problem. Can anyone hlp me in this regard.May be this helps you !!
<b>
FYI</b>
<b>Symptom</b>The standard scenario for the distribution of HR master data and organizational data via message type HRMD_A only covers a limited number of infotypes.
Additional standard infotypes should be distributed using a customer enhancement.
Other terms
PFAL, RHALEINI, HRMD_A
Reason and Prerequisites
In the standard scenario, only infotypes are distributed, which are required for a distributed HR in a non HR-system.
Solution
The following activities are required if standard infotype Pnnnn (with nnnn = infotype number) is to be distributed in addition.
Consider the restrictions at the end of this note in particular!
Release 3.1
1. Source code corrections:
According to the attachment (programs not contained in the standard system), repairs are necessary in the Includes LRHA2U06 and UP50RU01.
You only have to change Include UP50RU01 if it is a PA infotype.
If you also want to distribute infotypes starting with 2nnn or 9nnn, an additional repair in Include LRHALF01 is necessary. Remember that in this case the Infotype 2011 is stored differently than the other infotypes and cannot therefore be distributed.
Note that these changes are not contained in the standard system.
2. Customizing:
Transaction WE31 for Z1Pnnnn (in the sending system and the receiving system):
For each additional infotype, create a new segment type Z1Pnnnn (with nnnn = infotype number).
Transaction SM30 for table T777D only for PD infotypes (in the sending system and the receiving system):
For the entry infotype nnnn, enter Z1Pnnnn in field IDOC segment.
Transaction WE30 for ZRMD_A01 (in the sending system and the receiving system):
With Transaction WE30, create extension ZRMD_A01.
Create E1PITYP as a reference segment type, as child segments of this, the extension segment types Z1Pnnnn. As an IDoc type, create ZRMD_A01 for the basic IDoc type HRMD_A01 and extension ZRMD_A01.
Transaction WE82 (in the sending system and the receiving system):
The entry for message type HRMD_A and basic IDoc type HRMD_A01 is copied to a new entry with the extension ZRMD_A01.
Transaction WE20 (in the sending system):
In the sending system, for the partner number of the receiving system in the outbound parameters, enter ZRMD_A01 as idoc type in the line for entry message type HRMD_A.
Transaction WE57 (in the receiving system):
Copy the entry for function module name IDOC_INPUT_HRMD, basic IDoc type HRMD_A01 and message type HRMD_A, and enter ZRMD_A01 in the field extension.
As of Release 4.0B
1. Source code corrections:
Implement the attached advance corrections or:
Apply Hot Package for 4.0B: SAPKH40B02 or
Legal Change Patch for 4.0B: SAPKE40B02
The Include UP50RU01 must only be changed if it is a PA infotype.
Include UP50RU01 is not contained in the Hot Package and must be changed in accordance with the advance correction if the Legal Change Patch is not applied.
After applying the Hot Package (and manually repairing the UP50RU01) or the Legal Change Patch, only the Customizing activities are necessary.
2. Customizing
Transaction WE31 for Z1Pnnnn (in the sending system and the receiving system) :
For each additional infotype, create a new segment type Z1Pnnnn (with nnnn = infotype number). The function "Create by copying" can be used to reduce the work load.
Transaction SM30 for table T777D (in the sending system and the receiving system):
For entry infotype nnnn, enter Z1Pnnnn in field IDOC segment.
Transaction WE30 for ZRMD_A02 (in the sending system and the receiving system):
With Transaction WE30, recreate extension ZRMD_A02.
The linked basic type is HRMD_A02. Insert the new Z1Pnnnn segments as child segments of E1PITYP.
Transaction WE82 (in the sending system and the receiving system):
Copy the entry for message type HRMD_A and basic type HRMD_A02 to a new entry with extension type ZRMD_A02.
Transaction WE20 (in the sending system):
In the sending system enter ZRMD_A02 as an 'Extension' for the partner number of the receiving system in the outbound parameters in the entry message type HRMD_A with basic type HRMD_A02.
Transaction WE57 (in the receiving system):
Copy the entry for the FM name IDOC_INPUT_HRMD, basic type HRMD_A02 and message type HRMD_A, and in field 'Extension' enter ZRMD_A02.
As of Release 4.5A
Here, the Customizing activities described in Release 4.0B are to be carried out.
As of Release 4.5A, HRMD_A03 is used as the basic type and ZRMD_A03 is used as the extension type.
As of Release 4.6A, HRMD_A04 is used as a basic type and ZRMD_A04 is used as an extension type.
As of Release 4.6C, HRMD_A05 is used as a basic type and ZRMD_A05 is used as an extension type.
As of Release 4.70, HRMD_A06 is used as a basic type and ZRMD_A06 is used as an extension type.
Restrictions:
SAP cannot offer any support concerning compatibility with different releases for the additional infotypes of the enhancement in the standard system. For release specific changes to the infotypes of the enhancement a client-specific solution must be found (project solution).
Other known restrictions:
Known restrictions are listed here with possible solution approaches. If you should discover a restriction that is not yet documented, you can inform us of this via the R/3 SAPNet Frontend with a low priority problem message.
01/25/1999: PA infotypes with subtypes are not found in T591A
For infotypes in personnel administration, whose subtypes are stored in a different table than T591A according to table T582A, distribution works in the transfer mode 'Insert' and using the change pointers. Distribution in the transfer mode 'Update' does not work. The approach to solve the problem is a customer-specific extension of the routine HR_INFTY_GET in program RHALEINI by the corresponding infotype/subtype combinations.
02/01/1999: Workflow infotypes
Workflow infotypes, thus in the area 12xx, are not supported since the object type workflow is not supported in the standard ALE scenario. The approach to solve the problem is the use of the manual transport connection (RHMOVE30).
05/17/1999: Infotype 2011
The Infotype 2011 is stored differently than the other infotypes and therefore cannot be distributed.
11/09/2000: Segment for infotypes with a width of more than 1000 characters
The maximum width of a segment is 1000 characters. For this reason it cannot be generated automatically for infotypes with a width of more than 1000 characters.
A possible solution is to create the segment manually and to only insert the key fields and the application fields that are really needed in the segment in order to avoid exceeding the 1000 characters. The values of the fields are transported from infotype into the segment and vice versa in the case of infotypes that are distributed additionally. The reason is that the fields have the same names in segment and infotype.
07/17/2002: In ALE inbound processing, only the data records of the infotypes are posted - similar to the infotypes to be distributed in the standard. No additional functions regarding possibly dependent or derived data in other (database) tables are executed. A solution approach is to distribute the dependent or derived data in a separate (customer) scenario or implement a customer exit (RHALE001) or a BADI (HRALE00INBOUND_IDOC) with the desired functionality.
<b></b> -
hi iam having z-basic type how to find what is the standard idoc type(for ex MATMAS,Creamas) for that
Step1. Go to WE30 and give the extended IDoc name
Step2. Check the extension button and click on display
Step3. Click on header button (Top 3rd left button)
Step4. In Technical Attributes, you will get the name under "Linked Basic Type"
Hope it solves your query...
Regards,
Prasoon Sahay
Edited by: Prasoon Sahay on Sep 2, 2009 2:18 PM -
Hi all,
can any one take me the structure of Idoc Basic type PEXR2003.
WE60 ==> Basic Type checked ==> enter PEXR2003 ==> F9 key
Thanks in advance
Ragerds
MercuryxUp,
No ideas?????? -
Basic type, Idoc type, Message type
hi,
can anyone please explain me the exact difference between basic type, idoc type and message type...
Thanks in advance,
KrishHi,
Idoc Types and the Basic Types are the same which is provided by SAP Standard Idoc Names.This will have the releases like 01, 02 ,03
And the Message type names will be the same as Idoc type name with out releases
The combination of the message type & Idoc type will be------CREMAS.CREMAS03( Message type.Idoc type)
Check this Screen for better clarity , and we added some extra Segments to the standard Idoc also, so thats why it has the Extension also
http://img182.imageshack.us/img182/3749/64960008jl7.jpg
Regards
Seshagiri
Edited by: N V Seshagiri on Aug 20, 2008 8:51 AM -
Error: Basic type 'WVINVE03' is unknown
hi sdn frnds
I am doing File to Idoc scenario in that i am getting the error as
Error: Basic type 'WVINVE03' is unknown
can any one know about this and how to solve this problem
thanks in advance
VasuHi,
where do you try to find this idoc?
this IDOC should only be in the R3
(not in the XI)
if you want it in the XI you need
to download it's sigmature in <b>integration repository</b>
just like described here:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a> -
SAP B1- Can we have the functionality of Indent to purchase?
Dear All,
Can we have the functionality of Indent to purchase in SAP B1-Client? If yes, kindly let me know the necssary steps.
Thanks in advance..!
Regards
RounakHi Rounak.....
This is your duplicated thread with same doubt so please close this one...
Any ways.....
Hi Rounak......
Purchase Indent is not as such there in B1 but you can get it done by having approval procedure on Purchase Order level.
Purchase before approval is nothing but Indent....
Regards,
Rahul -
Deactivating the Function codes of Buttons on standard RF screen
I have to deactivate the functionality of some of the function keys(Buttons) on Std. SAP RF Screen(Quant screen) of LM51 transaction (Pgm: SAPLLMOB & Screen# 0152). How can I achieve this. I appreciate if any one can guide me on this.
Thanks
UshaHi,
Try this out with Transaction Variant (T.code is SHDO)
<b>Transaction SHD0 -</b> Create a variant for the required transaction bychanging the layout through hiding fields and screens
The Below data i copied from the web, this may helpyou ...
Case one for creating Transaction Variants
Step 1:
Execute transaction SHD0 and create a Transaction Variant against the original transaction.
Step 2:
As soon as you press the create button, the original screen of the transaction will appear. After pressing any button/tab on the screen a menu variant screen will appear. Make sure to check any field or tab or any button you want to disappear from the menu functions. Press the exit and save button when you are sure that no further settings are required on sub-screens (if present). After pressing the exit and save button another menu variant screen will appear. Press the save button here and save as a local object or under any development class.
Step 3:
When you are back on the Transaction Variant (SHD0) screen, press shift+F6 or click the goto menu and press the create variant transaction button. Through this transaction SE93 will be executed. Enter the transaction name you want to create and any other required field and now press the save button.
Step 4:
Now execute the transaction you create through create Transaction Variant and enjoy the results.
Case two for creating Transaction Variants
Step 1:
Create a dialogue transaction through SE93 and enter the program name and screen number of the original transaction you want to make a variant on (e.g., PFCG). Press the save button and check whether the replica transaction (PFCG) has been created successfully by executing it on a new session.
Step 2:
Execute transaction SHD0 to create a Transaction Variant. Specify the transaction name (replica of PFCG) which you have just created and create a Transaction Variant against the replica transaction.
Step 3:
As soon as you press the create button, the original screen of the transaction will appear. After pressing any button/tab on the screen a menu variant screen will appear. Make sure to check any field or tab or any button you want to disappear from the menu functions. Press the exit and save button when you are sure that no further settings are required on sub-screens (if present). After pressing the exit and save button another menu variant screen will appear. Press the save button here and save as a local object or under any development class.
Step 4:
When you are back on the main screen of the SHDO (Transaction Variant) click the edit option on the menu tab and activate Standard Variant. Through this a Standard Variant will be assigned to the transaction specified (replica transaction).
Regards
Sudheer -
Function module to send mail from SAP
Can any one please tell the Function module to send mail from SAP. The scenario is like this,I have a file in local system that i have to send to a particular mail address like [email protected] through a report program.
Hi shafiq,
1. There is some trick involved
in the binary files.
2. I have made a program (and it works fantastic)
ONLY 6 LINES FOR EMAILING
BELIEVE ME
ITS A FANTASTIC PROGRAM.
IT WILL WORK LIKE OUTLOOK EXPRESS !
3. The user is provided with
a) file name
b) email address to send mail
and it sends ANY FILE (.xls,.pdf .xyz..)
Instantaneously !
4. Make two things first :
1. Include with the name : ZAMI_INCLFOR_MAIL
2. Report with the name : ZAM_TEMP147 (any name will do)
3. Activate both and execute (2)
4. After providing filename, email adress
5. Code for Include :
10.08.2005 Amit M - Created
Include For Mail (First Req F16)
Modification Log
Data
DATA: docdata LIKE sodocchgi1,
objpack LIKE sopcklsti1 OCCURS 1 WITH HEADER LINE,
objhead LIKE solisti1 OCCURS 1 WITH HEADER LINE,
objtxt LIKE solisti1 OCCURS 10 WITH HEADER LINE,
objbin LIKE solisti1 OCCURS 10 WITH HEADER LINE,
objhex LIKE solix OCCURS 10 WITH HEADER LINE,
reclist LIKE somlreci1 OCCURS 1 WITH HEADER LINE.
DATA: tab_lines TYPE i,
doc_size TYPE i,
att_type LIKE soodk-objtp.
DATA: listobject LIKE abaplist OCCURS 1 WITH HEADER LINE.
FORM
FORM ml_customize USING objname objdesc.
Clear Variables
CLEAR docdata.
REFRESH objpack.
CLEAR objpack.
REFRESH objhead.
REFRESH objtxt.
CLEAR objtxt.
REFRESH objbin.
CLEAR objbin.
REFRESH objhex.
CLEAR objhex.
REFRESH reclist.
CLEAR reclist.
REFRESH listobject.
CLEAR listobject.
CLEAR tab_lines.
CLEAR doc_size.
CLEAR att_type.
Set Variables
docdata-obj_name = objname.
docdata-obj_descr = objdesc.
ENDFORM. "ml_customize
FORM
FORM ml_addrecp USING preceiver prec_type.
CLEAR reclist.
reclist-receiver = preceiver.
reclist-rec_type = prec_type.
APPEND reclist.
ENDFORM. "ml_customize
FORM
FORM ml_addtxt USING ptxt.
CLEAR objtxt.
objtxt = ptxt.
APPEND objtxt.
ENDFORM. "ml_customize
FORM
FORM ml_prepare USING bypassmemory whatatt_type whatname.
IF bypassmemory = ''.
Fetch List From Memory
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
listobject = listobject
EXCEPTIONS
OTHERS = 1.
IF sy-subrc <> 0.
MESSAGE ID '61' TYPE 'E' NUMBER '731'
WITH 'LIST_FROM_MEMORY'.
ENDIF.
CALL FUNCTION 'TABLE_COMPRESS'
IMPORTING
COMPRESSED_SIZE =
TABLES
in = listobject
out = objbin
EXCEPTIONS
OTHERS = 1
IF sy-subrc <> 0.
MESSAGE ID '61' TYPE 'E' NUMBER '731'
WITH 'TABLE_COMPRESS'.
ENDIF.
ENDIF.
Header Data
Already Done Thru FM
Main Text
Already Done Thru FM
Packing Info For Text Data
DESCRIBE TABLE objtxt LINES tab_lines.
READ TABLE objtxt INDEX tab_lines.
docdata-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 = 'TXT'.
APPEND objpack.
Packing Info Attachment
att_type = whatatt_type..
DESCRIBE TABLE objbin LINES tab_lines.
READ TABLE objbin INDEX tab_lines.
objpack-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( objbin ).
objpack-transf_bin = 'X'.
objpack-head_start = 1.
objpack-head_num = 0.
objpack-body_start = 1.
objpack-body_num = tab_lines.
objpack-doc_type = att_type.
objpack-obj_name = 'ATTACHMENT'.
objpack-obj_descr = whatname.
APPEND objpack.
Receiver List
Already done thru fm
ENDFORM. "ml_prepare
FORM
FORM ml_dosend.
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
document_data = docdata
put_in_outbox = 'X'
commit_work = 'X' "used from rel. 6.10
IMPORTING
SENT_TO_ALL =
NEW_OBJECT_ID =
TABLES
packing_list = objpack
object_header = objhead
contents_bin = objbin
contents_txt = objtxt
CONTENTS_HEX = objhex
OBJECT_PARA =
object_parb =
receivers = reclist
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
IF sy-subrc <> 0.
MESSAGE ID 'SO' TYPE 'S' NUMBER '023'
WITH docdata-obj_name.
ENDIF.
ENDFORM. "ml_customize
FORM
FORM ml_spooltopdf USING whatspoolid.
DATA : pdf LIKE tline OCCURS 0 WITH HEADER LINE.
Call Function
CALL FUNCTION 'CONVERT_OTFSPOOLJOB_2_PDF'
EXPORTING
src_spoolid = whatspoolid
TABLES
pdf = pdf
EXCEPTIONS
err_no_otf_spooljob = 1
OTHERS = 12.
Convert
PERFORM doconv TABLES pdf objbin.
ENDFORM. "ml_spooltopdf
FORM
FORM doconv TABLES
mypdf STRUCTURE tline
outbin STRUCTURE solisti1.
Data
DATA : pos TYPE i.
DATA : len TYPE i.
Loop And Put Data
LOOP AT mypdf.
pos = 255 - len.
IF pos > 134. "length of pdf_table
pos = 134.
ENDIF.
outbin+len = mypdf(pos).
len = len + pos.
IF len = 255. "length of out (contents_bin)
APPEND outbin.
CLEAR: outbin, len.
IF pos < 134.
outbin = mypdf+pos.
len = 134 - pos.
ENDIF.
ENDIF.
ENDLOOP.
IF len > 0.
APPEND outbin.
ENDIF.
ENDFORM. "doconv
CODE FOR PROGRAM
5.
REPORT zam_temp147 .
INCLUDE zami_inclfor_mail.
DATA
DATA : itab LIKE tline OCCURS 0 WITH HEADER LINE.
DATA : file_name TYPE string.
data : path like PCFILE-PATH.
data : extension(5) type c.
data : name(100) type c.
SELECTION SCREEN
PARAMETERS : receiver TYPE somlreci1-receiver lower case.
PARAMETERS : p_file LIKE rlgrap-filename
OBLIGATORY.
AT SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CLEAR p_file.
CALL FUNCTION 'F4_FILENAME'
IMPORTING
file_name = p_file.
START-OF-SELECTION
START-OF-SELECTION.
PERFORM ml_customize USING 'Tst' 'Testing'.
PERFORM ml_addrecp USING receiver 'U'.
PERFORM upl.
PERFORM doconv TABLES itab objbin.
PERFORM ml_prepare USING 'X' extension name.
PERFORM ml_dosend.
SUBMIT rsconn01
WITH mode EQ 'INT'
AND RETURN.
FORM
FORM upl.
file_name = p_file.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = file_name
filetype = 'BIN'
TABLES
data_tab = itab
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17.
path = file_name.
CALL FUNCTION 'PC_SPLIT_COMPLETE_FILENAME'
EXPORTING
complete_filename = path
CHECK_DOS_FORMAT =
IMPORTING
DRIVE =
EXTENSION = extension
NAME = name
NAME_WITH_EXT =
PATH =
EXCEPTIONS
INVALID_DRIVE = 1
INVALID_EXTENSION = 2
INVALID_NAME = 3
INVALID_PATH = 4
OTHERS = 5
ENDFORM. "upl
regards,
amit m. -
Do we have any functionality to handle stale cheques in sap
Dear Guru's,
I need the functionality to handle stale cheques in sap. If any configuration is required then plz let me know, it's urgent.
Thanks in Advance,
KishoreHi,
You have to void cheques individually.
What we are doing is that we have done a Z program calling FCH9 and created a BDC for mass void
in selection you give the date range so that you can choose a date prior to six months.
Get the help of an ABAPer
Assign points if useful
Sunoj -
Functionality in long text -- include -- characters-- SAP Icons
Can any one please tell me the functionality in long text -->include >characters>SAP Icons. Is it possible to include any icon in longtext.
regards
RavikumarHi,
The standard icons should be available. If not, see note [1067936|https://service.sap.com/sap/support/notes/1067936] that explains how they can be made available.
-Paul
Maybe you are looking for
-
I am wondering if using a Mac Mini with a 26" HDTV would give me equivalent or better image quality than I would merely get by using a 27" iMac? I want to use my Mac in 2 different locations (staying in each for several mos at a time), and am conside
-
APD - Column Headers are not displaying properly when downloaded
Hi All, I am trying to download a simple query as a comma delimited file on my desktop using APD. When I execute the APD, the all the data getting properly downloaded as required but I am facing the following problems. 1) The column heading are comin
-
I am unable to run any of the sample VB Scripts on Win 7. I checked the WScript.exe and it exists in both the system and SySwow folders. Can anyone suggest me as to what I might be doing wrong ?
-
Sync videos other than purchased from iTunes
I ripped my own videos (concerts, etc.) using Handbreak software, but I can not manage to sync them to Apple TV. What should I do? and How should I do it? any dieas? thanks in advance
-
HT3702 Cancelling itunes download once the deed is done
I made a mistake. How do I undo it? Tried calling Apple support. No luck getting a real human being. Help!