Duplicate PO in sales order?

Hello Friends,
Requirement is to get a duplicate PO warning message in sales order when the SO is created in 2 different distribution channels, we are using same sales org./div but different dist. Channel.
Currently we have a setting  in place to give warning message when duplicate PO is created in same dist. Channel.which is working fine.I don't know how I can accomplish the above reqmnt. Appreciate if you could please advice how I can deal with the above request.
Thanks in advance.
MIke

I don't know if i have understood your query correctly.
You have this PO field in the Sales Order Header, and there should be some coding already in your system, in standard MV45AFZZ exit to check if the customer PO Number is already referenced in some earlier order by comparing with the Distribution Channel.
A simple coding can be done here which will check if the PO number has been referred earlier, then produce a warning message, indicating the order number and the sales area.
The values can be picked from VBAK/VBAP.
You can also have a Z Table created where the sales order number and the PO number get posted to, upon saving the sales order..
Later on everytime you create an order, the system can always validate this Z table to check if the PO number exists in coordination with some sales order or not. If the system finds that the PO number has been used already, a warning message can be brought in.
Hope this helps.
Regards,
Vivek

Similar Messages

  • Duplicate records for Sale Order Cycle Report(excluding item level detail)

    I have posted this issue in number of forums but till today no one is able to answer it correctly.Here it is:
    I need to create a report which I think most of the sd consultants have also done it.It basically covers sales order cycle without item lvel detail such as:
    Sale Order No -- Sales Order Date-- Delivery No-- Delivery Date
    Now as we all know ,sales orders and deliveries are connected through item table which means in the output I will get duplicate rows for the report above.For Example, if a sales order share 3 items with the delivery then we will get 3 exact duplicate rows in the report.
    What can be the best solution?connecting through VBFA has alos same result as it also has item level details.
    I need a good solution.This a common report and there must be some solution

    Hiiii,
    It is standard SAP rule that system will catch the document flow (document link history) at item level.
    Now your problem that you dont want to show the line item based report because of duplicacy.
    Try this.
    Brows table VBFA -
    In screen selection select the following......
    1. Subsiquent document category
    2. Preceding item
    select "J" in Subsiquent document category
    and "000010" in Preceding item  then execute the table.
    Now system will not show multple line item based delivery report. so No duplicacy will be there
    Regards
    Shambhu Sarkar

  • Report for duplicate PO and Sales Order

    Hi All,
    I need to find out two reorts for below purpose:
    1) Report that will give me list of all PO's which has duplicate sales order against them .
    2) Report that will give me list of  all sales order which has duplicate PO's .
    I know there is a report SDD1, but it is not giving required reports.
    Regards
    Nidhi

    Hi Nidhi,
    As you told SDD1 will work. But what fields you are expecting.
    Regards,
    Madhu.

  • Duplicate Overheads in Sales Order costing

    Hi Experts,
    We are facing an issue in VA02 and VA22. Here we are getting duplicate overheads in costing as below image:
    Kindly help. I am an ABAPer and debugged for it but could not find any bug. So this functional approach could help, I thought.
    Thank you so much.
    Jayaprakash

    As Warren mentioned, you need to work with your CO specialist. To analyze the issue, more information on the process is needed. If the process involves sell from stock, then take a look at OSS 1972019 - Sales Order Costing: Duplicate Overhead Rates for Sell-from-Stock
    Or if it is a re-work scenario, you may need to implement OSS 1844495 - Rework for product costing: duplicate overheads and  1204894 - Rework sales order costing: Duplicate process costs
    Regards,

  • Is it possible to avoid duplicate material in Sale order creation

    Dear SD gurus
    Is it possible to avoid material duplication in va01 sale order creation. For amendment purpose the marketing user making new line item with amended qty instead of quantity change. kindly advise me to solve the problem.
    Thanks & Regards
    R.Udayakumar

    HI,
    There's no alternative to user disciplibe . Business reqt are sometimes like this only
    what you can do is use exit mv45afzz in saels order and put coding logic . this will surely work.
    {Removed by Moderator}
    regards
    Edited by: Lakshmipathi on Aug 29, 2009 6:13 PM

  • To avoid Duplicate material entry while making sales order by VA01

    Sir / Madam,
    While making sales order by VA01 , duplicate material also accepted by system .There should be no duplicate material in sales order list.
    please suggest solution.
    Thanks.

    Hi,
    You should use userexit USEREXIT_SAVE_DOCUMENT_PREPARE in MV45AFZZ and not USEREXIT_SAVE_DOCUMENT,.The reason behind this is prepare userexit is activated just before saving the document,so at the time of saving if the logic which you will give is not satisfied then you can set warning or error in the code.
    Rewards points if useful.
    Regads,
    Amrish Purohit
    Message was edited by:
            AMRISH PUROHIT

  • User Exit during Sales Order Creation - New Line Item needed

    I have a situation during the process of sales order creation. If a Material in a line item has say 27 EA and the Base Unit is EA. But the Sales Unit is CSE. Then whenever the user enters 27 EA and presses enter he should get two line items.
    The first line item needs to convert to maximum number of CSE posible and the rest will be the second line item with the remaining EA. The order isn't important but that is what is needed. Question is how do I approach this problem and code my user exit accordingly and where do I code it.
    I was looking at SAPMV45A and saw the program MV45AIZZ which is meant as a user exit for any PAI event handling. If anybody has encountered this kind of requirement can you please share your view on this.
    I will definitely reward points for useful answers.
    Clark

    Hello Mahendra
    The requirement is as follows :
    PART 1:
    Sales Order Enter: 
    1.     When a line item is entered on a sales order (VA01 or VA02), at enter, check the sales unit of measure (VBAP-VRKME).
    •     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP.  TANN are free goods that should not be considered for consolidation.  TAPS & ZTAP are lower level materials as a result of product selection.  They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
    •     Do not check items where VRKME <> EA
    2.     If VRKME = EA, go to MARM for MATNR.
    3.     Go to record where alternate unit of measure (MEINH) = CSE, get the value from the numerator field (UMREZ).
    4.     Divide the order quantity (VBEP-WMENG) by UMREZ.
    5.     If the result is greater than 1.0, the customer has ordered more than one case and a new line item needs to be added to the sales order for the case quantity.
    6.     Add a new line to VBAP for the same material with the case quantity.  If not a whole value, the remainder of eaches (bottles) should update the qty on the first item on VBAP.
    •     Part 1 is relevant for order types ZCA, ZOR, ZSO, RE, ZSM
    PART 2:
    Batch Job to run prior to the Delivery Due List:
    1.     Read VBUK for Delivery Status (LFSTK) = A (delivery not processed).  Get all of the document numbers (VBELN).
    2.     Go to VBEP for those document numbers to get the goods issue date for the order.  There will be many records in VBEP for the same sales order.  Look at all orders with a goods issue date (WADAT) of next day.
    3.     Go to VBAK for those document numbers to see if there are multiple sales orders for the same Sold To party (KUNNR).
    4.     For customers who have more than one order in VBAK, search all line items (for all orders).  If there are no duplicate materials across sales orders, do nothing.
    •     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP.  TANN are free goods that should not be considered for consolidation.  TAPS & ZTAP are lower level materials as a result of product selection.  They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
    •     Do not check line items where reason for rejection (VBAP-ABGRU) is not blank
    5.     If there are duplicate materials, go through the same logic as in part 1.  If the quantity across the sales orders adds up to greater than one case, add the appropriate quantity to a new line item on the first sales order.   If there is a remainder qty, update the line item on the first sales order with this qty. In this case, the quantities on the second sales order needs to be closed out with a reason for rejection code of 50, ‘Line Item Consolidation’. If there is no remainder,  update the qty on this item directly.
    •     Part 2 is relevant for order types ZOR, ZCA, ZSM
    •     This batch job will have to be run manually for Day Pick orders.  The end of this program should automatically kick off the delivery due list for Day Pick orders, shipping condition 02.
    Business Justification:
    The business requires that like order line items be consolidated to one line item prior to the order going to the warehouse for picking.  This will aid in picking at the warehouse as well as result in the customer invoice not reflecting more than one line item for the same material.  In the case where the customer has truly ordered more than a case, i.e;, 1 case, 2 bottles, the documents in SAP will still reflect 2 lines.

  • Duplicate production order due to sales order on credit block

    Dear Experts !
    Need feedback on the following scenario:
    - Sales order is entered for material which is produced in-house specific to the sales order (ie customer's logo is on product).
    - Schedule line in sales order creates a production order specific to the sales order.
    - Customer runs into credit check a few days later and consequently the schedule line in the sales order is removed due to credit block, however the linked production order still remains and is produced by factory.
    - Sales order is released from credit check and a new schedule line is created resulting in another production order being released.
    Any ideas on how to prevent duplication of production order?
    Thanks in advance!
       -Alvin

    Hello,
    Apologies for the confusion, let me explain it a bit more.
    - Sales order is entered for material with planning strategy group of make-to-order, the schedule line initiates new production order for make-to-order material.
    - A few days later - the customer goes over credit limit or has overdue invoices, etc..
    - During background rescheduling (or any sales order change) the sales order gets a credit block due to static check.
    - Sales order block deleted schedule line in sales order, however the production order remains active.
    - Once the sales order is released from credit block, a new schedule line is created which initiates a new production order.
    - Duplicate production order is now being made in shop floor.
    I hope the above explains my scnario a little clearer.
    Thanks and regards,
    Alvin

  • Item should not duplicate in sales order form in line tab ..

    Hi All,
    Not very sure this is the right forum for this if not please tell me the correct forum to post this.
    We have a requirement(11.5.9) which we have to achieve it using custom.pll, as I am very much new to use it need help on this.
    In Sales Order form once we enter in Lines Information TAB,
    For example we will enter Item 'ABCD' at Line 1.1 then again at Line 2.1 if I try to enter the same item 'ABCD' it should pop up a message saying "Item Already Entered" once we press Tab on Ordered Item Field.
    If we enter a different Item it should take as usual.
    I will appreciate if some body posts the code for the same which we can do it using CUSTOM.pll
    Thanks in Advance
    Devender

    If you are in the WHEN-VALIDATE-ITEM trigger, you cannot navigate back through the list of already entered records (especially if record you are in is not complete). It does delay the validation, but duplicate checks are typically done by querying the database on both WHEN-VALIDATE-ITEM and PRE-INSERT/PRE-UPDATE triggers. This means when entering a new Sales Order, you won't be warned that Line 2 has the same item as Line 1 until you save, but there are no navigation required to avoid issues such as trying to leave the current record before it is valid.

  • Stop duplicate entry of item in Order management sales order

    Dear,
    i have a requirment to stop duplicate entry (while making sales order) in Order management Sales order. When user enter any new line on the sales order then it is validate that same item has already been selected before in the same order.
    If user hase already select that entry then form shows error and restrict the duplicate entry.
    i have to achive this funcionality on the standard Sales Order form of Order Management Super User.
    Regards,

    Please review these docs and see if it helps.
    [ID 1105868.1]
    ARCHIVED: Cannot Change Selling Price On Sales Order Lines [ID 414472.1]
    Transaction Workbench Error: FRM-40735 ON-UPDATE Trigger Raised Unhandled Exception [ID 781264.1]
    Thanks,
    Hussein

  • Disable duplicate check for customer address on sales order creation

    I am using the following tables to create sales order as well as customer and addresses together. All data are coming from third party system through dblink.
    OE_HEADERS_IFACE_ALL
    OE_LINES_IFACE_ALL
    OE_CUSTOMER_INFO_IFACE_ALL
    however, whenever the address to be created already exist in OFS, the sales order import program ended with:
    Source/Order/Seq/Line    Message
    *1122/SOSHM006// Duplicate SHIP_TO ADDRESS found for SOSHM006_S. Please correct the data.*
    *1122/SOSHM006// Duplicate BILL_TO ADDRESS found for SOSHM006_B. Please correct the data.*
    how can I disable the above checking? ie: allow the address to be created even the address already exist.
    See Example below, notice that the addresses for SOSHM006_S and SOSHM005_S are identical, and addresses for SOSHM006_B and SOSHM005_S are identical, but we want them to be created as separately addresses.
    Example (first time)
    Insert into ONT.OE_HEADERS_IFACE_ALL (ORDER_SOURCE_ID, ORIG_SYS_DOCUMENT_REF, ORG_ID, ORDERED_DATE, ORDER_TYPE, PRICE_LIST, SALESREP_ID, SALES_CHANNEL_CODE, SHIP_FROM_ORG_ID, CUSTOMER_NUMBER, BOOKED_FLAG, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OPERATION_CODE, ORIG_SHIP_ADDRESS_REF, ORIG_BILL_ADDRESS_REF) Values (1122, 'SOSHM005', 86, sysdate, 'Corporate (NOR)', 'Corporate', 1, 'CORPORATE', 90, 'SHM01', 'Y', 0, sysdate, 0, sysdate, 'INSERT', 'SOSHM005_S', 'SOSHM005_B');
    Insert into ONT.OE_LINES_IFACE_ALL (ORDER_SOURCE_ID, ORIG_SYS_DOCUMENT_REF, ORIG_SYS_LINE_REF, LINE_TYPE, INVENTORY_ITEM, ORDERED_QUANTITY, SHIP_FROM_ORG_ID, FULFILLMENT_SET_NAME, UNIT_LIST_PRICE, UNIT_SELLING_PRICE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OPERATION_CODE, SUBINVENTORY) Values (1122, 'SOSHM005', 'SOSHM005A_S', 'Corporate Line (NOR)', '01-09-PAC-3522-01', 1, 90, '1', 0, 0, 0, sysdate, 0, sysdate, 'INSERT', 'Mesad');
    insert into OE_CUSTOMER_INFO_IFACE_ALL(CUSTOMER_INFO_REF, CUSTOMER_INFO_TYPE_CODE, current_customer_number, org_id, COUNTRY, ADDRESS1, CITY, STATE, POSTAL_CODE, IS_SHIP_TO_ADDRESS, IS_BILL_TO_ADDRESS, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) values('SOSHM005_S', 'ADDRESS', 'SHM01', 86, 'MY', 'Ship4 479, JALAN PASIR PUTEH 31650 IPOH PERAK.', 'IPOH', 'Perak', '31650', 'Y', 'N', sysdate, 0, sysdate, 0);
    insert into OE_CUSTOMER_INFO_IFACE_ALL(
    CUSTOMER_INFO_REF, CUSTOMER_INFO_TYPE_CODE, current_customer_number, org_id, COUNTRY, ADDRESS1, CITY, STATE, POSTAL_CODE, IS_SHIP_TO_ADDRESS, IS_BILL_TO_ADDRESS, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) values('SOSHM005_B', 'ADDRESS', 'SHM01', 86, 'MY', 'Bill4 479, JALAN PASIR PUTEH 31650 IPOH PERAK.', 'IPOH', 'Perak', '31650', 'N', 'Y', sysdate, 0, sysdate, 0);
    Example (second time) - the differences are highlighted in bold.
    Insert into ONT.OE_HEADERS_IFACE_ALL (ORDER_SOURCE_ID, ORIG_SYS_DOCUMENT_REF, ORG_ID, ORDERED_DATE, ORDER_TYPE, PRICE_LIST, SALESREP_ID, SALES_CHANNEL_CODE, SHIP_FROM_ORG_ID, CUSTOMER_NUMBER, BOOKED_FLAG, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OPERATION_CODE, ORIG_SHIP_ADDRESS_REF, ORIG_BILL_ADDRESS_REF) Values (1122, *'SOSHM006'*, 86, sysdate, 'Corporate (NOR)', 'Corporate', 1, 'CORPORATE', 90, 'SHM01', 'Y', 0, sysdate, 0, sysdate, 'INSERT', *'SOSHM006_S'*, *'SOSHM006_B'* );
    Insert into ONT.OE_LINES_IFACE_ALL (ORDER_SOURCE_ID, ORIG_SYS_DOCUMENT_REF, ORIG_SYS_LINE_REF, LINE_TYPE, INVENTORY_ITEM, ORDERED_QUANTITY, SHIP_FROM_ORG_ID, FULFILLMENT_SET_NAME, UNIT_LIST_PRICE, UNIT_SELLING_PRICE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OPERATION_CODE, SUBINVENTORY) Values (1122, *'SOSHM006'*, *'SOSHM006A_S'*, 'Corporate Line (NOR)', '01-09-PAC-3522-01', 1, 90, '1', 0, 0, 0, sysdate, 0, sysdate, 'INSERT', 'Mesad');
    insert into OE_CUSTOMER_INFO_IFACE_ALL(CUSTOMER_INFO_REF, CUSTOMER_INFO_TYPE_CODE, current_customer_number, org_id, COUNTRY, ADDRESS1, CITY, STATE, POSTAL_CODE, IS_SHIP_TO_ADDRESS, IS_BILL_TO_ADDRESS, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) values( *'SOSHM006_S'* , 'ADDRESS', 'SHM01', 86, 'MY', 'Ship4 479, JALAN PASIR PUTEH 31650 IPOH PERAK.', 'IPOH', 'Perak', '31650', 'Y', 'N', sysdate, 0, sysdate, 0);
    insert into OE_CUSTOMER_INFO_IFACE_ALL(
    CUSTOMER_INFO_REF, CUSTOMER_INFO_TYPE_CODE, current_customer_number, org_id, COUNTRY, ADDRESS1, CITY, STATE, POSTAL_CODE, IS_SHIP_TO_ADDRESS, IS_BILL_TO_ADDRESS, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) values( *'SOSHM006_B'* , 'ADDRESS', 'SHM01', 86, 'MY', 'Bill4 479, JALAN PASIR PUTEH 31650 IPOH PERAK.', 'IPOH', 'Perak', '31650', 'N', 'Y', sysdate, 0, sysdate, 0);

    Hi George Chen
    with sales order stock .. is ther a way of allocating the stock from unrestricted stock .. i understand that you have to have the stock in a "special" area to move it to the sales order?
    excuse my ignorance but what is IS-AD solution?
    thanks
    Nick

  • Duplicate Sales Order - UserExit or BADI

    Hi,
    I have a requirement for one of my workflow.
    When duplicate sales order is received through EDI , I need to notify to Customer service team.
    If purchase order and ship-to is same and PO date is within 30 days, need to notify that it is a duplicate sales order. Do we have any user-exits or BADI'S for this requirement?
    Thanks
    Ashu
    Edited by: Ashu on Jul 8, 2009 9:10 PM

    Hi Ashu,
    Customer function module EXIT_SAPLVEDA_001 (with include ZXVEDU03). This is called for every segment.
    Customer function module EXIT_SAPLVEDA_011 (with include ZXVEDU13). This is called after segments are filled. I suppose this is the correct one. Make your validation and fill the error table DERRTAB with the message.
    Customer function module EXIT_SAPLVEDA_010 (with include ZXVEDU12). This is used to change the idoc status, as well you can trigger the workflow.
    Customer function module EXIT_SAPLVEDA_005 (with include ZXVEDU07). You can check this.
    All my suggestions are based after checking the code. Please debug before you use them.
    Please update the thread with your approach.
    Thank you,
    Goutham.

  • Duplicate Sales Order - Workflow

    Hi,
    I have a requirement like this..
    When duplicate sales order is received through EDI , I need to notify to Customer service team.
    If purchase order and ship-to is same and PO date is within 30 days, need to notify that it is a duplicate sales order. Do we have any user-exits or BADI'S for this requirement?
    Thanks
    Ashu
    Edited by: Ashu on Jun 22, 2009 11:12 PM

    HI,
    You have posted it in the wrong forum. Try posting this in ABAP--> Enhancement & modifications forum.
    Anyways, you can try the below mentioned BOs to trigger your workflow and send notification.
    IDOCORDCHG
    IDOCORDERS
    Hope it helps.
    Regards,
    Raj

  • Duplicate Sales Order Check run

    Hi all,
    How to run a duplicate sales order check report?
    Thank you
    Vinu

    Hi
    Sales order number is a unique number in the SD. To check the duplicate sales order means r u going to check the sales orders with same numbers, or you are trying to check the sales order with copied from some other sales order
    First case, you can check the SO number and capture the counts more than 1 sales documents
    In the second case,you have to find the refernce number field in the Sales doc and compare the item...it will take a quite bit of workaround
    Regards
    N Ganesh

  • Duplicate sales order

    •     Developed a report to display duplicate sales orders based on the PO Number, Net value of the document and the creation date.
    i saw this report is it possible to exits duplicate sales orders. if it exits how it possible what is business scenario which business scenario its possible give me some example
    regards
    sreedhar.

    Hi,
    This kind of scenerio may arise because of manual errors. Example : User might create multiple sales orders for a single PO received from the customer. Technically also it is possible to create multiple sales orders using same PO unless there is a specific check in place.
    Regards,
    Ram

Maybe you are looking for