Hi,
Maintain the allowed posting period as current fiscal year only in OB52 for the company code and test again!
Regards,
AKPT
↧
Re: How to restrict the invoice posting in previous year period
↧
Re: Internal Order Mandatory in PR, PO for Specific GLs only
Thnakx Rosh
Its working
↧
↧
Re: MEMASSPO does not support upload of manual pricing condition
Hi,
If its a manual condition, I would suggest to check the BAPI: BAPI_PO_CHANGE
Regards,
AKPT
↧
Re: MEMASSPO does not support upload of manual pricing condition
I would do that, thanks Prasoon.
↧
ABC classification for material
Hi gurus,
My client wants to classify materials based on the usage level manually. Will ABC indicator in material help this. Also I am not using ant inventory cycle count or any classification based on the usage.
I tried to give A, B & C for same material for three different plants and when I checked in MC40 is shows total value equals zero and no analysis performed. Please give your suggestions for this.
Thanks
Sathish
↧
↧
Re: Unable to Change Net Price in Info Record
Can you try using ME11 for the same Inforecord and maintain the Purchasing Data & Conditions and let me know what error do you get.
Regards,
Niranjan
↧
Re: Vendor is being considered as Intercompany plant even without this setting
I am able to check in production. you are bang on.
That's the issue which you pointed out.
↧
Is there BAPI function available for tcode ME2ON
Hi SAP experts,
I am wondering if is there any bapi function available to be used in standard SAP ECC 6.0 for tcode ME2ON?
If there is, is there any sample function that i could refer to?
Thanks.
↧
PR visibility to End user
Hi All,
We have started PR to Process for our client but PR is getting visible to End User.
As concerned department has created their requirement in PR and forwarded PR no. to Purchase department but the same is not visible to End user.
There are two user who is having full authorization( Like PO creation, Material creation etc) as end user , they are able to find PR but some end user who don't have full authorization are not able to find PR.
Screen shot is also attached for authorization.
Please help for this issue.
Regards,
Shri Prakash
↧
↧
Re: Unable to Change Net Price in Info Record
Hi,
Check the pricing procedure determined by the vendor schema, it will not be having PB00 condition.
Change the vendor schema with pricing procedure having PB00 & then go to ME12 and you will be able to access conditions tab.
Regards,
Sangeetha V
↧
Re: PR visibility to End user
There is no screenshot, you have to load it up from your local directory to this discussion by clicking the photo icon here.
The command /nsu53 should actually show which authorization is missing. Get support from your local authorization team in such cases.
↧
Re: Unable to Change Net Price in Info Record
Hi,
Info record usage condition type PB00, better change the settings for that condition type.
Use t.code:M/06 and SELECT CHECK BOXES of Amount/ percentage and Value in Changes which can be made segment and save for PB00 condition type.
Also update the changes of PB00 condition type in the MM pricing procedure which is used for your info record* in t.code: M/08
Now try your expected requirement on changing value in the info record.
Regards,
Biju K
↧
Re: PR visibility to End user
Hi,
For those users PR not authorized, Use their user ID and display PR with ME53N and later have SU53 screen to find authorization object with value/values.
Use authorization concept and allow those users to view PR for particular that department /purchasing group by allowing those values for authorization object etc.....Discuss with Basis and S &A team.
Regards,
Biju K
↧
↧
Re: How to restrict the invoice posting in previous year period
Exactly for my scenario fi period is not closed for p12 2015. but we need to restrict posting in P12 2015.we need to post in current period.
↧
Re: How to restrict the invoice posting in previous year period
Hi Upendra
You can just close the p12 in 2015 through OB52 and that should not allow your postings to happen in P12, 2015. If however, for your annual closing you still want p12 to be open, but still the general postings like IR etc should happen only to P1, 2016, you can introduce an authorization group in OB52. This will ensure that only specific set of users are able to post to P12, 2015 to complete the year end closing and most of the other users who do daily logistics transactions will not be able to post to P12, 2015. The below link should help on the same
OB52 – Maintain posting period control through authorization group.
regards
Sanil Bhandari
↧
Re: Po delivery date should not be less than PO Doc date
Dear Himanshu,
Use BADI: ME_PROCESS_PO_CUST to put a check on delivery date not less than PO document date, for this you need to take help of an ABAPER.
↧
Re: unable to save in po
First question: PO printout issue - I discussed with abaper what you had told.
Thanks you Sir. I am discussed with abaper he wants the sample in quality server.
Second question:
Afterthat, while creating po in quality server its throwing an error:
Error:1
"
Purchase order still contains faulty items
Message no. MEPO000"
Error:2
Error : Item 30
&5 & 6 &7 &8
Item 20 Sch. Line 1
↧
↧
Re: unable to save in po
Hi Niranjan,
Thanks for your question. Here I asked two different question.
1. PO print out issue with 19 lines instead of 12 lines in production server.
2. while doing sample in quality server 19 lines or single lines unable to save the po. It's throwing an error.
Question 1 : was answered by Mr. Biju Sir. Thanks.
Question 2: expecting the answer from your goodself.
Kindly look attached screen shot for your reference.
Regards,
Vivek
↧
Re: WAERS field in EKKO for RFQ not getting updated
Hi,
If the currency is not maintained in vendor master at the time of creating (ME41) RFQ, the currency field in the header (EKKO) will be blank only. If you maintain the currency later in the master data, it wont update in the already created purchasing documents. In this case, you have two options:
- Create new RFQ's and test the scenario again. Please remember to make the order currency as mandatory in vendor master to avoid this issue in future.
- Make the currency field as "optional" in ME41 and ME42 in the field selection for RFQ in the path: OLME - RFQ/Quotation - Define Screen Layout at Document Level. Maintain the currency field as optional for the field selection keys ME41 and ME42. Now, go to ME42 for already created quotations and go to header details to maintain the currency manually as shown below:
Now, try again in ME47 / ME48 / ME49
Regards,
AKPT
↧
Re: SFG inhouse, Purchased order not create if procurement type E
I have completed test but it not shown the error message find the below details
Please suggest me more
Regards
Akshay
↧