How R4101P Validates to Delete Item and Considerations

Purpose of Document

Table of Contents

As business grows, the data from the Item Master may grow. This document will provide guidance on how to maintain a compact item master file by purging it regularly.

R4101P is to be run after R4102P has run successfully; as R4102P has a routine to check whether there is any open transaction across EnterpriseOne. So R4102P validates a transactional file based on the master file, whereas R4101P validates against master files.

What tables will be validated before data from the Item Master (F4101) gets deleted?

Below are tables to be validated:

  1. F4102 - Item Branch File
  2. F41021 - Item Location File
  3. F4105 - Item Cost File
  4. F4108 - Lot Master
  5. F3002 - Bill of Material Master File
  6. F3003 - Routing Master File
  7. F43090 - Supplier/Item Relationships

Note: Above information reflects validation sequence. So if F4102 contains item number to delete, it will exit from routine.

How does R4101P validate data from above tables?

It validates data through Business Functions to be listed below. This way we can minimize conflicts between F4101 and tables related.

  1. B4100210 - CheckItemBranch (F4102 Get Item Branch Row)
  2. XF41021 - VerifyAndGetItemLocation (F41021 Get Item Location Row)
  3. B4100060 - VerifyExistenceOfUnitCost (F4105 Verify Cost Existence)
  4. B4000610 - GetLotMasterByLotNumber (F4108, Get Lot Master Row)
  5. B4100060 - VerifyItemAsParentInBOM (F3002 Verify BOM Parent Existence)
  6. B4100060 - VerifyItemAsComponentInBoM (F3002 Verify BOM Component Existence)
  7. B4100190 - VerifyItemInRoutingFile (F3003 Verify Existence of Item)
Note: If all the validation is successful (there is no data from tables listed above based on item number in F4101) data from F4101 gets deleted and not to have orphaned data from Item Units of Measure Conversion Factors (F41002).