E1: 47: Why Does EDI Detail (F47012) Contain Successfully Processed Records Which Have Not Been Purged (Doc ID 2847196.1)

Last updated on SEPTEMBER 07, 2023

Applies to:

JD Edwards EnterpriseOne EDI - Version XE to 9.2 [Release XE to 9.2]
Information in this document applies to any platform.

Goal

Why are successfully processed records in EDI Purchase Order Detail - Inbound (F47012) not purged?

If the EDI Purchase Order Detail - Inbound (F47012) table is allowed to grow large with previously processed records that are no longer needed, it can result in slower performance when running EDI Inbound Purchase Order Edit/Create (R47011).

Solution

	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

Goal

Solution

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

E1: 47: Why Does EDI Detail (F47012) Contain Successfully Processed Records Which Have Not Been Purged (Doc ID 2847196.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!