Scribd Logo
Upload

Welcome to Scribd!

  • 53 views

    Dealer Management System (Field Details) : Ref of Design Doc # Applications Groups

    Uploaded by

    sumit chauhan
    This document outlines the fields and functional logic for a dealer management system. It includes 25 sections covering details like the dealer's profile, orders, accounts, payments, schemes, return orders, product catalog, compliance documents, announcements, and alerts. Each section lists the relevant fields and provides information on how the data will be retrieved and calculated from the backend Z system.

    Copyright:

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

    Dealer Management System (Field Details) : Ref of Design Doc # Applications Groups

    Uploaded by

    sumit chauhan
    53 views27 pages
    This document outlines the fields and functional logic for a dealer management system. It includes 25 sections covering details like the dealer's profile, orders, accounts, payments, schemes, return orders, product catalog, compliance documents, announcements, and alerts. Each section lists the relevant fields and provides information on how the data will be retrieved and calculated from the backend Z system.

    Original Description:

    Field Details_Apps_

    Original Title

    Field Details_Apps_

    Copyright

    © © All Rights Reserved

    Available Formats

    XLSX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document outlines the fields and functional logic for a dealer management system. It includes 25 sections covering details like the dealer's profile, orders, accounts, payments, schemes, return orders, product catalog, compliance documents, announcements, and alerts. Each section lists the relevant fields and provides information on how the data will be retrieved and calculated from the backend Z system.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd
    Download as xlsx, pdf, or txt
    53 views27 pages

    Dealer Management System (Field Details) : Ref of Design Doc # Applications Groups

    Uploaded by

    sumit chauhan
    This document outlines the fields and functional logic for a dealer management system. It includes 25 sections covering details like the dealer's profile, orders, accounts, payments, schemes, return orders, product catalog, compliance documents, announcements, and alerts. Each section lists the relevant fields and provides information on how the data will be retrieved and calculated from the backend Z system.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd
    Download as xlsx, pdf, or txt
    of 27

    Dealer Management System

    (Field Details)
    Ref of Design Doc
    # Applications Groups
    5.1 My Details My Profile
    5.2 1 My Details My Crompton Buddy
    5.3 My Details My Service Request
    5.4 My Orders Create Purchase Order
    5.5 My Orders Check Purchase Order Status
    2
    5.6 My Orders Check Dispatch Details
    5.7 My Orders Check Sales Order Status
    5.9 3 My Accounts C-Forms
    5.10 My Payments Cash Discount Amount
    5.11 My Payments Outstanding and Overdue Amount
    4
    5.12 My Payments Payment Gateway
    5.13 My Payments Outstanding and Overdue Amount – Retailers
    5.15 5 My Schemes Schemes Settled
    5.16 My MOU MOU Achievement – MTD
    6
    5.17 My MOU MOU Achievement – YTD
    5.18 Defective returns Return Order Create
    7
    5.19 Defective returns Return Order Status
    5.20 Product Catalogue Product Catalogue and Price List
    5.21 8 Product Catalogue User Guides / Videos
    5.22 Product Catalogue TV Commercials
    5.23 Compliance Balance Confirmation
    9
    5.24 Compliance My Annual Documents
    5.25 10 Company Announcements Company Announcements
    5.26 11 Alerts & Notifications Alerts & Notifications
    Groups Field Name Mandatory Data Type Length Drop Down help
    My Profile

    My Crompton Buddy

    My Service Request
    Functional Logic (mention if this is being picked from Z logic) Back to list
    Groups Input/Output Field Name
    Create Purchase Order Output Order No.

    Input/Output Ship to Party

    Input/Output Req.Shipping date

    Output Total Order Value


    Input/Output Item No.
    Input/Output Material
    Output Material descripition
    Input/Output Quantity

    Output Price(Per Unit)


    Output Item Value

    Output ATS
    Output Open Order Qty
    Output Schedule Item
    Output Schedule Qty
    Output ATS
    Check Purchase Order Status Created Status

    Blocked/Released Status

    Stock Allocated
    Invoiced

    Check Dispatch Details

    Check Sales Order Status


    Functional Logic (mention if this is being picked from Z logic) Back to list

    - Logic while creation of Sales order:


    Pass sold to party to FM - CUSTOMER_PARTNERFS_GET
    pick all value of PARVW = SH and show code, show Name1 and
    Name 2 (pass SH code in KNA1 and pick Name1 and Name 2) with
    region description (Pick KNA1-REGI & KNA1-LAND1), and pass to
    T005U with SPRAS = EN and LAND1 that is picked from KNA1). Pick
    BEZEI.
    - for reports: Pass sales order number in VKPA-VBELN and pick all
    values with partner function (PARVW) = SH
    name1 and name 2 logic will remain same as above point.

    - Creation of Sales Order:


    Delivery date will be either entered manually by user or system will
    automatically determine.
    - for Reports
    the confirmation from client is awaited. (if the delivery date of a
    sales order will remain same and hence it will be of header or will it
    be at item level?)
    at item level
    pass - sales order number in VBEP-VBELN and POSNR of the sales
    order line item and pick date - VBEP-EDATU with respective BMENG
    (quantity) with VRKME.
    ( now one line item of sales order can have multiple delivery dates
    based on the availability of material. I am posting this query to
    client).
    (Shivani- it will be at header level)

    for report -
    Addition of A & B
    A- Net Value- NETWR (header level - VBAK-NETWR)
    B- Tax - MWSBP (sum up for all line items - VBAP-MWSBP)
    it is POSNR of VBAP (Sales order)
    VBAP-MATNR
    VBAP-ARKTX
    VBAP-KWMENG
    posted query to client. Need confirmation on list of condition types
    to consider to calculate the price per unit.
    VBAP-NETWR
    I have posted to client to get confirmation on ATS date, if this is
    schedule delivery date.
    standard VA05N report is available
    What is required in this
    how it is different from order quantity. Logic can be provided acordingly.
    to understand ATS, query is posted to client.
    Pass order number in VBAP_-VBELN and pick VBAP-GBSTK (order
    overall status) of each line item. Based on value listed below, display
    the descritpion of the POSNR and MATNR of sales order)
    blank- Created
    A Not yet processed
    B Partially processed
    C Completely processed

    Queries_Crompton, point number 24 - In the report, show YES or NO


    for SO block at header / line item level. No need to specific the type
    of block in the report.
    Thus functioal logic:
    Blocking status:
    if any of the below condition is true:

    1) Reason for rejection ( VBAP-ABGRU) - is not blank for the item


    (Pass order number in VBAP-VBELN)
    (Status- Reason to display -ABGRU in TVAGT, pass SPRAS= EN and
    display - BEZEI)

    2) Delivery Block - (VBEP-LIFSP) if not blank for any of the schedule


    line of line item (Pass order number in VBEP-VBELN)
    (Status- Reason to display - pass LIFSP in TVLST with SPRAS=EN and
    pick VTEXT)

    3) Billing Block (VBAP-FAKSP) - if not blank for the item


    (Status- Reason to display - Pass FAKSP in TVFST with SPRAS=EN and
    pick VTEXT)

    THEN
    for report - 'YES'
    for status- 'Blocked'
    ELSE
    for report - 'NO'
    for Status - 'Not Blocked'

    ATS - field to be developed by Crompton and still they need to


    comeback on this by 17 sep to handle multiple schedule line.
    pass Order number (VBAP-VBELN) in VBFA-VBELV (Prceeding doc)
    and VBAP-POSNR in VBFA-POSNV
    and VBFA-VBTYP_N (Subsequent category) = J and then PICK
    all subitem (VBFA-POSNN) and respective and VBFA-VBELN (follow
    on document)

    pass VBFA-POSNN in LIPS-PSNR and VBFA-VBELN in LIPS-VBELN


    (delivery document)
    check all LIPS-LFIMG (delivery quantity) and add them and display in
    status with LIPS-MEINS (quantity)

    Also check billing status (LIPS-FKSTA) whereever LIPS-MENS is NOT


    equal to ZERO. and display as
    if FKSTA is equal to
    1) A- then display - Not yet processed
    2) B -then display - Partially processed
    3) C - then display - Completely processed
    Groups Field Name Mandatory Data Type Length Drop Down help

    Transporter
    name
    Functional Logic (mention if this is being picked from Z logic) Back to list

    pass sales order number in VBFA-VBELV, and subsequent item


    category - VBFA-VBTYP_N = J and pick the value VBELN (delivery
    document number). Pass this delivery number in VBFA-VBELV and
    VBFA-VBTYP_N=8 and pick follow on document - VBFA-VBELN. This
    will be shipment document number. Pass this shipment document
    number in VTTK-TKNUM and pick Service Agent VBFA-TDLNR. Pass
    this service agent code in LIFA1-LIFNR and display Name1 and
    Name2
    Groups Field Name Mandatory Data Type Length
    Cash Discount Amount

    Outstanding and Overdue Amount

    Payment Gateway

    Outstanding and Overdue Amount – Retailers


    Drop Down help Functional Logic (mention if this is being picked from Z logic) Back to list
    Groups Field Name Mandatory Data Type Length Drop Down help
    Schemes Settled
    Functional Logic (mention if this is being picked from Z logic) Back to list
    Groups Field Name Mandatory Data Type Length Drop Down help
    MOU Achievement – MTD

    MOU Achievement – YTD


    Functional Logic (mention if this is being picked from Z logic) Back to list
    Groups Field Name Mandatory Data Type Length Drop Down help
    Return Order Create

    Return Order Status


    Functional Logic (mention if this is being picked from Z logic) Back to list
    Groups Field Name Mandatory Data Type Length Drop Down help
    Product Catalogue and Price List

    User Guides / Videos

    TV Commercials
    Functional Logic (mention if this is being picked from Z logic) Back to list
    Groups Field Name Mandatory Data Type Length Drop Down help
    Balance Confirmation

    My Annual Documents
    Functional Logic (mention if this is being picked from Z logic) Back to list
    Groups Field Name Mandatory Data Type Length Drop Down help
    Company Announcements
    Functional Logic (mention if this is being picked from Z logic) Back to list
    Groups Field Name Mandatory Data Type Length Drop Down help
    Alerts & Notifications
    Functional Logic (mention if this is being picked from Z logic) Back to list

    You might also like