Creation of new distribution Channel

Can anyone give me a step by step process of creatinf a new distribution channel & assignment of the same.
Sumit Gulati

1. SPRO --> IMG --> Enterprise Structure --> Definition --> Sales and Distribution --> Define, copy, delete, check distribution channel
It is recommended to copy (copy as ) from existing Distribution Channel.
2. SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign distribution channel to sales organization
3. SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Set up sales area
4. SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign sales organization - distribution channel - plant
The above are settings for Distribution Channel at Enterprise Structure Level
Regards,
Rajesh Banka

Similar Messages

  • Adding new distribution channel

    Hi,
    I added a new distribution channel and added the relevant divisions,. Also set upd the sales areas. It picks correctly when trying to create the sales order.
    but when i try to create a material in this new sales area if t gives a error sayin invalid sales area in the material master creation.
    could there be any setting i could have missed? appreciate ur help on this.
    Thanks
    Keshini

    Dear Keshini,
    Please do the settings for common divisions and distribution channels through VOR1 and VOR2 transactions.
    Then try,
    I hope this will help you,
    Regards,
    Murali.

  • Using new Distribution Channel for dealers.

    Hi experts
    Currently Domestic sales is operating only on one channel  DD.
    Proposal is to set DR channels for all Dealers sales and DD will be used only for Retail Sales .
    DR Channel was previously configured but we were only using DD channel for both retailors & dealers sales.. all configuration is already done like sales area setup  and pricing etc. for DR channel
    so i would like to what are the pros and cons for using two Distribution channel and maintainence we require.
    thank  you

    You need to extend all customers and materials for new distribution channel.
    You also neeed to maintain prices for DD and DR channels separately.
    ITs advantage is this that your reporting will be separately executed. You can check how much sales you have done in retail and how much you have done in Whole sale.
    I dont know what kind of business your company is running. I suggest you to make a provision for 3rd distribution channel which is DC. B2B sales. corporate sales. May after some months or years your company feel need of it.
    For extending customers and materials 2 uploads will do this. Ask you ABAPER to create uploads.
    There must be separate distribution channels for corporate, retail, wholesale and Expots if your company is dealing with exports sale.
    Hope its clear to you now

  • New distribution channel

    can any one tell what are the customisation we need to do to create a new distribution channel
    i am asking baout the assignments to be done in SPRO
    THANKS

    Hi
    Define Distribution Channel
    In this step, you define the distribution channels in your company, adapting the functional scope of a distribution channel to your organization.
    Enterprise Structure -->Definition -->Sales and Distribution -->Define, copy, delete, check distribution channel
    On the Choose Activity dialog box, choose Define distribution channel.
       2.  On the Change View “Distribution Channels”: Overview screen, choose New Entries.
       3. Enter the following.
          Distr. Channel      Name
          01      Direct Sales
          02      Wholesale
          03      Intercompany
            11. Assign Distribution Channel to Sales Organization
    Use
    In this step, you allocate the distribution channels to a sales organization. In this case as many distribution channels as desired can belong to a sales organization. In addition, a distribution channel can be valid for several sales organizations.
    Procedure
       1. Access the activity using one of the following navigation options:
    Transaction code      OVXK
    IMG path      Enterprise Structure ® Assignment ® Sales and Distribution ® Assign distribution channel to sales organization
       2. On the Distribution Channels -> Sales Organization: Overview screen, select Sales Org.BP01 BP01 and assign it to the following Distribution channels:
          Distr. Channel      Name
          01      Direct Sales
          02      Wholesale
          03      Intercompany
       3. Choose Save.
    Refer below LINK For more details
    Organizational Structure-SD

  • Creation of new internal delivery channel using AQ

    Hi,
    I wanted to route one of Trading partner data to a different queue.(no want to use existing queues - IP_IN /IP_OUT queue).
    This needs to create a new delivery channel using AQ in B2B.
    I have gone thru the steps & entered all entries, but I am not able to find any queues created in B2B schema.
    Do I need to create a queue using PL/SL in B2B to make it available as internal delivery channel or this setup itself will create a queue in B2B?
    PFA the entirs:
    for transport parameters
    - transport server (B2B server IP)
    - Protocol as AQ
    -URI - b2b.<uri_name> (name of Queue, wanted to create)
    - Hostname
    - Port
    -SID - b2b
    -consumer - b2buser
    - receiptient - null
    -Polling interval - 6000
    Transport server details:
    Host name - (IP)
    IP - Host IP
    username -
    Pswd - for B2B schema
    Any pointers will be a great help.
    Regards,
    MS

    As mentioned by TH in the above post, first thing is to create the data type that is used for messages - IP_MESSAGE_TYPE. This data type will already be present in the B2B database and could be reused.
    For a new data type you could do the following.
    ==============================================================
    Create a new data type using the following
    ==============================================================
    create type IP_MSG_TYPE as OBJECT (
         MSG_ID VARCHAR2(128),
         INREPLYTO_MSG_ID VARCHAR2(128),
         FROM_PARTY VARCHAR2(512),
         TO_PARTY VARCHAR2(512),
         ACTION_NAME VARCHAR2(512),
         DOCTYPE_NAME VARCHAR2(512),
         DOCTYPE_REVISION VARCHAR2(512),
         MSG_TYPE INT,
         PAYLOAD CLOB,
         ATTACHMENT BLOB
    Once you have created a new Data type ( or are reusing the existing data type), you need to create Queue Table that will hold the Outbound and Inbound message queues. The existing Queue table is "IP_QTAB" which can again be reused.
    For new Queue table you could do the following
    ==============================================================
    Create a new Queue Table using the following
    ==============================================================
    execute dbms_aqadm.create_queue_table (     queue_table => 'MY_QTAB',
                             queue_payload_type => 'IP_MSG_TYPE',
                             multiple_consumers => FALSE);
    If you need to reuse the datatype change the queue_payload_type to 'IP_MESSAGE_TYPE'.
    Once we have the Queue Table that will hold the queues, we need to add and start the queues that are to be used for the inbound and outbound messages.
    ==============================================================
    Create the new Queues into the Queue Table using the following
    ==============================================================
    execute dbms_aqadm.create_queue (queue_name => 'B2B.MY_OUT_QUEUE', queue_table => 'B2B.MY_QTAB');
    execute dbms_aqadm.create_queue (queue_name => 'B2B.MY_IN_QUEUE', queue_table => 'B2B.MY_QTAB');
    execute dbms_aqadm.start_queue(queue_name => 'B2B.MY_OUT_QUEUE', dequeue => TRUE, enqueue => TRUE);
    execute dbms_aqadm.start_queue(queue_name => 'B2B.MY_IN_QUEUE', dequeue => TRUE, enqueue => TRUE);
    If you are reusing the queue table IP_QTAB for creation of new queues, then reference that for the queue_table in above commands.
    You need to reference the queue_name eg. B2B.My_OUT_QUEUE in the B2B UI screen.
    Hope this helps.
    AKT

  • 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.

  • Create several distribution channel for an existing customer

    Hi,
    to create a new customer, we use the BAPI "BAPI_CUSTOMER_CREATEFROMDATA1" with the specified distribution channel.
    After creation of the customer I want to create another distribution channel to this customer without create a new customer number.
    Is there any BAPI, which solve this issue?
    Best regards,
    Dirk

    hii,
    From ECC it is manadatory that you maintain Common Distribution Channel (Reference distribution channel for conditions, Reference distrib.channel for cust.and material masters) and Common Division (Reference division for conditions, Reference division for customers). so you will have to create the customer similarly. Thumb rule it is standardized.
    Customer created for one sales area i.e., 1000,10,01 cannot be used in another sales area 1000,11,01 unless the customer is extended. (which means you cannot use the customer for other sales area)
    rgrds,
    Shweta

  • Creation of new plant and the impact of business

    Hi to all
    i am creating a new plant, and would like to know the impact of the plant, what are the changes to be made in the customization, i want to know what are the chages required, and let me know after unit testing and integration testing what activity to be performed, as i am at go live stage and in the production client how to extended the master data,  what is data migration how it can be done,
    thanking you

    Hi there,
    As an SD consultant, these are the things you need to take care.
    Assign the plant to the company code in OX18.
    You need to assign the new plant to the sales org / distribution channel in OVX6.
    Then assign the shipping point to plant in OVXC. If WH is active for your plant, then assign warehouse WH to plant & storage location in LE assignment.
    Reg the master data, you need to assign the material master to the new plant. Also maintain the MRP profiles, plant specific data in the MM01.
    Maintain the shipping point determination in OVL2 & storage loc determination in OVL3 (OVL3 if required)
    Check with MM, PP & FI if they need to maintain any plant specific configs. There are some configs from their end for sure. For eg for production orders, purchase orders, movement types etc.
    Reg the testing, you need to ensure that plant gets proposed automatically when a new sales order is created. Also maintain the relevent plant specific condition records.
    Similarly when PGI is done, it should update the transfer postings in MM & FI w.r.t plant.
    Even tough your project is in final stages, you have to do a regrious testing when a new plant is created. Testing cannot be compromised for time lines. It will lead to serious production issues if tsting is not properly done.
    Regards,
    Sivanand

  • Trx. MM41: Creation of new article data

    Hi togehter,
    I've a special question regarding tax data proposal in the area of SAP Retaill - Creation of new article data.
    We've distribution centers in different countries.
    If I create a new article masterdata for a sales organization assigned to Austria and a distribution center
    assigned to Italy I get the following tax data proposal (if I enter '1' in field MARA-TAKLV):
    IT     Italy     MWST     Output tax               1     Full tax    
    IT     Italy     LCIT        VAT license Italy      1    Full tax    ->     error: the category LCIT does not define classification 1 (only 0)
    I assume that the entry LCIT comes from table TSKM.(material taxes).
    Now my question.
    We don't need the entry LCIT. It is possible or it is the right way to delete the entry named before?
    Or should we create a new entry?
    Thanks in advance for your help/info.
    Best regards
    Frank

    Moved from SAP ERP SD Sales to SAP for Retail.  Please try to post in the right forum to get right direction to your requirement / issue.  Also go through the following blog which will help you.
    Find Topic Spaces on SCN (Forums)
    G. Lakshmipathi

  • Distribution channel-wise customer sales and outstanding report.

    Hi
    In our scenario, one customer is direct factory sales as well consignment sales customer also. We created two distribution channel. But customer master record is one.
    Now my client requires customer report:
    Total sales value and quantity - distribution channel wise
    Outstanding customer balance - distribution channel wise
    Please let me know if this report is possible.
    I tried with some reports: S_ALR_87012171 and S_ALR_87012186. But its showing total sales.
    I tried with VF05N. It shows billed amount and does not quantity.
    Please help.

    Distribution Channel-Wise Sales can be made avaialble thru Standard Reports or LIS / SIS.
    But, I believe you cannot get the Distribution Channel-wise Outstanding Report from SAP Standard. You will have to go for Z-Report Development.
    Speak to your ABAPer & get a new Report developed.
    Hope this helps,
    Thanks,
    Jignesh.

  • Common distributions channels

    Hi everybody:
    I want to use the functionality of common distributions channels only for the creation of customer's master data.
    I want to preserve the update of sales area to the material’s master data because the same material in the same company code could have different “Acct assignment group” and “Output Tax” depends on the sales zone.
    But if I have many sales area when I have the same customer in many sales zone and in this case the data never changes only I need one sales area to maintain.
    Can I customize only the common distribution channel applies only for the creation customer’s master data?
    I really appreciate the help.
    Susana

    Hi Susana,
    I don't think this is possisble with customizing :(.
    And I don't think there is an 'easy' solution for it neither
    1) Either go for an automated creation / change of the customer master data to the 'non-maintained' sales areas
    ( maybe you can setup something with ALE and link back to your own system and only override the distribution channel when creating the customer  in the 'remote' system )
    2) If it's only necessary for certain pricing / tax operations to use the material master data for the original sales area ( rather then the common sales area ) , it's probably possible to use userexits to overule the default values found by SAP for the commoen sales area and replace them with your own : e.g. userexit 'userexit_move_field_to_vbap'  in mv45afzz
    can be used to retrieve your own vbap data
    regards
    Dirk

  • Common distribution channel

    Hi forum,
    Can we map Common distribution channel in R/3 to CRM. I know common division can be mapped by defining Common (Dummy) division. Is there any provision for distribution channel.
    Thanks in advance,
    Regards,

    Goto VOR1 and VOR2
    In VOR1:
    Here you have the option of assigning a Reference Distribution Channel to your combination of Sales Org+Distribution Channel.
    What ever distribution channel you give here in the Refrence Fields, you will then be maintaining the Material masters using this reference Distribution channel.
    Having assigned a reference D Channel to the combination of Sales Organization and other divisions, while creation of a Sales Order with Sales Org and any other division, the system will use the master data maintained for this Reference D Channel for your Sales Area in sales order.
    The use of this is that, Master data can be maintained for only Common Distribution Channel & Division. So it reduces a lot of system load.
    The same applies to VOR2, here you assign a common division to the combination of Sales Org+Divisions.
    Hope this helps you.
    Reward points if helpful.
    Regards,
    Vivek Sahni

  • Distribution channel ( tax problem )

    Dear Gurus ,
    I created distribution channel  with reference to standard SAP distribution channel "01"  .
    Beacuse of this , In tax classification , "DE" and tax category MWST is appearing by default at the time creation of customer master and material master .
    i also check it is not assign to tax determination rule for country india . I want to remove that tax classification .
    Kindly pls suggest corrective action for this .
    further I can't delete distribution channel now this stage .
    Thanks & rgds
    Anchal Pawat

    Well anchal,
    Sorry..i was bit wrong..here are the details
    The system displays the countries provided in the customer master based on "the plant assignment (plant country)
    for the distribution channel and sorg (transaction OVX6)."
    so check what are the plants that u have assigned to ur Sorg and DC....countries of those plant will be shown in customer master
    The system displays the countries provided in the material
    master based on "the plant assignment (plant country)
    for the distribution channel and sorg (transaction OVX6)."
    so check what are the plants that u have assigned to ur Sorg and DC...countries of those plant will be shown in material master
    Let me know whether this resolves
    Regards
    Jagdish

  • Restricting transaction VL06O by distribution channel

    Hello,
    Can someone please help as I am new to this?
    I have added transaction VL06O to a role and I need to restrict this by distribution channel.  When I have checked in SU24, there is no authorisation object associated with the transaction that will check for distribution channel.  So in SU24, I have added the authorisation object V_VBAK_VKO and set this to Check/maintain, the authorisation object then appears in PFCG and I can add the value for the distribution channel to the organisational levels of that role.  However, when I test this, it still does not appear to be doing an authorisation check on the distribution channel and I can view data regardless of what value has been set for distribution channel.  Can anyone please offer me some advice on how I can force this authorisation object to be checked? 
    Thanks.  
    Leah

    Hi
    Which version of  your SAP R/3?
    The only one option is customizing the tcode by writing AUTHORITY-CHECK statements in the assoicated ABAP programmes and later same should be maintained in SU24.

  • Change of Distribution Channel and Division

    Good day, everyone!
    Is there a transaction code that will allow me to change the distribution channel and division of the material?
    Thank you.

    Division can be changed with MM02.
    But distribution channel is a key for the sales data. You can only flag the existing sales data for deletion in MM06 and create new sales data with MM01.

Maybe you are looking for