I have inserted production runs in Picaso, but if I go to see one of the codes I have MD04 in sap completely empty.
|
First, verify if the run is exportable.
If it is exportable, run a diagnostic. Go in Process Order Uploads table in ADM, and find the Process Order Upload table.
|
Use the filter option to narrow the list down. Typically, use whichever parameter that is relevant (here, the SKU code will do). Using the date of last upload is generally a good idea:
|
(scroll right to find it)
The notes will help you figure out what the problem is:
|
| Typical notes | Meaning | Solution |
|---|---|---|
| Please specify the order deadlines in ascending order | The Picaso-to-SAP interface tries to create a Planned order with a negative duration. This is due to the schedule upload lag adjustment being greater than the QC lag | You want to make sure that the QC lag is always greater than the Schedule upload lag adjustment. It likely that the QC lag had been updated, but the Schedule upload Lag adjustment was forgotten. |
| The Picaso run maps with a planned order in SAP that has already been converted to a Process order, and this Process order has been TECOed. | The Picaso run is likely to be deleted since Production is either completed or cancelled. |
| The Picaso-to-SAP interface tries to create a Planned order for which the production version in SAP does not exist. | For units that always use Prod Vers 0001, verify if PV has to be created. For other production units, check coherency of the formula used in the run. The formula maps with the SAP Production version |
|
You may want to use a panel to highlight important steps.
|
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|