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

Similar Messages

  • 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.

  • 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

  • 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

  • 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

  • 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?

  • 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

  • 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 not defined for object

    Hello,
    When I look into one of the standard tasks in my wf, this message appears:
    "Method 'POPUPCONTABLE' is not defined for object type 'ZBUS2081'"
    This problem happens in Test (Quality - QAS) environment, but not in Development (DEV). So I have activated and generated the object type in DEV and then generated again the whole wf, and included it all into a transport request.
    After the requests were released and imported in QAS these modifications apparently did not take place, and the method is still unrecognized for that object.
    How could I make sure that this change will be included in the requests? And, is this approach right (activating the object type)?
    Appreciate your suggestions,
    Best regards,
    Ivson
    Note: There are other/similar methods in that object type, in the same wf, that work ok.

    Hi Ivson,
    The transport system can be a bit flaky, though to be fair it can get quite complex. What it tries to do in the case of interdependent objects is to attempt activation of one thing, then reactivate the other and go back and reactivate any failed ones.
    There are a few notes on OSS regarding transports and you'll see a few recommendations to simply retransport things if they failed. One way to minimize problems is to transport objects and code first, then workflows, then customizing.
    As to delegation, you said 'other attributes work' so I assumed you'd delegated. What you should be doing is creating a delegation from BUS2081 to ZBUS2081. This is effectively the reverse of inheritance and makes all your additional components in the Z-object available as part of the BUS...-obj. In your workflows you should then ONLY work with BUS2081.
    Cheers,
    Mike

  • Payment order are not defined for extended withholding  tax

    Hi Gurus,
    Would you please help me with the message below. It appears on F110 when I try to pay a vendor open item with extended withholding tax:
    Message FZ626 -Payment orders are not defined for extended withholding tax
    In my company payment orders are created in F110 for accounts payable, as we use another ERP system (Baan) to perform the local accounts payments, and now I've just activated Extended withholding tax functionality With accumulation (necessary in Brazil) but I get this error.
    Is it not possible to user payment order with extended withholding tax + accumulation? I find it hard to believe...
    I've tried to unflag the payment order only for the payment method I'm using in FBZP t.code, but then no payment order were created but instead a payment document were posted with the withholding tax accumulation, but this is not the way we are working, and nothing is sent to Baan
    any help is welcome

    The payment method "Y" the option "payment order only" was marked?
    For a withholding tax type with accumulation in a company code with extended withholding tax payment
    methods that create only payment orders can´t be used. Payment orders can only be created only if there are
    no tax types with accumulation involved in the paid items of the payment run.
    The functionality extended withholding tax works fine for Brazil
    however, you can´t use the payment order with this functionality.
    Please, review your customizing for payment method 'Y" in transaction
    FBZP.
    Best regards,
    Leonardo Vedovelli
    FI Support Engineer
    SAP Active Global Support

  • Acct determination for Account-assigned purchase order with keys not define

    Hi,
    I'm trying to post an IDOC of type BBPIV through XI to an R/3 system.
    The posted idoc in R/3 is in status 51 (Application document not posted) with the error message "Acct determination for Account-assigned purchase order with keys not defined in chart of acts WP2P"
    As per my understanding this is something related to FI.
    Long text of the error is "The system cannot generate an automatic posting because there is no account determination defined for Account-assigned purchase order with keys   in chart of accounts WP2P.
    Correct the account determination for Account-assigned purchase order"
    Please help me how to solve this.
    Regards,
    Rashmi

    Hiya,
    This looks like its a MM posting / transaction.
    You need to go to OBYC and maintain the account assignment. If you provide the business scenario (GR into Stock, Subcontracting, etc.) for the process, I may be able to help.
    VKOA is for SD account assignment and I don't believe you can use that here.
    Cheers.

  • Scheduling parameters are not defined for production orders

    Hi All,
             when i convert the planned order to production order  i got this massage popup coming  Scheduling parameters are not defined for production orders . please let me know this .

    Hi,
    One of major customization steps for the order type is missing. Run OPU3 and maintain settings for the order type you are using. You may copy settings from an older type.
    Regards.

  • Message FZ626 -Payment orders are not defined for extended withholding tax

    Hi Gurus,
    Would you please help me with the message below:
    Message FZ626 -Payment orders are not defined for extended withholding tax
    In my company  payment orders are created in F110  for accounts payable, as we use another ERP system (Baan) to perform the local accounts payments, and now I've just activated Extended withholding tax functionality With accumulation (necessary in Brazil) but I get this error.
    Is it not possible to user payment order with extended withholding tax + accumulation? I find it hard to believe...
    I've tried to unflag the payment order only for the payment method I'm using in FBZP t.code, but then no payment order were created but instead a payment document were posted with the withholding tax accumulation, but this is not the way we are working, and nothing is sent to Baan
    any help is welcome !
    TREAD LOCKED SINCE IT IS DUPLICATED FROM THREAD payment order are not defined for extended withholding  tax

    Hi,
    On the analysis,  the system expects an entry in the T059Q table with
    code as XX.
    The reason being in the extended withholding tax we use multiple
    witholding tax codes and these entries are stored in the table
    with_item. And in BSEG we populate the field withholding tax code i.e.
    BSEG-QSSKZ  with the value 'XX'. In classical withholding tax we used to
    store the code directly which is not possible with Extended withholding
    tax.
    As the field BSEG-QSSKZ refers to the values in the table T059Q-QSSKZ
    the entry 'XX" needed in this table for the corresponding country of the
    company code to maintain the correct relationship and consistent
    database information.
    Hence for the statistical purpose and for the internal calculations we
    need an entry in the table T059Q. Could you please maintain this code
    i.e. 'XX' also in the table T059Q in a test system? Then retest your issue.
    This should resolve your issue.
    Kind Regards,
    Vanessa.

Maybe you are looking for