Delivery Type cannot be determined in subcontracting

Hi All,
I am getting the msg as
Del type (Del Category for MAterial 1623 and BWART) cannot be determined in SAP
Message no. VL295.
Delivery has been saved
Delivery type was not transmitted
While doing delivery creation in ME20, I got theses messages.
How to get delivery type, delivery category, material and mvt type
combination.
Can anyone help me?
Thanks
Keerthi

Hi Jurgen,
Thanks for ur inputs.
The customer master has got the sales information.
I found the problem now. For the Raw Material, I am not getting the views of Sales Data:
--> Sales Org Data 1
--> Sales Org Data 2
--> Sales : General / Plant Data.
All these views r not found for the material created using the material type ROH.
Please let me know about this.
Thanks

Similar Messages

  • Customs document type cannot be determined for external document Type F8

    Hello Experts
    Need help
    I am trying to transfer F8 to GTS 10.1 and getting following message in GTS  Transfer log for export:
    Customs document type cannot be determined for external document Type F8
    New implementation
    GTS 10.1 running with SP 12
    ECC side Plug-In settings are fine. BAdi is Active.(There is no document mapping for F8/CUSDEC as it is not required in 10.1)
    GTS side configurations are also fine. Checked several times by 4 sets of eyes!!
    (Include general settings configurations, Customs communication configurations:)
    (Defining technical medium, conditions/output parameters, defining messages for communication process,
    defining determination for activity sequence and control settings for communication process)
    Despite this I am not able to trnasfer F8 successfully
    Can someone throw some light on this issue please?
    Keshav Murthy
    [email protected]

    Hi Dhilipan
    Here we go..
    You asked me to check the following
    Please check following things
    1) Legal regulation is activated. - Yes Activated
    2) Process template assigned to the legal regulation - Yes Assigned
    3) Activity Sequence determination - Yes done
    4) Open the activity sequence in under Control settings for Communication processes and check if there is a document type assigned to it. Table- /SAPSLL/TLEPAF - Yes done.
    It is really puzzling.
    Thanks
    Keshav Murthy

  • BAPI_GOODSMVT_CREATE Dlv. type cannot be determined

    Hello experts,
    I trying to perform a post goods receipt with a PO using BAPI 'bapi_goodsmvt_create' (I want to simulate a MB01, I use gm_code = 01 in the bapi). I have the following error message:
    Dlv. type (dlv. catgry  for mat. 704A46220023 and BWART 101) cannot be determined (message id = VL and message number = 295).
    Do you have any idea where it comes from? I am quite new in ABAP and I am a bit lost with this message.
    Thanks in advance for your help.
    Lionel

    Hi Lionel,
    don't worry!
    Maybe the material is not enabled on this plant?
    Did you try to book the Goods receipt in Transaction MIGO?
    If you want to book it the same way the Transaction does you can make a breakpoint at "call function bapi goodsmvt_create" in Debugger mode and save/copy the data to se37.
    In se37 you can test all the different values.
    To undo the booking of 101 try 102 later on for tests.
    Maybe also SAPNOTE 540185 can help you for the current Topic.
    https://websmp230.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D35343031383526http://
    BR
    Bernhard

  • Delivery type determination

    Hi Experts,
    Need to understand the logic as to how the delivery type is getting determined whenever we create a delivery against a purchase order .
    If we have created Z delivery types how system picks up the delivery type .
    Thanks
    Jimmi

    Hi,
    You can go through the link
    1. ) SPRO -
    >  Materials Management -
    > Purchasing -
    >  Purchase Order -
    >  Define Document type
    2. ) SPRO -
    >  Materials Management -
    > Purchasing -
    > Purchase Order -
    > Set Up Stock Transport Order -
    >  Assign Delivery Type & Checking rule
    3. SPRO ---> Materials Management --> Purchasing --- >Purchase Order -
    > Set Up Stock Transport Order -
    > Assign Document type, One step Procedure, Under Delivery Tolerance.
    hope you will get idea..

  • Delivery type mapping

    Hi
    We create a stock transfer order and process a outbound delivery with a delivery type say Z10.
    Against the outbound delivery we process a inbound delivery thru MIGO > Goods Receipt > outbound delivery , which post goods receipt with a inbound delivery
    In the inbound delivery the delivery type is say HID,
    Now I am trying to find out where does system pick delivery type 'HID' against 'Z10'
    Can I get some help on this please
    Regards
    Prakash.G
    +4550310479

    Hi,
    Delivery Type Z10 is determined from SPRO > MM . Purchasing > Purchase Order > Set up Stock Transport Order > Assign Delivery Type and Checking Rule
    And Delivery Type HID is determined from SPRO > MM . Purchasing > Confirmations > Define Internal Confirmation Categories & Set Up Confirmation Control

  • Dlv. type (dlv. catgry  for mat. 80001278 and BWART 553) cannot be determin

    We have handling unit managed FG material. When we try to do scrap stock posting from QA11 transaction we are getting following error message. It is difficult to understand. Can you help?
    Message no. VL295
    Dlv. type (dlv. catgry  for mat. & and BWART 553) cannot be determined
    Reply appreciated.
    Edited by: Tom_Eric on Jun 15, 2011 7:13 PM

    1.Check the delivery category for movement type 553
    SPRO > Logistics - General > Handling Unit Management > Basics > Materials Management > Inventory Management > Set QM Check and Delivery Type for Each Movement Type
    2.Check the delivery type for category
    SPRO > Logistics - General > Handling Unit Management > Basics > Delivery > Delivery Type Determination
    I would suggest you ask your MM team about this.
    Regards
    Luke

  • Dlv. type (dlv. catgry  for mat. 1133 and BWART ) cannot be determined

    Hi,
    Am getting the error while doing the transaction me2o the error is like this"Dlv. type (dlv. catgry  for mat. 1133 and BWART ) cannot be determined"
    Message no. VL295
       please help me on this

    as per the error it seems that system is not able to find the relevant delivery item category for the document type of delivery
    Please check the configuration for it. GO to IMG>LE>Shipping>

  • Dlv. type (dlv. catgry for mat. and BWART 601 ) cannot be determined.

    Issue : Error msg VL 295 Dlv. type (dlv. catgry for mat. and BWART 601 ) cannot be determined.
    We do have an automated process and in which we have a defined output type(zdlp).Which is supposed to perform the following:
    Output type: O/b delv & GI for PO
    Processing log for program ZSXXU01_NAST_AUTOMATION routine Z_SXX_CREATE_DL_AND_GI_FOR_PO
    Adding automation fn. Z_SXX_CREATE_DL_AND_GI_FOR_PO to list of processes to run against do
    Automation Start: Z_SXX_CREATE_DL_AND_GI_FOR_PO 20101104 191525
    Purchasing document 4500991256 identified.
    Our reference document 4500991255 identified.
    Delivery 0085982639 created.
    Replen.Cross-company 85982639 has been saved
    Material document 4916887062 / 2010 created.
    Processing step completed normally
    but sometimes it fails in the middle as follows:
    Object 491716968320100002
    Output type: O/b delv & GI for PO
    Processing log for program ZSXXU01_NAST_AUTOMATION routine Z_SXX_CREATE_DL_AND_GI_FOR_PO
    Adding automation fn. Z_SXX_CREATE_DL_AND_GI_FOR_PO to list of processes to run against do
    Automation Start: Z_SXX_CREATE_DL_AND_GI_FOR_PO 20101104 103729
    Purchasing document 4500995625 identified.
    Our reference document 4500995623 identified.
    Dlv. type (dlv. catgry  for mat.  and BWART ) cannot be determined
    Dlv. type (dlv. catgry  for mat.  and BWART ) cannot be determined
    Delivery type was not transmitted
    Delivery type was not transmitted
    Error creating delivery for ref.doc. 4500995623.
    Processing step completed abnormally
    but when we process it manually it works.Please help getting a permanent fix

    Thank you very much Eduardo!
    I've checked in NAST and i dont find the entry of any of the failed documents.Could you please eloborate on your explanation.As your example is with the print output type, its unclear.
    Also what could be the possible reason that it fails then and there and it works fine when we retrigger it.For the same material,plant and company code it fails sometimes and works well sometimes without any error.Which means all the settings and configurations are fine..right?
    Thank you in advance.

  • Delivery type determination in case of returns to vendor without return PO

    Hello Gurus,
    When we create Return PO, and when we want to created delivery for this PO , we assign delivery type RL to the PO in SPRO.
    Now when I return the material thorugh MIGO (without return PO) with delivery check box active, system determines different delivery type than RL. My question is that where do we assign this delivery type and how the system determines this delivery type in case of returns to vendor without return PO.
    Thanks
    Pravin

    Control parameters at movement type level determine the delivery type created. I guess you are using MvT 161. Try configuring delivery category for MvT 161 in OMJJ.
    Hope this helps.
    Rajiv..

  • Delivery type LR cannot be invoiced with billing type RE?

    Hi,
    I am refering below flow to create an return order, but face an error when creating credit billing document:
    ret sale order(RE)-ret delivery(LR)-post goods receipt(stock will be restored in corresponding storage loc)---credit for return(RE)
    Error msg: " Delivery type LR cannot be invoiced with billing type RE;
    Check the table entries for the copying control of billing
    documents and add the missing entries as necessary.
    Make the appropriate settings in Customizing if you have
    the authorization to do so."
    So i guess i might need maintain corresponding copying control for 'delivery document to billing document'...As the source order type is LR, and target order type is RE...I checked SPRO and found there are below inputs needed.  May i know what kind of data should be inputed normally??
    "Copying requirements
    Determ.export data
    Assignment Number
    Reference number"
    Thank you very much!!

    Hi
      In standard SAP credit memo for sale returns with refrence to return order only. (RE). Thats why you are getting this error. If your requirement is to refer the delivery quantity for the credit memo then you can do any one of the following
    1. Change the copy control setting for Return order to Credit memo.
        Go to VTFA transaction and select your return order type (RE) and Credit memo type (RE) and go to item category level and select your returns item category (REN) and change the billing quantity to 'D' -Delivery quantity.
        Now create your credit note with reference to your returns sale order. (not delivery). Onlly delivered quantity will be copied to the credit memo.
    2. If you want to create return credit memo with reference to your return delivery then follow the first two guy's reply. Also you have to do one more setting at your return order document type (RE).
       Go to VOV8 and enter ur return order type and go to details then enter the return credit memo type in the delivery related billing field. (FKARV) in the billing section.
    Regards
    Shiva

  • How movement type will be determined in Delivery without reference order

    hi gurus,
    i want to know what movement type will be determined in delivery type LO(Without reference of order) . i think in a normal delivery with referance to sales order movement type will be taken from the sales order schedule lines.  Incase of delivery without referencing an order whether system will use any movement type? if yes what movement type and from where the movement type will be picked up?

    When you create a delivery without referring to a preceding document, the system copies the following data into the document from the appropriate master records:
    Data from the customer master record of the ship-to party
    Data from the material master records of the delivery items
    normally schedulelines are determined by item category mrp type and schedule line.
    so it is determined by mrp type of the material

  • Problem with Delivery Type Determination in Purchase Order

    Dear All,
    We are working on a IS-Retail Scenario where we are dealing with generic articles. While creating a PO, we have encountered an error which says:"Also specify a delivery type in case of shipping data relevance". The error message number is MEPO 099. We have checked that Delivery type NL is attached to the document type under the supplying site customizing, and supplying site is attached to the receiving site with the correct document type. Can anybody throw some light on what we might be missing out in this scenario?
    Thanks and Sincere Regards,
    Amitabha

    Hi
    I suppose you are creating a retuns PO ,
    Please maintain the customizing of the same in SPRO-> MM -> Purchasing-> Purchase Order-> Returns Order-> Store Return / Return Plant to Plant
    here you need to maintain the delivery type for returns.
    This message is trigerred only in case of Returns order
    In SAP Retail, plants are referred to as distribution centers or stores. With store returns, you can map the return delivery of goods from
    a store to a distribution center (this is the most common case),
    from one distribution center to another distribution center,
    from one store to another store,
    from a distribution center to a store (although this is not very common).
    Requirements
    For the return delivery types, you have to make settings for the item category determination.
    Partner schema must be assigned to the return delivery types.
    The relevant goods movement types must be assigned to the schedule line categories (for the returns in Sales). The following schedule line categories are also available in the system:
    NR - Replenishment Returns and
    NS - Replenishment Cross Company Returns
    Activities
    Assign the required return delivery type to
    purchasing document category F (purchase order),
    purchasing document type (NB - standard purchase order, UB - stock transport order),
    the supplying plant (the one to which the goods are being returned)
    The following return delivery types are available in the system:
    NLR - intra-company-code store returns (purchasing document type UB for replenishment and return orders, delivery type NL for the replenishment delivery)
    NCR - cross-company-code store returns (purchasing document type NB for replenishment and return orders, delivery type NLCC for the replenishment delivery)
    Please maintain the required customizing
    Thanks & Regards
    Kishore

  • Delivery type determination in SD document

    Hello Guys,
                     When a sales order is created,outbound delivery is created .
                     Can you please let me know how delivery type for this outbound delivery is determined from Sales order type.
    Thanks,Kiran

    Kiran
    del type is assign to sales doc type .
    thru t code vov8 u can assign the del type .
    cheers
    shalsa007.........

  • Storage location-determination of return-deliveries (delivery type RL)

    Is there a difference between picking storage location-determination of return-deliveries (delivery type u201CRL Returns (pur.ord.)u201D/return to vendor) on 4.6C compared to ECC6.0? Is there a SAP-note?
    Within 4.6C-system the storage location is determined based on the customizing settings (Logistics Execution \ Shipping \ Picking \ Determine Picking Location \Assign Picking Locations).
    Within ECC6.0-system the storage location in the return-delivery is always the storage location that is entered in the Return-Purchase Order. It seems like the customizing-settings are no longer beeing taken into account.

    This storace location-determination of return-deliveries (delivery type RL) in customozing that you mention is only true within the 4.6C-system. Within the ECC6.0-system the storage lcoation is always the one that is entered in the return-purchase order. In ECC6.0 the customizing settings you are refering to a no longer valid for deliveries with delivery type RL.
    The questions is why/ and is there an OSS note.

  • Program error: Object type of receiver cannot be determined

    Hello Experts,
                   Am getting this error "Program error: Object type of receiver cannot be determined" when creating internal orders using BAPI_INTERNALORDERS_CREATE. I read many forums, but they are not answered. I didn't get any solution. Any Solution Please.
    Thanks in Advance

    Here is my Code
    TYPE-POOLS : TRUXS.
    TYPES:BEGIN OF TY_COAS_SVALD,
          AUART TYPE AUFART,         "Order Type
          BUKRS TYPE BUKRS,          "Company Code
          KTEXT TYPE AUFTEXT,        "Description
          GSBER TYPE GSBER,          "Business Area
          WERKS TYPE WERKS_D,        "plant
          KDAUF TYPE KDAUF,          "Sales Order Number
          KDPOS TYPE KDPOS,          "Item
          USER0 TYPE AUFUSER0,       "Applicant
          USER1 TYPE AUFUSER1,       "Applicant's telephone number
          USER2 TYPE AUFUSER2,       "Person responsible
          USER6 TYPE AUFUSER6,       "Department
          KOKRS TYPE KOKRS,          "Controlling area
          AUFWAERS TYPE AUFWAERS,    "Currency
          END   OF TY_COAS_SVALD .
    DATA : IT_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
    DATA:T_COAS TYPE STANDARD TABLE OF TY_COAS_SVALD INITIAL SIZE 0,
        WA_COAS TYPE  TY_COAS_SVALD.
    PARAMETERs : p_file TYPE IBIPPARMS-PATH.
    at SELECTION-SCREEN on VALUE-REQUEST FOR p_file.
      PERFORM browse_file.
    INITIALIZATION.
      CLEAR:WA_COAS.
      REFRESH:T_COAS.
    START-OF-SELECTION.
    PERFORM LOAD_FLAT_FILE.
    PERFORM SUB_CALL_BAPI_FOR_KO01.
    FORM browse_file .
    CALL FUNCTION 'F4_FILENAME'
    IMPORTING
       FILE_NAME           = p_file
    ENDFORM.                    " browse_file
    FORM LOAD_FLAT_FILE .
    DATA : LT_RAW TYPE TRUXS_T_TEXT_DATA.
      CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
        EXPORTING
          I_FIELD_SEPERATOR          = 'X'
         I_LINE_HEADER              = 'X'
          I_TAB_RAW_DATA             = LT_RAW
          I_FILENAME                 = P_FILE
        TABLES
          I_TAB_CONVERTED_DATA       = T_COAS
       EXCEPTIONS
         CONVERSION_FAILED          = 1
         OTHERS                     = 2
      IF SY-SUBRC <> 0.
      ENDIF.
    ENDFORM.                    " LOAD_FLAT_FILE
    FORM SUB_CALL_BAPI_FOR_KO01 .
      DATA:L_MASTERDATA  TYPE BAPI2075_7,
           LE_MASTERDATA TYPE BAPI2075_2,
           T_BAPI TYPE STANDARD TABLE OF BAPI2075_6 INITIAL SIZE 0,
           WA_BAPI TYPE BAPI2075_6.
    clear:l_masterdata,
          le_masterdata,
          wa_bapi.
    refresh:t_bapi.
      LOOP AT T_COAS INTO WA_COAS.
      L_MASTERDATA-ORDER_TYPE = WA_COAS-AUART.
      L_MASTERDATA-COMP_CODE = WA_COAS-BUKRS.
      L_MASTERDATA-ORDER_NAME = WA_COAS-KTEXT.
      L_MASTERDATA-PLANT = WA_COAS-WERKS.
      L_MASTERDATA-BUS_AREA = WA_COAS-GSBER.
      L_MASTERDATA-SALES_ORD = WA_COAS-KDAUF.
      L_MASTERDATA-S_ORD_ITEM = WA_COAS-KDPOS.
      L_MASTERDATA-APPLICANT = WA_COAS-USER0.
      L_MASTERDATA-APPLICANT_PHONE = WA_COAS-USER1.
      L_MASTERDATA-PERSON_RESP = WA_COAS-USER2.
      L_MASTERDATA-DEPARTMENT = WA_COAS-USER6.
      L_MASTERDATA-CO_AREA = WA_COAS-KOKRS.
      L_MASTERDATA-CURRENCY = WA_COAS-AUFWAERS.
      WA_BAPI-SALES_ORD = WA_COAS-KDAUF.
      WA_BAPI-S_ORD_ITEM = WA_COAS-KDPOS.
      WA_BAPI-COMP_CODE = WA_COAS-BUKRS.
      APPEND WA_BAPI TO T_BAPI.
    CALL FUNCTION 'BAPI_INTERNALORDER_CREATE'
          EXPORTING
            I_MASTER_DATA       = L_MASTERDATA
    IMPORTING
       E_MASTER_DATA       = LE_MASTERDATA
    TABLES
       SRULES              = T_BAPI
       RETURN              = IT_RETURN
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
      ENDLOOP.
      WRITE : / IT_RETURN-TYPE, IT_RETURN-MESSAGE.
    ENDFORM.                    " SUB_CALL_BAPI_FOR_KO01

Maybe you are looking for

  • Why does my free trial not work?

    Why does my free trial not work?  This is intentially misleading.

  • Invoke a function in a package

    I need to call a function in a package that will return back to me the database I am connected to The package and function is called :p_common.sf_get_dbname CallableStatement getDBName=null; ResultSet rs2=null;          try               ggetDBName =

  • **** Editing and Saving an Adobe Form on the Server ****

    We are trying to achieve the following: 1. Generate 3D PDF from VRML (Done) 2. Embed the 3D PDF into a PDF Template and save it on the Server as an editable .pdf file 3. Then, the user must be able to open the Editable PDF inside a web browser such a

  • FORMAT MASK JSP WITH BC4J

    I am developing a jsp application with bc4j. I want to give a format to date fields. I have got it when I display records but when I edit or insert records it breaks. I override methods setXXX, getXXX in the MyEntityImpl.java file. Has anyone got it?

  • SB X-Fi Driver Installation Problem (X-Fi does not install on Asus A8N-VM CSM

    Dear forum members, I want to install Soundblaster X-Fi Xtreme on my Windows XP x64 Professional computer, but i am not able to succesfully finish 64bit X-Fi driver installation. Whether i use newer x64bit X-Fi beta driver or older official x64bit X-