Scribd Logo
Upload

Welcome to Scribd!

  • 363 views

    4 - FS - Purchase Order Amendment Print

    Uploaded by

    sachin
    The document provides a functional specification for developing an ABAP program to print purchase order amendments. It outlines objectives to print the amendment format provided after approval. It lists relevant transaction codes and fields to be captured from various tables for supplier details, PO information, existing and amended quantities, rates, and amounts. A pseudo code explains the logic to apply the client's provided format for all companies and materials. The technical specification section will be completed by the ABAP team to specify objects used and logic applied.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    4 - FS - Purchase Order Amendment Print

    Uploaded by

    sachin
    363 views4 pages
    The document provides a functional specification for developing an ABAP program to print purchase order amendments. It outlines objectives to print the amendment format provided after approval. It lists relevant transaction codes and fields to be captured from various tables for supplier details, PO information, existing and amended quantities, rates, and amounts. A pseudo code explains the logic to apply the client's provided format for all companies and materials. The technical specification section will be completed by the ABAP team to specify objects used and logic applied.

    Original Description:

    PO Print out

    Original Title

    4_FS_ Purchase Order amendment Print

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document provides a functional specification for developing an ABAP program to print purchase order amendments. It outlines objectives to print the amendment format provided after approval. It lists relevant transaction codes and fields to be captured from various tables for supplier details, PO information, existing and amended quantities, rates, and amounts. A pseudo code explains the logic to apply the client's provided format for all companies and materials. The technical specification section will be completed by the ABAP team to specify objects used and logic applied.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    363 views4 pages

    4 - FS - Purchase Order Amendment Print

    Uploaded by

    sachin
    The document provides a functional specification for developing an ABAP program to print purchase order amendments. It outlines objectives to print the amendment format provided after approval. It lists relevant transaction codes and fields to be captured from various tables for supplier details, PO information, existing and amended quantities, rates, and amounts. A pseudo code explains the logic to apply the client's provided format for all companies and materials. The technical specification section will be completed by the ABAP team to specify objects used and logic applied.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 4

    Project “UPMPL”

    _________________________________________________________________________

    Functional Specification for ABAP development

    Development Summary:

    Development ID To be filled by ABAP Team

    Author & Testing By

    Name of Development
    Purchase Order amendment Print
    (Short Description)

    Development Type Smartform

    Module/Business Process MM

    Required TCode NA

    Priority High

    Version History:

    Versio Date Change Revision Reason for Revision


    n No Updated Request Author
    No
    1.1
    1.2
    1.3

    Technical Summary:
    Name of Technical Consultant
    Request No MM_CLIENT_ABAP_DEV_MM--
    Start Date
    Completion Date
    Approval Date

    Functional Specification - NO Page 1 of 4


    Project “UPMPL”
    _________________________________________________________________________

    1. Functional Specification:
    1.1. Objective of Development
    To print the Purchase Order amendment as per the format provided after
    approval.

    1.2. Relevant Transaction Codes (Mandatory)

    Transaction Code Description


    ME21N, ME22N, ME23N Purchase Order Display

    1.3. Selection Parameters

    1.4.

    Field Name Table Name Description (M)andatory (P)arameter


    (O)ptional (S)elect Option
    NAME1 ADDR1_DATA Supplier Name M
    STR_SUPPL1 ADDR1_DATA Supplier Address M
    TEL_NUMBER SZA1_D0100 Telephone M
    Number
    SMTP_ADDR SZA1_D0100 Email M
    MOB_NUMBER SZA1_D0100 Mobile Number M
    EBELN MEPO_TOPLINE PO Number M
    VERKF MEPOCOMM Kindly Attention M
    BUKRS EKKO Plant M
    BEDAT MEPO_TOPLINE PO Date M
    MOB_NUMBER SZA1_D0100 Contact No M
    ANFNR MEPO1211 Your Ref. No M
    ANFDT RM06E Dated M
    EBELP EKPO SR NO M
    EMATN EKPO Item Code M
    TXZ01 MEPO1211 Item Description M
    MEINS MEPO1211 Order Unit M
    MENGE MEPO1211 Quantity M
    KBETR KOMV Rate (Rs.) M
    NETWR EKPO Amount(Rs.) M
    KWERT KOMV Sub Total M
    KBETR KOMV Condition Type M
    VTEXT T685T Condition M
    Description
    BUKRS EKKO Pl. Bill & deliver M
    to
    NAME1 WERKS Pl. Bill & deliver M
    to
    NAME_CO ADDR1_DATA Contact Person M
    TEL_NUMBER SZA1_D0100 Contact No M
    VALUE_OLD CDPOS Existing M
    Quantiry

    Functional Specification - NO Page 2 of 4


    Project “UPMPL”
    _________________________________________________________________________

    VALUE_OLD CDPOS Existing Rate M


    VALUE_OLD CDPOS Existing Amount M
    = Existing
    Quantiry *
    Existing Rate
    Existing Total = M
    Total of existing
    Amount
    Note: Parameter is single input and Selection option is range of input

    1.5. Enhancements / Interface details (for User-Exit / BADI / BAPI / BDC)

    Name Description
    NA

    1.6. Pre-requisite, if any

    1.7. Program Logic/Pseudo Code (with all possible scenario’s)

    Format provided by the client will be applicable for all the companies for Material
    Purchase Order Amendment.

    Detail of the logic is provided in the attached file. Attached file is the format
    provided by the client. How to capture these details in Smartform is mentioned in
    Callout Box and RED Colored text needs to be hardcoded.

    1.8. Report / Screen Layout

    1.9. Special Requirement

    1.10. Assumption/Note
    1.11. Authorization Requirement :-

    2. Technical Specification (By ABAP Team)

    Functional Specification - NO Page 3 of 4


    Project “UPMPL”
    _________________________________________________________________________

    2.1. Objects Used

    Logical Database

    Tables

    Secondary Indexes (if exist / created)

    Includes

    Function Modules / RFC

    BAPI / BDC Type

    Message Class

    Called Screens / TCode / Programs

    Implementation Name / Project (SAP


    enhancement)

    Package

    2.2. Logic Applied

    2.3. Assumption/Notes

    Functional Specification - NO Page 4 of 4

    You might also like