1. Archiving tipcs300

• Using Session tipcs2260m000:
  • When archiving PCS projects, selecting the "Archive Financial data" option ensures that:
    • Records in tipcs300 are archived to the archiving company.
    • Records are deleted from the original company.
  • If records remain in tipcs300:
    • They may belong to projects that have not been archived.
    • The project may have been archived without selecting "Archive Financial data."
  • Verify there are no errors during the archiving process.
• Using Session tipcs3500m001:
  • The session "Delete Financial Transactions by Project" can delete records from tipcs300.
  • Note: This session is not for archiving; it removes records without copying them to the archiving company.

2. Archiving ticst300

• Using Session ticst0250m000:
  • The session "Archive Production Orders" allows:
    • Archiving and deleting records from the original company.
    • Only deleting records from the original company.
  • When executed:
    • Records in ticst300 associated with archived orders are removed.
    • Remaining records belong to unarchived orders.

Statistical Inventory Control (SIC) is an inventory-controlled order system designed to maintain stock levels based on predefined thresholds, rather than being demand-driven like EP (Enterprise Planning). Since SIC relies on inventory levels, it may lead to higher stock levels. To minimize financial risks, SIC is best suited for:

• Low-cost items.
• Items with predictable demand or short lead times.

Applications of SIC

• Low-Cost Items: Particularly effective for inexpensive goods.
• Predictable Demand or Short Lead Time: Suitable when demand patterns are stable or lead times are minimal.
• Warehouse-Specific Planning: Useful for planning by warehouse rather than across the supply chain.
• Trading Industries: Commonly employed in sectors like supermarkets.
• Immediate Demands: Effective for items required immediately by customers.
• Ease of Use: Simple to implement and manage.

Limitations of SIC

Transitioning away from customizations can indeed pose challenges, but it's not insurmountable with the right approach. Here’s a look at the real issues and solutions that can pave the way for a streamlined, up-to-date ERP.

Common Challenges:

1. Dependency on Custom Processes
   Custom processes become ingrained, and removing them disrupts established workflows. However, business processes often evolve over time, as do best practices incorporated into modern ERP systems.

2. Cost and Time Constraints
   Testing, retraining, and hiring consultants for an upgrade are valid concerns. Yet, consider the efficiency gains and reduced maintenance costs over time by utilizing standard ERP features.

3. User Resistance
   Change management is critical, as employees can be skeptical of losing tools they’re familiar with. Effective communication about the benefits of standardized, future-ready tools can help ease the transition.

The Reality Check: Has Your Organization Changed?

Evaluate how much your business needs have shifted, how user expectations have evolved, and if any workarounds or interim solutions are now adding unnecessary complexity. Many companies discover that industry-standard ERP features can replace outdated customizations.

Did You Know?

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

• Bank Statement Workbench (tfcmg5610m100)
• Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

AI: Transforming Manufacturing—From Production to Profitability

As AI reshapes industries, manufacturers are asking critical questions: How will customers discover and purchase products in an AI-driven world? And how can companies keep pace with these advancements?

At Crossroads RMC, we address these challenges with our AI Readiness Assessment (AIRA). An AIRA creates a clear, actionable digital roadmap, significantly boosting efficiency, accuracy, and strategic capabilities. This assessment ensures a smooth, swift AI transition.

Our AI Readiness Assessments target key areas:

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.