MD04, Firming Indicator (urgent)

Hi All,
In MD04, i see a '' next to a purchase requisition, indicating it has been firmed by the system. I would like to know in which table i can get information for all materials having this '' for a given plant. I tried joining the tables MARD & MDTB, but the field FIX01, is not showing the data. Kindly let me know the field & the table i will get this information from. Hope my problem is clear, look forward for your inputs.
Vivek

Vivek,
I understand what you are saying. I am not an MRP expert but I will give it a shot.
The * (firmed indicator checked) that you see next to the purchase requisition in MD04 is not actually stored in any table. This is a structure field (MDPS-FIX01) and is updated when the MD04 (stock requirements list) program is called. The * next to the purchase requisition (or planned order for that matter) indicates that the purchase requisition is firmed as far as MRP is concerned (meaning that MRP CANNOT change this requisition, the 'firming' functionality is built to prevent undesired deletion of your purchase requisitions/planned orders by MRP).
Now, the interesting question is how the firmed indicator (*) is actually set in MD04 next to the purchase requisition and what is its relation to the 'fixed indicator' in the purchase requisition (EBAN-FIXKZ). The 'firmed indicator' flag in MD04 is automatically set in the following cases -
- When you create a purchase requisition manually (EBAN-ESTKZ = 'R') using ME51N, it is treated as firmed as far as MRP is concerned. Note that in this case even if you have NOT flagged the 'fixed indicator' (EBAN-FIXKZ) in the requisition, the 'firmed indicator' is flagged in MD04. This may very well be the reason why you are seeing purchase requisitions with a * next to them in MD04 but you don't find these in EBAN with the 'fixed indicator' set. I don't think you retreive this information by querying any table. You can have an APAPer debug how this 'firmed indicator' flag is actually set in MD04 but I would think the EBAN-ESTKZ drives it in this case. As a side note, I would suggest you a take a look at function module MD_STOCK_REQUIREMENTS_LIST_API.
- The 'fixed indicator' (EBAN-FIXKZ) in the purchase requisition is manually flagged by users in ME52N or programmatically flagged which will in turn trigger the 'firmed indicator' flag in the MD04 program.
- The purchase requisition is manually changed in ME52N or programmatically changed (say you change the qty, delivery date, p.org, sloc etc).
- You have converted the purchase requisition into an RFQ or a PO either for the full or partial quantity.
- The 'fixed for MRP' or the 'firmed for req. planning' indicator has been set in the release indicator for your purchase requisition release strategy. This way, you prevent MRP from accidentally deleting purchase requisitions that have already been released by someone.
The 'fixed indicator' (EBAN-FIXKZ) is automatically set in the above 3 cases which in turn will trigger the 'firmed indicator' to be set in the MD04 program.
I am pretty sure I have not covered all the cases but I am done for now:)
Hope this helps.
H Narayan

Similar Messages

Firming indicator activation for PR

hi all,
i want to tick firm indicator for PR created by MRP run to avoid deletion of PRS and creation of new one.
how to activate it in MD04 screen.
please advise

Dear,
Yes you can for all PR of that material only. for collective use MD07 select the material then click on stock reqt list tap and then go ahead as I told you in my previous posting.
Regards,
R.brahmankar

Firming indicator in MRP run!!!

hello! everyone!
can anyone tell me the importance or use of firming indicator in relation to MRP run?
when does it appear or what are the settings required?
value answers will be rewarded!!!

Hi,
If MRP generates a Purchase requisition and if nobody changes (or allocates) that requisition then it can delete or change that requisition in the next MRP run.
If the flag has been set then MRP cannot change it.
The flag is set automatically when you change the requsition or if you (fully or partially) allocate it to a PO.
this means that the reaquisition wioll stay there forever unless it is manually deleted or converted into a PO.
the most important use of this indicator is for it to be set automatically by the release strategy. The reason for this is that MRP can be run in a way that it is "told" to delete all requirements and start again. If it deletes a requisition and then decides that it still needs it, it creates the requisition again and (very cleverly) uses the same number. BUT if that requisition has been released by someone (due to the release strategy) this will be "lost" and the requisition will have to be released again. This can happen time and time again, with the same requisition authorised and then reset then authorised and then reset many times.
On the release indicator (in the release strategies) there is a "fixed" indicator. If you set this, MRP treats it as Firmed (Fixed) and so does not delete it. This can save a LOT of effort and confusion (if the requisition is no longer required you still get warning messages telling you this and so it doesn't matter that MRP cannot delete it)
So a VERY important flag.
Steve B

Firming indicator (*)

Hi All,
How to delete the schedule lines , purchase req, planned order if the this have firming indicator (*)

Dear Raj,
For Planned order,check in MRP type settings in OMDQ,for the setting with value - 1(Delete Firmed Planned Orders) - for Roll
Forward and then take a MRP run.
Dear Chandra,
Correct me if I'm wrong.
Check and revert back.
Regards
Mangalraj.S

Remove Firm indicator for Purchase Requisitions

Hi MM Gurus,
May I please know how to remove the firmed indicator (MDPS-FIX01) from a Manually changed MRP created PR.
I tried to unflag the fixed indicator in the PR but it does not do the trick. Are you able to please give me any ideas on this?
Thanks!
Jograd

any PR that is manually changed is automatically firmed.
As removing the firmed indicator is a manual activity, it would automatically result in firming when saving.
In short: it is not possible.
Delete the PR and run MRP again.

Returning Firm Indicator

Hi All,
I'm new to Postalsoft.
I'm receiving customer Full names and Business names (like Hospital Names, Surgery centers, Medical Centers, Healthcare,...) in Name field. Now I need to parse the Full Name into name parts (i.e. First, Middle and Last Names), I've a job which returns the same, but i've firm names also in Full Name field and the job parsing the firm names also. I heard that DataRight will return the Firm Indicator based on the name. Can someone help me on getting this indicator in the output. Please see the fmt, def and diq files. Would appreciate your help.
================
FMT file
================
VISIT_ID,10,C
FULL_NM,45,C
NM_PRFX,10,C
FIRST_NM,20,C
MID_NM,20,C
LAST_NM,25,C
NM_SUFX,5,C
GENDER_CD,1,C
EMAIL_ADDR,100,C
ADDR_LINE_1,50,C
ADDR_LINE_2,50,C
CITY,30,C
ST_PROV_CD,5,C
ZIP_CD_BASE,7,C
ZIP_CD_SUFX,5,C
COUNTRY,5,C
MTCH_KEY,15,C
ADDRESS_ID,14,C
INDIV_ID,13,C
FILLER,1,C
EOR,1,B
================
DEF file
===============
database type = ASCII
PW.Name_Line=FULL_NM
PW.Address=ADDR_LINE_1 & ADDR_LINE_2
PW.City=CITY
PW.State=ST_PROV_CD
PW.Zip=ZIP_CD_BASE
=====================
Output control in DIQ job
=====================
BEGIN Output Control ==========================================
Output Each Record (ONCE/ALL FILTERS) = ALL FILTERS
Undetermined Records (DEFAULT/IGNORE) = IGNORE
Default Output File (path & filename) =
END
BEGIN Create File for Output ==================================
Output File (location & file name)... = [FL_work]/Name_std_nm.dat
File Type (See NOTE)................. = ASCII
Create DEF file (Y/N)................ = N
Rec Format to Clone (path & file name)= [FL_work]/Name_stage_extract.fmt
Field (name,length,type[,misc])...... = fl_nm_err, 4,c
Field (name,length,type[,misc])...... = gndr_src, 1,c
Field (name,length,type[,misc])...... = fl_title, 10,c
Field (name,length,type[,misc])...... = fl_first_nm, 20,c
Field (name,length,type[,misc])...... = fl_last_nm, 25,c
Field (name,length,type[,misc])...... = fl_mid_init, 20,c
Field (name,length,type[,misc])...... = fl_nm_sufx, 5,c
Field (name,length,type[,misc])...... = nm_parse_score, 3,c
Field (name,length,type[,misc])...... = fl_gender_cd, 1,c
END
BEGIN Create File for Output ==================================
Output File (location & file name)... = [FL_work]/Name_nm_bad.dat
File Type (See NOTE)................. = ASCII
Create DEF file (Y/N)................ = N
Rec Format to Clone (path & file name)= [FL_work]/Name_stage_extract.fmt
Field (name,length,type[,misc])...... = fl_nm_err, 4,c
Field (name,length,type[,misc])...... = gndr_src, 1,c
Field (name,length,type[,misc])...... = fl_title, 10,c
Field (name,length,type[,misc])...... = fl_first_nm, 20,c
Field (name,length,type[,misc])...... = fl_last_nm, 25,c
Field (name,length,type[,misc])...... = fl_mid_init, 20,c
Field (name,length,type[,misc])...... = fl_nm_sufx, 5,c
Field (name,length,type[,misc])...... = nm_parse_score, 3,c
Field (name,length,type[,misc])...... = fl_gender_cd, 1,c
END
BEGIN Post to Output File =====================================
Output File (location & file name)... = [FL_work]/Name_std_nm.dat
Existing File (APPEND/REPLACE)....... = REPLACE
Output Filter (to 916 chars)......... = !empty(ap.Last_Name1) .or. !empty(db.LAST_NM)
Nth Select Type (USER/AUTO/RANDOM)... = USER
User Nth Select (1.0 - ???).......... =
Maximum Number of Records to Output.. =
Character Encoding (See NOTE)........ =
Unicode Conversion Name.............. =
Copy Input Data to Output File (Y/N). = Y
Copy (source,destination)............ = iif(!empty(ap.Last_Name1), chrtran(ap.Pre_name1,".",""), chrtran(db.NM_PRFX,".","")),fl_title
Copy (source,destinatson)............ = iif(!empty(ap.Last_Name1), chrtran(ap.FirstName1,".",""), chrtran(db.FIRST_NM,".","")),fl_first_nm
Copy (source,destinatson)............ = iif(!empty(ap.Last_Name1), chrtran(ap.Last_Name1,".",""), chrtran(db.LAST_NM,".","")),fl_last_nm
Copy (source,destinatson)............ = iif(!empty(ap.Last_Name1), chrtran(ap.Mid_Name1,".",""), chrtran(db.MID_NM,".","")),fl_mid_init
Copy (source,destinatson)............ = iif(!empty(ap.Last_Name1), iif(!empty(ap.MAT_POST1), substr(ap.MAT_POST1,1,5), substr(ap.Oth_Post1, 1, 5)), chrtran(db.NM_SUFX,".","")), fl_nm_sufx
Copy (source,destination)............ = ap.Name_Error,fl_nm_err
Copy (source,destination)............ = apc.Name1, nm_parse_score
Copy (source,destination)............ = iif(empty(db.GENDER_CD), "I", "S"), gndr_src
Copy (source,destination)............ = iif(!empty(db.GENDER_CD), db.GENDER_CD, (iif((ap.Gender_Rec = "1" .or. ap.Gender_Rec = "7"), "M", (iif((ap.Gender_Rec = "5" .or. ap.Gender_Rec = "8"),"F", "U"))))),fl_gender_cd
Copy (source,destination)............ = ap.newline,eor
END
Thanks.

I'm giving some more details about my DataRight job
BEGIN Parsing Control =========================================
Parsing Mode (NONE/PARSE).............. = PARSE
Presumptive Parse Name Lines (Y/N)..... = N
Presumptive Parse Firm Lines (Y/N)..... = N
END
*BEGIN Multiline Parsing ======================================
Multiline Number (SEE NOTE).......... = DEFAULT
Parse Address (Y/N)................. = Y
Parse Name (Y/N)..................... = Y
Parse Firm (Y/N)..................... = Y
Parse SSN (Y/N)...................... = Y
Parse Date (Y/N)..................... = Y
Parse Intl Phone Number (Y/N)........ = Y
Parse US Phone Number (Y/N).......... = Y
Parse UDPM (Y/N)..................... = Y
Parse Email (Y/N).................... = Y
END
NOTE:
for Multiline Number, specify a valid multiline field number or DEFAULT for all fields
BEGIN Auxiliary Files =========================================
Rule File (path & drlrules.dat)...... = /opt/postware/dtr_iq/drlrules.dat
Pattern File (path & drludpm.dat).... = /opt/postware/dtr_iq/drludpm.dat
SSN File (path & drlssn.dat)......... = /opt/postware/dtr_iq/drlssn.dat
Email File (path & drlemail.dat)..... = /opt/postware/dtr_iq/drlemail.dat
Int'l Phone (path & drlphint.dat).... = /opt/postware/dtr_iq/drlphint.dat
Parsing Dct (path & parsing.dct)..... = /opt/postware/dtr_iq/parsing.dct
Address Dct (path & addrln.dct)...... = /opt/postware/dtr_iq/addrln.dct
Lastline Dct (path & lastln.dct)..... = /opt/postware/dtr_iq/lastln.dct
Firmline Dct (path & firmln.dct)..... = /opt/postware/dtr_iq/firmln.dct
City Directory (path & city10.dir)... = /opt/postware/dirs/city10.dir
ZCF Directory (path & zcf10.dir)..... = /opt/postware/dirs/zcf10.dir
Capitalization Dct 1(path & pwcap.dct)= /opt/postware/dtr_iq/pwcap.dct
Capitalization Dct 2(path & file.dct) =
Default Format (path & file name)....=
Default DEF (path & file.DEF)........ =
END
BEGIN Standardization/Assignment Control ======================
Standardize Lastline (Y/N)........... = N
Non-Mailing Cities (CONVERT/PRESERVE) = PRESERVE
Case (UPPER/lower/Mixed/SAME)........ = UPPER
Use Generated Prenames (Y/N)......... = Y
Female Prename Assignment (MS/MRS)... = MRS
Provide Firm Acronyms (Y/N).......... = N
Compound LastName (COMBINE/PRESERVE). = PRESERVE
Associate Name & Title (Y/N)......... = Y
Associate Name & Title Typed (Y/N)... = Y
Associate Name & Title Multi (Y/N)... = Y
Output Date Format (SEE NOTE)........ = 11
Output Date Delimiter (SEE NOTE)..... = 2
Output Date Zero Pad (Y/N)........... = Y
Use 20xx for Years 00 to ?? (00-99).. = 20
Phone Number Format (SEE NOTE)....... = 1
Standard Phone Extension ............ = ext
SSN Delimiter (SEE NOTE)............. = 4
END
BEGIN Salutation Options ======================================
Salutation Format (FORMAL/CASUAL).... = CASUAL
Use Title Salutation if No Name (Y/N) = Y
Salutation Initiator................. = DEAR
Salutation Punctuation............... = ,
Salutation Connector................. =
Short Greeting for All Male Record... = SIRS
Short Greeting for All Female Record. = LADIES
Alternate Salutation................. =
Alternate Salutation Threshold(1-100) = 87
END
BEGIN Output Control ==========================================
Output Each Record (ONCE/ALL FILTERS) = ALL FILTERS
Undetermined Records (DEFAULT/IGNORE) = IGNORE
Default Output File (path & filename) =
END
BEGIN Create File for Output ==================================
Output File (location & file name)... = [FL_work]/Name_std_nm.dat
File Type (See NOTE)................. = ASCII
Create DEF file (Y/N)................ = N
Rec Format to Clone (path & file name)= [FL_work]/Name_stage_extract.fmt
Field (name,length,type[,misc])...... = fl_nm_err, 4,c
Field (name,length,type[,misc])...... = gndr_src, 1,c
Field (name,length,type[,misc])...... = fl_title, 10,c
Field (name,length,type[,misc])...... = fl_first_nm, 20,c
Field (name,length,type[,misc])...... = fl_last_nm, 25,c
Field (name,length,type[,misc])...... = fl_mid_init, 20,c
Field (name,length,type[,misc])...... = fl_nm_sufx, 5,c
Field (name,length,type[,misc])...... = nm_parse_score, 3,c
Field (name,length,type[,misc])...... = fl_gender_cd, 1,c
END
BEGIN Create File for Output ==================================
Output File (location & file name)... = [FL_work]/Name_nm_bad.dat
File Type (See NOTE)................. = ASCII
Create DEF file (Y/N)................ = N
Rec Format to Clone (path & file name)= [FL_work]/Name_stage_extract.fmt
Field (name,length,type[,misc])...... = fl_nm_err, 4,c
Field (name,length,type[,misc])...... = gndr_src, 1,c
Field (name,length,type[,misc])...... = fl_title, 10,c
Field (name,length,type[,misc])...... = fl_first_nm, 20,c
Field (name,length,type[,misc])...... = fl_last_nm, 25,c
Field (name,length,type[,misc])...... = fl_mid_init, 20,c
Field (name,length,type[,misc])...... = fl_nm_sufx, 5,c
Field (name,length,type[,misc])...... = nm_parse_score, 3,c
Field (name,length,type[,misc])...... = fl_gender_cd, 1,c
END
BEGIN Post to Output File =====================================
Output File (location & file name)... = [FL_work]/Name_std_nm.dat
Existing File (APPEND/REPLACE)....... = REPLACE
Output Filter (to 916 chars)......... = !empty(ap.Last_Name1) .or. !empty(db.LAST_NM)
Nth Select Type (USER/AUTO/RANDOM)... = USER
User Nth Select (1.0 - ???).......... =
Maximum Number of Records to Output.. =
Character Encoding (See NOTE)........ =
Unicode Conversion Name.............. =
Copy Input Data to Output File (Y/N). = Y
Copy (source,destination)............ = iif(!empty(ap.Last_Name1), chrtran(ap.Pre_name1,".",""), chrtran(db.NM_PRFX,".","")),fl_title
Copy (source,destinatson)............ = iif(!empty(ap.Last_Name1), chrtran(ap.FirstName1,".",""), chrtran(db.FIRST_NM,".","")),fl_first_nm
Copy (source,destinatson)............ = iif(!empty(ap.Last_Name1), chrtran(ap.Last_Name1,".",""), chrtran(db.LAST_NM,".","")),fl_last_nm
Copy (source,destinatson)............ = iif(!empty(ap.Last_Name1), chrtran(ap.Mid_Name1,".",""), chrtran(db.MID_NM,".","")),fl_mid_init
Copy (source,destinatson)............ = iif(!empty(ap.Last_Name1), iif(!empty(ap.MAT_POST1), substr(ap.MAT_POST1,1,5), substr(ap.Oth_Post1, 1, 5)), chrtran(db.NM_SUFX,".","")), fl_nm_sufx
Copy (source,destination)............ = ap.Name_Error,fl_nm_err
Copy (source,destination)............ = apc.Name1, nm_parse_score
Copy (source,destination)............ = iif(empty(db.GENDER_CD), "I", "S"), gndr_src
Copy (source,destination)............ = iif(!empty(db.GENDER_CD), db.GENDER_CD, (iif((ap.Gender_Rec = "1" .or. ap.Gender_Rec = "7"), "M", (iif((ap.Gender_Rec = "5" .or. ap.Gender_Rec = "8"),"F", "U"))))),fl_gender_cd
Copy (source,destination)............ = ap.newline,eor
END
BEGIN Post to Output File =====================================
Output File (location & file name)... = [FL_work]/Name_nm_bad.dat
Existing File (APPEND/REPLACE)....... = REPLACE
Output Filter (to 916 chars)......... = empty(ap.Last_Name1) .and. empty(db.LAST_NM)
Nth Select Type (USER/AUTO/RANDOM)... = USER
User Nth Select (1.0 - ???).......... =
Maximum Number of Records to Output.. =
Character Encoding (See NOTE)........ =
Unicode Conversion Name.............. =
Copy Input Data to Output File (Y/N). = Y
Copy (source,destination)............ = chrtran(ap.Pre_name1,".",""),fl_title
Copy (source,destinatson)............ = chrtran(ap.FirstName1,".",""),fl_first_nm
Copy (source,destinatson)............ = chrtran(ap.Last_Name1,".",""),fl_last_nm
Copy (source,destinatson)............ = ap.Mid_Name1,fl_mid_init
Copy (source,destinatson)............ = iif(!empty(ap.MAT_POST1), substr(ap.MAT_POST1,1,5), substr(ap.Oth_Post1, 1, 5)), fl_nm_sufx
Copy (source,destination)............ = ap.Name_Error,fl_nm_err
Copy (source,destination)............ = apc.Name1, nm_parse_score
Copy (source,destination)............ = iif(empty(db.GENDER_CD), "I", "S"), gndr_src
Copy (source,destination)............ = iif(!empty(db.GENDER_CD), db.GENDER_CD, (iif((ap.Gender_Rec = "1" .or. ap.Gender_Rec = "7"), "M", (iif((ap.Gender_Rec = "5" .or. ap.Gender_Rec = "8"),"F", "U"))))),fl_gender_cd
Copy (source,destination)............ = ap.newline,eor
END
Edited by: sminnakanti on Feb 7, 2011 3:56 PM

PP-Firmed indicator set automatically

Hi Experts
After APO SNP heuristics run, pp-firmed indicator is set automatically on planned orders and purchase requisitions.
I understand it is a standard functionality.
Is there a way, where this PP-firmed indicator should not be there after heuristics run.
Kindly advise.
Thanks
Pradipta Sahoo

Hello Pradipta,
Below you have a good explanation from SAP Help. So, if you delete the Output Firmed the order status PP - Firmed will be deleted too!
Thanks, Marius
Order Status PP-Firmed
Use
For an order with the status PP-firmed, the receipt quantities are firmed. Thus, the system cannot change the receipt quantities, or delete the order, during planning with the production planning heuristics, even if the requirements quantitiy has changed. However, you can change the receipt quantity or delete the order manually.
The system automatically sets the status PP-firmed
if the availability date of the order is within the planning time fence,
if the order is a Supply Network Planning order that is outside the SNP production horizon,
if the order has one of the following statuses:
output firmed
input firmed
date fixed
The status PP-firmed is therefore a higher-level status that is assigned automatically to an order under certain planning conditions, or because of other statuses.
The system automatically recalls the status PP-firmed if these conditions are no longer fulfilled.

Regarding firming indicator of PR in MD04

Dear all,
If we change quantity of PO item, the realted to PR item will be firmed, but the field EBAN-FIXKZ is still blank, when I display in MD04 , there is a star sign in the PR then click details of element of it and find the field 'firmed' is fix .
My question: which table save the firmed data ?
Thanks
Colin.

Hi Karthik ,
I compare a PR between ME53 and MD04:
in ME53:
The screen field "fixed " (table field: EBAN-FIXKZ) is blank.
in MD04
The screen field "firmed" (structure field:MDPS-FIX01) is "X".
I want to select the data MDPS-FIX01 = 'X'. but it is a struture.
Thanks
Colin.

Firming indicator to PR

Dear All,
I am using a MRP type PD inraw material, which is part of FG BOM.
WHen I am running MRP for FG, PRs generated for raw material are automatically firmed. I have already checked settings for MRP types and coversion for purchase proposals.
Can someone guide me to resolve the issue?
Regards
Milind

Uma Shankar, This is to confirm that your observations are correct.
SAP Note 88266 - Fixed indicator PReq - MD04 confirms this. Pasting the details as this should serve as a good to know read for consultants.
Symptom
In certain circumstances, purchase requisitions (PReq) are displayed in the current stock/requirements list (transaction MD04) as 'fixed', although the "fixed" indicator is not set in the purchase requisition.
Reason and Prerequisites
This phenomenon can be explained as follows:
The "fixed" indicator in the purchase requisition is always set if you manually change MRP-relevant data in one of the purchase requisition s generated from materials planning.
However, materials planning must also interpret other statuses of the purchase requisition to decide whether an automatic change is allowed. The following are the three instances in which materials planning regards the purchase requisition as "fixed":
if the "fixed" indicator is set
if the purchase requisition is subject to a release procedure and if it can no longer be changed for materials planning according to its release status.
If the purchase requisition has already been converted into a follow-on document (for example, into a request for quotation - status 'A', or into a purchase order - status 'B'
Transaction MD04 interprets these three statuses in the same way, that is, that the purchase requisition is fixed for materials planning.
This could be interpreted as an apparent 'data inconsistency', but this is incorrect.
Solution
There is no correction available because the system behavior is correct.

MD04 firm schedule line - ME38 schedule line manualy changed

Hello Gurus,
many users change manually quantity in schedule lines but then the schedule is locked and becomes firm in MD04 ( * ) so that MRP does not take this quantity into account.
How to change this behaviour as I want the MRP to take this modification into account ?
Thanks a lot.

Hi,
When your users change a schedule line they are automatically firmed as the system can only assume that they know more about the supply position than it does.
MRP does take the quantity into account, however, it is not allowed to change the date nor the quantity, so any increase or decrease in demand is reflected in the first unfirmed schedule line.
This behaviour is not configurable.
If the firmed schedule line is not correct because the user has made a change in error then you need to set the quantity to zero so that the schedule line is deleted. MRP will then create a new schedule line in line with the planning parameters and current stocks / demand.
Hope that has answered your question
Alex Dixon

Planned Order Creation - Firming Indicator

Hi Team,
When i am creating the planned order in MD11, the field "Planned Order (Firming)" is automatically set. I do not want to set this field is getting set automatically. Any configuration required to set this?
Thanks

Hello Sugan
Remove the fixed indicator for a planned order created manually makes no sense!!!
This planned order will be deleted or changed by MRP on the next planning run.
I can tell you that this is not possible on the standard system, however, you can use BADI MD_PLDORD_CHANGE to do that.
See this document with more details about the BAdIs available on MRP:
BAdIs for MRP
BR
Caetano

MD04--- Delivery date--***URGENT***

Hello Gurus,
In md04 the delivery date is pushed out to open sales order date and i see exception 15
What setting in the system makes it look for dependent requirements
WE WANT delivery date as per PLANNED LEAD TIME
Can any one help me get through this
Will award full points
Justin

what is checking group 32 what is <b>And planned delivery date is 95</b>
I am not getting you.
If there is no commited date in the PO, that means available qty is zero?
Why are you using STO, you told it is PO?
If I correct- you create a sales order, then you create PO to get that material
Now in sales order you have availability check activated, hence it will look for the receipt element.
Now you are creating PO manually and entering the delivery date manually...
let us say del date you eneterd today.
Your planned delivery days let us say 20 datys,
the system will say "can delivery date met? - it is warning message. if you stll save syetem will save that order.
Now when you see the date in MD04 and if you run MRP, then if the delivery date us not matching with SO delivery date, then system will give resceduling date, which willnot be copied to PO unless you change it.
See below MD04 sumulation
<b>DATE---recp/issue-resch date-qty--balance</b>
20.11.2007Stock--
0
10.12.2007SO--
-10 -
-10
15.12.2007PO10.12.2007-- 10 -
0
Since as per the date proposed by system as per MRP2 view data(planned del days) is 15.12.2007. But required del date from SO is 10.12.2007, hence MRP reschedules and give youn indication that del date should be 10.12.2007 instead of 15.12.2007.
Is it the case with you? if not please give example like what i gave above.
Message was edited by:
Rajesha Vittal
Message was edited by:
Rajesha Vittal

CO27 - Missing part indicator (Urgent)

Hi All,
In CO27, i find for a few materials, the missing part indicator has been ticked, while for a few materials it is not. I would like to know how is this indicator being set by the system. Because for the parts which i do not seen the indicator ticked, are not available at the moment in stock & hence i believe this indicator should be ticked. Kindly let me know where all i should check.
Vivek

Dear Vivek
1st question
If no ava check is not ticked and status check is ticked.
System will check availability of material when released and saved. Then after this if the MAT not available status NMAT you can see in the header. Once it is register, system will check the availability every time you saved till you will get the status with out NMAT. In case NMAT is not there during release and after that there was some problem with the material stock and let us say stock is reduced, then actually material is not available, but in production order Since NAMT is not there system will not check the material availability.
In your case since you are checking the ava in background , if you want the system to check all orders with or without NMAT then dont tick-status check.
In this case system load will increase as system has to check all the orders.
2.Please do not mistake this tick. This is applicable for HALB material, and not for Raw material.
If you have HALB material and it is having stock of 10, production orders for this halb material lets say 2 prod orders released (qty 10 each) and 3 are not released(qty 10 each).
Then ava qty will be
I leave Production orders field blank = 10
(ii) when i consider only released production orders = 10+10*2=30
(iii) when i consider all production orders = 1010*210*3 = 60
If you are taking raw material, this tick has not relevant
your 3rd question -
Ava check if material consists of 2 things
checking rule - defined for a transaction - PP for production order, A is for sales order, B is for delivery etc.
Checking group - what you define in material master 01/02/CH.
Combination of above checking rule and checking group will fix the scope of check.
Hence in OPJJ, you need to give checking rule and checking group both.
as per understanding 01 will not change to 02 as in that plant 01 is fixed if it is in material master.
Please come back if required
If you want I will send you the preliminary document to understand what is AVA check if required.

Material Deletion Indicator - Urgent

Hi All,
By mistake i have deleted a component in a work order & saved it. I would like to like to is it possible to undo this deletion?
I know i can add back this component to the work order, but i want to undo the deletion.
Await inputs.
Vivek

Hi,
It is not possible to perform UNDO for deletion after you save.
Regards,
Krishna Mohan

SA Schedule Lines Fix indicator in MD04.-

Hello,
   I want to modify fix indicator from Schedule Agreement Schedule line in transaction MD04.
   (check and uncheck)
   Could you tell what to do?
Thanks in advance.
Edited by: Juan Manuel Caballero on Oct 6, 2009 9:00 PM

Hi
There are two possible scenarios for fix indicator
1) Firm indicator will be set automatically based on the no of days maintained in the firm zone from the date of MRP run.
2) If you change the schedule line manually the system will set the firm Indicator automatically.
I think there is no provision in SAP to change this manually in MD04.
Hope it helps
Thanks /Karthik

MD04, Firming Indicator (urgent)

Similar Messages

Maybe you are looking for