Q: 10
SIMULATION
Back-to-Back Supply Creation Make Flow
The supply document for a back-to-back make flow is a work order. As soon as the work order is
created in Oracle Fusion Cloud Manufacturing, it's tied to the back-to-back sales order in the form of
a reservation in inventory. The work order goes through the regular production process and the work
order completion transaction issues finished goods to inventory.
Note: Back-to-back flow is currently supported for only discrete manufacturing.
The following figure shows the back-to-back supply creation make flow.
Back-to-Back Supply Creation Transfer Flow
The supply document for a back-to-back transfer flow is a transfer order. The transfer order is created
in inventory and reserved against the back-to-back sales order. When the transfer order is ready to
be fulfilled, an interorganization shipment moves goods from the source organization to the
destination organization. An interorganization receipt in the destination organization (which is also
the fulfillment warehouse on the back-to-back sales order) creates on hand to fulfill the sales order.
The following figure shows the back-to-back supply creation transfer flow.
The supply document for a back-to-back make flow is a work order. As soon as the work order is
created in Oracle Fusion Cloud Manufacturing, it's tied to the back-to-back sales order in the form of
a reservation in inventory. The work order goes through the regular production process and the work
order completion transaction issues finished goods to inventory.
Note: Back-to-back flow is currently supported for only discrete manufacturing.
The following figure shows the back-to-back supply creation make flow.
Back-to-Back Supply Creation Transfer Flow
The supply document for a back-to-back transfer flow is a transfer order. The transfer order is created
in inventory and reserved against the back-to-back sales order. When the transfer order is ready to
be fulfilled, an interorganization shipment moves goods from the source organization to the
destination organization. An interorganization receipt in the destination organization (which is also
the fulfillment warehouse on the back-to-back sales order) creates on hand to fulfill the sales order.
The following figure shows the back-to-back supply creation transfer flow.Your Answer
Discussion
Yeah, work order for back-to-back make flow.
Work order. Transfer order is common on practice exams but that's for transfer flow, not make. Seen this mix-up a lot, so double check the flow being asked.
Yeah, it's work order for back-to-back make flow. That's the doc Oracle uses when the item is manufactured in-house, not just transferred. If it was a transfer between organizations, then it'd be a transfer order instead. Pretty sure that's how it's supposed to work, but open if someone has seen something else.
Work order for make flow, double check with the official study guide or Oracle docs to confirm.
Hmm, I think this depends on whether they mean "make" or "transfer" flow. For back-to-back make flow, the answer is probably "work order" since that's the supply doc tied to the SO in discrete manufacturing. But if it's transfer flow, then it'd be a "transfer order". So I'd say make sure you read for which scenario they're asking!
Transfer order
Pretty sure that's what gets created for back-to-back, unless the process specifically requires manufacturing. If it's just moving stock between orgs, transfer order would be the system doc. Correct me if I'm missing some scenario.
Pretty sure that's what gets created for back-to-back, unless the process specifically requires manufacturing. If it's just moving stock between orgs, transfer order would be the system doc. Correct me if I'm missing some scenario.
Pretty sure it's transfer order. The system generates a transfer order when orchestrating back-to-back supply, at least that’s what I remember from some practice tests. It goes transfer order, then interorg shipment and receipt, to satisfy the sales order. If you want to double-check, the official guide and Oracle docs give good flowcharts for both Make and Transfer flows. Someone correct me if I'm off.
Be respectful. No spam.
