TABLE FOR MOVEMENT TYPE

Hi,
Can anybody the table name in which movement types are stored.
Regards,
Prabu

Hi,
Movement types are stored in Table T156 & field name BWART.
Thanks,
AMIT

Similar Messages

Need Fields KDAUF, KDPOS, BWART update in table GLPCA for movement type 633

Hi All,
I need following field update in Table GLPCA for movement type 633 (Consignment Issue):
KDAUF : sale document no.
KDPOS : Order Line Otem
BWART : Movement Type
The same fields are updated for movement type 601 (Standard order). Also I checked with Table MSEG and find the same as above.
Thanks in advance.
AT

You should use the BAPI instead BAPI_GOODSMVT_CREATE
of BDC.
http://www.sap-img.com/abap/bapi-goodsmvt-create-to-post-goods-movement.htm
Welcome to SDN. Please be sure to award points for any helpful answers and mark your post as solved when solved completely. Thanks.
REgards,
Rich Heilman

Issue with Return Delivery for movement type 262

Hi,
I have got a strange issue, the user is trying to do a MIGO Return Delivery for a material document using movement type 262, this he claims has been doing it for many materials. However when i go to the MKPF table i see the transaction Code field to be MIGO_GI for all the material documents for which he claims to have done return delivery. But under this transaction code we have only 4 options - Display, Issue, Cancel and Remove from storage.
Now when he tries to do the return delivery for movement type 262 he get an error message "Check table T156N: entry RL 262 does not exist" , but this has been very well maintained in the table.
Can you please let me know -
If it is possible to do a return delivery for a movement type 262?
If yes how to address the above error encountered.
Thanks in advance
Sachin

Hi Sachin,
If you think of return delivery to vendor with or w/o PO reference you can use movement types 161, 122, 124 as default settings.
Movement type 261 means withdrawal against production order and its reverse is MVT 262. The latter can be used e.g. via MB1A (or you can make storno of a confirmation by 261).
Are you sure your user is using the correct terminology ('return delivery')? Please check the material documents he/she claims to have booked as return delivery. (in MB51 you can get a list of all material movements of MVT 261 that belong to 'your user' and after that you can open the material document and check through which transaction the booking was made.)
BR
Csaba

BAPI_GOODSMVT_CREATE for movement type 161, issues in PO creation

Hello Gurus,
I am using movement type 161 with BAPI_GOODSMVT_CREATE in order creating a vendor PO based on the goods receipt posted with the BAPI.
It works fine, nevertheless due to business requirements, I need to apply the following changes:
- in SAP standard the order type is NB by default but in our case I would like to force another order type using the same range that NB. I guess this could be done by activating exit ZXM06U17 (MM06E003). Does someone could confirm it?
- in our process, the purchasing group is not maintained at vendor level (LFM1-EKGRP) but as this field is mandatory in the PO creation and as this data can not be maintained in BAPI_GOODSMVT_CREATE, does someone know if it would be possible to force this value during the PO creation (EKKO-EKGRP) based on a maintenance table? If yes in which user-exit? Exit ZM06U43 could be used?
- furthermore, our specific PO type should have a specific account assignement EKPO-KNTTP instead of the default value U, does someone know if it would be possible to force this value during the PO creation (EKKO-EKGRP) based on a maintenance table? If yes in which user-exit? Exit ZM06U43 could be used?
Kind regards
Chris

Hi Priya,
Just want to share with your guys how to fit this error in BAPI_GOODSMVT_CREATE.
For movement type 161 of PO return you have to pass movement type 101 instead of 161
goodsmvt_item-bwart = 101. After that standard function will determine 101 to 161 automatically and
post that material doc.
NOTE:
In my case
It just heppen only the FIRST time that you do movement with PO Return wich is needed to pass
101 in stead of 161 but after that you can pass 161 the system will continue process correctly.
Hope it help.
Sayan.

Account modification key for movement type 643

Hello Experts,
I am reaching out to you today as I am in need of some info on Account assignment for Goods issue process. I looked at transaction OMWN or OMJJ for movement type based settings. I am running a business process ' Intercompany stock transfer order'. Goods issue movement on delivery reads 643(Goods issue for cross company), which is picking 'Account modification key' VAX.
My requirement was how do I force system to pick VAY for 643 without overwriting VAX with VAY in OMWN transaction. Also there are several possibilities listed out for movement 643 alone. Appreciate if you could briefly tell me how system determines other parameters such as 1) Special stock indicator 2)Consumption posting 3) Value string & 4)Counter to determine 'Account modifier' in the customizing table V_156X_KO for Intercompany movement type 643.
Additional info: Trigger is Stock tarnsfer order type NB. Subsequent process is VL10B for Delivery creation using type NLCC and Intercompany invoice(IV) for shipping the goods to ordering company code. Then in the receiving company MIGO or goods receipt with reference to outbound delivery and fianlly MIRO or Invoice verification.
Regards
SG

Valuation Structure
Data on a material is valuated using the following structure:
Valuation area
Valuation class
Valuation category
Valuation type
Material type
Movement type
Valuation Area
Organizational level at which material valuation is carried out. You can define a valuation area as
follows:
Valuation area = company code
All stocks of a particular material in this company code are valuated together.
Valuation area = one plant
The stocks of a particular material in this individual plant are valuated together. Stocks in
other plants are not included in this valuation area.
You define in Customizing the level at which valuation should take place.
Valuation Class
You group together different materials with similar properties into valuation classes so that you
do not have to manage a separate stock account for every material.
The following table contains examples of possible valuation classes:
Valuation class Description
3001 Colors
3002 Paints
3030 Operating supplies
3100 Trading goods
Which valuation class a material can be assigned to depends on the material type. You can
define the following assignments in Customizing:
All materials with the same material type are assigned to just one valuation class.
Different materials with the same material type are assigned to different valuation classes.
Materials with different material types are assigned to a single valuation class.
MM - Material Price Change (MM-IV-MP) SAP AG
Valuation Structure
10 April 2001
A material is assigned to a valuation class in the material master record. The system checks
whether the material type allows the material to be assigned to the valuation class specified.
The system refers to the valuation class of a material to determine which stock account to post to
when a posting is made for this material.
Valuation Category
Criterion according to which split valuation is carried out:
Procurement
You can valuate a material differently depending on whether it is manufactured in-house
or procured externally.
Origin
You can valuate a material differently depending on where it comes from (such as home
or abroad).
Status
You can valuate a material differently depending on its status (such as new, used,
repaired).
You define the valuation categories in Customizing. A material is assigned a valuation category
in the material master record.
Valuation Type
The valuation type specifies the individual characteristic of the valuation category, such as
internal or external, in the case of Procurement. Within the valuation category Origin, you can
define the different countries as the valuation types. You define valuation types in Customizing.
You first determine all the valid valuation types for a valuation category.
You define in the material master record which valuation types are allowed for a particular
material. For every material subject to split valuation, you must enter all the valuation types
allowed in the material master record.
Material Type
You assign every material to a material type when you create it. Examples of material types in
the standard system include raw materials, operating supplies and finished products.
The material type controls the properties of a material and which data must be maintained for the
material. The following control features are important for valuation:
Is the material managed by quantity?
Is the material managed by value?
Which price control type may be used for the material?
Which valuation class can the material be assigned to?
The system administrator can create or change material types in Customizing.
Movement Type
For every material movement, there is a movement type in the SAP System. The movement type
controls the properties of the movement, for example, which entries you must make when
SAP AG MM - Material Price Change (MM-IV-MP)
Valuation Structure
April 2001 11
entering a material movement, and which updates are carried out when the movement is posted.
The following control features are important for valuation:
Does the material movement cause the quantity to be updated?
Does the material movement cause the value to be updated?
Does the material movement lead to postings in Accounting?
Is the material movement relevant for LIFO/FIFO valuation?
The system administrator can create or change movement types in Customizing.

Account assignment for movement type 221

Hi,
Instead of using account suggested by GBB-VBR for movement type 221 we want to use account entered by user in transaction as an offset to inventory account.
However SAP keeps on hitting account determined automatically (from GBB-VBR) and ignores account entered by user in transaction. In fact account entered by user in transaction is getting replaced by GBB--VBR and is also not available in any table (MSEG etc)
I have already checked - checkbox "Check account assignment" that states preference to user entered account in transaction, in movement type -- account grouping config but for no use.
Please help
Thanks,
Ashutosh
Edited by: Ashutosh_x on Apr 6, 2010 7:22 PM
Edited by: Ashutosh_x on Apr 6, 2010 7:23 PM
Edited by: Ashutosh_x on Apr 6, 2010 7:25 PM

In OBYC for Transaction GBB, instead of BSX, maintain BSA, VAX & VAY for each Valuation Class of material and its respective G/L Account.
For example, if you are trying for a FERT material, then the entries should be
0001::::BSA:::::7920::::::4XXX30
0001:::VAX:::::7920:::::::5XXX30
0001:::VAY:::::7920:::::::6XXX30
Also check in OMJJ whether you have the settings as follows:-
MvT::S::Val.Upd:::Qty.upd:::Mvt::Cns:::Val.stng:::Cn:::TEKey:::Acc mod:::Check acct.
561::::::::::::X::::::::::::::::::::::::::::::::::::::::::::WA01:::::2:::::GBB:::::::BSA::::::::::::::::X
561::::::::::::X::::::::::::::::::::::::::::::::::::::::::::WA01:::::3:::::PRD::::::::PRA:::::::::
561::::::::::::X::::::::::::X:::::::::::::::::::::::::::::WA01::::::2::::GBB:::::::BSA:::::::::::::::::X
561::::::::::::X::::::::::::X:::::::::::::::::::::::::::::WA01::::::3:::::PRD:::::::PRA:::::::::
Check whether your settings are similar to above.
thanks
G. Lakshmipathi

BAPI to reverse Goods Issue for movement type 601

Hi Everyone,
Does anyone know of any BAPI that could be use to reverse Goods Issue for Movement type 601?
I tried using BDC of transaction VL09 and was able to reverse the GI document successfully but the return message type was 'E' with unreadable message -
Tabelle 'E' enth#t keinen Eintrag f# 'Ch 004 &'
When I tried using BAPI_GOODSMVT_CANCEL, I get the error message 'E M7 130 Material document cannot be processed'.
Best Regards,
Junwen

hi, Junwen!
the following code works pretty well:
      fp_vbeln = vbeln_val.
      fp_budat = budat_val.
      fp_tcode = 'VL09'.
      fp_vbtyp = 'J'.
      CALL FUNCTION 'WS_REVERSE_GOODS_ISSUE'
        EXPORTING
          i_vbeln                         = fp_vbeln
          i_budat                         = fp_budat
        I_COUNT                         =
        I_MBLNR                         =
          i_tcode                         = fp_tcode
          i_vbtyp                         = fp_vbtyp
        TABLES
          t_mesg                          = it_mesg
       EXCEPTIONS
         error_reverse_goods_issue       = 1
         OTHERS                          = 2.
luck.

Re: Changing Inspection lot origin from 08 to 05 for movement type 322 and 349

Reference discussion: Changing Inspection lot origin from 08 to 05 for movement type 322 and 349
With reference to the above discussion and your explanation for user EXIT QAAAT0001, it was stated that:
If you only have two inspection types, you can mark one as preferred. Then with exit use logic that if MM = 311 use preferred inspection type, if 911 use, non-preferred inspection type.
May I ask what are you refer to for MM? It seems like movement type to me, however, I can't find movement type field in the structure within the component of EXIT_SAPLQAAT_002. Appreciate if you could shed some light on this.
Best Regards,
CY
Branched from older discussion by moderator. When there are questions concerning an older discussion, please create a new discussion with reference to the older one. Thanks!

Yes.. you are correct. But with the info that is provided by EXIT_SAPLQAAT_002, you should be able to identify the proper material document in table MSEG which will have the material movement.
You can use the values of plant, batch, material number, Purchase order number, Order number, item number, storage location as well as the current date since the exit would normally be executed on the same date the material movement was done. You'd also probably only execute the logic if QKZ is "X".
Craig

Report RFDUZI00 claims about entry for movement type CREIR

Hello,
we have moved from R/3 4.6 to ECC 6.0. Now we have some errors coming up in FI module.
One is this:
Report RFDUZI00 (debitor interest calc. run) ends with a comment before posting:
"For movement type CREIR and interest attribute 01 the table of time dependent interest conditions is not maintained" (message translated from german).
We had to add this entry in transaction OB81 to get rid of this issue.
In 4.6 we didin´t need this entry to run the report successful.
We have checked and did not find any comments in release notes.
Question: Can anybody confirm to this new requirement of the system, which looks like RFDUZI00 or dependent include etc. was enhanced to check entries for creditors (for which reason?).
Possibly we found the answer in OSS 670117, which explains changes in RFDUZI00 relevant since R/3 4.7.
Regards
Dirk
Message was edited by:
Dirk Meinhard

Solved on my own!

BAPI_GOODSMVT_CREATE is not working for movement type 701 in MIGO

Hi gurus
Can anybody help to track that bapi: BAPI_GOODSMVT_CREATE is not working for movement type 701 for MIGO Transaction.

call this standard BAPI, AND EXECUTE IN SE37
""Local Interface:
*" IMPORTING
*"     VALUE(GOODSMVT_HEADER) LIKE BAPI2017_GM_HEAD_01 STRUCTURE
*"        BAPI2017_GM_HEAD_01
*"     VALUE(GOODSMVT_CODE) LIKE BAPI2017_GM_CODE STRUCTURE
*"        BAPI2017_GM_CODE
*"     VALUE(TESTRUN) LIKE BAPI2017_GM_GEN-TESTRUN DEFAULT SPACE
*"     VALUE(GOODSMVT_REF_EWM) LIKE /SPE/BAPI2017_GM_REF_EWM STRUCTURE
*"        /SPE/BAPI2017_GM_REF_EWM OPTIONAL
*" EXPORTING
*"     VALUE(GOODSMVT_HEADRET) LIKE BAPI2017_GM_HEAD_RET STRUCTURE
*"        BAPI2017_GM_HEAD_RET
*"     VALUE(MATERIALDOCUMENT) TYPE BAPI2017_GM_HEAD_RET-MAT_DOC
*"     VALUE(MATDOCUMENTYEAR) TYPE BAPI2017_GM_HEAD_RET-DOC_YEAR
*" TABLES
*"      GOODSMVT_ITEM STRUCTURE BAPI2017_GM_ITEM_CREATE
*"      GOODSMVT_SERIALNUMBER STRUCTURE BAPI2017_GM_SERIALNUMBER
*"       OPTIONAL
*"      RETURN STRUCTURE BAPIRET2
*"      GOODSMVT_SERV_PART_DATA STRUCTURE
*"        /SPE/BAPI2017_SERVICEPART_DATA OPTIONAL
*"      EXTENSIONIN STRUCTURE BAPIPAREX OPTIONAL
*"      GOODSMVT_ITEM_CWM STRUCTURE /CWM/BAPI2017_GM_ITEM_CREATE
*"       OPTIONAL
call function 'BAPI_GOODSMVT_CREATE'
    exporting
      goodsmvt_header         = goodsmvt_header
      goodsmvt_code           = goodsmvt_code
      testrun                 = testrun
      goodsmvt_ref_ewm        = goodsmvt_ref_ewm
    importing
      goodsmvt_headret        = goodsmvt_headret
      materialdocument        = materialdocument
      matdocumentyear         = matdocumentyear
    tables
      goodsmvt_item           = goodsmvt_item
      goodsmvt_serialnumber   = goodsmvt_serialnumber
      return                  = return
      goodsmvt_serv_part_data = goodsmvt_serv_part_data
      extensionin             = extensionin.
commit work.
hi, rewards point, if this is useful,
regrds
karthikeyan

GOODSMVT_CREATE for movement type 161, Error mg " Enter Purchase group "

Hi Experts,
While creating PO for movement type 161 , it doesnu2019t insert the good receipt in SAP . I am getting the error message " Enter the Purchase group" after coming out from the BAPI_GOODSMVT_CREATE.
i tried with movement 101 and it create correctly the GR in SAP . Problem oly with movement type 161.
Anything i have to do changes in code or its functional side (they have to maintain.).
Please help me.
Thanks a lot in Advance.
Regards,
Priya.

Hi Priya,
{CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
    EXPORTING
      goodsmvt_header = p_lt_goodsmvt_header " here in this header struc pass movement type
      goodsmvt_code    = ' '   " pass this value correctly
      testrun          = ' '
    IMPORTING
      goodsmvt_headret = p_e_goodsmvt_headret
    TABLES
      goodsmvt_item    = p_lt_goodsmvt_item
      return           = lt_return.}
Thx,
Vishnu .

BAPI_GOODSMVT_CREATE for Movement type 262

Can anyone please suggest a BAPI or FM for MB1A transaction for movement type 262 ?
I am trying to use it but returns with error 'Stock data of serial number 40000000 not suitable for movement'
Edited by: Venkat Naga on Dec 2, 2011 8:31 PM

Hi,
Here is some sample code from one of my programs, which does a 551 movement type. This should get you started. Just check the RETURN table for messages, they should tell you what you are missing.
code
Structures for BAPI
data: gm_header type bapi2017_gm_head_01.
data: gm_code type bapi2017_gm_code.
data: gm_headret type bapi2017_gm_head_ret.
data: gm_item type table of
bapi2017_gm_item_create with header line.
data: gm_return type bapiret2 occurs 0.
data: gm_retmtd type bapi2017_gm_head_ret-mat_doc.
clear: gm_return, gm_retmtd. refresh gm_return.
Setup BAPI header data.
gm_header-pstng_date = sy-datum.
gm_header-doc_date = sy-datum.
gm_code-gm_code = '06'. " MB11
Write 551 movement to table
clear gm_item.
move '551' to gm_item-move_type .
move '000000000040001234' to gm_item-material.
move '1' to gm_item-entry_qnt.
move 'EA' to gm_item-entry_uom.
move '0004' to gm_item-plant.
move '4000' to gm_item-stge_loc.
move '201' to gm_item-move_reas.
Determine cost center per plant
case xresb-werks.
when '0004'.
move '0000041430' to gm_item-costcenter.
when '0006'.
move '0000041630' to gm_item-costcenter.
when '0007'.
move '0000041731' to gm_item-costcenter.
when '0008'.
move '0000041830' to gm_item-costcenter.
endcase.
append gm_item.
Call goods movement BAPI
call function 'BAPI_GOODSMVT_CREATE'
exporting
goodsmvt_header = gm_header
goodsmvt_code = gm_code
importing
goodsmvt_headret = gm_headret
materialdocument = gm_retmtd
tables
goodsmvt_item = gm_item
return = gm_return.
call function 'BAPI_TRANSACTION_COMMIT'
exporting
wait = 'X'.
[/code]
Welcome to SDN! Please remember to award points for helpful answers and mark you post as solved when solved completely. Thanks.
REgards,
Raj.

Field Selection error for movement type and G/L account

I am currently experiencing a field selection error between movement type 601 and G/L account 7140000. The problem field is 'Segment'. This field is set to required for the G/L account, but it is hidden for the movement type 601. This inconsistency causes an error when posting the goods movement. According to business requirement the field must be required for the G/L account, therefore we must make this field optional for the movement type.
However, in configuration the field segment does not appear for the movement type 601. Therefore it can not be changed to optional.
Does anyone know a workaround other than making this field optional for the G/L account because the business requirement is to have this field as required?????
Many Thanks

Hi,
On the Error message detail, system will guide you to the Configuration details for Field settings for Movement type & Account, please get in touch with your FI consultant, to make the Field selection for the account similr to that of your movement type, this is a very common issue.
Regards
Chandra Shekhar

Hide/Suppress Cost center field in MIGO and MB1A for movement types 551&552

Hi All,
Can anybody tell me how to suppress or hide the cost center field in MIGO or MB1A for movement types 551 and 552?
I did below settings and it worked fine for only MB1A and for MIGO still it is showing cost center field.
IMG > Materials Management > Inventory Management and Physical Inventory >Goods Issue/Transfer posting > Define screen layout > select movement type to change the option.
Also I did gothrough the settings for Enjoy transaction (MIGO) there we have only option to make fields either "Required entry" or "Optional entry" and we don't have an option to hide/suppress.
Please advise or help me .
Thanks in advance!
Regards,
Praveen

Hi
The cost center field is a required field in mvt type 551 as you are scrapping materials, some cost center will need to take the cost of this operation.
Anyway, you first need to make the field as optional for example, before you move.
One option is that you create a screen variant in Tcode SHD0 for MB1A, where 551 is setup as constant (with content) , and mark Cost center as invisible and assign this screen variant to a transaction in SE93.
regards
Sidi

Error in MB1C but works perfectly in MIGO for movement type 501.

Hi
I get an error in MB1C but works perfectly in MIGO for movement type 501
here is the error Account 353300 requires an assignment to a CO object.
I know for this if we add the co object in OKB9 it works.
But my question is - how it works in MIGO transaction but throws an error in MB1C
Any idea ? has any one faced this kind of an issue ? Please let me know.
Thanks
Dkmurthy

Hi
Are the entires same in both the transactions? Means did you check 353300 GL was hit when you posted through MIGO?
Check in FS00 - for GL account 353300 - under bank/interest tab - double click on field status variant -> under Additional account assignments - CO object is ticked as mandatory?
Thanks

TABLE FOR MOVEMENT TYPE

Similar Messages

Maybe you are looking for