Use this session to define simulated purchase prices for purchased items per site.

Field Information:

• Cost Calculation Code - price calculation code
• Item

The raw materials, subassemblies, finished products, and tools that can be purchased, stored, manufactured, and sold.

An item can also represent a set of items handled as one kit, or which exist in multiple product variants.

You can also define nonphysical items, which are not retained in inventory but can be used to post costs or to invoice services to customers. The examples of nonphysical items:

• Cost items (for example, electricity)
• Service items
• Subcontracting services
• List items (menus/options)
   
• ​Site - The site for which the purchase price is simulated.
• Purchase Currency - The currency of the simulated purchase price.
• Simulated Price - Purchase price

The simulated purchase price and currency are recorded twice.

• Simulated Price Multi Currency - The purchase price in multiple currencies.

The simulated purchase price and currency are recorded twice. The amount in this field is related to the price of the supplier.

• Unit - Purchase price unit
• Cost Component - The cost component that must be of the type Material Costs.

Note: The cost component specified in this field does not become part of the standard cost detail structure if it is part of the cost component scheme of the selected item. If calculations are performed with a calculation code not used for actualization (simulations only), the simulated purchase price is mapped to the cost component defined in the records for this session.

TECHNOLOGY & FINANCE: Archiving Finalized Transactions

To support correct archiving in a multicompany structure, the following rules apply:

• Each company must have its own archive company. Companies cannot share an archive company.
• The structure of archive companies must be an exact copy of the live environment.
• A company must keep the same archive company until the end of its lifetime. Once data has been archived, you cannot change the archive company.

If extra archiving capacity is required, it is recommended that you set up...

TECHNOLOGY & FINANCE: Archiving Finalized Transactions

OPERATIONS: Simulated Purchase Prices (ticpr1170m000)

You can maintain all the master data, such as items, business partners, central purchase contracts, general ledger and related data in one company and share this data with the other companies. This master data company can be one of the operational companies, but you can also assign a separate company only to be used for the master data.

The advantages of having a separate master data company are:

• Clarity: Having a single company as master data company is clear for all users.
• Authorization: In general, only a few people in an enterprise can maintain the master data and, particularly for this maintenance, the authorization is important. If one dedicated master data company exists, you can use the company authorization to maintain this authorization very easily.

After selecting the Manufacturing check box and clicking Generate in the Generate Master Data (tccom0231m000) session, LN generates Manufacturing item data by site in the Items - Production by Site (tiipd0151m000) session.

The data is retrieved from:

• The Items (tcibd0501m000) session
• The Item - Production (tiipd0101m000) session
• The Item - Production Defaults (tiipd0102m000) session, if default data have been specified.

• The value in the Site field is retrieved from the warehouse or the work center listed in these sessions:

  • Bill of Material (tibom1110m000)
  • Generic Bill of Material (tipcf3110m000)
  • Production Orders (tisfc0501m000)
  • Production Schedules (tirpt4101m000)
  • Production Schedule Lines (tirpt4102m000)
  • Routing Operations (tirou1102m000). Sites are not retrieved from subcontracting work centers.

In a multilogistic/single-finance company structure, you can manage the manufacturing and distribution processes in a number of separate companies and perform the financial accounting in one company.

You must create one or more enterprise units in each logistic company and link all the enterprise units to the financial company.

For example, you can use a multilogistic/single-finance structure for an organization that consists of a number of separate production plants in one country that use their own BOM and production process but that form one legal entity. The reason for this is because BOMs, and the item cost prices based on them, are specific for each logistic company.

FINANCE: Multilogistic/Single Finance

OPERATIONS: Generating Manufacturing Item Data by Site

TECHNOLOGY: Table Sharing with a Multi-Company Setup - Using a Master Data Company

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

• It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

• For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

• The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.