Smart form function module

hi ,
The code in program lines is stored in which part of the generated function module and belongs to which include.
Thank you.

Hi ,
Try to locate the any variable u have written in the program line in se37 .
Regards

Similar Messages

Smart form function modules

I have a smart form and executing it with standard tcode but I couldnt see the output. How could i view the generated function module and where to assign this. Help needed immediately.
Janelle

In your print program first call the following FM. Pass the name of your smartform. It will return the generated FM name.
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
       EXPORTING
            FORMNAME           = V_FORM_NAME
       IMPORTING
            FM_NAME            = V_FM_NAME
       EXCEPTIONS
            NO_FORM            = 1
            NO_FUNCTION_MODULE = 2
            OTHERS             = 3.
Now call the returned FM name.
CALL FUNCTION V_FM_NAME

Smart forms function modules

hi all,
what is the function module to pass the print partamets in smartforms.

Hi
the function module is SSF_FUNCTION_MODULE_NAME.
here is sample code....
in this vname is the function module which is generated when we execute the smartform.....it is declared as ...
vname type rs38l_fnam.
in the ssf_function_module_name...in exporting we need to pass the values which we want to pass ,from print program to form.
 STRUCTURE DECLARATION
data : wa_lfa1 type z50875_lfa1,
 wa_ekko type z50875_ekko,
 wa_ekpo type z50875_ekpo,
 it_ekpo type z50875it_ekpo,
 vname type rs38l_fnam.
 SELECTION-SCREEN
selection-screen begin of block b1 with frame title text-000.
parameter : p_no type ekko-ebeln obligatory.
selection-screen end of block b1.
at selection-screen on p_no.
perform validate.
 START-OF-SELECTION
start-of-selection.
perform get_vendordata.
perform get_itemdata.
call function 'SSF_FUNCTION_MODULE_NAME'
 exporting
 formname = 'ZMM_SMARTFORMS'
 importing
 fm_name = vname
 exceptions
 no_form = 1
 no_function_module = 2
 others = 3.
if sy-subrc <> 0.
 message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
call function vname
 exporting
 wa_lfa1 = wa_lfa1
 wa_ekko = wa_ekko
 wa_ekpo = wa_ekpo
 tables
 it_ekpo = it_ekpo
 exceptions
 formatting_error = 1
 internal_error = 2
 send_error = 3
 user_canceled = 4
 others = 5.
if sy-subrc <> 0.
 message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*& Form GET_DATA
form get_data .
select single ebeln lifnr
 from ekko
 into wa_ekko
 where ebeln = p_no.
endform. " GET_DATA
*& Form GET_VENDORDATA
form get_vendordata .
select single lifnr name1 land1 ort01 regio
 from lfa1
 into wa_lfa1
 where lifnr = wa_ekko-lifnr.
endform. " GET_VENDORDATA
*& Form GET_ITEMDATA
form get_itemdata .
select ebelp ematn aedat mtart netwr
 from ekpo
 into table it_ekpo
 where ebeln = wa_ekko-ebeln.
endform. " GET_ITEMDATA
*& Form validate
form validate .
perform get_data.
if sy-subrc ne 0.
 message 'PURCHASE DOCUMENT DOES NOT EXISTS' type 'E'.
 exit.
endif.
endform. " validate

Smart Form and Module Pool

Can anybody provide me good step by step procedurehow create smart form and module pool programming.
My email Id is [email protected]

hi,
SAP Smartforms can be used for creating and maintaining forms for mass printing in SAP Systems. The output medium for Smartforms support printer, fax, e-mail, or the Internet (by using the generated XML output).
According to SAP, you need neither have any programming knowledge nor use a Script language to adapt standard forms. However, basic ABAP programming skills are required only in special cases (for example, to call a function module you created or for complex and extensive conditions).
1. Create a new smartforms
Transaction code SMARTFORMS
Create new smartforms call ZSMART
2. Define looping process for internal table
Pages and windows
First Page -> Header Window (Cursor at First Page then click Edit -> Node -> Create)
Here, you can specify your title and page numbering
&SFSY-PAGE& (Page 1) of &SFSY-FORMPAGES(Z4.0)& (Total Page)
Main windows -> TABLE -> DATA
In the Loop section, tick Internal table and fill in
ITAB1 (table in ABAP SMARTFORM calling function) INTO ITAB2
3. Define table in smartforms
Global settings :
Form interface
Variable name Type assignment Reference type
ITAB1 TYPE Table Structure
Global definitions
Variable name Type assignment Reference type
ITAB2 TYPE Table Structure
4. To display the data in the form
Make used of the Table Painter and declare the Line Type in Tabstrips Table
e.g. HD_GEN for printing header details,
 IT_GEN for printing data details.
You have to specify the Line Type in your Text elements in the Tabstrips Output options.
Tick the New Line and specify the Line Type for outputting the data.
Declare your output fields in Text elements
Tabstrips - Output Options
For different fonts use this Style : IDWTCERTSTYLE
For Quantity or Amout you can used this variable &GS_ITAB-AMOUNT(12.2)&
5. Calling SMARTFORMS from your ABAP program
REPORT ZSMARTFORM.
Calling SMARTFORMS from your ABAP program.
Collecting all the table data in your program, and pass once to SMARTFORMS
SMARTFORMS
Declare your table type in :-
Global Settings -> Form Interface
Global Definintions -> Global Data
Main Window -> Table -> DATA
Written by : SAP Hints and Tips on Configuration and ABAP/4 Programming
 http://sapr3.tripod.com
TABLES: MKPF.
DATA: FM_NAME TYPE RS38L_FNAM.
DATA: BEGIN OF INT_MKPF OCCURS 0.
 INCLUDE STRUCTURE MKPF.
DATA: END OF INT_MKPF.
SELECT-OPTIONS S_MBLNR FOR MKPF-MBLNR MEMORY ID 001.
SELECT * FROM MKPF WHERE MBLNR IN S_MBLNR.
 MOVE-CORRESPONDING MKPF TO INT_MKPF.
 APPEND INT_MKPF.
ENDSELECT.
At the end of your program.
Passing data to SMARTFORMS
call function 'SSF_FUNCTION_MODULE_NAME'
exporting
 formname = 'ZSMARTFORM'
VARIANT = ' '
DIRECT_CALL = ' '
IMPORTING
 FM_NAME = FM_NAME
EXCEPTIONS
 NO_FORM = 1
 NO_FUNCTION_MODULE = 2
 OTHERS = 3.
if sy-subrc <> 0.
 WRITE: / 'ERROR 1'.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function FM_NAME
EXPORTING
ARCHIVE_INDEX =
ARCHIVE_INDEX_TAB =
ARCHIVE_PARAMETERS =
CONTROL_PARAMETERS =
MAIL_APPL_OBJ =
MAIL_RECIPIENT =
MAIL_SENDER =
OUTPUT_OPTIONS =
USER_SETTINGS = 'X'
IMPORTING
DOCUMENT_OUTPUT_INFO =
JOB_OUTPUT_INFO =
JOB_OUTPUT_OPTIONS =
TABLES
 GS_MKPF = INT_MKPF
EXCEPTIONS
 FORMATTING_ERROR = 1
 INTERNAL_ERROR = 2
 SEND_ERROR = 3
 USER_CANCELED = 4
 OTHERS = 5.
if sy-subrc <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
What is SAP Smart Forms?
SAP Smart Forms is introduced in SAP Basis Release 4.6C as the tool for creating and maintaining forms.
SAP Smart Forms allow you to execute simple modifications to the form and in the form logic by using simple graphical tools; in 90% of all cases, this won't include any programming effort. Thus, a power user without any programming knowledge can
configure forms with data from an SAP System for the relevant business processes.
To print a form, you need a program for data retrieval and a Smart Form that contains the entire from logic. As data retrieval and form logic are separated, you must only adapt the Smart Form if changes to the form logic are necessary. The application program passes the data via a function module interface to the Smart Form. When activating the Smart Form, the system automatically generates a function module. At runtime, the system processes this function module.
You can insert static and dynamic tables. This includes line feeds in individual table cells, triggering events for table headings and subtotals, and sorting data before output.
You can check individual nodes as well as the entire form and find any existing errors in the tree structure. The data flow analysis checks whether all fields (variables) have a defined value at the moment they are displayed.
SAP Smart Forms allow you to include graphics, which you can display either as part of the form or as background graphics. You use background graphics to copy the layout of an existing (scanned) form or to lend forms a company-specific look. During printout, you can suppress the background graphic, if desired.
SAP Smart Forms also support postage optimizing.
Also read SAP Note No. 168368 - Smart Forms: New form tool in Release 4.6C
What Transaction to start SAP Smart Forms?
Execute transaction SMARTFORMS to start SAP Smart Forms.
Key Benefits of SAP Smart Forms:
SAP Smart Forms allows you to reduce considerably the implementation costs of mySAP.com solutions since forms can be adjusted in minimum time.
You design a form using the graphical Form Painter and the graphical Table Painter. The form logic is represented by a hierarchy structure (tree structure) that consists of individual nodes, such as nodes for global settings, nodes for texts, nodes for output tables, or nodes for graphics.
To make changes, use Drag & Drop, Copy & Paste, and select different attributes.
These actions do not include writing of coding lines or using a Script language.
Using your form description maintained in the Form Builder, Smart Forms generates a function module that encapsulates layout, content and form logic. So you do not need a group of function modules to print a form, but only one.
For Web publishing, the system provides a generated XML output of the processed form.
Smart Forms provides a data stream called XML for Smart Forms (XSF) to allow the use of 3rd party printing tools. XSF passes form content from R/3 to an external product without passing any layout information about the Smart Form.
PROGRAM YMPSKEL MESSAGE-ID YL.
DESCRIPTION
written by !
TABLES:
DATA: OK_CODE(4), " ok code - screen 1
OK_CODE2(4).
DATA C LIKE SY-INDEX. " Index for screen loop
*& Module USER_COMMAND_0100 INPUT
process after input for screen 0100 *
MODULE USER_COMMAND_0100 INPUT.
CASE OK_CODE.
WHEN 'SAVE'.
WHEN 'DISP'.
WHEN 'LIST'.
C = 0. "reset loop control
WHEN OTHERS.
ENDCASE.
CLEAR OK_CODE.
ENDMODULE. " USER_COMMAND_0100 INPUT
*& Module STATUS_0100 OUTPUT
process before output for screen 0100 *
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'AMEND'. " set gui status
SET TITLEBAR '100'. " set title
ENDMODULE. " STATUS_0100 OUTPUT
*& Form SAVE data
Save screen details
FORM SAVE.
CLEAR OK_CODE.
ENDFORM.
*& Form DISPLAY
FORM DISPLAY.
ENDFORM.
*& Module EXIT_COMMAND INPUT
exit commands are processed before validation *
defined by E against function in menu painter(function list)
MODULE EXIT_COMMAND INPUT.
CASE OK_CODE.
WHEN 'EXIT'. CLEAR OK_CODE. SET SCREEN 0. LEAVE SCREEN.
WHEN 'CANC'. CLEAR OK_CODE. SET SCREEN 0. LEAVE SCREEN.
WHEN 'BACK'. CLEAR OK_CODE. SET SCREEN 0. LEAVE SCREEN.
ENDCASE.
ENDMODULE. " EXIT_COMMAND INPUT
*& Form list
text *
FORM LIST.
CLEAR OK_CODE. SET SCREEN 200. LEAVE SCREEN.
ENDFORM. " LIST
*& Module EXIT_COMMAND_200 INPUT
exit command processing for screen 200 *
defined by E against function in menu painter(function list)
MODULE EXIT_COMMAND_200 INPUT.
CASE OK_CODE2.
WHEN 'EXIT'. CLEAR OK_CODE2. SET SCREEN 0. LEAVE SCREEN.
WHEN 'CANC'. CLEAR OK_CODE2. SET SCREEN 0. LEAVE SCREEN.
WHEN 'BACK'. CLEAR OK_CODE2. SET SCREEN 100. LEAVE SCREEN.
ENDCASE.
ENDMODULE. " EXIT_COMMAND_200 INPUT
*& Module STATUS_0200 OUTPUT
process before output for screen 200 *
MODULE STATUS_0200 OUTPUT.
SET PF-STATUS 'POPUP'.
SET TITLEBAR 'xxx'.
ENDMODULE. " STATUS_0200 OUTPUT
Module pool programs are created in abap development work bench (TCODE: SE80).
Here we can do all the works whatever you can do in abap.
Module pool programs are also called dialog programs.
The module Pool are reports prepared for different screens and to manage the sequence of events of these screens, in the transaction SE80 you can see all the dynpros that you have for this kind of report, add new ones, add all types of element to the report.
Process Before Output is the part of the dynpro code that is processed before the user can do anything with the data in the screen
Process After Input is the part of the dynpro code that is processed after the interaction with the user.
module pool programs are excuted using Tcodes
regards,
sreelakshmi

Adobe Forms function module - downloading the xstring output in PDF file

Hi Guys,
I'm using Adobe forms and fetching its output in an XSTRING PDF format. How can I download this XSTRING output to a PDF file and store on the local file system?
I'm using the following approach to getting a PDF output:
ls_outputparams-getpdf = 'X'.
CALL FUNCTION 'FP_JOB_OPEN'
CHANGING
 ie_outputparams = ls_outputparams.
* Get the name of the generated function module
CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
 EXPORTING
 i_name = 'ZADOBEFORM'
 IMPORTING
 e_funcname = lv_fmname.
IF sy-subrc <> 0.
ELSE.
* Call the Adobe Form function module
 CALL FUNCTION lv_fmname
 EXPORTING
 /1bcdwb/docparams = ls_docparams
 IMPORTING
 /1bcdwb/formoutput = ls_form_output
 EXCEPTIONS
 usage_error = 1
 system_error = 2
 internal_error = 3.
 IF sy-subrc <> 0.
 ENDIF.
ENDIF.
* Close the spool job
CALL FUNCTION 'FP_JOB_CLOSE'.
Now, the variable LS_FORM_OUTPUT-PDF contains the PDF output in XSTRING. My question is how can I download this as a PDF file to my local machine.
Kind Regards,
Shailesh.

hi guys,
im using all FM to download my PDF adobe but in this part :
ls_spfli-carrid = 'AA'.
ls_spfli-connid = '0017'.
APPEND ls_spfli TO it_spfli.
flag = 'X'.
is_address_type = '1'.
is_address_number = '22515'.
is_person_number = '22517'.
is_country = 'IN'.
*&--- Call the generated function module
CALL FUNCTION '/1BCDWB/SM00000200'
 EXPORTING
* /1BCDWB/DOCPARAMS =
 it_spfli = it_spfli
 flag = flag
 is_address_type = is_address_type
 is_address_number = is_address_number
 is_person_number = is_person_number
 is_country = is_country
IMPORTING
 /1bcdwb/formoutput = fp_formoutput
EXCEPTIONS
 usage_error = 1
 system_error = 2
 internal_error = 3
 OTHERS = 4
I have usage_error knowing that the execution of the function module in SE37 pass successfuly and also the execution of the forms .
in your opinion what can be the problem?
Kind Regards,

Error while determining the form function module

Hi everyone,
We are experiencing problems while displaying one adobe form in ESS. Its the Travel Expense form (PTRV_EXPENSE_FORM). When pressing the button to Display/Print the form we get an error message: "Error while determining the form function module", and no form I shown. The ADS server is configured correctly and there are other forms that are actually working, for example the Travel Request form. We are running WAS 7.0 with SP12.
Anyone has an idea what can cause the problem? Any help is greatly appreciated.
Thanks in advance!
Regards,
Sophie

Viktor,
Thank you for your answer, it solved our problem!
Regards,
Sophie

Use of SAP Smart Forms - Text Modules

Hi!
One or two questions regarding the SAP Smart Forms text modules.
First: In which table the text name is saved? Is there something like the STXH table for SapScript Objects?
Second: Is it possible to use SmartForm text modules in the text determination for SD (Invoice e.g.)?
I´m looking forward for many answers
Greetings
Mark

Hi,
From STXL table u can get the text object, id n name pertaining to a text .These things put in FM 'READ_TEXT'. u get the long text...
Instead in smartforms, u can directly include texts using Create-Text, Type Include text...enter the id, name ,lang and object....
Also, for text names, objects and ID..u go to the place where long text has been entered, enter the sapscript editor from there, goto Header...u ll get all the detaails..
hope it helps,
Regards,
Bikash

Travel Display Form: Error while determining the form function module

Hi,
In Travel Reqeust (ECC6/ESS) when i click the Display Form after raising the Travel Request it shows the error
"Error while determining the form function module"
Can anyone have idea on this?
Regards,
Boobalan

Hi,
This error was due to Not supported platforms of ADS (Adobe Document services)
It was not supported on itanium64 bit processors.
Please check where the ADS is supported in service.sap.com/pam
You can use the ADS in the Non-Supported Server by linking it to Supported Platform Server using the SM59 link. This will make the ADS files to work.
Please refer the ADS Config Doc for details.
Hope you also solve this problem.
Regards,
Boobalan

What is control form function module.

hi
what is control form function module.

Hi Chaitanya,
The function module CONTROL_FORM can be used to pass the control
commands to FORM THROUGH ABAP/4 PROGRAM.
Function Call
CALL FUNCTION 'CONTROL_FORM'
EXPORTING COMMAND = ?...
EXCEPTIONS UNOPENED =
UNSTARTED =
Export parameters:
COMMAND
Enter the SAPscript statement you want to execute in ITF format, but without the statement paragraph attribute '/:'.
Exceptions:
UNOPENED
The current form function could not be executed, since the form output was no yet initialized using OPEN_FORM.
UNSTARTED
No form was opened yet.
Possible reasons:
>The form processing was started using OPEN_FORM without specifying a form name, but no form was opened yet using START_FORM.
>The last used form was closed using END_FORM, but no new form was opened using START_FORM.
>The last filled page of the current form has no subsequent page. In this case, the system automatically terminates form printing after this page. You need no explicit END_FORM call.
>In the current form, no page contains a main window, but a text element shall be output in the main window.
Regards,
Rajesh K Soman
Please rewared points if found helpful.

Smart Form Functional Specification

Hi Gurus,
I have to design a smart form functional specification, but i don't have any idea about how to prepare the functional specification?
can anybody send me the smart form functional specification template ?
which helps me to prepare the specification

Hi Devi,
Here is the FS for Form,
Functional Specification Document for Forms
Authors
Approved By
TABLE OF CONTENTS
1 OVERVIEW SECTION: 3
1.1 DOCUMENT OVERVIEW: 3
1.2 REVISION HISTORY: 3
1.3 OPEN ISSUES: 3
1.4 EXTERNAL REFERENCES: 3
1.5 REQUEST OVERVIEW: 3
1.6 GENERAL PROCESSING REQUIREMENTS: 4
2 BUSINESS/FUNCTIONAL REQUIREMENTS 5
2.1 REQUIREMENT DESCRIPTIONS: 5
2.2 BUSINESS DRIVER 5
2.3 TO-BE BUSINESS PROCESS: 5
2.4 TO-BE BUSINESS PROCESS FLOW DIAGRAM: 5
2.5 ASSUMPTIONS: 5
2.6 DEPENDENCIES: 5
2.7 RISKS: 5
2.8 SECURITY: 6
2.9 OTHER REQUIREMENTS: 6
3 FORM SECTION 7
3.1 REPORT SELECTION SCREEN: 7
3.2 STANDARD FORM NAME: 7
3.3 FORM LAYOUT: 7
3.4 DATA SOURCE: 7
3.5 SPECIAL REQUIREMENTS PROCESSING: 7
3.6 HOW TO EXECUTE THE FORM: 8
4 UNIT TEST PLAN SECTION 9
4.1 FUNCTIONAL UNIT TEST PLAN: 9
5 USER GUIDE REQUIREMENTS 10
5.1 USER GUIDE REQUIREMENTS: 10
6 APPENDIX 11
6.1 APPENDIX: 11
1 Overview Section:
1.1 Document Overview:
(Provide the high level identification information about the object to be developed. Id, title, Release etc)
Project Project Atlas
Development Object ID: SC-F-125
Development Object Title: Purchase Order Form
Release:
Process Team: Supply Chain
Process Area: Procure-to-Pay
1.2 Revision History:
{This section should be filled with other details about the owner of functional specs, current status of document as explained in the status key etc}
Date Modified Version Modified By Description of Change(s)
1.3 Open Issues:
(Any open issues should be reported in this section)
Issue # Issue Date Issue Title / Description Priority Resolved Date Any Other Comments
1.4 External References:
(Identify any documents referenced in any part of this document. (Attach documents where possible.)
Document Title Filename Author Identifier (Version/Date)
Process Flow diagram N/A
Screen Shots if any N/A
Sample data file PO Form Layout (Single Page) Erik Kraus 1/ (10/11/2006)
Sample data file PO Form Layout (Multiple Pages) Erik Kraus 1/ (10/11/2006)
1.5 Request Overview:
Complexity 0 High
1 Medium
0 Low
System(s) Impacted 1 R/3
0 CRM
0 BW
0
 0 Other
Existing SAP transaction(s) involved? ME22N, ME23N
New SAP transaction(s) involved? ME22N; then click Messages to print or Print Preview to view.
Menu path for transaction(s) Logistics  Materials Management  Purchasing  Change
1.6 General Processing Requirements:
(Check the appropriate boxes for e.g. if the development object is an batch report that runs monthly, then check the Online and Monthly boxes in the Processing mode and frequency section and also provide the expected data volume if known)
Processing Mode: 1 Online
0 Batch
Frequency 0 Annually
0 Quarterly
0 Monthly
1 Daily
 1 Real Time
1 Ad-Hoc
1 Others
Expected Data Volume
2 Business/Functional Requirements
Section 2 describes what is needed. This information is used to build the design (how to do it) in Sections 3 and on
2.1 Requirement Descriptions:
Describe the purpose of the object. Brief overview
The purchase order form is used to display the purchase order in SAP. This form can also be sent to the supplier via e-mail or fax in SAP. The PO can also be displayed in the Print Preview screen and printed out as well.
2.2 Business Driver
The PO Form is standard in SAP. Modifications to the form will be necessary to meet the needs of the purchasing organizations at Sage. The PO form is necessary so that all the details of the purchase order can be faxed/ emailed to the supplier and also can be printed out into a hard copy form for internal purposes. The PO form also needs to be able to be viewed via the print preview icon in SAP.
2.3 To-Be business process:
Describe the To-Be business process
Customized Sage Purchase Order Form.
2.4 To-Be business process flow diagram:
Describe the To-Be business process flow diagram
N/A
2.5 Assumptions:
List all the assumptions that were made when developing this object
1) Standard SAP PO Form will need to be modified from its standard layout.
2) Font for Purchase Order form will be Times New Roman
3) PO Form will be created in English
2.6 Dependencies:
List all the dependencies that were made when developing this object
N/A
2.7 Risks:
(What are the risks that make this development unique? What risks need to be proactively dealt with in order to be successful? What data sources are needed but not readily available? Are there any risks or concerns that make this development out of the ordinary?)
N/A
2.8 Security:
(Any security requirement for this object)
2.9 Other Requirements:
(If there are any other requirement which is not covered under section 2)
N/A
3 Form Section
Type: 0 SAP Script 1 Smart forms
3.1 Report Selection Screen:
Describe the selection screen of the program. Specify fields for selection and what checks are needed after the user has entered their criteria.
Field Name Select Options / Parameters / Radio Buttons / Check Boxes Default Values
From To Validation
 Required /Optional F4 Values
N/A N/A N/A N/A N/A N/A
3.2 Standard form name:
Give the name of the SAP Script or Smart form name if copied from SAP
MEDRUCK Form in SAP
3.3 Form Layout:
Describe the form layout for each page.
The PO form will contain information at the Header Level, Item Level, and Authorizations levels.
Header Level:
The header level will contain all the supplier, bill-to party/address, and ship-to party/address information. The header level will also contain the payment and shipping terms, logo, page number, purchase order title, purchase order number, supplier number in SAP, and the PO date.
Item Level:
The item level will contain the item number, material and description, order unit, quantities, date required, unit cost, and the total amount of the line-item. The item-level will also contain the line-item text of purchase order.
Authorization:
The authorization section of the form will contain the name, telephone number, and email address of the purchasing agent.
Other:
-The Total Amount and Currency will be displayed to the right of the Authorization information.
-The layout will include sections and fields with borders. For example the Ship-To, Bill-To, and Supplier will be enclosed in rounded edge boxes. The Layout can be viewed in the Attachments section:
portion of section 3.4. which will show an example of a PO with only one page and a PO with multiple pages.
3.4 Data Source:
Identify the data that has to be appeared in the forms. Table Name-Field Name
All the fields will be available on the SAP standard form MEDRUCK. Any additional fields that are not on the standard form will need to be added. The mapping for additional fields not in the standard form will be shown below in each section (Header Level, Item-Level, and Authoriztions) if required.
Please see below for the required fields in the form:
This Section will contain details on the Header, Line-Item, and Authorization sections of the form. A section for attachements will also be inlcuded at the end.
I. Header Information:
The following fields will be displayed for the header information.
- Title: Purchase Order
- Logo: The Sage Software logo will appear in the top left corner of the form.
- PO Creation Date (MM/DD/YYYY)
- Supplier Number
- PO Number
- Page Number
- Bill to Name and Address
- Supplier Name and Address
- Ship to Name and Adress
- Payment Terms: (not on standard form, see field mapping section below)
- Shipping Terms: (not on standard form, see field mapping section below). The shipping terms are the same as the incoterms in SAP. There are two fields for the incoterms and both will be used for the shipping terms.
- Header Text
Additional Notes for Header Fields:
PO creation date should be in format MM/DD/YYYY
Page Number should be in format Page 1 of 1, Page 2 of 3, etc format
The Bill To name and address will come from the company code that is assigned to the plant in the purchase order.
The Ship To name and address will come from the storage location in the first line-item on the purchase order if the SC Vendor box is not checked on the delivery address tab of the purchase order. If the SC Vendor box is checked on the delivery address tab, then the Ship To address will come from the delivery address tab on the purhcase order from the central address management system.
The Supplier name and address will come from the vendor master in the purchase order.
The central address management system will need to be queried when looking up the Bill To, Deliver, and Supplier addresses.
Header Text: The text to be inserted here will be pulled from the Header Text in the purchase order.
Example: Text is pulled from the Header text with the green checkmark.
If the PO Form requires additional pages, then the header information should be duplicated on the subsequent pages.
Additional Fields :
Field Mapping for additional header fields that are not on the Standard SAP PO (MEDRUCK) Form . These fields can also be viewed on the PO Forms in the Attachments section.
PO Form Additional Fields
Field Name SAP Table/ Field Name
Payment Terms MEPO1226-ZTERM
Shipping Terms (incoterms1) MEPO1226-INCO1
Shipping Terms (incoterms 2) MEPO1226-INCO2
II. Item Level Information
The following fields will be on the PO form for the item-level:
- Item Number
- Material
- Material Description
- Unit (Unit of Measure)
- Quantity
- Date Reqd (MM/DD/YYYY)
- Unit Cost
- Amount
Each field will have an allotted amount of characters, so that all the text can fit on the line-item. Using .5 inch margins with times new roman 10pt font; there are 105 possible characters in microsoft word for the line-item details to fit on the line. The fields are broken down as follows with their allotted characters to accommodate the 105 allowed spaces:
Characters:
Item Number: 1-3
Material: 6-18
Descriptoin: 6-36
Unit: 39-49
Quantity: 44-56
Date Required: 60-69
Unit Cost: 77-86 (Commas and Delimals will be included in the Price. Two total decimal Spaces)
Amount: 92-103 (Commas and Delimals will be included in the Price. Two total decimal Spaces)
The Numbering Ranges above can be viewed below line-item 040 in the PO Form Outline (Sinlge Page) document in the Attachments section.
Note: These number ranges are shown as an example of what the form should like. They do not have to match up identicle to the specifications listed above.
Additional Notes for Line-Item Fields:
- Material Description will be displayed directly below the Material on the next line.
- Item Text: The Item text will be displayed if there are any item texts from the Purchase order. The text will be displayed two lines below the Material description. So there will be one line without any text. Also, the next line-item on the PO form will be displayed two lines below the item-level text; so there will be only one line with no text between the line-item with text and the subsequent line-item. Line items 020 and 030 depict this in the PO Form Outline_v1 document in the attachments section. The Line Item text will come from the Material PO text (identified below with a green checkmark) from the line-item on the purchase order as shown below.
- The Date Required Format will be MM/DD/YYYY.
- For every item in the purchase order, the program should loop through each item and check to see if the returns item box is checked (MEPO1211-RETPO). If this box is flagged on the purchase order, then the purchase order form needs to be updated with a return indicator. This indicator can be viewed on line-item 030 of the attached word document PO Form Outline (Single Page) in the Attachments section.
- The line-item fields should have the following alignment:
Material: Left
Material Description: Left
Unit: Left
Qty.: Right
Date Required: Left
Unit Cost: Right
Amount: Right
- If the line-items do not fit on one page, then they should continue on to subsequent pages. The Header information should be copied to all the subsequent pages and the authorization section will be displayed on the last page as well as the total amount and currency. This example can be viewed in document PO Form Outline (Multiple Pages) in the Attachments section.
Dislclaimer:
A disclaimer will also be included in this section and after all the line-items. The disclaimer text is still pending. An example of a disclaimer is shown in the PO Form Outline (Single Page) after line-item 040. This document can be found in the Attachments section.
If a PO requires multple pages, the the disclaimer will be displayed on the last page after the last line-item.
III. Authorization Information
This section will contain the purchasing agent: The purchasing agent will be the person who created the purchase order. This section will also contain their telephone number and email address.
The first and last name of the person who created the purchase order should be displayed here. This can be looked up in the users profile. The user profile will also contain their email and telephone number.
The field names for can be viewed below or in the PO Form Outline (Single Page) document in the Attachments section.
PO Form Additional Fields
Field Name SAP Table/ Field Name
First Name ADDR3_DATA-NAME_FIRST
Last Name ADDR3_DATA-NAME_LAST
Telephone Number SZA5_D0700-TEL_NUMBER
Email SZA5_D0700-SMTP_ADDR`
Attachments:
3.5 Special Requirements Processing:
Describe the processing required to support any special requirements (e.g. signatures, logos, OCR, bar coding etc.).
3.6 How to execute the form:
Describe how to trigger the form e.g. Standard SAP transaction code or custom transaction code etc. If standard SAP transaction code describe the menu path
The form needs to be able to be viewed and printed.
To View:
Transaction ME22N or ME23N; Then Click the Print Preview icon to view the Form.
To Print:
1) Transaction ME22N.
2) Click Messages
3) Select Output NEU and medium 1 Print output
4) Click the Further data button as shown in the screen shot above
5) Select 4 Send immediately (when saving the application)
6) Click Back then Click Save
7) Select LOCAL for logical Destination
8) Click Save again
4 Unit Test Plan Section
4.1 Functional Unit Test Plan:
Document the criteria to be used for validating programming accuracy and positive/ negative results
Step Scenario Expected Results
Number Description of what is being tested in this step Description of what is expected to happen in this step
1 Go to Transaction ME22N and Display PO Form by clicking the Print Preview Icon Form should mirror the forms in the Attachments section.
2 Go to Transaction ME22N and Print PO Form PO Form should print as showed in the Print Preview Screen and the forms the Attachments section.
3 Create PO that will force PO form to cross multiple pages and then click Print Preview PO Form should have Header information on all pages and line-item shoulds continue on to the subsequent pages. Authorization, Total Amount, Currency, and Disclaimer will be on the last page. The page numbers should also be correct and in the right format. This should mirror the PO Form Outline (Multiple Pages) document in the Attachments section.
4 Go to Transaction ME22N and print PO as in step 3 PO Form shoul print as showed in the Print Preview Screen and the PO Form Outline (Multiple Pages) document in the Attachments section.
5 User Guide Requirements
A User Guide must be provided to assist the person responsible for running the program(s). The User Guide must be in cookbook-style (required elements with step by step instructions) and annotated screen prints. The User Guide will be required in the running of the object in the Production environment as well as the QA and Test environments.
5.1 User guide Requirements:
N/A
6 Appendix
6.1 Appendix:
N/A
Hope it will help ..
Regards,
Arjun.
Reward the points if it hepls

Caling smart form from module pool

Hi,
i want to call smartform from module pool screen when click on some pushbutton.
ex i want to call smart form of sales order by passing perticular S.O number from module pool screen.
plz help me o get this.
thanks.

Hi,
Enable hotspot option in the field catalog for the .SO.NUMBER field. On clicking on SO.Number
get the cursor field value and call the smart form in the PAI (ie., in user_command module).
Probably pick ucomm triggers with hotspot.
Venkat.

Cash book printout - forms & function module

Hi SAP Gurus,
Please provide me for cash book the function modules involved and standard sap forms for printout in the following-
1. cash receipt tab
2. cash payment tab
3. check receipt
4. check issued
I want to attach my own form for this functions.
THANKS

Hi....
go to FBCJ transaction and check for output type. then got to NACE and find out what are the forms assigned or go to NAST table find entries based on output type. there u can find form and program name.
Regards,
KP.

E-recruitment 6.0 - Smart Form - Text Module - Qualifying Event

Hi all,
Once more a question:
E-recruitment 6.0
Smartforms with invitation letters (for example for an interview)
In the recruiter's portal we use a 'qualifying event' to 'set' an appointment' , date, time, place etc.
We use the input from this reference activity in the text module of the smartform.
The text module holds the main text of the letter.
The text from the module appears in the recruiters portal when the recruiter performs activity 'send letter' (act. type: invitation) so that he can add some text manually if he likes.
This functionality is in E-R6.0 since SP7
It goes well when the recruiter does not add anything manually. The variables load in the smartform and it works as wel wanted.
BUT when the recruiter manually changes the letter (the text module) in the recruiters portal, all variable are lost from the letter.
I hope someone can help me out.
Edited by: N. Lodewijk on Dec 4, 2008 11:57 AM

You need to use the functionality "Changeable letter".

Call Pop-up screen with I/O fields form function module.

Hello experts,
I have a Zfunction module with input paramteres i_matnr, i_posnr and i_kwmeng.
My requirement is to call a pop-up screen with following fields.
Material - Inputbox for material (Read Only) " v_matnr
Item     - Inputbox for Item (Read Only)      " v_posnr
Quantity - Inputbox for Qty (Read Only)       " v_kwmwng
Price    - Inputbox for Qty (Change only)     " v_price
Submit button.
I created function ZSD_MAT_DATA.
Added statement CALL SCREEN 0005
In PBO_0005, (include Prog)
v_matnr = i_matnr
v_posnr = i_posnr
v_kwmeng = i_kwmeng
1. But it gives me error for not declaration i_matnr. What I am missing here?
2. Is there anything to make window as pop-up with some specific size?
Regards,
RH

Hi,
You can use the stanadard FM K_KKB_POPUP_RADIO3
else like same you can craete a new function accordind to your requirement.
Hope it helps you.
Reagrds
Arbind

Smart form Text module translation and Standard text

Hi i have a requirement in smartforms in which i need to create text modules and transtale into diffrent languages.
I have created text modules they are in my transport,
when i am translating through SE63 into target language it is not asking for any transport request , Can any one help me regarding how i can assign Transaltion thing to my transport.
Another thing is i require to use standard text, i am not much aware of it also as per my understanding i need to create it through SO10 Transaction , and i can use it in include text please correct me if i am wrong, i need this standart text also in two language but while creating standard text it is not asking transport request, and how i would convert standard text in diff lang and how can i assign to my transport.
Surely i would provide points for the valid reply.
Thanks in advance.

Hi Gudia San,
To transport Standard text, use the standard Report Program RSTXTRAN, execute it, on the selection screen, enter your standard text name as
Text key - name, press F8, it will display a ouput list. Now press F5 key and it will ask for transport request number.
Regards,
Abdul.
P.S: Rewards points, if useful!

Smart form function module

Similar Messages

Maybe you are looking for