When the invoice is copied, the status in the Invoice Status field in the Received Purchase Invoices (tfacp1500m000) session is set to Registered. The invoice cannot be copied again.

Note: If you have started this session using the browse arrow, you can only find and select a record.

Field Information

• Invoice-from Business Partner: The invoice-from business partner
• Document - The document number: The document number is a sequence number under which the invoice is temporarily recorded. When an invoice is registered officially, you must assign the invoice to a different number, in combination with a transaction type.
• Business Partner Invoice Number: The invoice-from business partner's invoice number is the invoice identification used in LN: This number is printed as the payment reference when the invoice is paid.
• Invoice Date: The date printed on the invoice. This date is used as a reference date for the term of credit allowed.
• Currency: The invoice currency
• Amount: The invoice amount

FINANCE: Copy Received Purchase Invoices (tfacp1210m000)

OPERATIONS: Production Order Parameters

TECHNOLOGY: Audit Configuration Management

Crossroads RMC has fine-tuned our Technical Help Desk Service to meet specific job requirements. Our service delivers product-level support and development assistance with significant cost savings compared to traditional models. Our Help Desk is a tailored service that provides a dedicated ERP LX/BPCS technical resource, ensuring our support precisely aligns with your needs for a more efficient and effective solution. 

Key Features:

• Flexible Hours: Tailored to fit your budget and requirements.
• Duration Options: Choose from 3, 6, 9, or 12-month agreements.
• Remote Accessibility: Primarily remote support with on-site options for comprehensive assistance.
• Expertise Spectrum: Includes RPG proficiency, robust documentation, design skills, IBM i system knowledge, job scheduling, SQL expertise, CL development, and more.
• Scope: Focuses on technical support and development, with application support available upon request.
   

What's NEXT together.
Schedule a brief consultation with Crossroads RMC to discuss your technical support and development needs. We’ll help define the right scope, duration, and expertise to align with your goals and budget.

Let’s design a Help Desk solution that fits your business.
Contact Crossroads RMC at 800.762.2077 to get started.

INSTALLBMR

• Installs BMR Explosions from *SAVF or *LIB
• Installs objects after backing up replaced objects
• Installs source after backing up replaced source
• Installs Webtop Metadata
• Installs /InforBMR subdirectories
• Writes all activity to log file and spooled file report
• Optionally runs DBUPDATE command

DBUPDATE

• Installs new or updates existing database tables, views, indexes, triggers, procedures, logical files.
• Installs source for above objects
• Sets authorities to replaced objects based on previous object settings
• Sets journalling on replaced objects based on previous object settings
• Installs Priming Data
• Installs SSAOVR updates
• Installs message file updates for core message files
• Installs message file updates for NLV message files if included in explosion

This enhancement reduces the time required to install BMR Explosions. There still may be manual steps required after the processing completes, but the overall time required is dramatically reduced.

Access to Order Entry/Maintenance has traditionally been controlled by using LX Program Security to grant or remove authority to ORD700. LX Company Security and LX Warehouse Security further control which transactions a user is allowed to create or maintain. A separate 8.4.2 enhancement allows security managers to control which types of transactions a user is allowed to create or maintain, through LX Order Type Security and LX Order Class Security. Building on these LX transaction security features, the Order Entry Action Code/Function Key Security enhancement allows security managers to further control what actions a user can take regarding an authorized transaction.

Security managers can now control the actions each user is allowed to be restricted from in the Order Entry job stream. The benefit is easily illustrated by some examples:

• Regular users can be allowed to create and revise customer orders but are restricted from deleting an order.
• Salespersons can be authorized to full authority with quotes and can be allowed to create customer orders but not to revise or delete them.
• Or, salespersons could be restricted from 1=Create in Order Directory, with the result that they could only create an order by copying a quote, if they are authorized to 3=Copy in Quote Directory.
• Only selected customer service users can be allowed to create RMAs, by controlling 1=Create in RMA Directory. A different group of customer service users who handle the actual returns can be authorized to create the return orders or credit memos from those RMAs, by controlling 3=Copy in RMA Directory.

This enhancement provides the ability for IDF Order Inquiry to release order holds via a host job.

LX IDF Order Inquiry displays numerous details about an order, order lines, special lines and related files. An Order Inquiry user can copy, modify or delete an order through WebTop calls to ORD700 Order Maintenance, if authorized. Among the many details Order Inquiry also lists the Hold Codes for customer hold, credit hold, user hold, margin hold, and credit card hold. This enhancement provides the capability to release holds through a host job function that executes ORD680B, Order Hold Mass Release.   Batch Hold Release host job has been added to IDF Order Inquiry. The Order Inquiry user must be authorized to ORD680 in LX program security, SYS600.

ORD680 has been modified to accept parameters for multiple executions by host job. The user can release holds for a single order, a range of orders, or for multiple individually selected orders.

The following hold releases can be requested:

• Credit hold – orders on credit hold by the system (01) or by a user (02) are released from credit hold.
• Customer hold – orders on customer hold are released.
• User hold – orders on user hold are released.
• Margin hold – ORD680 re-evaluates orders or order lines that are on margin hold.