This document provides an overview of the physical inventory process in Oracle Inventory, including defining a physical inventory, taking a snapshot of on-hand quantities, generating tags, entering counts, approving adjustments, and posting adjustments. Key steps include defining criteria for the inventory, generating tags to match physical items to the system, entering count quantities, and making approved adjustments to update inventory records. The process integrates with cost management and general ledger modules to update item costs and inventory values.
The objective of this white paper is to assist users in better understanding and troubleshooting of discrete job closure issues. Additionally, common month end issues are addressed. When material and/or resource transactions are stuck, discrete job closure cannot be accomplished.
This presentation is about how to Create Line Sets like Ship / Arrival / Fulfillment in Oracle Order Management and Functionality as well as advantages of having line sets.
This presentation is about how to Create Drop Ship Sales Order Across the Operating Units in R12i and then how to perform Inter company Transactions.
Here I will discuss following Process
1.Drop Ship SO Creation
2.PO Creation
3.Receiving against PO
4.AP/AR Invoice Creation
5.Intercompany Invoice Creation
This document shows the complete Pick,Pack and Ship Confirm Process in Oracle Apps using Public APIs(includes sample codes and table names from various sources)
To understand following features:
OPM Inventory conversion.
Material traceability: Enhanced material control
Dual UOM functionality.
Material Status control.
Advanced Lot control.
Lot indivisibility functionality.
Material aging workflow.
The objective of this white paper is to assist users in better understanding and troubleshooting of discrete job closure issues. Additionally, common month end issues are addressed. When material and/or resource transactions are stuck, discrete job closure cannot be accomplished.
This presentation is about how to Create Line Sets like Ship / Arrival / Fulfillment in Oracle Order Management and Functionality as well as advantages of having line sets.
This presentation is about how to Create Drop Ship Sales Order Across the Operating Units in R12i and then how to perform Inter company Transactions.
Here I will discuss following Process
1.Drop Ship SO Creation
2.PO Creation
3.Receiving against PO
4.AP/AR Invoice Creation
5.Intercompany Invoice Creation
This document shows the complete Pick,Pack and Ship Confirm Process in Oracle Apps using Public APIs(includes sample codes and table names from various sources)
To understand following features:
OPM Inventory conversion.
Material traceability: Enhanced material control
Dual UOM functionality.
Material Status control.
Advanced Lot control.
Lot indivisibility functionality.
Material aging workflow.
ObjectivesUse inheritance to create base and child classes.docxmccormicknadine86
Objectives:
Use inheritance to create base and child classes
Utilize multiple classes in the same program
Perform standard input validation
Implement a solution that uses polymorphism
Problem:
A small electronics company has hired you to write an application to manage their inventory. The company requested a role-based access control (RBAC) to increase the security around using the new application. The company also requested that the application menu must be flexible enough to allow adding new menu items to the menu with minimal changes. This includes re-ordering the menu items and making changes to the description of a menu item without having to change the code.
Security:
The company has suggested to start the application by prompting the user for a username and password to authenticate the user. There are two types of users at this company, managers and employees. If managers log on to the application, they will see all options on the menu list. If employees log on to the application, they will see a limited set of options on the menu list. User information is stored in Users.dat file, which may or may not exist at the start of the program. A super user “admin” with password “admin” has already been hardcoded in the program to allow for the initial setup and the creation of other users. The Users.dat file contains the FirstName, LastName, Username (case insensitive), HashedPassword and a flag to indicate whether a user is a manager or not. The file is comma separated and it is formatted as follows:
Joe, Last, jlast, 58c536ed8facc2c2a293a18a48e3e120, true
Sam, sone, samsone, 2c2a293a18a48e3e12058c536ed8facc, false
Jane, Best, jbest, 293a18a48e3e12052058c536ed8facc2c, false
Note: Ensure that the 'AddUser' function does not add duplicate values, and the 'ChangePassword' function does not change password if username/password is entered incorrectly. If adding a new user or changing the password is successful, return true, or else return false.
Application Menu:
The menu of the application is dynamically loaded and displayed to the user only after the user successfully logs on. The menu items will be loaded from file “MenuList.dat”, which may or may not exist at the start of the application. If the file doesn’t exist, the application should show at least an Exit menu item as default. The file will contain all menu items details, including the name of the command that will be executed when the menu item is selected. If a menu item is marked as restricted (Boolean flag), only managers can see that item. The file contains the following comma separated fields, Description, a Boolean flag to indicate if the option is restricted to managers only, and the name of the menu command that will be executed when the option is chosen. The order and option number of a menu item may change depending on how they are listed in the file. The Exit option will always be listed last and it will not be in the file.
Below is a sample of how the MenuL.
Prosigns: Transforming Business with Tailored Technology SolutionsProsigns
Unlocking Business Potential: Tailored Technology Solutions by Prosigns
Discover how Prosigns, a leading technology solutions provider, partners with businesses to drive innovation and success. Our presentation showcases our comprehensive range of services, including custom software development, web and mobile app development, AI & ML solutions, blockchain integration, DevOps services, and Microsoft Dynamics 365 support.
Custom Software Development: Prosigns specializes in creating bespoke software solutions that cater to your unique business needs. Our team of experts works closely with you to understand your requirements and deliver tailor-made software that enhances efficiency and drives growth.
Web and Mobile App Development: From responsive websites to intuitive mobile applications, Prosigns develops cutting-edge solutions that engage users and deliver seamless experiences across devices.
AI & ML Solutions: Harnessing the power of Artificial Intelligence and Machine Learning, Prosigns provides smart solutions that automate processes, provide valuable insights, and drive informed decision-making.
Blockchain Integration: Prosigns offers comprehensive blockchain solutions, including development, integration, and consulting services, enabling businesses to leverage blockchain technology for enhanced security, transparency, and efficiency.
DevOps Services: Prosigns' DevOps services streamline development and operations processes, ensuring faster and more reliable software delivery through automation and continuous integration.
Microsoft Dynamics 365 Support: Prosigns provides comprehensive support and maintenance services for Microsoft Dynamics 365, ensuring your system is always up-to-date, secure, and running smoothly.
Learn how our collaborative approach and dedication to excellence help businesses achieve their goals and stay ahead in today's digital landscape. From concept to deployment, Prosigns is your trusted partner for transforming ideas into reality and unlocking the full potential of your business.
Join us on a journey of innovation and growth. Let's partner for success with Prosigns.
Cyaniclab : Software Development Agency Portfolio.pdfCyanic lab
CyanicLab, an offshore custom software development company based in Sweden,India, Finland, is your go-to partner for startup development and innovative web design solutions. Our expert team specializes in crafting cutting-edge software tailored to meet the unique needs of startups and established enterprises alike. From conceptualization to execution, we offer comprehensive services including web and mobile app development, UI/UX design, and ongoing software maintenance. Ready to elevate your business? Contact CyanicLab today and let us propel your vision to success with our top-notch IT solutions.
How Does XfilesPro Ensure Security While Sharing Documents in Salesforce?XfilesPro
Worried about document security while sharing them in Salesforce? Fret no more! Here are the top-notch security standards XfilesPro upholds to ensure strong security for your Salesforce documents while sharing with internal or external people.
To learn more, read the blog: https://www.xfilespro.com/how-does-xfilespro-make-document-sharing-secure-and-seamless-in-salesforce/
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...Shahin Sheidaei
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...Hivelance Technology
Cryptocurrency trading bots are computer programs designed to automate buying, selling, and managing cryptocurrency transactions. These bots utilize advanced algorithms and machine learning techniques to analyze market data, identify trading opportunities, and execute trades on behalf of their users. By automating the decision-making process, crypto trading bots can react to market changes faster than human traders
Hivelance, a leading provider of cryptocurrency trading bot development services, stands out as the premier choice for crypto traders and developers. Hivelance boasts a team of seasoned cryptocurrency experts and software engineers who deeply understand the crypto market and the latest trends in automated trading, Hivelance leverages the latest technologies and tools in the industry, including advanced AI and machine learning algorithms, to create highly efficient and adaptable crypto trading bots
Unleash Unlimited Potential with One-Time Purchase
BoxLang is more than just a language; it's a community. By choosing a Visionary License, you're not just investing in your success, you're actively contributing to the ongoing development and support of BoxLang.
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
Software Engineering, Software Consulting, Tech Lead.
Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Security,
Spring Transaction, Spring MVC,
Log4j, REST/SOAP WEB-SERVICES.
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
Understanding Globus Data Transfers with NetSageGlobus
NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?
Accelerate Enterprise Software Engineering with PlatformlessWSO2
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
Designing for Privacy in Amazon Web ServicesKrzysztofKkol1
Data privacy is one of the most critical issues that businesses face. This presentation shares insights on the principles and best practices for ensuring the resilience and security of your workload.
Drawing on a real-life project from the HR industry, the various challenges will be demonstrated: data protection, self-healing, business continuity, security, and transparency of data processing. This systematized approach allowed to create a secure AWS cloud infrastructure that not only met strict compliance rules but also exceeded the client's expectations.
Experience our free, in-depth three-part Tendenci Platform Corporate Membership Management workshop series! In Session 1 on May 14th, 2024, we began with an Introduction and Setup, mastering the configuration of your Corporate Membership Module settings to establish membership types, applications, and more. Then, on May 16th, 2024, in Session 2, we focused on binding individual members to a Corporate Membership and Corporate Reps, teaching you how to add individual members and assign Corporate Representatives to manage dues, renewals, and associated members. Finally, on May 28th, 2024, in Session 3, we covered questions and concerns, addressing any queries or issues you may have.
For more Tendenci AMS events, check out www.tendenci.com/events
In software engineering, the right architecture is essential for robust, scalable platforms. Wix has undergone a pivotal shift from event sourcing to a CRUD-based model for its microservices. This talk will chart the course of this pivotal journey.
Event sourcing, which records state changes as immutable events, provided robust auditing and "time travel" debugging for Wix Stores' microservices. Despite its benefits, the complexity it introduced in state management slowed development. Wix responded by adopting a simpler, unified CRUD model. This talk will explore the challenges of event sourcing and the advantages of Wix's new "CRUD on steroids" approach, which streamlines API integration and domain event management while preserving data integrity and system resilience.
Participants will gain valuable insights into Wix's strategies for ensuring atomicity in database updates and event production, as well as caching, materialization, and performance optimization techniques within a distributed system.
Join us to discover how Wix has mastered the art of balancing simplicity and extensibility, and learn how the re-adoption of the modest CRUD has turbocharged their development velocity, resilience, and scalability in a high-growth environment.
2. Understanding Physical Inventory
INTRODUCTION
Oracle Inventory provides several tools to aid users in controlling and improving the
accuracy of inventory records.
a. ABC Analysis
b. Cycle Counting
c. Physical Inventory
This white paper will give an overview of Physical Inventory, various steps involved,
associated tables, forms, packages, concurrent programs and reports.
EXECUTIVE OVERVIEW
Oracle Inventory provides a fully automated physical inventory feature. Physical
inventory is a periodic reconciliation of system on-hand balances with physical
counts in inventory.
Physical inventory can be performed, whenever there is a need to verify the accuracy
of system on-hand quantities. This can be done for entire organization or for
particular subinventories within an organization. Accurate system on-hand quantities
are essential for managing supply & demand, maintaining high service levels,
effective planning, minimizing inventory investment and for audit purpose.
Physical inventory and cycle counting can both be a part of annual program to
manage and improve inventory record accuracy. Cycle counting would be a daily,
weekly or monthly activity. Physical inventories might be performed at periodic
intervals - monthly, quarterly, annually and so on. One strategy is to only perform
physical inventories as required to satisfy auditors of the organization.
INTERFACES
Physical inventory integrates with Oracle Cost Management and Oracle General
Ledger. If there is a quantity discrepancy for items, Inventory derives the item costs
from Cost management and posts the inventory value changes to General Ledger.
Oracle Cost Management Physical Inventory Oracle General Ledger
Item Costs Quantity Changes Inventory Value Changes
3. STEPS INVOLVED IN PHYSICAL INVENTORY
Define Physical Inventory
Take a Snapshot of system On–hand quantities
Generate Physical Inventory Tags
Enter Counts
Approve or Reject Physical Inventory Adjustments
Post Adjustments
Purge Physical Inventory information
1. DEFINE PHYSICAL INVENTORY
Unlimited number of physical inventories can be defined and maintained to count
selected portions of inventory or total inventory. A physical inventory is identified
by a unique name. To define physical inventory navigation is Inventory -> Counting
-> Physical Inventory -> Define Physical Inventory
4. a. Enter a unique physical inventory name in the name field
b. Select approval requirements for the adjustment. Options available are
Always: Requires approval for all physical inventory adjustments.
Adjustments program cannot be run until all the adjustments are approved.
If out of tolerance: Quantity and / or Value adjustment tolerances can be
entered. Adjustments exceeding tolerances must be approved before running
the adjustment program.
Adjustment value = (Actual count - System count) x Item cost
Never: Allow any adjustment to post without approval.
Choose when to Approve adjustments
Enter Tolerances
Specify Scope
Enable or disable Dynamic Tag entry
c. Enter positive and negative approval tolerances
d. Select the scope of physical inventory
Determines whether the physical inventory is for all subinventories of the
organization or for one or more specific subinventories. Enter only quantity-
tracked subinventories
e. Indicate whether to allow dynamic entry of tags
Determines whether manually created tags can be entered. If the option is
not to allow dynamic tag entry all tags must generated before the use.
5. Technical Notes:
When physical Inventory definition is saved the following table–column values are
inserted / updated
Tables Columns Updated / Inserted
MTL_PHYSICAL_INVENTORIES PHYSICAL_INVENTORY_ID
ORGANIZATION_ID
ALL_SUBINVENTORIES_FLAG
Permitted values are
1 - Yes (All subinventories)
2 - No (Specific subinventories)
APPROVAL_REQUIRED
Permitted values are
1 - Required for all adjustments
2 - Not Required for adjustments
3 - Required for adjustments out of
tolerance
APPROVAL_TOLERANCE_POS
APPROVAL_TOLERANCE_NEG
(Updated if approval required is
3-‘If Out of tolerance’ and choose +ve /
-ve tolerance for quantity)
COST_VARIANCE_POS
COST_VARIANCE_NEG
(Updated if approval required is
3-‘If Out of tolerance’ and choose +ve /
-ve tolerance for cost)
DYNAMIC_TAG_ENTRY_FLAG
Permitted values are
1 - Yes (Allowed)
2 - No (Not Allowed)
MTL_PHYSICAL_SUBINVENTORIES While defining the physical inventory
if user chooses
ALL_SUBINVENTORIES_FLAG as
1 –Yes(All subinventories) no data is
populated.
6. While defining the physical inventory
if user chooses
ALL_SUBINVENTORIES_FLAG as
2-No (Specific subinventories) the
fields updated are
PHYSICAL_INVENTORY_ID
ORGANIZATION_ID
SUBINVENTORY
MTL_PHYSICAL_INVENTORY_TAGS Nil
MTL_PHYSICAL_ADJUSTMENTS Nil
Form Name: Define Physical Inventory
Short Name: INVADPPI
2. SNAPSHOT OF SYSTEM ON–HAND QUANTITIES
To run the snapshot navigation is Inventory -> Counting -> Physical Inventory ->
Define Physical Inventory -> Choose the Snapshot button
Snapshot must be completed before generating the tags. After taking the snapshot,
system will no longer allow to update header information of the physical inventory.
The snapshot saves all item on–hand quantities and costs and uses this information as
the basis for all physical inventory adjustments rather than the current on-hand
quantity. System allows to resume transaction activities even before running the
adjustments program for the physical inventory .Therefore need to procedurally
coordinate snapshot of physical inventory with actual counting and ensure that no
transaction activity occurs in a particular location until adjustments are launched and
posted.
Once snapshot concurrent process is finished, the snapshot complete box is checked,
the snapshot date is updated and the Tags button is enabled in the define physical
inventory window.
7. Technical Notes: When
snapshot is finished the following table–column values are inserted / updated
Tables Columns Updated / Inserted
MTL_PHYSICAL_INVENTORIES
( MPI )
FREEZE_DATE
NUMBER_OF_SKUS : Number of
SKU’s are calculated and updated .
MTL_PHYSICAL_SUBINVENTORIES Nil
MTL_PHYSICAL_INVENTORY_TAGS Nil
MTL_PHYSICAL_ADJUSTMENTS
( MPA )
ADJUSTMENT_ID : Number of rows
equal to NUMBER_OF_SKUS of
MPI are inserted
PHYSICAL_INVENTORY_ID
ORGANIZATION_ID
SUBINVENTORY_NAME
INVENTORY_ITEM_ID
SYSTEM_QUANTITY
ADJUSTMENT_QUANTITY will be
set as –ve of SYSTEM_QUANTITY
ACTUAL_COST
REVISION LOCATOR_ID
LOT_NUMBER
LOT_EXPIRATION_DATE
SERIAL_NUMBER
The concurrent program INCAPF - Freeze Physical Inventory executes the
following
· Updates the Freeze date in MTL_PHYSICAL_INVENTORIES table.
· Calculate and insert number of SKU’s in physical inventory into
MTL_PHYSICAL_INVENTORIES table.
· Adjustment records will be inserted into
MTL_PHYSICAL_ADJUSTMENTS table.
· Cost of the items will be calculated and updated in
MTL_PHYSICAL_ADJUSTMENTS table
· The On-hand quantity of the items will be calculated from table
MTL_ONHAND_QUANTITIES and updates in
MTL_PHYSICAL_ADJUSTMENTS.
8. 3. GENERATE PHYSICAL INVENTORY TAGS
Physical inventory tags are used to record the count of inventory items. Tags are
referred by its alphanumeric identification code. Oracle Inventory can automatically
generate tag numbers that can be used to enter inventory counts. Tags can be
generated only after snapshot is completed. The system also supports using numbers
generated outside the Oracle Inventory. There should be only one item on a tag but
multiple tags can refer to the same item .
Physical Inventory can be performed for items under serial control. If default tags
are generated, system generates one tag per item per serial number.
Dynamic Tag Entry : Determines whether manually created tags can be entered or
not . If the option is not to allow dynamic tag entry, all tags must be generated
before the use. Dynamic Tag Entry is allowed when tag numbers are generated
outside the system. For example when using third-party pre-numbered tags.
Option 1: Dynamic Tag Entry
No need to run the Tag Generation program
Use own tag numbers while entering the counts
Default Tags : Contain information on items in the physical inventory definition.
Generates a tag for each SKU i.e. unique combination of item, subinventory, locator,
revision, lot number and serial number that exists in the subinventories of physical
inventory.
Option 2: Default Tags
Specify the starting tag number and digit increments
Run the Tag Generation program
Use system generated tag numbers to enter counts
9. Blank Tags: Do not contain any information about the items in physical inventory
definition. Blank tags can be generated to enter counts for those items whose
locations are not currently recorded in the system.
Option 3: Blank Tags
Specify the starting tag number and digit increments
Specify quantity of tags or the ending tag number
Run the Tag Generation program
Use system generated tag numbers to enter counts
To generate the tags navigation is Inventory -> Counting -> Physical Inventory ->
Tags Generation -> Choose Generate button
a. Enter the name of the physical inventory.
b. Select the type of tag to create.
10. c. Indicate whether it is required to show serial numbers on the physical
inventory tags. If the option is not to show serial numbers on the tags,
system will generate a tag for each item but user has to match the serial
numbers to the items manually. It is allowed to enter a value in this field
only if tag type selected is default.
d. Enter the starting tag number for example - 0001 and say user wants the
increment to be 5, then for the increment enter 1115. The increment field
should have the number of digits the starting tag has and it should have 1's
preceding what the actual increment value would be. Tag numbers may be
alphanumeric, but increment will be done only for the numeric portion.
e. Choose the Generate button to create the tag numbers and information. Note
that this process does not physically print the tags. To print the tags, user
need to run the Physical Inventory Tags report using the navigation
Inventory -> Reports -> ABC and Counting -> Run Physical Inventory Tags
report
Technical Notes: When the
tags are generated the following table–column values are inserted / updated
Tables Columns Updated / Inserted
MTL_PHYSICAL_INVENTORIES Based on the increment that is entered
while generating the tags the following
columns are updated
NEXT_TAG_NUMBER
TAG_NUMBER_INCREMENTS
MTL_PHYSICAL_SUBINVENTORIES Nil
MTL_PHYSICAL_INVENTORY_TAGS PHYSICAL_INVENTORY_ID
ORGANIZATION_ID
TAG_ID
VOID_FLAG is set to 2.
Possible values are 1-Void, 2- Active
TAG_NUMBER
ADJUSTMENT_ID
SUBINVENTORY
REVISION
LOCATOR_ID
LOT_NUMBER
LOT_EXPIRATION_DATE
SERIAL_NUMBER
11. MTL_PHYSICAL_ADJUSTMENTS Nil
Form Name: Generate Physical Inventory tags
Short Name: INVARPGT
Concurrent program INCAPT - Generate physical Inventory Tags executes
the following
· Gets ORGANIZATION_ID for particular PHYSICAL_INVENTORY_ID
from MTL_PHYSICAL_INVENTORIES table
· NEXT_TAG_NUMBER and TAG_NUMBER_INCREMENTS will be
calculated and updated in MTL_PHYSICAL_INVENTORIES
· Inserts the records to MTL_PHYSICAL_INVENTORIES using the
sequence MTL_PHYSICAL_INVENTORY_TAGS_S
· Generates tag numbers based on the starting tag number & the increment
and insert the records in to table MTL_PHYSICAL_INVENTORY_TAGS
table
· Generates pre printed tags by fetching rows from
MTL_PHYSICAL_ADJUSTMENTS table for a
PHYSICAL_INVENTORY_ID and insert tag numbers in
MTL_PHYSICAL_INVENTORY_TAGS table
4. ENTER COUNTS
Generated tags are used to record the physical counts. After recording the physical
counts user must enter the quantity for each tag. To enter the Tag counts the
navigation is Inventory -> counts -> Physical Inventory -> Tag Counts.
Navigate to the Physical Inventory Tag Counts window. Enter name of the employee
that performed the physical inventory in the Default Counter field. This is used as a
default for the Counted by field of each tag.
If the default tags are used, the system will display the tags with relevant item
information. User need to enter only the quantity counted for each tag. User can also
query a subset of tags by any combination of tag number, item, revision,
subinventory, locator, lot and serial number.
If blank tags are used in the physical inventory, user can query up the tags by tag
number. The system displays the tags but no item information. Need to enter the
count quantity as well as the item information i.e. item name, subinventory, locator,
revision, lot and serial numbers.
If dynamic tags are allowed in physical inventory definition user can enter tag
numbers generated outside the system. User needs to enter the count quantity as well
as the item information.
12. Void Tags: If any of the tags are not used, they have to be voided, as this is necessary
for auditing purpose. A voided tag is not reported as a missing in the Physical
inventory Missing Tag Listing report. Tags can be voided if they are lost, damaged or
discarded before the approval or before the adjustment process. If a default tag is
voided Oracle Inventory adjusts the quantity in that location to zero.
Technical Notes:
After entering the counts and save the following table–column values are inserted /
updated
Tables Columns Updated / Inserted
MTL_PHYSICAL_INVENTORIES Nil
MTL_PHYSICAL_SUBINVENTORIES Nil
MTL_PHYSICAL_INVENTORY_TAGS TAG_QUANTITY is set as equal to
COUNT_QUANTITY entered
If Tag is voided TAG_QUANTITY is
updated as Null and VOID_FLAG is set
to 1.
TAG_UOM
COUNTED_BY_EMPLOYEE_ID
13. COST_GROUP_ID
MTL_PHYSICAL_ADJUSTMENTS COUNT_QUANTITY
ADJUSTMENT_QUANTITY set as
equal to [(COUNT_QUANTITY)–
(SYSTEM_QUANTITY)]
Form Name: Physical Inventory Tag Counts
Short Name: INVADPTE
5. APPROVING PHYSICAL INVENTORY ADJUSTMENTS
Oracle Inventory supports two types of physical inventory approval tolerances i.e.
quantity tolerances and cost tolerances. For each type, it is allowed to specify a
positive and a negative limit. The adjustments that can be viewed from this window
are determined by the approval option selected while defining the physical inventory.
If a particular adjustment is approved, physical Inventory Adjustments program
adjusts inventory balance by that quantity. If an adjustment is rejected, Oracle
Inventory does not change the system on–hand quantity.
Navigation to approve physical Inventory adjustments is Inventory -> Counting ->
Physical Inventory -> Approve Adjustments
a. Select the physical inventory and choose approve.
b. Enter the name of the employee approving the adjustments.
c. Select an adjustment to approve or reject and check the Approve/Reject
option.
User must either approve or reject all adjustments of the physical inventory before
running adjustments program.
Technical Notes:
When physical Inventory records are approved the following table–column values
are inserted / updated
Tables Columns Updated / Inserted
MTL_PHYSICAL_INVENTORIES Nil
MTL_PHYSICAL_SUBINVENTORIES Nil
MTL_PHYSICAL_INVENTORY_TAGS Nil
MTL_PHYSICAL_ADJUSTMENTS APPROVAL_STATUS set to
1 – if approved
2 – if rejected
14. Permitted values are
1-Approved
2-Rejected
3-Posted
APPROVED_BY_EMPLOYEE_ID
Form Name: Approve Physical Inventory
Adjustments
Short Name: INADPAP
6. POST ADJUSTMENTS
After entering all the tag counts and approve the adjustments that need approval, user
can submit the process that posts the physical inventory adjustments. This will
automatically creates a material transaction, adjusting the item quantity and
debiting/crediting the adjustment account specified for the physical inventory. If the
count of an item matches with the snapshot system on–hand quantity, there will be
no adjustment transaction posted.
Once the adjustment program is completed it does not allow new tag generation and
no longer will be able to make changes to the physical inventory. Oracle Inventory
will not post adjustments, if any adjustment is pending for approval.
User must approve or reject all the adjustments before running the adjustment
program. Adjustments can be previewed before actually posting them by running the
Physical inventory adjustments report. If the approval option for a particular physical
inventory is Never, Oracle Inventory does not at any time prevent from submitting
the adjustment process. For any tag that has no count entered, it assumes a count of
zero and performs adjustment transactions accordingly.
To run the adjustment program
a. Navigate to the Physical Inventories Summary window.
b. Select the physical inventory.
c. Choose Launch adjustments from the Tools menu. The Launch Adjustments
window appears.
d. Enter the Adjustment Account number against which adjustments should be
charged.
e. Enter the adjustment date.
f. Choose the Launch Adjustments button to submit the concurrent request.
15. Technical Notes:
When post adjustments program is run the following table-column values are
inserted / updated
Tables Columns Updated / Inserted
MTL_PHYSICAL_INVENTORIES LAST_ADJUSTMENT_DATE
TOTAL_ADJUSTMENT_VALUE
MTL_PHYSICAL_SUBINVENTORIES Nil
MTL_PHYSICAL_INVENTORY_TAGS Nil
MTL_PHYSICAL_ADJUSTMENTS
(MPA)
GL_ADJUST_ACCOUNT
APPROVAL_STATUS is set to
3 - Posted
MMTT / MMT Records will be inserted for the
difference of quantity i.e.
[(COUNT_QUANTITY)–
(SYSTEM_QUANTITY)]
DISTRIBUTION_ACCOUNT_ID of
MMT is set to
GL_ADJUST_ACCOUNT of MPA
PHYSICAL_ADJUSTMENT_ID of
MMT is set to ADJUSTMENT_ID of
MPA.
MMTT is MTL_MATERIAL_TRANSACTIONS_TEMP table
MMT is MTL_MATERIAL_TRANSACTIONS table
The concurrent program INCAPA- Perform Physical Inventory Adjustments is
responsible for posting the adjustments and executes the following
· Checks for adjustment records, which are pending approval/rejection .If
there are any pending, then no adjustments will be posted.
· Gets the approved records from MTL_PHYSICAL_ADJUSTMENTS for
which adjustment quantity is not equal to zero.
· Gets description, tolerance from MTL_PHYSICAL_ADJUSTMENTS.
· Gets period close id for adjustment date and check whether it is in open
period.
· Gets transaction_id from sequence. Takes 100 transactions and then
16. commit.
· The adjustment transaction records are inserted into
MTL_MATERIAL_TRANSACTIONS_TEMP
· If the item is lot, serial controlled the records are also inserted into
MTL_TRANSACTION_LOT_NUMBERS
MTL_SERIAL_NUMBERS_TEMP and respectively
· Updates the table MTL_PHYSICAL_ADJUSTMENTS with approval
status
· Updates the table MTL_PHYSICAL_INVENTORIES with adjustment
date and value.
7. PURGE PHYSICAL INVENTORY INFORMATION
Purging physical inventory will delete definition from the database. Purge does not
affect any adjustments or adjustment transactions made using the physical Inventory.
Options to choose while purging are ‘Tags only’ or ‘All’.
Tags Only: Purges all the tags associated with a physical inventory definition. If
irreversible mistakes are made in the count-entry phase, user can start over without
refreezing the inventory.
All: Purges the physical inventory definition, frozen quantities, tags and count
quantities.
Identify the Physical Inventory to be purged
Choose Purge option: Tags only or All
To run the purge program
a. Navigate to the Physical Inventories Summary window.
b. Select the physical inventory
c. Choose Perform purge from the Tools menu.
d. Choose purge option ‘Tags only’ or ‘All’
17. Technical Notes:
When Purge program is run using Tags only option the following table–column values
are inserted / updated / deleted
Tables Columns Updated/Inserted/Deleted
MTL_PHYSICAL_INVENTORIES Resets the value of the fields
NEXT_TAG_NUMBER and
TAG_NUMBER_INCREMENTS to
Null
MTL_PHYSICAL_SUBINVENTORIES Nil
MTL_PHYSICAL_INVENTORY_TAGS All records of physical Inventory will
be deleted
MTL_PHYSICAL_ADJUSTMENTS COUNT_QUANTITY is set to Null
ADJUSTMENT_QUANTITY is set as
-Ve of (SYSTEM_QUANTITY)
When Purge program is run using ‘All’ option the following table–column values are
inserted / updated / deleted
Tables Columns Updated/ Inserted / Deleted
MTL_PHYSICAL_INVENTORIES Purge program checks for adjustment
transaction rows of that physical
inventory in
MTL_MATERIAL_TRANSACTIONS
table with
TRANSACTION_ACTION_ID=8 .
If no rows found, deletes the header
details of physical inventory.
To reuse the physical Inventory name
the adjustment transaction rows should
be purged from table
MTL_MATERIAL_TRANSACTIONS
and run the physical Inventory
purge – All
MTL_PHYSICAL_SUBINVENTORIES All records of physical Inventory will
be deleted
MTL_PHYSICAL_INVENTORY_TAGS All records of physical Inventory will
be deleted
MTL_PHYSICAL_ADJUSTMENTS All records of physical Inventory will
be deleted
18. The concurrent program INCAPP-Purge Physical Inventory Information executes
the following
· Gets the valid organization ID.
· Checks for adjustment record approval status 3 - Posted for purging the
records
· If the purge type is ‘All’ the records from the tables will purged in the
following order
o MTL_PHYSICAL_ADJUSTMENTS
o MTL_PHYSCIAL_SUBINVENTORIES
o MTL_PHYSICAL_INVENTORY_TAGS
o MTL_PHYSICAL_INVENTORIES – records will not be deleted if
adjustment transaction rows of that physical inventory are found in
MTL_MATERIAL_TRANSACTIONS table.
· If the purge type is ‘Tag Only’
o Records will be purged from
MTL_PHYSICAL_INVENTORY_TAGS table
o Updates MTL_PHYSICAL_ADJUSTMENTS with count and
adjustment quantities
o Resets tag information in MTL_PHYSICAL_INVENOTRIES table
PACKAGES
a. INV_PHY_INV_LOVS (INVPINLS.pls / INVPINLB.pls)
This will check for valid physical Inventories. Returns the count of physical
tag records for a given serial number inputted. This will validate whether
inputted serial is within the scope of the physical inventory i.e. exists in a
subinventory which physical inventory covers. This package also includes
API's to process a tag entry in a physical count.
b. INV_UI_ITEM_SUB_LOC_LOVS (INVITPSS.pls / INVITPSB.pls)
This will check for valid subinventories and locators associated with
physical Inventory.
c. INVADPT1 (INVADPTS.pls / INVADPTB.pls)
This server side package used by the form INVADPTE to update the table
MTL_PHYSICAL_ADJUSTMENTS
d. INV_CG_UPGRADE (INVCGUGB.pls / INVCGUGS.pls)
Records that do not have a default cost group will be identified and assigned
with cost group.
19. e. INV_UI_ITEM_LOVS (INVITMLS.pls / INVITMLB.pls)
Returns valid items that are associated with a given physical inventory.
Returns LOV rows for a given organization, item and user input text.
Returns LOV rows for a given organization, item and user inputted text for
valid uom's.
f. INV_INV_LOVS (INVINVLS.pls / INVINVLB.pls)
Returns a valid cost group associated with the given parameters. Returns lot
numbers for a given organization and inventory item within a particular
physical inventory
g. INV_UI_ITEM_ATT_LOVS (INVITATS.pls/ INVITATB.pls)
Return valid serial numbers for physical inventory when performing serial
triggered tag counts.
REPORTS
The following reports will help during the process of performing physical inventory.
Run these reports using the navigation Inventory -> Reports -> ABC and Counting ->
Choose to run one of the following reports.
Report Name: Physical Inventory Tags report
Short Name: INVARPTP
Use Physical Inventory Tags report to print the tags. This report prints all the tags or
range of tags for a single subinventory/all subinventories for a specified physical
inventory. Physical inventory tags represent actual hard copy of tags that companies
use to count inventory items. A tag contains the count of a given item.
Report Name: Physical Inventory Tag Listing report
Short Name: INVARPTG
This report lists all the default and blank tags that are generated and the entire
dynamic tags that are entered. Use the Physical Inventory Tag Listing to review the
tags created by the ‘Generate Physical Inventory Tags’ process.
Report Name: Physical Inventory Counts report
Short Name: INVARPSL
Shows information on the tags including the item, item controls, count location,
count quantity and count value.
20. Report Name: Physical Inventory Missing Tag Listing report
Short Name: INVARPMT
This report lists the tags that are missing from a user–specified range of tag numbers.
If the counts are not entered for the tag, it is considered as missing tag. Void tags are
not considered to be missing. Use this report before initiating physical adjustments to
verify all tags generated by the system.
Report Name: Physical Inventory Adjustments report
Short Name: INVARPAR
This report shows all adjustments against each SKU of physical inventory. Run this
report before processing the adjustments to get a preview of adjustment quantities
and values. This report is also automatically generated after the successful
completion of the adjustment program as a record of what was actually adjusted.
Report Name: Physical Inventory Accuracy Analysis report
Short Name: INVARPIA
Review the output of this report at various stages of physical Inventory i.e. snapshot,
entering tag counts..etc. This report can be used as a historical accuracy analysis tool.
Report Name: Physical Inventory Trend and Summary analysis report
Short Name: INVARPTS
While running the report choose to run either Summary Report or Trend Report
a) Summary report: Provides a summary of physical inventory adjustments by
subinventory. The output shows system on–hand value, actual count value, resulting
adjustment value in functional currency as well as the number of tags and
adjustments performed for each subinventory.
b) Trend report: This report compares past physical inventories to gauge the
accuracy level improvement over time. It provides a summary of physical inventory
adjustment values by date and subinventory as well as number of tags and
adjustments each subinventory required.
CONCLUSION
Using physical Inventory feature requires an understanding of the customer business
process. Physical Inventory has to define as per the company cost and quantity
discrepancy approval policy.