Down Payments Error: Account type K is not defined for document type DZ T

I am getting the error message: Transaction code: F-29
Account type K is not defined for document type DZ
     Message no. F5243
In this case i am trying to post a customer down payment in t.code:  F-29.
In the document type DZ in OBA7 we tick only G.L and Customer tab as this is not a vendor document.
Also the settings in T. Code : OBXR where we maintain configuration for customers has been maintained with a special G/L reconciliation account.
any help will be really appreciated,
Regards
Satish

I have checked all the settings
OBXR for Customer Down Payments. It is with indicator A and a Special G/L Account has been configured.
The special G.L Account is of the Recon account type Customers with FSG as Recon accounts
The document type DZ in OBA7 is ticked for G.L and Customer and this is how i think it should be as i am not paying a vendor downpayment
but it still gives me the same error.
Regards
Satish

Similar Messages

  • Error:Account type D is not defined for document type RE

    Hi! I encountered this error msg: "Account type D is not defined for document type RE"  while posting IR in mir6.  What does this error msg mean? Thanks!

    hi,
    RE stands for Gross postings...
    When you block the document for payments...its never possible to the post the payments for such documents...
    The invoice seems to get posted, but is internally blocked for payment and later you need to delete the payment block indicator and process the invoice further for payments...
    check OMBA as well for the settings...
    Regards
    Priyanka.P

  • Error - Account type D is not defined for document type WL

    I am getting error while doing PGI (Post Goods Issue).
    Error - Account type D is not defined for document type WL

    As we had the same problem for a document in our system, I was also browsing for the answer. I saw this thread and now we have found the solution, so could not resist sharing, although it is an old posting.
    In these cases it can be that a user wants to create a purchase order of the type UB. But if you have stock transport between two companies, you should not use this order type. You have to use order type NB.
    If the user creates the PO with NB then probably they will not get the message.

  • Account type D is not defined for document type RE - Credit Memo

    I tried to key in credit memo of fixed asset at MIRO but prompt out this errors "Account type D is not defined for document type RE". I checked OMBA - account type for vendor is selected. Any advise to resolve this problem?

    Hi Sanil,
    It is just a debit Vendor and Cerdit Fixed Asset. Is anything wrong here?

  • Account type D is not defined for document type RE

    Hi can any one tell me use of the field " Account with vendor" in table LFB1?
    Regards

    Which field are you speaking about exactly? Can you give its technical name?
    Is it LFB1-EIKTO? F1 help for the field:
    Short Text
    Our account number with the vendor
    Definition
    This field contains the account number the company is listed under at the vendor.
    You work for companyA, your vendor is companyB. At companyB, in companyB's system, companyA is created as a customer, and they define an ID for it (let's say: "123456").

  • Account type K is not defined for document type WA

    Hi,  I encountered this while doing movement type 301 - transfer posting plant to plant.   What does this mean?
    Thanks so much.
    Regards,
    Paula

    Hi,
    Intra-Company STO  R One Step Method & Two Step method:
    Inter Company STO - One step Method: 
    At Supp.Plant: Stock Acc. BSX is Credited  
    At. Rec.Plant : Stock Acc. BSX is Debited
    If you maintain Std. Pricing (S)at Rec. Plant and if there is any Price Diff., then Price Diff. Acc.( AUM) will be triggered....
    Here all the Acc.Doc. will be generated while doing PGI only.....No Acc. Doc. will be generated at GR...
    Inter Company STO - Two step Method:
    At Supplying .Plant....While doing PGI..:
    Stock acc. BSX is Credited
    Cost of Goods sold Acc.(VAY) is Debited(+)
    At. Receiving Plant While doing GR:
    Stock Acc. BSX is Debited(+)
    GR/IR Clearing Acc is Credited
    If you maintain any Std. Price and if there is any price Diff. then Price Diff. Acc will be triggered...
    Regards,
    Biju K

  • Method 'PROCESS' is not defined for object type 'BUS2081'

    Hi All,
    I am using a workflow for incoming invoice approval using WS20001004. I prepared one version for this. The standard business methos bus2081 i delegated to zbus2081. Here i placed one decision step for reject or approve. In the same task in inbox i can see the document i can see as attachment. Now the issue is after seeing the attachment when i click on task in  my inbox it status is changed to red and i can  not process it further.In log i can see the error like Method 'PROCESS' is not defined for object type 'BUS2081'. This method i do not have in standard or in delegated one. I was struck here. Pleas help in this.
    Regards,
    Madhu.

    Hi,
    "Here i placed one decision step for reject or approve." if your workitem is based on standard user decision step type of workflow, then the business object in underlying task should be 'DECISION' and method should be 'PROCESS'. I think in the task you have put your custom business object instead of business object 'DECISION'. This could be the reason you are facing error.
    Regards,
    Ibrahim

  • Error M8-688 - Creation of several vendor line items is not possible for document type RN.

    Hello All,
    We are using the Net Invoice Posting with document type RN(Invoice- Net). We are generating different vendor line items in the accounting document based on the withholding tax codes involved in the invoice posting. When it comes to net invoice posting system is giving an error message M8-688 - Creation of vendor line items is not possible for document type RN. Is there is any way to create multiple vendor items with net invoice posting? Please suggest.
    Thanks,
    Chandu.

    I dont think that there is any way because it is a hardcoded error message.
          IF NOT t003-xnetb IS INITIAL.
            MESSAGE e688 WITH pi_rbkpv-blart.
          ENDIF.
    SAP is checking the customizing for net/gross posting per document type in table T003
    And if it is set up as net, then it is a hard error.

  • Withholding tax type FE is not defined for country MY

    When I assign cocd to Fe (Withholding tax type for us-1099 fedral withholding tax) to us and unit 100.
    i get an error Withholding tax type FE is not defined for country MY..
    pls help

    Hello Prajay,
    You should first search in SCN before posting your queries. Most of your issues will be resolved.
    Anyhow for this., you Need to create a Withholding tax type for the Country wither for Invoice posting or for payment posting.
    The same can be maintained at the following path in SPRO.
    SPRO-->> Financial Accounting -> Financial Accounting global Settings --> Withholding Tax --> Extended Withholdingtax -> Calculation --> Withholding Tax type.
    Here create the Withholding tax type for Invoice posting or Payment Posting.
    BR
    Amitash

  • Set type COMM_PR_UNIT is not allowed for product type

    Hello all, I am working in SRM 7.0 and when I try to replicate service master (DNL_CUST_SRVMAS) I have this error:
    Set type COMM_PR_UNIT is not allowed for product type
    What can I do? I think that is an ABAP problem
    Thanks in advance
    Rosa Rodríguez

    Rosa,
    This note is something different and nothing to do with the issue. Can you share how did you resolve the DNL_CUST_SRVMAS issue? We are also getting same error.
    Thanks,
    Jagadish

  • Event 'INFO_APPRAISEE_CHANGE_APPROVE' is not defined for object type

    hi all
    i made 4 workflows for MBO appraisal using APPR_DOC BO nd using std wfs- ws12300114, ws12300122, ws12300124 nd ws12300125. all r working properly in development server.
    but
    in quality all r giving errors related to evevts. as for example, for ws12300114 workflow it is giving error--
    "Event 'INFO_APPRAISEE_CHANGE_APPROVE' is not defined for object type"
    for all 4 wfs it is giving error like this related to event nd business object.
    plzzzzzzzz anybody knows thn reply or call me at 09886999122 or mail at [email protected]
    thanks in advance
    Raj

    Hi,
    Since you are saying that the object worked fine in DEV and giving problem in Quality I feel that some sort of Your Dev work was not properly included in the Transport Request and was not gone to Quality server.
    Something like EVENT activation, release status etc were not gone to Quality
    check them.
    reward if useful
    regards,
    Anji

  • "Event 'INFO_APPRAISEE_CHANGE_APPROVE' is not defined for object type 'APPR

    hi all
    i made 4 workflows for MBO appraisal using APPR_DOC BO nd using std wfs- ws12300114, ws12300122, ws12300124 nd ws12300125. all r working properly in development server.
    but
    in quality all r giving errors related to evevts. as for example, for ws12300114 workflow it is giving error--
    "Event 'INFO_APPRAISEE_CHANGE_APPROVE' is not defined for object type 'APPR_DOC' "
    for all 4 wfs it is giving error like this related to event nd business object.
    plzzzzzzzz anybody knows thn reply or call me at 09886999122 or mail at [email protected]
    thanks in advance
    Raj

    Hi,
    Since you are saying that the object worked fine in DEV and giving problem in Quality I feel that some sort of Your Dev work was not properly included in the Transport Request and was not gone to Quality server.
    Something like EVENT activation, release status etc were not gone to Quality
    check them.
    reward if useful
    regards,
    Anji

  • Class type 022 is not defined for object for BATMAS

    Hi Experts,
    while creaitng the LSMW for batch classification,I faced the error during IDOC processing as "Class type 022 is not defined for object".I am using
    Business Object      BUS1001002
    Method               SAVEREPLICA
    Message Type         BATMAS
    Basic Type           BATMAS03
    Pleas guide how to resolve the error.
    Also ,as I intend to make LSMW for batch classifications.Is this the correct way.
    Please guide on this also.
    Regards.

    Hello Jass,
    Symptom
    The BATMAS03 basis type (message type BATMAS) /FB BAPI_BATCH_REPLICATE  cannot transfer any classification information. Please review note 1070634.
    First Option :
    You should first transfer the batmas and then the clfmas idoc.
    Second Option :
    You could create the batch together with classification. Normally the problem is the missing CUOBJ_BM in table MCH1. It is not necessary in all situations that the field have to be filled, but it can be in some cases (And it is better to store the right  information in the corresponding fields). Especially when you transfer batch/classification information in other system the field have to be filled.
    The way to create the batch TOGETHER with classification by using BATMAS IDOC is to set the following parameters correctly :-
    set E1BPBATCHCTRL-DOCLASSIFY to X and fill the segments with relevant classification information
    E1BP3060_ALLOCATION
    E1BP3060_VALUATION_CHAR
    E1BP3060_VALUATION_CURR
    E1BP3060_VALUATION_NUM
    In this case the field mch1-cuobj_bm should be filled with correct CUOBJ. You can also use function module BAPI_BATCH_SAVE_REPLICA to create batches together with classification.
    Hope this information helps
    Regards
    Amber

  • Class type 022 is not defined for object for batmas in LSMW idoc

    Hi Experts,
    while creaitng the LSMW for batch classification,I faced the error during IDOC processing as "Class type 022 is not defined for object".I am using
    Business Object BUS1001002
    Method SAVEREPLICA
    Message Type BATMAS
    Basic Type BATMAS03
    Pleas guide how to resolve the error.
    Also ,as I intend to make LSMW for batch classifications.Is this the correct way.
    Please guide on this also.
    Regards.

    Hi,
    Go to TCode OMCE and check the batch level.
    If batch is activated at material/client level then use class type 023, if it is at plant level the class type 022.

  • Order Reason ABC not defined for Order Type Retrun order

    Hi
    I am getting following " Message no. V1 899 " when i am  doing return order without refernce .
    Order reason is defined in customization but still we are getting the following message " Message no. V1 899 " /Order Reason E18 not defined for Order Type ZEF9.
    Can any one help me
    regards,
    kiran

    Hi Kiran
    As you have created sales order with document type ZEF9 but you have not taken any reference document then go to VOV8 and select ZEF9 and maintain  the order reason feild and then do the process
    Regards
    Srinath

Maybe you are looking for