Error while assign doc type to sale area

hi,
     while assigning a sale area to a doc type i am getting the following error, " define the sale area(XXXX/YY/zz) as a general sale area?  i have alreadly done "set up sale area" what is general sale area and how to do it? need help.
regards
leo

hi
The Assignment of Sales Areas to Sales Documents
There may be a need to assign sales documents to specific sales areas. For example, a different
sales document is used for all sales orders from a specific sales organization.
Transaction Code OVAZ
You may assign reference sales organizations as well as reference distribution channels and divisions. Do not confuse this referencing with the assignment of common distribution channels and common divisions. The referencing done here is only used by the system to determine which sales documents are permitted for which sales areas.
If all sales document types can be used by all sales areas, leave the assignment fields blank.
check your sales area in
Set up sales area - Enterprise Structure  ® Assignment ® Sales and Distribution ® Set up sales area
T-code: OVXG     
Also check the following setting
OVAM - To Combine distribution channels Sales Document Types     -- Sales and Distribution ® Sales ® Sales Documents ® Sales Document Header ®  Assign Sales Area To Sales Document Types -
choose Combine distribution channels.
OVAN - To Combine division to Sales Document Types      - Sales and Distribution ® Sales ® Sales Documents ® Sales Document Header ®  Assign Sales Area To Sales Document Types -
choose Combine divisions
OVR1 - Define Common Distribution Channels - Sales and Distribution ® Master Data ® Define Common Distribution Channels
OVR2 - Define Common Divisions - Sales and Distribution ® Master Data ® Define Common Divisions
Regards
Vishal
Edited by: WISH on May 6, 2008 7:57 AM

Similar Messages

  • Assign document type to sales area

    Hi,
    I created a new document type and know when i assign this document type to sales area < 1000/10/10 >, its giving an error message " define < 1000/10/10 >first as general sales area" .
    I defined an sales area with that combination. can anyone help me in solving this?
    Thanks,
    Challa

    Hi,
    Step 1.
    IMG (SPRO) -> Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area.
    Step 2.
    IMG (SPRO) -> Sales and Distribution -> Sales -> Sales Documents -> Sales Document Header -> Assign Sales Area To Sales Document Types:
    a. Combine sales organizations
    b. Combine distribution channels
    c. Combine divisions
    d. Assign sales order types permitted for sales areas
    Arthur.

  • Error while posting Customer with Multiple sales areas using DEBMAS05.

    Dear experts,
    We are generating IDOCS vis SAP DS for posting Customer master. The message type used is DEBMAS and basic type is DEBMAS05.  we have a requirement to create 1 customer with multiple sales areas. However, we are ending up with a strange error:  "Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1". Despite the IDOC going into status 51, the customer gets created and the 1st sales area too. the 2nd sales area however is not created!  The IDOC data definitely contains Name1, otherwise the customer would not have been created in the first place.
    As the error message is related to the Address data, I also explored upon exploring this erorr further on the lines of Central Address management where in the ADRMAS and DEBMAS have to be passed together(IDOC Serialiization).  OSS Note (384462)  provides further details about this. One Important point from the note is: 
    "As you have to specify the logical name of the sending system among other things, SAP is not able to make any default settings in the standard systems. When you use the serialization groups delivered as a standard by SAP, the address objects are imported before the master objects.Thus the sequence address data before master objects must only be adhered to if one of the following points applies to your application:
    Such fields are set as required entry fields that are only provided by the BAS in the Customizing of the customer or vendor master.
    For your customers, contact persons exist to which a private address or a different business address is assigned.".
    This is not the case in our situation, as we do not have required entry fields in customizing that are only provided by the BAS, so the error is all the more confusing and I am not too sure what the cause is.
    If someone have experienced the same issue before and have found a solution to it, kindly help out.

    I have found the cause and solution to this problem.
    This error ”Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1” and other similar errors like “Fill all required fields SAPMF02D 0111 ADDR1_DATA-SORT1“ which occurrs during the IDOC posting when there are more than one sales area or company code occurs when the customer number range is set up for Internal numbering. This means, that the number gets generated only at the time of save and upon debugging the IDOC, we found out that after creating the customer and the first sales area/company code record, the segment E1KNA1M is cleared completely! This is the reason, it throws an error which points to a mandatory KNA1 field as missing. (Like NAME1, SORT1 etc.)
    This was resolved by splitting the IDOC into 2.
    The solution is to First post only the KNA1 segment and create the customer.
    In the second step, pass the IDOC with all other segments along with E1KNA1M, but pass only KUNNR in E1KNA1M and the rest of the fields in E1KNA1M as “/”:  you would have got the KUNNR after the first step.
    Important note: This requirement to split the IDOCs does not occur when the customer number is known upfront. (Meaning cases where the customer number is externally generated) I also tested this and created a customer with external numbering and I was able to post more than 1 sales area with the same IDOC. 
    I noticed multiple threads with the same issue, but none of it had a concrete answer. I hope this information will be useful for anyone facing similar problems.
    Cheers
    Venkat

  • Error while assigning Operating concer to Controlling Area

    Hi...
    while I am trying to assign operating concern to controlling area, the system is showing the following error message.
    Diagnosis
    Controlling area 7500 and operating concern 7500 have different fiscal year variants (01 and K4). However, for cost center assessment, settlement, and many other types of postings to Profitability Analysis, the controlling area and the operating concern must have identical fiscal year variants, otherwise error messages or serious data inconsistencies can occur.
    But i already changed fiscal year variant from K4 to 01 in Operating concern and i run the generate operating concern environment also. still the system is showing the same error message.
    Is there anything more i need to do after changing fiscal year variant in Operting concern.
    Please help me.
    Thank you,
    Regards,
    Santosh

    I have got the solution.
    Thank you,
    Regards,
    Santosh

  • BCD_FIELD_OVERFLOW  error while assigning value to dynamic work area

    Hi guys,
                I am trying following code --it uses dynamic table concept.
           LABSTD2 TYPE P DECIMALS  1,
           LABST_2 TYPE P DECIMALS   1,
           LABST_12 TYPE P DECIMALS 1,
           T_ARTMAS-LABST_12 = T_ARTMAS-LABSTD1 + T_ARTMAS-LABSTD2.
           ASSIGN COMPONENT 'LABST_12' OF STRUCTURE <DYN_WA> TO <DYN_FIELD>.
           <DYN_FIELD> = T_ARTMAS-LABST_12.
    Value in T_ARTMAS-LABST_12 in debug was 14690.0....still it gave following error-----
    Runtime Error       BCD_FIELD_OVERFLOW
    Except.                CX_SY_CONVERSION_OVERFLOW
    Even i changed decleartion as follows
    LABST_12 TYPE P lenght 10 DECIMALS 1,
    Still it is giving same problem ...
    Kindly help.

    Hi, I think it has nothing to do with an overflow but something with the code. Try this simple (rather stupied) code:
    TYPES: BEGIN OF ty_line,
            fld1      TYPE p DECIMALS 1,
            fld2      TYPE p DECIMALS 1,
            fld3      TYPE p DECIMALS 1,
          END OF ty_line.
    DATA lv_rec       TYPE ty_line.
    DATA lv_count(1)  TYPE n.
    DATA lv_fld1      TYPE p DECIMALS 1.
    DATA lv_fld2      TYPE p DECIMALS 1.
    DATA lv_fld3      TYPE p DECIMALS 1.
    DATA lv_field     TYPE string.
    FIELD-SYMBOLS: <fs_fld> TYPE any.
    BREAK-POINT.
    lv_fld1 = 15211444 / 10.
    lv_fld2 = 54879072 / 10.
    lv_fld3 = lv_fld1 + lv_fld2.
    DO 3 TIMES.
      lv_count = lv_count + 1.
      CLEAR lv_field.
      CONCATENATE 'lv_rec-fld' lv_count INTO lv_field.
      CONDENSE lv_field NO-GAPS.
      ASSIGN (lv_field) TO <fs_fld>.
      <fs_fld> = lv_fld3.
    ENDDO.
    BREAK-POINT.
    Succes.

  • Error in assigning sales document type to sales area

    Dear All,
    I am trying to assing sales document type to sales area, but system is not allowing me to do that
    I am having this error message
    " First, maintain the sales area <1000/14/00> as a common sales area, and
      then assign allowed sales document types. This means: Complete the IMG
      activity Assign sales area to sales document types in the sequence
      entered here."
    Note:
    I have never created a distribution channel "14" and division "00" then why system is asking me to define this as a common sales area.
    How can I maintain common sales area ?

    Dear Ali,
    1.You go to VOR1 transaction here you check what is the distribution channel assigned as common distribution channel for your sales organisation and distribution channel ,if it is improper then maintain correct Distribution channel.
    2.You go to VOR2 transaction here you check what is the division assigned as common division to your sales organisation and Divisionif ,it is improper then maintain correct Division.
    3.You go to OVAO transaction here you assign reference sales organisation to your sales organisations.
    4.You go to OVAM transaction here you assign reference distribution channel to your sales organisation and common distribution channel.
    5.You go to OVAN transaction here you assign reference division to your sales organisation and common division.
    6.Finally you assin sales document type to your referenced sales area.
    I hope this will help you,
    Regards,
    Murali.
    Edited by: Murali Mohan.Tallapaneni on Nov 11, 2008 5:58 AM

  • Error while assigning dates to associative array of date type

    Hi All,
    I am facing the issue while assigning dates to associative array of date type:
    Oracle Version:
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
    PL/SQL Release 10.2.0.1.0 - Production
    CORE    10.2.0.1.0      Production
    TNS for Linux: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    Stored procedure i am trying to write is as following
    create or replace procedure jp1 (
    p_start_date date default trunc(sysdate,'MM')
    , p_end_date date default trunc(sysdate)
    is
    l_no_of_days number;
    type t_date_id is table of date
    index by pls_integer;
    l_date_id_arr t_date_id;
    begin
    l_no_of_days := p_end_date - p_start_date;
    for i in 0
    .. l_no_of_days - 1
    loop
        l_date_id_arr := p_start_date + i;
        dbms_output.put_line(p_start_date + i);
    end loop;
    end;
    I am getting error at line 14 while compiling this. and the error message is as following:
    Errors for PROCEDURE JP1:
    LINE/COL ERROR
    14/5     PL/SQL: Statement ignored
    14/22    PLS-00382: expression is of wrong type
    So while investigating this i tried to output the value of (p_start_date + i) using dbms_output.put_line and the output is date itself.
    create or replace procedure jp1 (
    p_start_date date default trunc(sysdate,'MM')
    , p_end_date date default trunc(sysdate)
    is
    l_no_of_days number;
    type t_date_id is table of date
    index by pls_integer;
    l_date_id_arr t_date_id;
    begin
    l_no_of_days := p_end_date - p_start_date;
    for i in 0 .. l_no_of_days-1
    loop
        --l_date_id_arr := p_start_date + i;
        dbms_output.put_line(p_start_date + i);
    end loop;
    end;
    output of the
    exec jp1
    is as following:
    01-DEC-13
    02-DEC-13
    03-DEC-13
    04-DEC-13
    05-DEC-13
    06-DEC-13
    07-DEC-13
    08-DEC-13
    09-DEC-13
    10-DEC-13
    11-DEC-13
    12-DEC-13
    13-DEC-13
    14-DEC-13
    15-DEC-13
    16-DEC-13
    17-DEC-13
    18-DEC-13
    I see the output as date itself. so why it is throwing error while assigning the same to associative array of date type.
    I tried to google also for the same but to no avail.
    Any help in this regard is appreciated or any pointer some other thread on internet or in this forum.
    Thanks in advance
    Jagdeep Sangwan

    Read about associative arrays :
    create or replace procedure jp1 (
    p_start_date date default trunc(sysdate,'MM')
    , p_end_date date default trunc(sysdate)
    ) is
    l_no_of_days number;
    type t_date_id is table of date
    index by pls_integer;
    l_date_id_arr t_date_id;
    begin
    l_no_of_days := p_end_date - p_start_date;
    for i in 0..l_no_of_days - 1
    loop
        l_date_id_arr(i) := p_start_date + i;
        dbms_output.put_line(p_start_date + i);
    end loop;
    end;
    Ramin Hashimzade

  • Error: EDI: Error while assigning IDoc number

    Hi Everybody,
    using XI 3.0 on Linux 64 bit SLES9 with Oracle I got some probleme sending messages from mq series to sap:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!-- Call Adapter
    -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
    SOAP:mustUnderstand="">
    <SAP:Category>XIAdapter</SAP:Category>
    <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
    <SAP:P1>EDI: Error while assigning IDoc number</SAP:P1>
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>Error: EDI: Error while assigning IDoc number</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    What is missing here?
    Kind regards,
    Michael

    Hi Jayakrishnan,
    thanks a lot for your answer.
    SM59 is working finde. In IDX1 I got the the correct RFC destination entered and a double click works fine also.
    The other way around R3 -> XI -> mq series is working fine. Here we are trying mq -> XI -> R3 and it stops sending from XI to R/3.
    How to check the IDOC type?
    Regards,
    Michael

  • Error while filling setup table for Sales

    Dear Team,
    We are getting following error while filling setup table for Sales (application component 11) and for Billing (application component 13),
    application component 11
    Error determining rate: foreign curr.  local curr. INR date 08.10.2007 (doc. 673624) (JOB - RMCVNEUA)
    Message No M2810
    application component 13
    Billing document 480050000: error determining stats. currency rate (no updating)
    More faulty documents found than the tolerated 0000000000 (JOB - RMCVNEUF)
    I have seen lot of threads based on this but all r showing diffrenent currency to INR but for the above mentioned documents currency is in INR only so why it is showing the error I am not able to determine.
    If anybody faced this problem kindly reply to this.
    Best Regards,
    SG

    Hi There,
    Might be your using a wrong document number.
    I mean if your using the 11 you should use only Sales document number and for 13 you should only use billing document number.
    If you use vice versa that error will throw.
    Regards,
    MQ

  • Error while creating Project Change Control - You are trying to access a page that is no longer active.

    Hi there
    We are on Release 12.2.4 (on Linux x86-64) and getting the following error while assigning the Agreement to a Change Control's Action Item. As a result of this we are unable to proceed ahead with completing the Project Change Control process.
    Any help will be greatly appreciated.
    Steps to reproduce
    Navigation - Project SU Vision Services Responsibility > Project > Control > Change Orders
    1. Create a new Change Order > Create a new Action > Impact > Check Financial Impact checkbox
    2. Under the 'Agreement Information' choose the Funding Agreement. Following error is thrown:
    You are trying to access a page that is no longer active.
    - The referring page may have come from a previous session. Please select Home to proceed.
    3. I tried clearing the cache, bounced Apache, and even restarted the entire Application Tier. The error doesn't go away.
    Regards
    Kabeer Khan

    Hi there
    We are on Release 12.2.4 (on Linux x86-64) and getting the following error while assigning the Agreement to a Change Control's Action Item. As a result of this we are unable to proceed ahead with completing the Project Change Control process.
    Any help will be greatly appreciated.
    Steps to reproduce
    Navigation - Project SU Vision Services Responsibility > Project > Control > Change Orders
    1. Create a new Change Order > Create a new Action > Impact > Check Financial Impact checkbox
    2. Under the 'Agreement Information' choose the Funding Agreement. Following error is thrown:
    You are trying to access a page that is no longer active.
    - The referring page may have come from a previous session. Please select Home to proceed.
    3. I tried clearing the cache, bounced Apache, and even restarted the entire Application Tier. The error doesn't go away.
    Regards
    Kabeer Khan

  • Getting error while creating condition type in SPRO

    Hi ,
    can somebdy tell me why i am getting the following error while creating condition type in SPRO
    No valid change license available for message /sapcnd/
    and also while rule determination using condition type we are getting the following error.
    system error:system cannot read the structure for table
    reg
    venkat

    Hi Venkat,
    Do you have the error number code!?
    Regards,
    Michel  Bohn

  • Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number

    Hi,
    I'm attempting to create a simple interface which converts cutomer data from a flat file and loads it into a SAP enterprise system as an DEBMAS06 IDoc type. I am getting the error message Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number in the XI message monitor.
    Has anyone come accross this error before and if so, what is the resolution???
    Thanks, in advance,
    Pete

    Hi Peter,
    did you fixed it?
    How did you?
    got the same problem
    Kind regards,
    Michael

  • Error while assigning Decimal Attribute to PA

    Hi,
    I am receiving an error while assigning a decimal attribute to the planning area. I am attaching the screen shot below . Can anybody shade some light on this error, what could be the reason ?
    Thanks in advance.
    Regards,
    Chandan

    One cannot have a decimal attribute as the 'attribute' in planning. A decimal attribute can always be marked as a key figure.
    For eg: Price. It cant be a attribute of planning area (like Plant, product).

  • Error while assignment of Paying Co Code in FBZP

    HI friends,
    I am getting the following error while assigning Paying Co Code in FBZP -
    Company code 7144 is not permitted as the paying company code
    Message no. F3063
    Diagnosis
    The paying company code and the company code on whose behalf the payment is being made must be in the same country, have the same local currency, and display the same currencies managed in parallel. The setting regarding extended withholding tax functions (active or not active) must also be identical for both company codes.
    System Response
    The entry is not accepted since these requirements are not met.
    Procedure
    Correct your entry.bold**
    The reason for the same isCompany code 7144 is not permitted as the paying company code
    Message no. F3063
    Diagnosis
    The paying company code and the company code on whose behalf the payment is being made must be in the same country, have the same local currency, and display the same currencies managed in parallel. The setting regarding extended withholding tax functions (active or not active) must also be identical for both company codes.
    System Response
    The entry is not accepted since these requirements are not met.
    Procedure
    Correct your entry.
    The scenario is that one company code is making the payments for the other. However, the 2 companies are based in different countries. Hence, system is not allowing this assignment.
    Has anyone come across this scenario? Is there any other wayaround for this which can result in Intercompany postings.
    If we assign the Paying Company Code in the Variant screen in F110( instead of FBZP), will that work? I have tried the same but it doesnt work that way.
    Any help on this will be highly appreciated.
    Thanks in advance,
    Hrishi

    - i am not sure if its possible; help on FBZP clearly states this
    +++++++++++++++++
    The paying company code and the company code to which payment is made must be in the same country and have the same local currency and parallel currencies. In addition, both company codes must have the same settings for enhanced withholding tax functions (active or not active).
    Only the valid company codes for the paying company code are included in the possible entries.
    +++++++++++++++++
    Rgds.

  • Read Only Access while assigning Analysis Types and Reports in User/Group

    Hi Team,
    While Assigning Analysis Type,Reports and Workbooks to User "Read" option is not enabled. It is not working and as soon as we select analysis type ,Only one option is editable "Create/Update/Delete". The other two Option is always there as display "Read" and "Execute" . Execute might work with "Scripts template" but "READ" should work for analysis types and Reports.
    We are already struggling with "Read Only" Access in security filter as its not working now.
    Thanks
    Edited by: user7918731 on Mar 2, 2011 11:22 AM

    The behavior for Analysis type, workbook and script as follow:-
    The Analysis type create/update/delete option will be enabled, read and execute option will be disabled by default.
    The report workbook read option will be enabled, and other two options will be disabled.
    The script execute option will be enabled, and other two option’s will be disabled.
    For providing “Read Only” access in security filter, Switch to the administration tab, Click on Security Filters, Click on Add button, Open Create Security Filter window, Select the access level to Read Only and select user in assigned user , Click on ok.
    It should work.

Maybe you are looking for