Default GL(123456) for movement type 221

Hi Frds,
We have the requirement to put the default perticular gl (12345678) when the user is using 221 movement type.Is it possible throuth configuration wise? Anyone can assist on this requirement.
Advance thanks to your help.
Regards,
Nivas.

Hi Nivas
                 Try the following steps to create a new G/L for the particular movement type. Take help from the FI person if possible.
             1. Create a customized movement type (copy of 221) in T.Code, OMJJ.
             2. Create a new valuation modifier (copy of VBR, say ZBR) in Account Grouping option
             3. Do Account Determination in T.Code, OBYC (GBB-ZBR) for the new valuation modifier
             4. Assign a new G/L (123456) for it.
             5. Now try posting the material document.
Regards,
Rajesh.

Similar Messages

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

How to set field "vendor" as optional for movement type 221

Hello experts, I want to set the field "Vendor"(LIFNR) as optional for movement type 221 when create reservation using T-code MB21. As far as I know, field selection of reservations is determined by the settings in the field selection(from201) of the movement type. But even when I have set the field "Vendor" as "optional" both in field selection (from 201) and field selection (Enjoy) for mvt 221 using T-code OMJJ, it is still not shown on the screen of creating reservation. Is it the SAP inside logic that restrict this field for movement type 221 or should I change any other settings elsewhere?
Any help will be highly appreciated.
Best regards!

Let me understand ,
u want to reserve stock with MB21 with optional for vendor code or name .
then against the reservation u was t to issue to cost centre or production with 201 rt .
If so hopefully this scenario excludes the normal production order process ( cozz their GI is w.r.t prd order only since reservation is created at backend and also shown in prod order).
ur req is normally for consumables or spares etc and u want o track the vendor also in the Reservation .
possible check is Movement type - screen in omjj
GL account variant settings
MB1a setting
last option - create a screen variant with SHDO tode and activate it .
all will be at client level so please

Create storage location automatically for movement type 261

Hi Experts,
Currently we're inprocess of implementing "create storage location automatically" for reservation, and I've done with the configuration for both reservation side (Define Default Values) and movement type side (GI/transfer posting - Create Storage Location Automatically).
For movement type 201, new storage location successfully extended/created using T-Code MB21 (Create Reservation). But we found an error message while conducting the same thing for movement type 261 (which only can be created using T-Code IW31 (Create material reservation form Work Order).
Did we missed any required configuration? Pls kindly advice on what we should do.
Thanks a lot. Really appreciate the prompt response.
Rgds,
MD

Here's the current situation,
We configured the plant/storage view (SPRO), most of materials already extended to desired plant and storage location. Commonly, we can extend or create any materials for certain plant and/or storage location by maitain material master data (using T-Code MM01).
Recently, we develop the additional configuration to activate "automatic create storage location" for reservation, aligning with the movement type for Goods Issue (201,221,261,301,etc).
Let's say we have material number 123456789 and currently assigned to plant YYYY, but not extended to storage location XXXX. By performing T-Code MB21 (create reservation) with movement type 201 inputted, the respective material (123456789) is automatically created for the XXXX storage location.
But the above condition is not effected while performing the same thing using T-Code IW31 (create material reservation via Work Order) with movement type 261 (GI for Order).
Any idea to perform create storage location automatically while creating reservation for movement type 261? is there any possible configuration or procedure to be added?
Thank you

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.

Layout for movement type 101 (MB01)

Hi experts,
1) I would like to know more on how can I define the layout for MB01 other than using screen variant?
2) Also, I would like to know more on how can I define layout for movement type lower than 201?
I can only do that for movement type > 201 in SPRO.
Thanks and regards,
JT

Hi Parag Mahajan,
Just want to double confirm with you about this.
What if I want to grey a field or make it available for user to make changes to a grey field?
My problem is tcode MB01, the Document Date field was grey and defaulted to today's date. I want to make it available and allow user to change the document date.
Thanks and regards,
JT

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

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

HUMO-A reason has to be entered for movement type 344

Hi All,
We currently have the system configured to enter a 'reason for movement' for movement type 344 and this field is marked as required in the movement type configuration. We have configures the transactions allowed for the movement type and HUMO is one of them.
When I try to post the same HU using the path 'Edit-> Change HU Posting-> Other Postings->Process-> Transfer posting unrestriced to blocked', it prompts me for a 'Reason for Movt' and allows me to post it to a blocked stock.
However, when we try to post an HU to blocked to stock using the path in HU monitor 'Edit-> Change HU Posting->In Blocked Stock', the system gives an error 'A reason has to be entered for movement type 344'. Please note, it does not even prompt me to enter a reason for the movement.
Is there a configuration node to have the above error corrected? Or is there any SAP note which could help us solve the problem? We are aware of the SAP note 1679167 for transaction VLMOVE but not sure the same would actually correct the issue for HUMO. Any help in this regard is appreciated.

Hello Biswajit,
unfortunately, as far as I can see in source
SAPLHUMO
/ LHUMOF04
FORM
/ TRANSFER_POSTING_HU
during debugging, there is no GUI code to ask user for a reason. So it's a lack of functionality.
I think you can add this by an implicit enhancement around FORM transfer_posting_hu asking user e.g. with function module call POPUP_GET_VALUES_DB_CHECKED.
But transfering the entered reason down to the MM posting seems also not so easy because reason field "GRUND" may not visible in that callstack level.
Hope that helps you along
Best regards,
Matthias

Error in Transfer posting for movement type 303

Hi Sir,
I am getting following error while doing Transfer posting for movement type 303 thru BAPI_GOODSMVT_CREATE
Error in Function:
Order    not found or not permitted for Goods Movement.
I am passiing all mandatory parameter for it as per BAPI Documentaion in tcode BAPI
Transfer posting
Transfer posting without reference to a reservation
The following fields must be populated:
Material number
Plant
Storage location
Movement type
Movement indicator
Quantity in unit of entry
ISO code unit of measurement for unit of entry
If I am doing manually by MB1B tcode, it is successfully done.......here its not asking any ORDER No...
Please help me .........
Regards,
Krishan

I'm not sure what you're system set up is...   So I'd suggest looking at everything you enter on the screen and then checking to make sure you are passing all the information in the BAPI.
With that said our system does require posting date, and batch. You might check that.   Also check that you've included all the required information in the header.
Did you use the same data when you tried to process the BAPI that you used when you tried to do MB1B manually?

Field selection for movement type 601 account 894025 differs for cutomer

While posting goods after saving delivery merror message
Field selection for movement type 601/aact 894025 differs for customer goods movement
I tried OMJJ>Mvtmt Type>601>Field selection enjoy>601 KONTO Optional field
Now this is only happening in the cases where I have assigned free goods Inclusive 10MT. If the order is less than 10MT (that is if no free goods attached) posting is accepted & billing & account determination is processed successfully.
I am unable to identify the reason though I have worked a lot on MM/Fico on the system.
Please provide your valued inputs why this is happening?
Thanks for your time.
Rajiv

Hi Raja,
Thanks for prompt reply.
I shall appreciate if you elaborate how to check
check the Field selection goup in control tab for that GL
I tried OBC$--> (Is this correct?)
I checked cost center field G004 -->Addl Act assignemtn -->Cost center which is Optional entry. Should I check any other items on the screen as I am unable to understand which field is applicable on a/c field.
Profit center, cost object are in G004 as supressed field.
So should I make optional? So thing will work.
Other Q should I also consider G025 Inventory adjustment account? As per error this a/c is not shown. So pl advise me steps or heading which I should consider.
Thanks for yr time.
Rajiv

GL account for movement type 309

How to find GL account for movement type 309. Tcode etc
Stop Cross-Posting

Hi,
Try using transaction code OMWB (press cancel on pop-up) >
Press "Simulation" button and enter plant + mat + movement type >
Press "Account assignments" button
Dr/Cr G/L accounts displayed for posting lines.
Kind regards,
Robert

Default GL(123456) for movement type 221

Similar Messages

Maybe you are looking for