Documents types definition rational

Dear All,
What i expect from you all is not the "How to do" but the "Why doing that this way"
We are designing our customer system and i have been asked the following questions:
Why should we use these document types?
What is the rational of creating new ones?
I tried to find out the solution for my question over the WEB but I have not been able to resolve my issue.
AB General document
DG Customer credit memo
DZ Customer payment
DR Customer invoice
KZ Vendor payment
KG Vendor credit memo
KN Vendor net invoice and credit memo
KR Vendor invoice
SA All G/L accounts
What is the rational to choose the number of documents types to be used?
Thank you in advance for your help
Kind regards
M.

Hi
Why should we use these document types ?
As already explained by MBN and Sowmya we use the different doc types
1.To differentiate the transactions posted in FI from different modules and in FI module itself.
2.To build the logic as per user requirement in respect of any particular document type
3.To identify the transactions posted from a particular module or from the same module(ex., for cash transactions we can have CJ)
4.Better not to have same document type for two types of postings ex., for postings from payroll doc type AB and for clearing document also doc type AB since differentiation between payroll documents and clearing documents becomes difficult.
Rational of creating a new one
1.To identify the nature of transactions pertaining to one particular area viz., excise etc.,we can have a new document type for example Doc Type EX
What is the rational to choose the number of documents types to be used?
Discuss with the client and decide.
In general for customers we use doc types beginning with letter D and for Vendors we use doc types beginning with letter K and for GL documents we use SA.
Regds

Similar Messages

Document type definitions for xml documents exported from SBO?

I am looking for DTD or XSD specifications for the documents that are exported from SBO via the DI API. It seems that this information is not available with the standard DI API documentation. Does anyone have a clue about where to look for these specifications ?
Best regards,
Henry Nordströ

The DI Company object has a GetBusinessObjectXmlSchema method which allows you to retreive the schema details.
Below is the sample from the DI help file.
Dim XMLStr As String
Dim domDoc As DOMDocument
Set domDoc = New DOMDocument
XMLStr = vCmp.GetBusinessObjectXmlSchema(oInvoices)
domDoc.loadXML (XMLStr)
domDoc.save ("C:\ XMLFiles \MyXML2.xml")
Regards,
John.

Document type should always post to specific account type

Hello experts,
I have 1 question, Depeneding on the Document type definition I can post to different account types (S, K, D , M ,A). Assume I created a doc type ZA and checked all the account types then it allows me post to all the account types.
Here I want the document type ZA to validate one of the line in the document should always be type K (vendor). In short in the combinaton of account types posted to under this document type should always have one specified account type.
All contributions welcome.
Thanks,
KKR

Hi Eli,
I am not sure how to do that in this case, I have worked on validations before and I always worked with 'Constants'. If I write
If Doc type is ZA
then account type should be 'K'
But the problem is it wont allow me to post as the other line will always be different, that means a combination K and other than K.
And we are not sure how many lines going to be there in a GL document.
Do I nee to look at user exits in validations? If yes, please let me know how can I do that.
Thanks,
KKR
Edited by: KK Rao on Sep 24, 2010 11:07 AM

Document type control

hi
in my company i have two prequisitons
one is used for imports and one for domestic .Ineed to make the field account asignment category an mandatory field for the domestic purchase requisition and for imports i do not how can i do this
and
can u also specify how this can be done to a purchase order also
With regards
chaitanya

You can make account assignment category mandatory in configuration. The path in SPRO is Materials Management --> Purchasing --> Purchase Requisition --> Define Screen Layout at Document Level.
Remember to make it mandatory in the field selection key at Document Type level. In case the field selection key is same at the document type level, change the field selection key in the document type definition (under Define Document Types). This way you can have different field selections at the document type level.
Same way in Purchase Order also. Menu path in SPRO is Materials Management --> Purchasing --> Purchase Order --> Define Screen Layout at Document Level
Hope this helps.
Lakshman

Change document type without changing file extension

I've recently started using Dreamweaver CS3 after nearly a decade on Homesite (which regrettably wouldn't work on my new Windows 7 machine). I like Dreamweaver's code view but find it lacking in some of the flexibility and intelligence that Homesite had.
Case in point: I work on a rather large site that uses Classic ASP. Most of the site uses .html file extensions, but we have these configured to be processed through the ASP engine. When editing the pages on this site, Dreamweaver sees the .html file extension and assumes they're regular HTML documents, and color codes them accordingly, but it can't figure out ASP comments and code blocks and mangles the color coding. If I try to change the Document Type (in the Application > Server Behaviors panel), Dreamweaver insists on changing the file extension too.
It appears I can modify Dreamweaver's MMDocumentTypes.xml file so that it thinks .html files are ASP. But I don't want to do this globally for ALL the sites I work on, only for this particular site. It would be really nice if I could change the document type definitions on a per-site basis, or to change the document type for a file without having to change the file extension. Surely I'm not the first person to use non-standard file extensions on webpages. Any ideas on how to fix this?

I think you have to disable it in your Operating system:
8dot3NameCreation
[http://support.microsoft.com/kb/121007]

Configuring Document Types by Ledger

There are 3 configuration steps for configuring document types:
1) Define Document Types in Entry View
2) Define Document Types in Entry View by Ledger
3) Define Dcoument Types in General Ledger View
What is the purpose of each step and how would I go about creating unique document types that would only be posted to in specific ledgers and have their own unique number ranges?
If I needed to create a document that posts across all ledgers can I just do step 1 and skip steps 2-3 for those document types?

Hai Hari
Define Document Types for General Ledger View
In this IMG activity, you define for Non-leading ledgers the document types for the documents in the General Ledger view. At the same time, you assign for each document type a number range to be applied in the assignment of document numbers:
u2022     You do not need to make these settings for your leading ledger because, in the case of this ledger, the document number in the entry view always corresponds to the document number in the general ledger view.
u2022     You only have to make these settings for any non-leading ledgers that have a fiscal year variant that differs in at least one company code from the fiscal year variant of the leading ledger in this company code. In this case, the document number in the entry view does not correspond to the document number in the general ledger view and you have to define a separate document type with document number assignment for the general ledger view.
For all non-leading ledgers that, in the company code to which the postings are made, have a fiscal year variant corresponding to the fiscal year variant of the leading ledger in this company code, the document number in the entry view always corresponds to the document number in the general ledger view.
Note
The need to define a document type for documents in the general ledger view depends only on whether the fiscal year variant of the non-leading ledger in the company code (to which the postings are made) differs from the fiscal year variant of the leading ledger in this company code. On the other hand, document type definition is independent of which the type of ledger group to which postings are made, that is, regardless of
o     Whether postings are made without a ledger group
o     Whether postings are made to a ledger group with a leading ledger as the representative ledger
o     Whether postings are made to a ledger group with a non-leading ledger as the representative ledger
Define Document Types for Entry View in a Ledger
Here, you make the settings specifying the document type for postings to non-leading ledgers.
Under Define Document Types for Entry View, you make the document type settings for postings in the entry view that effect all ledgers and for postings to the leading ledger.
Requirements
You work with a leading ledger and with non-leading ledgers.
Activities
To define document types for postings to non-leading ledgers, proceed as follows:
Set up a separate document type for these postings. Assign a unique number range to this document type for each ledger.
Example:
Document Type SX, Closing Postings, Ledger L2, Number Range FI
Document Type SX, Closing Postings, Ledger L3, Number Range FI
Note
By segregating the ledger-related postings (here, for the non-leading ledgers) in a separate number range, you ensure the contiguous assignment of document numbers at the ledger level for each number range.
Within a ledger group, the representative ledger determines the document types and number ranges applied. For this reason, you cannot perform this IMG activity for a ledger group.
If you use a ledger group to make account assignments for postings, it is only possible to verify that document numbers are assigned contiguously at the ledger level for the representative ledger.
Regards
Madhu I

Document Types Defintion

VOV8 is giving me the sales document type definitions but what transactions show me the delivery type and billing type definitions?

Please find the path for delivery document & billing document
1) Delivery Document
SAP Customizing Implementation Guide
      Logistics Execution
              Shipping
                   Deliveries
                         Define Delivery Types (OVLK)
2) Billing Document
SAP Customizing Implementation Guide
     Sales and Distribution
         Billing
           Billing Documents
              Define Billing Types (VOFA)
Regards,
Ganesh Sabnis

OGSD document types

Hi friends, we are implementing Is Oil with OGSD (Oil and Gas Secondary Distribution), that is an add on developed by Implico and marketed by SAP.
OGSD works with a specific sales order types, like OTA, OSO, OKM, among others. The problem we have is that when we review in IMG the standard sales document type definitions, all of them are empties. They have no values in any of the fields.
Regards and thanks in advance.
Gerardo.

Hi Gerardo,
there is a matching customer message for this tissue: 0001023466 2011. This message is in customer action. Since this seems to be an issue that is specific to your system please continue to process it in the customer message. Support may need to acess the system and this will only be possible from the support infrastructure.
Kind regards,
Thorsten Klingspor
OGSD Development

Restriction of GR & IR for PO with specific document type

Hi,
How we can restrict doing Goods Receipt & Invoice Receipt for a Purchase order, instead they do the payment directly for the Purchase order item in FI. We need to restrict GR & IR for PO with particular document type.
Regards,
Srinivas

Hi,
Yes i do feel the same. Normally if a PO is created means system expects a GR and and IR .If you do not expect the ir means it is a free entry.
But however you can control the GR / IR through account assignment .please check the account assignment definition at SPROMMPUR-Account assignment-AAcategory.
Once the PO is created with account assignment the procurement is for consumption (non stock)
if it is a stocked procurement system will check the GR/IR indicator in the PO.
When a PO is created in MM module and the cycle is not completed , it will always show as open PO.I think the context for FI direct posting will be differrant.
Regards,

Logic in Creation of Document Types

Good Morning Folks-
Is there documentation on when to create a new document type? I am on an AR project and I have a client that has (in my opinion) duplicate document types. For example, they have 2 document types for incoming payments and they are different because cash comes via lockbox(FLB2) and the other comes from a wire. I have 4 document types to identify invoices and they are different because they come from the legacy system or created in SAP, etc. They have a document type for credit memos and typically I have seen it is the same as an invoice but differentiated by posting key. For credit memo, would be posting key 11.
I am trying to find some documentation that gives advice and warnings about this. I have worked with 9 US A/R projects and at most had to be concerned with was only 4 document types. I know what the definition of a document type is but they think it is to have them by source. I see warning flags here. I don't even know how to create clearing rules because it is so complex. In addition, they are unable to balance from their legacy system to SAP.
Points promised

Hi,
This looks to be a Business Process question or as per the requirements of the client. You can find documentation on document types and how to configure, but not on how many document types to be set up. This purely depends upon Business practice adopted by the client.
If a client has moved from a legacy system to SAP, the document types used in legacy system also influences this decision. There will be some reluctance to reduce or increase number of document types vis a vis legacy system.
There should be too many or too less number of document types. Basically, document types will be helpful for reporting and analytical decision making.
Thanks
Murali.

Document types show up twice when creating a new blank HTML document.

I followed the below instructions for getting HTML 5 as a document type option on CS4. Although I do have HTML 5 as an option now, my other stock CS4 document type options now show up twice in the menu. Any idea how to fix this?
To add the HTML document type, however, you need to modify the file named MMDocumentTypeDeclarations.xml. Here’s how to do that:
1. Find the configuration folder then navigate to the documenttypes folder. The Configuration folder can be found under the folder where you installed Dreamweaver.
2. Find and make a backup copy of MMDocumentTypeDeclarations.xml (MMDocumentTypeDeclarations.xml.bak)
3. Open MMDocumentTypeDeclarations.xml in your favorite text editor. If anything goes wrong, you can always get back to the default state by replacing your changes with the backup copy.
4. Go to the end of the document and find the </documenttypedeclarations> tag and add the following lines just before the </documenttypedeclarations> tag:
<documenttypedeclaration id="mm_html_5">
<title>
HTML5
</title>
<doctypedecl>
<![CDATA[<!DOCTYPE HTML>]]>
</doctypedecl>
<rootelement>
<![CDATA[<html></html>]]>
</rootelement>
<dtdcontext>html</dtdcontext>
<dtdcontext>html5</dtdcontext>
<dtdcontext>frameset_frame</dtdcontext>
<dtdcontext>xslt</dtdcontext>
</documenttypedeclaration>
5. Save the document
6. Restart Dreamweaver
You should now have an HTML5 document type option when you create a new document.
There was an issue with Dreamweaver CS4 that needed to be fixed in code to fully support HTML5 documents which is why upgrading to CS5 was recommended. In CS4, Dreamweaver’s definition of a well formed HTML document has a meta content type which isn’t required for HTML5 documents so, no matter what we do to CS4, any HTML document created by CS4 will have the following:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Replace that line with this:
<meta charset=utf-8">
You’ll need to do this every time you create a new HTML5 document.
Once you finish go to Preferences New Document and select HTML5 as default Doc Type...
Thanks to:
What I did was create a snippit of the meta and added it to my snippit's meta folder
Jeff Booher
Dreamweaver Engineering
Thanks for your feedback.

Hi,
I have done a test and I can reproduced your issue.
I referred to the blog about Automatically create Word documents which include list fields:
http://blogs.technet.com/b/brenclarke/archive/2009/04/15/automatically-create-word-documents-which-include-list-fields.aspx
When I create a multiple line of text column in a list, I just choose Plain text, Then I solved the issue:
Besides, here is a similar post, you can take a look at:
https://social.technet.microsoft.com/Forums/sharepoint/en-US/a7ab3a61-6643-4a47-a464-fe46b5db1558/rich-text-field-showing-html-code
Best Regards,
Lisa Chen
Lisa Chen
TechNet Community Support

Oracle Fusion Middleware 11G B2B Document Type not getting Identified

Hello,
I have installed Oracle Fusion Middleware 11g on my local machine and created a custom document type with proper .xsd definition and XPath Expression Identifier in Oracle B2B interface and configured its trading partners ( Host & Remote ) along with an agreement between the partners.
I have also configured the host listening channel of Generic-File type which picks xml files from my c:\orclsrvs_in folder.
My problem is that the moment I drop any sample file in the expected directory, it gets picked up from B2B , but there isn't any record of the same under Reports and Metrics links.
The Business message, Application message and Conversation message tabs are also not showing any information about the record picked, but in wire message tab, the record is shown in PROCESSING state.
I am not able to conclude whats wrong behind this.. where can i track the logs for the same ??
kindly help to resolve this issue.
Thanks & Regards
Hiteshkumar Chaudhary

Hi Hitesh,
i came to know that B2B extracts the TP name from the filename itselfYes, in case of Generic File, Generic SFTP and Generic FTP, file name provides the necessary values to Oracle B2B to identify the Trading Partner. You can define your own file name format in the Delivery Channel under Transport Protocol Parameters in field "Filename format" (It's an optional field but it is always good to define your own format, otherwise B2B will take it's default format - TradingPartner_DocumentType_Revision_msgType_msgId_replytoMsgID_extension.xml ). Following Filename formats can be used -
%FROM_PARTY%
%TO_PARTY%
%DOCTYPE_NAME%
%DOCTYPE_REVISION%
%MSG_ID%
%TIMESTAMP%
These file name formats can be used in any combination; for example,
%TO_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%.dat
Note - Any file extension is allowed.
what are the system parameters to be set in weblogic console and how?? This activity is part of the pre and post installation steps. If you have done those without getting any errors then nothing else is required.
how shall I reinstall XEngine properly ??XEngine is part of B2B installation. If B2B gets installed without flashing any errors then we assume that other components of this part has installed properly.
Regards,
Anuj
Edited by: Anuj Dwivedi, Infosys on Aug 28, 2009 5:51 PM

B2B Custom Document Type not getting identified

Hello,
I have installed Oracle Fusion Middleware 11g on my local machine and created a custom document type with proper .xsd definition and XPath Expression Identifier in Oracle B2B interface and configured its trading partners ( Host & Remote ) along with an agreement between the partners.
I have also configured the host listening channel of Generic-File type which picks xml files from my c:\orclsrvs_in folder.
My problem is that the moment I drop any sample file in the expected directory, it gets picked up from B2B , but there isn't any record of the same under Reports and Metrics links.
The Business message, Application message and Conversation message tabs are also not showing any information about the record picked, but in wire message tab, the record is shown in PROCESSING state.
I am not able to conclude whats wrong behind this.. where can i track the logs for the same ??
kindly help to resolve this issue.
Thanks & Regards
Hiteshkumar Chaudhary

Hi Hitesh,
i came to know that B2B extracts the TP name from the filename itselfYes, in case of Generic File, Generic SFTP and Generic FTP, file name provides the necessary values to Oracle B2B to identify the Trading Partner. You can define your own file name format in the Delivery Channel under Transport Protocol Parameters in field "Filename format" (It's an optional field but it is always good to define your own format, otherwise B2B will take it's default format - TradingPartner_DocumentType_Revision_msgType_msgId_replytoMsgID_extension.xml ). Following Filename formats can be used -
%FROM_PARTY%
%TO_PARTY%
%DOCTYPE_NAME%
%DOCTYPE_REVISION%
%MSG_ID%
%TIMESTAMP%
These file name formats can be used in any combination; for example,
%TO_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%.dat
Note - Any file extension is allowed.
what are the system parameters to be set in weblogic console and how?? This activity is part of the pre and post installation steps. If you have done those without getting any errors then nothing else is required.
how shall I reinstall XEngine properly ??XEngine is part of B2B installation. If B2B gets installed without flashing any errors then we assume that other components of this part has installed properly.
Regards,
Anuj
Edited by: Anuj Dwivedi, Infosys on Aug 28, 2009 5:51 PM

Document type to default content repository

Is it possible to configure the DMS system so that when you create a document using CV01N and check in the original (using a KPro document type) it will enter it into a content repository by default, without using the pop-up box.
For example a document of type DMO (if DMO it has KPRO checked in it's setup) - always puts the original document in DMS_C1_ST?
Thanks for any advice.

Dear Arthur,
if I understood your latest information correctly your request is that
the files are stored automatically to storage category if
you add a file of a specific workstation application to a document info record and save it.
This first setting enables the automatic start of the checkin
process. But to have a specific storage category choosen for an
original workstation application, you have to do another setting and
create a profile in your system in the customizing under
- Cross Application Components
     - Document Management System
         - General Data
             - Define profile
For this profile pleasee add your workstation applications under
"Determine definitions for applications". Here you can maintain the
default storage category for this application in field 'Storage cat.'.
Since this profile is created assign it to all your users directly.
Then if an user adds a new original file and chooses a workstation
application the system should take the storage category automatically
from the profile.
To achieve an automatic checkin behavior the additional required setting here are the flags
"Checkin" and "Checkin required" which must be set for the used document status in transaction DC10.
Another proposal would be to use the BADI DOCUMENT_STORAGE01 which
shoudl offer also methods to control which storage category should
be taken for which workstation application.
I hope that this information could be useful for you. To set up this
scenario in detail I would recommend you to contact your local
consulting organisation too which will help you in realising a solution
that meets all your requirements.
Best regards,
Christoph

Deployment Tool Error - unknown document type - Add to Application EJB jar

I am creating a new application in the J2EE deployment tool and adding an EJB JAR to it. The jar contains the ejb-jar.xml file. This file has the standard doctype:
<!DOCTYPE ejb-jar PUBLIC
'-//Sun Microsystems, INC.//DTD Enterprise JavaBeans 1.1//EN'
'file:/C:/j2sdkee1.3/lib/dtds/ejb-jar_2_0.dtd'>
I get the Unknown Document Type error when I try to add this jar to the application:
Error: Adding EJB JAR - java.lang.RuntimeException: Invalid XML : Unknown document type : org.apache.crimson.tree.Doctype@e8647
The xml file validates fine in NetBeans 3.4. I use NetBeans to generate the jar file.
Any ideas as to what is happening would be appreciated.

Try replacing the DTD definition as specified below.
http://java.sun.com/dtd/ejb-jar_2_0.dtd
regards,
Siddique

Documents types definition rational

Similar Messages

Maybe you are looking for