Error: Movement type 101 k not planned

Hi Freinds,
While doing GR for Consignement framework order , im getting this error as 'Movement type 101 K is not planned. (Entry is not copied over)'.
Could u help me with this please.
Thanks
Akkshaya

Hi,
Enter the item category K for the consignment item in your FO . To ensure that the goods receipt is posted to the consignment stores and an invoice receipt cannot be generated for the item.
BR
Diwakar
reward if useful

Similar Messages

"Movement type 123 is not planned (Entry is not copied over)".

Dear All,
While executing Movement Type 123, for reversal of a vendor return i get an error message "Movement type 123 is not planned (Entry is not copied over)".
Transaction used : MIGO
Goods Receipt | Purchase Order | Movement Type 123
Any specific reason as to why the system is not allowing me to execute the movement. And what is the procedure to overcome this error.
Shall await your reply
Thanks
Shabeen Buhary

dear shabenn
It is absolutely true, you can perform 123 movement i .e. cancellation of return delivery only through reversal procedure of movement type 122.
If you are trying to do MIGO for 123 movement, the system supposed to throw out same error.
If you returned a goods receipt using movement type 122, you can reverse the return delivery using movement type 123. This movement type has the same effects as movement type 101.
Please revert back if any query still exist...
Rahul

Movement type 311 is not planned in Back Ground Processing

Hello,
I have created a BDC to run the transaction "MIGO" with movement type 311.
Its working fine in foreground. But i execute in Background i am getting a error message "Movement type 311 is not planned for this operation".
I think there should be some config settings. But i don know where to check configuration ?
If anyone has any sugggestions or answers , Pls post here.

Hi,
Better you can use the BAPI "BAPI_GOODSMVT_CREATE".
Check with your Functional Consultant for this issue......
You may also look for an OSS note and in Last raise a ticket to SAP..but there is no surety that every txn will work with BDC in Background Mode.

Movement type 101 does not currently support

Dear Experts
there is an error occur at the Time of MB31 with 101 Movement type
Movement type 101 does not currently support serial number Management.
Rgds
Pankaj

Hi
Serialization config is missing for 101.
Check in below config
spro>plant maintenance & customer service>master data in plant maintenance & customer service->technical objects>serial number management-->define serialization attributes for movement types
Check with the help of PM or CS consultant
Regards
Antony

Movement type 101 does not currently support serial

Hi experts,
I'm trying to realize MIGO for a PO with a material with serial number.
The error msg is " Movement type 101 does not currently support serial number Management." IO306
I already config. spro>plant maintenance & customer service>master data in plant maintenance & customer service->technical objects>serial number management-->define serialization attributes for movement types
And
Plant Maintenance and Customer Service -->Master Data in Plant Maintenance and Customer Service -->Technical Objects --Serial Number Management -->Define Serialization Attributes for Movement Types
And assigned the material to attributes ate MM02.
I have know ideia what else i have to do.
Is there anone here already see that?
Tks
Antonio Oliveira

try posting GR via MB01 transaction instead of MIGO and let us know if you are getting same issue.
also there are few OSS notes created for this kind of issue which has to do with maintainenance of table V_T156SY, check below thread
Movement type 101 does not currently support
yogesh

JITOM error movement type 000 is not allow (check your entry)

Hello experts,
In transaction JIOM i try to do an ACTION, but the system display below error message.
movement type 000 is not allow (check your entry)
Could you please help me this is very urgent..
Regards!!
Hugo

Hello Hugo,
Can you clarify what the functionality of transaction JIOM is? I am assuming that this is your own transaction? Going from previous cases of error L3001 being raised, this is almost always associated with the creation of TO documents, can you confirm this is correct?
Can you check that the Item category is relevent for picking? (Transaction 0VLP)
Regards
Stephen

Migo (Movement type 101) does not update quntity in the report.

Dear experts,
I have a custome report for goods receipt (ABAP Query).
In this report, quntity (unrestricted stock) is not updated when I do MIGO (mType 101). The quntity however, is updated in MMBE unrestricted stock columm after MIGO.
Could you please help me how to make quntity updated in the report when I do MIGO with movement type 101?
I thank in advance for all replies.
Jaan
Edited by: Bhajan Singh on Feb 9, 2010 10:19 AM

Thanks R.S. Nambi for your rpely.
The question is solved.
I went to query, then Additional fields and picked movement tyep-quntity field, went to Local fields and added complex calculation for mtype 101.
I am going to close this thread.

Error in MIGO Movement type 101 E is not planned.(Entry is not copied over)

Hie Experts,
I had created a process order for XYZ material. Now i want to assign this goods receipt to sales order. For this i am trying to go MIGO with mvt type 101 & special stock indicator as 'E'(order stock). I am facing the error as "Movement type 101 E is not planned. (Entry is not copied over)".
Can anyone help to solve this error.
Regards,
Piyush

Hie,
Thanks for your valuable response. But, my scenario is like this. I am doing goods receipts against PRODUCTION Order.
I want to take this stock as Sales order stock(Special Stock).
Can u pl help me for this scenario.
Regards,
Piyush

Movement type 101 Q is not planned. (Entry is not copied over)

Hi,
I have created a purchase order with account assignment to WBS element.
While i am trying to create migo using 101 Q movement type, i get the following error.
"Movement type 101 Q is not planned. (Entry is not copied over)"
if i post the migo using only 101 (without mentioning Q), project stock is not shown.
Please help me create a GRN with project stock.
Cheers!
AUN

hI,
check whether below link useful or not.
Movement type 101 Q is not planned. (Entry is not copied over)

Some key figure are not update for movement type 101

Dear All,
I have done load for Inventory and now i am finding that for some material the with movement type 101 the key figures are not getting populated, for these materials the values in characteristics is getting populated fine.
I have loaded the data according to stranded procedure in "How to Load...."
I have checked the values of material in R3 and it is there.
Example of the record::
Material    Plant Movement type Calender Day    quanity Base Unit
10101      01       350                     01.02.2006     20             KG
10101        01       101                     05.07.2006                      KG
10101         01      101                      10.07.2006                      KG
The Quantity is not appearing in second and third record.

Hi,
Please check whether you have set ''Rule groups'' at transfermation level . There you can set the conditions like materials having movement type X can be updated to one Key Figure and material having movement type Y can be updated to another Key figure.
Please check whether you have set this option at transfermation level.
For example, may be in your case materials from different plants are updating to different key figure.
Thanks,
Edited by: kavitha nagandla on Feb 17, 2010 7:19 AM

Field_PERNR available on movement type 101

Good Day
Please can you look/investigate whether it is possible to make personnel number an optional field for the movement type 101. In FI I am making the personnel number an optional field for the GL accounts:
o                    If the personnel number field is required in FI but optional in MM, the field may not be populated in MM (because itu2019s optional) resulting in an error when trying to post a MIGO transaction because a FI document cannot be created.
o     Currently personnel number (field u2013 PERNR) is not available as an entry field on the MIGO transaction for movement type 101, you cannot add field PERNR to the MIGO transaction because you get the SAP standard error message Nr: CZ287 u201CField PERNR is not allowed for transaction type 101u201D
Please can you advise whether it would be possible to add the field_PERNR to the movement type 101.
Regards
Ropetra

Hi,
   Mvt 101 derives some settings from the PO. So if you can get PERNR optional in the PO , it should then be in MIGO for 101.
Kind regards

Movement Type 101 K

Hello,
I have a question regarding movement type 101 K. Currently we are trying to do vendor consignments and I have came across few documents stating to do a movement 101 K when doing MIGO. I do get an erro message stating that Movement type 101 k is not planned. My question is in the drop down list for movement types, am I suppose to see 101, 101 K for special stock indicator? I do see 201 K, 501 K and etc... But for 101 I do not see one for 101 K. Is this movement type setup by default? If not how can I setup movement 101 K? Please advise.
Thank you

Hi
do we have to create a purchase requisition(PR), then a consignment purchase order (PO), then do a MIGO with 101 K will that create any accounting document once receiving the material?
Yes as this is from an External source you have to create a Purchase order & then MIGO for the same.Creating PR is SPRO setting whether directly create PO or always with reference to PR.
MIGO must be done in order to get payment to vendor & exice etc.
Do we use movement type 411 K to transfer posting consignment to own? Will that create any accounting documents or will hit any G/L accounts?
In OMJJ check the entry in account grouping tab against the 411K.
Check account assignment
Indicates that the account assignment is checked.
If this indicator is set, the system checks whether a G/L account or an account assignment has been specified on the item screen. If so, the system copies this data to the posting line.
If this indicator is not set, the system always uses the G/L accounts or account assignments determined automatically.
means G/L account is hit when you are transfer posting consignment to own.
Regards
Sujit

Backflush Components With Movement Type 101 When Confirm Production Order

Hi PP Gurus,
I found that we have a backflushing material (procurement type: F) in 'Good Movement' with movement type 101 instead of 261.
The movement type of this material (procurement type: F) in reservation is 261. How did system determine the movement type 101 there?
Is there any user exit used there?
Appreciate any help. Thanks.
Regards,
Sun Qiang

>
Qiang Sun wrote:
> Hi Arun,
>
> The control key has not been changed.
>
> In another production order, the error ocurred on another component which is the first line in 'Goods Movement'.
>
> Cheers,
> Sun Qiang
Hi,
Pl check in component overview which operation has been assigned to pericular material in Operation tab.
It should be 10.
Arun

Movement type 647 does not currently support serial numbers management

we can't do "shipment start/PGI for DOWN shipment 1178184 DN# 40309339.
Error message " Movement type 647 does not currently support serial numbers management" see also attachment
Error is like that
Stop : Save Shipment
Stop : Shipment 0001178184 :Action for Shipment start
Read Activities profile ZPGI
Main issue
Stop: Movement type 647 does not currentely support serial number management.
Delivery 001114455 in shipment could not be posted GI
Ssome problem with the movement type 647.
what I understand is, its a SD movement which place the material in transit and automatically executes
the 101 movement. If possible please help in this matter.
Pls help what exactly issue and resolution .
Regards
Vicky

Check this thread
[STO with delivery in 1 step (mvt. type 647) with serial numbering |STO with delivery in 1 step (mvt. type 647) with serial numbering]
thanks
G. Lakshmipathi

Mb51 trx (movement type 101) - Doc info- FI Doçuments takes ages

Hello
We are experienceing performance problem when accessing FI document (FB03) from MM document.
in praxis this means when choosing an todays document in mb51 trx (movement type 101) ->Doc info->FI Doçuments
it takes ages to get FI document
Does anyone has idea how to make system faster in this regards
Thank you in advance

hi
check out this SAP Notes
555893 MB51: Preventing runtime error DBIF_RSQL_INVALID_RSQL 15.05.2008
848474 MB_GET_MM_MATBEL: Performance problem 21.08.2007
857311 MB_GET_MM_MATBEL: Performance problem / error
921164 MB51: Improving the runtime using database hints
1608810 MB51: Enhancements for multiple account assignment MAA2

Error: Movement type 101 k not planned

Similar Messages

Maybe you are looking for