Valuatin type not maintained

Dear Experts,
I am creating a po,the material is domestic spares excisable i.eDOM-S(E).valuation categarised as H.while saving  purchase prder the system is displaying warning message as "valuation data for material xxxxxxxxx valuation type DOM-S(E) not maintained.why message is showing.what i can do ,to rectify the warning.please answer it.
Regards,
Ramakrishna

Hi,
Just check the material in the display mode T Code MM03, whether any Valuation type is maintained for this material . Check the valuation class/Price control/Procurement type  also. Eg  If it is Raw material then whatever valuation type defined in your company has to be given and procurement type -External has to be selected.  After getting the correct valuation type u can go to T Code. MM01 and put the same material . Then it will ask for plant , storage location , valuation type , u can just put the particular valuation type. Select the views u want to maintain and then keep on entering and save it.
Go to  PO , same valuation type has to be given..it will show a 'X' mark against that particular valuation type if u press F4. (Eg.  x - Lcxin    where Lcxin is valuatiopn type)
If its not appearing that means its still not assigned to that material . Then u have to again check in MM03.
resgards,
somu c

Similar Messages

  • CONTROL DATA FOR ACTIVITY TYPE NOT MAINTAINED

    dear all
    i get this error when calculating production order cost
    control data for activity type 1000\4230\1420 not maintained for fiscal year 2007
    i hv maintained data in kp26
    can any one pl help. i am learnign sap pp and hv 4.7 version
    thanks and regards

    Dear Anshuman
    my prob. started during cost cal. in prod. order first error was version 0 not maintained for fiscal year 2007, THEN i maintained it in the path as told by you T code OKEQ.
    but after that error changed to CONTROL DATA FOR ACTIVITY TYPE NOT MAINTAINED ( 1000/4230/1420)
    i maintained data in kp26, but the error is still coming
    pl. suggest some solution as i am not able to proceed further.
    Thanks and regards
    Raj

  • Recipient type not maintained in Vendor master  During TDS deduction

    Hello Gurus,
    My client Posted somany Documents deducting TDS, but  during deduction  time all other vendor masters (except one or vendors) were not maintained with Recipient type. due to this system has taken posting date as due date for challan payment.
    for example if the document was posted on 10 Oct 2009, system showing due date as 10 Oct 2009 in t Code J1INMIS ( challan update tab). Documets pertaining to those vendors maintained with Recipient type is correctly showing due date as 06 Nov 2009.
    now when i want to make challan in J1INCHLN documets pertaing to the correct vendors are being up by the system. but other line items are not picked up..
    how to solve this problem >?//
    Please advise..
    Mamillapalli V

    No i thought  so,, but system picked up the posting date as due date. this happend only for those vendors in whose vendor masters the recipient type was not maintained.
    For two three vendors where Recipient type was maintained those TDS line items due date is correctly showing as 06 Nov 2009. this iam telling for the same TAX TYPE (ex. IE.).
    now, these few  line items are only displayed in J1INCHLN. the input i have given is
    Posting date 01 Oct 2009 to 31 Oct 2009
    Section - 194C
    iam still not convinced, Please advice..
    Thanks in advance

  • Object type not maintained for message type

    Hi,
    I am working on chnage pointers for Vendor classification data. when I execute the program RBDMIDOC (BD21) I get the error Object type LIFNR not maintained for Message type.
    If anyone has worked on change pointers, please guide me in solving this error.
    Thanks
    Hari

    Hi
    Which msg type u r using there.
    Regads,
    Prasad.

  • Error inALE service (Segment type not maintained in Message type) status:29

    Hi all,
    Need your help.
    I have a added the a segment to the message type and which is linked in WE82( Message type:Debmas,basic type:debmas06 and extensionZxxx). And the segment is also set for release.It is an outbound senario. When i process it manually in WE19 using the basic type with the enhancement and via message type (with the message type and the extended type) I can process the idoc and the segment whic i have added with the following fields are displayed. But when i post the customer in BD12 with the message type I am getting the error in BD87 as " error in ale service Segment type ZXXX does not exist in message type DEBMAS".
    PLease do the needful. Its since 2 days I am struck with the same and was trying but I could not get any. Hope you guys might help me.
    Anything else to be refreshed or anything else to be done except we31.we30, we81
    Thanks in advance.
    Edited by: Farhy Farhy on Aug 2, 2010 12:29 PM

    Thanks for your reply Mr. Das.
    I have tried all the things and did not find any solution..
    Posted after checking all the things and the procedure. I did not write any custom program. Earlier I created the extension type and deleted and created the new extension type. But now it is taking the same old extension type and giving the error as the extension type is not maintained in the message type.
    I have deleted the old extension type completely but the old is onle getting reflected. Anything to be done to refresh.
    Waiting for the reply.

  • Metadata EDISDEF not maintained  - Idoc adapter error

    hi,
    In our scenario, SenderParty->XI->R/3, we are using custom idoc to post into R/3. The idoc adapter throws an error, Metadata EDISDEF for port SAPXXX, IDoc type ZKAGXXX and CIM type not maintained, but when i use standard idoc, i don't get this error. We even applied oss note 837595 to fix authorization issue, but it didn't help.
    Any ideas or suggestions.
    Thanks
    Pandari

    One LAST suggestion.  Looking at Note 837595, it doesn't seem to specify a value for authorization group (DICBERCLS).  Try authorization group 'SS' (without quotes).  So:
    Object: S_TABU_DIS
    Activity: 03
    Auth. Group: SS
    I recall now that a customer recently had this issue and (for them), this helped.
    Jin

  • Error Message : Condition type is not maintained in the schema RM0002

    HI Gurus,
    I have created a new purchasing procedure as follows.
    ZVATV : <b>Condition Schema</b>
    VATV  : <b>Condition Type</b>
    VA : <b>Sch.Grp Vndr</b>
    When I create the Purchase order, the above mentioned schema, ZVATV is automatically determined.
    But when I create Contract, system throws an error message saying condition type VATV is not maintained in the schema RM0002.
    I am very new to SAP, Kindly explain in very detail about this error message and ways to get rid of it.
    If u have got any <b>very detailed material</b> about pricing kindly forward it to my mail id: [email protected]
    Thanks in advance.
    ~Gokul.

    Hi,
    The new condition type you are specifing is the gross price condition (PB00). for PB00 condition type a supplementary pricing procedure is assigned as RM0002. u may have copied the PB00 and changed it to VATV, but with out changing the RM0002. copy the RM0002 and in that also change the PB00 to VATV. after this go to VATV condition type control data (M/06) and assign the new supplementary pricing procedure instead of RM0002.
    The supplementary pricing procedure is required to have the condition types for which no access seqeunce is mentioned. All the condition types in main pricing procedure with out access sequence needs to be mentioned in supplementary pricing procedure.therefore all these condition types will have the same validity periods as PB00.
    Regards,
    Ramakrishna

  • Legal Control : Document Type Mapping not Maintained

    Getting an error SAP GTS :Legal Control : Document Type Mapping not Maintained ,while creating order in feeder system .
    I checked the configuration maintained SAP Global Trade ServicesSAP Compliance ManagementGeneral SettingsDocument StructureAssignment of Document Types from Feeder Systems-Assign Document Type at Feeder System Group Level
    Similarly I checked for item category.
    Please let me know what further configuration have to be maintained for correcting the error.
    Thanks & Regards

    Hi,
    The document type mapping is required in R/3 system too. You have to maiatain order type say OR/TA in R/3  below path
    IMG--> Sales and Distribution --> Foreign Trade/Customs --> SAP Global Trade Services - Plug-In --> Control Data for Transfer to SAP Global Trade Services --> Configure Control Settings for Document Transfer --> SDOA.
    Note: If you maintain OR in R/3, you will have to maintain same in GTS. if you maintain TA in R/3, same maintain in GTS.
    Regards,
    Lakshmikanth

  • Error : Inspection type not properly maintained

    Hi Experts,
    I am trying to perform MB1B for a material and its giving me an error ...." Error : Inspection type not properly maintained" any suggestions would be appreciated...
    Regards
    Albert

    Hi
    Check the material master Quality management view where the inspection type is maintained.
    Check the settings for inspection type in that material master.
    Regards
    Prasad

  • Fiscal year variant Z1 is not maintained for calendar year 2012 when loadin

    Dear Experts,
    We are working on BI7.0 extracting data from ECC 6.0.
    I am trying to load data from 0HR_PY_PP_1 which is a Self DataSource in our BW System (extracts data from 0EMPLOYEE and 0PERSON) to load into ZPA_C50 which is a copy of BCT InfoCube 0PAPA_C02 (Headcount).
    The data has come through into the PSA very well.
    However, DTP is throwing an error while loading 32242 records of data from PSA into ZPA_C50 InfoCube. The error details as below:
    Error while updating to target ZPA_C50 (type INFOCUBE)
    Fiscal year variant Z1 is not maintained for calendar year 2012     FGV     2
    Messages for 1 data records saved; request is red acc. to configuration
    Processing Terminated
    We are actually doing a Re-implementation of BW 3.0b in BI 7.0 Ehp1. We have imported Maintenance of Fiscal Year Variant from the BW 3.0b Production System. So this shouldn't be a problem I guess since I have also checked the setting in SPRO in BI 7.0 Development (New) System and they are looking good.
    Also, when I do a Filter on 0CALDAY in DTP from 01.01.1900 to 31.12.2010, the loads are working fine. I want the load to run without any Filters on 0CALDAY.
    Has anyone been in similar situation. How did you resolve this issue? Your time is very much appreciated.
    Thanks in advance.
    Chandu

    Dear Experts
    Thanks for your time.
    We have resolved this issue ourselves. We have maintained 'Shortened Fiscal Years' for 'Z1' and it is working fine now. Steps are as below:
    In BI Dev System -> SPRO -> SAP Reference IMG -> SAP Customizing Implementation Guide -> SAP NetWeaver -> Business Intelligence -> General BI Settings -> Maintain fiscal year variant -> Select 'Z1' Fiscal Year Variant and then DoubleClick on 'Shortened Fiscal Years' to set the Fisc Year Variant -> Save.
    The dataload should work fine now.
    Cheers,
    Chandu

  • VA00 condition type not getting determined for the returns order

    Hi All,
    I have a case where VA00 condition type not getting determined for the returns order that has been created with respect to the billing document.
    When the pricing conditions are being copied from invoice it is getting copied but later it is getting deleted in the include LV61AA42.
    Note:VA00 condition type is getting deleted from the  internal table tkomv[].
    If any one came across  this scenario can you please help me.
    Request your valuable inputs

    Hi,
    Please check the copy control setting in VTAA.
    Maintain the pricing type as "D" at item category level for the respective document type .
    Hope this will resolve your issue.
    Regards,
    Krishna O

  • Profit Center was not maintained during order n billing creation.

    Dear, Gurus
    I'm facing a problem of Profit Center. User created a service material, maintenance contract. They created a Billing Document as it is order related billing. Accounting document was not generated when saving invoice. When I got to the bottom of this I realized no costing tabs were ever maintained for material type services. (Henceforth no Profit Center in Sales Order n Invoice).
    I have done the necessary config n assignments but question now is what should I do as in billing doc  the field is greyed out it will not allow me to assign Pr Center now. I am thinking that this may work if I cancel the billing document and then go back to sales order and try and changing the field, then re-create the invoice. I'm trying to avoid canceling. Is there any program, bapi, user exit I may use to re assign or make system re check the MM while saving invoice to allow accounting document to be created?  This is one scenario.
    2nd scenario is similar but in the case of this contract everything was made. Accounting document was cleared even but with some dummy weird Profit Center. (No proft center in Order nor invoice.) Whole problem at first in this scenario is User saying everything is complete so status in doc flow should show maintenance contract as complete but wasn't. it showed being processed. I discovered no completion rule was maintained. I maintained E Full target value referenced but status still has not changed any idea guys? (New config not showing on old existing data only show on new document, concept?) Is there a program or anything to make system update status doc flow? aside from this Profit center  incompletion log is coming in Contract. Not maintained in order or invoice.

    In one of my earlier projects, a similar requirement was putforth by users and we had developed a zee tcode to change the profit center in billing document via SM30 which can be done only by FI authorised users.
    I am reproducing the said program as under:-
    REPORT  "ZPROFIT_CHG"
    TABLES : VBRP.
    SELECTION-SCREEN : BEGIN OF BLOCK B1 WITH FRAME.
    SELECT-OPTIONS : SO_VBELN FOR VBRP-VBELN OBLIGATORY.
    PARAMETERS:      P_PRO LIKE VBRP-PRCTR OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK B1.
    DATA : BEGIN OF IT_VBRP OCCURS 0,
            VBELN LIKE VBRP-VBELN,
            POSNR LIKE VBRP-POSNR,
            PRCTR LIKE VBRP-PRCTR,
          END OF IT_VBRP.
    DATA COUNT(3).
    DATA W_MESSAGE(30).
    START-OF-SELECTION.
      LOOP AT SO_VBELN.
           IF SO_VBELN-LOW CA '~`!@#$%^&*()_+|\=-><,.;":' OR SO_VBELN-HIGH CA '~`!@#$%^&*()_+|\=-><,.;":'.
               MESSAGE 'Special character not allowed' type 'S'.
               LEAVE LIST-PROCESSING.
               STOP.
           ENDIF.
      ENDLOOP.
      IF P_PRO CA '~`!@#$%^&*()_+|\=-><,.;":'.
               MESSAGE 'Special character not allowed' type 'S'.
               LEAVE LIST-PROCESSING.
               STOP.
      ENDIF.
      SELECT B~VBELN B~POSNR B~PRCTR FROM VBRK AS A  INNER JOIN VBRP AS B ON A~VBELN EQ B~VBELN INTO CORRESPONDING FIELDS OF TABLE IT_VBRP
                                WHERE A~VBELN IN SO_VBELN
                                AND   A~FKART EQ 'ZFF2'
                                AND   A~FKSTO NE 'X'.
      IF SY-DBCNT EQ 0.
          MESSAGE 'NO DATA FOUND' TYPE 'S'.
          LEAVE LIST-PROCESSING.
      ENDIF.
      SORT IT_VBRP BY VBELN.
      DELETE ADJACENT DUPLICATES FROM IT_VBRP COMPARING VBELN.
      CLEAR COUNT.
      IF IT_VBRP[] IS NOT INITIAL AND P_PRO IS NOT INITIAL..
          LOOP AT IT_VBRP.
              UPDATE VBRP SET PRCTR = P_PRO  WHERE VBELN = IT_VBRP-VBELN AND POSNR = IT_VBRP-POSNR.
              IF SY-SUBRC = 0.
                 COUNT = COUNT + 1.
              ENDIF.
              COMMIT WORK.
              CLEAR IT_VBRP.
          ENDLOOP.
    ENDIF.
    IF COUNT IS NOT INITIAL.
        CONCATENATE 'No Of Records Updated Is - ' COUNT INTO W_MESSAGE.
        MESSAGE I000(ZSFL) WITH W_MESSAGE.
    ELSE.
        MESSAGE 'No Records Updated' TYPE 'S'.
    ENDIF.
    Since I am so weak in ABAP coding, not sure whether the above coding is correct.  You need to check with your ABAPers and develop this logic.  This should work.
    thanks
    G. Lakshmipathi

  • 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

  • Message no. AK005 - Asset is investment measure, transaction type not allow

    Dear All,
    I am getting following error while transfering Investment AuC to Main Asset.
    Message no. AK005 - Asset is investment measure, transaction type not allow
    I searched the Forum and got some input.., but in that I have a clarification.
    Please see my doubt and the forum input.
    Internal Order as Investment Measure:
    Can you explain me Step 10. Settle the amounts to Main Asset from AuC(Prcg type: Full) - KO88 once again.
    How we can give the Receiver Main Asset master in KO88. In KO88 we can only provide the Internal Order. But that Internal Order is already settled to AuC in Step 8.
    Please guide me.
    Thanks.
    Regards,
    nms
    Re: Settlement of cost center to final asset ?
    Posted: Oct 27, 2009 11:40 AM
    Hi,
    Are you doing any settlement using the AUC asset ?
    Normal practice is to Create an Auc Asset and settle cost to Auc. Once the asset is ready for use, finally settle the Auc to final asset.
    This can be done in two ways like - line item settlement / investment measure.
    Below are steps in two scenarios :
    Internal Order as Investment Measure:
    1. Define the AuC Asset Class (with investment measure) - OAOA
    2. Define the Asset Class u2013 for Main Asset - OAOA
    3. Define Investment Profile - OITA
    a. Assign the AuC Asset Class (Step-1) in the investment profile
    4. Assign Investment Profile to Model Order - OITA
    5. Define Order Type (Investment) - KOT2
    a. Settlement Profile - OKO7
    b. Maintain Allocation Structures - OKO6
    c. Planning Profile - OKOS
    d. Budget Profile - OKOB
    6. Create an Internal Order - KO01
    a. With the Investment Profile (Step-2)
    b. AuC automatically created by the system using Asset Class given in the Investment Profile
    7. Post the amounts to IO - FB01
    8. Settle the amounts to AuC from IO (Prcg type: Automatic) - KO88
    9. Create the Main Asset - AS01
    10. Settle the amounts to Main Asset from AuC(Prcg type: Full) - KO88
    AuC using Line Item Settlement:
    1. Define the AuC Asset Class (with Line Item Settlement) - OAOA
    2. Define the Asset Class u2013 for Main Asset - OAOA
    3. Define Order Type (Overhead) - KOT2
    4. Create an AuC-Asset (using Step-1 Asset Class) - AS01
    5. Create an Internal Order - KO01
    a. Assign the AuC u2013 Asset in Settlement Rule in IO
    6. Post the amounts to IO - FB01
    7. Settle the amounts to AuC from IO - KO88
    8. Create Main Asset (using Step-2 Asset Class) - AS01
    9. Assign the Main Asset in IO (Step-5) - KO02
    10. Settlement AuC u2013 Line Item List - AIAB
    11. Settlement AuC - Receiver - AIBU
    VVR

    nms,
    Your message is not very clear - while you have mentioned at what stage are you getting the above-mentioned error message, you haven't mentioned exactly what you were trying to do. The fact that you are getting this error is a straight-forward indication that you are attempting to do something that SAP does expect.
    However, answering your query about how to use KO88, you have to settle the AuC to a FA (fixed asset, with asset class other than AuC ), as that will close the open AuC, transfer the value from the AuC to the FA and from this point onwards, all transactions will happen to this FA. Your statement "in KO88, we can only provide the Internal Order" is incorrect.
    Hope this helps.
    Regards
    Gulshan

  • Getting error logical file name not maintained adequtely

    Hi,
    when i execute a z report and press the download botton getting error logical file name not maintained adequtely,see long text.
    Below code i wriien. Please somebody help..
        DATA: lt_rows TYPE lvc_t_row.
        CASE e_ucomm.
          WHEN 'DOWNL'.
    Determine and construct OS specific file name                        *
            PERFORM get_file_name_for_os.
    in the  above perform , i wriien
    FORM build_file_name USING pf_os
                               pf_with_file_extension
                               pf_param_1
                               pf_format
                               pf_fname.
      DATA: lf_para1(20) TYPE c.
    pf_param_1 hold the materialnr with leading zeros not prefered in    *
    download file name                                                   *
      WRITE pf_param_1 TO lf_para1.
      CALL FUNCTION 'FILE_GET_NAME'
        EXPORTING
      CLIENT                        = SY-MANDT
          logical_filename              = 'Z_MATERIAL_BOM_FILE'
          operating_system              = pf_os
          parameter_1                   = lf_para1
      PARAMETER_2                   = ' '
      PARAMETER_3                   = ' '
      USE_PRESENTATION_SERVER       = ' '
          with_file_extension           = pf_with_file_extension
      USE_BUFFER                    = ' '
        IMPORTING
      EMERGENCY_FLAG                =
        file_format                   = pf_format
        file_name                     = pf_fname
    EXCEPTIONS
       file_not_found                = 1
       OTHERS                        = 2
    Error handling.
      CASE sy-subrc.
        WHEN '1'.
          MESSAGE e014(ba) WITH 'Z_MATERIAL_BOM_FILE'.                     "error message i am getting      LEAVE.
        WHEN '2'.
          MESSAGE e213(ky) WITH 'Z_MATERIAL_BOM_FILE'.
          LEAVE.
      ENDCASE.

    Hi.
    In file txn,
    click on "Logical File Name Definition, Cross-Client" from the left.
    Then click position and check for your logical file name.
    If you dont get it, it means you need to create it. You can click on New Entries to create.
    Thanks
    Mani

Maybe you are looking for