Customer Creation Date

Hi all,
Is there any report that provides customer creation date?
Regards,
Aisha Ishrat
ICI Pakistan Ltd.

Hi,
Check OV50 transaction,there you get creation date in the last column.
Reward if it helpful.
Regards,
Chandra

Similar Messages

  • Error during create CR for MDGC "Enter a relevant role for creation of customer master data"

    Hello Experts,
    I am unable to create a Customer CR in 'MDG 6.1 Customer UI' , the UI throws an error saying "Enter a relevant role for creation of customer master data".It looks like it is expecting me to mention the BP role ( like FLCU01 Customer or FLCU00 FI Customer ) , but I don't see that BP role section in the Customer UI to mention .
    While creating the vendor CR  , I am able to enter the BP role ( like FLVN01 vendor or FLVN00 FI Vendor ) in the UI BP Role section.
    Following are the UI's for Customer and Vendor
    Customers BS_OVP_BP: BS_OVP_CU > OVP: BS_CU_OVP - I do not see BP role section here.
    Vendors BS_OVP_BP: BS_OVP_SP > OVP: BS_SP_OVP - This is working fine  , I see BP role section here.
    Please advice what I am missing here , what should I do for the successful CR creation . Should I change the UI for Customers or do I need to do anything in CVI configuration.
    Thanks,

    Hi Abdullah,
    You were right in the first place the UIBB is missing  , the UIBB 'Role' was present in the 'Search Customer' page but not available in the 'Create Customer CR' page , so I created the 'Role' UIBB again and was able to create the CR now . Not sure how it got deleted in the first place , is there any options where we reset the UI screen to the default initial configuration
    But after approving the CR , only the Business Partner BP is getting created and the Customer is not getting created . Not sure what might be the issue now. Is there any config that tells to automatically create customer when BP is created. I was able to create Vendor using the create Vendor CR before.
    Thanks

  • Customer Creation - Want to pass custom field data to KNA1(Customer Master)

    Hi,
    I have created BAPI for customer creation which uses standard program RFBIDE00 for customer creation.
    I have appended new custom field(ZZATTR1) in the table KNA1 and its currosponding stucture used in the standard program BKNA1.
    Import parameters of my BAPI is one structure which is having this custom field, on executing this BAPI it creates the customer but data which I give through this field is not getting transfered in the table KNA1.
    This sstandard progaram uses file to containing customer information, In the BAPI I on the data from the structure to the file and further it gets submitted to the program.
    My requirement is to pass the data of teh custom field which I have created, How to achieve this ?
    Pls Suggest.
    Regards
    Vishal

    Hi Vishal,
    When implementing a customer exit (i.e. field, user etc) have you ever wanted to be able to read additional
    field values available in the main SAP program but not available in your exit. Now with the use of
    field-symbols you can have access to any field available in the main SAP program. The code below
    demonstrates how this is done within a field exit on BSTNR which can be tested using transaction
    ME21. Information on creating field exits can be found here. 
    FUNCTION field_exit_bstnr.
    ""Local interface:
    *"  IMPORTING
    *"     REFERENCE(INPUT)
    *"  EXPORTING
    *"     REFERENCE(OUTPUT)
    create field symbol
      FIELD-SYMBOLS: <status>.
    Assign value of variable from calling prog to field symbol
      ASSIGN ('(SAPMM06E)RM06E-BSART') TO <status>.
    Display value retrieved in message
    Note: Messages of type i and w are not allowed
      IF sy-subrc = 0.
        MESSAGE e003(zr) WITH <status> 'kkk'.
      ENDIF.
    ENDFUNCTION.
    Rewords some point if it is helpful.
    Rgds,
    P.Naganjana Reddy

  • Error in Customer master data creation

    when I am creating customer master data, error is in sales area data :partner functions
    data is not complete:
    I can't proceed from there. If I choose account group 001, it is working, when I am doing with my own account grp gets eorror.
    I hope I did correct partner determination procedure.
    how to solve this?

    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

  • Creation of Customer Master Data

    Hi
    I have problem with Customer Number range, Created external number Range for customers With number interval
    'SA1 to SA10000000' ,Then when i am creating customer master data it is accepting only some number like SA1, SA10, SA100, SA1000 ....  like this .
    My problem is why it is not accepting all the numbers like SA1, SA2, SA3, SA4.............. SO ON any body please help me
    Thanks in advance,
    Regards
    Prabhakar

    Hi, because SA2 is out of this range! SAP checks available rang according with sorting. If you take value SA1,SA10000000,SA2 and sort it:
    SA1
    SA10000000
    SA2
    So it's out of range

  • Customer creation in R/3 from PI data using IDOCs

    Hi All,
    I am creating customers in SAP r/3 system using IDOCs which are coming from PI system in the form of XML files.
    For that DEBMAS and ADRMAS message types and DEBM process code is used for creating or changing customer master data.
    Existing functionality : 1 IDOC is creating/changing 1 customer master data using standard function module IDOC_INPUT_DEBITOR.
    Required Functionality: need to create/change data for multiple customers using only one IDOC file.
    I have tried using DEBMDM. Unlike DEBMAS, message type DEBMDM can hold  multiple customers but if any DEBMDM IDOC sent to R/3, it was remaining in status 75 with message 'IDOC Received via qRFC'.
    Any help will be appreciated.
    Thanks & Regards,
    Anshoo

    Hi,
    Status 75 refers to that "IDoc is in inbound queue".
    Transaction SMQ2 (qRFC Monitor - Inbound Queue)
    Transaction WEINBQUEUE (IDoc Inbound Queue).
    The transactional asynchronous tRFC guarantees that all database operations are fully executed or, if one of the function modules responds with a termination, they are fully rejected (rollback). If an LUW is executed without errors, it cannot be executed again. In some cases it may be necessary, to rollback an LUW in an application program, for example, because a table is locked.
    Regards,
    Srilatha.

  • 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

  • Sales order creation - data stored in which tables for customer

    Hi experts,
    During sales order creation, data entered during sales process is stored in various related tables. Can anyone list the tables where data is stored for customers?
    Thank you

    Dear Manisha
    Once you saved the sale order,
    - all header datas are stored in VBAK
    - all item level datas are stored in VBAP
    - schedule line confirmation in VBEP
    - all condition types and values are stored in KONV / KONP
    - Partner functions in VBPA
    - Delivery related fields like Shipping Point, Delivery Date, Goods Issue etc., are all in VEPVG
    thanks
    G. Lakshmipathi

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

  • How to fetch post goods issue date and sales order creation date

    Hi All,
    How to find out the difference between SD Sales Order Item Creation Date and final Post goods issue Date. I would like to know how to fetch those dates and what is the relationship between the tables from which i will get the dates.
    Please let me know the solution .
    Thanks in advance.

    Hi,
    Sales order creation date is when u raise a sales order in favor of the customer using VA01.......using ATP logic system purposes the material availability date....
    after saving ur sales order...when u raise the Delivery using VL01n  w.r.t to OR...than u have to perform picking ....In the picking Tab...specify the amount to be picked than press Post Good Issue....means the goods left the company premises ..
    You can the fetch the values using tables-  Use T code   SE12  or SE16
    Vbak-----order header
    Vbap-----order item
    Vbek-----order schedule line
    Likp-----Delivery header
    Lips----Delivery item

  • How to restrict Duplicate Customer Creation in SAP

    Dear all,
    How can we restrict duplicate customer creation in SAP SD.
    We are into retail sector, across the store customers are being created by different employees.
    in this way for many customers more than one business partner records are being created.
    we are looking for a sytem wise functionality to restrict the customer master creation (for Sold to party only) if name1, telephone number and street field values are same, then system has to stop customer creation by giving an error message.
    Is there any standard functionality to address these requirement. If so how could we configure it.
    Any of you can help us to solve the issue. your solutions and help will be highly appreciated.
    thank you.
    Raghu ram.
    Edited by: Raghu Ram on May 26, 2008 5:34 PM

    Hi,
    2 solutions :
    - Procedure manually (no SAP) ;
    - Use extension SAP (SMOD : SAPMF02D) to check with differents data before recording.
    No solution in standard.
    Regards,
    Lionel

  • Regarding custom currency data element issue in custom Table.....

    Hello,
    I am currently working on creation of a Z custom table in SAP. There is data coming from
    mainframe for amount field in the form -9999.9999.
    To store data like this I am creating a custom Z data element with Z domain definition as follows:
    Data type; Curr
    No of characters: 5
    Decimal places: 4
    Sign box is checked.
    Now when I use this Z data elemnt for a firle in custom table, while activating, it asks for table refernce and table field. What do I give it here ?
    Please help.
    Regards,
    Jainam..

    Hi Jainam,
    very basic ABAP knowledge: A field of type CURR isn used to store a currency amount. Every currency field must be connected to a currency key of type CUKY.
    The same concept applies for quantities and units.
    You can spare a lot of trouble if you look at standard tables and programs, copy or use data elements and/or structures from standard.
    If you want to re-invent the world, you may need more than seven days.
    Regards,
    Clemens

  • How to Make Field "Creation Date" Mandatory (in EP Selection Screen)

    Dear experts,
    I am on SRM 7.0.
    In Shopping Cart, i'd like to set Field "Creation Date" as Mandatory Field in EP Selection Screen / Criteria Maintenance.
    Is there BADI or SPRO need to be maintained?
    Thanks & regards,
    Jack
    Edited by: Jack4ever on Aug 9, 2011 7:42 AM
    Edited by: Jack4ever on Aug 9, 2011 7:43 AM

    Hi Jack,
    Not sure if it possible in standard with any customizing but it might be able to achieve this through webdynpro enhancements.
    Regards,
    Prasanna

  • PROBLEM IN CUSTOMER CREATION

    hi
    friends
             when i am creating customer master data by xd01 an erros is coming----
    Sales area INSO ID CP is not defined for customers
    this is my sales area
    i have checked all set up
    sales organisation to distribution channel
    sales organisation to division
    set up sales area
    even in database table TVTA entry is there
    also customer creation screen if i click all sales area tab i sales area is not appearing
    though it is coming
    but it is allowing me to creat customer under company code view through fd01.
    i am working in ecc 6 version this is totally new system & i am configuring sd module 1st time.
    plz give some quick solution 
    ambarish

    Dear Ambarish,
    The Enterprise Structure Configuration you have already checked & as mentioned by you, it sounds to be appropriate.
    As per my understanding, you are facing an issue with Sales Area Tab Pages. There are 2 recommendation, which I can suggest:
    1. Check the configuration setting in VOR1 & VOR2, & ensure that the distribution Channel & Division are maintained appropriately for the Sales Organization.
    2. Also ensure to check Account Group setting:
    2.1.1     Account Group
    2.1.1.1       Maintain Number Range for Account Group
    Use
    The purpose of this activity is to control number range of Account Group.
    Procedure
    Access the activity using one of the following navigation options:
    IMG --> Financial Accounting (New) --> Accounts Receivable and Accounts Payable --> Customer Accounts --> Master Data --> Preparations for Creating Customer Master Data --> Create Number Ranges for Customer Accounts --> Select the Icon to maintain Number Range
    Transaction Code: SPRO
    Data to be maintained:
    No | From      | To | Current No | Ext (Tick in Check Box)
    01 | 0000000001 | 0000099999 | 0 | No
    02 | 0000100000 | 0000299999 | 0 | No
    XX | A | ZZZZZZZZZZ |      Yes
    2.1.1.2       Assign Number Range to Account Group
    Use
    The purpose of this activity is to maintain number range of Account Group.
    Procedure
    Access the activity using one of the following navigation options:
    IMG > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Customer Accounts > Master Data > Preparations for Creating Customer Master Data > Assign Number Ranges to Customer Account Groups
    Transaction Code     : SPRO
    Data to be maintained:
    Group | Name | Number Range
    0001 | Sold-to party | XX
    0002 | Goods recipient | XX
    0003 | Payer | XX
    0004 | Bill-to party | XX
    2.1.1.3       Define Account Groups with Screen Layout (Customers)
    Use
    In this step, you determine the account group of the customer.
    Procedure
    Access the activity using one of the following navigation options:
    IMG > Financial Accounting (New) > Accounts Receivable and Accounts Payable > Customer Accounts > Master Data > Preparations for Creating Customer Master Data > Define Account Groups with Screen Layout (Customers)
    Transaction Code     : SPRO
    The groups indicated below are a few examples. There are many groups in Standard SAP & if we require additional Group, it can be copied from appropriate group & maintained.
    Group | Name
    0001 | Sold-to party
    0002 | Goods recipient
    0003 | Payer
    0004 | Bill-to party
    0005 | Prospective customer
    0006 | Competitor
    Select Sold-to-party > go to Details > Double Click on General data / Company code data / Sales data. It will take to next screen which details Tab Pages of General data / Company code data / Sales data. Double Click on Tab Page for example: Address, Control, Marketing & so on. Here you can maintain whether the field is to be Suppress, Req. Entry, Opt. entry or Display
    IS THIS MANDATORY IN TOTALLY NEW SYSTEM WHEN I WILL BE CREATING ENTERPRISE COMPONENT ALAWAYS I NEED TO COPY ? BECAUSE WHEN I AM COPYING IT FROM STANDARD IT IS PERFORMING AS PER EXPECTION
    It is not Mandatory, but a recommended Practice. The Advantage is when we copy from Standard, by default it updates all relevant table, which sometimes misses out if we are creating without using copy functionality.
    Regards,
    Rajesh Banka
    Edited by: Rajesh Banka on Jun 28, 2008 9:08 PM

  • How can I get the File Creation Date OR Last modification date of the incoming file in my message?

    I need the Last Modification Date and the File creation date of the consumed file in my message, is it possible to do that using a custom pipeline component in decode stage or any other way? The FILE namespace have File creation time that actually gives
    the time the file was dropped in receive location, not the actual creation time. Also this namespace doesn't have the Last Modification Date.

    Yes,
    As per MSDN, "File.FileCreationTime" - "Defines the time that the file was written to the folder that is monitored by the File receive
    adapter."
    So for File Modified DateTime, only option I can think of is create a custom file adapter (updating the File Adapter code from SDK ..\SDK\Samples\AdaptersDevelopment\File Adapter) and access the received file with the code something like the following, which
    you give you the Last Modified date
    string sLastModifiedDate = File.GetLastWriteTime(path).ToString();
    If there are any business requirements which drives you this, then this the only way I can think of. Because you can access the file properties only in adapter, when it passes through adapter file is handled as stream and you will only have context properties
    to access the file related properties.
    If you're looking for implement this for any audit purpose or for your any technical purpose, then you can suggest some alternate than using File updated datetime.
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Maybe you are looking for