Posting Control - Supply Chain and Manufacturing

[About Posting Control - General] [About Posting Types and System Events - Supply Chain and Manufacturing] [About Control Types per Posting Type - Supply Chain and Manufacturing]

Basic financial data and sets of rules for IFS Applications are managed in the IFS/Accounting Rules component. This module includes code parts, posting control, and functions for creating a code string, such as code string completion. The common IFS Applications information in the IFS/Accounting Rules module allows unified inspection and automatic functions throughout IFS Applications.

Creating the Code String

Financial monitoring occurs in connection with certain events in Supply Chain and Manufacturing:

• Inventory movements
• Changes in value
• Refinement
• Costing differences
• Customer invoices
• Supplier invoices

As a rule, a financial event in the system usually creates one debit and one credit posting. Each financial event in the system has an event name; for each event name, in manufacturing and supply chain there are predefined posting types to be used for debit and credit posts. See the posting types section for more information about posting types. You can also see the control types that you can use in the control types per posting type section.

When the system creates postings for a financial event, it uses the rules in the IFS/Accounting Rules module, in the order:

1. Posting control (Accounting Rules)
2. Preposting (Manufacturing/Supply Chain)
3. Code string completion (Accounting Rules)
4. Preposting (Manufacturing/Supply Chain)

The Financial Events and their bookings section lists the financial events that can occur in manufacturing and supply chain, and what posting types will be posted.

Posting Control

The IFS/Accounting Rules module contains a set of rules called posting control, which helps you to control how your posting will look and what will affect it. The central concepts in posting control are posting types and control types.

Posting Types

The posting types that you link to the financial event are the terms for which you create posts. Posting types are registered in IFS/Accounting Rules. Here, you specify how you want the code string for the posting type to be controlled.

You can register posting control for up to 10 code parts for all posting types. The following is a table of the posting types, i.e., credit and debit posts, that are installed with IFS Manufacturing and IFS Supply Chain, depending on which components you have installed.

Control Types

For each posting type, there are several possible control types. These are codes and system data that can be traced to the object of the post, for example, parts or customers. In posting control in the IFS/Accounting Rules module, specify the control type to control each posting type and the controlling data that corresponds to each code part value.

The control type decides which value the code string part is going to receive with each transaction. The control type is the term you use to vary posts. Control types are often terms linked to the transaction to be posted. For example, to control posting of inventory issues, you can use catalog group or inventory type. Control types are predefined for each posting type and product. Specify the control type for each posting type.

When you process control types and control type values, there are two ways of using default values. You can either use a default code part value or a fixed default value. If posting is always to be done on the same code part, enter a fixed value as the control type, and a default value that will always be used as the code part value. If you use a default code part value, the value is only used if you do not enter the control data value. You can use default values for all posting types in manufacturing and supply chain.

Posting control and other settings in the IFS/Accounting Rules module control how an event is posted. There are two different ways of handling preposting in IFS Applications: mandatory preposting and preposting.

• In mandatory preposting, a code part value must be manually entered. Mandatory pre-posting can be used for purchase requisitions, purchase order rows, customer order headers, customer order rows, manual issue from inventory, and manual receipt into inventory. Mandatory preposting can be defined as mandatory for several code parts within the same function. The code part values are used later when creating the order's final postings. For example, if a customer order header is defined with mandatory preposting for code parts B, C, and G, you must manually enter valid code part values for these code parts when entering a customer order.  Mandatory preposting rules are set up in Posting Control/Accounting Rules.
• In preposting, a code part value can be manually entered but is not required. Preposting can be used for purchase requisitions, purchase order headers, purchase order rows, customer order headers, and customer order rows. These values are validated against the code parts in IFS/Accounting Rules. The code part value is used later, e.g., in the order header and as the order line default, which can be changed or deleted per order line. A value entered on an order line is not automatically transferred to the header.

If no pre posting rules are defined, the default posting type is used for the functions, i.e., VAT free sales for customer order rows will be posted according to the M30 (VAT Free Sales) posting type.

Code String Completion

Code string completion is used to add more parts to the code string based on the code part value. You can specify code string completion for all code parts. The code string will be supplemented with the values you enter for the other code parts linked to the code part value. For example, a certain project is connected to a certain cost center through the code string completion function.

For each posting type and code part, you must specify if code string completion should override the value that posting control has assigned the code part.

Validating the Code String

When a code string is created according to the rules above, it must be checked for information, such as validity interval. The code string is validated in the following order:

1. Validity on the code part level (IFS/Accounting Rules)
2. Code part requirements (IFS/Accounting Rules)
3. Combination control (IFS/Accounting Rules)

Validity on the Code Part Level

In the basic data windows in IFS/Accounting Rules, specify the validity interval of each code part.

Code Part Requirements

Code part requirements indicate how other code parts in the code string may be used with an account. The requirement can be Can, Mandatory or Blocked. You enter code part requirements per account in IFS/Accounting Rules; they are default depending on the account type you specify when you enter accounts.

Combination Control

The rules for combination control are found in IFS/Accounting Rules. Combination controls define the combinations of code parts that are allowed or blocked per user group. It is possible for a given combination of code parts to be legal and illegal at the same time. The illegal combination is always dominant.

Error Handling

Errors may occur when posting and checking validations are made for a transaction. For example, a control type value may be missing, or the different sets of rules may clash. If an error occurs, the posting process stops and the result so far is stored. The superior posting record is also marked with the error. However, the transaction itself is not put on hold.

After this, you can check the incorrect postings in the Distribution and Manufacturing Postings Analysis window. Here, the Status Code column shows if the posting is incorrect or simply needs to be supplemented. The Error Description column shows what needs to be done. You can trace the inventory transaction, invoice, and operation to see what went wrong by using the right mouse button menu options.

Usually, the errors can be found in the rules for posting control, code string completion, code part requirements, or combination control, so this is where you must make changes. You cannot change the code string in the error form; you must go to the IFS/Accounting Rules module.

When you have corrected the rules, you can rerun the incorrect posting in the Rerun Erroneous Distribution and Manufacturing Postings window.