Class type not defined for this object type

Hi Friends,
Could u please guide me ?..We have a requirement to extract some data from classification system.
This is related with class type 023 - Batch
I want to use the following parameters in CTBW.
basis datasource :Z_BATCH_ATTR
class type : 023
object table :MCHA
Datasource type : ATTR
I am getting an error "Class type not defined for this object type" when i enter the above entries in CTBW.
The only way I'm being able to make this work is changing object table from MCHA to MCH1.
This solution does not fit me bacause MCH1 table dont have Plant as Key, and I need it.
Do you know what should I do to solve this?
Thanks in advance

Hi,
I believe we have to use the list of standard "Basis DataSource", as I'm also stuck with the same issue. Let me know what Basis Data source you selected in this case.
As I'm trying to extract Batch attributes from "AUSP" Table.
I have given class type= 023
Obj Table= AUSP
But not sure which "basis datasource" I need to select.
Thanks,
Satish

Similar Messages

  • Sales order creation is not possible for this notification type

    Hello,
    I want to create Sales Order through following menu:
    Notification -- Functions - Sales order - CreateSelection of Order Type.
    But I get following message:
    'Sales order creation is not possible for this notification type'
    The message says: No sales order type is assigned to the notification type.
    But I did not find any such configuration where I can assign notification type to Sales Order document type.
    Please help.
    regards

    Transaction OIM9
    Menu Path
    Customizing > Plant Maintenance and Customer Service > Maintenance and Service Processing > Maintenance and Service Notifications > Notification Creation > Notification Types > Define Order Types and Special Notification Parameters
    Nomally CS (customer service) area use this function.
    Regards
    Luke

  • Table type not defined for table control "T_CONTROL" (Custom table)

    Hi All,
    I m facing a problem in ITS mobile service.
    The Table control designed by me in R/3 (Module pool program) is
    not getting displayed in ITS mobile page.
    It is giving me an error "Table type not defined for table control "T_CONTROL" (Custom table) ".
    Can you please let me how this issue can be resolved.
    With Regards,
    Mahesh

    CONTROLS: table_ctr TYPE TABLEVIEW USING SCREEN '0010'.
    try using this....
    Regards
    Vasu

  • Rebate-Manual payment is not allowed for this agreement type

    Hi,
    While processing the Rebates, after the Sales cycle till Billing document, when i i try to process the partial settlement it is givin a message as "Manual payment is not allowed for this agreement type"
    could you please suggest.
    Regards
    AS

    Hi AS
    If you want to do manual payment then in VB)2 select the Agreement type and then in that agreement type check wheather Manual rebate order type has been assigned or not and Manual payment has been checked or not . If they are not maintained and Checked  then maintain the rebate document type and check the box Manual accruals and then you can do Manual Payment for that agreement
    Regards
    Srinath

  • Problem Instanciating BO - No default attribute defined for the object type

    Hello Experts,
    I am instanciating the BO BUS2038 to ZBUS2038 and when I click in u201Cto implementedu201D and follow u201Cto releasedu201D the message No default attribute defined for the object type is appearing!
    Can anybody help, please?

    Hello everyone,
    it appears to me, that no one has a clue about the "default attribute" and is widely guessing what can be done about that.
    I feel deeply sorry for that, Marcos.
    At first: You don't really need to care about the missing default attribute. If it's missing, the object's instance key will be used instead. Skip the warning message.
    Secondly: The default attribute is used to display the instance within the "Object links & Attachments" under the work item preview when using the SAP Business Workflow.
    Thirdly: You can select any existing attribute of your business object type to be the default attribute, by navigating to the "Basic data" (it's the heat-icon within the object builder), use tab "Defaults" and use the Input Help on the field "Attribute".
    There you'll go.
    Best wishes,
    Florin

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

  • Item category RENN is not defined for this item

    Hey SD experts,
    I've created a sales order with free of charge and standard items.
    Now, I'm trying to create a return order with reference to this sales order.
    I got this error message: Item category RENN is not defined for this item.
    I've checked in VOV4 : the combination Sales document type + Itemcategory group =>Itemcategory seems to be correct.
    Why am I getting this error message then ?
    Regards,
    Bahia.

    Dear Bahia,
    Check item level copy control settings between Sales order free of charge and Return sales order i.e copy control settings between free of charge order item category and returns order itemcategory.
    Once again check item category determination through VOV4 transaction for the combination of
    Your returns order document type+Itemcategory group-->RENN.
    I hope this will help you,
    Regards,
    Murali.

  • Cbs build portal application dc fail.  Build Plugin IS NOT DEFINED for this

    hi all
    I use NW7.0 ehp1,have portal and a nwdi.
    I create a track at nwdi . and develop a portal application .
    local build is ok . but when i check in .run a activitce.  dc is broken.
    log is -
    CBS Request Log - [  300/DEP_PESKM_D  ]
    Build number assigned: 314
    Change request state from QUEUED to PROCESSING
    REQUEST PROCESSING started at 2010-11-05 02:17:38.921 GMT
        ACTIVATION request in Build Space "DEP_PESKM_D" at Node ID: 13,975,650
         [id: 300; parentID: 0; type: 4]
         [options: NO OPTIONS]
        Waiting for access: 79 ms
        ===== Pre-Processing =====  started at 2010-11-05 02:17:39.000 GMT
            List of requested for activation activities:
                'deep.com_PESKM_1' compartment
                    tet
                        [ISN 111][created by YANLIANG at 2010-11-05 10:17:31.0][OID 6b2f604ae87c11df94ff000000d54062]
                There is 1 activity in compartment deep.com_PESKM_1
                1 activity will be processed by this request
            Analyze dependencies to predecessor activities... started at 2010-11-05 02:17:39.031 GMT
                Analyzing predecessors in compartment "deep.com_PESKM_1"
                    No dependencies to predecessor activities found.
            Analyze dependencies to predecessor activities... finished at 2010-11-05 02:17:39.046 GMT and took 15 ms
            Analyze versions... started at 2010-11-05 02:17:39.046 GMT
                List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2010-11-05 02:17:41.812 GMT and took 2 s 766 ms
                Synchronize metadata for [deep.com.cn/dc_logo_par] started at 2010-11-05 02:17:41.812 GMT
                    Verification of DL [ws/PESKM/deep.com_PESKM/dev/active/] finished at 2010-11-05 02:17:41.906 GMT and took 0 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2010-11-05 02:17:41.937 GMT and took 31 ms
                Synchronize metadata for [deep.com.cn/dc_logo_par] finished at 2010-11-05 02:17:41.937 GMT and took 125 ms
                < CHANGE > 'deep.com.cn/dc_logo_par' DC
            Analyze versions... finished at 2010-11-05 02:17:41.937 GMT and took 2 s 891 ms
            Analyze activities... started at 2010-11-05 02:17:41.937 GMT
                Loading component definitions
                1 component to be build in compartment "deep.com_PESKM_1"
            Analyze activities... finished at 2010-11-05 02:17:42.000 GMT and took 63 ms
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2010-11-05 02:17:42.109 GMT
                    'deep.com.cn/dc_logo_par' variant 'default'
                    'deep.com.cn/dc_logo_par' variant 'default' cannot be built. ACTIVATION will fail.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
            Analyze request DC BV... finished at 2010-11-05 02:17:42.140 GMT and took 31 ms
        ===== Pre-Processing =====  finished at 2010-11-05 02:17:42.187 GMT and took 3 s 187 ms
        Change request state from PROCESSING to FAILED
        Error! The following problem(s) occurred  during request processing:
        Error! The following error occurred during request processing:Activation failed due to component "deep.com.cn/dc_logo_par" variant "default". The component is BROKEN.
    REQUEST PROCESSING finished at 2010-11-05 02:17:42.187 GMT and took 3 s 266 ms
    No build logs available for the request.
    Edited by: yan liang on Nov 5, 2010 3:12 AM

    Hi Yan,
    please check the NWDI troubleshooting guide:
    http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CBS%29Q0030
    --> Understanding Broken and Dirty DCs
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30b7c94e-fc6b-2910-30b8-d34a7b51309e
    Did you import the dependent build plugins for the track in question?
    (tab "development" in the /devinf --> CMS webui --> Transport studio)
    See also the sap note: #1080927 - Creating CMS Tracks for Common Application Types (http://service.sap.com/sap/support/notes/1080927)
    Best Regards,
    Ervin

  • Build Plugin IS NOT DEFINED for this component or the defined Build Plugin

    Hello,
    we have upgraded our NWDI (nw04s) to SP13 and to DB2 V.9. We don't know if this has something to do with our problem. The NWDS developers called us. They can't activate the changes anymore. When I check the CBS I can see, that all components are broken. Any idea?
    REgards,
    Alexander
    Build number assigned: 487
    Change request state from QUEUED to PROCESSING
    REQUEST PROCESSING started at 2007-10-10 10:46:13.526 GMT
        BUILD request in Build Space "NW1_GPMS_D" at Node ID: 27,972,750
         [id: 473; parentID: 0; type: 2]
        Waiting for access: 33 ms
        ===== Pre-Processing =====  started at 2007-10-10 10:46:13.559 GMT
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2007-10-10 10:46:13.702 GMT
                    'zurich.com/gpms/jco_pool' variant 'default'
                    'zurich.com/gpms/jco_pool' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/yea' variant 'default'
                    'zurich.com/gpms/yea' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/chgpwd' variant 'default'
                    'zurich.com/gpms/chgpwd' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/rep' variant 'default'
                    'zurich.com/gpms/rep' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/model' variant 'default'
                    'zurich.com/gpms/model' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/idp' variant 'default'
                    'zurich.com/gpms/idp' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/ovt' variant 'default'
                    'zurich.com/gpms/ovt' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/arch' variant 'default'
                    'zurich.com/gpms/arch' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/myr' variant 'default'
                    'zurich.com/gpms/myr' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/div' variant 'default'
                    'zurich.com/gpms/div' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/ume' variant 'default'
                    'zurich.com/gpms/ume' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/com' variant 'default'
                    'zurich.com/gpms/com' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/ovw' variant 'default'
                    'zurich.com/gpms/ovw' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/obj' variant 'default'
                    'zurich.com/gpms/obj' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/chgpwdb' variant 'default'
                    'zurich.com/gpms/chgpwdb' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/pdata' variant 'default'
                    'zurich.com/gpms/pdata' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
            Analyze request DC BV... finished at 2007-10-10 10:46:14.049 GMT and took 347 ms
            Prepare build environment in the file system... started at 2007-10-10 10:46:14.049 GMT
                Synchronize development configuration... started at 2007-10-10 10:46:14.049 GMT
                Synchronize development configuration... finished at 2007-10-10 10:46:14.068 GMT and took 19 ms
                Synchronize used libraries... started at 2007-10-10 10:46:14.068 GMT
                Synchronize used libraries... finished at 2007-10-10 10:46:14.068 GMT and took 0 ms
            Prepare build environment in the file system... finished at 2007-10-10 10:46:14.068 GMT and took 19 ms
        ===== Pre-Processing =====  finished at 2007-10-10 10:46:14.069 GMT and took 510 ms
        Waiting for access: 3 ms
        ===== Processing =====  started at 2007-10-10 10:46:14.072 GMT
            No Components to be built.
            BUILD DCs
        ===== Processing =====  finished at 2007-10-10 10:46:17.407 GMT and took 3 s 335 ms
        ===== Post-Processing =====
        Waiting for access: 5 ms
        ===== Post-Processing =====  started at 2007-10-10 10:46:17.412 GMT
            STORE build results... started at 2007-10-10 10:46:17.413 GMT
                "zurich.com/gpms/jco_pool" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/jco_pool": store meta-data
                "zurich.com/gpms/jco_pool" in "default" variant  is PROCESSED
                "zurich.com/gpms/yea" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/yea": store meta-data
                "zurich.com/gpms/yea" in "default" variant  is PROCESSED
                "zurich.com/gpms/chgpwd" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/chgpwd": store meta-data
                "zurich.com/gpms/chgpwd" in "default" variant  is PROCESSED
                "zurich.com/gpms/rep" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/rep": store meta-data
                "zurich.com/gpms/rep" in "default" variant  is PROCESSED
                "zurich.com/gpms/model" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/model": store meta-data
                "zurich.com/gpms/model" in "default" variant  is PROCESSED
                "zurich.com/gpms/idp" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/idp": store meta-data
                "zurich.com/gpms/idp" in "default" variant  is PROCESSED
                "zurich.com/gpms/ovt" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/ovt": store meta-data
                "zurich.com/gpms/ovt" in "default" variant  is PROCESSED
                "zurich.com/gpms/arch" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/arch": store meta-data
                "zurich.com/gpms/arch" in "default" variant  is PROCESSED
                "zurich.com/gpms/myr" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/myr": store meta-data
                "zurich.com/gpms/myr" in "default" variant  is PROCESSED
                "zurich.com/gpms/div" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/div": store meta-data
                "zurich.com/gpms/div" in "default" variant  is PROCESSED
                "zurich.com/gpms/ume" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/ume": store meta-data
                "zurich.com/gpms/ume" in "default" variant  is PROCESSED
                "zurich.com/gpms/com" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/com": store meta-data
                "zurich.com/gpms/com" in "default" variant  is PROCESSED
                "zurich.com/gpms/ovw" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/ovw": store meta-data
                "zurich.com/gpms/ovw" in "default" variant  is PROCESSED
                "zurich.com/gpms/obj" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/obj": store meta-data
                "zurich.com/gpms/obj" in "default" variant  is PROCESSED
                "zurich.com/gpms/chgpwdb" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/chgpwdb": store meta-data
                "zurich.com/gpms/chgpwdb" in "default" variant  is PROCESSED
                "zurich.com/gpms/pdata" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/pdata": store meta-data
                "zurich.com/gpms/pdata" in "default" variant  is PROCESSED
            STORE build results... finished at 2007-10-10 10:46:17.440 GMT and took 27 ms
            Change request state from PROCESSING to SUCCEEDED
            Analyze effect of applied changes to buildspace state... started at 2007-10-10 10:46:17.440 GMT
                Skip check for build time dependency cycles. DC metadata is not changed.
                Determine components that have become DIRTY due to the results of this request started at 2007-10-10 10:46:18.601 GMT
                    No such components have been found.
                Determine components that have become DIRTY due to the results of this request finished at 2007-10-10 10:46:18.602 GMT and took 1 ms
                No Internal Build Requests are canceled by this request
            Analyze effect of applied changes to buildspace state... finished at 2007-10-10 10:46:18.642 GMT and took 1 s 202 ms
            Request SUCCEEDED
        ===== Post-Processing =====  finished at 2007-10-10 10:46:18.646 GMT and took 1 s 234 ms
    REQUEST PROCESSING finished at 2007-10-10 10:46:18.646 GMT and took 5 s 120 ms
        ===== Pre-Processing =====  started at 2007-10-10 07:16:55.069 GMT
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2007-10-10 07:16:55.104 GMT
                    'zurich.com/gpms/jco_pool' variant 'default'
                    'zurich.com/gpms/jco_pool' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/yea' variant 'default'

    Here are some things to have a look at:
    - Check your SC definitions and their Usage Dependencies in the SLD
    - Check that the basis SCA's have been imported into the track. You can quickly see this by having a look at the total nr of DCs for these SCs in CBS.

  • Shipping Point is not defined for this transaction

    Dear All,
    I have a question in creating new shipping point.
    Scenario:
    1. Created new shipping point and assigned it to plant.
    2. Maintain Shipping Point determination.
    When ever create a sales order, when i enter the new shipping point I hit this error.
    "Shipping Point is not defined for this transaction". What else is there to check. Please advise.

    Hope you have done intial trouble shooting,
    i.e. Combination of Shipping Point Determination=
    Loading Group - (1-Material Master Record)
    Shipping COnditions (1- Sales doc type , 2- Customer Master Data - Sold to Party)
    Delivering Plant - (1-Customer Material Info record , 2- Customer Master Record & 3-material master record)
    if system finds the above combination, SHipping Point will be determined.
    I hope you have done Copy of existing Shipping Point & renamed it. Then all the shippig Point determination Combinations will be copied. if not, you have to maintain manually in Shipping point determination customization.
    re-check n revert

  • Message no. V1321 - Item category ALES is not defined for this item

    Hi,
    I am trying to use ALES - Item Category for creation of the Sales Order. But i am getting this eerror message as Item category ALES is not defined for this item. Please let me know the config changes that i need to do to use this Item Category.
    Thanks in Advance !!

    To maintain the item category for a sales order type first you have to assign the item category in SPRO.
    SPRO>Sales & Distribution>Sales>Sales Documents>Sales Document Item>Assign item categories.
    In the screen Change view Item category assignement:overview screen
    select your sales document type + ItemcategorygroupUsageHigherLevel Item category
    Then you have to maintain Default item category and Manual item category.
    Default item category will be proposed by the system when you enter a material in sales order. You can change the item category to any one of the manual item category maintained above.
    For e.g.: You are creating a thrid party sales order. Default item category is TAN, if manual item category is maintained as TAS for this combination of sales document type + ItemcategorygroupUsageHigherLevel Item category and then system will allow you to change item category to TAS. If this is not maintained then system will give you an error as"Item category TAS is not defined for this item".
    Again depending the item category further acitivites will be carried in SAP, like in third party item (TAS) PR screen will be displayed.
    Thanks,
    Sarvesh Desai
    Edited by: Sarvesh DeSai on Jan 11, 2012 7:08 AM

  • 'Item category SUBC is not defined for this item'

    Hi,
    When i tried to create an SO with item category SUBC, the system pop-up this error msg: 'Item cateogry SUBC is not defined for this item'
    Please let me know what should i do?  Thank you.
    I've maintained the item category assignment with same item category group maintained in material master data..But it still not work...

    Dear Laa,
    This is due to not done the itemcategory definition and determination.So
    First you define the itemcategory  SUBC through VOV7 transaction (By copying standard TAN)
    Then do the itemcategory determination through VOV4 transaction for this combination
    Sales document type+Itemcategory group--->Itemcategory
    Itemcategory group is different from itemcategory.
    Itemcategory group maintained in the Material master data
    The item categroy will get determine in the sales order based on Sales document type+Itemcategory group
    I hope this will help you,
    Regards,
    Murali.

  • Item category IRIN is not defined for this material

    Hi,
    When creating Sales Order, I assign a service material with Material Type DIEN , System gives me error as
    "Item category IRIN is not defined for this item."
    I want to know where and how is the link between Item Category and Material is maintained
    Thanks in advance.
    Regards,
    Nitin

    hi
    i am not a expert , based on my knowledge system will determine the item category for line item , based on  vov4 , here you will give the
    sales document typeitem category groupusage+higher level item= default item category
                  or                +            leis               +  sein  + enter over item= irin
    this is for determination ,
    in the material master  you will check the item category group , sale view tab 1, 2,  and also basic data.
    based on this will take , line item , item category . so sales view and basic data view item category group are same , other wise system sows this is error message ,
    please check this
    regards
    sankar

  • Err in PO creation-Sales document item is not defined for this transaction

    Dear Consultants the errror  occurs when we process  Individual Purchase Order scenario.
    Err in PO creation-Sales document item is not defined for this transaction  
    Thanks&Regards,
    SanthaRam

    This error because the item category is not determined correctly in the sales order.
    Check the item category in Sales order line item, for Individual Purchase order scenario its TAB.
    If its not TAB, then check the assignement for Item category in VOV4.
    This thread is more of the SD part, so also put it in SD forum for better solutions.
    Regards,
    Sheetal

  • The requested action is not supported for this object. [message 131-171]

    Hi,
    One user is having the below error message appear when she attempts to print remittances. This has only started happening since yesterday and all other documents are still printing.
    "The requested action is not supported for this object. [message 131-171]"
    Any ideas what could be the problem?
    Regards,
    Mohan

    Hi Johnson,
    I have not tried your suggestion till now as I am waiting for the database copy from my client.
    Just a quick question, As I already mentioned earlier and I also keep getting the issues from the users reporting that the user's get this error only if they print 'remittance advise reports' has multiple invoices.
    The report prints fine if it has single invoice even if it is a check payment.
    Will your suggestions address this as well?
    Regards,
    Mohan

Maybe you are looking for