This chapter covers the following topics:
This flow is used to create a new collection plan, adding elements to the collection plan, copying the plan and deleting the elements and the plan.
Hybrid: PLSQL
Create_Plan_Copy_Plan_Add_Element_Delete_PLSQL
Not Applicable
Not Applicable
The following predefined data must be used:
| Entity | Field Name | Field Value |
|---|---|---|
| User | User Name | MFG |
| Responsibility | Responsibility | Manufacturing and Distribution Manager |
| Organization | Inventory Organization | M1- Seattle Manufacturing |
Not Applicable
Following are the details of the scenarios in the flow:
| Scenario | Objective | Artifact Method | Component Set | Main Component |
|---|---|---|---|---|
| New_Plan | This scenario creates a New Plan | QA_PLANS_PUB_CREATE_COLLECTION_PLAN | - | QA_PLANS_PUB_CREATE_COLLECTION_PLAN_Main |
| Add_Element_To_New_Plan | This Scenario adds an Element to the new plan | QA_PLANS_PUB_ADD_PLAN_ELEMENT | - | QA_PLANS_PUB_ADD_PLAN_ELEMENT_Main |
| Copy_Plan | This scenario copies the existing plan to the new Plan | QA_PLANS_PUB_COPY_COLLECTION_PLAN | - | QA_PLANS_PUB_COPY_COLLECTION_PLAN_Main |
| Add_Element_To_Copied_Plan | This scenario adds an Element to the Copied plan | QA_PLANS_PUB_ADD_PLAN_ELEMENT | - | QA_PLANS_PUB_ADD_PLAN_ELEMENT_Main |
| Add_Another_Element_To_Copied_Plan | This scenario adds another Element to the Copied plan | QA_PLANS_PUB_ADD_PLAN_ELEMENT | - | QA_PLANS_PUB_ADD_PLAN_ELEMENT_Main |
| Delete_Element_From_Copied_Plan | This scenario deletes the Element from the Copied Plan | QA_PLANS_PUB_DELETE_PLAN_ELEMENT | - | QA_PLANS_PUB_DELETE_PLAN_ELEMENT_Main |
| Delete_Existing_Plan | This Scenario Deletes the Newly Copied Plan | QA_PLANS_PUB_DELETE_COLLECTION_PLAN | - | QA_PLANS_PUB_DELETE_COLLECTION_PLAN_Main |
| Delete_Based_Plan | This Scenario Deletes the created Plan | QA_PLANS_PUB_DELETE_COLLECTION_PLAN | - | QA_PLANS_PUB_DELETE_COLLECTION_PLAN_Main |
This open interface flow is used to insert Quality Results to the interface table and inserts the records in to the base table by running the concurrent program Collection Import Manager. This flow is also used to verify the quality results entered through UI and forms.
Hybrid: Open Interface (O/I)
QA_Results_Interface_OI
The plan, collection elements and mandatory data for the Collection Elements should be available in the system for entering the quality results.
Not Applicable
The following predefined data must be used:
| Entity | Field Name | Field Value |
|---|---|---|
| User | User Name | MFG |
| Responsibility | Responsibility | Manufacturing and Distribution Manager |
| Organization | Inventory Organization | M1- Seattle Manufacturing |
The following data must be set up:
| Transaction | Field Name | Field Value |
|---|---|---|
| Collection Plan | A Collection Plan for which the results should be entered should exist in the Organization. For entering the results we have selected the plan Mentioned in the Field Value. | WIP COMPLETION COLLECTION PLAN |
| Collection Elements | A Collection Plan should have the Collection Elements assigned for Entering the Results. | All the Collection Plan elements that are attached to plan will be taken in to consideration for entering the results. |
| Mandatory Fields Data | All Mandatory Fields Collection Element Data should Exist in the system | Item and Job are the Mandatory Elements for the Collection Plan WIP COMPLETION COLLECTION PLAN. Hence the Item and Job has to be Provided. In this context we have used Item AS54888 and Job 266904 for entering the results. |
Following are the details of the scenarios in the flow:
| Scenario | Objective | Artifact Method | Component Set | Main Component |
|---|---|---|---|---|
| QA_Results_Interface | This scenario is to insert records to the Quality results interface and validate the results in both Forms and UI | Collection_Import_Manager_QLTTRAMB | Collection_Import_Manager_QLTTRAMB | Collection_Import_Manager_QLTTRAMB |
| Verify_Result_Informs | Verify_Quality_Results | - |
This flow is used to create an Item and assign an item to required Organizations and Create an Bill of material.
Hybrid: PLSQL
Create_Item_Assign_Org_BOM_PLSQL
Not Applicable
Not Applicable
The following predefined data must be used:
| Entity | Field Name | Field Value |
|---|---|---|
| User | User Name | MFG |
| Responsibility | Responsibility | Manufacturing and Distribution Manager |
| Organization | Inventory Organization | M1- Seattle Manufacturing |
Not Applicable
Following are the details of the scenarios in the flow:
| Scenario | Objective | Artifact Method | Component Set | Main Component |
|---|---|---|---|---|
| Create_Item | This scenario creates a New Item. | EGO_ITEM_PUB_PROCESS_ITEMS | EGO_ITEM_PUB_PROCESS_ITEMS | EGO_ITEM_PUB_PROCESS_ITEMS_Main |
| Org_Assignment | This Scenario assigns the Item to the required Inventory Orgs | EGO_ITEM_PUB_PROCESS_ITEM_ORG_ASSIGNMENTS | EGO_ITEM_PUB_PROCESS_ITEM_ORG_ASSIGNMENTS | EGO_ITEM_PUB_PROCESS_ITEM_ORG_ASSIGNMENTS_Main |
| Create_BOM | This scenario creates Bills of Material. | BOM_BO_PUB_PROCESS_BOM | BOM_BO_PUB_PROCESS_BOM | BOM_BO_PUB_PROCESS_BOM_Main |
| Verification_BOM | - | VERIFICATION_COMPONENT |
This Open Interface is used for creating a new discrete job.
Hybrid: Open Interface
WIP_Mass_Load_Create_WIP_JOB_OI
Not Applicable
Not Applicable
The following predefined data must be used:
| Entity | Field Name | Field Value |
|---|---|---|
| User | User Name | MFG |
| Responsibility | Responsibility | Manufacturing and Distribution Manager |
| Organization | Inventory Organization | M1- Seattle Manufacturing |
Not Applicable
Following are the details of the scenarios in the flow:
| Scenario | Objective | Artifact Method | Component Set | Main Component |
|---|---|---|---|---|
| WIP_Mass_Load_Create_WIP_JOB | This scenario is for creating a new job. | WIP_Mass_Load_WICMLP | WIP_Mass_Load_WICMLP | WIP_Mass_Load_WICMLP |
| Verification | This scenario verifies if the new job is created | VERIFICATION_COMPONENT | - | VERIFICATION_COMPONENT |