New Sales Order Type

Hello,
I would like to ask either it is neccessary to have a new division for new sales order type.
Thanks for your time.
Your fruitful answer will help me to move one step forward
Sherry.

Hi,
If you created new division then you have to maintain sales area
IMG >> enterprise structure >> assignment >> SD >> assign division to sales organization and set up sales area
How is it possible for the Y109 to be assigned to the new division. How to make it default
Y109 is not assigned to division rather it can be assigned to sales area
IMG >> sd >> sales >> sales documents >> sales document header >> assign sales area to sales document type >> Assign sales order types permitted for sales areas
Kapil

Similar Messages

  • Regd creation of New Sales Order Type - Credit Memo Request

    Hello Gurus,
    I have created a New Sales Order Type as per the given requirements. This is a Credit Memo Request. I have done all that are needed from SD perspective.
    Can you please let me know what needs to be done from FI-CO perspective when a New Sales Order Type is created and this is a Credit Memo Request. If some one can let me know the customizations that needs to be done it will be very helpful for me.
    Thanks,
    SNK.

    Hi,
    As per my understanding, there is nothing to be required from FI-CO perspective, in case when you defined a document type in SD.
    During the sales order processing the SD-FI interface happenes for following activities
    1) Credit check (In case you use Credt management)
    2) Tax determination
    For more knowledge
    go through the link given below.
    http://www.sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm
    Hope it helps,
    Regards,
    MT

  • IMG Settings for creating a new sales order type

    Hello All,
    I seek you valuable inputs on the steps to follow in IMG(SPRO) setting to create a new sales order type in the system.
    I want to create a new sales order type for which i have done the following setting in IMG,
    1) Sales and Distribution->Sales->Sales Document Header->Define sales document type.
    2)  Sales and Distribution->Sales->sales Document Header->Assign Sales Area To Sales Document Types.
    3) Sales and Distribution->Sales->Sales Document Item->Define Items Categories
    4) Sales and Distribution->Sales->Sales Document Item->Assign Item categories
    5) Sales and Distribution->SalesàSchedule Lines->Assign Schedule lines Categories.
    Also created a new number range for the same.
    After this when i am trying to create a sales order with VA01 i get an error "Enter a Sales Area".
    what am i missing ?Please suggest.
    Thanks in advance,
    Swati

    Hello,
    In the Initial screen of VA01 you have to enter the sale area which is nothing but the combination of
    Sales organization
    Distribtion channgel
    Division
    And in the transaction code  OVAZ you should assign the sales document type for this sales area .
    Please revert if you need any frther clarification
    regards,
    santosh

  • Automatic Batch Determination is not happening for New Sales Order Type

    Dear Experts,
      I have created a new sales order type ZBPY - For Free Sales, but automatic batch detrmination and batch pick up is not happening for new sales order type,  but it is activated for all the other sales order types in Production Server, can any body let me know the steps how to map this new order type to batch management and let it behave like other order types.
    Thanks in Advance.
    Saravanan(EKS).

    Hi Saravanan,
    Kindly check the following steps for automatic batch determination.
    1. First check the material is maintained with batch in the warehouse management.
    2. Maintain new entry for search procedure for batch determination with the new created doc type.
    3. Maintain new entry for automatic batch determination for sales order or automatic batch determination for delivery ( This depends on the business process of our client, whether they want to determine the batch with sales order or at the delivery level. check this and make new entry)
    4. Create Batch using T.code MSC1N with proper date of manuf. and SLED.
    5. Create Batch Search Strategy using T.code VCH1 with proper strategy type.
    6. Maintain stock with active batch. check this with t.code LS26 or LS24.
    regards
    Ravishankar M

  • Can't specify the customer to use a new sales order type ,why?

    I created a new sales order type, finished the configeration.. but when I use it to create a order by t_code VA01 ,input the order type and sales area ,then enter, why the sold-to-party and ship-to-party are inmodifiable? i can't specify the customer... where is the problem?
    appreciate you help.thank you !

    Hi Sue,
             I think u havent did the Partner determination for that Sales document.  If you create ur own sales doc type in VOV8 ,new entries.
    U need to maintain the Partner determination for that sales doc type.
    this is the same,the way u maintaint the customer partner determination.
    If you dont maintain this , in VA01 screen, u cant able to enter Sold to & ship to parties as it will be in display mode. I think the same error ur getting know as per ur issue.
    This will def solve ur issue as i faced n overcome long back.
    *reward points ,if helpful

  • Should we create new sales order type for Brazil

    Hi,
    We are having SAP Global templete environment & going for Brazil rollout. My question is whether we can have exitsing sales order type or should we create a new one so as to capture complicated Nota fiscal requirements.
    What SAP recemmends
    Thanks
    Amb

    Most of the sales document types for Brazil are identified by BR in the description, for instance, sales document type ORB for Standard Order BR. This means a separate order type.
    [Country version Brazil exclusively deals with Nota Fiscais.|http://help.sap.com/erp2005_ehp_04/helpdata/EN/10/e0f0371bc15d73e10000009b38f8cf/content.htm]

  • What is the impact on MM if assign new sales org to sales order type?

    hi expert!
    need to ask you guys, what is the setting need to be done if on sales side they want to assign a new sales org,distribution channel and division to sales order type for drop shipment process? Do we only need to make sure that purchase org has been assigned to company code of the sales area?
    Thanks.

    Sales Organisation has to be assigned to a company code & Sales view of the material has to extended to this new sales organisation using T code MM01.
    Regards
    Bhavesh Mistry

  • After creating new sales order through BAPI, it is not showing in VA03

    Hi Experts
    I am developing one program to create sales order using FM BAPI_SALESORDER_CREATEFROMDAT2. In output screen it is showing that the new sales order number created with new sales order number. But whenever I want to display the newly created sales order via VA03 it shows an error message SD document 10007547 is not in the database or has been archived but in program output it shows that 10007547 is created. This is in DEV server. Document numbers are generated by the system sequencially, but it is not reflected in database.
    I am also attaching my code below.
    REPORT  z_bapi_salesorder.
    DATA : gt_header LIKE bapisdhd1,
           gt_item TYPE TABLE OF bapisditm,
           gt_itemx TYPE TABLE OF bapisditmx,
           gt_partner TYPE TABLE OF bapiparnr,
           gt_return TYPE TABLE OF bapiret2.
    DATA : gs_item LIKE LINE OF gt_item,
           gs_itemx LIKE LINE OF gt_itemx,
           gs_partner LIKE LINE OF gt_partner,
           gs_return LIKE LINE OF gt_return.
    DATA : v_vbeln TYPE vbeln_va.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(30) ord_type FOR FIELD p_auart.
    PARAMETERS : p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN SKIP 1.
    SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    PARAMETERS       : p_vkorg TYPE vkorg OBLIGATORY,
                       p_vtweg TYPE vtweg OBLIGATORY,
                       p_spart TYPE vbak-spart OBLIGATORY,
                       p_sold TYPE kunnr OBLIGATORY,
                       p_ship TYPE kunnr OBLIGATORY,
                       p_matnr TYPE matnr OBLIGATORY,
                       p_menge TYPE kwmeng OBLIGATORY,
                       p_plant TYPE werks_d OBLIGATORY.
    SELECTION-SCREEN : END OF BLOCK b1.
    INITIALIZATION.
      ord_type = 'Order Type'.
    START-OF-SELECTION.
    *Header information data.
      gt_header-doc_type = p_auart.
      gt_header-sales_org = p_vkorg.
      gt_header-distr_chan = p_vtweg.
      gt_header-division = p_spart.
    *Partner information data.
      gs_partner-partn_role = 'AG'.
      gs_partner-partn_numb = p_sold.
      APPEND gs_partner TO gt_partner.
      CLEAR gs_partner.
      gs_partner-partn_role = 'WE'.
      gs_partner-partn_numb = p_ship.
      APPEND gs_partner TO gt_partner.
      CLEAR gs_partner.
    *Item data
      gs_item-itm_number = '000010'.
      gs_itemx-itm_number = 'X'.
      gs_item-material = p_matnr.
      gs_itemx-material = 'X'.
      gs_item-plant = p_plant.
      gs_itemx-plant = 'X'.
      gs_item-target_qty = p_menge.
      gs_itemx-target_qty = 0.
      APPEND gs_item TO gt_item.
      APPEND gs_itemx TO gt_itemx.
      CLEAR : gs_item, gs_itemx.
      CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
        EXPORTING
      SALESDOCUMENTIN               =
          order_header_in               = gt_header
      ORDER_HEADER_INX              =
      SENDER                        =
      BINARY_RELATIONSHIPTYPE       =
      INT_NUMBER_ASSIGNMENT         =
      BEHAVE_WHEN_ERROR             =
      LOGIC_SWITCH                  =
      TESTRUN                       =
      CONVERT                       = ' '
       IMPORTING
         salesdocument                = v_vbeln
        TABLES
         return                       = gt_return
         order_items_in               = gt_item
         order_items_inx              = gt_itemx
         order_partners               = gt_partner
      ORDER_SCHEDULES_IN            =
      ORDER_SCHEDULES_INX           =
      ORDER_CONDITIONS_IN           =
      ORDER_CONDITIONS_INX          =
      ORDER_CFGS_REF                =
      ORDER_CFGS_INST               =
      ORDER_CFGS_PART_OF            =
      ORDER_CFGS_VALUE              =
      ORDER_CFGS_BLOB               =
      ORDER_CFGS_VK                 =
      ORDER_CFGS_REFINST            =
      ORDER_CCARD                   =
      ORDER_TEXT                    =
      ORDER_KEYS                    =
      EXTENSIONIN                   =
      PARTNERADDRESSES              =
      IF v_vbeln <> space.
        COMMIT WORK.
        WRITE :/ 'Document', v_vbeln ,'created'.
        CLEAR : v_vbeln, gt_header.
        REFRESH : gt_partner, gt_item, gt_itemx.
      ELSE.
        WRITE :/ 'Error in creating document'.
      ENDIF.
    Please give the possible solutions for this. What is reason for that update termination.

    CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
        EXPORTING
          ORDER_HEADER_IN           = ORDER_HEADER_IN
      WITHOUT_COMMIT            = ' '
      CONVERT_PARVW_AUART       = ' '
       IMPORTING
         SALESDOCUMENT             = SALESDOCUMENT
      SOLD_TO_PARTY             =
      SHIP_TO_PARTY             =
      BILLING_PARTY             =
         RETURN                    = RETURN
        TABLES
          ORDER_ITEMS_IN            = ORDER_ITEMS_IN
          ORDER_PARTNERS            = ORDER_PARTNERS
      ORDER_ITEMS_OUT           =
      ORDER_CFGS_REF            =
      ORDER_CFGS_INST           =
      ORDER_CFGS_PART_OF        =
      ORDER_CFGS_VALUE          =
      ORDER_CCARD               =
      ORDER_CFGS_BLOB           =
         ORDER_SCHEDULE_EX         = ORDER_SCHEDULE_EX
    use bapi_transaction_commit.
    Regards,
    Venkat

  • OURPUT TYPE FOR A SALES ORDER TYPE

    Hi,
    When i create a new sales order for the type SO, the system don't affect the output type to my order. I have to do it manualy.
    What's missing?
    In custo, I define the same output type of CS to the order type SO but is still not working.
    It's work perfectly for CS type order.
    Thanks for your quick answer.

    Hi,
    Please check whether you have maintained the condition record in VV11.
    Regards,
    Shekhar

  • Creation of new Sales order

    Hi,
           While creating a new Sales Order(tcode VA01) depending on the material, Item category will be generated and depending on the Item category purchase requisition screen(ME51n) will be automatically opened and PR will be created.
    Now to automate this process, BAPI_SALESORDER_CREATEFROMDAT1 will be called to create the sales order. But the requirement is that we need to pass Requisitioner and Vendor to the BAPI for creation of PR.
    But in this BAPI there is no option/field to pass Requisitioner and Vendor. So is there any other BAPI/Function Module where a new Sales order is created and also we can pass Requisitioner and Vendor required for creation of new PR.

    REPORT  ZSALESORDER.
    Parameters
    Sales document type
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
    PARAMETERS: p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Sales organization
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
    PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Distribution channel
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
    PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Division.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
    PARAMETERS: p_spart TYPE spart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Sold-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
    PARAMETERS: p_sold  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Ship-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
    PARAMETERS: p_ship  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Material
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
    PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Quantity.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
    PARAMETERS: p_menge TYPE kwmeng  OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Plant
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
    PARAMETERS: p_plant TYPE werks_d .
    SELECTION-SCREEN END OF LINE.
    Complete Deliver
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
    PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
    SELECTION-SCREEN END OF LINE.
    Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                             WITH HEADER LINE.
    DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                             WITH HEADER LINE.
    Initialization.
    INITIALIZATION.
    v_text   = 'Order type'.
    v_text1  = 'Sales Org'.
    v_text2  = 'Distribution channel'.
    v_text3  = 'Division'.
    v_text4  = 'Sold-to'.
    v_text5  = 'Ship-to'.
    v_text6  = 'Material'.
    v_text7  = 'Quantity'.
    v_text9  = 'Plant'.
    v_text10 = 'Complete delivery'.
    Start-of-selection.
    START-OF-SELECTION.
    Header data
    Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    *Complete delivery
        header-COMPL_DLV = p_autlf.
        header-COMPL_DLV = 'X'.
    Partner data
    Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    Ship to
      partner-partn_role = 'WE'.
      partner-partn_numb = p_ship.
      APPEND partner.
    ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
    item category
      itemx-ITEM_CATEG = 'X'.
      APPEND item.
      APPEND itemx.
      ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000020'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000020'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000020'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
    Call the BAPI to create the sales order.
      CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
           EXPORTING
                sales_header_in     = header
                sales_header_inx    = headerx
           IMPORTING
                salesdocument_ex    = v_vbeln
           TABLES
                return              = return
                sales_items_in      = item
                sales_items_inx     = itemx
                sales_schedules_in  = lt_schedules_in
                sales_schedules_inx = lt_schedules_inx
                sales_partners      = partner.
    Check the return table.
      LOOP AT return WHERE type = 'E' OR type = 'A'.
        EXIT.
      ENDLOOP.
      IF sy-subrc = 0.
        WRITE: / 'Error in creating document'.
      ELSE.
    Commit the work.
        COMMIT WORK AND WAIT.
        WRITE: / 'Document ', v_vbeln, ' created'.
      ENDIF.

  • How to configured pricing procedure to sales order type

    Dear Sir,
    Please tale me how to configure / change pricing procedure to sales order type. we have required to change pricing procedure from a to b for particular sales document type.
    Regards
    BK GAIKWAD

    HI
    Create a new document pricing pricedure
    SPRO>sales & distribution>basic functions>Pricing>Pricing Control-->Define And Assign Pricing Procedures
    and in the same path assign to your document
    and assign it to your document and also then to your Pricing procedure determination in OVKK
    regards
    Prashanth
    Edited by: Prashanth@SD on Jan 29, 2011 11:00 AM

  • Suppresing Delivery note prints for certain sales order types/item category

    Hi
    I need to find a way of suppressing some delivery notes from being printed.
    Relating to orders for consignment fill up and consignment issue.
    The delivery notes are needed to be printed for 'Consignment fill up order' type, BUT not for Consignment issue - as this is confusing some of the warehouse staff at month end.
    All have the same delivery type, the only difference i can see is the item category types are different
    Is there a way i can use the sales order type, with customer number as an access sequence for the Output type ?
    -  Or the Item category type ?
    Is it possible to add sales order type or Item category into the FIELD CATALOG :- output for deliveries
    Your help would be much appreciated
    Cheers
    Tony

    Hi,
    I can suggest you something, but do remember that I've never done such kind of thing till date.
    >> Copy LF and create new delivery type
    >> Assign this to your consignment doc. types
    >> Kindly remove the Header output determination procedure assigned to this new delivery type
    >> Then assign output det. procedure at Item level {according to Item category}
    >> Then check if will cater to your requirment or not.
    Please keep one thing in mind that I am giving you a proposal by thinking in one logical way and I can't confirm the practicality of the proposal.
    Hrishi

  • In ASCP Workbench - Need to take action against sales order types

    Hi Team,
    I am facing one issue, In ASCP workbench, when we query an item with conditions Order type=Sales Order, I can see many rows with Action=Release, Action=None.
    Some rows with Action=None is in pink colour (without taking action against this in ASCP WB) and some in black colour.
    For rows with Action = Release, We can check the Release check box and can modify the "Implement date" field, Save and Release (Tools-->Release). Then we can see the changes in Schedule ship date field in Sales Order line (Source Instance)
    But for Action=None, We can't check the Release check box (But User want to implement New date for this also)
    Since this is linked with OM, I am in a position to solve the issues urgently based on the below questions.
    1. Which one triggers the Action=Release or None
    2. What modification needs to change in SO line (Source instance) to know the changes in Action column in ASCP WB.
    3. User needs to implement new dates for the items having Action=None also. For this how can override or any workaround is there?
    Note: For the items having same Old due dates and
    Please suggest me ASAP.
    Thanks and Regards,
    Ramesh

    Dear Ramesh
    Ones in Pink - Your plan is ATP enabled plan. So if there is a new sales order entered in OM module there is a sales order entry made in the ATP table the moment its scheduled in source. But since ASCP has nt been run yet they are still showing actiona s none in the plan.
    W r t one with action release your understanding of ship date updation through ascp release is correct.
    Why does customer want to chnage date on other sales orders (action-none) ? . ASCP has planned and it is saying that such is the date of expected shipment and so action is none. Any business reason why a date change and release is required on action none sales orders? By default behaviour action None cant be released to source .
    Best Regards
    Partha

  • Unable to copy line item from Sales Order [ZPLV] to new Sales Order [ZPCV]

    I have here a requirement to create a new Sales Order[ZPCV] with reference to the previously created SO[ZPLV].
    I looked in transaction code VTAA, and the configuration for the aboves condition is:
    target sales doc type - ZCPV   from sales doc type - ZPLV
    dataT: 302, 907 and 001 respectively
    copying requirement: 001
    copy item number is checked
    complete reference is checked
    is there something wrong with the configuration?
    please advice!
    thanks,

    Hi
    For those line items you can assign a REASON FOR REJECTION. Automatically the status of those line items will be closed.
    Thanks,
    Ravi
    PS : sorry....please ignore my post.
    Edited by: sankar ravi on May 20, 2008 3:45 PM

  • Add fields to transaction VOV8  - Sales Order types maintaines

    Hi,
    I want to know if it is possible to add new fields to view V_TVAK (threw table TVAK), and then add them also to the view in transaction VOV8  for a sales order type.
    Thanks naama.

    Hi Nilmini,
    In My case, I have added custom fields to MDC change screen by using /AFS/MDC_CHANGE_CUSTOM_FIELDS but its not appearing in Grid list display. Would like to appreciate if you can Help me to achieve this.
    Regards,
    Jelli

Maybe you are looking for