Sage X3 - Release Notes

The application uses the Time entry API through the mobile automation framework with create, update, and delete.
The following web services need to be active: CWSPTECST, CWSPTECTC, and CWSPTEUOM.

The BETA installation package:

Includes the first version of the GraphQL API interface between Sage X3 and Web scheduling.
Is compatible with Sage X3 2022.R4 only.
Should not be installed on a live environment.
Should not be used with customers.

The purpose of the BETA distribution is for you to participate and share your feedback to further development of the package.

Complete the dedicated training.
Installations without customization:
- Uninstall your current sedApta version.
- Install sedApta version 2022 from scratch.
Installations with customization or with an advanced setup:
- Read the documentation prior to installation.
- Alternatively, contact your Business Support Partner for advice and guidance.

A new Crystal report production label report, ETIQONFLYPROD - Prod. labels on demand, is available as a Production documents report (RPT32).
Use a new Mobile Automation setup function (FUNADCSEARCH) (Setup > Stock) to define the production label report format for the Production label printing transaction to use.

Use the Manual allocation action available from the task products list. On return, the selected quantity is displayed in the Manual allocation field on the task product line.
Using the Deliveries function (GESSDH), select a nonbillable entry transaction, then use the Pick ticket selection to select the allocated stock.
The product cost price defined on the sales delivery document will then be valued in the Financial overview function for an Expense overview.
Note: Use a nonbillable sales deliveries entry transaction for products to be delivered to a customer, or to be consumed internally without an invoicing flow.

Grouping criteria Company, Site, and Role are available from the Group by field. Use these selection criteria to provide load analysis per role, per site, or per company.
To improve performance, the employee assignments details, as displayed on the detail screen, are only calculated on demand. Performance criteria are available from the Criteria selection screen.

Use the Refresh selection action to refresh project time or progress statuses.
Modify the Quantity, Amount, Billed percentage, and invoice dates on scheduled invoices, progress statuses, and time statuses.
Use the Milestone reached or the Validate checkbox to release invoicing flows. Select all and Deselect all checkboxes are available.
Open the sales document from the actions on the line.

SBONFAC
BONLIV
BONCDE
BONRET
BILLLAD
DCMDBT
DCMDRT
SBONFAC9
SBONFACP
SBONFACP2
SBONFAC2PI
SBONFACP9
SBONFACP92
SBONFAC92PI
BONLIV2
BONLIV2PI
BONLIV9
BONLIV92
BONLIV92PI
BONLIVTTC
BONLIVTTC2
BONLIVTTCPI
BONCDE2
BONCDE2B
BONCDE2PI
BONCDEOUV
BONCDEOUV2
BONRET2
BONRET2PI
BONRETLIV
BONAOF
BONAOF2
BONDLOUV
BONDLOUV2
BONTTC
BONTTC2
BONTTC2PI
RELBONAOF
RELBONAOF2
ARCCLIENT
ARCCLIENT2
ARCCLIENT2PI
ARCCLIENT9
ARCCLIENT92
ARCCLIENT92PI
ARCCLIOUV
ARCCLIOUV2
ARCTTC
ARCTTC2
ARCTTC2PI
BONPRELIV
BONPRELIV9
BONPRELIVP
BONPRELIVP9
DEVICLIENT
DEVICLIENT2
DEVICLIENT2PI
DEVICLIENT9
DEVICLIENT92
DEVICLIENT92PI
DEVTTC
DEVTTC2
DEVTTC2PI
QCANYS

For each approved product design revision a production BOM in design mode can be published, each with a different BOM code.
A production BOM in design mode can be used in a prototype work order to test the new product.
To test multiple revisions (specifications) of a product, a production BOM for each BOM code (alternative) can be tested in a prototype work order.
Successful, or approved product design revisions can be set to Production status.
The "best" approved design product revision and BOM can be released as an official product (in the Products table (ITMMASTER)) and as an active production BOM.
A design product must be "released" before it can be added to work orders and sales orders.

Limitation: Testing a design product in sales orders for selected customers in a "pilot" phase before it is "released" is for future development.

A new action - Split all lines - is available from the first line of the Time summary table in the Weekly timesheet function (PJMTEW). Use this action to separate all grouped time entry lines into separate, individual lines.
Two new actions - Currency rate and Remaining load update - have been added to the Time summary table in the Weekly timesheet function (PJMTEW). Both actions are available from the Actions icon in each timesheet quantity field. The Remaining load update action is also available from the Actions icon on each timesheet line. Use the Currency rate action to view and modify the currency rate for a specific timesheet quantity; the Remaining load update action to view and modify the planned and remaining load for a specific operation.
Analytical dimensions are available in the Time entry (PJMTE) detail screen.
A new field - Operating site - is available in the Selection block of the Time inquiry function (CONSPTE). Use this field to further filter employee time records.

Existing customers must make the following changes to display the customer Credit memos total:

Financial overview structure function (GESPJS): For Column sequence 062 (Free column 6), change the following:
- Set the heading for the Subcolumn 1 title field (SCOL1) to Credit memos.
- Set the data type for the Subcolumn 1 type field (COL1TYP) to Amount.
Financial overview queries function (GESPJQ): Select the Subcol1. calculation check box for Column sequence 053 (Sales outstanding orders) and Column sequence 054 (Sales BP invoices).

A Billing plan displays the list of sales orders linked to the project. Specific icons indicate if a sales order line has been billed, and how - using scheduled invoices, using a milestone billing process, or using a standard invoicing process based on sales deliveries.
Scheduled invoices, Deliverable/direct invoicing orders, and Invoices are detailed in respective subsections.
Additional header criteria can be combined with the Billing plan selection criteria to further filter the results in these sections.
The Scheduled invoices section can be filtered using project milestones.
Project tasks and budgets defined as milestones can be closed from the Scheduled invoices section using the Milestone reached check box. This action also makes the scheduled invoices billable.
To do this use the Functional authorization function (GESAFP) with option 1 to set up the required access control values for the function code PJMBIL.
The Estimated progress percentage of a milestone can be updated.

A budget code can now be selected and changed in the Budget update screen, enabling forecast quantities or amounts to be updated for a specific budget code. This functionality is available in the Project management function (GESPJM) via the Budget updates action from the Cost structure screen.
Additional selection criteria is available via a new Criteria action in the Project overview (PJMOVE) and Status update (PJMSTAUPD) functions. Memos can also now be managed.
The Criteria action is also available in the Project management function (GESPJM) via the Project overview action.
New selection criteria - Financial site, Employee site and Role – have been added to the Time validation function (PTEVAL).
Memos are managed in the Time inquiry (CONSPTE) and Time verification (CONSVTE) inquiry functions.
The Site field in the Time validation (PTEVAL), Time verification (CONSVTE), Time inquiry (CONSPTE) and Status update (PJMSTAUPD) functions is populated by default with the site defined in the Main site field on the employee user record (Project management section). If the employee's Main site field is blank, the site defined for the Common data module in the user Function profile is used.

Use the ESTPRGINIT – Estim. project progress init. parameter to define the SQL Query to be executed to initialize the project Estimated progress (%) field. The default query is PJMPRG. PJMPRG defines the default rules for calculating the progress of a project.
Use the ESTPRBINIT - Estim. budget progress init. parameter to define the SQL Query to be executed to initialize the budget Estimated progress (%) field. The default query is PJMPRGB. PJMPRGB defines the default rules for calculating the progress of a budget.
Use the ESTPRTINIT – Estimated task progress init. parameter to define the SQL Query to be executed to initialize the task Estimated progress (%) field. The default query is PJMPRGT. PJMPRGT defines the default rules for calculating the progress of a task.
Use the ESTPRGMET – Bud/proj progress estim method parameter to define whether the project and budget Estimated progress (%) fields are updated manually or automatically (by using the Refresh icon).
Use the ESTPRTMET – Task progress estim. method parameter to define whether the task Estimated progress (%) field is updated manually or automatically (by using the Refresh icon).

The Work centers function (GESMWS) has been updated as follows:

The figure in the Actual time field now reflects the total time taken to set the work center up plus the run time.
The Expected time and Actual time fields are adjusted where necessary when the Load resynchronization function (FUNSYNCO) is run.

A new check box - Availability date not applicable – has been added to the Products-sites function (GESITF). Use this check box to indicate if the product/component is to be included/excluded from the First Date of Material Availability (FDMA) calculations. The check box is clear, by default (the product is included in the FDMA calculations).

Two new fields - Status and Estimated progress (%) - have been added to the Predecessors table in the Task planning screen.
Task Category selection is opened automatically when a new task is added in the Task planning screen.
The majority of the fields associated with the Task planning and Cost structure hierarchies are editable.
Three new estimated budget progress fields - From/To budget progress and Budget progress range - have been added to the Project overview screen.
Two new sequence numbers used by Project management - TSK and BDG - have been added to the Common data module. Use the Assignment function (GESTCA) to use sequence numbers for new task codes and budget codes. You can use the Structures function (GESANM) to change the components that make up the structure of these sequence numbers to suit your organization.
Note: If manual numbers are not allowed, the Project copy function (PJMACTAFCP) ignores task code and budget code prefixes and suffixes.

A replacement or substitute component is checked for the existence of an active version (major or minor) and a current exception date.
The default validation flag for each selected BOM (parent product) is set to Yes.
Version managed parent products (BOMs) at status Available to use are included in the filtered results but flagged in red to indicate that they are excluded from the replacement process. The validation flag cannot be changed.
A component in a version managed BOM can be replaced or substituted only when the BOM is at status In development.
All messages for product versions have been replicated in both the Components replacement function and for the BOM component line revision.

A specific function can be linked to the Bank import settings.
This function is called after the bank statement file is uploaded and before the standard import process starts.
Within the specific function, you can modify the file and/or its content. Potential use cases:
- Splitting a file into several to separate multi-company bank statements.
- Filtering or grouping records, (i.e., a PayPal list of payments in multiple currencies, South Africa Standard Bank with multiple mixed headers and details...)
- Reformatting fields, removing characters etc.

Use the Rate multiplier field in the Time category (GESPJTC) function with appropriate time categories such as 'overtime'. The amount posted is then calculated using the following formula: Time spent x Employee labor rate x Rate multiplier
A new default journal entry template code – PTE (Project time entries) – is available in the Automatic journals (GESGAU) function. Use to define the structure of the time entry journals to be posted. The default contra accounts postings are to the 'Labor Expense account' (debit) and the 'Payroll clearing account' (credit). These accounts are obtained from the Accounting code assigned to the Project cost type on the time entry record in the Cost types (GESPJCC) function.
New Accounting code types – Project cost type and Project - have been added to the Accounting codes (GESCAC) function. The Project cost type code type is linked to the project cost types in the Cost types (GESPJCC) function; the Project code type is linked to the project in the Project management (GESPJM) function. They are used by the default Automatic journal to lookup the accounts to be used for the time entry journals.
Use a new GAUPTE - Time entry automatic journal parameter (TC chapter, PJM group) to define the automatic journal template to be used by the time entry posting process. The default journal template is PTE (Project time entries).
Use a new POSTPCCDEF - Source of posted labor account parameter (TC chapter, PJM group) to define which cost type provides the accounting codes. Set to Project cost type or Employee cost type. The default value is Project cost type.
Use a new POSTRATDEF - Source of posted labor rate parameter (TC chapter, PJM group) to define which labor rate is used. Set to Project labor rate or Employee labor rate. The default value is Employee labor rate.

Manage VAT declarations in the VAT box function (GESVTB).
Define the VAT form structure in the VAT form setup function (GESVEF). You can use the same form multiple times.
Extract values in the VAT returns function (GESVFE) and submit directly to the HMRC website.
Note: The DCLVATBRI preparatory report can only be run in simulation mode. The actual extraction and submission are managed in VAT returns.

Bank of Windhoek - format: e Bureau Version 3
FNB First National Bank - format: Statement export type: CSV

Stock entry movements follow the license plate number rules, (e.g., creation on the fly).
During the stock issue, you can use the license plate number to select stock lines.

The LPNG template is used to group license plate numbers with their related stock lines.
The LPNO template is used to assign license plate numbers to stock lines, to split license plate numbers, or to unlink license plate numbers, which means to remove the license plate number from the stock line.

To select products referenced for the supplier and the site. The selection window is available from the Product field, in the Purchase order and the Purchase open order functions.
To select suppliers referenced for the product and the site. The selection window is available from the Supplier field, in the Purchase request and the Buyer plan functions.

Some controls have been adjusted.
Non-receivable products are no longer submitted to the site referencing control.
In Purchase orders, in the Requirement selection screen, you can identify which purchase orders are blocked because of the referencing controls or due to the supplier blocking status.

If Activity code NCS-Non-conformance is set to "Active", additional fields are available in the Production tracking (GESMTL) Entry transaction, Operation/Manufacturing section – Non-conformance - process and Non-conformance - resource. Where the job role of users that have access to a specific entry transaction can raise a Non-conformance, select the types of Non-conformances a user can create.
New parameters for defining the default root cause are available at Site level (TC chapter, NCS group) – NCSROORES - Default resource root cause and NCSROOPRO - Default process root cause.
Key operational data (such as the employee processing the tracking, the time, quantity and work center) are automatically recorded if the original source of the non-conformance is the Production tracking resource or operation.
Multiple Operation tracking documents can be linked to "new" and "in progress" non-conformances.
The product code can be changed on "new" non-conformances to any product code associated with the work order - to a different released product code or to the routing product code if different to the released product code. The default product code is the first released product on a work order. The product code in the linked document line is also changed to the "new" NC product code.

If Activity code NCS-Non-conformance is set to "Active", additional fields are available in the Time tracking plan (GESMOL) Entry transaction, Parameters section – Non-conformance - process and Non-conformance - resource. Where the job role of users that have access to a specific entry transaction can raise a Non-conformance, select the types of Non-conformances a user is authorized to create.
The Time tracking plan (FUNBENCHO) function has been enhanced. A non-conformance can be created from an Operation tracking line where the Time Type = Work Order after the Tracking number has been generated, that is, after the tracking record has been saved.
- New check boxes are available – Non-conformance - process and Non-conformance - resource. An NC can be created for the operation resource (work center) or for the (operational) process, or for both.
- A new free-format Non-conformance description (70 characters) is available on the operation line. If left blank, it is populated with the default description Operation tracking: "+ Tracking-ID + OP-number" when the NC is created.
- A free-format detailed description of the probable cause can be recorded using a new operation line action - Non-conformance probable cause.
Only a basic (minimal details) NC can be raised against an operation line - the user parameter NCSDOCCRE-Non-conformance creation mode is ignored.
Key operational data (such as the employee processing the tracking, the time, quantity and work center) are automatically recorded from the tracking operation.

A new accounting code type Project has been added for use with the new Accounting code field.
The Estimated revenue at completion can be updated manually or automatically by refreshing the screen (F5).

Use the ESTREVINIT - Estimated revenue init. parameter to define the SQL Query to be executed to initialize the project revenue value. The default query is PJMREV. PJMREV calculates the estimated revenue at completion from the Sales order linked to the project.
Use the ESTREVMET - Revenue estimation method parameter to define whether the Estimated revenue at completion field is updated manually or calculated automatically.
Use the ESTPRGINIT - Estimated progress init. parameter to define the SQL Query to be executed to initialize the Estimated progress (%) field. The default query is PJMPRG. To calculate the estimated progress percentage PJMPRG compares the budget value to the total expenses.
Use the ESTPRGMET - Progress estimation method parameter to define whether the Estimated progress (%) field is updated manually or automatically (by refreshing the screen (F5)).

Only one snapshot can be selected for "Revenue recognition" per project.
Running a snapshot for a specific date overwrites previous extractions for the same date.
A revenue recognition method such as "Manual percent entry" or "Percentage of costs" must be defined on the project.

The PJMTIMENT - Time entry control phase parameter (TC chapter, PJM group) defines if a time entry "Control" phase for validated time entry lines is mandatory.
Available statuses are "Controlled", "Approved", "Rejected".
"Rejected" time entry lines are available in the Time entry (PJMTE) function; "Approved" time entry lines are not.

The sitemap has been renamed Navigation menu.
The Navigation menu no longer takes the entire screen width so you can see the open function behind it.
The top right cross has been removed.

You can move from one screen block to another (increasing/decreasing order)
You can move to the first/last field of a block.
You can trigger main actions such as create or save.
You can trigger the main links present on the fields.

JDK11 Zulu replaces the previous Java Runtime engine
Embedded Crystal engine 13.024
Microsoft Visual C++ redistributable for Visual Studio 2017

The following changes have been made to grid management:
- Direct access to the popup view is available from the top of the grid.
- On mobile devices, navigation in the popup view (and only for this view) remains in the same position when scrolling down.
- On mobile devices, the line size has been adapted for touch screens.
- The breadcrumb is no longer present on mobile (no change to desktop).
The fields are aligned horizontally in a page. The size reserved for the description is fixed and longer descriptions display as tool tips.
When stacked, the fields are left-aligned to enhance readability.
On mobile devices, the actions have been moved:
- The primary and secondary action buttons are at the bottom of the screen.
- The CRUD actions are at the top of the screen.
- The additional list of actions can be seen by clicking the Actions icon.
The attachment and comment icons display the number of attachments and/or comments if there are any.
On tablets, the layout is a combination of mobile and desktop. The navigation panel uses the mobile and layout and fields display as on a desktop. They are not stacked as on mobile phone.
The Cancel icon is an X in the right panel.
The Exit or Close page icon is a [--> in the right panel.

Five new field sizes
More consistent field sizes for existing fields
Improved alignment for fields and check boxes

The balance of the remittance is calculated and is then compared with the balance of the bank statement line.
If the signs or amounts of the balances are different, then an error message is displayed in interactive mode or in the log file when the file is imported.
The amounts in the "Detail of line #" grid are displayed in bank currency.

This report is available from the following locations:

Non-conformance (GESNCSH) function: Use the List action from the Print icon in the Side bar.
Reports (AIMP) function (Reports menu, submenu Reports): Use the NCSRECENT Report code.

States who closed an incident and when it was closed.
Contains a free-format narrative field that can be completed when the incident is closed. Use it to support the reason for closure.

The default supplier defined on the Product-site record can be assigned.
If the Product-site record has no default supplier defined, the default supplier on the Product record can be assigned.
If neither the Product-site record nor the Product record has a default supplier defined, the supplier is left blank. The supplier must be manually assigned from the BP supplier list. The supplier can be selected using the Actions icon.
Supplier assignment is controlled using the ITMBPS — Supplier referencing and ITMBPSFCY — Supplier-site referencing parameters (ACH chapter, REF group).

Where time spent on projects is less than or greater than the calculated capacity, the inquiry displays an alert on the line: red for less than and orange for more than.
Where time spent on projects is equal to the calculated capacity, the inquiry line is green.
Filters can be applied to display only lines with warnings or alerts.
Lines can be aggregated by days, weeks, or months using a Period to control filter.

Standard: Importing, matching, and generating payments take place within the full bank statement import workflow, including the Process bank transaction function (GESBSIMTC).
Reconciliation only: Importing takes place within the bank statement import workflow. Matching and generating payments take place in the Bank statement reconciliation function (RAPBAN). This flow allows you to import bank statements in MT940 or CAMT format into the Bank statement reconciliation function (RAPBAN).

Depreciation expense
Exceptional depreciation expense
Book vs Tax depreciation
Book vs Tax reversal of depreciation
Reversal of revaluation surplus
Impairment reversal transferred to Exceptional depreciation
Amortization fund decrease

Divider rate (RATDIV) for the transaction rate.
Multiplier rate (RATMLT) for the ledger rate.

Prepare periodic statistical declarations on nonresident payments and/or existing receivables or liabilities against nonresidents resulting from certain transactions.
Sales and purchases, net turn-over-values, from services delivered to or received from nonresidents
Sales and purchases, net turn-over-values, from transit trade
You must use dedicated general ledger accounts for the types of transactions to be submitted in the ZABIL statement.

Receivables/liabilities for services to/from nonresidents
Receivables/liabilities from financial transactions (credits, rent, real estate, etc.)
Receivables/liabilities resulting from transit trade
The data generated for the Z4 statement is not based on payments, but receivables or liabilities. You need to signal this fact to the Deutsche Bundesbank. See the documentation provided by the "Servicezentrum Außenwirtschaftsstatistik."
You must use dedicated general ledger accounts for the types of transactions to be submitted in the Z4 statement.

Payments to or from nonresidents
Statement of receivables or liabilities of nonresidents

Payment process
Products

For all payments made within the reporting period, the average time to pay in days
For all these same payments made within the reporting period, the percentage of payments
Paid within 30 days
Paid within 31 to 60 days
Paid after 61 days

Purchase requests
Purchase order
Buyer plan
Back to back order
Open orders
Delivery requests
Subcontract orders
And all processes that generate those purchase documents

MRP process, when creating purchase order and subcontract order quotes
Enterprise planning
Planning workbench, when amending the quotes and converting to firm orders
Grouping
Enterprise Planning and Planning Workbench updates:
- New selection screen on action menu to supplier field.
- On all intermediate screens: When transferring a quote to an order, the supplier becomes defaulted when previously the supplier could not be determined by MRP.
- Validation to supplier when creating the order.

Activate the REX activity code to use this functionality.
The REX number can be entered on the site or company record.
The REX number is printed on invoices and delivery reports if the company issuing the document is in the European Union and the delivery customer's country is in the Generalized System of Preferences (and vice versa).

Note that only "detail" lines can be linked if a non-conformance is for a specific product.
Selected details on linked documents can be amended – NC quantity, Lot, Serial numbers.
Linked production tracking documents can be restricted to a single work order using parameter NCSMULTIWO (TC chapter, NCS group) if a non-conformance was originally raised from Production tracking.

The default supplier defined on the Product-site record can be assigned.
If the Product-site record has no default supplier defined, the default supplier on the Product record can be assigned.
If neither the Product-site record nor the Product record has a default supplier defined, the supplier is left blank.
Supplier assignment is controlled using the ITMBPS-Supplier referencing and ITMBPSFCY-Supplier-site referencing parameters (ACH chapter, REF group).
When a suggestion is transferred to a real order in the Enterprise planning (FUNGBENCH), Planning workbench (FUNDBENCH), or Grouping (FUNMPICK) functions, the supplier must be manually assigned from the BP supplier list if the default supplier has not been determined. The supplier can be selected using the Actions icon.
Note that assignment of the default supplier is not available in the Multi-level planning (MULTIWOX) or Statistical reordering (FUNSTKB) functions.

Container management is activated using activity code MWC - Container management. The MWC activity code is linked to the MWM-Weigh station activity code.
Use Weighing container situation from the Weighing situation to view the weigh status by master container.
A By container selection is available with the RECONCIL - Reconciliation parameter (GPA chapter, WEI group). Use this value to reconcile weighings by master container.

The following queries provide detailed tracking on the operations to which the user is assigned.
PJMOPE20 - Progress rates by project
PJMOPE19 - Progress rates by task
PJMOPE01 - My assignments on projects
PJMOPE02 - My assignments on tasks
PJMOPE06 - My assignments on operations
The following queries provide global tracking of the projects to which the user is assigned.
PJMOPE09 - Planned vs. Launched
PJMOPE08 - My projects overview (Multi-level)
PJMOPE05 - My tasks overview (Multi-level)
PJMOPE03 - My projects progress
PJMOPE04 - My tasks progress

Task products can include a manual budgetary value (purchased products only).
Task products can include a stock based value method(s) for budgetary calculations based on the product profile relevant to stock valuation methods and the detailed breakdown structure (includes material, labor and machine costs).
The budget automation can integrate with existing budget lines, irrespective of the original source of the budget line. Products from a given budget automation run can be included or excluded.

The Financial situation link displays the budgets, commitments, actuals, forecasted cost price and budget margins.
The Revenue link displays the sales revenue and sales margin.

Associated MTP/MTF (product requirement) orders will be deleted but not the existing resources (Purchase orders, Work orders, Sales orders, etc.).
Stock allocations for the product will be deleted, thereby freeing up the stock for a sales delivery or a material consumption.
You can recreate the product requirement (MTP/MTF) by clearing the Manual WIP closure check box. The task status must not be Closed.

Sales site
Operating site
Currency
Rate type and date
Product requirement dates

The PJMTIMBUD parameter is set to Yes, by default. If set to No, the selection of task or operation becomes mandatory.
The PJMTIMBUD parameter can be defined at Site level.
The PJMTIMBUD parameter can be combined with general parameter PJMTIMTAS - Allow time entries on tasks.

The Entity/Use code field is available for all countries when Sage Sales Tax is active.
The Entity/Use code can then be entered for any shipping address when a sales document is being processed for a country that is tax exempt and Avalara does not capture and process taxes.

Accounting code line 15 of the WIP Automatic journal can locate the site account when tracking without a work order.
This journal change is integrated in the system folder.
Before copying manually from the system folder to the operating folder, start the automatic document comparison to identify the variances.

Standard cost & Revised standard cost - ITMCOSTPIT (ITCP)
Average unit cost - ITMMVTPIT (ITVP)
Lot average unit cost - STOLOTFCYPIT (SLFP)
FIFO cost & LIFO cost - STOCOSTPIT (STPP)
These tables are populated during the Stock accounting interface or WIP posting with the values based on information in the Stock journal (STOJOU). Fields PITVALFLG and PITVALFLG2 indicate the posting status.

Transactions dated earlier than the date of the Stock valuation method change cannot be entered.
If a transaction is dated earlier than the date of the Stock valuation method changes, the message "Transaction date cannot be prior to a valuation method change" displays.

When the valuation method is changed on the product-site record, the prior valuation method, along with the date and time the change was made, is written to the table.
These fields can store three prior valuation methods. The most recent change is always stored in the first historical field.
This information is not displayed in the Product-site maintenance (GESITF) function.

This inquiry uses an enhanced Stock valuation data model to display the product cost by fiscal year and period.
Selection criteria include a site, product, primary valuation method and lot.
Information displayed in the inquiry grid will vary based on the selected valuation method. For example, when selecting a FIFO valuation method, the receipt date will display for each cost layer; when selecting an Average lot cost method, the Lot for each cost layer will display.

The utility only recalculates the balances in the enhanced Stock valuation data model. It does not change information in the Stock journal table or update any journal entries.
The resync can be run in simulation mode to analyze the product-site costs.
A log of discrepancies is produced before committing the changes to the tables.

These reports use the point in time tables that are populated and updated during the General Ledger posting processes (stock, work in process, and subcontracting).
These reports are executed when the costing mode is Primary issue method or Secondary issue method and the accounting date option is selected.
Report features include the following:
- Ability to specify an end date for any valuation method
- Automatic inclusion of variance not absorbed
- Option for subtotal by version
- Selection filter and subtotal by accounting code

Applicable reports:

Components (REMPLCOMP) (Common data > BOMs > Replacement)
Components (SUPPRCOMP) (Common data > BOMs > Deletion)
Routing operations (FUNTDUPDR5) (Manufacturing > Serial modifications)
Replace work-centers (FUNTDUWST) (Manufacturing > Serial modifications)
Delete routings (SUPPGAMME) (Manufacturing > Serial modifications)
A message informs you that the version managed BOMs/routings included in the selection criteria will not be processed, and that these must be updated manually.
The versioned BOMs/routings that are excluded from the process are listed in the log file.

Major version
Minor version
Default Routing code (creates version)
The default Routing code is mandatory the first time a versioned routing is imported. Subsequent imports of the same routing will use the default routing code unless a different routing code is selected.

The import process initially creates a non-versioned routing as a new versioned-managed routing at status In development. When it has validated the coherence of the routing operations is correct it then sets the new versioned routing to status Available to use.
Versioned routings must be imported in the correct sequence.
Versioned routings that are older than today's date can be imported by typing D in the ROUTING table field *4 (Option).
A list of new and removed operations must be provided for each version in the import file.
Versioned routings can be exported. Note that all versions (major, major/minor) of a routing are exported, not just the current version.

A permitted user has their user parameter ECCWOCOM set to Yes. A user without permission to make critical changes to Work order components ECCWOCOM set to No. is blocked from making these changes.
Critical changes are defined as the following:
- Add an unexpected material
- Add an subassembly (phantom)
- Exclude/reactivate a component on a work order for a version-managed product
- Change the values on the following critical fields: Required qty., Operation number and Pick list code
Critical changes are allowed under the same conditions as changes on work orders for non-versioned products (for example, work order status combinations (Allocation, Scheduling and Status)).
The first time the user with permission clicks on a component line to make a change (to Add, Exclude, Reactivate or Change a critical field value) an information message will be displayed to warn that they are about to make critical changes on a work order for a versioned product. The message will not be displayed again whilst the user continues to make changes. After clicking Save the message will be displayed again if they make more changes to the component lines.
When a change is made (by any active user) to a work order header field that results in a BOM reload (for example, to the Start date ) and there are existing critical changes on the components, a message will be displayed to warn the user that any existing critical changes will be overwritten. The user can choose to continue with, or cancel the change.

A permitted user has their user parameter ECCWOOPE set to "Yes".
Critical changes are defined as the following:
- Add an unexpected operation;
- Exclude/reactivate an operation;
- Change the values on the following critical fields: Work center, Number of resources, Planned quantity, Setup time, Unit time, Run time, Labor work center, Subcontract product and Number of labor resources.

Critical changes to components on a work order for a versioned product are recorded in the Work Order Component Revision History table (MFGMATREV).
Critical changes to operations on a work order where both the product and the routing are versioned are recorded in the Work Order operations audit table (MFGOPEREV).
You can view the changes by selecting the Revision history action from the Actions icon on the component/operation line.

A Component sequence control check box is available on the Product-site parameters block (Manufacturing tab). Select this check box for the BOMs parent product to control the weighed components to restrict the weighing by the component line's sequence number.
Set the Site level parameter WEICOMSEQC - Weighing component seq ctrl (GPA chapter, WEI group) to Yes to automatically select the Component sequence control check box when creating new product-site records.

The user's Sage X3 login and password can be requested at the beginning or at the end of each weighing.
The user code is included in the weighing transaction.
The Weighing operator user code can be viewed in the Weighing situation (CONSMWO) history.

Project management (GESPJM): U - Project overview, 1 - Financial overview, 2 - Cost structure, 3 - Change status, 4 - Project copy, 5 - Task planning, 6 - Saleable products, ! - Financial snapshot comparison
Cost structure (PJMACTBUD): C - Create, M - Update, S - Delete, 2 - Change status, 5 - Budget automation, C - Sub levels, M - Budget update
Task planning (PJMACTTAS): C - Create, M - Update, S - Delete, 1 - Change status, 6 - Remaining load update, C - Sub levels, O - Operation Change status
Project snapshots (GESPJMOPSNP): 1 - Snapshot extraction
Financial snapshots (GESPJMSNP): 1 - Financial snapshot extraction

Code	Name	EU member	EU entry date	EU withdrawal date	Intrastat code	VAT radical
GB	United Kingdom	No	01/01/1973	31/12/2020	GB
XI	No. Ireland	Yes	01/01/1973		XI	XI
XU	United Kingdom (excl. No. Ireland)	No	01/01/1973	31/12/2020	GB

Release Notes

Compliance

Portugal (POR)

Working documents and payment declaration via web services

Finance

Austria (AUT)

VAT Framework for Austria

France (FRA)

Tax on vehicle changes for 2023

DAS2: 2023 updates

Germany (GER)

VAT Framework for Germany

Portugal (POR)

IES changes for 2023

Transportation notes (ATCUD)

Webservice for ATCUD communications updated

Spain (SPA)

Tax management updates 2023

Anti-fraud law compliance

For 190 form changes for 2023

BATUZ updates for 2023

Digital KIT

Updates to forms 303 and 390 for 2023

United States (USA)

1099 updates for 2022 reporting

Distribution

Licensing policy change: Project copy for operational PJM badge

Mobile Automation

Create LPNs on the fly when creating a misc. receipt document

Create LPNs on the fly when creating a purchase receipt document

Print purchase orders to receive

Receive orders linked to a shipment

Scan codes to enter product data in the Purchase receipt transaction

Scan codes with your mobile device

Select stock line in the Stock change transaction

Turn sound on or off

View product picture

Stock Valuation report include beginning balances and transfers

Manufacturing

Mobile automation

Work order production tracking production label printing

Project management

Mobile Automation

Time entry enhancements

Financial overview enhancement

GraphQL API

Distribution

Customer (Mutation)

Purchase invoice (Mutation)

Purchase invoice (Query)

Purchase order (Query)

Purchase receipt (Query)

Sales delivery (Query)

Sales invoice (Query)

Sales order (Query)

Sales return (Query)

Manufacturing

Team (Read)

Platform

Updates function improvement for large updates

Automated Test Platform

Parallel testing

Select an element in a picking list by using concatenation of text and (user) stored values

Generate Allure report results in PDF

Node.js upgraded to version 18

Timeout management improvement

Compliance

Finance

TRSSTRDAT parameter controls are not fully applied when document is modified.

Edit fields after monthly close

Belgium (BEL)

Incorrect VCS number for Suppliers (Belgium)

France (FRA)

2023 VAT changes

Germany (GER)

2023 VAT changes

Portugal (POR)

2022 inflation rates for asset reevaluation

CIUS-PT UBL2.1 format updated

Distribution