You are here
Home > Sales Order Management 9.2 > Describing Reposting and Purging Information > Understanding the Process for Purging Sales Order Information

Understanding the Process for Purging Sales Order Information

Understanding the Process for Purging Sales Order Information

Concept

When data becomes obsolete or you need more disk space, you use purge programs to remove data from tables.

 

The JD Edwards EnterpriseOne Sales Order Management system provides programs that purge:

• Sales order text lines

• Sales order header records

• Processed batch sales orders

• Sales order detail lines

• Audit log transactions

Required Field(s)

Comments

Output – Result(s)

Comments

Additional Information

Procedure

In this topic, you will learn the purge process.

Step

Action

The steps to purge tables are:

1. Back up table.

2. Specify the table to purge.

3. Verify the table is not in use.

4. Run the purge program.

Step

Action

The purge programs have predefined criteria that the system checks before removing any data to avoid removing associated data that is located in other tables.

Multiple programs are available that enable you to purge data:

• Purge Sales Order Header (F4201) (R4201P)

• Purge Sales Order Detail (F4211) (R4211P)

• Close Text Lines (R42960)

• Purge Batch Receiver File (F4001Z) (R4001ZP)

• Purge Detail to History (R42996)

• Purge Sales Order History (F42119) (R42119P)

• Purge Sales Order Ledger (F42199) (R42199P)

• Purge Audit Log (R42420)

The R4201P program enables you to purge sales order header records from the Sales Order Header table (F4201). The system purges records from the F4201 table only if no open detail lines with a matching order type and order number combination exist in the Sales Order Detail table (F4211).

You set the processing option for the system to create records for the purged information in the Sales Order Header History table (F42019).

The R42960 program enables you to delete specific information from the Sales Order/Purchasing Text Detail Lines table (F4314). The R42960 program checks the F4211 table and the Purchase Order Detail File (F4311) table for open detail lines with matching order type and order number combinations. The system performs these tasks:

• If the system does not find matching records, the system deletes the closed text lines from the F4314 table.

• If the system finds matching records, the system deletes the closed text lines from the F4314 table only if the matching detail tables have a status of 999 (closed). Order lines whose status is not 999 cannot be purged.

You can use the R42960 program to change the status of text lines to 999 on orders with no open detail lines. Use this program only if you have not set up the processing options for the Sales Update program (R42800) to purge text lines for closed orders.

The R4001ZP program enables you to delete processed sales orders from the batch receiver tables. The system selects only records with Y in the Processed (Y/N) field of the batch receiver tables. The system does not remove records from the Batch Receiver File – Destination Quantity table (F4012Z). Use the general purge to remove data from the F4012Z table.

The R42996 program enables you to purge detail lines with a status of 999 from the F4211 table and move them to the Sales Order History table (F42119). You can run this program when you update customer sales. You must set the processing options for the R42800 program to purge the detail lines to history.

Use the R42420 program to delete records from the Audit Log Transaction table (F42420). The system checks the F4211 table to verify whether the order still exists. Next, provided that you have set the processing option for the R42420 program accordingly, the system checks the F42119 table to verify whether the order still exists. If the order does not exist in either table, then the system deletes the order’s corresponding records that are contained in the F42420 table.

In summary, the purge programs enable you to remove data in tables that is old and no longer required.

End of Procedure.

Ayman Refat
Over 20 years of experience in IT area, working as Oracle JD Edwards Developer with expertise in Windows Server, SQL Server and Microsoft Exchange Server, experience in Linux operating systems (Debian and Redhat), VMWare ESX / ESXi, Novell Netware, relational databases like Oracle 10/11g and backup solutions from Computer Associates. Large experience in high-end servers from Dell and HP, having the following certifications: Microsoft: MCP, MCSE, MCDBA, MCSA and MCT (2008 ~ 2013), Computer Associates: Technical Specialist – Storage and Backup Solutions,
http://www.AymanRefat.com

Leave a Reply

Top