PJC G/L Integration Screen

Overview

Use the PJC G/L Integration screen to specify how Project and Job Costing interacts with General Ledger.

When you run the revenue recognition functions or post equipment, timecard, adjustments, cost, or reopen projects transactions, Project and Job Costing creates entries for your general ledger.

If you use Sage 300 General Ledger, Project and Job Costing creates batches of transactions in General Ledger, where you can edit and post them. If you use another general ledger system, or if your Sage 300 General Ledger system is at another location, the program creates batches that you can import or enter manually in your general ledger.

You use the G/L Integration screen, available in the PJC Setup folder, to select options to:

  • Produce general ledger transactions in the form and at the time that best suits your requirements.
  • Assign a wide range of job related information to the entry description, detail reference, detail description, and detail comment used in general ledger transactions.

Note: You cannot save most changes to the G/L Integration screen if any other Project and Job Costing screens are open.

Types of general ledger batches

Project and Job Costing creates separate general ledger batches for the following types of transactions:

  • Adjustments
  • Costs
  • Equipment Usage
  • Reopen Projects
  • Revenue Recognition
  • Timecards

Reporting general ledger data

You can print the G/L Transactions report, a listing of the general ledger transactions created by Project and Job Costing, whether or not you post batches in General Ledger.

Integration Tab

The Integration tab of the PJC G/L Integration screen lets you:

  • Specify how and when to create general ledger batches. More...

    You can create general ledger transactions automatically each time you run the revenue recognition functions or post equipment, timecard, adjustment, cost, or reopen projects transactions, or you can use the Create G/L Batch screen to create general ledger transactions when you need them.

    • To create general ledger transactions automatically, choose During Posting for the Create G/L Transactions option.
    • To create general ledger transactions only when you are ready, select On Request Using Create G/L Batch icon. Note that you should create general ledger transactions before you perform year-end processing in other Sage 300 ledgers.
  • Whether to add new transactions to an existing G/L batch or create a separate G/L batch. If you use Sage 300 General Ledger at the same location as Project and Job Costing, you can also choose to post new batches automatically.
  • Whether to create detailed general ledger transactions, or to consolidate them during posting. Note that any change to your selections for the Consolidate G/L Batch option applies only to transactions posted after the change, and has no effect on transactions already in a general ledger batch.
  • Specify the source code to use with each type of transaction in general ledger. (You cannot change the source code for Project and Job Costing.)
  • Look up the posting sequence number to be assigned the next time you post adjustment, cost, equipment usage, reopen projects, revenue recognition, and timecard transactions.

Before changing the Create G/L Transaction option to create transactions during posting (if it was set to create transactions using the Create G/L Batch icon), print an up-to-date copy of the G/L Transactions report, then create any outstanding transactions.

Transactions Tab

Use the Transactions tab on the G/L Integration screen to specify the type of information to use in the transaction description, detail reference, detail description, and detail comment fields for general ledger transactions.

This information also appears on Project and Job Costing posting journals and on General Ledger’s Journal Entry screen and reports.

Note: Any change to the data to include in the G/L Entry Description, G/L Detail Reference, G/L Detail Description, and G/L Detail Comment fields applies only to transactions posted after the change, and has no effect on transactions already in a general ledger batch.

You can assign one or more pieces of information (segments) to each field, provided that the combined length of the segments and separators does not exceed 60 characters. Fields exceeding this limit will be truncated when you post general ledger transactions.

The segments you can select depend on the type of transaction to which you are assigning information and whether the information is for the transaction header or the details. This ensures that the information passed to General Ledger is relevant for each type of transaction. For example, you can assign the ship-to information from invoice details to any of the General Ledger fields.

When you create general ledger transactions, if no data exists in the source transaction field, the field will be blank in the general ledger transaction. For example, if you assigned the original transaction description to the G/L Entry Description field, but there is no description for a particular entry, the field will be blank in the G/L transaction.