Access ADM and WebDP with this link: http://alphdb05.eua.solvay.com/ADMPrd/

If it gives you this screen, just hit 'cancel'.

Master Data

Material table

Picaso materials are not package specific. They match the SAP concept of a Material group.

Materials - Planning > ADM - Advanced Data Management > image2022-10-17_17-33-58.png

The material filelds are to be populated as below:

Field	Mandatory/Optional	Rule	Comment
Material	Mandatory		Once created, cannot be changed. Picaso materials are not package specific. They match the SAP concept of a Material group.
Nome Code	Mandatory	Same as Material	Must equal Material
Manager	Mandatory		Whomever is in charge. Usually the GP or the PM.
Material Type	Mandatory	Material Type
Description	Mandatory	Free text	when possible, make it the same as Nome Code
Lot Site
Unit of Measure	Mandatory	as fit	all other tables refer to that one. Example: production rates in production standards. Once set, better not change it.
Search Code	Mandatory	Material Search Code	Not to be mistaken with the Inventory target search code.
Quality Test Lag	Optional		consider the effect of the Quality test lag on the grid and on the SAP Planned orders.
Bulk Density
Box Liner Code
Box Shroud Code
Cust Tier
Margin
Inv Cost	Mandatory	default with 40000	used by EP
Bag Size Code		always 0
Material Field 1
Material Field 2
Material Field 3
Material Field 4
Material Field 5
Material Field 6
Material Field 7
Material Field 8
Material Field 9
Material Group	Mandatory	as per SAP
H4	Mandatory	as per SAP	For it to work, you want to update the Product Family / Business Unit table. Once this table is updated, the fields will autopopulate. H4: SPP H4 mapping
Business Unit	Mandatory
Finance Material Type	Mandatory
Archetype	still used?
Material Field 15
Material Field 16
Material Field 17
Material Field 18	Optional	X if product is under allocation

Material types

Material types	Identifier	What for
Finished Goods	P	Finished goods
Additives	A	Raw Materials
Intermediates	I	Bulk, polymers
Package Materials	P	Package Materials
Resins	R	Resins
sfm	M	monomers (TFEM, Sulfones, VF2,...)
wide spec

Materials Search Codes

Search code	What for
900 or 999	Obsolete
1	Raw Materials
2	Bulk, polymers

Location Dependent Quality Test Lag

The material shows a global Quality test lag:

Materials - Planning > ADM - Advanced Data Management > image2022-10-17_10-11-39.png

What if the QC time is not the same in the two (or more) production plants that this product is manufactured?

The Location dependent Quality test lag let you deal with locations where the Quality test lag differs from the material default.

Materials - Planning > ADM - Advanced Data Management > image2022-10-17_10-13-20.png

Effect of the Quality Test Lag on:

the production schedule: none
the grid: it offsets the availability of the output product of a run
the SAP Planned order: it offsets the end date of the planned order corresponding to a run.

In order to avoid duplicating QC times when one is maintained in SAP, you want to use the Schedule Upload Lag Adjustment Table.

Keep in mind that the Picaso → SAP interface always uses these two factors. This is hardcoded in the interface.

Effect of the Quality Test Lag on the availability of the output product of a run:

Consider this run. Its attributes:

Product: PVDC PV910
Package: BB5
Line: SUSP PKG
Formula 80 (from possible formulas for that line, determined by Production Standard and Production Standard Effectivity)
Quantity 176 MT
Start Date: Dec 02 2022
End Date: Dec 04 2022 - 12:00 (determined by quantity and rate. Rate from Production Standard Effectivity)
Customer Order: SAP Planned Order number. This Run has already been interfaced with SAP.

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_12-8-18.png

The effect of the plot of a 2 days QC Lag:

despite the run starting Dec 02, it will start affecting (increasing) the projected inventory Dec 04

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_12-9-37.png

the run ends on Dec 04, but the projected inventory will continue to increase until Dec 06

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_12-12-36.png

Effect of the Quality Test Lag on the end date of the corresponding SAP Planned order:

Consider the dates of this run:

Start Date: Nov 07 2022 - 15:26
End Date: Nov 08 2022 - 12:04
Customer Order: 1079448688 (SAP Planned Order number).

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_13-36-2.png

And the dates of its corresponding SAP Planned Order:

Start Date: Nov 07 2022
End Date: Nov 15 2022

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_13-36-51.png

	Picaso Run	SAP Planned Order	Difference
Start Date	Nov 07 2022	Nov 07 2022	same
End Date	Nov 8 2022	Nov 15 2022	7 day

What is going on? This:

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_13-44-21.png

The Quality Test Lag adds to the SAP Planned order End Date:

	Picaso Run	SAP Planned Order	Difference
Start Date	Nov 07 2022	Nov 07 2022	same
End Date	Nov 8 2022	Nov 15 2022	= Picaso End Date + QC Lag

Why this? Because the QC Lag affects the availability of the output product in Picaso, and in order to achieve the same in SAP, the interface offsets the End date of the Planned order accordingly.

This results in the availability date of the output product in Picaso and SAP to (better) match. See below:

Picaso plot (TFPD / C5 in AQS)

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_13-50-3.png

SAP MD04 (66328 / AQS)

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_13-52-10.png

In Plants where the QM module is operational, Lab time is also maintained in SAP. In order to avoid duplicating Lab times (in Picaso and SAP0, you want to maintain the Schedule Upload Lag Adjustment table.

SKU Mapping

SAP code added to SKU Code mappings (SKU code is 7 digits with leading 0’s )

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_11-4-26.png

Inventory Targets and Preferences

Time fence = 0
stockout allowed = 7 (to start with, you may adjust later)
forecast ignored = 7
SKU responsible = MTO or STK
search code = 1 (if MTO) or 0 (if STK)
service level target = 95
other necessary fields:

safety stock / high target / min order qty (use inv. unit)
Source location (if same as destination, PICASO understands this is a production location) & source packaging
lead time (for forecast adjustment algorithm)

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_11-16-43.png

Formula

A formula is a list of ingredients. It is our SAP Bill of Materials.

Most formulas are created in Picaso by uploading SAP BOM's.

(automatic refresh if BOM modified? TBC)

Picaso formulas are named after the SAP Production version they are selected from. Therefore, a BOM not associated to a Production Version will not load in Picaso.

Formulas numbers are generated automatically in Picaso. These numbers will be used in Production Standards Effectivity.

When creating a run in the Picaso Scheduler, specify the formula (or keep the default). This formula will determine the production version used when creating the Planned order in SAP. Unless, the Schedule Upload Unit Parameter drives whether SAP Planned orders always use production version 0001 or if the production version is determined by the formula.

Materials - Planning > ADM - Advanced Data Management > image2022-10-17_10-25-10.png

Materials - Planning > ADM - Advanced Data Management > image2022-10-17_10-32-11.png

Materials - Planning > ADM - Advanced Data Management > image2022-10-17_10-31-15.png

Materials - Planning > ADM - Advanced Data Management > image2022-10-17_10-33-57.png

Materials - Planning > ADM - Advanced Data Management > image2022-10-17_10-35-22.png

Production Standards

Materials - Planning > ADM - Advanced Data Management > image2022-10-17_10-37-54.png

Production Standards Effectivity

Materials - Planning > ADM - Advanced Data Management > image2022-10-17_10-39-45.png

Product Family / Business Unit

The Material groups are interfaced from SAP into Picaso.

However, in order for the Picaso Material table to autopopulate the H4, Business Unit, and Finance Material Type field, you want to assign these three attributes to their corresponding material group in this table.

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_14-39-17.png

Schedule Upload Lag Adjustment

The schedule upload lag adjustment has no effect in Picaso (neither on the grid, no anywhere else). It only affect the interface to SAP for planned orders.

Used when the GRPT / QM Module with Average Inspection Duration are used in SAP.

The lag adjustment prevents duplication of QC Times when they are maintained both in SAP and Picaso.

The Schedule Upload Lag Adjustment affects the SAP Planned order end date as below. Consider this Picaso run in plant AUA (Oudenaarde):

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_14-11-22.png

... and its corresponding SAP Planned order:

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_14-13-25.png

Recap:

	Picaso Run	SAP Planned Order
Start Date	Nov 24 2022	Nov 24 2022
End Date	Nov 27 2022	Nov 28 2022

Why such a difference? Consider the QC Lag: 5 days for TFWC in Oudenaarde

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_14-15-43.png

Based on QC Lag only, this is what should have happened:

	Picaso Run	SAP Planned Order	Effect of the QC Lag
Start Date	Nov 24 2022	Nov 24 2022	none
End Date	Nov 27 2022	Dec 2 2022	= Picaso End Date + QC Lag = Nov 27 2022 + 5 = Dec 2 2022

Still not adding up.

But, there is a QC Lag Adjustment record for TFWC in AUA

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_14-22-52.png

Now, it does add up:

	Picaso Run	SAP Planned Order	Effect of the QC Lag	Effect of the Adjustment
Start Date	Nov 24 2022	Nov 24 2022	none	none
End Date	Nov 27 2022	Nov 28 2022	Dec 2 2022	= Dec 2 2022 + (-4) = Nov 28 2022

Learn more about this: Determine QC Time, GRPT, Average Inspection Time, QC Lag Adjusment

Material Equivalents

Materials - Planning > ADM - Advanced Data Management > image2022-10-24_13-6-54.png

Equipment

Materials - Planning > ADM - Advanced Data Management > image2022-10-18_15-57-13.png

Locations

Materials - Planning > ADM - Advanced Data Management > image2022-10-24_13-9-14.png

Location types

Material types	Identifier	What for
Plant	P	Manufacturing facility
Warehouse		Storage facility
Vendor		Vendor

Transit Times

Applies to DRP Records and SAP STO's.

Materials - Planning > ADM - Advanced Data Management > image2022-10-28_11-32-24.png

Transitions

Schedule colors

Package

Materials - Planning > ADM - Advanced Data Management > image2022-10-24_13-10-27.png

Troubleshoot

Interface Management

Schedule Upload Unit Parameters

Production Schedule Monitoring

Push Button Management

Configure who can run the on-demand production schedule interface.

This table let one user run the interface for either one (or multiple) location, or for a set of equipment (production lines) within that location.

Materials - Planning > ADM - Advanced Data Management > image2022-11-8_7-45-22.png

For a unit-specific on-demand upload, insert a check-mark in the Unit-Specific checkbox, and hit the key.

Materials - Planning > ADM - Advanced Data Management > image2022-11-8_7-49-31.png

This takes you to the units list assigned to that user. For that user, the on-demand will only upload the production schedule related to these production units.

Materials - Planning > ADM - Advanced Data Management > image2022-11-8_7-50-58.png