Hi... im not quite sure if this subject belongs in this forum, but anyway...
We have a client who is running SAP R/3 4.6b and wishes to create a sales order interface on the web. Because they dont have WAS, we proposed building a sales order interface using ITS. Im unsure though on which programming model to use - Web Transactions (IAC) or flow logic. The interface simply will contain 10 line items and allow users to search for materials, enter quanities etc.
My issue with flow logic is that its difficult to allow users to search for materials. Within Web Transactions, theres a macro called ~searchhelp that brings up the standard SAP search screens. However, with the flow logic model this doesnt exist. Any suggestions on what programming model I should use for this type of web application?
Hello Costa,
I think you should use Flow Logic. I've published a example to create a sales order on my homepage:
http://www.computerservice-wolf.com/schulung/its-flow-logic-salesorder.html
For search functions you have to write your own RFC enabled function modules to fill dropdown or select boxes. Or do it like we did: We exported the SAP Catalogue to a MySQL PHP application. There we do the search, catalogue browsing and shopping chart. You can see this live at http://www.siteco.de/.
If you need further information, don't hessitate to contact me.
Regards
Gregor
Thanks for your response. A quick question about the persistance of data in flow files and moving data (variables) across pages. My Sales Order screen containes 10 line items consisting of material, quantity and description fields, with a search button next to each material name. When the user clicks on the search button, the app moves to a new page with material search parameters, which lists the materials when executed. Once the user clicks on the material, the app moves back to the original sales order screen and fills the material code and description with the selected material.
I've implemented this by calling a funciton module when the user clicks on the material search button, which stores the contents of all the current line items. Once the user selects a searched material on the next page, the same bapi is called again the material is added to the corresponding line item. I've used the 'persistance' parameter in the flow files to store the contents of the sales order screen. Is this the correct method of passing and storing data using flow files?
Thanks gregor....
Something that concerns me though. Apparently WAS does not support flow logic model of ITS, just IAC's. Our client is looking to upgrade from R/3 4.6b to R/3 Enterprise next year. What kind of impact will this have on our flow logic application? Would we have to convert it to a BSP application?
Thank you for your reply...
Can WAS 6.20 be downloaded and installed for free on a r/3 4.6b license? Would it just sit on a standalone server? Where would the development of the BSP be done, as 4.6b does not have the Web Application Builder in the ABAP workbench?
Add a comment