No document type defined  in mapping rule

Hi,
Information on document type is need to be loaded from SAP R/3 to BCS for reporting purpose. Customised doc type with assigned role - subassignment already defined. Problem is i still don't see the document type (fiels) for selection in mapping rule (under load from data stream).
Any input would be appreciated. Thanks.
Regards, Renee

Due to reporting requirement, there are certain GLs need to be filter futher by doc type. As long as the document type is successfully extracted from SAP R/3 to BW BCS and filtering is defined in BE Analyzer, i don't need to display it in the report.
Anyway, customised document type already created and doc type can be extracted from SAP R/3. tq

Similar Messages

  • Creation of new document types for document splitting rules

    Hi experts,
    We have copied from existing SA  document type to new document type.
    In standard SAP  SA  document type - define document splitting rule, we have select  "NO INHERITANCE OF ACCOUNT ASSINGNMENT", when posting the  GL document SA  document type without mapping partner profit center,system is control the derive the partner profit center.
      Our requirement is  copied from existing  SA  document type to create a new document type - we have created the new dusiness transaction variant and we have map the "classify document type to document splitting rule " and we have selet the "No inheritance of account assignment" while posting in FB01 GL document with out mapping partner profit center system is not control the " derive partner profit center".
    Could you please assist us as soon as possible
    Thanks ,
    Sreenivas
    Edited by: sapfico.srini12 on Jan 16, 2012 4:37 PM

    Hi,
    In order to create a document type for a purchase requisition  use the path
    spro-materials management - purchasing--purchase requisitions --define  document type
    in that screen you select the document type you want to copy to create your document type and perform the action.
    if you want to change the screen/field selection for your document type select the field selection key (if you select the document type as NBB the field selection key will be NBB.,and go to the screen and change the field status.
    Hope this will be suffient for your requirement.
    Regards,
    Raghu.

  • Multiple document types per Network in Purchase Requisition stage

    Hi,
    PRs get created automatically whenever we attach the material component to an activity.Required Document type of PRs are maintained in transaction 'OPTT'.
    My Client is using three document types for Imports, Material Procurement & Services Procurement respectively & he wants all the three document types to be mapped in Project System implementation.(All other modules have been implemented long back & now IM&PS modules are being implemented)
    In transaction OPTT, only one entry is possible to maintain as Document Type. Can anybody share how to maintain three Document Types?
    Thanks
    Kishore

    Hi Kishore
    Let me clarify one thing that Tcode:OPTT is to specify purchasing item categories(account assignment categories) and a purchasing document type for purchase requisitions in the network, this is not the area where u create new document type.
    1) u can create new document types in the IMG>Material Management >Purchasing > Purchase requisition>define document types. where in u have define the new document type with the allowed categories and link purchase requisition with the document types.
    2) U have to link this document type to the PO document type.
    3) Then go to the OPTT transaction maintain the account assignment categories for the new document type created.
    Reward points if useful
    Regards
    Murali

  • PR?PO document types

    Hi
    What is the purpose behind creating new document types for PR/PO/contact ? as i understood
    1. u may need to define different document types for diff company codes according to client needs, to differentiate them better
    2. u can assign diff internal/external number groups to each document type , so that it will be easy for searching/auditing purposes
    3. this helps to take them through release strategy easily
    Is there any other benifits other than this??
    Regards
    NSB

    Hi,
    The main purpose of document types is to map the business scenario. This is achieved via Account Assignment Category, Item Category and also additional features like assigning different number ranges etc for easy distinction among document type.
    A document type controls which Account Assignment Categories and Item Categories are allowed which in turn controls whether for a particular document type GR is allowed or not (Blanket Orders, GR is not permissible), GR based IV is mandatory or not (Subcontracting scenario), GR is valuated or not (Consignment), Cost Center & GL A/c is mandatory or not, IV is possible or not (Consignment not possible, system generates Invoice) etc and many more.
    Hope this helps you.
    cheers
    Yogi

  • How to change number range for document type ?

    Dear All
    Experts
    How to change the number range for document types for entry view? I am trying to change the number range for all document type as per defined ranges in FBN1, but at the time of saving document type and number range the system is throwing error message as 
    Doc. type C1: Number range 07 is used for ledger L6 with doc. type AE
    Message no. FAGL_LEDGER_CUST093
    I have defined a leading ledger in system too with these settings
    1)     Define ledger for accounting.
    2)     Defining currencies for it.
    3)     Defining ledger group for the same.
    4)     Defining accounting principles
    5)     Assignment of principles to leading ledger.  
    Are there any extra settings required for leading ledger settings?
    I have some doubts those are :-
    How document types defined at ledger level?
    How to define them at leading ledger level?  (Like my case)
    Focus on this will be appreciable.
    Regards,
    Sharvari Joshi.

    hi ,
    The document numbers in the leading ledger and the non leading ledgers should be in sync, they should not have any differences, so incase you are trying to change the number range for C1, the  number range 07 is already been assigned to doc type AE. i guess you have cant use 07 for C1. may be you can try out with an other number range. check this and let me know if you are able to do this.
    coming to
    1.How document types defined at ledger level?
    2.How to define them at leading ledger level? (Like my case)
    Ans 1. please try defining document types for entry view in a ledger.
    path : SPRO- financial accounting new -financial accounting global settings new - document -document types -define document types for entry view in ledger.
    upon prompt enter the ledger and go ahead creating the number ranges for the document types.
    Hope this helps.
    Regards
    amrutha

  • How to block or restrict document type

    Hi friends
    How to block or restrict document types .
    My Business people will not use document types in feature

    Hi,
    The documentation about the authority check within posting is given in the online documentation for the posting ta eg. FB01:
    Perhaps you would like to read the documentation from IMG on the authorization:
    Financial Accounting > Financial Accounting Global Settings > Document > Document Header > Check Display Authorization for
    Document type
    Defining Authorizations for Document Types
    Use
    You can define a special authorization for every document type. To do this, you need to determine what document types in which
    form employees are allowed to process. Authorizations are checked for the following activities:
    Posting documents
    Document display and line item display
    Changing documents
    Programs that evaluate documents.
    The system does not check the authorization for document types that are not assigned an authorization group.
    Procedure
    In Customizing for Financial Accounting, carry out the activity Maintain Enter an authorization group in the document type. You then assign autho For each document type, you can specify whether users are required to enter.
    The same for check of the authorizations of gl accounts.
    PLease check in OMR4 and in OBA7 that for the document types the athorizations groups are maintained.
    F_BKPF_BLA Accounting Document: Authorization for Document Type
    F_BKPF_BES Accounting Document: Account Authorization for G/L Account.
    For example:
    The transaction FB01 includes the above objects - you can see this in Trx. SU24, also as transaction F-02 is a parameter transaction with the original being FB01 these objects would be valid for F-02 also.
    Please also refer to the following NoteS
      150496     F_BKPF_BLA: Authorization for document types
      198238     FI reporting: Authorization check for documen
    I hope this helps to solve the problem.
    Regards
    Ravinagh Boni

  • Document type wise PO with refer PR

    Dear All,
    my clients requirement is that Document type wise PO creation with refer PR & Purchasing group is mandatory.
    but some document type wise PO generation withour PR & purchasing group is mandatory.
    please suggest me.
    Thanks
    Shital

    Hi,
    1. Create Seperate document types one for PO with PR and one for PO without or with PR.
    Follow the pthe SPRO->MM->Purchasing->PO->Define Document types
    Here copy from the standard document type NB and create your own.
    2. Cretae two seperate field selection grps one with PR field manadatory and one with PR field non mandatory.
    Follow the pthe SPRO->MM->Purchasing->PO->Define screen layout at doc level.
    here copy from the standard fields selection grp NBF and create your own two diffrent field selection grp.
    Then once created go to selection group Ref data item and for Purchase requisition as required entry and save it for one field sel grp and for the other as optional.
    3. Assign thease fields selection grps to document types as per your requirement.
    Follow the pthe SPRO->MM->Purchasing->PO->Define Document types
    Define new numbe ranges for your both the document types.
    hope it helps.
    Regards,
    Sujoy
    Edited by: Sujoy on Jun 24, 2009 7:09 AM

  • Change of clearing document type

    Hello,
    Whenever I make a clearing through F-44 t-code for a down payment the document type generated is the standard AB. What should I do in order to change this document type for the same as the original one? I mean that if the document I want to clear is doc.-type DT, I want the clearing document to be DT type too.
    Kind regards,

    Hy,
    I have just tested if change the document type for vendor in OBXH, then i posted invoice (FB60 )of Rs. 60,000 and then credit memo (FB65) Rs. 60,000, the type of invoice is KR and Credit memo is KG. After this I run clearing by F-44, and posted the clearing document and checked that system automatically took the document type defined in OBXH.
    I have tested it for vendor, customers and GLs as well.
    Please change the document types for GL, vendor, customer in OBXH and test it once again, I hope this will work.
    Thanks
    Javed

  • Linking Custom Storage Category to STandard Document Types

    We have created Custom Storage Category ZSRM pointing to Content server.
    We would like to link it with SRM document type defined in ECC in DMS.
    Really appreciate if you can direct us where we can link the above two.
    Additionally would be great to know , why for SRM DMS we have to set it up in ECC and why it is not available in SRM server.
    Thanks In Advance.

    Hi Sotage Catogories are defined and maintained in t-code OAC0 and OACT. Here you need to define certain parameter like area as document management then only these repositories are getting assigned to DMS.
    Understood , so dms is having it's own classification (017) area without which we can not store dms document into any other servers or repositories. If you want to store in other module repositories, then you need to define this repository first in DMS.
    I hope this will resolve the query.
    Regards,
    Ravindra

  • AB document type

    They just noticed that AB documents are showing whenever CCode d 505 payments are cleared. Can someone describe how and when an AB document type would be a payment document type vs normal like VP, KZ, VR?
    thanks

    Hi
    For your first query, Please check the document type assigned in OBXH. The document type defined here is used for generating the clearing document. If you want to change the document type here, you can do that.
    As for the use of a particular document type, it is again a process decision, which generally could vary from client to client. Generally for such transactions, SAP has defined document type AB.
    Assign points if the information is useful
    Regards
    Sanil Bhandari

  • Sales Document type not defined

    Hi
    I am working on an interface. Design is like below
    Purchase Order->File Adapter->XI (BPM)->RFC Adapter->Sales Order in R/3
    When I am trying to cretae a sales document in R/3, I am getting a message back from R/3 saying 'Sales Document is not defined'. But when Checked in R/3, that sales document type is existing. I don't see any Mapping execption in monitoring, but I am receiveing this message back from R/3
    Any feedback will be highly appreciate.
    Cheers
    Rajiv P

    Hi
    Well initially it was a value-mapping problem. It is possible to debug a BAPI/RFC from XI. If it is possible, the please advise me of the procedure. My XI is working fine but I am getting a message back from R/3 as below. Any feedback will be highly appreciated
    <?xml version="1.0" encoding="UTF-8" ?>
    - <rfc:BAPI_SALESORDER_PROXY_CREATE.Response xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
      <E_SALESDOCUMENT_EX />
      <E_STATUS>E</E_STATUS>
    - <RETURN>
    - <item>
      <TYPE>S</TYPE>
      <ID>V4</ID>
      <NUMBER>233</NUMBER>
      <MESSAGE>SALES_HEADER_IN has been processed successfully</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1>VBAKKOM</MESSAGE_V1>
      <MESSAGE_V2 />
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER>SALES_HEADER_IN</PARAMETER>
      <ROW>0</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>V1</ID>
      <NUMBER>384</NUMBER>
      <MESSAGE>Sales unit ****** is not defined for item 000000</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1>******</MESSAGE_V1>
      <MESSAGE_V2>000000</MESSAGE_V2>
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER>SALES_ITEM_IN</PARAMETER>
      <ROW>1</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>V4</ID>
      <NUMBER>248</NUMBER>
      <MESSAGE>Error in SALES_ITEM_IN 000001</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1>VBAPKOM</MESSAGE_V1>
      <MESSAGE_V2>000001</MESSAGE_V2>
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER>SALES_ITEM_IN</PARAMETER>
      <ROW>1</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>V4</ID>
      <NUMBER>219</NUMBER>
      <MESSAGE>Sales document was not changed</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1 />
      <MESSAGE_V2>000001</MESSAGE_V2>
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER />
      <ROW>0</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>C_</ID>
      <NUMBER>005</NUMBER>
      <MESSAGE>The object references could not be written to the CRMKEY</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1 />
      <MESSAGE_V2 />
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER />
      <ROW>0</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
      </RETURN>
      <TI_EXTENSIONIN />
      <TI_ORDER_CCARD />
      <TI_ORDER_CFGS_BLOB />
      <TI_ORDER_CFGS_INST />
      <TI_ORDER_CFGS_PART_OF />
      <TI_ORDER_CFGS_REF />
      <TI_ORDER_CFGS_REFINST />
      <TI_ORDER_CFGS_VALUE />
      <TI_ORDER_CFGS_VK />
    - <TI_ORDER_CONDITIONS_IN>
    - <item>
      <ITM_NUMBER>000001</ITM_NUMBER>
      <COND_ST_NO>000</COND_ST_NO>
      <COND_COUNT>00</COND_COUNT>
      <COND_TYPE>EDI1</COND_TYPE>
      <COND_VALUE>57.600000000</COND_VALUE>
      <CURRENCY>AUD</CURRENCY>
      <COND_UNIT />
      <COND_P_UNT>1</COND_P_UNT>
      <CURR_ISO />
      <CD_UNT_ISO />
      <REFOBJTYPE />
      <REFOBJKEY />
      <REFLOGSYS />
      <APPLICATIO />

  • Message No delivery type defined for supplying plant BP01 and document type

    Hi all,
    I am trying to create a purchase order with a BP01 supplier and the BP02 division but I get the following error message No delivery type defined for supplying plant BP01 and document type.
    When I create a PO with a BP02 supplier and the BP01 I do not get any message.
    How can I fix it ?
    Thanks
    Regards
    Pierre

    1)Create one Customer for Supplying Plant Sales area and assign this Customer no with Receiving Plant in OLME---> PO -
    > Set up STO -
    > define Shipping Data for plants. and maintain the same sales area in your Supplying plant.
    2) In OLME---> PO -
    > Set up STO.....for your Document Type: UB and Suppying plant Combination assign Del. Type NL and Checking rule RP
    3) In OLME---> PO -
    > Set up STO...for your Supplying Plant and Receiving Plant combination Maintain Doc. Type : UB
    Make sure you are maintaining Sales View for your Material at Supplying Plant.
    4) Maintain Shipping point at, SPRO----> Logistics Execution -
    > Shipping -
    > Basic Shipping Functions -
    > Shipping Point Determination for Plants.....there for your Loading group,Shipping Condition, Shipping Plant combination maintain Shipping plant..
    Now Create STO in ME21N with Doc.type: UB at Receiving Plant.
    Then Create Delivery in VL10B from Supplying Plant...
    Then Do PGI in VL02N from supplying Plant.
    Then do GR at Receiving Plant based on Outbound Delivery at Receiving Plant...

  • No delivery type defined for supplying plant 6110 and document type ZSTD

    Hi all,
    I am trying to create a purchase order with a P6110 supplier and the 6115 plant but I get the following error message No delivery type defined for supplying plant p6110 and document type.
    When I create a PO with a 6115 supplier and the 6110  I do not get any message.
    How can I fix it ?
    Thanks
    Regards
    SAGAR

    >
    sagarn wrote:
    > Hi all,
    >
    > I am trying to create a purchase order with a P6110 supplier and the 6115 plant but I get the following error message No delivery type defined for supplying plant p6110 and document type.
    >
    > When I create a PO with a 6115 supplier and the 6110  I do not get any message.
    >
    > How can I fix it ?
    > Thanks
    > Regards
    > SAGAR
    If ZSTD is a copy of UB type PO, then you need to provide the plant number as the supplier. The delivery type can be configured in the following path
    Materials Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order -> Assign Delivery Type and Checking Rule
    Copy and existing record and maintain the combination of your PO type (ZSTD), supplying plant (6110) and delivery type (NL). Leave the others the same.
    Regards,
    Aroop

  • How to define certain document type (BKPF-BLART) for certain movement (101)

    Sometimes ( I think it is becuase of the tcode)  certain purchase 101 movements create a WA type FI document and some other times purchase 101 movements create WE type FI documents. I have seen a table ( accessing from omba transaction) in which for diffenent tcode´s we have either WE or WA. If we always use migo transaction why sometimes in bkpf we have migo_tr, migo_gi, ....;....
    How should I do in order to create always WE FI documents for purchase 101 movements?
    Thanks in advance.

    Check the settings in SPRO-MM-Inventory Management-Number assignemnt-Define number ranges for accounting documents.
    Here you assign accounting document type to tcodes.
    Normally , WA is used in receipts for MB1C/MIGO_GI tcode - for e.g for 561 mvmt type.
    SAP recomends keeping this setting as it is.
    SAP help text copied here for reference:
    Define Number Assignment for Accounting Documents
    In this step, you set the number ranges for the accounting documents which are created when goods movements or inventory differences are posted.
    Accounting documents in inventory management
    For accounting-relevant goods movements, the system creates two different documents:
    material document
    accounting document
    Both the material documents and the accounting documents have their own document numbers. When inventory differences are posted, the system also creates an accounting document for the physical inventory document.
    In this step, you only maintain the number assignment for accounting documents.
    Document types
    Accounting documents are split into document types to allow differentiated document number assignment, which is the basis for distinguishing between the various accounting operations. A number range is assigned to each document type. In a company code, you have to define number intervals for each number range and fiscal year.
    In inventory management, the transaction determines which document type is used.
    Example: Goods receipt for purchase order
    Requirements
    You have already defined the company code.
    Default Settings
    In the standard SAP System, the following document types are predefined for inventory management:
    WA  for goods issues, transfer postings, other goods receipts
    WE  for goods receipts with reference to purchase orders
    WF  for goods receipts with reference to production orders
    WI  for inventory differences
    WL  for goods issues with reference to deliveries (SD)
    WN  for net posting of goods receipts
    PR  for revaluation documents
    Each document type is already assigned a number range. In company code 0001, number intervals are defined for each number range both for the current and the previous fiscal year.
    Number range 49 with the year-related interval 4900000000 to 4999999999 is assigned to the document types for all goods movements, except goods movements with reference to purchase/production orders.
    Document type WE is used for goods receipts with reference to purchase orders and production orders. This document type is assigned number range 50 with the year-related interval 5000000000 to 5099999999.
    Please note that net postings of goods receipts (document type WN) are not active in the standard SAP System. If you want to post goods receipts net, you have to assign document type WN (instead of WE) to the transaction MB01.
    Document type WI is used for posting inventory differences. This document type is assigned the number range 01 with the year-related interval 0100000000 to 019999999999.
    SAP Recommendation
    Activities
    1. Check whether you can use the standard settings.
    2. If not, you have to add new document types to satisfy your requirements:
    a) Define a new document type under Financial accounting document
    b) types.
    c) Assign a number range to the document type.
    d) Under Financial accounting number ranges, define the year-related number intervals for the given number range in your company code. If you do not want to use the year-related number assignment method, enter 9999 in the Year field.
    e) Under Allocate document type to transaction, assign the relevant document type to the transaction codes of inventory management.
    Document type PR (revaluation documents) is already assigned.
    Notes on transport
    You transport number range objects as follows:
    Choose Interval -> Transport in the accounting document Number Range screen.
    All intervals for the selected number range object are deleted in the target system first. After the import, only the intervals you export are present. The number statuses are imported with their values at the time of export.
    Dependent tables are not transported or converted.
    All other activities are linked to the automatic transport.
    Edited by: Saurav on Jan 24, 2011 6:03 PM

  • Output map: Document Type does not match any of the given schemas

    On a send port, we have a map that uses a custom xslt. We were hoping to somehow design the map so the output was essentially a generic xs:any schema.  But unless we ad a reference from our map assembly to the assembly that holds the actual schema for
    the message pertaining to the map out put we get an error:
    The Messaging Engine failed while executing the outbound map for the message going to the destination URL "C:\BizTalk\Test\%MessageID%.xml"
    with the Message Type http://test#testmessage. Details:"Document type "outputtest#outputtestmessage" does not match any of the given schemas.
    Is there a way to avoid having to have the reference? 

    Hi ,
    In BizTalk messages are distinct from each other based on the message type . In your case http://test#testmessage (Namespace#RootNode)
    Now coming to your case have you verified whether you have a schema type matching the response is deployed with the solution. The easy way is to look into specific BizTalk application schema node .
    If not ,What you can do is to create a new schema for output having "TestMessage" as record and any element inside it. After that apply a mass copy
    funtiod from source t destination(in your case any type schema created).
    Thanks
    Abhishek

Maybe you are looking for

  • How can I have html5 audio continue to play in background in iOS7 from my flex mobile app

    I have mobile app I've developed in flash builder 4.6 (flex 4.12 sdk) and I have a stagewebview component which contains HTML5 audio (mp3 retrieved from my web server and streamed / played via the app)... I want to have the ios version of the app CON

  • Freeze during iWork 09 installation

    The installer froze during the installation of iWork 09 trail. I downloded from Apple.com and opened the dmg file. The installation froze at the stage "Configuring Installation". I waited for about 1 day and I finally gave up. Is there something wron

  • "Fast Web View" changing depending on versions

    Hi there, We have some PDFs that need to have the "Fast Web View" option enabled. Although the files have this option enabled when viewed on version 6.0, when the files are viewed on a later version - Version X for example, some of them are still ena

  • Spawn setting in production environment

    Has anyone heard or been told by oracle analyst that Oracle doesn't support spawn setting in production environment? Answer that I received was enabling spawn can be flaky. The domain may easily hang without explanation and it's always been like that

  • Urgent- reset password/email notification

    HI I reset the password of user as administrator in user management console. Result is that, when the user logins with his old password itis asking to change to new password . This is coming . But user is not getting any email regarding this , though