Hi Taskin,
Maybe you should not allow account assignment prior to the Release? That can be done using the same approach with user statuses setup.
Availability control takes place at the time of the event, now you are raising commitments without active availability control, but next you want availability control to look back and check the history.
Regards,
Paulo
Hello,
Please consult your ABAP person for it.
Best Regards,
R.Brahmankar
Hello
You should consider that the SCN is not a forum for ordering free technical consulting. It is a collaborative community where people voluntarily help you to understand things better in the SAP world.
On this thread you have already received several suggestions and references for the documentation, but there is a limit of how far can we help you on a thread.
Now it's time for you to read the documentation, study this scenario in detail, read the documentation for the mentioned BAdIs and discuss with your ABAP consultant, in order to create an implementation of the suggested BAdIs and solve this issue.
You may also refer to the following documents for more details about the BAdIs on MRP:
Making an element not relevant to MRP or MD04 using BAdI MD_CHANGE_MRP_DATA
Regards
Caetano
Dear Caetano
Indeed its not for ordering free consultant. But I tried to implement Badi but it didn't work
I already have marked some answers helpful
Now, I have got a solution today which I am going to post here
my first query was about the report:
Go to ME5A, select creation indicator 'MRP created' PRs, select processing status 'B' i.e. PO created and tick 'partially ordered'
here you will get firmed PRs and some of them may be fixed
now run ME5A again and just select MRP created PRs and select 'fixed pr' from dynamic selection.
Now, MRP does not delete firmed PR so once you get the report, just close the PRs manually. For the first time, it will be a hectic job but if you make it SOP or check the report before executing MRP then your system will be smooth
Dear Experts,
After scheduling a Job via NWBC (NetWeaver Business Client), we noticed that in transaction SM37, the job is cancelled.
In the Job log, we see the message Job cancelled after system exception ERROR_MESSAGE.
For more information, see attached screenshot Job Cancelled.
Any ideas, please?
Thanks & best regards,
Sreenu
Hi SCN,
I have a client who is using RLM as part of their SAP system.
Scenario:
When MRP runs a Stock Transport Requisition is created with Item Category U. For UNBW materials all comes unstuck because the system requires an account assignment category. However, our STRs are not account assigned for MRP triggered requirements.
So when the conversion program O3O_SC01 runs it creates the STO but fails to create the follow on PR as no account assignment has been entered.
My question:
How can we best handle UNBW materials where STRs / STOs are generated from MRP but are non account assigned, so that when the follow on PR is generated the conversion program does not fail?
Any direction would be greatly appreciated.
Cheers
Sam
What are the Inputs we need to provide for below functional specification?
Business requirement:
During PR( ME51N ) creation system message required for available stock in SAP. Window message required with option TO CLICK "YES OR NO", and End user able to know availability of stock, while creating the Purchase Requisitions (PR) .
working fine for me. thanks
Hello,
In ME51N select the option "material stocks" under the an Environment tab in menu bar
or Go to [Quantities/Dates] tab, and press "availability check" button.
You can implement BADI like ME_PROCESS_REQ or ME_REQ_ATP_CHECK
Best Regards,
R.Brahmankar
Hello,
For your plant in OPPQ you can define the Account assignment category for non valuated material under external procurement tab. Like K Cost center Account assignment category for Non-valuated material material type UNBW
Please refer SAP note 302976 - MD14: Account assignment during conversion
Best Regards,
R.Brahmankar
Dear all,
Is it reallynotpossible to updatebyEHP8withWindows20008R2?
Are thereany tricks ?
Regards
Heike
PAM says you need Windows 2012. In that case there is no other option to upgrade the system. SUM will throw out errors saying the version of Windows is not supported.
So the only option here is to move the system to Windows 2012 (System Copy) and update the system to EHP8 unless SAP/Microsoft supports in-place upgrade of Windows. In that case you can avoid the system copy.
Dear Colleagues:
I am trying to execute Transaction IW51 and getting the Error message " Notification category not maintained for Transaction 03". Checked all my configuration but couldn't find any thing. Need support.
Regards,
Junaid
Hello,
In transaction OQN0 you have to define Notification type for Notification category 03 Service notification.
Best Regards,
R.Brahmankar
Dear Brahmankar:
Its already maintained as 03. I am not sure what else can be the problem. Do you think is it because of some Installation issue as I cant even access the IW51 T-code. Besides that in DP 80 and DP 90 I am getting the same issue where I am getting the message that RRB is only allowed for service orders. Need Support.
Junaid
Please provide more information. What do you mean by 3pr incorrecting posting document? What kind of documents they are? Why do you want to delete? Is reversal an option?
Hello,
What is error message number?
Also share screen shot of Notification type configuration.
Best Regards,
R.Brahmankar
Dear R.Brahmankar: Notification category not maintained for transaction 03 Message no. IM457 Procedure The system administrator needs to correct Table T365.