You are here
Home > Sales Order Management 9.2 > Performing End-of-Day Sales Update > Running the Sales Update Program

Running the Sales Update Program

Running the Sales Update Program

Concept

To maintain the most accurate sales information, you can update the records daily in the JD Edwards EnterpriseOne Sales Order Management system. The system updates the records in the JD Edwards EnterpriseOne Sales Order Management system and the records in the other systems with which it interacts, such as the JD Edwards EnterpriseOne Accounts Receivable and JD Edwards EnterpriseOne Inventory Management systems. After you run the Sales Update program (R42800), you can review and post sales transactions and review sales reports.

 

When you run the R42800 program, the system generates:

• Information about customer sales.

• Accounts receivable (AR) and general ledger (GL) entries.

• Sales for different categories, such as stock sales and freight, cost of goods sold (COGS), and profit percentages.

• Errors that result from running the program.

 

Because of the number of transactions that the system creates during the sales update process, run the R42800 program in proof mode first to detect and correct any errors before you run it in final mode. Oracle recommends that you run the R42800 program when no one is accessing the system. The system does not lock records. Therefore, if someone accesses a sales order record during the sales update process, the record might not be processed correctly.

 

Prerequisites

Before you begin this task, verify that:

• A status code for sales update is set up in the order activity rules.

• The next status on your sales orders is set to sales update.

Procedure

In this task, you will select a version of the Sales Update program, run the program in proof mode, review the output, and then run the program in final mode.

Step Action
Navigate to the Update Customer Sales program (R42800) on the End of Day Processing menu (G4213).

Click the End of Day Processing link.

Click the Update Customer Sales link.

Use the Available Versions form to select a version of the batch program. In your work environment, the system might display additional versions.

Step Action
Click the XJDE0002 option.

Click the Select button.

Use the Version Prompting form to access data selection and data sequencing for the batch program. If the Data Selection or Data Sequencing option is disabled, you cannot review or change the data selection or sequencing for the version.

Step Action
Click the Data Selection option.

Click the Submit button.

Use the Data Selection form to specify which records the system should retrieve from the database and include in the sales update process.

Step Action
Click the Comparison list.

Click the is equal to list item.

Click the Right Operand list.

Click the Literal list item.

Use the Select Literal Value form to specify the values that the system retrieves from the database. You can specify a single value, range of values, or list of values.
Click in the Literal Value field.

Enter the desired information into the Literal Value: field. Enter “377“.
Click the OK button.

Click the OK button.

Use the Processing Options form to set parameters for how a batch program processes data. Processing options are unique to a version. You should review processing options to ensure that the settings are correct.
Use the Specific Date as A/R Invoice Date processing option to specify a specific date for accounts receivable.

If you enter a specific date, the system ignores the Select Date Value as A/R Invoice Date processing option.

Use the Select Date Value as A/R Invoice Date processing option to specify the order processing date. You can specify the sales invoice date, ship date, or execute date for the AR invoice date.
Use the Specific Date as G/L Date processing option to specify a specific GL date.

If you enter a specific date, the date in the Specific Date as G/L Date processing option is ignored.

Use the Select Date Value as G/L Date processing option to specify the order processing date. You can specify the sales invoice date, ship date, or execute date for the GL date.
Use the Override Next Status Code processing option to specify the next step in the order process. You must specify a value from user-defined code (UDC) 40/AT that is set up in the order activity rules based on the order type and the line type that you are using.

If you are running the R42800 program in final mode, you should update status codes to 999 to ensure that the system does not retrieve and process orders that were previously updated.

Step Action
Click the Select Tab list.

Click the 2-Update list item.

Use the Proof or Final Mode processing option to specify whether the system runs in proof or final mode. You must use the version that is specific to the company’s update process, and you must indicate by version whether the system uses proof or final mode.

When you run the program in proof mode, the system does not update status codes or tables. You can print and review journal entries, review and correct errors, and, depending on processing options, review the sales journal.

Click the Select Tab list.

Click the 4-Print list item.

Use the Print Sales Journal before Update processing option to specify whether the system prints a sales journal before updating journal entries.

The sales journal contains only summary information. The report includes total invoice amounts, COGS, and profit amounts and percentages. This report is helpful if you want to review how sales revenues are distributed.

Click in the Sales Journal Version (R42810) field.

Use the Sales Journal Version processing option to specify the version of the Sales Journal program (R42810) the system uses to create the sales journal.

Make sure that you have set the processing options in the version on the R42810 program so that the system does not update the status codes of the sales orders.

Enter the desired information into the Sales Journal Version (R42810) field. Enter “XJDE0002“.

Click the Select Tab list.

Click the 11-Performance list item.

Use the Suppress Warning Messages processing option to specify whether the system writes warning messages to the Employee Work Center when you run the R42800 program.

You can improve the performance of the system when you select no to write warning messages.

Click the OK button.

Use the Printer Selection form to identify printer information for the report. In your work environment, the printer settings will be different.

Step Action
Click the OK button.

Step Action
Click the Form button.

Click the Submitted Jobs menu.

Use the Submitted Job Search form to locate and review the output results of a batch program. In your work environment, the system might display additional versions.

 

Step Action
Click the View Output button.

Step Action
Click the Open button.

Access the report output and review the data for accuracy.
The system does not assign a batch number or create any records in the database. The proof mode enables you to review the records before the system creates the records in the database.

Step Action
Click the Select button to run the program again in final mode.

Step Action
Click the Data Selection option.

Click the Submit button.

Verify the data selection is the same as the proof mode.

Step Action
Click the OK button.

Step Action
Click the Select Tab list.

Click the 2-Update list item.

Click in the Proof or Final Mode field.

Use the Proof or Final Mode processing option to specify whether the system creates records in the database.

When you run the R42800 program in final mode, the system updates status codes and tables and performs edits, such as checking for duplicate records against the GL, AR, and AP functional servers.

Enter the desired information into the Proof or Final Mode field. Enter “1“.

Use the Bypass processing options to specify whether the system updates the specified tables.

You bypass the table updates based on your business processes.

Use the Purge processing options to specify whether the system clears the records from the specified tables.

You purge the table records based on your business processes.

Click the Vertical scrollbar.
Use the Subledger processing option to specify whether the system creates subledger entries that are specific to the organization.
Use the A/R Next Number Index processing option to specify the next number that the system uses to assign an invoice (AR) number. If you leave this processing option blank, the system uses bucket 01 from system 03B.

The system uses this processing option if you have not previously assigned AR invoice numbers.

Use the Document Type for Invoices processing option to specify the document type that the system uses to assign to an invoice (AR) number.

The system uses this processing option if you did not assigned AR invoice numbers previously.

Click the Select Tab list.

Click the 3-Versions list item.

Use the processing options on the Versions tab to specify the versions that the system uses to create entries in AR and GL tables.

If you leave a processing option blank, the system uses the ZJDE0002 version for AR and the ZJDE0001 version for the GL.

Click the Select Tab list.

Click the 5-Summarization list item.

Use the processing options on the Summarization tab to specify whether the system writes AR, GL, COGS, and inventory entries in summary or detail.
Click the Select Tab list.

Click the 6-Cost Update list item.

Use the processing options on the Cost Update tab to specify whether the system updates costs prior to the sales update process, and the version of Sales Order Batch Price/Cost Update program (R42950).
Click the OK button.

Step Action
Click the OK button.

Step Action
Click the Form button.

Click the Submitted Jobs menu.

Step Action
Click the View Output button.

Step Action
Click the Open button.

When you run the program in final mode, the system assigns a batch number and creates the records in the database.
The system also displays the total for all invoices on the report.

Step Action
Click the Close button.

You have successfully run the Sales Update program in proof mode, reviewed the output, and then run the program in final mode for a specific sales order.

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