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

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

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

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.

Dlv. type (dlv. catgry LB for mat. and BWART 541) cannot be determined

Hi,
We want to post components to subcontracting stock. I'd use MB11 or MB1B to reference to just one PO/item. The subcontractor is replenished per component-kit. When I post in MB1B or MB11 I get message :
Dlv. type (dlv. catgry LB for mat. 10002683 and BWART 541) cannot be determ
Message no. VL295
With ME2O I can make a delivery document LB. What is the difference in settings between these transactions?
Anyone familiar with this ?
Thanks for your help.
DR

Hi,
There are 2 ways to tranfer stock to subcon:
1. Inventory mvt - 541 (from MB1B) - No logistics functionalities available, although the end result for stock mgmt and Finance are same
2. delivery using ME2O using delivery document (you can use all functionalities e.g. picking, packing etc) in details
for your error message -- did u check that delviery type LB is maintained for ur plant in txn OMGM
Cheers
Dheeraj

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

Message no. VL295 (Dlv. type (dlv. catgry LB for mat. & and BWART 541)

When attempting to do a transfer posting (MB1B or MIG_TR) from unrestricted stock to SC vendor stock the following error message is displayed "Dlv. type (dlv. catgry LB for mat. 85 and BWART 541) cannot be determined".
I checked all the configuration settings; could someone list the configuration and data steps involved to get this process working?
Thank you

Hi,
I am also facing the same error. Can you please let me know what the solution is?
Regards,
Ravi Davda

Error saving: The location of the document " DOC NAME " cannot be determined.

I am having issues saving .pages files on to our network drive after upgrading to Mavericks and Pages 5.0.
A bunch of errors and issues occur when editing old or saving new pages files on our local SMB server. Saving files on to my local machine is fine.
I cannot save to the original network location at all. It errors: The location of the document "<DOC NAME>" cannot be determined. The folder in question has permissions that have always worked before the upgrade of mavericks/pages. I can rename the files in question, and save other types of files in to that folder without issue.
When it errors, it provides the option to Save as... this also fails, no matter where I try to save it to - local or network.
The auto-save feature fails for the same reason. This creates several temp folders with blank pages documents in it.
Most disturbingly, it appears to be destroying the original file by renaming it to a temp file, that is henceforth un-usable. Luckily Ive got backups of the documents.
Help!

Update:
The new version of Numbers also comes up with the same errors.
The previous version of both Pages and Numbers work absolutely fine still - have had to revert to using these for now.

VKORG, VTWEG, SPART cannot be determined for customer C3000 , vendor VENDOR001

Message Type is ORDERS & basic Type is ORDERS05.
While executing IDOC, we are getting error message 51 with below message.
Message no. VG204
VKORG, VTWEG, SPART cannot be determined for customer C3000 , vendor VENDOR001.
Relation with SAP values is maintained table EDPAR. but while executing IDOC through IDOC_INPUT_ORDERS, System is not collecting values from EDPAR table.
Do we have user exit available to resolve this issue.
Please help.
Thanks & Regards,
Ashish Mankar/Ganesh.

Hi Guido,
One of my clients are getting the same error, and without a complete access to their system its proving very difficult to resolve.
I know about VOE4 - Mapping, where the supplier 'maps' the customers cost-centre/business unit/int ref etc to suppliers account number.
Just wondering what is the difference between VOE2 and VOE4?
Thanks,
Tanzim

IDoc status error 51 : A company code cannot be determined for LS

Hi,
We are trying to post an Idoc into R/3 but getting the IDoc status code 51 : A company code cannot be determined for LS
What could be the possible reason?
Should we use Party in Receiver IDoc scenarios?

Hi,
I have quite the same problem. I built an IDOC with WE19 and I have the message "A company code cannot be determined for LI 0000031004".
As explained in note OSS 117808, the partner number (31004) and partner type (LI) are read from the control record of the IDOC. I enter this values in OBCA and OBCE customizing points, to determine the company code 'LC'. It doesn't work.
PT Rao, what do you call "activate partner profile" ?
Thanks in advance.
Regards,
Arnaud

Condition Types in Price Determination Process

Hi
Can any one explain me about in Detail about the VARIOUS TABS that work in the CONDITION TYPE of PRICE DETERMINATION PROCESS
Thanks & Regards,
Senmani.

hi
hi
control data 1 :
Condition Class is a grouping that lets you control each condition type differently.
For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
Calculation type
Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:
10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
In rounding rule 'B', values are always rounded down:
1045.9 -> 1045 LIT
1045.1 -> 1045 LIT
In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
Structure condition
controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
Aduplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
control data 2 :
promotions
Specifies that the condition type in question is only valid for Promotions.
Use
Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
Use
If you mark this indicator, the condition appears in the document as a statistical condition.
Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition type:
'Variant condition' (KVARC)
'Internal costing condition' (KFKIV)
The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
inv.list condi
Condition for invoice list
Marks the condition type as relevant for internal costing.
Quantity conversion
This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
Scale :
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
Scale Type
Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
Formula for scale base value
Formula for determining the scale base value.
Use
You can use this formula to specify calculation methods that are not provided in the standard system.
reward points if helpful
thanks and regards
ravikant dewangan

Mov.aver.price cannot be determined.Material RMWE,plant 7210,billing docCAP

Hello Guys,
Can anyone help on this issue.
Mov.aver.price cannot be determined.Material RMWE,plant 7210,billing docCAPE_01
Message no. Z1022

Rajesha,
Typically the trans./event keys hit on GR against a PO are BSX (inventory/stock posting) and WRX (GR/IR clearing). If the material is subjected to standard price control, you will have an additionally have the PRD key (price difference posting).
If you go to OBYC and see the account assignments for the PRD trans./event key, you will notice that you can have a different price difference income/loss account based on the material (valuation class), plant (valuation grouping code) and the account modifier (mvt type). In your specific case, the account modifier is blank and there does not seem to be a provision to define a new account modifer and link it to mvt 101 for the required combination (that I mentioned in my previous response). This seems to be the problem unless I am missing something here. For instance, in the case of a 201 mvt or a 101 receipt against a production order, the required combination is available in OMJJ and hence it is possible to define and link a new account modifier to a new movement type and hence use a different account for different circumstances. I am just not sure why SAP has not provided this option for your scenario.
Hope this helps.
H Narayan

Error Message: Real estate object cannot be determined from entries

Hi
We are using the BBPIV01 IDoc Type to pass Invoice data to backend system. We have implemented BBP_ACC_CHECK_ICC BADI to update the RL_EST_KEY (Internal Key for Real Estate Object) field. But when the IDoc is processed in the backend system it end up with the following error message.
<b>Real estate object cannot be determined from entries (ID: RECAAP, No: 012 ).</b>
Note: We are treating Real Estate Contract as an Account Assignment Category in SRM.
Any help would be highly appreciated.
Regards
Kathirvel

Hi Ramki
I have check the same i.e. in ECC. All the necessary changes explained in the notes have already been done in the release we are using. And I meant that the notes are not relevant for the problem I am facing now.
Thanks a lot for your concern.
Regards
Kathirvel

BAPI_GOODSMVT_CREATE Dlv. type cannot be determined

Similar Messages

Maybe you are looking for