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

Master Data

Material table

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

The material filelds are to be populated as below:

Material types

Location Dependent Quality Test Lag

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:

• 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.

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

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

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).

And the dates of its corresponding SAP Planned Order:

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

What is going on? This:

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

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)

SAP MD04 (66328 / AQS)

In Plants where the QM module is operational, the SAP QC Lag (called Average Inspection Duration) is also maintained there. In order to avoid a duplication effect of the Picaso QC Lag and the SAP Av. Insp. Duration, 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 )

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)

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.

Production Standards

Production Standards Effectivity

Product Family / Business Unit

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):

... and its corresponding SAP Planned order:

Recap:

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

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

Still not adding up.

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

Now, it does add up:

Transitions

Schedule colors

Troubleshoot

Interface Management

Schedule Upload Unit Parameters

Production Schedule Monitoring

Push Button Management

User Management