Confirmation of sensitive filed of customer master

Hi all
Is that possible to BLOCK or NOT TO CREATE a sales order, if confirmation of sensitive filed of customer master yet to confirm ?
Is that need user exit or can we do Configuration.
Need your suggestions.
Regards,
Nagesh

Hi Nagesh,
behaviour of Sensitive filed is once activate some fields as a sensitive filed's if user change that field data from the master record system will stop payments until confirm the changes from other user.
But system not stop Sale order / Delivery / Invoice creation even though fields data change from master system will stop only payments for perticular customer / vendor.
The other name for sensitive filed is dual control. once fileds activated it will applicable entire client not to comp code.
Regards,
Viswa

Similar Messages

  • Customer Master Changes Confirmation

    Hi,
    I am changing one of the fileds in customer master. This eventually needs a confirmation from another user. But when the changes are rejected (T.code FD08), the changes that are made to customer master is retained. The new values are updated in the customer master in spite of rejection.
    Could anyone let me know why the new values are updated in spite of rejection?What is the actually SAP standard functionality using confirmation on changes to customer master.
    Regards,
    Mallikarjun G

    Hi, have you applied the note 877705 - Dual Control: changes remain effective despite rejection
    Hope it helps!
    Regards,
    Lorena

  • Dual Control for Vendor/Customer Master Data

    We can set Dual Control for Vendor/Customer Master Data. I have set it. According to the cycle, I have customized sensitive field, and make changes in Vendor/Customer A/c. Here the changes will be confirmed by other user who is authorised to confirm the changes. In this scenario, I would like to know, can we avoid this confirmation once we have actived? If, no than how could we confirm the changes and where can we set authorisation?

    Dear,
    No, You cannot avoid the dual check if You activate it. Another user by FK08 has to confirm the changes.
    Then You can delete the field for the dual control into the table T055F and no check will be done in the future.
    I hope this helps.
    Mauri

  • Creation of partner functions for customer master with LSMW

    Hello,
    I try to create partner functions together with a customer via Batch Input in LSMW.
    Object: 0050, method: 0000, program name: RFBIDE00, program type: B.
    I use the structure BKNVP (Customer master partner functions) to create a new partner and set values for the fields KTONR and PARVW.
    When I start the batch input the fields are filled in correctly in a new dynpro. After the confirmation of these values the dynpro changes back to the partner functions sscreen, but the value for KTONR isn'n being transferred. So I get an error message.
    Is it only possible to update partner functions with that BI or what is going wrong ?
    Thanks in advance and regards
    Alex

    Hi Alex,
    Could you specify what error message you are getting?
    Thanks!
    Rudra

  • Query in customer master data upload ....?

    Hi Guru's,
    I am uploading the customer master data from presentaion server to customer tables using functional module SD_CUSTOMER_MAINTAIN_ALL.
    while check the Function module separatly and it working properley and i am able to ctere customer...
    and i am using the same function module in the program i am unable to upload ..could please check and let me know where i am doing mistake in the below program logis..and values also moving properly before calling function module..while calling the functinal module the controle comming out of the loop and program went to dump i am able to see the message in dump as like this(it may helpfull for resolve):
    Name of function module...............: "SD_CUSTOMER_MAINTAIN_ALL"
    Name of formal parameter..............: "O_KNA1"
    Technical type of actual parameter....: "C"
    Technical length of actual parameter..: 20 bytes
    Technical type of formal parameter....: "u"
    Technical length of formal parameter..: 3634 bytes
    Name of formal parameter at caller....: "O_KNA1"
    *& Report  ZERP_CUSTOMER_CREATE_UPLOAD
    REPORT  zerp_customer_create_upload.
    PARAMETERS:p_files        TYPE string.
    *DATA :xkunnr(10)      LIKE kna1-kunnr.  "unique KUNNR
    DATA: gs_i_kna1           TYPE kna1,
          gs_i_knb1             TYPE knb1,
          gs_i_knvv           TYPE knvv,
          gs_return           TYPE bapireturn1,
          gs_i_bapiaddr1      TYPE   bapiaddr1,
          gt_t_xknvi          TYPE STANDARD TABLE OF fknvi,
          gwa_t_xknvi         TYPE fknvi,
          gt_t_xknbk          TYPE STANDARD TABLE OF fknbk,
          gwa_t_xknbk         TYPE fknbk,
          gt_t_yknvp          TYPE STANDARD TABLE OF fknvp,
          gwa_t_xknvp         TYPE fknvp.
    TYPES:BEGIN OF gty_itab1,
          abc(305),
          END OF gty_itab1.
    DATA: gt_itab1 TYPE STANDARD TABLE OF gty_itab1,
          gwa_itab1 TYPE gty_itab1.
    TYPES :BEGIN OF gty_itab2,
           ktokd(4),        "customer account grp      kna1
           kunnr(10),       "customer                  kna1
           name1(35),       "name1                     kna1
           sortl(10),       "sort filed                kna1
           stras(35),       "house number and adres    kna1
           pstlz(10),       "postal code               kna1
           ort01(35),       "city                      kna1
           land1(3),        "country                   kna1
           telf1(16),       "tele phone no             kna1
           telfx(31),       "fax num                   kna1
           kukla(2),        "cust classificaion        kna1
           bukrs(4),        "company code              knb1
           akont(10),       "reconcilation acct        knb1
           vkorg(4),        "sales org                 knvv
           vtweg(2),        "distr chan                knvv
           spart(2),        "division                  knvv
           zterm(4),        "terms of payment          knvv
           bzirk(6),        "sales district            knvv
           vkbur(4),        "sales office              knvv
           vkgrp(3),        "sales grp                 knvv
           kdgrp(2),        "cust grp                  knvv
           waers(5),        "currency                  knvv
           konda(2),        "price grp                 knvv
           kalks(1),        "pricing procedure assign  knvv
           lprio(2),        "delivery plant            knvv
           vsbed(2),        "shipping conditions       knvv
           vwerk(4),        "delivering plant          knvv
           inco1(3),        "inco1                     knvv
           inco2(28),       "inco2                     knvv
           kkber(4),        "cred control area         knvv
           ktgrd(2),        "acc assgn grp             knvv
           taxkd(1),        "tax classification 4 cust knvi
           bankn(18),       "bank account number       knbk -
            xkunnr(10),
           END OF gty_itab2.
    DATA: gt_itab2 TYPE STANDARD TABLE OF gty_itab2,
          gwa_itab2 TYPE gty_itab2.
    CALL FUNCTION 'GUI_UPLOAD'
      EXPORTING
        filename                = p_files
        filetype                = 'ASC'
      TABLES
        data_tab                = gt_itab1
      EXCEPTIONS
        file_open_error         = 1
        file_read_error         = 2
        no_batch                = 3
        gui_refuse_filetransfer = 4
        invalid_type            = 5
        no_authority            = 6
        unknown_error           = 7
        bad_data_format         = 8
        header_not_allowed      = 9
        separator_not_allowed   = 10
        header_too_long         = 11
        unknown_dp_error        = 12
        access_denied           = 13
        dp_out_of_memory        = 14
        disk_full               = 15
        dp_timeout              = 16
        OTHERS                  = 17.
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    LOOP AT gt_itab1 INTO gwa_itab1.
      gwa_itab2 = gwa_itab1-abc(305).
      APPEND gwa_itab2 TO gt_itab2.
    ENDLOOP.
    LOOP AT gt_itab2 INTO gwa_itab2.
      SPLIT gwa_itab2 AT ',' INTO gwa_itab2-ktokd
                                  gwa_itab2-kunnr
                                  gwa_itab2-name1 gwa_itab2-sortl
                                  gwa_itab2-stras gwa_itab2-pstlz
                                  gwa_itab2-ort01 gwa_itab2-land1
                                  gwa_itab2-telf1 gwa_itab2-telfx
                                  gwa_itab2-kukla gwa_itab2-bukrs
                                  gwa_itab2-akont gwa_itab2-vkorg
                                  gwa_itab2-vtweg gwa_itab2-spart
                                  gwa_itab2-zterm gwa_itab2-bzirk
                                  gwa_itab2-vkbur gwa_itab2-vkgrp
                                  gwa_itab2-kdgrp gwa_itab2-waers
                                  gwa_itab2-konda gwa_itab2-kalks
                                  gwa_itab2-lprio gwa_itab2-vsbed
                                  gwa_itab2-vwerk gwa_itab2-inco1
                                  gwa_itab2-inco2 gwa_itab2-kkber
                                  gwa_itab2-ktgrd
                                  gwa_itab2-taxkd
                                  gwa_itab2-bankn.
    *moving files values from ITAB2 work area to global structure related to FM.
      gs_i_kna1-ktokd   = gwa_itab2-ktokd.
      gs_i_kna1-kunnr   = gwa_itab2-kunnr.
      gs_i_kna1-name1   = gwa_itab2-name1.
      gs_i_kna1-sortl   = gwa_itab2-sortl.
      gs_i_kna1-stras   = gwa_itab2-stras.
      gs_i_kna1-pstlz   = gwa_itab2-pstlz.
      gs_i_kna1-ort01   = gwa_itab2-ort01.
      gs_i_kna1-regio   = gwa_itab2-land1.
      gs_i_kna1-telf1   = gwa_itab2-telf1.
      gs_i_kna1-telfx   = gwa_itab2-telfx.
      gs_i_kna1-kukla   = gwa_itab2-kukla.
      gs_i_knb1-bukrs   = gwa_itab2-bukrs.
      gs_i_knb1-akont   = gwa_itab2-akont.
    *I FOR GOT TO INCLUDE THE ZTERM VALUE IN EXCELL SHEET SO INCLUDED HARD CODE HERE
      gs_i_knb1-zterm   = '0001'.
      gs_i_knvv-vkorg   = gwa_itab2-vkorg.
      gs_i_knvv-vtweg   = gwa_itab2-vtweg.
      gs_i_knvv-spart   = gwa_itab2-spart.
      gs_i_knvv-zterm   = gwa_itab2-zterm.
      gs_i_knvv-bzirk   = gwa_itab2-bzirk.
      gs_i_knvv-vkbur   = gwa_itab2-vkbur.
      gs_i_knvv-vkgrp   = gwa_itab2-vkgrp.
      gs_i_knvv-kdgrp   = gwa_itab2-kdgrp.
      gs_i_knvv-waers   = gwa_itab2-waers.
      gs_i_knvv-konda   = gwa_itab2-konda.
      gs_i_knvv-kalks   = gwa_itab2-kalks.
      gs_i_knvv-lprio   = '02'.             "gwa_itab2-lprio.
      gs_i_knvv-vsbed   = gwa_itab2-vsbed.
      gs_i_knvv-vwerk   = gwa_itab2-vwerk.
      gs_i_knvv-inco1   = gwa_itab2-inco1.
      gs_i_knvv-inco2   = gwa_itab2-inco2.
      gs_i_knvv-kkber   = gwa_itab2-kkber.
      gs_i_knvv-ktgrd   = gwa_itab2-ktgrd.
      gwa_t_xknvi-tatyp  = 'UTXJ'.          "HARD CODE
      gwa_t_xknvi-aland  = 'US'.            "HARD CODED
      gwa_t_xknvi-kz     = '0'.             "HADR CODE
      gwa_t_xknvi-taxkd  = '0'.             "gwa_itab2-taxkd.
      APPEND gwa_t_xknvi TO gt_t_xknvi.
      gwa_t_xknbk-bankn  = gwa_itab2-bankn.
      APPEND gwa_t_xknbk TO gt_t_xknbk.
      gs_i_knb1-lockb          = 'X'.
      gs_i_knvv-kzazu          = 'X'.
      gs_i_knvv-kztlf          = 'X'.
      gs_i_knvv-perfk          = 'X'.
      gs_i_knvv-prfre          = 'X'.
      gs_i_kna1-spras          = 'EN'.
      CALL FUNCTION 'SD_CUSTOMER_MAINTAIN_ALL'
       EXPORTING
         i_kna1                              = gs_i_kna1
         i_knb1                              = gs_i_knb1
         i_knvv                              = gs_i_knvv
      I_BAPIADDR1                         =
      I_BAPIADDR2                         =
      I_MAINTAIN_ADDRESS_BY_KNA1          = ' '
      I_KNB1_REFERENCE                    = ' '
      I_FORCE_EXTERNAL_NUMBER_RANGE       = ' '
      I_NO_BANK_MASTER_UPDATE             = ' '
      I_CUSTOMER_IS_CONSUMER              = ' '
      I_RAISE_NO_BTE                      = ' '
      PI_POSTFLAG                         = ' '
      PI_CAM_CHANGED                      = ' '
      PI_ADD_ON_DATA                      =
      I_FROM_CUSTOMERMASTER               = ' '
    IMPORTING
      e_kunnr                             = xkunnr
      o_kna1                              = xkunnr
      E_SD_CUST_1321_DONE                 =
       TABLES
      T_XKNAS                             =
         t_xknbk                             = gt_t_xknbk
      T_XKNB5                             =
      T_XKNEX                             =
      T_XKNVA                             =
      T_XKNVD                             =
         t_xknvi                             = gt_t_xknvi
      T_XKNVK                             =
      T_XKNVL                             =
      T_XKNVP                             =
      T_XKNZA                             =
      T_YKNAS                             =
      T_YKNBK                             =
      T_YKNB5                             =
      T_YKNEX                             =
      T_YKNVA                             =
      T_YKNVD                             =
      T_YKNVI                             =
      T_YKNVK                             =
      T_YKNVL                             =
       t_yknvp                             = gt_t_yknvp
      T_YKNZA                             =
      T_UPD_TXT                           =
       EXCEPTIONS
         client_error                        = 1
         kna1_incomplete                     = 2
         knb1_incomplete                     = 3
         knb5_incomplete                     = 4
         knvv_incomplete                     = 5
         kunnr_not_unique                    = 6
         sales_area_not_unique               = 7
         sales_area_not_valid                = 8
         insert_update_conflict              = 9
         number_assignment_error             = 10
         number_not_in_range                 = 11
         number_range_not_extern             = 12
         number_range_not_intern             = 13
         account_group_not_valid             = 14
         parnr_invalid                       = 15
         bank_address_invalid                = 16
         tax_data_not_valid                  = 17
         no_authority                        = 18
         company_code_not_unique             = 19
         dunning_data_not_valid              = 20
         knb1_reference_invalid              = 21
         cam_error                           = 22
         OTHERS                              = 23.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      IF sy-subrc EQ 0.
        CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
        WRITE: / 'Error Message:', 'error in creation'.
      ELSE.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
        WRITE: / 'costomer', gwa_itab2-kunnr, 'created'.
      ENDIF.
    ENDLOOP.

    please let me know if my qestion is not clear...
    and please cinfirm me ..that can i use the function module (SD_CUSTOMER_MAINTAIN_ALL) instead of BAPI (BAPI_CUSTOMER_CREATEFROMDATA1) for uploading customer master data.
    please respond me ASAP.
    thanks in advance and will give full points
    thanks&regards
    Srinivas.

  • ERROR IN CUSTOMER MASTER CREATION -THROUGH IDOC.

    We are facing issue while creating customer through idoc. System is giving error "No batch input data for screen SAPLID_TAXNUM 1000 "
    On analyzing this error - we are able to find out that someone has enabled some duplicity check or message control on filed of tax number 1.In this filed we are storing some other legacy information which is not unique to each customer so system is poping up some screen which shows that this information already exist for other customers . Due to this customers are not getting created.
    We have checked the message control  setting bur there was no such message control.
    Now we are not able to figure it that who has done this change and how. Further how this can be resolved.
    Pls help.
    Rgds,
    Sudhanshu Dang

    Hai Jobi Thottungal,
    Since you can create a Customer with Account type 001, please check what is the PARTNER TYPE assigned.
    Now, GO TO
    IMG Sales and DistributionMaster DataBusiness PartnersCustomersCustomer Hierarchy
    Set Up Partner Determination for Customer Master
    Partner Determination Procedure Assignment
    Assign the Partner procedure to your Account group
    So at the time of creation of Customer master with your Account group, the partner function will get created automatically.
    Regards,
    Mani

  • Account Group and partner functions in customer master records

    Hi Gurus,
    I need your help to confirm the following understand if correct:
    1. To create customer master record for partner function Ship-To, need to create a customer master record using the uniquely assigned account group for Ship-To , that is, 0002 . In this ship-to master record, define in its partner function tab, the other partner functions related to it. 
    2. To create the above, it cannot be achieved by just assigning the partner functions in the partner function tab of SOLD-To customer master record , created using account group 0001.
    Question:
    1. How does the system know or allow what codes a user can select (f4) or enter manually when defining in customer master record's partner function tab, the partner functions and their respective codes?
    How is this controlled? Is it by user authorization? or will user / sales administrator be able to select any codes tied to a partner function?
    2. Lets say there are 2 partner functions : Sales employee VE and 9E called Sales Representative. Both of these partner functions are of Partner Type PE.
    When defining in customer master record's partner function tab, how does the system know what codes is selectable for the administrator for each of these partner functions?
    best regards
    M Russo

    hi russo,
    this is to inform you that,
    1. yes you are right.
    2. you need to follow the steps as you said.
    Question:
    1. that you can find in the search basing on account group for partners.  that assignment we should know russo which SH to be assigned to which SP.  no need to have authorization for that, make a note of the list of SH and SP to be assigned that's all.
    yes, he will able to select any SH from the list but make sure that we assign the correct SH to the list of SP.
    2. that you will be defining it in Partner Determination Procedures.  at the time of CMR creation you have to select the correct code that will get populated in sales order.
    hope this clears your issue.
    balajia

  • Customer master creation and maintenance

    Hi All,
    I have a question regarding customer master. The client is implementing FSCM credit and collections management. Initially, all the existing customers in AR are mapped or loaded to SAP Business partner using the functions available (I dont remenber on top of my head but i know we can do that).
    Now my questions are,
    1. When creating a new customer later some point, do we have to create in AR and then establish the relationship to SAP Business partner. Or directly create as SAP Business partner.
    2. If to be cretaed both in AR and as Business partner, this would be kind of duplication or maintaing in 2 seperate places. Please explain the reason behind it.
    3. If only to be created as Business partner, will all the fields available in Customer master (like business area, accounting clerk, Industry field) be available in Business partner
    one more question, We can automatically import credit data from External Credit Information service. Can we push the data from our system to the Provider like the payment data or anything for that matter. Client has a requirement for this to send data to provider and I am not sure. Please confirm.
    I know there are too many question, but please help me undertsand this more better.
    Regards,
    Satya

    I am sorry about that but first 3 questions are related and linked.
    I understand that a link is established between AR customer data and BP's and this will migrate all data. But the data will be in AR and will be copied to BP..right.
    Likewise, if you create a customer in AR, it will create a BP...will this be done automatically?
    And later if we want to create a new customer, do we need to do in AR and this will automaticall create a BP? Is this not duplication. I know that BP are maintained centarlly and for master data synchronization.
    Regards,
    Satya

  • Report Viewer Webpart is Blank in Custom Master Page

    Dear Experts ,
    Recently my team created a new master page to replace seattle default page in Sharepoint 2013. Things were fine till the moment we accessed one of site page containing a Report Viewer Web Part to load SSRS rdl. The web part is blank
    with just standard SSRS toolbar and parameter. To isolate the problem, I have confirmed that the same page works fine in seattle master. I notice that something could be missing in our site (though I am clueless on what those are). There is one post online
    from someone with potentially similar issue, but it does not help in our case. Some pointers from will be appreciated. Cheers.
    http://blogs.msdn.com/b/selvar/archive/2013/11/28/using-reporting-service-web-part-with-sharepoint-custom-master-pages.aspx

    Hi,
    Please try to add AsyncPostBackTimeout="0" inside the ScriptManager code in your master page.
    <asp:scriptmanager id="ScriptManager" runat="server" enablepagemethods="false" enablepartialrendering="true" enablescriptglobalization="false" asyncpostbacktimeout="0" enablescriptlocalization="true" />
    If the issue still exists, I suggest you provide some error messages or code for further research.
    Thanks,
    Dennis Guo
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Dennis Guo
    TechNet Community Support

  • Customer master data creation

    Hello Folks,
    I need some confirmations please :
    1 . customer master data (cmd) is created at account group and company code level.
    So, if a  customer is a customer of 3 company codes of a company , 3 customer master records needs to be created where the number range of the customer code being the same and the company code is different and the account group remains the same?
    2. A  customer can buy from any sales area combination in company code, but only 1 customer master record is created ? If so, 1 customer code is for any Sales areas for a customer?
    So, Sales area is data fields in a customer master record and only account group and company code and the customer code are key fields in the definition of customer master record?
    Please confirm for me. Thanks.
    regards
    Ravi

    Hi Ravi,
    _Extension of the CMR_
    a.     If the Customer is buying from under 1 Company Code and multiple Sales Areas then you need to extend the CMR for all sales area.
    b.     However when the sales areas change the Customer No., General data and the Company code data does not change
    While Extending the CMR by changing the Sales Area:
    a.     In XD01 or VD01 enter the Account Group of the customer which is to be extended
    b.     Enter the customer no.
    c.     Enter the New sales area
    d.     The system will take you directly to the sales area data
    e.     The Company Code data and the General data cannot be chosen.
    While extending the CMR for different company codes:
    a.  In XD01 or VD01 enter the Account Group of the customer, which is to be extended
    b. Enter the customer no.
    c.     Enter the New Company code
    d.     The system will take you directly to the Company Code Data
    e.     The Sales Area Data and the General data cannot be chosen.
    While extending the CMR for different company codes and sales Areas:
    a.  In XD01 or VD01 enter the Account Group of the customer, which is to be extended
    b.  Enter the customer no.
    d.     Enter the New Company code
    e.     Enter the New Sales Area
    f.     The system will take you to the Company Code Data
    g.     Then you can go to the Sales area data.
    h.     The General data cannot be chosen.
    Tables Used for CMR:
    Table Name     Used For
    KNA1         General Data
    KNVV         Sales Area Data
    KNB1         Company Code Data
    Q. Why are there 3 Data Groups or 3 different Tables for one customer?
    Ans. Since the Customer is expected to buy in more than one sales area and also in some cases in more than one Company code different data sets need to be maintained but however some data remain same, so to avoid data redundancy you maintain 3 different tables.
    Hope this helps,
    J Nagesh

  • How to set default field values in customer master data.

    hi,
    I want to set default values in customer master data (account group wise).
    but
    I don't know how to set it .
    please help me.
    (I don't want to change field status in account group rather than I want to set default values for field. )
    thank you.

    hi,
    this is to inform you that,
    in SAP there is no such a provision.
    but
    in LSMW there is an option of CONSTANT VALUES.
    check in SHD0 - also
    please check and confirm
    balajis\a

  • Prof Analysis characteristic changes KEA5 Customer Master to Sales Document

    hello gurus
    I need some help with this pa configuration change. our office in india wants to amend the 2 characterictics in bold in pa transaction kea5. currently they look at origin table - customer master sales data. charac details below No other changes will be made
    charac     desp     sht text     datatype     lngt     origin table     orig field descrip
    bzirk     sales district     sistrict     char     6     knvv     bzirk
    vkbur     sales office     sales sff.     char     4     knvv     vkbur
    business want to change these two characteristics from knvv to pick up the details from sales document order - table vbak for sales office and vbkd for sales district, so it matches with their mcsi. please note a number of changes are required on bw. But I am only concerned about pa changes, my colleagues will pick up bw changes.
    please can I get some help with this configuration task, as I've never configured pa - It appears to be more complexed than regular fico config. I believe it is a fairly small change via transaction kea5, is that correct
    please kindly provide the following information - 5 points below
    1. intend on deleting these two characteristics linked to knvv and then linking to vbak and vbkd respectively.
    2. the characteristice for vbak and vbkd already exist in config kea5, so I don't believe I need to recreate anything new, just pull in the fields, and link to the relevant characteristics.
    3. please can you confirm if I only need to amend kea5 to configure the above scenario? Or are there any other tables/areas in spro I need to amend.
    4. please can you provide me with step by step details on what I need to do to configure this new characteristic and scenario correctly.
    5. finally please can you provide me details of what testing I need to do to test this change.
    Thank you all very much.
    Awaiting feedback from all pa gurus, thanks in advance
    Thanks
    Jay
    Edited by: Jays77 on Jan 6, 2011 1:17 PM
    Edited by: Jays77 on Jan 6, 2011 1:18 PM
    Edited by: Jays77 on Jan 6, 2011 1:19 PM

    Hello Ajay / and All -
    Thanks very much for your feedback. I have carried out your configuration via KEDR, and created the derivation rule. Is it really as straight forward and I dare not say that easy, to create a new characteristic value.
    Is there absolutely no additional configuration required via kea0 - Maintain Operating Concern or kea5 maintain characteristic values. I agree we have added this derivation rule and I can to some extent understand what we've done, but in kea5 and kea0, the old characteristic value and fields are still there - as detailed below. So it is still mapping to the old characteristic values, I can only assume this derivation rule overwrites what is in kae5 and kae0, is that correct.
    charac  desp             sht text  datatype  lngt origin table orig field descrip
    bzirk      sales district  sistrict   char         6        knvv           bzirk
    vkbur    sales office     sales sff. char     4        knvv           vkbur
    I just want to make extra sure, I don't need to delete these old characteristic values, and add the new characteristic values to KEA5 and KEA0. The new characteristic values are not on kae5 and kae0 - hence my concern.
    Please kindly confirm configuration if any addition config is required, or only changes via KEDR as explained in your previous reply.
    Thanks again for your help - Much Appreciated.
    Jay
    Edited by: Jays77 on Jan 6, 2011 3:02 PM

  • Output proposal from customer master in 4.7

    Hi
      I'm trying to find configuration nodes in spro for <b>output proposal from customer master</b> in SAP R/3 4.7. Strangely it is not where it is supposed to be i.e.
    SD>Basic Functions>Output Control
         I tried by searching but unable to find it. However I found out that you can assign output determination procedure in define account groups.
          Please help me in finding the correct node or the t-codes for maintaining output procedure for output from customer master. Kindly note that I am looking in <b>SAP R/3 4.7</b> version.
    thanks in advance
    Koustav

    Output proposal from the customer master record
    IMG&#61664;SD&#61664;Basic fncs&#61664;Output&#61664;Output determination&#61664;Output proposal from the customer master record, Define output
    In this option one creates output types, such as BA00 (order confirmation). After creating the output type, one assigns the output type to an output procedure, such as DB0001. After the assignment of the output types to the procedure, the output procedure is then assigned to the customer account group. This is a simple procedure and results in the output that is placed on the customer master record being copied into the sales document.

  • Customer master message control

    hi folks,
    need to prevent duplicate MICR information in customer master. is there a way to do this via message control?

    Dear Amy,
    are You talk about the dual control?
    Within IMG: Financial accounting(new)->accounts receivable and accounts
    payable->vendor accounts->master data->preparations for creating customer master data->define sensitive fields for dual control (customers)
    I hope this helps.
    mauri

  • Output proposed  from customer master

    Hello SDN!
    I could not find output info in customer master.
    Can I check with you if output can be proposed from the customer master when creating a sales order?
    Or the only way output is determined is from output determination procedure where customer code can be one of the key condition record fields?
    regards
    Ravi

    Hi,
    Please go through the below Configuration process for Outputs
    Output is a form of media from a business to one of its business partners. Ex: Printouts, Faxes, Telexes, E u2013 mails and Electronic Data Interchange (EDI). The Output determination component offers output functions for Sales, Shipping and Billing to help in manage sales transactions with our customers and within the organization.
    Output can be sent to any of the partners defined in the document.
    Outputs are usually in the form of order confirmations, delivery notes, invoices and shipping notifications.The output determination component offers output functions for sales, shipping transportation and billing to help in manage sales transactions with our customers and with in the organization.
    We can create output.We can group output.Employers can send/receive output.
    Output directly linked to the corresponding sales transaction Ex: Trough EDI.
    System automatically proposes output for a sales and distribution document.
    System uses condition technique to determine output.
    We use output type to control how the output should be transmitted.
    Ex: Via EDI, be printed.
    We can determine output for all kinds of objects in SAP u2013 SD. Ex: For sales activities sales documents delivery documents and billing documents.
    We can determine output, we can process output, and we can send output.
    SAP uses condition technique to determine output.Output types can be Inquiry, Quotation, Order confirmation, Shipping document, Billing document, etc.The output can be sent through transmission mediums.
    Ex: Local printer, Fax, Telex, E u2013 mail, SAP inbox or even to SAP.
    Output determination closely integrated with technical module as technical consultant prepares the output format in SAP script or smart forms.
    Configuration settings:
    Output determination for sales documents: Transaction code: V/57
    Path:
     IMG
     Sales and distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Maintain condition tables
     Maintain output condition table for sales documents
    Save and Exit
    Maintain output types: Transaction code: V/30
    We define output types for output type records. Out put type represents different output.
    Ex: Quotation, Order confirmation, etc.
    Path:
     IMG
     Sales and distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Maintain output types
     Check different output types existed or not
    Ex: AF00 = Inquiry
    AN00 = Quotation
    BA00 = Order confirmation
    LP00 = Scheduling agreement
    MAIL = Internal message
    RD03 = Cash sales invoice
     Click on change/display icon
     Choose u201CBA00u201D
     Click on copy icon (press ENTER till 28 entries copied) and rename it
     Select our output type
     Check u201CMail titleu201D and u201CTextu201D control button whether mail and texts are existed in all languages or not
     Check processing routines for all transmission mediums are existed or not
     u201CProgramu201D, u201CFORM routineu201D, u201CFormu201D are maintained and provided by technical consultants.
     Check partner functions has been assigned to transmission mediums in partner functions control button
     Save (press ENTER up to u201CSAVEu201D request disappears)
     Come back
     Go to details icon
     Assign access sequence [ ] (create access sequence in next step)
     In general data section
    Check access to conditions
     In default values section
    Maintain dispatch time as u201Csend immediatelyu201D
    Transmission medium: u201CPrint outu201D
    Partner function: SP
     In time section
    Check timing: 1
     Save and Exit
    Maintain access sequence
    Path:
     IMG
     Sales and distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination
     For sales documents
     Maintain access sequences
     Go to new entries
     Define your access sequence
     Select it and click on accesses icon
     Go to new entries
     Specify access sequence No. 10
    Table No. Ex: 001
     Save and Exit
    Assign output types to partner functions
    Path:
     IMG
     Sales and distribution
     Basic functions
     Output control
     Output Determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Assign output types to partner functions
     Check whether the system has copied output types with relevant transmission mediums and partner functions
     Save and Exit
    Maintain output determination
    Path:
     IMG
     Sales and distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Maintain output determination procedure
     Choose standard output determination procedure u201CV10000u201D
     Copy and rename it
     Save and select our output determination procedure
     Click on control data button and change output type u201CBA00u201D as ours Ex: SREE
     Save and Exit
    Assign output determination procedure
    Allocate Sales Document Header: Transaction code: V/43
    Path:
     IMG
     Sales and Distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Assign output determination procedure
     Assign Sales Document Header
     Choose sales document type u201CORu201D from position button
     Assign out output determination procedure (ours) Ex: SREE
     Save and Exit
    Sales Document Item: Transaction code: V/69
    Path:
     IMG
     Sales and Distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Assign output determination procedure
     Assign Sales Document Items
     Choose item category as u201CTANu201D form position button
     Assign our output determination procedure
     Save and Exit
    Maintain condition record: Transaction code: VV11
    Path:
     Logistics
     Sales and distribution
     Master data
     Output
     Sales document
     VV11 u2013 Create
     Specify our output type Ex: SREE
     Click on key combination
     Maintain the details like below
    Customer No. Partner
    function
    Message transmission medium
    [M]
    Dispatch date Language
    1001007 SP 1 18 u2013 02 u2013 06 EN
     Select condition line item
     Click on communication
     Specify outputs devise [LP01]
     Check print immediately
     Save and Exit
     Go to VA01 and raise the sales order
     Go to Extras  Output  Edit  Check condition record values are copied or not
     Save and Exit
     Go to VA02  Extras  Output  Header  Print preview
     Check the result
    Steps:
    1. Put the fields into the field catalog that you will need.
    2. Create the condition tables.
    3. Create the access sequence
    4. Assign the condition tables to the access sequence
    5. Create the condition types
    6. Assign the access sequence to the condition type
    7. Create the determination procedure (if necessary) and assign the condition types to it.
    8. Assign the determination procedure.
    9. Create your condition records.
    Regards,
    Siva

Maybe you are looking for