APO system offers only 5 product specific and another 5 product-location specific, version dependent fields called AT101 – AT105 and ATT01 – ATT05. But what if you need MORE than these 10 extra fields to be version dependent? You can generate more extra fields using the EEWB (Easy Enhancement Workbench) but this tool generates the extra fields as version independent (all planning versions will share the same values).
In this article I’ll show how to make these extra fields made by EEWB version dependent.Continue reading →
Here I’d like to present my solution of a problem in APO planning books where it was necessary to load multiple products and locations at the same time into the planning view and execute some Default macros on all of them. Continue reading →
It it (almost) impossible to debug CIF interface on inbound side because the data being sent from ECC to APO is passed via RFC enabled functions which are called “remotely” from ECC. Therefore it is not possible to just put break point in target (APO) system and expect that debugger will start when you send data from source (ECC) system. Continue reading →
All development or customizing in SAP is written into a transport request unless it is a local object not intended to be transported ($TMP package). Sometimes it might be useful to backup your development but in SAP this task is quite complicated to export all programs, classes, standard texts, …
Therefore there is an option to export the whole development encapsulated on a transport request level. And that’s what this article is about – exporting development encapsulated in a transport request to local file system. Continue reading →
X-Plant material status means that the material can be procured or blocked or not blocked, etc. After you create the status in customizing you can go into its configuration details and setup the the response for everything the material can be related to (Purchasing, BOM’s, Routing/recipe, etc.) using message type either error (type B) or warning (type A). Continue reading →