Access ADM and WebDP with this link: http://alphdb05.eua.solvay.com/ADMPrd/
Picaso materials are not package specific. They match the SAP concept of a Material group.
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 | |
| Lot Site | |||
| Unit of Measure | Mandatory | as fit | all other tables refer to that one. Example: production rates in production standards |
| Search Code | Mandatory | ||
| 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 | |
| Business Unit | Mandatory | as per SAP | autopopulated, For it to work, you want to update the Product Family / Business Unit table. Once this table is updated, that field will autopopulate. |
| 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 | What for |
|---|---|
| Finished Goods | Finished goods |
| Additives | Raw Materials |
| Intermediates | Bulk, polymers |
| Package Materials | Package Materials |
| Resins | Resins |
| sfm | monomers (TFEM, Sulfones, VF2,...) |
| wide spec |
The material shows a global Quality test lag:
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.
Effect of the Quality Test Lag on:
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.
Consider this run. Its attributes:
The effect of the plot of a 2 days QC Lag:
Consider the dates of this run:
And the dates of its corresponding SAP Planned Order:
| Picaso Run | SAP Planned Order | Difference | |
|---|---|---|---|
| Start Date | Nov 07 2022 | Nov 07 2022 | same |
| End Date | Nov 8 2022 | Nov 15 2022 | 7 days |
What is going on? This:
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 |
SAP code added to SKU Code mappings (SKU code is 7 digits with leading 0’s )
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.
The schedule upload lag adjustment no effect in Picaso (neither on the grid, no anywhere else). Only affect the interface to SAP for planned orders.
Used when the GRPT / QM Module with Average Inspection Duration are used in SAP.
The Planned order end date = Run End Date + QC Lag + Schedule Upload Lag Adjustment.
For more, visit Effect of the Quality Test Lag on the end date of the corresponding SAP Planned order
