Incorrect document types?

I'm not sure if this really belongs in "Customization," so bear with me.
I recently restored all my data following a fatal hard drive crash. Everything seems to be working fine, but I've run into an odd situation with my Microsft Word documents.
For some reason, they are all displayed with a generic icon, but the file preview window confirms that the computer understands that they are a Microsoft Word document. If I just double-click on the file, it looks like the computer briefly starts up an unknown program -- not MS Word, tho -- but then nothing.
I can manually go into the Get Info box of the individual MS documents and set them to be opened by MS Word (as they used to before the crash/restore), but that seems tediously inefficient, as I'd have to do that to hundreds of files all across my hard drive.
Looking around the system, it appears that the 'default' application that the computer seems to think should be used for these documents is, strangely enough, a gif image (not even an application). I got rid of the image, and now the computer seems to think that the document's default application is an apparently random PDF document instead.
I tried using the 'Change all' option in one of the Word doc's Get Info screens where it allows you to change the default application globally, but that doesn't seem to work either. In fact, if I try it on an individual file I've already manually selected the default document properly for, it not only doesn't change anything globally, but actually goes ahead and resets the Word doc's default applciation to that PDF file again (even though the confirmation windows reads fine).
I seem to recall there was a program or utility somewhere that governed all these extension maps, but I'll be darned if I can find it. Any suggestions on how to fix my problem?
iMac Mac OS X (10.3.9)

The script may be for Tiger.
Try this (from Dr. Smoke's The XLab).
1 Quit all running applications.
2 Trash the com.apple.LaunchServices.6B.csstore file in the Macintosh HD > Library > Caches folder. Type your Admin password if prompted to authenticate the deletion of this file.
3 Restart your Mac.
4 Log in to the affected account.
5 Empty the Trash.
6 Verify that the problem is solved. If not:
a Trash the com.apple.LaunchServices.plist file in the Home > Library > Preferences folder of the affected account.
b Repeat steps 1-5.

Similar Messages

Change Document Types for CV02N

Hi
We implemented SAP content server and have assigned a lot of the documents in CV01 to a wrong/incorrect Document type.
Now we have to limit the authorization based on the document type.
We were wondering if there is a way to change the Document Type of an uploaded document, say for example, Change a document from Document type "NPO" to say "NSC" or vise versa.
Is there a report of something that can help us?
Thanks
Abhi

You will not be able to change the document type of already uploaded documents...
Instead you can go to those DIRs and mark those DIRs for deletion and run a Standard SAP Program "MCDOKDEL" in T-code SE38 which will delete all DIR marked for deletion.
Afterwards you can create DIRs under right Doc Type,
Control Authorization based upon Doc. Type - use Tcode PFCG

This error is often caused by incorrect use of the "Strict" document type

Okay...so I have 6 errors - all the same and has to do with my document type.
I've searched the code and I am using a transitional doc type so why the errors?
http://02cada7.netsolhost.com/Stasik_Family_Website/index.html

Yeah I did that...but the cause doesn't make sense to me.
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
I'm not using a strict document time - I am using transitional and I am not using proprietary extensions.

Incorrect requirements type in sales doc.

HI,
Due to incorrect requirements types of material the costs and sales volume are posted directly to sales doc instead of posting
to WBS element.
How can this be fixed (after cancellation of posting)?
How can we identify already created u201Cincorrectu201D sales docs?
Regards,
Anup
Edited by: anup12 on Jun 3, 2011 7:29 AM

Hi !
regarding your query, there may be various sales documents type which might be created during configuration.
Some of these might not be required by end users and need to be blocked so that wrong document types are not chosen. so an indicator 'X' is placed againt these document types and these can not be used.
There may be some documents wherein manual creation might not be allowed, and auto creation is desired. so againt these doc types-'A' is placed by which these doc types can not be created manually,
Other sales doc types might not be blocked so that they can be used or created manually, hence kept blank against the indicator field.
Plz reward point if useful.

Easy DMS document type issue

Hi Gurus,
DMS configuration done in SAP R/3 and able to see all configured document types in sap easy dms as well. But document description wrongly showing under document types.
SAP R/3                                                       EASY DMS
Eg:1   ZSD sales document                          Eg 1 : ZSD    material document
Eg 2 ZMM material document                      Eg2:   ZMM    sales document.
Please help me on this.
Regards,
Nithal.

Hi Chandu,
Everything fine.
In SAP r/3 , document type & document description correctly given but while in EasyDMS document type picking incorrect document description. Remains no issue in easyDMS.
Please help.
Regards,
Nithal.

Invoice Reduction - Incorrect Document Number Transferred

I am attempting Total-Based Invoice Reduction on an IDoc that is held up in Invoice Overview.
As far as I can tell, the document types are correct and the number ranges are correct.
The RD and RS ranges are pointing to internally assigned numbers beginning with 51 and the RE and (invoice reduction) ZI document types for MR1M are pointing to number range 51 which is external.
What can I be missing to get the following error?
Incorrect doc.no.: $ 2. Select document number between 5100000000 and 5199999999
Message no. F5151
Diagnosis
The document number you specified, "&v1", is not in the appropriate number range. The number range is dependent on the document type.

It seems that the Invoice Reduction Document Type did not have the correct numbering assignment - it was external when it should be internal.
In my mind I was thinking the invoice reduction document would be a transfer from MM, but it is not. It is an internally created financial document so it need an internal document assignment.

'Incorrect value type for array element in index N'

Please help. Preflight is flagging multiple 'Incorrect value type for array element in index N" > Required key /F is missing >Array element at index 0 is of wrong type' messages for pages throughout my text document with embedded navigation and annotations.What does it mean? Is there anything I can do?
The origins of the file are from a selection of emails taken from Mail and gmail, and letters probably written on pc (Office) and converted to pdf...
I'm on Mac Mavericks.
Thanks for reading.

What problem are you trying to solve with preflighting? What are you checking for?

Error Document type "" not defined

Hi All,
I am getting below error message when i am trying to see the output of a query build on Infoset in SAP R3 system.
The Infoset is build on top of BKPF,BSEG and EKPO Tables.
Document type not defined
Message no. F5814
Diagnosis
Financial Accounting service: document type "" was not found in the document type table. There are two possible causes:
document type "" has not been set up in FI customizing
document type is supplied incorrectly from the calling application
System Response
System error.
Procedure
There are two possible measures:
set up document type "" in FI customizing
system error within the calling application - get in contact with the SAP Hotline Service.
Any input on above issue will be of great help.
Regards,
Anjali Singh

Hi Anjali,
In which system you are getting this error? Development or Production?
I think you have doc. type just in BKPF (Accounting documents headers). Check if you have any record with document type blank.
You can use t code SE16N for this issue. When you are setting filter on field "document type" (BLART) you can see the list of values. Check if there is any blank item
Regards,
Omid

Incorrect message type in IDOC for Purchase order change

Hi Gurus.
Please advise on below.
We have several purchase orders that are configured to trigger IDOC upon change. But accidentally, someone has deactiveted the automatic proposal of EDI message type for these Purchase orders which resulted to not transmitting purchase order change documents automatically.
As a workaround, we have proposed to create EDI message manually during Purchase order change. But upon checking in tcode WE09, message type is ORDERS which is PO create instead if ORDCHG for purchase order change.
Please kindly advice on why it is behaving like this for purchase orders with EDI message previously deactivated.
Thanks in advance.
Acel.
To simulate.
Create PO. go to messages, select EDI message then deactivate permanently. Save PO. Release PO if needed. Change PO. go to messages, EDI is not automatically proposed. create EDI message mamanually. Save PO. Release PO id needed. check tcode WE09, for PO create, no IDOC since it was deactivated permanently. For PO change, IDOC was triggered but with incorrect message type ORDERS instead of ORDCHG.

Hi Acel,
You will need to check the settings in transaction WE20 - You will be using a Partner Profile to determine the outbound message, either for each vendor or a generic one.
on the outbound parameters, you will need to ensure that ORDCHG is set up as a message type. If not, add it, ensuring that you use the message ORDCHG, the basic type (or extension) that you are using, usually ORDERS05 and make sure that in message control, you have process code ME02 set up. This should enable the correct message type to be determined.
Regards,
Rob

Document type with posting level 12 not being carryforward

Hi gurus,
We are now implementing SEM-BCS 6.0 in the BI 7.0 server.
We have a document type u201CMIu201D which properties are:
Posting level: 12
Balance check: 0 error when balance note equal to zero
Application: Other
Posting: Manual posting
Inversion: No automatic inversion
The problem is that when we execute the Balance Carryforward in the subsequent year this is the only document type that is not being carryforward.
Why is this happening?
Thanks for your help.
Best regards.

This is by design
http://help.sap.com/saphelp_erp60_sp/helpdata/en/0c/ab0240536fe369e10000000a155106/content.htm
"Data records for preparatory postings for consolidation group changes are neither translated nor carried forward."
I'll try an example...
Company A is sold from company 1 to company 2 in June (EoP)
For periods 0 - 6:
BCS reports company A's balance sheet under company 1
BCS reports company A's income statement under company 1
starting period 7
BCS reports company A's balance sheet under company 2
BCS reports company A's 0 - 6 income statement under company 1
BCS reports company A's 7 income statement under company 2
this is managed through the posting level 02 12 and 22 document types, as well as PL30 if using CoI.
Assuming the period of first consolidation and period of divestiture were set correctly in the groups for company 1 and company 2, BCS wants to read all 0 - 6 data under group 1 and all 7 + data under group 2. This is obviously incorrect from an accounting standpoint and the PCC postings correct that.
So BCS books a PL02/12/22 in group 1 to zero out the balance sheet. It then books another set of entries in group 2 to write up the entire balance sheet in the new group.
However, once you get to the end of the year and run your BCF, the entire balance sheet is now sitting in period 0. The system is able to report company A's balance sheet under group 2 withou the aid of the PCC documents. Therefore, the system does not roll these documents forward into the new year.
The PCC documents were only required because of the periodic nature of the BCS data storage vs. the LTD nature of the balance sheet for reporting. Once the full LTD balance is available in a single period, as is the case just after a BCF, the PCC documents are no longer required.
Anyway, hope that made some sense. If not, I'd encourange you to create an Excel sheet replicating how BCS stores the data in the cube, perfrom a divestiture, and see why the system is not carrying forward the documents. This is how I came to understand it.
Now, if you're doing something "non-standard" with the PL12, all bets are off
Good luck,
Chris

Search via classification in CV04N returns incorrect documents

When doing a search in SAP DMS CV04N using classification, and incorrect list of DIRs return. The search criteria is for one signle value, but it returns documents that does not form part of the search criteria.
Any suggestion as to what the problem can be?
Thanks
Pierre

hi,
1. Document may be not indexed For TREX.
2. In define Charectristics u need to maintain Class type 017, DMS, in the field Restrict.
3. Check whether u set class and class type for perticular document type, in tc- DC10, basic data screen.
Benakaraja
??P

Document Type Change

Hi evryone,
We have a scenario in which the client has migrated documents from an old PDM system to SAP DMS .
Now there are some 1000 documents which have been migrated with a wrong document type & we want to change the
document type of those documents.
Is there any way this can be accomplished?What is the recommended way of doing it ?
Hoping to hear from you all.
Thanks in advance.
Regards
-Neha

Hi Neha,
Kindly follow follwoing steps for this:
1. If you have a program available for the migration then correct the document types which are incorrectly transferred and then reupload these documents from old to new.
2. If you don't have program of old system available. Then write a bdc for these documents in new systen and run it all records will get updated.This can be achived with help of abap'r. use t-code SHBD.
Hope this will reolve the query.
- Ravindra

Mistake posting financial document using document type AA

HI,
The client post a journal entry document through FB01 but select document type AA (Asset transaction) and this financial document is posted as the document type AA.
Now, she run transaction ASKB but she keeps getting the error : "Internal error in item 0000000000: asset row is not complete"
and she cannot move on.
Is there any solution to this problem?
Thank you.

Verify that the incorrect financial document and its reversal document have the same offsetting entries. Also make sure you re-run any asset process that occur normally before ASKB gets ran.
Although I have never had this particular problem. I am seeing many posts that refer to this problem being related to asset reconciliation accounts. Meaning that the accounts used for periodic posting in ASKB cannot be set as reconciliaton accounts.
If you know the accounts used with ASKB, make sure they are not included in transaction OAMK. I think you can also display the GL account using FS00 and look at the control data tab to see if the reconciliation account indicator is set for "A" assets.
Perhaps the following thread will help..
Error while AFAB Run
The thread references notes 7595 and 859617

Document type declaration for root element type "web-app" must end with ' '

I am attempting to deploy an application (.war file) using the Sun Access Manager Agent installed, (Reference http://docs.sun.com/app/docs/doc/819-3201/6n5eht3k4?a=view -near the bottom) and I get this error:
Error loading deployment descriptors for ajacs Line 3 Column 19 -- The document type declaration for root element type "web-app" must end with '>'.
Here is the relavent code:
<!DOCTYPE web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<web-app>
<filter>
<filter-name>Agent</filter-name>
<filter-class> com.sun.identity.agents.filter.AmAgentFilter </filter-class>
</filter>
<filter-mapping>
<filter-name>Agent</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>INCLUDE</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>ERROR</dispatcher>
</filter-mapping>
<display-name>AJACS</display-name>
<welcome-file-list>
<welcome-file>frameSet.jsp</welcome-file>
</welcome-file-list>
etc...
Now, when I remove the parts that http://docs.sun.com/app/docs/doc/819-3201/6n5eht3k4?a=view said to add, it deploys just like it used to deploy- just fine with no errors. However, I add that code and it breaks.
Note: The code was a straight copy/paste, so if there is any error in the code, it is because it's written incorrectly on the Sun doc website.
Any help would be MUCH appreciated. Thanks!

Well, if that was pasted on one line, it would be:
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
So it's supposed to be that way. I just tried it with the extra quotes, and no dice...

Set up document type "" in FI customizing

Hello experts,
While running MR11 (ACCM) GR/IR clearing in the backend we are getting the below error message - What needs to be done to correct this ?
<b>Document type not defined</b>
Message no. F5814
Diagnosis
Financial Accounting service: document type "" was not found in the document type table. There are two possible causes:
document type "" has not been set up in FI customizing
document type is supplied incorrectly from the calling application
System Response
System error.
Procedure
There are two possible measures:
set up document type "" in FI customizing
system error within the calling application - get in contact with the SAP Hotline Service.
Points will be awarded.
Thanks,
Manish Singhi

Hi,
Thnx. for ur inputs. The Document type and number ranges have all been defined. Also when we run the t-code MR11 and execute in Front end there is no issue. However, when we execute the Program SAPRCKM_MR11 and call the varaints we encounter that error. The variant has been created with the same info. what we are giving when executing in front end.
Can you give some idea ?
Thanks, Manish

Incorrect document types?

Similar Messages

Maybe you are looking for