Page 1 of 39
Table of Contents
Introduction .................................................................................................................................................. 3 Oracle Applications Navigation HOT KEYS - Release 11i....................................................................... 4 Lab 1 Lab 2 Lab 3 Lab 4 Lab 5 Lab 6 Lab 7 Lab 8 Lab 9 Lab 10 Lab 11 Lab 12 Lab 13 Lab 14 Lab 15 Lab 16 Create Items............................................................................................................................... 5 Create Standard Bills of Material............................................................................................ 7 Create Resources and Departments....................................................................................... 11 Create Routings ....................................................................................................................... 12 Calculate Lead Times.............................................................................................................. 14 Transfer from Engineering to Manufacturing...................................................................... 16 Create Workday Calendars.................................................................................................... 17 Create a New Bill Using BMCOIN and then Update ........................................................... 19 Create a New Bill Using the BOM Business Object (API) and then Update...................... 21 Create a New Bill Using the ECO Business Object (API).................................................... 23 Explode a Bill Using the Exploder_Userexit ......................................................................... 25 Implode a Bill Using the Imploder_Userexit......................................................................... 26 Export a Bill and Routing....................................................................................................... 27 Manual ECO Approval and Implementation ....................................................................... 28 ECO Alerts and Approval Notifications................................................................................ 29 Approve an ECO via Workflow ............................................................................................. 31
STANDARD WORKFLOW PROCESS ............................................................................................................................. 31 SECTION I - SETTING UP ORACLE ENGINEERING ..................................................................................................... 31 SECTION II - MODIFY THE STANDARD APPROVAL PROCESS IN ORACLE WORKFLOW BUILDER ............................. 31 SECTION III CREATE THE ECO AND LAUNCH THE WORKFLOW PROCESS ........................................................... 33
Lab 17 -
Use Up ECO............................................................................................................................. 35
SECTION I CREATE THE PLANNER, USE-UP ITEMS AND BILL OF MATERIAL ......................................................... 35 SECTION II CREATE ON-HAND QUANTITY FOR THE USE UP COMPONENT ........................................................... 36 SECTION III CREATE THE MRP PLAN ................................................................................................................... 36 SECTION IV CREATE THE USE UP ECO ................................................................................................................ 37 SECTION IV SET UP THE ECO USE UP ALERT....................................................................................................... 38 SECTION V REVISE TEST PARAMETERS ................................................................................................................. 38
Page 2 of 39
Introduction
The following labs are designed to illustrate basic functionality within the Oracle Bills of Material and Oracle Engineering applications as well as some of the more advanced topics that may not be well documented or require a fair amount of setup. The labs build upon each other so they usually must be completed in order. Some labs utilize provided SQL scripts. The scripts can be used as a starting point for developing more advanced versions. These are provided in a single ZIP file that is included as an attachment of MetaLink Note 416802.1. Unzip the file to a location that can be accessed via SQL*Plus or SQL Developer. The requirements for using the labs are: 1. Access to an Oracle Vision Demo instance. Although any test environment can be used, all the examples reference entities within a Vision Demo instance. 2. Oracle SQL*Plus or Oracle SQL Developer. These are free downloads from the Oracle Technology Network (OTN) website: (http://otn.oracle.com). Click the Downloads link to access all downloads. Only one of these is needed to run the SQL scripts. 3. Oracle Workflow Client Release 2.6.3.5 for Microsoft Windows. This is a free download from the Oracle Technology Network Website.
Note: It is recommended that you install Workflow Builder in a new oracle home. Not doing this may cause your existing oracle home to stop functioning properly. Change the Destination Name to a new oracle home name. Change the Destination Path as needed. Click the Next button when complete.
4. Oracle SQL*Net Client. This is a free download from the Oracle Technology Network website as part of the Oracle Client software. This is needed by SQL*Plus, SQL Developer and Workflow Client software to connect to an instance. SQL*Net Client is automatically installed when you install SQL*Plus.
Page 3 of 39
Page 4 of 39
##1010 ##1010 Subassembly ##1040 ##1040 ##1010 ##1010 ##1010 ##1010 ##1010 ##1010 ##1010 ##1010 ##1010 ##1010 ##1010 ##1010 ##1010 ##1010 ##1010 ##1010
(N) Engineering > Prototypes > Items > Master items Enter in the item number, and description. (M:) >Tools, Copy from Enter (or choose from a LOV) a value for the template type or item from the chart above. Click on Apply, then click on Done Save the item. (M:) > Tools, Organization assignment Assign the item to the M1-Seattle organization, then save. Repeat for the next item until all the items above have been created. 2. Using the Item Search form, search for all of your items. (N) Engineering > Prototypes > Items > Item Search Go to the Item Mask field and type ##% (where ## are your unique initials) Click on Find Close the window, click on the Clear button, and acknowledge the warning. Try to define one of your items in the Inventory responsibility. (N) Inventory > Items > Master Items What was your result? ____________________________________________
3.
Page 5 of 39
Page 6 of 39
2.
Create a new BOM for ##2011 by copying from ##2010. Then, add component ##3031 for 20 pieces and disable ##3030 for 20 pieces. (N) Engineering > Prototypes > Bills > Bills Enter ##2011 as the new BOM, then tab to the next field but enter nothing.
Page 7 of 39
(M:) > Tools, Copy bill from Tab to the item field and enter item ##2010 Click Copy button and then acknowledge note after reading. Add a new item sequence for item ##3031 for 20 pieces, then disable item ##3030. Save your work. 3. View an indented BOM for item ##1000. (N) Engineering > Prototypes > Bills > Indented Bills After entering the part, click on the Find button Try clicking on the buttons at the bottom and note the display changes. What does clicking on the ++ button do? Compare BOM ##2010 to BOM ##2011. (N) Engineering > Prototypes > Bills > Comparison Create an alternate name called ##Sub for a substitute part. (N) Bills of Material > Setup > Alternates Insert new record, or click on the next available line Type ##Sub and enter in a description, then save your work. Create an alternate BOM for item ##2010 using the alternate name ##Sub. Disable your ##3010 and add another persons ##3010 in your alternate BOM. (N) Engineering > Prototypes > Bills > Bills Enter in your item ##2010, then from a LOV in the alternate field, choose your ##Sub. Copy from your BOM ##2010. (Refer to the previous steps for copying BOMs.) Disable the part ##3010, and add another individuals part ##3010. (Refer to the previous steps for adding and disabling BOM components.) Enable items ##2010, ##3010, ##3020, and ##3030 in the M2 Boston Manufacturing organization. Copy ##2010s BOM from the M1 Seattle Manufacturing organization. (See if you can remember the steps for completing these objectives; if you need help, ask your instructor or refer to previous lab exercises.) Remember that you will have to change your current organization from Seattle to Boston before you will be able to create the BOM for that item. Why is this so?____________________ What was the result of the BOM copy to M2?________________________________ Perform a loop check (change back to the M1 Org) on the BOM for item ##1000. (N) Engineering > Prototypes > Bills > Bills (M:) >Tools, Check for loops Do not close the record when you have finished checking for loops. Attach a text document to this record. Click on the paper clip icon. In the attachments form, click on the category field and choose from a LOV Miscellaneous. Enter a brief description and in the data type field, pick from a LOV short text. Type some small text document, then save your work Now, test your attachment. Close the form and then bring up the BOM record again. Do you notice a difference in the paper clip icon? _______ What is that difference? ___________________________ 10. Add designators to your item ##3030 Bring up the BOM for item ##2010. Make sure your cursor is on the item sequence for the component ##3030, then click on the Designators button. Click on the Add Range button. Enter in any prefix and / or suffix you would like. Number of values: 30 Starting value: 1 Ending value: 30
4.
5.
6.
7.
8.
9.
Page 8 of 39
Click on the Add button and acknowledge the note. Save your work.
Page 9 of 39
11. Use the following queries to view item, bill and component information. To find the item data: SELECT * FROM mtl_item_flexfields WHERE item_number = ##1000; Use the inventory_item_id from the above query to find the bill of material data: SELECT * FROM bom_bill_of_materials WHERE assembly_item_id = &inventory_item_id AND organization_id = &organization_id; Use the bill_sequence_id from the above query to find the bill component data: SELECT * FROM bom_inventory_components WHERE bill_sequence_id = &bill_sequence_id;
Page 10 of 39
Note: For each resource, use the following additional information: UOM: Charge Type: Default Basis: Costed: Standard Rate: Absorption Account: Variance Account: Overheads: Resource Costs: 3. HR WIP Move Item Yes Yes Use any account number Use any account number Do not enter anything Use a price of $45.00 @ Frozen cost.
Create departments using the following table (N) Engineering > Prototypes > Routings > Departments Department ##AutoIns ##ManAssy ##Test ##PCFinal ##PCFinal Description Auto Insertion Manual Assembly Testing PC Final Assembly PC Final Assembly Resource Name ##Inserter ##Assblr ##Tester ##Assblr ##Tester Capacity Units 1 10 3 4 2
Assign the departments to class ##PCMFG. Note: For each department, use the following additional information: Class: Shared: Available 24 hrs.: Assigned Shifts: ##PCMFG No No 1
Page 11 of 39
Note: For each resource, use the following additional information: UOM: Schedule: 2. Hr. Yes
Create a routing for Item ##1040 using the following table: Operation Sequence 100 200 Department ##PCFinal ##PCFinal Description Assemble CPU Chassis Test the CPU Chassis Resource Sequence 10 10 Resource Name ##Assblr ##Tester Usage Rate 0.5 1 Basis Item Item Assigned Units 4 1
Note: For each resource, use the following additional information: UOM: Schedule: 3. Hr. Yes
Create a routing for Item ##2010 using the following table: Operation Sequence 100 Department ##AutoIns Description Machine install components Hand install components Test motherboard Resource Sequence 10 Resource Name ##Inserter Usage Rate 2 Basis Lot Assigned Units 1
200 300
##ManAssy ##Test
10 10
##Assblr ##Tester
0.1 2
Item Item
10 1
Note: For each resource, use the following additional information: UOM: Schedule: 4. Hr. Yes
Associate each bills components with its corresponding routing. This is accomplished by assigning an operation defined for the routing to the component. (N) Engineering > Bills > Bills Query the bill. For each component, use the LOV in the Op Seq field (or enter) to assign an operation. Notice that you cannot enter an operation sequence that is not on the routing (except 1 which is used to signify no operation). Bill ##1000 Component 1010 1020 Operation Sequence 100 100 Page 12 of 39
##1040
##2010
1030 1040 ##2010 ##2020 ##2030 ##2040 ##3010 ##3020 ##3030 ##3040
100 200 100 100 100 200 100 100 200 300
Page 13 of 39
1.
a.
Enter lead times for your buy items using the following table: Item Number ##1010 ##1020 ##1030 ##2020 ##2030 ##2040 ##3010 ##3020 ##3030 ##3040 Preprocessing LT 5 5 5 5 5 5 5 5 5 5 Processing LT 5 5 5 5 5 5 10 60 5 30 Post-processing LT
2 1 1
b. 2.
Enter lot sizes of 10 pieces for items ##1000, ##1040, and ##2010.
Calculate lead times for items ##2010, ##1040, and ##1000. (N) Engineering > Prototypes > Routings > Lead Times Choose and run Calculate Manufacturing Lead Times GUI View fixed, variable and processing lead times for items ##2010, ##1040, and ##1000. (N) Engineering > Prototypes > Items > Organization Items (Lead Times tab) Roll up the lead time for item ##1000. (N) Engineering > Prototypes > Routings > Lead Times Choose and run Rollup Cumulative Lead Times GUI View cumulative lead times for the item ##1000. (N) Engineering > Prototypes > Items > Organization Items (Lead Times tab)
3.
4.
5.
Page 14 of 39
6.
View the indented BOM for ##1000, noting the lead time for the components. (N) Engineering > Prototypes > Bills > Indented Bills ** To view lead times, check the Lead Time checkbox on the Find form before clicking the Find button **
ITEM
##1000 ##1010 ##1020 ##1030 ##1040 ##2010 ##2020 ##2030 ##3010 ##3020 ##3030 ##3040
FIXED LT
VARIABLE LT
4.21866319444444
0 14.9996875
8.43732986111111 15.0746979166667
POST PROCESSI NG LT 0 0 0 0 0 0 2 0 2 1 0 1
PRE PROCESSI NG LT 5 5 5
5 5 5 5 5 5
Page 15 of 39
Bills 1. 2. 3. 4.
No No No No
Yes Yes
No No
Items#Item Information Prototypes#Items#View Item Details Items#Organization Items Prototypes#Items#Organization Items Items#Master Items Prototypes#Items#Master Items
No No No No No No
Page 16 of 39
2.
3. 4.
6.
Page 17 of 39
Click on dates and select a month that you put holidays into. Answer the following questions about your calendar. What was your workday pattern? __________________________ Which days are designated as Off days? _______________________________ How did you identify the Off days? ___________________________________ Take a look at another month in which you designated exceptions to your workday calendar. What days have designated exceptions? _________________________ Close form and return to the Manufacturing responsibility.
Page 18 of 39
2.
5.
7.
Page 19 of 39
quantity of component ##6230' from 1 to 5. 10. Run the Bill and Routing Open Interface (BMCOIN) (N)Bills > Import Run with the following parameters: Run for All Orgs=No Import Routings=No Delete Processed Rows=No Review the request log for success: (M)View > Requests 11. Query your bill in the Bill Define form (N) Bills > Bills The quantity for component ##6230 is now 5
Page 20 of 39
Lab 9 - Create a New Bill Using the BOM Business Object (API) and then Update
The 2 scripts in this lab illustrate the use of the BOM Business Object Application Programming Interface (API) to create a new bill (BOMBO_Create.sql) and then update it (BOMBO_Update.sql). 1. Locate the folder you where you unzipped the lab SQL scripts and access the BOMBO subfolder (see Introduction). Edit BOMBO_Create.sql and update the section as shown to reflect the items you created in Lab 1: ------------------------------------------------------------------- Change these as needed define ORG_CODE = 'M1' define PARENT_ITEM = '##6101' define COMPONENT_ITEM_1 = '##6110' define COMPONENT_ITEM_2 = '##6120' define ALTERNATE_BOM_CODE = '' -----------------------------------------------------------------Examine the script and review the script 3. 4. Start SQL*Plus Run BOMBO_Create.sql The script calls the BOM Business Object to create a single alternate bill with 2 components. When the script runs successfully, edit the script and uncomment the following line so the bill will be created permanently. --commit; 6. -- uncomment this if you want to commit the change...leave commented for testing
2.
5.
Query your bill in the Bill Define form (N) Bills > Bills Query Bill = ##6100, Alternate = ##
7.
Edit BOMBO_Update.sql and update the section as shown to reflect the bill you created above: -----------------------------------------------------------------define ORG_CODE = 'M1' define PARENT_ITEM = '##6101' define COMPONENT_ITEM = '##6110' define OPERATION_SEQ_NUM = 60; -- When updating, Start_Effective_Date needs to be set -- to the EXACT effectivity date of the component define START_EFFECTIVE_DATE = 'DD-MON-YYYY HH:MI:SS' define ALTERNATE_BOM_CODE = '' define QUANTITY_PER_ASSEMBLY = 99
8. 9.
Start SQL*Plus Run BOMBO_Update.sql The script calls to BOM Business Object to update one component of the alternate bill created above. It changes the quantity to 99.
10. When the script runs successfully, edit the script and uncomment the following line so the bill will be created permanently.
Page 21 of 39
--commit; 11.
-- uncomment this if you want to commit the change...leave commented for testing
Query your bill in the Bill Define form (N) Bills > Bills The quantity for component ##6110' is now 99.
Page 22 of 39
Lab 10 - Create a New Bill Using the ECO Business Object (API)
This example of the ECOBO is a bit more complex. It stages data in some of the interface tables. A custom procedure is defined and loaded into the database. This custom procedure is then called. The custom procedure reads the staged interface data and passes it to the Process_ECO procedure call (the ECO API). This example creates a new ECO that creates a new bill by creating the ECO with a single revised item and component. Since this is a new item with no defined bill yet, the act of adding the component to the revised item on the ECO will cause the bill to be created automatically under ECO control. All run time output is spooled to the file runall.txt in the current directory on your PC and Process_ECO debug output is turned on for your review (see step 5). 1. Locate the folder you where you unzipped the lab SQL scripts and access the ECOBO subfolder (see Introduction). There are 8 files in all: Name runall.bat runall.sh runall.sql DefineParameters.sql LoadProcedure.sql Description Run to process all (Windows) Run to process all (UNIX) Called by runall.bat or runall.sh to run all SQL scripts Define the processing variables to pass to the your custom procedure. Defines and loads a custom procedure which (when called) will: read the BOM and ENG interface tables data (loaded next) load the interface data into ECO API table variables call the ECO API to process the data Loads data into the BOM and ENG interface tables. This example utilizes the BOM and ENG interface tables to store the data being imported. Calls your custom procedure loaded by LoadProcedure.sql Displays the created ECO
Create a new manufacturing item ##1002 (N) Inventory > Items > Master Items Description = Pentium Computer (Chassis Only) Copy from item ##1000 Assign to organization M1 Edit DefineParameters.sql and update the highlighted variables. Note that the v_commit variable should be changed only at the very end of testing after your script is running successfully. Leave with a value of FALSE until that time. -- ************************************************************************** -- *** CHANGE THESE VALUES AS NEEDED ** -- ************************************************************************** -- Identity define v_user_name define v_initials define v_resp_name define v_today define v_prog_appid -- ECO header define v_eco_name define v_org_code define v_change_type define v_priority define v_hierarchy
3.
= '########' -- your application user name = '###' -- your initials = 'Manufacturing and Distribution Manager' = trunc(SYSDATE) = NULL
-- ECO name -- 3 letter code of the org to create ECO in -- ECO change type -- ECO priority
-- Revised Item (RI) define v_new_revised_item_revision = ''; Bills of Material, Engineering Labs
= '##1002'; = '';
-- Revised Component (RC) define v_revised_component_name = '##1040'; define v_comp_eff_date = '&&v_today' define v_old_operation_seq_num = 1 define v_operation_seq_num =1 -- Reference Designator define v_reference_designator -- Control define v_commit
-- name of revised component (must exist) -- component effectivity date -- old operation sequence number -- new operation sequence number
= ''
-- reference designator
= 'FALSE';
4.
Edit runall.bat. Change the SQLPLUSW.EXE path in the batch file to match the location of the file on your PC. Run runall.bat. This batch file calls runall.sql that in turn calls all necessary sql scripts necessary to call the API. If it fails, examine the debug output file and spool output file (runall.txt) to determine the cause. Make corrections as needed and rerun until successful. The debug file exists on the celalnx23 server in /usr/tmp (see the complete name of the file in the spool output file and on the screen). When the script runs successfully, edit the DefineParameters.sql and change the v_commit parameter to TRUE. This will allow the scripts to commit the ECO when successful. define v_commit = 'TRUE';
5.
6.
Run runall.bat again. This time, your ECO will be commited to the database. 7. Query the ECO in the ECO Define form (N)Engineering > ECOs > ECOs Query the bill. (N)Bills of Material > Bills > Bills Since the ECO is not implemented, uncheck the Implemented Only checkbox so you can view the unimplemented components.
8.
Page 24 of 39
2. 3.
4.
Page 25 of 39
2. 3.
4.
Page 26 of 39
4.
Page 27 of 39
2.
3.
Click the Revised Items button Enter item ##2510 Create a new revision by entering a value in the Item Rev field Set the effective date one month from today For the revised components, disable ##3010 and add (replace it with) item ##6110.
Click the Components button to enter the component changes: Disable component ##3010 Replace it with component ##6110
Save the ECO. It should have an approval status of Approved. Choose Tools > Release to change the status to Released. This will save the ECO with the new status. 4. View bill ##2510 note the pending change (hint: use Future and Current and uncheck the Implemented Only checkbox) (N) Bills of Material > Bills > Bills Now go back to the ECO form and Implement the ECO (Tools > Implement) Look at any other inquiries you care to as time allows
5. 6.
Page 28 of 39
b.
2.
Add the Alert Manager responsibility to your current user. (N) System Administrator > Security > User > Define Query your user. Add the responsibility: Alert Manager, Vision Enterprises. Save. Create an Approval List (N) Engineering > Setup > Approval Lists Enter unique name for the approval list, ###-List Enter description, ### Approval List Enter Sequence = 10 Enter your Employee Name <Last Name%> to query for the name> Save Create an ECO for item xx-2010 to increase the quantity for item xx-3040 to a quantity of 25 (N) Engineering > ECOs > ECOs If no organization has been set, choose the M1 - Seattle Manufacturing organization. With the cursor in the ECO field, tab to accept the ECO auto number. Set ECO Type to Prod Chg (Product change). Tab out of the ECO Type field and the creation date will populate and the Status will default to Open. Enter your user name as the Requestor Note: Requestor is a required field when using the ECO Approval alert. If one is not entered, the Alert will not be sent. Bills of Material, Engineering Labs Page 29 of 39
3.
4.
In the Approval List field; enter the approval list you created previously. Tab out of the Approval List field and the ECO Approval Status will default to Not submitted for approval. Save and take note of the ECO number. Click on the Revised Items button. Revised Items Form Enter item ##2010 and the tab out. Item ##2010 was created in the Create Standard Bills of Material lab. Click on the Components button. Revised Components Form Set Action = Change Place your cursor in the Component field, enter a percent (%) and tab out. The LOV will open and display only those components defined for this revised item. Enter or select component ##3040. Tab out of the component field and the component information will populate into the form. Change the component New quantity to 25. Save Close the Revised Components form. Close the Revised Items form. On the Engineering Change Orders form, update the ECO Approval Status to Ready to approve (place your cursor in the field and choose Ready to approve from the LOV). Save. 5. Verify that the ECO Approval alert is defined and enabled. (N) Alert Manager, Vision Enterprises > Alert > Define Query: Application = Engineering Name = ECO Approvals Confirm that the Enabled box is checked. Launch the ECO Approval Alert concurrent program. (N) Alert Manager, Vision Enterprises > Request > Check Enter Application = Engineering, Alert = ECO Approvals Submit. (M:) > View > Requests Confirm radio button for All My Requests is enabled. Click the Find button to find all requests. Confirm that the request, ECO Approvals (Check Periodic Alert), completes successfully. Click the View Log button to confirm that the ALECDC module: Check Periodic Alert shows rows updated. Click the View Output button to confirm that actions defined in the ECO Approval Alert have completed. Confirm that the ECO Approval Status has been updated. (N) Engineering > ECOs > ECOs Query the ECO created in step #4 and observe that the Approval Status has been updated to Approval Requested. Confirm that email is received at the email address specified for your employee. Observe that the requestor name in the email is the same as that specified on the ECO.
6.
7.
8.
Page 30 of 39
2.
3.
Page 31 of 39
2.
Launch Oracle Workflow on your laptop or desktop: Start > All Programs > Oracle - Home > Application Development > Oracle Workflow Builder (your path may vary). In the workflow navigator, click the open file icon, which launches the Open window. Click the Database radio button and enter the following: User = apps Password = apps Connect = visinv02 Click OK, which opens the 'Show Item Types' window. This may take a few minutes. In the 'Show Item Types' window, choose 'ECO Approval' from the Hidden column list of values. Click the double arrow button to move the 'ECO Approval' to the Visible column. Click OK, which will load the 'ECO Approval' Item Type. This may also take a few minutes.
3.
View the Workflow: Click the plus sign (+) to expand apps@visinv02 Click the plus sign (+) to expand the ECO Approval Click the plus sign (+) to expand Processes Double click on the Standard Approval Process to display the process diagram.
Double click the Standard Approval Notification icon to display the activity properties. In the Navigator Control Properties window, click the Node tab. Confirm the Performer values Item Attribute for Type, and Approval List Name for Value.
The package ENG_WORKFLOW_API_PKG contains the procedures and functions for the ECO Approval Workflow and is created by file engwkfwb.pls. The ECO Approval Workflow Notification Process that is seeded in Release 11 and 11.5 Embedded Oracle Applications does the following:
Page 32 of 39
Description ----------------------------------------------------------------------------------------------------------* Mark start of process. * This activity, which is seeded by the Oracle Engineering product, sets pre-defined ECO attributes that can be used by this item type. * Gets the data from Eng_Engineering_Changes for the ECO Number (Change_Notice), Organization Id (Org_id). * This is the standard ECO Approval Notification seeded for Oracle Engineering. * Sends the Notification with the ECO Attributes collected above to the individuals in the Approval List using Workflow Notification Mailer.
Standard Approval
If Approved: Set MRP to Active * This function sets MRP Active to Yes for all "Open" or "Scheduled" revised items belonging to the ECO. * Updates Mrp_Active to 1 (Yes) in Eng_Revised_Items for Change_Notice, Org_Id and having a Status_Type of 1 (Open) or 4 (Scheduled). * This function sets the ECO's Approval Status to "Approved", sets the Approval Date to the current date and sets all "Open" revised items belonging to this ECO to Scheduled". * Updates Approval_Status_Type to 5 (Approved) and Approve_Date to Sysdate in Eng_Engineering_Changes table for Change_Notice, Org_Id. * Updates Status_Type = 4 (Scheduled) in Eng_Revised_Items table for Change_Notice, Org_Id. *Marks the end of the process.
Approve ECO
* This function sets MRP Active to No for all "Open" or "Scheduled" revised items belonging to the ECO. * Updates Mrp_Active to 2 (No) in Eng_Revised_Items for Change_Notice, Org_Id and having a status_type of 1 (Open) or 4 (Scheduled). * This function sets the ECO's Approval Status to "Rejected" and clears out the Approval Date. * Updates Approval_Status_Type to 4 (Rejected) and Approval_Date to NULL in Eng_Engineering_Changes for Change_Notice, Org_Id. *Marks the end of the process.
Reject ECO
End
Section III Create the ECO and Launch the Workflow Process
1. Create item ##Super1010 by copying from ##1010. Be sure to also enable it in the M1 organization. You will have to do this in the Inventory Master Item form since you transferred ##1010 to manufacturing. Create an Engineering Change Order (N) Engineering > ECOs > ECOs Tab to accept default ECO number. Make note of the ECO number: ________________________ Enter the ECO Type (###-Type), created earlier, which uses the standard workflow. The status will default to Open. Enter the Priority, which you associated with the ECO type (Standard). Enter your Approval List (###-List) The Approval Process should default to Standard; the process associated with your ECO Type and Priority. Bills of Material, Engineering Labs Page 33 of 39
2.
The Approval Status should default to Not submitted for approval. Save. Click the Revised Items button Use ##1000 as the revised item Set the change Effectivity Date one month from today using the LOV. For the revised components, disable ##1010 and add (replace it with) the ##Super1010. For the Add line, enter the same operation sequence and item sequence in the Op Seq New and Item Seq fields as the disabled line. Save. Launch the Workflow Process by clicking the Submit button. The Approval Status will change to Approval Requested. NOTE: Once submitted, you cannot change the ECO. You can abort the approval by selecting the Special Menu option and Abort Approval. When you abort, you can then make changes and resubmit. 3. Review the Notification (N) Engineering > ECOs > Notification Click the link in the Subject of the notification (ECO Approval Notification). Note the message, at top left of the form. ECO <eco number> is awaiting your approval. At the top right of the form, you will see the buttons Approve, Reject, Reassign and Request Information. There is also a ECO Form link, which would take you back to the application ECO form and open the ECO from which the notification was sent. Click the Approve button. NOTE: Notifications are sent when using the Standard Approval Process. Emails are only sent when using the Voting Approval Process. 4. Query the ECO to Check Current Status. (N) Engineering > ECOs > ECOs The ECO Status should now show Scheduled The Approval Status should now show Approved. To view the Approval History: Tools > View Approvals Click the Status button to view the Activity History
Page 34 of 39
3.
Assign planner to all three items at the child organization level. Change organizations to the M1 Seattle Manufacturing organization. (N) Manufacturing and Distribution Manager > Inventory > Items > Organization Items Query each of the three items. For each item, click the General Tab: Enter the planner created in step #1. Create Bill of Material (N) Manufacturing and Distribution Manager > Bills of Material > Bills > Bills Enter your finished good item, ##-FG1000, as the top assembly item. Bills of Material, Engineering Labs Page 35 of 39
4.
Enter the component ##-Useup Component 1. In the component Main tab, enter component Quantity = 2. This means that each assembly will require 2 components. Save.
2.
2.
Page 36 of 39
View Requests to confirm all processes complete normal. All processes must complete normal prior to the next step. You cannot confirm MRP demand until all processes have completed. About 21 processes will run as a result of launching the concurrent process. 3. Confirm Demand for the MRP Plan. (N) Manufacturing and Distribution Manager > Material Planning > MRP > Workbench Choose your MRP plan from the list of values. Click the Supply/Demand button. In the Find Supply/Demand form, click the Find button without entering any values. In the Supply/Demand form, confirm that there is demand created for both the finished assembly, ##-FG1000, and the bill component, ##-Useup Component 1, for each planned order. Review MRP Table Information. SELECT compile_designator mrp_plan_name, organization_id orgid, organization_code org, inventory_item_id item_id, planner_code planner, inventory_use_up_date use_up_date, description item_description FROM mrp_system_items WHERE compile_designator = '&MRP_PLAN_NAME'; At this point, you should see 2 lines, one for the top assembly and one for the component. Make note of the component inventory_use_up_date: ______________________________________
4.
Note: The contents of the effectivity date LOV can be queries using the following query: Make note of the Revised Item Effective Date: ___________________________________ This should match the use up date seen in the query of the MRP_SYSTEM_ITEMS table. Click on the Use Up Details tab. The Use-up Item and Plan name should now be populated with the use up item, description and plan name.
2.
Page 38 of 39
bill components, ##-Useup Component 1 and ##-Useup Component 2. 4. Review MRP Table Information. Select * From MRP_SYSTEM_ITEMS Where COMPILE_DESIGNATOR = &MRP_Plan_Name; At this point, you should see 3 lines, one for the top assembly and one for each component. Why are there now 3 lines? Make note of the inventory_use_up_date for ##-Useup Component 1: _____________________________ Has it changed? If so, why? Launch the Periodic Alert Scheduler, then View Requests (N) Alert Manager, Vision Enterprises >Request > Schedule View > Requests Click the radio button for Specific Requests. In the Name field, enter %Alert%. Click the Find button. You should see the Periodic Alert Scheduler in a Pending Scheduled status. Click the View Details button. On the Request Detail page, click the Schedule button. Choose As soon as possible and click OK. 5. Check your email for the Oracle Alert. You were defined as the planner on the items for this test. When the use up date is changed to an earlier date, the ECO Use Up Alert will send an email to the planner to review the new use up date. Modifying the effective date on the ECO is a manual process done after receiving the alert.
Page 39 of 39