Thursday, September 29, 2005

Form Notes

Form Notes

Table Name that is used is called.

TKOEXPALU_B

Underlying table changed to mtl_system_items

changed form to TKONTPALU

Tuesday, September 27, 2005

reportschedule

























































Wednesday, September 21, 2005

Forms Generation

Forms Generation

To Register Forms

  1. Application Developer (Register Form)

  2. Create Form Function

  3. Menu (system Administrator)
  • responsibility define

  • menu attached to report

To generate fmx (executable)
f60genm Module=TKONTSNQRY.fmb userid=apps/apps Module_Type=FORM
 
To generate fxt (to check in to PVCS)
f60genm Module=TKONTSNQRY.fmb userid=apps/apps Module_Type=FORM Script=Yes
 
To generate fmb from fmt
f60genm Module=TKONTSNQRY.fmt userid=apps/apps Module_Type=FORM Parse=Yes
 

  

Update PAL

1)      Update PAL
Schedulers need a form to update  5 data elements that currently reside on mtl_system_items.  Three  of these columns will be moving to tk_mtl_system_items (Tek Item Table) with the OMAR 11iG project.
  1. PAL Leadtime (tk_mtl_system_items)   This is a number that represents the number of days that it will take Tektronix to be able to ship  the item. This column currently resides in mtl_system_items.attribute5, but is moving to tk_mtl_system_items

  2. PAL Quantity (tk_mtl_system_items)  This is a number that represents the qty that can be ordered that can meet the PAL Leadtime for the item.  Blank means 1.  This is because this field appears on the View Item Notes form that pops up during Order Entry if any of its fields are populated.  Since most products have a PAL Qty = 1, its trained that blank means 1, instead of filling in the value of 1 resulting in the form popping up every time  only for that. This column currently resides in mtl_system_items.attribute4, but is moving to tk_mtl_system_items

  3. Commit Rule (tk_mtl_system_items)  This is used so that schedulers can communicate to CSRs if they can schedule the line.  Since OMAR and O-Mfg aren’t integrated and not all items can be scheduled by CSRs we needed a way to communicate this information.

  4. Marketing Status (tk_mtl_system_items)  This value represents some orderability information.  Examples would be SD (Supply Depleted), QRO (required option).  This column currently resides in mtl_system_items.attribute12, but is moving to tk_mtl_system_items

  5. Planner_code (mtl_system_items)  Schedulers need the ability to update planners for many items at one time.  Example:  If they query up VM700T% they can update the planner for the product and all the options in this form while updating all the other data elements as well.  This is not in the exising form but we want it in 11i.
The reason a form is needed instead of just updating it in the Organization items is because a given product can have many options and it is cumbersome to bring up each item to maintain its values.  In addition, this information is critical that it be accurate because CSRs are giving delivery and orderability information to customers based on these values.
Example:   760A has many options i.e, 01, 02, A1, A2, A3, A4, A5, L0, L1, L2, L3, L4, L5, R3, R5, C3, C5, D1, D3, D5.
The form would allow the user to input in 760% (wildcard) and get all the product related items at once for updating and just copy the data down to all the rows