Document Mangement system(Document type settings )

Helllo friends,
Hello I want to create a document type with all possible settings in one system
and i want to trasfer these document type with seeting to other system...
How can I transfer document type with other possible seetings from one system to other system?
Please Help me
Thanks in Advacne
Preethi

Hi
SAP DMS - Document Management System
SAP DMS are for storing documents such as CAD drawings, Materials pictures etc.
With the document management system, users will be able to view the documents with ease within their SAP systems.
Installing the SAP DMS requires a little bit of planning on how you want to do it.
You have to give a little thoughts to stuff such as :-
1.  The total numbers of documents that will be store monthly.
2.  The average file size of each documents.
3.  The capacity of your present R/3 system.
4.  Your present network bandwidth.
5.   Document Archiving Strategy.
6.   Backup and Recovery Plan.
Additional purchasing of hardware are required, especially if you have large amount of documents to stored.
With this in mind, you can then decide on how you want to do it.
You can do this in a few ways :-
1.  Import the documents into the R/3 system.
2.  Use an external document server.
3.  Have a dedicated PCs where all the documents are stored.
Most companies that intend to used DMS will opt for Option 2 as they does not want to overstretch the R/3 database.
Options 1 requires you to setup the conversion interface. 
The conversion interface allows R/3 to automatically covert your files and import it into the R/3 database.
Here is a simple example of storing documents into your PCs, just to have a feel how the SAP DMS works:-
For those using Citrix, you have to set this at the Citrix Server where the SAPGUI is located.
Configure SM30 - V_TDWE_C1
Put this command in your autoexec.bat
SET HOSTNAME=PC1234
Restart your pc.
You can create/manage your documents in transaction code CV01N / CV02N
Assigning Documents to a Material Master Record
Access a material master record in Create or Change mode, and select Basic Data. 
To create links to documents, choose Additional data -> Document data.
The Link to Documents dialog box appears.
Assign one or more documents to the material. 
If you do not know what the document number is, you can search for it using the search help or by choosing Find document.
When assigning a document to a material, you have the following options:
1. Viewing the document by choosing it in the Link to Documents dialog box.
2. Viewing any originals of the document by positioning the cursor on the document and 
   choosing Display originals in the Link to Documents dialog box.
To return to the Basic Data screen, choose Continue.
Save your data. 
Reward points if useful
Regards
Anji

Similar Messages

  • Document  type settings

    Hi,
    In the Document type settings for PO, there is one check box is Vendor.
    What is the purpose of vendor check box in the document type settings?
    Kindly explain
    Thanks
    Ravi

    You set the indicator. If a stock transport order or scheduling agreement is then created and a vendor is assigned to the supplying plant, the system
    adopts the data from the vendor master record (e.g. the currency, price determination indicator) and the info record (e.g. planned delivery time, order unit), and
    updates the statistics of the Logistics Information System with the vendor data.
    Normally this indicater used for Stock transport order document types e.g :UB document type.

  • Credit Group-Document type settings.

    Hi All,
    i have created one order document  type ZFAC  for sale from mfg. plant.
    company has 5 plants(each plant manufacures different products)
    i need to have product division wise credit check.
    ZFAC- credit Group- 01 for order -> Plant 1(Product A)
    ZFAC- credit Group- 02 for Delivery -> Plant 2(Product B)
    ZFAC- credit Group- 03 for PGI -> Plant 3(Product C)
    how to achieve this? i cannot create 3 different order document types for 3 different plants.
    Reg,
    Amol

    Dear Amol,
    As per your requirement, please test after doing the following settings.
    You have to create 3 CCArea based on your business requirement.
    lets say it is 1000, 2000 and 3000
    lets say we have 3 risk category 001/002/003
    We have 3 credit groups 01(sales order  /02 delivery /03 PGI)
    You can find the configuration for credit management in the WIKI or in FORUM itself.
    Hence i will be mentioning only the deviations which you need to make from those standard configuration.
    ccarea to company code assignment need to be done based on the configuration steps.
    In ovfl, you need to specify the credit control area for the sales areas.
    you have to assign different credit control areas created for the 3 sales areas (division)
    Now in ova8, there is a combination of credit control area / risk category / credit group.
    For the division which needs check in sales order level, in OVA8 for the combination 1000/003/01
    check the required checks / blocks and reactions (you can decide whether the check need to be on credit amount or oldest open item or any other factor -- refer the configuration for credit management)
    for the remaining combination ie, 1000/003/02 and 1000/003/03 do not maintain any checks.
    For the division which needs check in delivery level, in OVA8 for the combination 2000/003/02
    check the required checks / blocks and reactions (you can decide whether the check need to be on credit amount or oldest open item or any other factor -- refer the configuration for credit management)
    for the remaining combination ie, 2000/003/01 and 2000/003/03 do not maintain any checks.
    For the division which needs check in PGI  level, in OVA8 for the combination 3000/003/03
    check the required checks / blocks and reactions (you can decide whether the check need to be on credit amount or oldest open item or any other factor -- refer the configuration for credit management)
    for the remaining combination ie, 3000/003/01 and 2000/003/02 do not maintain any checks.
    check and revert back after testing.
    One limitation of this scheme (if it works as per requirement ) is that we need to maintain seperate credit limit for the customer in all the 3 divisions.
    Thanks & Regards,
    Hegal K Charles

  • Delivery document type settings

    Hi all,
    In standard SAP For LF delivery type, Default order type DL (Delivery with out sales order reference) is assigned.What is the use of this.
    For delivery with out reference to sales order system will not allow us to use delivery type LF.
    we only use Delivery type LO.Then why DL is assigned to this.
    One more question for LO delivery type DL is assigned.Can I see DL anywhere in the delivery document?
    Regards
    Mano

    Hello Mano,
    It is not the case that you cannot use LO for Delivery with Order reference or LF without Order Reference.
    It is because it has been set in the Delivery document parameter setting that it requires an Order Reference or not .
    You can change it if you want by making a copy of the Document type so that Standard is maintained.
    For your query,SAP has probably maintained most of the  Delivery documents with Default Order as DL.
    Because if you create a delivery with or without reference the items declared in the Delivery document should have some reference document before it.
    This is the F1 help which clearly states the use of declaring the Order type
    Default order type for deliveries without reference to order
    The default for a "pseudo" order type for deliveries or delivery items that do not refer to an existing order.
    Use
    When you create delivery documents that do not refer to existing orders, you must provide some of the control criteria that are normally copied from a sales document header into the delivery document.
    Example
    A delivery document, for example, needs information about which item types need to be defined.
    Procedure
    You can define a pseudo order type in Table TVAK. When you create a delivery that does not refer to an existing order, the system automatically uses the pseudo order type.
    Hope it is clear to you now.
    Regards,
    Karthik

  • Document type KR is not picking to Clear GL account with T-code F-03

    Hi all,
    My client wants to clear GL account Cash-in-Transit which is open item managed. He has posted two items. One is with KR document type like Intercompnay adjustment account debit (40) and Cash-in-Transit account credit (50). Second item is with SA document type like Cash-in-Transit accont debit (40) and Intercompany adjustment account credit (50). He did not give vendor number and appropriate posting key (31) while postings. With document type KR, he posted with posting keys 40 and 50. Now while clearing the GL account through T-code F-03, system is picking only SA document type. The system is not picking document type KR. He wants to clear the items with each other. I have checked the document type settings. Check boxes Intercompany postings and trading partner are active in both above document types.
    How can the GL account be cleared ? Are any configuration settings missing ? Kindly advice as soon as possible.
    Thanks in advance.
    Regards,
    K.S.K

    Hi,
    First of all..why would system need a Exchange gain/Loss Account..If your local currency is INR and you posted a debit and a credit document both in INR..then there is no question of a foreign exchange gain/loss account..
    BUT, if you have posted the document in any currency other than INR, ie: your local currency...then the system would need a exchnage gain/loss account when you try to clear the debits and credits.. i am giving an example below to explain better..
    You posted a debit of 100 USD @ 40 = Rs. 4000.00
    You posted a Credit of 100 USD @ 42 = Rs. 4200.00
    Now, if you clear this debit and credit then there is no difference in 100 USD, as the debit and credit is netting off.. but if you see INR there is a difference of Rs. 200.00 which system posts to Exchange gain/loss account..which we maintain in OB09.
    Hope it is clear to you now..
    Regards,
    SAPFICO.

  • Default Exchange rate type at document type level for parallel currencies

    Hi,
    I have a scenario wherein 2 parallel currencies have been maintained (Grp & index based) against a Co Code and have maintained a default exchange type (Z2) in the Document type settings (OBA7).
    But when I want to post a foreign currency document, system picks Z2 rates for Co Code currency conversion and not for Grp & index based. In fact it picks M rate for these addtional currencies.
    I know that for parallel currencies, the system will always use the exchange rate type defined in transaction OB22 ( "M" rate) which is at Co Code level but I want default exchange rate type Z2 to be picked at Document Type level for all the parallel currencies.
    Please suggest how to archive this.
    Thanks,
    Sam

    Dear Sam,
    The exchange rate type defined in the FI document type (-> field
    exchange rate type in transaction OBA7) is only used for the currency
    translation from transaction/document currency into first local
    currency, not for the currency translation into second local (group)
    currency or for the currency translation into third local currency.
    The exchange rate types for the currency translation into second
    local (group) currency and third local currency are defined in
    transaction OB22.
    Unfortunately there is no option to change the exchange rate of 2nd or
    3rd local currency in our posting transactions. The design doesn't
    regard that requirement. But you have the chance to adjust the parallel
    currencies in OB22 or to change the amounts manually.
    I hope this helps.
    Mauri

  • 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 Type Not Found in Shift Note Settings

    Dear gurus,
    I'm implementing Ecc-dimp function, shift note report.
    I check in PRD SPRO configuration:
    Logistics General -> Make Settings for Shift Note, I have made one Shift Note Type "MS".
    The settings from DEV Server (transport) is "DMO", but when I browse (F4), there's error "Document type DMO cannot be used".
    I've CORRECTLY configured the document type in DMS in production (used by MM consultant for MARA attachment).
    Then I check the settings in DEV server, and browse (F4) on the same configuration.
    There's only one document type which can be used, that is "DMO"
    Here's the error in PRD system:
    [http://postimage.org/image/bjyus8a3x/]
    Is it some SAP bug?
    Thanks for help.
    Best Regards,

    We're running ECC 6.0 EhP4.
    Technical component is 7.01 level 0009
    Business software component is 604 level 0009
    Latest kernel patch
    Regards,

  • What are the sources system will pick the document type while creating invo

    hi
    I would like to know how system will pickup the doucment type while creating invoice in vf01.
    i have taken off the fields  f1, f2, from the document type. in billing sub tab.  so  The moment when am creating billing system automatically displaying F2 invoice doucment creation.  What are the sources for this.
    thanks & Regards
    Rack129

    Hi,
    Hope you have maintained u2018Delivery relevant billing type F2u2019 and u2018Order relevant billing type F1u2019 in the billing tab of the Sales document type in VOV8.
    If you create delivery related billing, the system will pick F2. This is controlled in Item category (VOV7). Billing relevance in Business data of Item category decides whether this is delivery related or order related. u2018Au2019 for delivery related billing; u2018Bu2019 for order related billing and so on.
    Item category is determined by this combination: Sales document type + Item cat group + usage + higher level item cat.
    Regards,
    K Bharathi

  • Not able to upload file in DMS(Document Mang. system) using Web dynpro ABAP

    Hi All,
    I am facing a problem while uploading the file into the DMS ( Document Management System ) from Webdnrpo .
    I am using the BAPI - BAPI_DOCUMENT_CREATE2 to create the document .
    CASE - 1
    when i am providing the storage category mention below and no data carrier1
    ls_documentfiles-storagecategory = 'ZHMEL_CS'.  it is not able to upload the document in the DMS system and when i check
    in the debugg mode it giving error as  ""Error while checking in and storing: C:\TEST.TXT "" .
    CASE - 2
    When i am not using the storage category and providing the the data carrier as default
    ls_documentdata-DATACARRIER1 = 'DEFAULT'. It is able to create the document in the DMS but i am not able to read that document .
    I checked with DMS Consultant that DMS is configured for  ZOL ( documenttype) with a storage category  as 'ZHMEL_CS'.
    The code which i have used is below :
    ls_documentdata-documenttype = 'ZOL'.
    ls_documentdata-documentversion = '00'.
    ls_documentdata-documentpart = '000'.
    ls_documentdata-description = 'Test Document'.
    ls_documentdata-laboratory = '001'.
    ls_documentdata-WSAPPLICATION1 = 'TXT'.
    ls_documentdata-DOCFILE1 = 'C:\TEST.TXT'.
    ls_documentdata-SAVEDOCFILE1 = 'C:\TEST.TXT'.
    *ls_documentdata-FILESIZE1 = 000000000000.
    *ls_documentdata-FILESIZE2 = 000000000000.
    ls_documentdata-WSAPPLICATION1 = 'TXT'.
    ls_documentfiles-DOCUMENTTYPE = 'ZOL'.
    ls_documentfiles-DOCUMENTPART = '000'.
    ls_documentfiles-DOCUMENTVERSION = '00'.
    ls_documentfiles-storagecategory = 'ZHMEL_CS'.
    ls_documentfiles-WSAPPLICATION = 'TXT'.
    ls_documentfiles-DOCPATH = 'C:\'.""lv_filename.
    ls_documentfiles-DOCFILE = 'TEST.TXT'."lv_filename.
    ls_documentfiles-description = 'Test Document'.
    ls_documentfiles-language = 'EN'.
    ls_documentfiles-CHECKEDIN = 'X'.
    APPEND ls_documentfiles to lt_documentfiles .
    *&----Fill Descriptions
    w_descr-language = 'EN'.
    w_descr-language_iso = 'EN'.
    w_descr-description = 'Test'.
    append w_descr to lt_descr.
    clear w_descr.
    **w_hostname = 'HMEL-DV1R3_DR3_00'.
    CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
    EXPORTING
    documentdata = ls_documentdata
    *hostname = 'content-srv'
    *pf_http_dest = 'SAPHTTPA'
    *pf_ftp_dest  = 'SAPFTPA'
    IMPORTING
    DOCUMENTNUMBER = lv_DOCUMENTNUMBER
    return = gv_return
    TABLES
    documentdescriptions       = lt_descr
    documentfiles              = lt_documentfiles.
    Please let me know your valuable inputs on the same ..
    Edited by: Omm Awasthi on Dec 30, 2010 12:22 AM
    Edited by: Omm Awasthi on Dec 30, 2010 12:25 AM

    Hi omm , from functional side your require a document type and content repository
    I have used below code in a function module to create document , we have create object link as PO to the doc.
    FUNCTION ZFM_SR_CREATE_FROM_EXTERNAL .
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(IV_DOCUMENTNUMBER) TYPE  DOKNR OPTIONAL
    *"     VALUE(IV_DOCUMENTTYPE) TYPE  DOKAR OPTIONAL
    *"     VALUE(IV_DOCUMENTVERSION) TYPE  DOKVR OPTIONAL
    *"     VALUE(IV_DOCUMENTPART) TYPE  DOKTL_D OPTIONAL
    *"     VALUE(IV_STORAGE_CAT) TYPE  CV_STORAGE_CAT OPTIONAL
    *"     VALUE(IV_DOKST) TYPE  DOKST OPTIONAL
    *"     VALUE(IT_DM_FILES) TYPE  ZDM_TT_FILES OPTIONAL
    *"     VALUE(IV_EBELN) TYPE  EBELN
    *"  EXPORTING
    *"     VALUE(EV_DOCUMENTNUMBER) TYPE  DOKNR
    *"     VALUE(ES_RETURN) TYPE  BAPIRET2
    V00.00  DD.MM.YYYY                                                   *
    *********************New Method of Uploading File*********************************
      CONSTANTS path_name    TYPE dms_path
               VALUE '/tmp/'.
      CONSTANTS log TYPE dms_path VALUE '/tmp/logFO.txt'.
      DATA: ls_draw TYPE bapi_doc_draw2,
            lt_documentfiles TYPE TABLE OF bapi_doc_files2,
            ls_documentfiles TYPE bapi_doc_files2,
            ls_dm_files TYPE zdm_files,
            lv_filename TYPE string,
            lv_ext TYPE string,
            lv_file_type TYPE draw-dappl,
            lv_file_name TYPE dms_path,
            lv_msg(80) TYPE c,
            lt_objectlinks TYPE TABLE OF bapi_doc_drad,
            ls_objectlinks TYPE bapi_doc_drad,
            lv_ebelp   TYPE ebelp
    Prepare Data
      MOVE iv_documentnumber TO ls_draw-documentnumber.
      MOVE iv_documenttype TO ls_draw-documenttype.
      MOVE iv_documentversion TO ls_draw-documentversion.
      MOVE iv_documentpart TO ls_draw-documentpart.
      ls_draw-statusextern = iv_dokst.
      ls_draw-statusintern = iv_dokst.
      ls_draw-username = sy-uname.
      LOOP AT it_dm_files INTO ls_dm_files.
        SPLIT ls_dm_files-filepath AT '.' INTO lv_filename lv_ext.
        CALL FUNCTION 'CV120_DOC_GET_APPL'
          EXPORTING
            pf_file   = ls_dm_files-filepath
          IMPORTING
            pfx_dappl = lv_file_type.
        TRANSLATE lv_file_type TO UPPER CASE.
        OPEN DATASET log FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
        TRANSFER lv_ext TO log.
        ls_documentfiles-wsapplication = lv_file_type.
        TRANSLATE ls_documentfiles-wsapplication TO UPPER CASE.
        CONCATENATE path_name
                           lv_filename
                            lv_ext
                            INTO lv_file_name.
        CONDENSE lv_file_name  NO-GAPS.
        TRANSFER lv_file_name TO log.
        OPEN DATASET lv_file_name FOR OUTPUT IN BINARY MODE MESSAGE lv_msg.
    *Transfer Attachment Content to Application Server
        TRANSFER ls_dm_files-content TO lv_file_name.
        CLOSE DATASET lv_file_name.
        TRANSFER 'move data to lt_files' TO log.
        ls_documentfiles-storagecategory = iv_storage_cat.
        ls_documentfiles-docfile = lv_file_name.
        ls_documentfiles-DOCUMENTVERSION = IV_DOCUMENTVERSION.
        APPEND ls_documentfiles TO lt_documentfiles.
        CLEAR lv_file_name.
        CLOSE DATASET log.
      ENDLOOP.
      IF iv_ebeln IS NOT INITIAL.
        ls_objectlinks-objecttype = 'EKPO'.
        SELECT SINGLE ebelp INTO lv_ebelp FROM ekpo WHERE
                                          ebeln = iv_ebeln
                                          AND loekz eq space.
        CONCATENATE iv_ebeln lv_ebelp INTO ls_objectlinks-objectkey.
        APPEND ls_objectlinks TO lt_objectlinks.
      ENDIF.
    CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
       EXPORTING
         documentdata   = ls_draw
         pf_ftp_dest    = 'SAPFTPA'
         pf_http_dest   = 'SAPHTTPA'
       IMPORTING
         documentnumber = ev_documentnumber
         return         = es_return
       TABLES
         objectlinks          = lt_objectlinks
         documentfiles  = lt_documentfiles.
    DATA:   ls_doc_data  type bapi_doc_draw2,
       ls_doc_datax type bapi_doc_drawx2,
       ls_return type bapiret2.
    Set value for document data
      ls_doc_data-statusextern  = 'IW'.
      ls_doc_data-statusintern  = 'IW'.
    Set value for document data check
    ls_doc_datax-statusextern = 'X'.
    ls_doc_datax-statusintern = 'X'.
    CALL FUNCTION 'BAPI_DOCUMENT_CHANGE2'
      EXPORTING
        DOCUMENTTYPE               = 'ROS'
        DOCUMENTNUMBER             = IV_DOCUMENTNUMBER
        DOCUMENTPART               = IV_DOCUMENTPART
        DOCUMENTVERSION            = IV_DOCUMENTVERSION
        DOCUMENTDATA               = ls_doc_data
        DOCUMENTDATAX              = ls_doc_datax
      HOSTNAME                   =
      DOCBOMCHANGENUMBER         =
      DOCBOMVALIDFROM            =
      DOCBOMREVISIONLEVEL        =
      SENDCOMPLETEBOM            = ' '
          pf_ftp_dest    = 'SAPFTPA'
          pf_http_dest   = 'SAPHTTPA'
      CAD_MODE                   = ' '
      ACCEPT_EMPTY_BOM           = ' '
    IMPORTING
       RETURN                     =  ls_return
    TABLES
      CHARACTERISTICVALUES       =
      CLASSALLOCATIONS           =
      DOCUMENTDESCRIPTIONS       =
      OBJECTLINKS                =
      DOCUMENTSTRUCTURE          =
       DOCUMENTFILES              = lt_documentfiles.
      LONGTEXTS                  =
      COMPONENTS                 =
      move es_return to ES_RETURN.
      IF es_return-type CA 'EA' ."NE 'E' AND es_return-type NE 'A'.
        "do nothing
      ELSE.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            wait = 'X'.
      ENDIF.
      LOOP AT lt_documentfiles INTO ls_documentfiles.
        DELETE DATASET ls_documentfiles-docfile.
      ENDLOOP.
    ENDFUNCTION.

  • Standard settings on SA document type

    Hi All,
    My company has been delivered an "all in one" solution and i believe it has been significantly modified from standard SAP.
    Can you please identify if the standard settings on the SA document type allow intercompany postings?
    Many thanks
    Phil.

    hi ,
    in the document type sa
    there is a control data
    in that select Inter-company posting
    try with this
    regards

  • FB70-Document type display settings globally

    Hi,
    I want to know whether it is possible to change the document type field settings in 'FB70-Customer Post Customer Invoice' entry screen globally eventhough each user can make the setting using Editing Options, but my client wants it to be done globally.
    Thanks
    Suresh

    There are actually 2 ways to do it. The first is a cross client changes using OBU1. The second is more relevant which is SPRO> Fin Acct> Gen Ledger Acct > GL Acct Posting > GL Acct Posting -Enjoy > Define Doc Type for Enjoy Trx  of which you specify by companies, Acct Type and Tcode with the default Doc type.

  • PUBLIC vs. SYSTEM document type id's

    I am developing an XML language used to describe plot layouts for a data analysis system. Currently the dtd is stored on a web server. This will not work out, since the program that interprets the XML and produces the plot will not necessarily be able to access the web. I haven't yet looked into whether or not the SYSTEM type identifier can be the URI for a resource in a jar file. I was wondering if there was a way to have the xml parser recognize a PUBLIC document type identifier that I have declared. I am using DOM with the Crimson release packaged with JDK1.4.1, but will soon be switching to Apache's Xerces.
    Any help would be appreciated
    Edward

    Specify SYSTEM identifier with a jar url.
    jar:<url>!/{entry}
    For example:
    <!DOCTYPE root_element SYSTEM "jar:file://c:/dtds.jar!/config.dtd">

  • How does system automatically picks up document type when you enter INV?

    1.How does system automatically picks up document type when you enter Invoice?
    2.What is Algorithms? Where is it used?
    3.What is the use of Customer Ledger Inquiry?

    The document type is hard coded by the system. Look at UDC table 00/DT for the document types in your system. Notice that some of those are marked as hard coded/reserved by JDE. You may wish to dowload the Accounts Receivable manual and read that to learn more about the document types.
    Not sure what you mean by algorithm, unless you are looking for how the system determines what document type to assign on invoice entry.
    These comments apply to accounts receivable and to JDE World, since you posted in the JDE World forum and are talking about the customer ledger inquiry. If you are in Enterprise One and asking about Accounts Payable, then this reply can be ignored (though Enterprise One works pretty similar to World in this respect).
    What is the use of the Customer Ledger Inquiry. To view accounts receivable detail history for a given customer, viewing on line. Whomever works in the accounts receivable department will likely use the Customer Ledger Inquiry quite a bit.
    Hope this helps a bit.
    John Dickey

  • Document Management system - Document Type configuration.

    Hi Friends,
    We are have having document type same as Document class (Dock Type PDF = Dock Class PDF). Now we have to identify documents that are stored based on geographical location. Is there any possibilities to differentiate the based on different region by using Doument parts or some other ways?
    Thanks in Advance.
    -Thanks,
    Ajay

    Hi Ajay,
    This can be possible by two ways;
    1 you assign lab office for document type.
    2 assign geographic characteristics to doument by way of classification in DIR.
    for Lab office;
    Goto SPRO-Cross appln comp-Doc management-Gen Data-define Lab / office. Here u have to define diff offices as per your geographic locations. Then in Doc type in field selection you have to make lab/office as required entry. By doing this u can search documents based on Doc type & Lab/office location.
    for Classifcation;
    You have to create geographic characteristic in CT04, and needs to assign tht to class in CL02 with class type 017. In DIR by classification tab you have to assign Geo char with Document. By this way also you can search document based on classification.
    for less complex classification option 1st is advisable.
    Please award points if above information is useful/solves your problem.
    Pramod

Maybe you are looking for