Check Duplicate PO No. By Sales Document Type with irrespective of customer

Dear Team,
Requirement: PO No. shouldn't repeat in the particular Sales document type.
Currently :
1. I have set the configuration in VOV8, Check po no.--A
2.and set the warning to error by using T-code OVAH (E)
This setting satisfy only ---PO no. is check's by customer wise in that particular sales document type..(not for other customer)
I mean if i use the same PO No. with other customer in same sales document type it is accepting(it is not giving error message)
so I need here to check PO no. by sales document type irrespective of customer nos.
So please guide me regarding this
Thanks
YRH SP

Hello SP,
The system behaviour is correct, let us take an example.
I have a customer and he raises a purchase order and sends us the info.. against which we place a sales order and this PO number provided by customer is added in the sales order and it is used for tracking.. however when hewants to place a new order he will  raise a different PO.. it will hav a different PO number...
Having said that there are chances that two different customers are using the same number range for their purchase order documents and place order with same PO numbers.. in this case system shouldn't ristrict us from creating sales order for both of them, hence system checks based on customer and not based on sales doc type..
as far as my understanding gose you need to go in for custom development to fulfill your requirement.
Regards
Naveen

Similar Messages

  • Sales Document type not defined

    Hi
    I am working on an interface. Design is like below
    Purchase Order->File Adapter->XI (BPM)->RFC Adapter->Sales Order in R/3
    When I am trying to cretae a sales document in R/3, I am getting a message back from R/3 saying 'Sales Document is not defined'. But when Checked in R/3, that sales document type is existing. I don't see any Mapping execption in monitoring, but I am receiveing this message back from R/3
    Any feedback will be highly appreciate.
    Cheers
    Rajiv P

    Hi
    Well initially it was a value-mapping problem. It is possible to debug a BAPI/RFC from XI. If it is possible, the please advise me of the procedure. My XI is working fine but I am getting a message back from R/3 as below. Any feedback will be highly appreciated
    <?xml version="1.0" encoding="UTF-8" ?>
    - <rfc:BAPI_SALESORDER_PROXY_CREATE.Response xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
      <E_SALESDOCUMENT_EX />
      <E_STATUS>E</E_STATUS>
    - <RETURN>
    - <item>
      <TYPE>S</TYPE>
      <ID>V4</ID>
      <NUMBER>233</NUMBER>
      <MESSAGE>SALES_HEADER_IN has been processed successfully</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1>VBAKKOM</MESSAGE_V1>
      <MESSAGE_V2 />
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER>SALES_HEADER_IN</PARAMETER>
      <ROW>0</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>V1</ID>
      <NUMBER>384</NUMBER>
      <MESSAGE>Sales unit ****** is not defined for item 000000</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1>******</MESSAGE_V1>
      <MESSAGE_V2>000000</MESSAGE_V2>
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER>SALES_ITEM_IN</PARAMETER>
      <ROW>1</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>V4</ID>
      <NUMBER>248</NUMBER>
      <MESSAGE>Error in SALES_ITEM_IN 000001</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1>VBAPKOM</MESSAGE_V1>
      <MESSAGE_V2>000001</MESSAGE_V2>
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER>SALES_ITEM_IN</PARAMETER>
      <ROW>1</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>V4</ID>
      <NUMBER>219</NUMBER>
      <MESSAGE>Sales document was not changed</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1 />
      <MESSAGE_V2>000001</MESSAGE_V2>
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER />
      <ROW>0</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
    - <item>
      <TYPE>E</TYPE>
      <ID>C_</ID>
      <NUMBER>005</NUMBER>
      <MESSAGE>The object references could not be written to the CRMKEY</MESSAGE>
      <LOG_NO />
      <LOG_MSG_NO>000000</LOG_MSG_NO>
      <MESSAGE_V1 />
      <MESSAGE_V2 />
      <MESSAGE_V3 />
      <MESSAGE_V4 />
      <PARAMETER />
      <ROW>0</ROW>
      <FIELD />
      <SYSTEM>UD1CLNT010</SYSTEM>
      </item>
      </RETURN>
      <TI_EXTENSIONIN />
      <TI_ORDER_CCARD />
      <TI_ORDER_CFGS_BLOB />
      <TI_ORDER_CFGS_INST />
      <TI_ORDER_CFGS_PART_OF />
      <TI_ORDER_CFGS_REF />
      <TI_ORDER_CFGS_REFINST />
      <TI_ORDER_CFGS_VALUE />
      <TI_ORDER_CFGS_VK />
    - <TI_ORDER_CONDITIONS_IN>
    - <item>
      <ITM_NUMBER>000001</ITM_NUMBER>
      <COND_ST_NO>000</COND_ST_NO>
      <COND_COUNT>00</COND_COUNT>
      <COND_TYPE>EDI1</COND_TYPE>
      <COND_VALUE>57.600000000</COND_VALUE>
      <CURRENCY>AUD</CURRENCY>
      <COND_UNIT />
      <COND_P_UNT>1</COND_P_UNT>
      <CURR_ISO />
      <CD_UNT_ISO />
      <REFOBJTYPE />
      <REFOBJKEY />
      <REFLOGSYS />
      <APPLICATIO />

  • Authority-Check for Sales Document Type

    Hi All...
    I would like to incorporate Authority-Chack for the field Sales Document Type "TVAK-AURT"...
    Can any one give me the sample code or exact code..?
    I have written Authority-check for Sales Organization as follows...
    authority-check object 'V_VBAK_VKO'
                     id 'VKORG' field i_sales-vkorg
                     id 'VTWEG' field '00'
                     id 'SPART' field '00'
                     id 'ACTVT' field '03'.
            if sy-subrc ne 0.
            delete i_sales.
    BUT HOW TO WRITE FOR V_VBAK_AAT..??

    Please check object: <b>V_VBAK_AAT</b> for the same.
    EG:
    authority-check object 'V_VBAK_AAT'
    id 'AUART' field L_AUART
    id 'ACTVT' field '03'.
    Kind Regards
    Eswar
    Message was edited by: Eswar Rao  Boddeti

  • Checking rule for sales document types

    Hi,
    Can I change the cheking rule for a sales document type? Where could I change it? or should I build Z table?
    Thanks!

    7,
    Checking rule is hard-coded into standard SAP sales doc maintenance programs.  For SOs, it is A or A* (depending on the stock type).  For Deliveries, it is B or B*.  There is no way to use standard configuration to alter the rule within SD.
    Best Regards,
    DB49

  • Billing block for customer for sales document type OR

    Hi
    I want to block a customer for a particular sales document type OR
    How to do it?
    Regards

    Hi Nikhil
    There is a field called "Check Partner Auth.", but it is necessary to create the order from a contract. This field is in sales document customizing VOV8.
    SAP Documentation:
    Check partner authorizations
    This check determines whether a partner is authorized to release against a contract.
    Procedure
    Here you can specify whether the check is to be performed against the partners in the contract or the partners in the customer hierarchy. If you do not want the check to be performed, leave the field blank.
    When you create a release order for a contract, the system determines whether a partner is authorized to release against the contract. The check is performed at header level. Depending on the rule you enter in this field, the system checks against one of the following:
    Partners in the contract
    If the partner has the partner function AG (sold-to party) or AA (sold-to party authorized to release) in the contract, the system accepts the partner as the sold-to party for the release order.
    Partners in the hierarchy
    If the sold-to party of the contract is at a higher level in the customer hierarchy to the partner who wants to release against the contract, the system accepts the partner as the sold-to party for the release order.
    Note
    If you create a contract with reference to another contract, the system does not run a check and it copies all the partners created in the target contract. If you do not want it to do this, use copying control in Customizing to change it.
    Regards.
    Mikel

  • SAP SD Material Determination not reflected in assigned sales document type

    Hi Experts,
    I have implemented customized material determination, with requirement to change the UoM of the entered material, from GJ to MJ. I have assigned the procedure to 3 document types:
    1. sales order type
    2. credit memo request
    3. debit memo request
    However, this setup is only reflected in the 1st sales document assigned with the procedure. It is not reflected in the credit or debit memo request.
    I have turned on the material determination analysis in sales order. Per my checking during credit memo request creation, the analysis indicated that the condition is found successfully. But the UoM did not change in the document.
    Please assist.
    Thank you.
    HJMY
    Edited by: HJMY on Sep 20, 2011 1:24 PM

    Hi Ravi,
    Thx for your reply.
    But I am creating credit/debit memo request without reference to billing.
    When I create credit/debit memo request, the material determination is triggered.
    Per my test today for credit memo request, I found that the material determination is triggered.
    However, the substition UoM is not reflected in the credit memo request document.
    The result is reflected only in sales order.
    Please help.
    Edited by: HJMY on Sep 21, 2011 3:28 AM

  • Issue With Sales Document Type in BW.

    Dear Experts,
    I am facing an Issue with Sales Document Type(Object name is 0DOC_TYPE).
    when i am loading data from R/3 to BW It is converting Sales Document type as follow
    Sales Document Type in R/3                         Sales Document Type in BW
    OR                                                                        TA
    CR                                                                        G2
    DR                                                                        L2
    I check with an ABAPer and he told that there is conversion exit for this Object so that's why it is converting when sending to BW. But the user wants to see in Report same as it is in R/3 like OR, CR DR ... etc.
    I have done some investigation and found that the conversion exit (CONVERSION_EXIT_AUART_INPUT and CONVERSION_EXIT_AUART_OUTPUT) are converting the values based in the table TAUUM
    The staructure of TAUUM is
    MANDT(Client)  SPRAS(Language) AUART(Sales document type (not converted)   AUART_SPR(Language key for sales document type)
    and values are
    100 E TA OR
    100 E G2 CR
    etc....
    The same Conversion exits(CONVERSION_EXIT_AUART_INPUT and CONVERSION_EXIT_AUART_OUTPUT) and table TAUUM are available in BW as well. So i thought I can Use InfoObject 0DOC_TYPE by changing it's conversion Routine as AUART(which runs based on the above mentioned conversion exits).
    but the the problem is table TAUUM(Pool Table) does't have any data in BW.
    So can anyone tell me is there any option to load data into table TAUUM from R/3 or any other option to solve this issue.
    Your ideas will really help's me.
    Thanks in advance,
    Dara.

    Hi Venkat,
    Thanks a lot for your immediate response.
    The InfoObject 0DOC_TYPE was without conversion exit by default. but when data coming from R/3 it is converting and sending to BW So that's why i am planning to use conversion exit "AUART" in the info Object.
    I checked data in R/3 using RSA3 it is showing sales document type as "OR" and for the same transaction data when i checked in PSA it is showing as "TA".
    Could you please let me know if there any other options.
    Thanks in advance,
    Dara.

  • Reading the description of Sales document type and Profit centre from table

    Hi
    I want to print the description of Sales document type and Profit center on output
    I have checked in table TVAK and CEPC  but i am unable to pick description against the code
    Can anyone please suggest from where can i capture the description of sales document type and profit centre
    Thanks and Regards
    Sunil Srinivasan

    Hi
    If you have the sales document number VBELN then pass this VBELN in to table VBAK and you can get the sales document type VBAK-AUART.
    Now pass the same VBELN to VBAP table here you can get the Profit Center VBAP-PRCTR
    For sales Document type description you pass the VBAK-AUART values into table TVAKT  table and get the values for TVAKT-BEZEI is you sales document type description
    For Profit center description goto table CEPCT and enter the profit center you will get the
    KTEXT
    LTEXT
    MCTXT
    regards
    Prashanth
    Edited by: Prashanth@SD on Oct 25, 2010 12:29 PM

  • Disable sales document type from COPA? Is it possible?

    Hello gurus
    We have a situation where we dont wish system to create Profitability Analysis segments for items belonging to the quotes that we are creating?
    Is is possible to disable PA assignments by a sales document type and or item categories?
    Many thanks
    Jai

    The best person to guide for this would be your FICO consultant.
    Anyhow, check following thread for some understanding:
    How to deactivate COPA
    Note: Check all possible result before deactivating it on your system.
    Check Following link for understanding
    [Business Area Vs. Profit Center Vs. Profitability Segment|http://sapdocs.info/sap/fico/business-area-vs-profit-center-vs-profitability-segment/]
    [Profit Center Default In Sales Order|http://www.sap-img.com/sap-sd/profit-center-default-in-sales-order.htm]
    Thanks & Regards
    JP

  • Why should we create a new sales document type

    I want to know the actual reason behind creating new sales document type when the standard document is available

    General procedure when setting up sales document types
    You have three options for configuring new sales document types:
    1. Change an existing sales document type.
    2. Copy an existing sales document type and change it according to your requirements.
    3. Create a new sales document type.
    Recommendation
    For small changes, SAP recommends that you copy similar existing sales document types in the standard SAP R/3 System and make the appropriate changes. Small changes might, for example, be, a changed description, a different number range or a different increment for the numbering of items.  The name is to start with the letter Z as SAP keeps this range free in the standard system.
    This procedure has the following advantages:
    All the specifications of the existing sales document type are copied. In particular, the data concerning, for example, partner determination, pricing or document flow which you would otherwise have to edit manually is copied.
    You can test your new sales document types in respect to the settings made without having to edit the other settings.
    When copying sales document types, item categories and schedule line categories, the SAP R/3 System automatically creates a log with the copied data. Using the log, you can check whether all of the copied data applies to your sales document type or whether you need to make changes.
    Actions
    1. If you need to make further changes, you should define new sales document types. To do this, you enter an alphanumeric key with a maximum of four characters for a sales document type and a textual description for the key.
    2. Maintain the specifications on the detail screen according to your requirements.

  • 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

  • Unable to assign new sales document type to sales area.

    Hi,
    I had created new sales document type. While I assigning to sales area it showing error " Define <XXX/XX/XX > first as a general sales area." I had already created sales area in enterprise structure. I had configured Combine sales org, dist channel & division also. Kindly help me on this.
    Regards
    Nagendra

    Hi,
    I hope you have maintained following Settings:
    SPRO --> IMG --> Enterprise Structure --> Definition --> Sales and Distribution --> Define, copy, delete, check Sales Org
    SPRO --> IMG --> Enterprise Structure --> Definition --> Sales and Distribution --> Define, copy, delete, check Distribution Channel
    SPRO --> IMG --> Enterprise Structure --> Definition --> Logistics - General --> Define, copy, delete, check Distribution Channel
    SPRO --> IMG --> Enterprise Structure --> Definition --> Logistics - General --> Define, copy, delete, check Plant (In case)
    SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Sales Org. to Company Code
    SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Dist. Channel to Sales Org.
    SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Divsion to Sales Org.
    SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Set up Sales Area
    SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Sales Org.-Dist. Channel-Plant
    SPRO --> IMG --> Sales and Distribution --> Master Data --> Define Common Dist. Channel
    SPRO --> IMG --> Sales and Distribution --> Master Data --> Define Common Division
    SPRO --> IMG --> Sales and Distribution Channel --> Sales Document Header --> Define Sales Doc. Type
    SPRO --> IMG --> Sales and Distribution Channel --> Sales Document Header --> Define No. range Sales Doc.
    SPRO --> IMG --> Sales and Distribution Channel --> Sales Document Header --> Assign Sales Area to Sales Doc. type
    Best Regards,
    Amit

  • BLOCK A SALES DOCUMENT TYPE

    HI FRIENDS,
    WE WANT TO BLOCK PERTICULAR DOCUMENT TYPE FOR A SALES AREA FOR PERTICULAR PERIOD. IS THERE ANY SETINGS? PLEASE CONFIRM, IT'S URGENT.
    KAUSHIK

    Hello,
    you vcan assign sales area to the document type.
    Please go into the customizing the following menu path:
    > PRO
    > Sales and Distribution
    > Sales Document
    > Sales Document Header
    > Assign Sales Area To Sales Document Types
    Assign Sales Area To Sales Document Types
    In this menu option, you allocate the allowed order types to each sales area group.
    You do not need to make any entries at all if all the sales order types are allowed for each of your sales areas.
    If you wish to check allowed sales document types, you must set up common sales areas. This means you must define common sales organizations, common distribution channels and common divisions. If, for example, you have define common divisions, then you must also define common distribution channels and sales organizations.
    Example 1 (simplest case):
    Only the sales document type "standard order" (OR) should be allowed for a specific sales area <0001/01/01> (that means: sales organization 0001, distribution channel 01, division 01). The following activities are required for this:
    1.1) Activity "group together sales organizations":
         Sales org.  Ref.sales org.
         0001        0001
    1.2) Activity "group together distribution channel":
         Sales org.  Distr.ch.  Distr.ch.  Doc.type
         0001        01         01
    1.3) Activity "group together divisions":
         Sales org.  Division  Division Doc.type
         0001        01        01
    1.4) Activity "assign allowed order types to sales areas":
         Ref.sales  Distr.ch.  Division Sales doc.type
         0001       01         01       OR
    Example 2:
    The above settings should also be used for the sales area
    I hope that the information are helpful.
    Regards
    Claudia
    Edited by: Claudia Neudeck on Jul 23, 2008 3:47 PM

  • Sales docu type ZLCO Vs Billing type ZLR - Error

    Hi Experts,
    Pls help me in the following scenario : I made one sales order with order type ZLCO.(Order relevant Billing type) maintained in VOV8, when i create billing for this order i am getting the following error  Sales document type ZLCO cannot be invoiced with billing type ZLR.
    Regs.
    SR

    Hi,
    Pls check whether you have maintained the following settings:
    Did you maintain the Billing type ZLR in order related billing type in VOV8 .
    Did you maintain the billing relevance B     (Relevant for order-related billing - status acc.to order qty) in VOV7.
    Did you maintain the copy control from Sales document type ZLCO to billing type ZLR in VTFA.
    Regards
    M. Lakshmi Narasimhan

  • Field Exit for Sales Document Type in VA01

    hi
       i want to do field exit for Sales Document Type in VA01.
    but i dont know to find the correct exit.
    pls tell the exit name and the steps to find it.
    thank u

    Hi,
    Goto this link u will get the information u required....
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9cd334f3-0a01-0010-d884-f56120039915
    Check the numerous threads that already exist in SDN :
    CMOD and SMOD
    http://www.sap-img.com/abap/what-is-user-exits.htm
    Regards,
    Manish

Maybe you are looking for

  • Adobe Reader 9 won't open some files -- jp2klib.dll

    I've had this problem for some time, and I think I've at least narrowed it down a bit. The problem is that some (but not all) PDF files cannot be opened in Adobe Reader 9.x on some computers, though they open fine on others. When you click on a probl

  • Using SQL Query for page item source does not insert populated value

    Hi All, Following are the attribute details of a certain page item on an edit form: Display As: Text Field Page Item Source Type: SQL Query Source value Expression: SELECT a from tab where id = 'ABC' Although the field appears populated on the screen

  • Insert/link a PDF file in MM02 transaction.

    hi I would like to know if it is possible to insert/link a PDF file in MM02 transaction. Please let me now something.

  • Delete Content area Error

    Error: An unexpected error has occurred (WWS-32100) ORA-2292: ORA-02292: integrity constraint (PORTAL30.WWSBR_URL_SITELANG_FK) violated - child record found (WWC-36000) Delete the record manual creates this Error: table wwsbr_sites delete ID 53 Inhal

  • Archivo de datos SAP

    Buenos días, quisiera saber si alguno de ustedes ha usado alguna vez la opción de asistente para el archivo de datos, lo que sucede es lo siguiente: Estamos usando la versión de SAP 9.0 PL10 llevamos 4 años con sap hemos visto que esta opción permite