My Oracle Support Banner

E1: 42: Case Study: How to Populate Sales Order Detail Tag File (F49211) Based on Sales Order Detail File (F4211) in World Software to EnterpriseOne Data Migration (Doc ID 2227673.1)

Last updated on SEPTEMBER 08, 2020

Applies to:

JD Edwards EnterpriseOne Sales Order Management - Version 9.1 and later
Information in this document applies to any platform.

Purpose

This document is a guide to populate F49211 (Sales Order Detail File - Tag File) based on F4211 (Sales Order Detail File) when open sales order data are converted from World Software. This is a necessary routine because F49211 is used as optional in World Software whereas same table is required in EnterpriseOne. 

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 Difference Between World Software and EnterpriseOne Software
 Example of Data Migration 
 Error in Sales Order Entry (P42101) When F49211 Missing
 Workaround to Overcome Record Invalid Error
 Why the Error is Specific to P42101 and not P4210
 When F49211 Records Are Created in EnterpriseOne
 How to Implement F49211 Based on Migrated Data
References


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