Hey this sounds interesting
Personal Data Miner for SAP - gives you the ability to reach into the SAP database directly from MS Access.
http://www.pdm.lu
I should try and remember to try this one out.
Thursday, November 27, 2003
Further SAP projects
Processing returns of configurable & serialized materials in SAP
Return processing in SAP is pitiful. Try adding configurable and serialized products. It blows SAP out of the water.
Move the configurable material out of sales stock and into inventory. But first, create a material variant for this configurable material. Here lies the next problem, SAP does not create a variant which references the configuration in a sales order. So I have to write your own program to create material variants. (Steps involved are: Create a new material master, configure it, attach a BOM and a routing, create and mark a cost estimate).
Once this is in inventory, you need to break it down to its components. More problems. Since it is configurable and changes frequently, the components in the current BOM may not match what you built and shipped out. So read the components from the original production order and compare this with today's BOM. At the end, perform a 561/562 (or something similar) to swap the variant for the components.
Now the serial numbers. If you don't reuse your serial numbers, there is no problem. Sadly, that is not the case in most companies. The serial number of purchased components need to be reused. So when we break down the KMAT, we need to make these component serial numbers available for use. Also if there are configured serial numbers, we need to remove configuration information to avoid problems during delivery (In an inbound delivery, the system checks the serial number configuration with the purchase order configuration).
Return processing in SAP is pitiful. Try adding configurable and serialized products. It blows SAP out of the water.
Move the configurable material out of sales stock and into inventory. But first, create a material variant for this configurable material. Here lies the next problem, SAP does not create a variant which references the configuration in a sales order. So I have to write your own program to create material variants. (Steps involved are: Create a new material master, configure it, attach a BOM and a routing, create and mark a cost estimate).
Once this is in inventory, you need to break it down to its components. More problems. Since it is configurable and changes frequently, the components in the current BOM may not match what you built and shipped out. So read the components from the original production order and compare this with today's BOM. At the end, perform a 561/562 (or something similar) to swap the variant for the components.
Now the serial numbers. If you don't reuse your serial numbers, there is no problem. Sadly, that is not the case in most companies. The serial number of purchased components need to be reused. So when we break down the KMAT, we need to make these component serial numbers available for use. Also if there are configured serial numbers, we need to remove configuration information to avoid problems during delivery (In an inbound delivery, the system checks the serial number configuration with the purchase order configuration).
Its been a long time since my last post. Life got in the way.
With so many items trying to grab your attention, it is easy to forget the non-urgent activities.
Recent trends
SAP - Using Javascript to script and automate the SAPGUI frontend.
(I should write an article about this, since it is a lot of fun)
SAP - Planning for configurable materials. Despite the rich functionality that SAP provides in 4.6C, there is a lack of clear instructions on planning KMATs. Working with the planning folks, I've learnt a lot about the complex nature of planning these beasts. Furthermore, what information must drive your forecasting. I wrote two SAP extract programs that get production order information from SAP. The extract files are imported into Access (500K + 3M rows) where I do some crunching to reduce the data volume. The resulting time series is something that the planners can use. But I went a step further, looked at all KMAT BOMs and extracted the characteristics used for any selection condition/procedure in a BOM. That list of characteristics is what is relevant for planning. By comparing this list with the planning profiles of your KMATs, you can analyze how much coverage you have for each KMAT.
The next step is to compare the percentages in your configuration points with the actual characteristic - value percentages. Again this was accomplished in Access.
Now all this information is not useful if it is difficult to update percentages. So I wrote an update program that can go in and change percentages on each configuration point.
Interested? Give me a yell.
With so many items trying to grab your attention, it is easy to forget the non-urgent activities.
Recent trends
SAP - Using Javascript to script and automate the SAPGUI frontend.
(I should write an article about this, since it is a lot of fun)
SAP - Planning for configurable materials. Despite the rich functionality that SAP provides in 4.6C, there is a lack of clear instructions on planning KMATs. Working with the planning folks, I've learnt a lot about the complex nature of planning these beasts. Furthermore, what information must drive your forecasting. I wrote two SAP extract programs that get production order information from SAP. The extract files are imported into Access (500K + 3M rows) where I do some crunching to reduce the data volume. The resulting time series is something that the planners can use. But I went a step further, looked at all KMAT BOMs and extracted the characteristics used for any selection condition/procedure in a BOM. That list of characteristics is what is relevant for planning. By comparing this list with the planning profiles of your KMATs, you can analyze how much coverage you have for each KMAT.
The next step is to compare the percentages in your configuration points with the actual characteristic - value percentages. Again this was accomplished in Access.
Now all this information is not useful if it is difficult to update percentages. So I wrote an update program that can go in and change percentages on each configuration point.
Interested? Give me a yell.
Tuesday, August 27, 2002
I have to download .NET frameworks to use the componentsworkbook example. I think that I'll stick to using MSXML4 and the MSXSL application
Search for MSXSL.EXE on www.microsoft.com/msdn
http://download.microsoft.com/download/xml/Utility/2.0/NT5XP/EN-US/msxsl.exe
It is really easy to use this to generate XLST docs from XML.
msxsl data.xml sheet.xslt -o output.html
Search for MSXSL.EXE on www.microsoft.com/msdn
http://download.microsoft.com/download/xml/Utility/2.0/NT5XP/EN-US/msxsl.exe
It is really easy to use this to generate XLST docs from XML.
msxsl data.xml sheet.xslt -o output.html
Reading more about the weblog movement, I found this article on how weblog or K-logs can be used within an organization
http://www.blogroots.com/chapters.blog/id/4
http://www.blogroots.com/chapters.blog/id/4
http://www.componentsnotebook.com/notebooks/index.html
This website discusses how to use XML within Frontpage to generate menus on the fly.
There is VBA code that goes and replaces the menu tables with XSLT transformed XML.
The actual code is located here
http://www.developerfusion.com/show/2021/3/
Interesting approach which combines XML only content + XSLT with HTML.
I feel that a pure XML and XSLT solution would be better.
I will continue using the SLIQUA web template from OWSD.ORG to generate good looking web pages from XML.
Currently struggling with the structure of the XML document.
One idea was to have each content page as a seperate document. The menu structure would be a seperate XML document.
There would be seperate templates to generate the mainbody and menus.
I am still wondering how can I integrate BLOGGER or Radio into the website.
This website discusses how to use XML within Frontpage to generate menus on the fly.
There is VBA code that goes and replaces the menu tables with XSLT transformed XML.
The actual code is located here
http://www.developerfusion.com/show/2021/3/
Interesting approach which combines XML only content + XSLT with HTML.
I feel that a pure XML and XSLT solution would be better.
I will continue using the SLIQUA web template from OWSD.ORG to generate good looking web pages from XML.
Currently struggling with the structure of the XML document.
One idea was to have each content page as a seperate document. The menu structure would be a seperate XML document.
There would be seperate templates to generate the mainbody and menus.
I am still wondering how can I integrate BLOGGER or Radio into the website.
Jon Udell's article
http://www.infoworld.com/articles/pl/xml/02/06/24/020624plcomp.xml
http://www.byte.com/documents/s=7181/byt1022183228615/0527_udell.html
This article discusses how distributed Knowledge management can take place across the Internet.
The most powerful concept is that of using RSS (Rich Site Summary) and WebLogs to have something akin to a huge organic filter of content. The analogy to Google is striking.
http://www.infoworld.com/articles/pl/xml/02/06/24/020624plcomp.xml
http://www.byte.com/documents/s=7181/byt1022183228615/0527_udell.html
This article discusses how distributed Knowledge management can take place across the Internet.
The most powerful concept is that of using RSS (Rich Site Summary) and WebLogs to have something akin to a huge organic filter of content. The analogy to Google is striking.
Subscribe to:
Posts (Atom)