Delivery Address..in smart form

Hi ,
I need Delivery address to be printed with logic 
If adrnr is maintained for any 1 line item for the given ebeln then use that adrnr to fetch the address from adrc table else get the plant address
To get the plant address
L_EKKO-RESWK = P_WERKS.
L_EKKO-BSAKZ = 'T'.
CALL FUNCTION 'MM_ADDRESS_GET'
      EXPORTING
           I_EKKO          = L_EKKO
      IMPORTING
           E_ADDRESS       = L_ADDRESS
           E_SADR          = P_SADR.
Please Guide me the logic .
Regards,
Neelima.

Hi,
If ADRNR is maintained for EBELN. Then write like this.
if not EKKO-ADRNR is initial.
select single * from adrc where ADDRNUMBER = EKKO-ADRNR.
Else.
select single * from T001W where werks = P_WERKS.
if sy-subrc is initial.
select single * from adrc where ADDRNUMBER = T001W-ADRNR.
endif.
endif.

Similar Messages

  • Delivery Output- 2 smart forms

    Hi Gurus,
    we are having a delivery out put 'ZDUR'.
    In delivery output configuration 2 programs and 2 smart forms have been assigne to this out put.
    but when i try to print the output iam getting only the layout of the second smartform.
    but i want the layout of the first smartform for the same output.
    could any one suggest on this.
    Srini

    Hi,
    It is not possible to give two program in NACE for Delivery Output. Why u want two programs. IF u want two programs and two smartforms for the same output type u need to Create one common prog and assign it in NACE and write the logic based on u r condition it will call either of the program.
    No Need to the SMARTFORM NAME in the NACE. IF u have given one smartform name and in the print program if u selected the ssecond smartform based on u r condition u will get the output with second smartform.
    If u have any problem revert back.
    Regards,
    Srinivas.

  • Delivery address in PO item level with no addressnr

    Hello,
    I have to print the delivery address in a form. This goes correct if the addrnumber is filled in the tab PO-item/delivery.
    However if this addressnumber is not filled it is not printed.
    Searching in adrc i have found the correct addressnumber (which is not shown in ME23N). But i cannot found the link between this po-item delvery address and this addressnumber.
    does anyone could me tell the link between this.

    In the received IT_EKPO table, look for address til found
    - ADRN2
    - ADRNR
    - If KUNNR is not initial, look for a customer address (select from KNA1)
    - If EMLIF is not initial, look for a vendor address (select from LFA1 or use FM VENDOR_MASTER_DATA_SELECT_00)
    - If WERKS is not initial, look for a plant address (FM MM_ADDRESS_GET)
    Look at the standard forms delvered by SAP (*) to get more information and coding samples)
    Regards,
    Raymond
    (*) You can also look at best practices forms for your country or industry

  • Smart Form problem with address layout

    Hello everyone,
    I need your help please for a smart form problem. We need the address layout for great britain with street1, street2 etc. but currently street2 is alligned before street1.
    We are using the FM ADDRESS_INTO_PRINTFORM (SAP standard address node) and according to the documenation the layout for GB is different as we see it currently.
    We have checked the sold-to and all contact persons, they have as country GB and language EN maintained.
    In customizing for address screen layout there is nothing chosen (tested to set up Europe, but did not change anything).
    For the customizing 'specify my countries...' we have maintained GB as country with the address layout key 006, vehicle country key GB and language key EN.
    For the described setting shouldn't there be designed the address in our smart forms according to 006? Anyhting in customizing we missed?
    Thanks a lot for your answers.
    Torsten

    Hi,
    Try to use line priority of FM, below is a brief of documentation. You can read it more in FM documentation:
    Control Parameters
    See also the parameter documentation.
    ADDRESS_TYPE - Address type (from 3.0C)
    There are three types of address:
    Address type '1': addresses of firms or organizations; the address
    structure which is used in most SAP applications as 'Address'.
    Address type '2': address of a person
    Address type '3': work address, usually the address of a contact person
    in a company
    The default value SPACE for the address type is handled like type '1',
    and is needed for the upwards-compatibility of the function module.
    Which parameters are used for which address type is explained in the
    ADDRESS_TYPE parameter documentation.
    The three character "address layout key" of the recipient country (LAND1) controls which of the available country-specific routines is used to format addresses for the country in question. This key is stored in field T005-ADDRS and is entered in Customizing under Global settings -> Set countries -> Define countries, on the detail screen under "Address layout key".
    Keys for customer routines in the SAP enhancement SZAD0001 can be
    maintained via the transaction SM30 (extended table maintenance),table
    name T005A, in the customer name range, and be assigned in country customizing.
    The address attributes are passed in the structures ADDRESS1 (type 1), ADDRESS2 (type 2), ADDRESS3 (type 3) or ADRSWA_IN (type SPACE).
    NUMBER_OF_LINES (ADRSWA_IN-ANZZL)
    The number of lines available for the address layout. If the number of
    lines is not sufficient for the complete layout of an address, then
    lines are consecutively suppressed according to the rules of the country in question. Use the parameter LINE_PRIORITY (ADRSWA_IN-PRIOR) overrules the standard sequence in which the output lines are to be suppressed.
    LINE_PRIORITY (ADRSWA_IN-PRIOR)
    If not equal to SPACE, this field overwrites the standard sequence in
    which the lines are suppressed if the available number of lines ANZZL is
    insufficient.
    The standard sequence is defined as follows:
    Type 1:   'AP43HRT7I86LC2BS5O'       (GB:  'APRT4327I86CBS5LO')
    Type 2:   'APHRT7I86LCBS5O'          (GB:  'PRT7I86CBS5LO')
    Type 3:   'APF43HR7I86TLC2BSND5O'    (GB:  'APRT4327I86CBS5LNDIO')
    where (if they occupy a line of their own):
    A = Title
    P = Mandatory empty line 1
    F = Function of the contact person in the company
    4 = Name 4
    3 = Name 3
    H = Different city
    R = Region
    T = District
    L = Name of country
    C = Postal code
    T = District
    7 = Street 3 (field STR_SUPPL2)
    I = Street 5 (field LOCATION)
    8 = Street 4 (field STR_SUPPL3)
    6 = Street 2 (field STR_SUPPL1)
    L = Country
    C = Postal code
    2 = Name 2
    B = PO Box
    S = Street or PO Box
    5 = c/o name
    N = Name (and title) of a person
    D = Department
    O = City
    Which of these attributes are available for maintenance can vary. All
    fields exist in Business Address Services.
    STREET_HAS_PRIORITY (ADRSWA_IN-WAREN)
    'X': Street has priority over PO Box (delivery address for example)
    ' ': PO Box has priority over street. This is the default value.
    regards,

  • One-Time Customer or Vendor Address Printing in Smart Forms

    Hi friends,
    I am using the Address Node in Smart Forms to print the Addresses in Tax Invoice Printing. How to get the address details for the One-Time Customers which is stored in the BSEC table using the same Address Function.
    (We can directly get the address details from BSEC and display it by using a separate Text Node. But the address formatting according to the recipient country postal standards will be handled only by Address Function in Smart Forms right)
    Regards,
    Riaz.

    Hi friends,
    I am using the Address Node in Smart Forms to print the Addresses in Tax Invoice Printing. How to get the address details for the One-Time Customers which is stored in the BSEC table using the same Address Function.
    (We can directly get the address details from BSEC and display it by using a separate Text Node. But the address formatting according to the recipient country postal standards will be handled only by Address Function in Smart Forms right)
    Regards,
    Riaz.

  • Delivery *** invoice smart form

    Dear experts,
    I have created a form for Delivery *** invoice.When I am running the smart form it generated the function module succesfully and after entering the out out device as LP01 and running it.It is giving the exception message as Reference field wa_header-brgew unknown in form.
    I have defined the brgew fiield in ty_vbrp.
    and assigned dat wa_header-brgew to header text.
    Can u suggest me what may be the problem?
    Regards,
    Farook.
    Edited by: farook shaik on Oct 16, 2008 9:54 AM

    Hi,
    Please debug the programe, Place break-point where brgew is filled.
    Regards
    Jana

  • Smart Form for Delivery Returns

    Hi guys
    I am in the process of defining a Smart Form as an output after doing a Goods Return in MIGO via a Delivery.
    And I am using the form ZSD_DELNOTE_SUPP in the transaction 'SAPSMARTFORMS'
    however, i am not able to determine which are the fields that would be relevant to defining this....
    I keep putting in and taking out fields, but I am still not able to generate an output
    Can anyone please shed some light on this
    Thank you
    Rukshana

    Hiya Andrew
    if you type in SMARTFORMS - it takes u to the form painter.
    I wish I could use a standard existing form but I dont knw any
    My requirement is
    When we do a MIGO for a Returns Delivery {A02 return Delivery -movement type 122} via a SD delivery document, we need to generate an output.
    My transactions would be - MIGO, then VL02n, then MB02 and I attach the output type to my material document;
    I do a get printout now, however its very basic and not what the users need.
    So I need to create a Smart form; My problem is that I did find a standard smart form for deliveries from SAP Help - ZSD_DELNOTE_SUPP but this holds only SD specific tables and fields
    My requirement includes MM specific stuff too - and thats where I am stuck
    Thanks for the support
    Rukshana

  • Smart form for outbound delivery

    Hi Can anybody tell me which smart form is used for outbound delivery also. Can some one tell me what is the process of taking out printout put of outbound deelivery what is the T code for that.
    Urgent help is required.
    Thanks,
    Lekhram

    Hi Lekhan,
    The answers given by the other two persons is right.
    If you want to take a output for a single document you have to take it from delivery change mode initial screen. click on menu outbound delivery, next issue output to, a pop up appears. Here system will show you the condition types available( if assigned). select the condition type you require and you can print it or you can have a preview.
    If you want to have output for several documents go to VL71 transaction code give the range of documents and have your output.
    You have lot of options for having an output from delivery be clear what is your requirement.
    If this message gives you the result don't forget to reward points.
    Thanks
    Venkat Cheeedalla

  • In Smart forms How to print address

    Hi all,
    If we have Multiple line items and if all the line items have the same address  then address should be printed at Header level if not all the line items are holding different address then that address should be printed at line item level.
    and again if the address is not displayed at Header level then that window should be hidden i.e the area should be hidden.
    Please help in this issue ASAP.
    Regards
    Anu

    Hi Anupama,
    You mean Delivery Address???
    1. Declare a Variable ADRNR in Import Parameters like ADRNR TYPE ADRNR.
    2. Have a seperate Window to display Address.
    3. Create a Address Node in that window, Give Address Number value as &ADRNR&.
    4. In the Conditions tab maintain as ADRNR <> space
    4. Get Data for ADRNR variable in Print Program and pass that value in Smartform Function Module for ADRNR Parameter.
    Reward Points if this helps,
    Satish

  • How to mention two different next pages in smart forms

    Hi
    In our scenario there is smart form in which we have one main window, after that we need to print two different pages one for instructions and other for delivery address.
    In main window we can add a command and mention the condition for a next page e.g Instructions page. but for  delivery address page we are unable to specify condition in main window or in secondary window  in instruction page/main page.
    Kindly help us
    Regards
    Ammad

    Hi Ammad,
    Create two pages(page2 and page3), page2 for printing the "Instructions" and second(page3) for "delivery address".
    in the first page, at the end of main window create the command and specify as below
    general attributes->check the go to new page check box->choose the page which u wanted to be print on the second(for your case it is page2).
    In the page2->general attributes->next page->give "page3".
    Thanks,
    Prabhakaran
    Edited by: prabakar1998 on Dec 12, 2011 9:42 AM
    Edited by: prabakar1998 on Dec 12, 2011 9:44 AM

  • How to creat 2nd page in smart forms

    hi
    in smart forms iam facing problem i'e if i gave 10 material's it was comming fine if i give 30 materials it was going to 2nd page in that again from starting it was comming like Header delivery adress.
    what i want is if materials increase than main window should increase size & rest of thing(footer )should comes in 2nd  window
    regards
    A K reddy

    Hi,
    For the header details not to print on the second page:
    -> Go to Conditions tab of the window in which u r printing Header  delivery address and check the condition 'Only on first Page'
    This will solve ur problem.
    thanks,
    Anon

  • Purchase Order Output delivery address

    Hi, All,
    I have issue on the delivery address in the Purchase Order. I need to a PO with multiple items, and each item there is different plant. In the item details, there is delivery address tab, showed up all plants address for each item.
    Then I need to print out the PO. But all the 'delivery to' address for each item is printed out.
    The issue is that I won't get that plant delivery address print out. I want to only 1 ship to address in this Purchase Order. This address maybe I can maintain manully somewhere? Or I need to setup somewhere?
    How to solve this issue?
    Thanks in advance

    Hi
    As has been suggested by Kl you can achieve that  by modifying your PO script or Smart form. Which one you are using? Please tel your ABAPer to hide the delivery addresses which you do not want to be pinted and tell him to bring the the delivery address in the output which you want to be printed. It should not  difficult at all for.
    Best regards

  • Functional specification and logic flow for smart form PO

    Dear Friends ,
    For PO develelpment in smart form as per client requirement which are the details we need to give for developers . I had given only table and fiels name for the displaying elements in PO , message type , document type . They are asking conditions also , is it this the job of functional consultant ? .
    If any one having sample FS for PO plaese send . Other than EKKO , EKPO which are the table are there for PO related...?
    RB

    Hi
    Based on your requiremnts you need to give the details of the fields
    First List down all the Required fileds to be in the layout like Vendor details, Plant details, delivery details, Material details, Conditions, Terms & conditions.
    Based on the above you can get the details from the tables used in PO creation.
    EKKO Purchasing Document Header
    EKPO Purchasing Document Item
    EKKI Purchasing Condition Index
    EKAN Vendor Address: Purchasing Document
    EKKN Account Assignment in Purchasing Document
    EKPA Partner Roles in Purchasing
    EKPB "Material Provided" Item in Purchasing Document
    EKPV Shipping Data For Stock Transfer of Purchasing Document Item
    KONV Conditions (Transaction Data)
    EREV Version in Purchasing
    MARA -
    MARC -
    These tables can be used based on your requiremnts
    Thanks & Regards
    Kishore

  • PO smart form help required

    Dear Friends ,
    For PO develelpment in smart form as per client requirement which are the details we need to give for developers . I had given only table and fiels name for the displaying elements in PO , message type , document type . They are asking conditions also , is it this the job of functional consultant ? .
    If any one having sample FS for PO plaese send . Other than EKKO , EKPO which are the table are there for PO related...?
    RB

    hi,
    find all tables in MM-PUR (Purchasing) :
    EBAN  - Purchase Requisition 
    EBKN  - Purchase Requisition Account Assignment 
    EBUB   - Index for Stock Transport Requisitions for Materi
    EINA    - Purchasing Info Record: General Data 
    EINE     - Purchasing Info Record: Purchasing Organization D
    EIPA     - Order Price History: Info Record 
    EKAB   - Release Documentation 
    EKAN   - Vendor Address: Purchasing Document 
    EKBE    - History per Purchasing Document 
    EKBEH - Removed PO History Records 
    EKBZ    - History per Purchasing Document: Delivery Costs 
    EKBZH  - History per Purchasing Document: Delivery Costs 
    EKEH    - Scheduling Agreement Release Documentation 
    EKEK    - Header Data for Scheduling Agreement Releases 
    EKES     - Vendor Confirmations 
    EKET     - Scheduling Agreement Schedule Lines 
    EKETH   - Scheduling Agreement Schedules: History Tables 
    EKKI      - Purchasing Condition Index 
    EKKN    - Account Assignment in Purchasing Document 
    EKKO    - Purchasing Document Header 
    EKPA     - Partner Roles in Purchasing 
    EKPB     - "Material Provided" Item in Purchasing Document 
    EKPO    - Purchasing Document Item 
    EKPV    - Shipping-Specific Data on Stock Tfr. for Purch. D 
    EKRS    - ERS Procedure: Goods (Merchandise) Movements to b 
    EKUB    - Index for Stock Transport Orders for Material 
    EORD    - Purchasing Source List 
    EQUK    - Quota File: Header 
    EQUP     - Quota File: Item 
    T024      - Purchasing Groups 
    T024E    - Purchasing Organizations 
    T024W   - Valid Purchasing Organizations for Plant 
    T024Z    - Purchasing Organizations 
    T027A    - Shipping Instructions, Purchasing

  • 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   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 &#61664; Materials Management &#61664; Purchasing &#61664; 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 Req’d (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.
    <b>Reward the points if it hepls</b>

Maybe you are looking for

  • After 10.5.1 update, Pages won't save

    After I installed Leopard, Pages would not save new documents or save new versions of existing documents. It would crash and leave a black outline of the Save window on the desktop, requiring me to Force Quit. I trashed the preferences and repaired p

  • BIT Locker Key is not working in a first attempt.

    I have enabled bit locker key for my system. when I restart the system it will ask for bit locker and like how many time I enter the password it won't work and says wrong key. My friend suggested a temporary solution which is working. I have remove k

  • Re: How do you create and use "common" type classes?

    Hi, You have 2 potential solutions in your case : 1- Sub-class TextNullable class of Framework and add your methods in the sub-class. This is the way Domain class work. Only Nullable classes are sub-classable. This is usefull for Data Dictionary. The

  • Copy Undeliverable Mail To / luser_relay no worky?

    Hi everyone, I know it's a despised feature, but I just need it working until I'm confident everything has been migrated well. I'm of course referring to "Copy Undeliverable Mail To:". When I first turned it on, and tested in, mail was still bouncing

  • ORA-31000 when register schema in oracle 10g

    I am trying to register a schema in oracle10g rel2. The schema contain "<xs:include schemaLocation="papiNetCommonDefsV2R31.xsd"/>" and papiNetCommonDefsV2R31.xsd is successfully registered in Oracle repository. But i am still getting the error as 1 b