Академический Документы
Профессиональный Документы
Культура Документы
1. Which intra operation steps might you want to enable if you have a just-in-time production
environment?
Ans: You would probably enable only Run and To Move to model your environment.
2. You cannot move more assemblies than are available at a routing operation.
a) True b) False
3.What are the three transaction available in WIP?
Ans: Material transaction, Move transaction, Resource transaction.
4.When the lot based resource gets charged?
Ans: When the first unit is moved, the lot based resources will be charged.
5.In a assembly, all the components have supply type as operational pull, they are serial
controled. During move transaction, how we can select the serial numbers.
Ans: During move transaction, a window Backflush will popup, there we can select serial
numbers.
6.For an assembly, the move transaction does not allow me to complete in that screen iteself?
What will be the problem.
Ans: The assembly will be serial control, therefore you have to complete it in completion
transaction screen only
7.In an assembly, one of the item has supply type = bulk, what transaction should i perform.
Ans: no need to perform any transaction, it is just a label.
8.In profile option, WIP: Define discrete job, it has been defined as concurrent. While creating a
Discrete order, what concurrent will be running?
Ans: WIP concurrent exploder.
9.Explain shopfloor status?
Ans: Shop floor status are control move transactions which can be assigned to interaoperations
steps.
10.What are the two types of scheduling available in WIP?
Ans: Dynamic lead time offsetting and Detailed scheduling.
11. Which status in discrete job cannot be reversed?
Ans: Complete No charges
12.Which field in Discrete job is non- editable before saving?
Ans: UOM
13.How can we add material and Resource in a discrete job? What is the implicaiton of this action
on bills and routing?
Ans: In Job / Schedule details we can add materials and resource for the particulat order. This will
be effect for this order only. Engineering BOM and Manufacturing BOM has no effect.
14.What is repetative schedule?
Ans: Repetative schedule builts an assembly on a line at specifited production rate and for
specified number of days.
8.What are the status of DJ ( both user status and Processing status)
Ans
S.No User status Processing Status
1 Unreleased Pending routing load
2 released Failed routing load
Complete Pending bill load
Complete No charge Failed bill load
Cancel Pending scheduling
Hold Pending closed
Closed Failed close
9.Can i complete an assembly with out order? Explain in detail
Ans: Yes, In Workorder less completion we can complete an assembly with out order.
Ther are 4 options available: WIP assembly compeltion , WIP assembly return, WIP assembly scrap,
WIP return from scrap.
10.How to unclose an order, what are the prequestes for forecast
Ans: In Close Discrete jobs form query with the order number. Tools--> Unclose.
The prequestes are a) Job status should be closed.
b) Accounting period should be open
Discrete Jobs
Supply Type
i. Based on Bill
Components required for the Bill has to be issued. Method of issuing the components is given as
supply type in Bill of Material. If we can use the same , select based on Bill.
ii. Push
If all the components to be used as PUSH type, select PUSH. In PUSH, we need to issue the
components through WIP Component Issue transactions before starting the Job.
iii. Operation Pull
Components Issue will be taken care of by the system itself. Once the operation is completed,
required components will be pulled from the mentioned supply subinventory .
iv. Assembly Pull
Once the assembly is completed, required components for that assembly will be pulled from the
given supply subinventory.
v. Supplier
Issue of item by supplier, need not to transact this item . It is only for reference only to
items.
Supply subinventories and locator can be defined at the item or bill of material component level.
If they are not defined, the system uses the supply subinventory and locator specified by the WIP
Backflush Supply Subinventory and Locator Parameters when components are backflushed.
To ensure adequate supply for backflush transactions, you can replenish supply subinventories and
locators as required.
Revision Control
For component items under revision control, the system always defaults the revision based on the
item's current revision as of the date of the transaction.
Thanks & Regards,
S.Grace Paul Regan
Posted by S.Grace Paul Regan at 11:04 PM No comments:
You can manually change user-controlled statuses. For example, you can change a job's
status to Released to initiate the production cycle. Some user-controlled statuses are
automatically changed based on other events. For example, when you complete a job,
its status is changed to Complete.
Released The job is available for production and can be transacted
against. When a job is changed to this status, the date
released is automatically set to the current date and, if a
routing exists, the job quantity is moved to the Queue
intraoperation step of the first routing operation.
You can change jobs to this status as you define them.
Unreleased The job is not released for transaction activity. You can
update but cannot transact against it.
You can assign a status of Unreleased if there are no net
issue, move, resource, completion, or scrap charges
associated with the job and no purchase orders or purchase
requisitions linked to the job.
Complete The job is completed but accepting transactions and
charges. Jobs are automatically updated to this status when
the quantity completed into inventory equals the job
quantity.
You can manually assign this status only when you update
the job, not when you define it.
Complete-No Charges The job is complete and accepting no further activity. You
cannot update or transact against it, but you can change its
Prerequisites
r You must have at least one closed period for your organization. See: Period Close,
Oracle Cost Management User's Guide.
appears.
2. Query to find one or more discrete jobs. See: Finding Discrete Jobs, page 3-82.
The Purge Discrete Jobs Summary window appears with the results of your query
Oracle ASCP, better known as Oracle Advanced Supply Chain Planning corresponds to MRP2 in the
evolution of planning systems. MRP1 took care of unconstrained planning and mostly addressed the
BOM explosion and lead time offset requirements for simplistic planning. But since MRP1 did not
take care of in-house and out-sourced, vendors capacities the need for an advanced planning system
which can take care of such constraints was realized and Oracle enhanced its simple MRP solution to
come out with a more advanced constrained based planning solution. This let to the advent of Oracle
ASCP module.
Oracle ASCP comes as a separate module in Oracle Applications suite with separate licensing
requirements.
Let me start by dwelling onto some of the initial topics on ASCP configuration from system
perspective.
Typically there are two kinds of architectures supported to incorporate Oracle ASCP module with
your ERP system.
1. Centralized Architecture
2. Distributed Architecture
Centralized architecture essentially means that your transactional modules and planning module
be sitting on the same application instance and would be pointing to the same database for data
storage. This architecture is preferred where the transactional data volume is not very high. Since
planning engine can put significant amount of load on the hardware it is very important to assess
the overall data volume load at the inception of ASCP implementation itself. From IT costing
perspective centralized architecture is good because there are obvious cost savings that can be seen
as this requires only one application tier and one database tier. But then as mentioned earlier this
decision should be strictly governed by the current data volume and the kind of growth you are
expecting for your business in future.
Distributed architecture, as the name suggests points to having planning modules installed on a
different instance. Again the decision to go for this architecture has to be governed by the
transactional data volume. This architecture has the inherent benefit that you can always keep your
planning data separate and continue your planning functions even when your transactional system is
down to due maintenance or patching activities etc.
To start with I would keep this post till here only and would dig deeper in the future posts. To
highlight what could be coming your way in future I would put down some of the topics here:
Technical architecture of ASCP, Engine logic for optimization, mapping constraints in EBS, plan
output analysis etc