Hallo every one

Question

Hallo I am  tring to write apcode to
2     Structuring
2.1     Overview
The application should be able to create BOD’s (bill of documents) using a drag & drop based UI to be able to built up the object relations between cross discipline objects. The possibility to attach single documents and bill of documents to the cross discipline structure (as items) has to be provided as well as the creation of material links for specific BOD items.
2.2     Application architecture
We will have to create a new SAP transaction (namespace /CENIT/). This transaction will call a module pool (also to be created in the /CENIT/ namespace and assigned to a new package). The module pool (dialog program) will be able to display a start screen (where it is possible to search for document structures) and a maintenance screen where the chosen structure can be created/enhanced/viewed. The main screen will use SAP Enjoy Controls techniques to display the data with a docking control, splitter control, tree control and ALV grid.
2.2.1     Data Structure
2.2.1.1     Input data
The input data is placed on the start screen. We will need here the entrance information for a document structure (document type, document number, document part, document version). In addition to this information, the document search help CV01 has to be assigned to the input information. It should also be possible to create a new ORM structure using a new document number.
2.2.1.2     Output data
The output will be displayed on the main screen. The main screen area will display a complete BOD explosion of the input. (Column Tree Control). We will need also 2 different areas where we will provide 2 ALV controls displaying document search / material search result data. Drag & drop behaviour has to be implemented between the tree display (BOD explosion ) and the ALV areas. When dragging a document from the ALV to the tree, it should be added as new item. When dragging a material to a certain node of the tree display, it should be added as material link to the corresponding document.
The header document of the BOD structure should have the document type ORM. This has to be checked before exploding the structure. The initial view of the tree structure will not display the exploded BOD. Only if the user is going to expand a certain node, the next level of the current BOD is displayed.
Following column informations should be provided in the tree view:
·     Document type
·     Document number
·     Document part
Document version
·     Document description
·     Document status
·     Linked material
The document search (ALV grid) – top right screen area has following search criteria:
·     Document number
·     Document type
·     Document part
·     Document version
·     Document description
·     Language
·     Owner
·     Document status
The document search ALV result will provide all DRAW-fields as columns.
The material search (ALV grid) – bottom right screen area has following search criteria:
·     Material number
·     Material industry sector
·     Material type
·     Material description
·     Plant
The material search ALV result will provide all MARA / MARC fields as columns.
Drag & drop behaviour / event handling / double click behaviour:
·     If a document info record is dragged from the result ALV grid to a specific tree node, there should come up a decision popup, asking if the document should be inserted as BOD item on the same level or underneath the dropped node.
·     If a material master is dragged from the result ALV to a specific tree node, this material should automatically generate a object link to the corresponding document info record.
·     If a document info record, which is BOD header is dragged to the tree, there should come up a decision popup, asking if only the stand-alone document has to be inserted as BOD item or if the complete structure has to be inserted.
·     The tree display has to be right-click sensitive (context menu), containing following functions:
o     Delete current item
o     Display document info record
·     Double-clicking the tree control or the corresponding ALV grid entry, the application has to be able to provide forward navigation to the document info record / material.
will not display the exploded BOD. Only if the user is going to expand a certain node, the next level of the current BOD is displayed.
Following column informations should be provided in the tree view:
·     Document type
·     Document number
·     Document part
Document version
·     Document description
·     Document status
·     Linked material
The document search (ALV grid) – top right screen area has following search criteria:
·     Document number
·     Document type
·     Document part
·     Document version
·     Document description
·     Language
·     Owner
·     Document status
The document search ALV result will provide all DRAW-fields as columns.
The material search (ALV grid) – bottom right screen area has following search criteria:
·     Material number
·     Material industry sector
·     Material type
·     Material description
·     Plant
The material search ALV result will provide all MARA / MARC fields as columns.
Drag & drop behaviour / event handling / double click behaviour:
·     If a document info record is dragged from the result ALV grid to a specific tree node, there should come up a decision popup, asking if the document should be inserted as BOD item on the same level or underneath the dropped node.
·     If a material master is dragged from the result ALV to a specific tree node, this material should automatically generate a object link to the corresponding document info record.
·     If a document info record, which is BOD header is dragged to the tree, there should come up a decision popup, asking if only the stand-alone document has to be inserted as BOD item or if the complete structure has to be inserted.
Thank you in advance .
Waiting for your reply.

Answer 1

> Is there a question in there somewhere?
> Regards,
> Rich Heilman
C'mon Rich.. the spec was cut & pasted and the question was the last line of the post ie
"Waiting for you reply"
I am pretty sure someone there is unwilling to spend time & do the coding..
~Suresh