MIGO error
Hi All,
This regarding Txn MIGO.
In this txn the screen changes with the business transaction we enter e.g. if we choose Good Reciept the Screen fields and heading changes to Good Reciepts, and if we choose Transfer Posting The screen changes accordingly...
In actual this should happen....
But in our case this is not happening ...i.e. by default it is Good Recipts Screen but as we choose Transfer Posting ,it is not changing, because of that we are getting movement type error.
We know that somewhere we have missed some config..
Please suggest..
Thanks
R
Thanks for reply Vipin,
Let me tell you what exactly is happening...
We have done a BDC for MIGO for automatically Posting for txn type Transfer Posting ...
In BDC we are using A08 for selecting Transfer Posting....
Accordingly the screen has to change for Transfer Posting with corresponding Movement types....
But in actual whn we execute the BDC, The txn Type changes to A08 Tranfer Posting with Others but the screen still shows the Good recipt Others....
dont know where is the problem...
It is working fine in Dev server but in Prod it is giving this problem and due to this it is giving us the error 'Movement type 301 is not planned for this operation"....
In production the txn type name is also changed from Transfer Posting to A08 Transfer Posting....thats why i asked earlier that does it affect the config...
so please suggest the solution....
Thx R
Similar Messages
-
MIGO error while posting..!!!
H Alli,
Getting below error while posting in MIGO:
"Account 413501 requires an assignment to a CO object"
Regards,
AmitHi
Check whether profit centre is assigned to your material at sales general plant data
If not , then give profit centre and create a fresh cycle and see
Regards
Raja -
MIGO-Error when MIGO is execute by call transaction on background
When we execute MIGO_TR or MIGO_GI in call transaction, this error is showed.
"RAISE_EXCEPTION" " "
"CL_GUI_CUSTOM_CONTAINER=======CP" or "CL_GUI_CUSTOM_CONTAINER=======CM001"
"CONSTRUCTOR"
Is there any alternate function available for the MIGO and avoiding the same error.
Thanks in advance.
WalterHi Walter,
MIGO is a SAP Enjoy transaction so BDC is not supported on the same.
Regards,
Atish -
MIGO error 'Purchase Order does not contain a confirmation control key'
Hi,
while posting GR to a PO i am getting an error ' Purchase order XXXXXXXXX does not contain a confirmation control key'
it is true that i have not defined any confirmation control key in PO, Aknowled rerd checkbox is also not ticked
Still why this message coming, what setting would be bringing this message
Please clarityHi,
Until the installation of Note 589422 (with SP SAPKH46C43) you could due to a program error - create a delivery even though the purchase order did not contain any confirmation control key.
This is now prevented through error message M7394. The transfer of this check (Confirmation control key existing in the purchase order, see Note 589422) was necessary as otherwise you could post a purchase order as desired. (Refer to also Note 616944 -> SAPKH46C44)
589422 Several inbound deliveries can be created with MIGO :
"Implement the program correction.
With Transaction SE91 create message M7394 with the message text:
Purchase order & & does not contain a confirmation control key".
After you implemented this correction, when you want to create an
inbound delivery with Transaction MB01 or MIGO or with
BAPI_GOODSMVT_CREATE and if the purchase order does not contain a
confirmation control key the system displays error message M7394
"Purchase order & & does not contain a confirmation control key".
Hope this can explain the error you met.
Regards,
Mauro -
Error during MIGO-Error during maint. of delivery costs in master condition
Hi
We are getting error as below during MIGO against a PO with doc type NB:
"Error during maint. of delivery costs in master conditions, Delivery cost conditions in different validity periods not identical"
What might be cause??
Thanks
MaruthiCheck the delivery conditions in condition tab of PO.
Try to check if there are any delivery condition records mainatined.
I think the problem is mostly due to overlapping validity period. Try to change the validity period for the same. -
MIGO Error -while refering the subcontracting challan
Hi all
1.)We purchsed material from vendor A & send these material to vendor B directly for Job work ( for this we have seperate PO with subcontractor)
2.) In Material PO we tick SC vendor & give vendor B.
3.) Then made GR(with only part 1)
4.) MMBE report shows stock provide to vendor B.
5.) After that we made subcontracting challan for vendor B with reference to GR number.
6.)Then capture and post the Excise invoice no
7.) Now when I am trying to the GRN of subcontracting PO and refering the subcontracting challan , system is throwing an error " Challan material is different from material document "
Usualy in the normal scenario, while doing the 541 movement type , we use to refer the subcon PO(by making the PO no field mandatory/optional against the movement type 541 in customization ) , as during MIGO, system checks the PO no against the material issued and PO against the GRN is being done, if it does't matches, then the above error comes.
But in the above scenario, there is no way to give the reference of giving the subcon PO during 101 "o" . that is why , this error is coming.
Please suggest the way out , how to deal this scenario.
Thanks & Regards
Nitin Chhabrahi nitin
pls refer following link
Re: SUBCONTRACT J1IFQ ERROR
Vipin -
Cannot post Goods receipt in MIGO Error message"Field Business Area requird
Hai
I am posting Goods Receipt ( MIGO) with Reference to Purchase Order its having 47 Line item material. When i will doing Goods Receipt with rreference to po number its triggered error message in :Message No F5808 Field business Area is a Required field for G/L account 1180 300000 . for only particular line item 47 material shown error..
i checked all the settings in MM Automatic determination And G/L element, field variants, posting keys.. but everything configured profer settings..why particulat materail it shown error? how to resolve this error?Hi Thiru,
A somewhat late aswer, but it might be helpfull for other users with the same problem. You can solve this problem by assigning the division/valuation area to the business area. Follow the path below to execute this:
SPRO - enterprise controlling - Consolidation - Integration: preparation for consolidation - Preparation in the sender system - Further settings for Business Area Consolidation - Materials Management - Assign Division/Valuation Area to Business area.
Under Enterprise structure - Assignment - Logistics General, you will find a similar function. First execute option 1 or 2 here and then execute option 3. This makes it work as well, exept that it will not be recorded in a proper transport. The first option I gave for assigning is properly transportable.
Greetings,
Sjaak van den Berg
Magnus Technology Consultants
Edited by: S. van den Berg on Aug 14, 2009 1:09 PM
Edited by: S. van den Berg on Aug 14, 2009 1:10 PM -
Hi,
While creating MIGO in STO process,we are getting error "Maintain Vendor for the excise invoice"this is the first time we are doing in our company
STO-2PLANT in 1Sales Org
Process
1)ME21N
2)VL01N
3)VF01
4)J1IIN-for Excise posting
5)MIGO
Every thing is ok up to J1IIN but while creating MIGO i am getting that error.
Regds
NAGDear Naga,
Perform few checks:
Customer Code at both the places must be same.
Note-down the Customer Code assigned to the Supplying Plant,in:
SPRO --> MM --> Purchasing --> Purchase Order --> Set up Stock Transport Order --> Define Shipping Data for Plants
Now, Go to, T. Code: XK02
Here, in to Screen: Control, assign the Customer Code and Save.
Maintain the Vendor Excise-Details in T. Code: J1ID.
Maintain Condition Record in T. Code: FV11
Best Regards,
Amit -
Maintain Vendor Excise details - MIGO error
Hi all........
Im doing Stock transfer from one plant to another plant within a company code through stock transport order.
I created STO in receiving plant, after the I created outbound delivery in VL10B and PGI in VL02N in supplying plant. With Post Goods Issue Material document I created Excise Invoice in J1IS.
While doing MIGO in receiving plant I hve to enter the same Excise Invoice number which I created in supplying plant.
When I enter the EI number system is recognizing the number. But the problem is when I click on save its giving error "Maintain Vendor Excise details".
In sto we will not mention any details then y system is giving this error.
Please suggest.
reg
Durga RamHi Durga
There are few check points to resolve this problem
--Check for vendor master for plant XYZ & in control data we have to maintained the customer no. e.g. 999 for XYZ
---Check in J1ID Chapter id,Material and Chapter Id Combination whether you have maintained or not, if not maintained it
--- Check J1ID whether you have maintained the Vendor excise Details for That supplying plant, if not Maintained it.
i hope this will get resolved your problem
Thanks -
MIGO Error for subcontracting scenario through PO
Hello All,
We have PR PO process where PR is created for subcontracting and then PO with BOM explode in PO for same material for in and out.
User is getting error while posting MIGO for Subcontracting GR though PO.
Though 541 stock has been transferred to vendor
and though PR PO process we are doing subcontractor PO and MIGO 543 movement
getting error with blank message in migo
Message no. M7895
Due to this not able to complete MIGO and stock transfer to plant from vendor
Please check the attached file for error
Thanks and regards
Hard VoraI think it is still possible to place the cursor on the message and to click the icon with the question mark, this should then hopefully bring a pop-up with the message number.
from there you can investigate further. e.g. if it is a Z or Y message, then it is a home made message, and you can get the info who created it from transaction SE91.
In any case you should do the following in Migo:
Open the sub-items before you press Save or before you click the Check button. Only then you can know whether the message belongs to the header or to the item. -
MIGO Error- Order Unit & Order Price Unit
Hi,
I have a material whose base UOM is EA & alternate UOM is KG.(Conversion is maintained in the Material Master).
I have created a PO for this material with order unit as EA & order price unit as KG.
Now,when I try to do the GR using MIGO,I get the following error message:
"Quantities cannot be converted for the the Material".
i.e, the system is not able to do the conversion between EA & KG.
How to resolve this issue? Please advise.
Thanks,
KaveriHi Mallinath,
I had tried a similar thing with another material & it was working fine.
To summarise my problem once again,please see the below data maintained by me:
MMR-
Base UOM in EA
Alternate UOM in KG (25 KG = 1EA)
PO-
Order unit in EA
Order price unit in KG
With the above settings,MIGO is giving me the error:
Quantities cannot be converted for the material.
Please advise.
Thanks, -
MIGO error with Return Delivery
Dear guru ,
We have a requirement where we:
1.) Create a PO for a material using ME21N.
2.) Post GR using MIGO
3.) Post Return Delivery using MIGO with movement type 122, with "Return Delivery" flag set.
When I post return delivery the system send me this error :
VL 384 Sales Unit is not valid for item 000010
How can I solve this problem ?
Thanks in advanceHi,
For return delivery, system always check the settings of material master in the distribution channel of intercompany transfer.
If you have 2 dis channels for e.g 01 , 02
And 02 is your intercompany dis channel then you have to maintainmaterial master in 02 for retur delivery.
Kindly check the sales unit in this dis channel. You may get some help for this.
Regards
Karan -
MIGO Error against SUB-Contract LB031
Hi Expert,
i have a Sub-contract scenario, both material and component under this material are managed with HU.
step is:
1. Create a sub-contract PO ME21N
2. Create a delivery to Vendor for this component via ME2O
3. G/R against this sub-contract PO MIGO
4. Create a TO against the inbound Delivery Note which create in Step 3 LT0F;
5. Confirm TO LT11;
6. Post good receipt against Delivery note which create in Step 3 VL32N
then there is a error message "Of the required quantity of material H000003786, 2.000 EA remain(s) open
Message no. LB031"
I checked there is enough component stock under vendor in MMBE.
Can anybody help me?
Much appreciate.
RockyHi All,
Thanks for your reply.
+"what is the PO quantity? what is the receipt quantity? is H000003786 the material you ordered or the material that is consumed?
what is the percentage of this material in your BOM if it is the component?"
PO is 5000EA, and receipt quantity is 1 EA.
BOM structure is:
1EA F0000007677 map 1EA H000003786 (Include 2% component scrap)
So 1 EA F00007677 G/R requires 2 EA H0000003786. And i need to backflush 2EA H0000003786.
You are talking about PGI and saying you have created TO in LT0F !! (which is for inbound delivery Putaway) !! Iam asking you to create a TO in LT03 and confirm. How do you issue your goods in IM? You have to create and confirm the TO for the same transaction. Pls be clear and revert.
When i do G/R, only Inbound Delivery note is generated, so i can only to create TO via LT0F. How can i create outbound Delivery Note during MIGO transaction?
Thank
Rocky -
MIGO Error for subcontracting PO
Hi,
This is regarding the error which I am getting when I am doing a GR using MIGO for a subcontracting PO.
The Error message is as *'of the required quantity of material &, && quantity is open'*. This error comes for few plants.
I am working on 46C version of SAP.
OSS note 526850 says this is a program error in version 46c but then why this error is not comming for all plants .
Any helpful inputs related to this issue will be rewarded with points.
Thanks in Advance.I think it is still possible to place the cursor on the message and to click the icon with the question mark, this should then hopefully bring a pop-up with the message number.
from there you can investigate further. e.g. if it is a Z or Y message, then it is a home made message, and you can get the info who created it from transaction SE91.
In any case you should do the following in Migo:
Open the sub-items before you press Save or before you click the Check button. Only then you can know whether the message belongs to the header or to the item. -
M7242: MIGO Error Valuation control differs
We have old SalesOrder Stock in our system. Therefore we wanted to do MIGO (MB1A) Movemettype 551 Special Stock Indicator = E.
We receive the following Error Messag: M7242: Valuation Control between material master and special stock differs.
Do you have any suggestions/solution?
SAP ERP 6.0
OSS 896806 implemented.
Edited by: Hartmer2 on Mar 30, 2009 5:24 PMsolution provided in OSS Note 661856 - Correction of valuation indicator KZBWS with 0 stock
Maybe you are looking for
-
Mac Mini defaults to 640 by 480 and can't be reset?
Hello fellow macfolks... I have a Mac Mini that I use only on an occasional basis. Tonight I connected it to my trusty, known-good NEC 20 inch monitor, and lo and behold, the mini boots up at 640 by 480 resolution with NO other choices in teh display
-
MSI Z97-G43 Gaming microphone not working
Hi, I installed my new MSI Z97-G43 today but my microphone doesn't work... It still works on my old computeur... I tried to connect it in front panel too, it doesn't work too... What can i do? BR
-
How to use Function Module ARCHIV_CREATE_TABLE.
Hi Gurus, I need to use FM-- ARCHIV_CREATE_TABLE in my Report. Please help me to use this function module as I was not able to find the documentation for the same. Regards, Amit.
-
How to make swatches persistent from one document to the next?
I want to have a custom swatches in my workspace each time I open a document. How can I make swatches persistent in InDesign?
-
Error in BizTalk Web Service publishing wizard BizTalk 2013
Hi, I am facing an error when i am trying to publish a BizTalk orchestration as a Web Service. It is a very generic error message that is popping up. Failed to create project "http://localhost/mycode.Orchestrations_Proxy". Object reference not set to