I tried with exactly same data in my system and got PO qty as 453.592 KG. Do you have any user exist implemented to round off order qty or doing any calculation? You can also check with you techincal team, why order qty calculation or conversion is wrong. But route cause of your warning message is PR qty and PO qty is not same.
↧
Re: Order Quantity violates rounding rules - ME386 when converting Req to PO.
↧
Re: Subcontract component consumption with MIGO Goods Receipt.
Ashok,
Thanks for your answer. I agree that the root problem is a training / discipline issue.
Can you explain more about the Subsequent Adjustment option in MIGO.
In my experience, the only way to correct the problem has been to cancel the original receipt document, and re-receive it correctly. Is there another function to consume the component to the purchase order without the need to cancel the original receipt ?
↧
↧
Re: Subcontract component consumption with MIGO Goods Receipt.
Thanks to all who have answered.
We already have the "Propose OK function in the future" indicator set, and by default, all items are marked as OK. The problem occurrs if the receiving clerk manually removes the OK indicator from a subcontract component, or sets the component to zero.
In my opinion, this is a training / discipline issue, but my users wanted me to check if there is a way to prevent it.
↧
Re: Vendor Subrange question
Satish,
Thanks a lot. Your instruction is very helpful. So, it looks like I have to create additional two vendor as an account group 006 for OA. Then, when I cut he PO for with vendor 12345, it picked up Ordering address as Detroit since my info record sub range = GLUE. At t he header of the PO under PARTNERS tab, I do see OA= Detroit. May be, I am little bit confused about the vendor subrange. I thought vendor subrange is used to avoid creating another multiple vendor master.
Also, Jurgen L is saying "it is not mandatory to use a vendor from account group 0006, it is certainly possible to use a vendor from a different accoutn group" is that a true statement?.
↧
moving avg price should hit pricing condition type but not to be the part of invoice value.
Can some one post their suggestions please
↧
↧
Re: Vendor Subrange question
Laura,
You are right. And also as Jurgen said Using 0001 for creating 'OA' partner function is also works.. But 0006 account group is specifically for Ordering address as per sap standard..
Regards
Satish
↧
Re: Distance between plant and vendor to be updated in system
If you are not using this data for any calculation, then you can maintain distance between vendor & plant by using vendor classification data (you need to create new class and chars to capture distance for a plant) or by extending vendor to plant level data and maintain distance in any field which you are not using.
↧
Re: How to check split valuation change log
Yes we do have maintained the valuation type, but for this material valuation type is not there without this PO got created, if the user make the goods receipt definately it will also ask valuation type, and point is here how this material got created with valuation catogory S, if I can say create new material to user he will ask answer for this material.
Thanks
Mahesh
↧
Re: Subcontract component consumption with MIGO Goods Receipt.
investigate the first drop down box on the upper left in MIGO, this has the activity, here you should find the subsequent adjustment
Alternative the old transaction MB04 is still there.
Posting a Subsequent Adjustment (SAP Library - Managing Special Stocks (MM-IM))
↧
↧
Re: How to check split valuation change log
in the material master, next to the material description you find a blue info button.
After clicking it it will show you who has created which view and when. Then just call this person and let explain how it was created.
The OSS Note 155874 - Change valuation category in material master explains all checks that are done before a category can be changed. And explains as well what would happen if you change the category despite of this transactional data.
If you do not have access to download SAP notes, then ask your basis team or another consultant to do it for you. Maybe you will find it in the Internet, even its publishing violates copyrights.
As changes to customizing are usually done in development client, you can certainly find its transports in the system
↧
Re: Make Purchasing Group Optional in ME41
Hi,
Try this.
If you wish to have optional selected for ME41 you will also need to
make the change to AKTH, AKTV, ME42 and ME43.
I mean from AKTH,AKTV,ME42 and ME43,please select purchasing group as 'optional'.
With Regards,
Jaheer
↧
How to read the field FASU1 in table T162
Hi Gurus,
Can anyone explain me, how to read the field FASU1 of table T162 for GR-based IV on ME21N.
Thanks
Puneet
↧
Re: How to read the field FASU1 in table T162
there is no such field in table T162.
I think you are talking about FAUS1 field
go SM30 enter table name, then click customizing button and SAP will take you usually to all the IMG activities that change fields in that table.
e.g. IMG > MM > Purchasing > purchase order > Define screen layout at document level
I am not on a system now, but if I am not mistaken, then you see there plus and minus signs, points and spaces. which means mandatory, optional, display only and hidden. I just do not remember which sign stands for what.
each character represents a field, from the left to the right like it is from top to down in the customizing activity.
↧
↧
Re: Make Purchasing Group Optional in ME41
Hi Tareq,
Leave a field (EKGRP) blank in material master and leave the blank in Vendor master purchasing section but at a time of creation of info record it will ask. you can maintain after pur group.
other option already explain by expert above.
Regards
Sanjeet Kumar
↧
Open text Suspected duplicates
Actually in opentext there is a BDC for MIRO , when user choses to post invoice , this BDC is called after which depending on the success of the BDC , the open text tables are updated with various things like the invoice document number....
what really happened in this scenario of suspected duplicate is that the acounting document for that PO is present already when user tried to post the PO invoice....I checked the accounting document its creation date + time is same as in the workflow log of the first time user executed the step post PO invoice... which gives us the suggestion that the first time user clicked on post po invoice it was successful, however it did not updated the open text tables...
I tried the same case , by successfully creating a invoice document after the BDC and skipping the updation of opentext tables, however i still did not get the suspected duplicate exception when i again tried to post po invoice the second time , it just posted it with a different number and updated it on the second time....
so wanted to know if someone actually knows how this suspected duplicate exception might occur or just have an other opinion what could have occured ... i hope it was clear this time... 
BDC logs are saved in a table , however open text always keep the latest log and deletes the previous log , the user executed 3-4 times so the BDC log for the first time is already deleted which would have been helpful.....
one more thing you said that it depends on the vendor master customizing settings , would this setting be for all vendors or specific vendors ? , if only specific vendors are checked then may be i tried with a vendor for which this was unchecked ...
thanks for your help..
↧
Open text Suspected duplicates
customizing for duplicate invoice check is valid for all vendor that have the box for duplicate invoice check activated in vendor master company code view.
↧
Open text Suspected duplicates
thanks... will check with such type of vendors...
↧
↧
Re: How to read the field FASU1 in table T162
Hi,
Refer below help link to understand the field selection (FAUS1),
http://help.sap.com/saphelp_46c/helpdata/en/ad/2d547bb435d1118b3f0060b03ca329/content.htm
Regards
Vijay
↧
Re: Make Purchasing Group Optional in ME41
Hi Tareq,
Make the field selection key optional at transaction level (ME41), activity type level (creation mode), at document type level and finally at item category level : ANA, AKTH, ME41, PT0A. Check the below link to understand the functionality in more detail.
http://help.sap.com/saphelp_46c/helpdata/en/ad/2d547bb435d1118b3f0060b03ca329/content.htm
Regards
Vijay
↧
Re: Prices in Condition Record
Hi,
Refere this document to understand how the pricing conditions are determined in P.O.
Regards
Vijay
↧