E1: 42: Transfer Orders (ST/OT) FAQ (Doc ID 1586709.1)

Last updated on APRIL 05, 2022

Applies to:

JD Edwards EnterpriseOne Sales Order Management - Version XE and later
JD Edwards EnterpriseOne Procurement and Subcontract Management - Version XE and later
JD Edwards EnterpriseOne Sales Order Processing - Version XE and later
JD Edwards EnterpriseOne Sales Order Entry - Version XE and later
JD Edwards EnterpriseOne CRM Sales Order Entry - Version XE and later
Information in this document applies to any platform.

Purpose

This document provides Answers to frequently asked questions about the set up and processing logic of Transfer Orders.

Questions and Answers

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Questions and Answers

Question 1: During the transfer order (ST/OT) process, is there a way of preventing a receipt from being entered against the OT before the ST has been ship confirmed?

Question 2: Is there a way to have the OT order automatically entered into receipt routing at shipment confirmation of ST order?

Multicurrency

Question 1: Where does the currency default from for the OT when entering in a multicurrency transfer order?

Order Integrity

Question 1: When a transfer order is created (ST/OT), is the related order populated at the detail level (F4211/F4311) or the header level (F4201/F4301)? Is it possible to have multiple OT purchase orders and one ST order (sales transfer)?

Question 2: Can quantity be cancelled at time of order entry for a transfer order?

Question 3: Is it possible to generate automatically the OT related with the ST using the standard sales order generation WebService calling a P4210 version configured for that propose?

Question 4: Why isn't the purchase order number populated on the header during Sales Transfer Order Entry?

Question 5: The List Price field (F4211.LPRC) is not being populated when entering a transfer order (ST/OT). Why isn't this field populated?

Transfers To A Branch Where Item Data Does Not Exist

Question 1: Is there a warning that is generated in EnterpriseOne when creating an Item Branch (F4102) record on the fly?

Non-Stock Transfers

Question 1: Can transfer orders be used with non-stock items?

Credit Orders

Question 1: What is the correct way to create a credit order for a Transfer Order (ST/OT)?

Question 2: How can we cancel the ST order after it has been run through Sales Update? The OT has not yet been received.

Intercompany Transfers

Question 1: When entering a sales transfer (ST/OT) that crosses company lines should the Inter Branch Sales (SO01) field to be updated on the Sales Detail (F4211) line?

Question 2: Is it possible to create one version of Sales Update (R42800) that will process both Intercompany (SI/SK/OK) orders AND Transfer (ST/OT) orders AND will automatically perform the Voucher Match (P4314) for both the OK Intercompany Purchase Order AND the OT Transfer Purchase Order?

Question 3: Is there a functionality to restrict users from doing interbranch transfer between certain branch plants?

Fulfillment Management

Question 1: Can Transfer Orders be used along with Fulfillment Management?

Customer PO Number

Question 1: Is it possible to enter a transfer order with the header information first, so the Customer PO Number (VR01) can be populated at order entry?

Question 2. When the Customer PO Number is changed on the Sales Transfer order (ST) detail line (F4211.VR01)after order creation, why doesn't the related Purchase Order (OT) field (F4311.VR01) also get updated?

Branch Sales Markup

Question 1: Why is error JAS_MSG317 Duplicate key not allowed displayed when attempting to add a new record in the P3403 Transfer Markup program using different effectivity dates?

Inventory Commitment Preference

Question 1: Can the Inventory Commitment Preference be used with Transfer Orders (ST/OT)?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.