Document-Type not known for scanned invoice

Hi experts,
I assign in OAWD a scanned document (Vendor Invoice) with "Storing for subsequent entry" to an user.
Vendor Invoice is linked to TA F-43.
The message appears in the Business Workplace SBWP. After executing a window appears "Process document type (Enter Document)" but without document type and TA F-43 will not be called.
It looks like that the document lost the relation to document type and the transaction.
Has anybody experience with this issue?
Thank you in advance
Martin

Hi Martin,
I suppose you did configure the OAC2, OAC3, SOA0 (BKPF-CREATE) and OACA - with parameter Transactioncode eq. F-43
Now 1st try F-43 for your user in standard dialog mode. Working?
Does the scanned image come up at after executing the workitem? (it should)
Than the F-43 should be called. This has no other pre-set value. So FI document type (BLART) is not set in OAWD.
How far do you get?
Regards
Tomas H

Similar Messages

  • Accounting documents are not posted for Excise invoice

    Hi,
    1. The Excise invoice has been created with reference to F2 invoice but the accounting documents is not posted for excise invoice, what is the settings needs tobe maintained to post the accounting entries to excise invoice..?
    2. where we will maintain number ranges for excise invoice..?
    Thanks
    Rao..

    hi
    1. The Excise invoice has been created with reference to F2 invoice but the accounting documents is not posted for excise invoice, what is the settings needs tobe maintained to post the accounting entries to excise invoice..?
    Not sure but can u try to relese this to accounting
    2. where we will maintain number ranges for excise invoice..?
    Excise invoice number range is depend on Excise series group.
    T-Code : SNRO
    Following is the No. Range Objects related to Excise, select the proper no. range object as per your requirement.
    J_1I57FC - 57FC Number Range
    J_1IARE1 - ARE1 Doc No object based on Series Group
    J_1IARE3 - ARE3 Doc No object based on Series Group
    J_1IBOND - Excise Bonding: Bond number object
    J_1ICERT - Withholding Tax Certificates (India)
    J_1ICHLNNO - Internal number range for challans
    J_1ICONPLA - Consolidated PLA serial no. generation
    J_1IDEPINV - Excise Invoice Number for Depot Invoices
    J_1IEXCEXP - Export excise invoice number range
    J_1IEXCINV - Excise invoice number
    J_1IEXCLOC - Local excise invoice numebr range
    J_1IEXCTST - Excise invoice with intervals
    J_1IEXINEX - Excise invoice number for export
    J_1IINTNUM - Internally document number to be generated
    J_1IINTPR2 - Despatch serial number
    J_1ILIC - Excise Bonding: License number object
    J_1IPLA2 - PLA part II number range object
    J_1IRG1 - RG1 Number range object
    J_1IRG1_T - No. Range for RG1 - Excise group / Material
    J_1IRG23A1 - RG23A part 1 no. range object
    J_1IRG23A2 - RG23A part II number range object
    J_1IRG23C1 - RG23C part I number range object
    J_1IRG23C2 - RG23C part II number range object
    J_1IRG23D - Folio Numbers for RG 23D
    Check the link
    Re: Excise Invoice Number Range
    excise invoice and domestic invoice sharing same number range

  • Invoice output Condition type not populated for many invoice documents

    Hi Guru's
    Invoice  Out put Condition  type for printing  not populated in the invoice document. Now We need to insert condition type for many  documents to print at a time. We can manually place condition type  at document header level individually for every document. But we have many documents to print.
    plz advice me how to print all these documents
    Thanks in advance.
    Regards,
    Ravikanth

    Hi Ravi
    Just take help from your ABAP team. Record the event in SHDB ask then to get invoice number from excel file and loop the program.
    This will be more faster then LSMW.
    I am giving you BDC code
    report ZBILVF02
           no standard page heading line-size 255.
    include bdcrecx1.
    start-of-selection.
    perform open_group.
    perform bdc_dynpro      using 'SAPMV60A' '0101'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'VBRK-VBELN'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'VBRK-VBELN'
                                  '90010310'.
    perform bdc_dynpro      using 'SAPMV60A' '0104'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'VBRK-FKART'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=SICH'.
    perform bdc_transaction using 'VF02'.
    perform close_group.
    Regards
    Vijay

  • Originating document number not updated for one invoice line item

    Hi,
    We have a invoice document number in which the originating document number is not updated for one of the line items ,this is order related down payment invoice .May be this is due to system inconsistency so is there any SAP note to overcome this problem.
    Best Regards,
    Rohit

    Dear All,
             I found out the problem for not updated in F-04. "While create the receipt document in GL master Open item management maintained box was not checked". It can be found in BSIS table - OI Management'.
             Is there any other way to clear this document.
    Thanks...

  • Accounting Document not posted for Cancelled Invoice -error in FI interface

    Hi,
    When I create a billing document then an accounting document gets created automatically in the background and then when I cancel the billing document no accounting document gets generated and the field Posting Status in header Detail of Billing document updated as "Errors in Financials Interface.
    I tried to release it for Posting via VFX3 but failed due to below error message in Log:
    "Incorrect doc.no.: 4900000005. Select document number between 3000000000 and 3099999999"
    I have checked the Number range assignments to the Invoice type and Accounting type.
    The number range is same for both Invoice type (Y0F2) and Cancelled Invoice type (Y0S1).
    The Accounting document type (RV) is also same for both the cases. But it is working fine for Y0F2 (Acounting document generated and cleared automatically). But not working fine for Cancelled Invoice (Y0S1).
    Can anybody please help me find out a solution to the issue.
    Thanks, Ram.

    Hi,
    The error message F5151 refers to the number range of the FI document.
    Please have a look at the note 1259505: FAQ: New cancellation procedure in SD, which covers this issue in detail.
    Question 5:
    Q5. What is the FI document type, generated by the cancellation ?
    In the old cancellation procedure, the FI document type is always
    determined in SD, and passed to FI (the same when a normal invoice  -
    not a cancellation -  is transferred to accounting).
    In transaction VOFA there is the field 'Document type' (TVFK-BLART).
    If this field is filled, then the FI document will have the document
    type maintained here.
    If TVFK-BLART is empty, then the FI document will get the default
    document type 'RV'.
    If the new cancellation procedure is performed, the FI document type is
    always determined in FI, based on the document type of the FI document
    to be reversed.
    In transaction OBA7 the FI document type has assigned the field 'Reverse
    document type' (T003-STBLA).
    If it is filled, then the FI cancellation document will get the document
    type maintained here.
    If T003-STBLA is empty, then the FI document cancellation will get the
    same document type as the cancelled FI document.
    Notice that an unexpected FI document type can cause the error message
    F5 151.
    Example:
    F2 invoice 90000001 was released, creating an accounting document with
    document type 'RV'.
    This F2 invoice is reversed by the S1 billing document 70000001.
    In customizing of SD there is:
    Billing Type    Document Type
    F2              RV
    S1
    In customizing of FI there is:
    Document Type    Number range   Reverse Document Type
    RV               00             AB
    AB               01             AB
    The FI number ranges (object RF_BELEG) are:
    No  From number    To number   Ext
    00  0090000000     0099999999  X
    01  0100000000     0199999999
    Different situations can occur, due to these customizing settings of the
    FI document type, caused by the type of cancellation.
    If the new cancellation is used:
    The FI document type 'RV' has 'Reverse Document Type' = 'AB'.
    Document type 'AB' has number range '01' set as internal.
    So the FI document will have its own number included in
    100000000-199999999.
    There is no issue.
    If the old cancellation is used:
    The cancellation billing type S1 has no 'Document type' maintained, so
    the FI document will get document type 'RV'. It has number range '00',
    set as external number range.
    So the FI document should get the same number of S1 billing document.
    But the S1 billing document has number 70000001, not included in the
    interval of number range '01'.
    This will cause error F5 151.
    I hope this information helps you.

  • Accounting document not generating for excise invoice-please help

    Dear all ,
    my issue is
    accounting document not generating for excise invoice
    we are creating accounting document in J1iin
    with refferance to billing document but the accounting docuemnt is not generating
    the accounting document for billing document is generated
    so why the accounting document for excise invoice is not genrating its showing the correct amount in BED ,cee and HE Secc.
    please help

    Dear G. Lakshmipathi,
    As uknow i am getting problem when i am creating the debit memo
    so is there any specific ETT for debit memo is there .because we are not maintaining delivery type to billing type here in CIN setting
    so its not goods removal through sales . so what will be transaction type for this.
    how to check the error that why the accounting document is not generated as no error log is also comming.
    so please help me in this regards.
    Thanks with Regards
    Subrat

  • The document is not relevant for invoice lists

    Hi SD Experts,
    When i am creating invoice list (T.Code:VF21),I got the error that"the document is not relevant for invoice lists". i entered  invoice list type per billing document type (transaction OVV7).
    I already did those settings in the IMg. But still its not working, i really appericiated that you look into the query.
    Please advise.
    Thanks
    Tulasi

    Hi GTNRNR, 
    -- Check in  Customer Master Record (XD01) in billing tab the invoicing list Dates & Invoicing dates fields
    --Go to T.Code OVT0 & check these fields are included in your account group
    --Maintain the Copy controls for Proforma Invoice (F8) to Invoice list(LR) in VTFF
    --in header Copying Req 016
    --check mark on copy item numbers
    --Pos/neg qty is +
    ---Go to VF21 and enter the billing document No & Billing Type as LR & Execute
    Let me know if your problem is resolved.
    Regards
    Pradeep

  • Accounting document not generating for excise invoice.

    Dear all ,
    my issue is
    accounting document not generating for excise invoice
    we are creating accounting document in J1iin
    with refferance to billing document but the accounting docuemnt is not generating
    the accounting document for billing document is generated
    so why the accounting document for excise invoice is not genrating its showing the correct amount in BED ,cee and HE Secc.
    please help
    regards
    Subrat

    IMG -> In Logistics u2013 General -> Tax on Goods Movement -> India ->  Account Determination -> Specify Excise Accounts per Excise Transaction
    Check if the following is maintained or not
    DLFC       CR Credit      PLAAED PLA AED account
    DLFC       CR Credit      PLAAT1 PLA AT1 Account
    DLFC       CR Credit      PLABED PLA BED account
    DLFC       CR Credit      PLACESS PLA cess account
    DLFC       CR Credit      PLAECS PLA ECS Account
    DLFC       CR Credit      PLASED PLA SED account
    DLFC       CR Credit      RG23AED RG 23 AED account
    DLFC       CR Credit      RG23AT1 RG 23 AT1 Account
    DLFC       CR Credit      RG23BED RG 23 BED account
    DLFC       CR Credit      RG23ECS RG 23 ECS Account
    DLFC       CR Credit      RG23SED RG 23 SED account
    DLFC       DR Debit       MSUSP CENVAT suspense account
    Also IMG -> In Logistics u2013 General -> Tax on Goods Movement -> India ->  Account Determination -> Specify G/L Accounts per Excise Transaction
    Check if for all Excise group u2013 DLFC u2013 Company Code combination GLs are maintained or not (especially in production client)

  • Textbook download error message: "Document is not licensed for this device type"

    Hi everyone,
    I bought a textbook that came with a free digital edition. I downloaded it, then tried to load it into Digital Editions (which I registered to my account). The texbook almost finished importing, then at the very end gave me an error message that said "[The name of the book]: Document is not licensed for this device type." The textbook is published by Aspen Law. I'm running Mac OS X 10.7.1 (Lion). Has anyone else had a similar issue or know of a resolution?
    I've looked at other forum posts, and my situation seems remarkable like this one:
    http://forums.adobe.com/message/3098928#3098928
    I called the publishing company and tried to explain this to them, but they just said it was a problem with Adobe and Mac.
    Thanks in advance,
    Chris

    OK - here's the issue.
    When I downloaded Adobe Digital Editions I authorized my computer with my Adobe Account - apparently I wasn't supposed to do that.  McGraw-Hill said that their file would ONLY work if the computer was not authorized with an Adobe Account (they should have said so after the order).
    So after de-authorizing the account (ctrl+shift+d) I tried to open up the .acsm file again and I got a new error: e_lic_already_fulfilled_by_another_user.  I'm afraid that the license was used up by Adobe Account, never mind that it actually never downloaded.
    I guess the next step is to try and get another license issued?

  • Document is not relevant for billing

    Dear All,
    We are implementing ECC 6 in one of our client.
    Our client manufacturer of x finished product, they want monitor the production process through Project system and deliver should be through project system,
    We did the complete configuration from Production order till delivery in PS is working fine.
    But when we try to post billing document from the delivery document, the system is showing the following error,
    Document is not relevant for billing: LP is not relevant for F2.
    Our doubt is in this process, whether excise invoice will be generated or not?
    this LP is hard coded in SAP, We are unable to rectify the error,
    our GO-LIVE date is 1st March
    can any one help us to solve this issue?
    Thanks in advance
    regards
    Elango

    LP is not relevant for F2
    What is LP ??  Is it Delivery type or Item Category ??  Nevertheless, copy control is missing in VTFL.
    whether excise invoice will be generated or not?
    If physical material movement is there from a manufacturing plant to outside, then definitely, you should generate an excise invoice
    thanks
    G. Lakshmipathi

  • The document is not relevant for billing

    Hi Experts,
    I have a problem while doing STO from plant to depot. I am not able to generate Proforma Invoice. I am using following steps:
    ME21N, VL10B, VF01.
    I have check all my setting of STO. And I have set Billing Relevance-D (Relevant for proforma) to Item Category NLN.
    I am getting the following error in vf01:-
    0080015463 000000 The document is not relevant for billing.
    Please reply and thanx in advance.

    Hi,
    Can you check if both the Plants used are belonging to two different Company Codes? 
    If both Plants are from the same Company Code, you would not be able to create Billing document in this case.
    After that, could you also confirm the type of STO type that you are using?  Is it UB or NB?
    Where inter-company is concern, when you use STO Type = NB, then inter-company billing should be able to be created without any problem.
    For intra-company, you may use STO type = UB.
    If all the checking is OK, you may want to check also the copy controls in VTFL.
    Hope the above helps.
    Thanks.
    Rgds.

  • An accounting document is not required for this billing document

    Hi,
    While releasing the billing document to accounting the error is coming like "An accounting document is not required for this billing document"
    Diagnosis:
    The billing document has the net value '0' and does not create an accounting document. Despite this, the posting status 'C' (Posting document has been created) is set internally for this billing document.
    But the net value is coming in the sales order and alsi into the Billing document.
    gurus plz help me.
    regards,
    ragesh.

    Goto VOFA screen and check for ur billing type , what is assigned in the document type field?.
    Also please check, the posting block is activated. if it is, please remove.
    Also goto the accounting document type settings at OBA7, check whether the customer field is ticked under the account type allowed tab.
    Please let me know, whether ur problem solved..
    Reward points if useful..

  • 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

  • PO document type not transferring to Customs management

    Hi,
    We have configured PO document type in GTS for Import and it got transfer to Complaince not to customs.  I have created CULOIM document type and item category on customs.  when i checked on this table /SAPSLL/V_TLEYVS i couldn't find CULOIM document type..  When i try to create a new one it say CULOIM document type already exist...
    I do not know why it is saying like that even document type not there in that table and where would i find that.
    One more question:
    When we assign document type to logical system on Customs we can see GTS document type field... when you press F4 you can see CD Cat - A... Can you tell me what is that and where do you define and assign to custom document type.
    regards
    rc gopi

    You can maintain the table by going into the SPRO and defining the doc tyoe you looking for , Onc eyou maintain there it reflects in in this table as it Configuration table.
    If you want to delete , add any entry directly in table then u can do that by getting in debug mode.
    Select a  entry in table
    Double click on it
    Do /h  to switch on the debugging
    Press Enter
    You will See different Case for "Code"
    Type the filed name Code in in "field Name"
    it will display the value 'SHOW'  you can change this value as desire like to Delete 'DELE' , to insert new value 'AVNO' and then click on change pencil.
    and press F8.
    Now you come to the screen where u can do the changes and save it.
    Custom Doc Category is taken automatically by SAP as for Export and Import doc type  in customs it is always A.
    If you cDefine Document Types for Advance Docs for Customs Declaration it is C.
    Each category has got it one chateristics , so if we defining correct documnet type we need not to worry for category as it will by default come as set in SAP.
    Kind Regards,
    Sameer

  • Profit center Document is not created for Balance sheet items

    < MODERATOR:  Message locked.  Please post this message in the [Controlling forum|SAP ERP Financials - Controlling;. >
    Dear all,
    Profit center document is not created for balance sheet accounts , where i specified in 3KEH (default profit center for balance sheet a/c's) , i did n't do any changes , if i do any changes in dev , then i will transport to quality  there is no pending requests
               Same entry In quality environment profit center is updating and creating profit center document  for balance sheet accounts . I compared with actual posting settings like  Maintain Document Types and Define Number Ranges for Local Documents but it is same as development
    regards
    Govind
    Edited by: Govind Yadav on Sep 24, 2008 8:33 PM

    Is any body find the solution of this problem
    I am also facing the same problem Profit center document is not getting created from any MM document
    3KEH configuration is there but still the system not generating the Profit center document for those materials where there is no profit center assigned in the material master data and in 3KEH i have configured that it should post to dummy if there is no profit center in the material master data
    Please tell me if some one have the solution to this problem
    Bilal

Maybe you are looking for

  • How can we bug Apple to enable temp readouts?

    I've read somewhere that Apple has said that they will enable temperature readings in the new Macbook Pros if there is enough interest. How can I express my interest to them?

  • Oracle 11g Form/Reports Server - Stable Version 11.1.1.7 (or) 11.1.2.1.0?

    Hi Friends, We are using Oracle 10g Forms and Reports with 10g Database. We would like to upgrdae 10g Forms/Reports to 11g Forms/Reports and Database to 11g. Please let us know which version of Forms/Reports is stable. 11.1.1.7 (or) 11.1.2.1.0 What i

  • CORBA Errors

    I am new to CORBA Programming. Are the below errors very common errors occur due to some misunderstanding on Java ORB & CORBA Programming? ERROR: org.omg.CORBA.MARSHAL: minor code:0 complete: Maybe org.omg.CORBA.MARSHAL: minor code:0 complete: Maybe

  • (Example) Books to get me started

    Hi, I am new to Java programming and besides the Herbert Schildt's, "Java2: The Complete Reference" book (required by instructor), I would like to purchase some other books to get me started into the subject. I am specially interested about books loa

  • Photoshop CS5 Error - Bad Image

    I am getting the following error on our machines in a computer lab.  We are using Windows 7 Professional.