Number of backward edges

This is one of my favourite planning indicators from /SAPAPO/PMON. It's very simple, just a count of pegging delays, but it has a strong correlation with planning caos (or people screaming). This graphic shows the average indicator for serveral plants already using APO and for a new plant rollout. The first month was problematic then it became stable.



Music playing: Cranes

Web spreadsheet

Yesterday the webmail and calendar, today the spreadsheet and word processor, tomorrow the web ERP.

Today Microsoft is becoming obsolete. Tomorrow, will it be SAP?

Open source software and music

Some years ago, it was through an open source software project named Plone that I discovered the Plone band. And it become one of my favourites. Now it happened again, the project Django lead me to the great Django Reinhardt.

Open source is good.

Sailing the ATP storm

ATP integration between APO and R3 is a mess. Whenever possible, following this simple recipe avoids many problems:

1) Don't set any restriction on receiving hours at the customer
2) Change the default requested time in sales orders to some normal value like 9 am.

In sales order the proposed delivery time can be changed on exit MV45AFZZ, in userexit_move_field_to_vbep. For stock transport orders it can be changed in BADI ME_PROCESS_PO_CUST.