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

Similar Messages

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.

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

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.

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

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

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.

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.

Returns and Free Item indicator in Purchase Requsition

Can we get the FREE Item and Returns Item indicator (as available in PO) in Purchase requsition.
Can we create returns PR or free item PR.
Thanks,

PR is an internal document. You do not need a FREE indicater at that level

What is the use of Return indicator in Service entry sheets

Hi,
I would like to know the use of Return Indicator ?, and When actually we can use this. Please advise.
Thanks
Udaya

Hi
The Return Active indicator enables you to specify that a return is possible when time sheets are converted into external services (i.e. incorporated in service entry sheets).
If you have selected the activation indicator for the return, you can retrospectively change a time or quantity in a time sheet that you have already incorporated in a service entry sheet. As soon as you convert this changed time sheet into external services, the system generates generates both a service entry sheet with the new data and a return document cancelling the original data. The system sets the Return Indicator in this document.
Where you can use this Indicator
In a time sheet for which you have already created a service entry sheet you subsequently change a specified time or quantity and reconvert the time sheet into an entry sheet for externally performed services. The system then creates both an entry sheet with the new data and an entry sheet in which the original data is cancelled and the returns indicator is selected.
The return indicator cannot be selected manually, but is set only by the system after the conversion of a changed time sheet into external services.
To facilitate the return of time sheets during the service entry process, you must select the relevant Activation Indicator in Customizing for External Services Management.
Source Determination and Default Values -> Specify for Client -> Returns Active.
Regards

Firming

HI, if my earlier sales order cancels, next time when i run mrp, that cancelled sales order should be considered by the system and accordingly that planned ORDER GENERATED must be deleted. as i understand once it is firmed, that planned order will not be cancelled. please advise in which scenarios this firming functionality is useful. PLEASE ALSO ADVISE WHEN PROCUREMENT PROPOSAL GENERATES (PR), whether it will automatically become firmed or do we need to do firming manually. how to do the firmimng . please advise.

Hi
Firming indicator for planned order data
This firming indicator specifies whether the planned order is firm, that is, the system will not change either dates or lot sizes during planning runs.
The conditions in which the planned order /PR get firmed indicator.
1. For manually created planned orders:
The indicator is suggested by the system when the planned order is created. However, you can remove it if desired.
2. For planned orders created by planning runs:
The indicator is set by the system as soon as you have manually changed a planned order. However, you can remove the indicator when you change the planned order again.
Or
3. If the Planned order comes under the Planning time fence .
( The planning time fence specifies a period within which no automatic changes are to be made to the master plan )
The firming type determines how order proposlas are to be created or scheduled within the planning time fence.
For the PR,
If you change the anything in the PR say qty or dates. or if you process the PR so at the time the particualr PR get firmed.
please advise in which scenarios this firming functionality is useful
So the firm functionality will be useful , if you find this palnned order is going to uses in the future and it should not be deleted in the next mrp run. even though the reqmt is not available.
The firmed planned order will not be deleted by the mrp run

Scheduling Agreement Schedule Lines firmed after outbound delivery

Dear All,
We use scheduling agreement for cross-company process in our client. After MRP run schedule lines created automatically. For the next step outbound delivery is created via VL10F (or VL10B).
After outbound delivery creation, on MD04 or ME39, i see the schedule line firmed (*). Because firmig MRP doesn't change those schedule lines. This is a problem for our client.
Do you know a way for MRP can change the schedule lines even outbound delivery created ? How can i manage this situation ?
Best regards,

Hi Anil
The '*' that you see means that the schedule line has been changed manually and the Firming indicator (EKET-FIXKZ) is set when there is any change to the Schedule line.
So, when a Delivery is created, the schedule line should be 'Fixed'.
Otheriwse, MRP can delete or change this schedule line and it would cause an inconsistency in the system. This is the logically intended behaviour.
Please see the F1 help for the field EKET-FIXKZ:
"Schedule Line is "Fixed"
Fixes the schedule line and determines that it cannot now be automatically changed as a result of materials planning and control/MRP activities.
Procedure
The indicator is set automatically if:
.- You make manual changes to a line of a scheduling agreement delivery schedule that was created via the materials planning process
.- You create a schedule line manually
Dependencies
You can specify whether Materials Planning/MRP can change delivery schedule lines within the firm and trade-off zones in the additional data for the scheduling agreement item."
I hope this helps.
Anna

Firming the Schedule Lines in Sch.Agreement

Hi , I have done the following to firm the schedule lines in Scheduling agreement.
1. Firm Zone as 30 days
2.Tradeoff zone days as 60 days
3.Binding MRP indicator as NULL(Lines not changeable within Zones)
4.In OMIN , Firm Schedule lines enabled for the MRP group
When i run the MRP, schedule lines are getting created with Firm Indicator (*) for the requirements lying within these zones. After transmitting the schedule lines to vendor , if i change the requirement again, the schedule lines within Firm Zone are getting adjusted as per the new requirment. I dont know whats the purpose behind maintaining these Firm Zone and Trade off Zone.
Pointers are much appreciated.
Thanks and regards,
Milton Isaac

Hi,
Rolling delivery schedules issued under scheduling agreements are divided into different time zones indicating the degree to which lines of the schedule are binding.
Firm zone (zone 1) (go-ahead for production).
The schedule lines within this zone count as firm and thus as fully binding. If you cancel a schedule line that falls within the firm zone, the vendor is entitled to charge you with both production costs and the costs of procuring input materials incurred by him as a result of the cancellation.
Trade-off zone (zone 2) (go-ahead for procurement of input materials)
This is the "semi-firm" zone, giving the vendor the go-ahead to procure necessary input materials for the manufacture of the item ordered. If you cancel a schedule line within this semi-firm zone, the vendor is only entitled to charge you the material costs. Schedule lines falling within this time zone are thus less binding that those falling within the firm zone.

Returning Firm Indicator

Similar Messages

Maybe you are looking for