Duplicate EDI Order Check

We occasionally receive duplicate PO from the EDI subsystem in SAP. We don't have the error check for PO no. while creating the order.
I am trying to check this in user exit ZXVEDU03. I know I have to check for segment E1EDK02 with qualifier '001' . If the PO no. is found in VBKD, then the idoc is for the same PO. Now what should I do ? How can I prevent that idoc to be created ?
Your help will be greatly appreciated.

Hello, Just write the error message within this user exit that "Duplicate order should not be created" so this process would stop If we write the error message.
Thanks.

Similar Messages

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

ATP check for EDI orders

hello all,
When we create a sales order manually, we get a delivery proposal screen with the options of choosing different dates and quantity. Can I know how this works with an Inbound EDI order?
Whether the sales order will be created with unconfirmed quantities ? Does user intervention is required if IDOC fails due to availability failure? Can we automate the process for EDI orders so that the order picks up alternate plant or material if it is linked to GATP(APO)?
regards,
shan

closed

ATP check with EDI orders

hello all,
When we create a sales order manually, we get a delivery proposal screen with the options of choosing different dates and quantity. Can I know how this works with an Inbound EDI order?
Whether the sales order will be created with unconfirmed quantities ? Does user intervention is required if IDOC fails due to availability failure? Can we automate the process for EDI orders so that the order picks up alternate plant or material if it is linked to GATP(APO)?
regards,
shan

closed

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.

EDI Order Response

Hi,
How can i check the net price calculations done for a particular item on the sales order response. My problem is.
The value sent in field vprei is having a netprice value and from this i have to deduct bill back condition value.and this should be happen only to the sales order response (EDI). how can i implement this senario.

Visit the followingl links:
https://wiki.sdn.sap.com/wiki/display/ERPLO/SD+Configuration
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erplo/cin%2bconfiguration
Also, visit the following threads:
SAP SD Configuraton training
/message/3505991#3505991 [original link is broken]
SD Configuration:
Enterprise Structure:
1. Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
2. Assigning Sales Organization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
4. Assigning Distribution Channel to Sales Organization
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
5. Maintaining Division
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
7. Setting up Sales Area
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
10 Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
11. Defining Common Distribution Channels for Master Data
Use
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2
Pricing Procedure
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
The configuration differs from scenario to scenario & requirement of the client.
Interesting &important link to learn much more about configuration & business process is as under:
Link: http://help.sap.com/
Path: SAP Best Practices --> Baseline Packages --> Based on SAP ECC 5.00 --> Select Country: for eg, Localized for India --> Technical Information --> Building Blocks --> Select Country for eg, India --> List of Basic Configuration & scenarios will be listed.
Select the required basic configuration / scenario. These will consist of overview, configuration guide, business process, master data &so on.
All Standard Reports which are available are as under:
SAP Easy Access: Information Systems -> Logistics -> Sales and distribution ->
1. Customer -> Incoming orders / Returns / Sales / Credit memos / Sales activities / Customer master / Conditions / Credit Master Sheet
2. Material -> Incoming orders / Returns / Sales / Credit memos / Material master / ...
3. Sales organization -> Sales organization / Sales office / Sales employee
4. Shipping point -> Deliveries / Returns
5. SD documents -> Orders / Deliveries / Billing documents ...
& so on.
Some of the Standard reports in SD are:
Sales summary - VC/2
Display Customer Hierarchy - VDH2
Display Condition record report - V/I6
Pricing Report - V/LD
Create Net Price List - V_NL
List customer material info - VD59
List of sales order - VA05
List of Billing documents - VF05
Inquiries list - VA15
Quotation List - VA25
Incomplete Sales orders - V.02
Backorders - V.15
Outbound Delivery Monitor - VL06o
Incomplete delivery - V_UC
Customer Returns-Analysis - MC+A
Customer Analysis- Sales - MC+E
Customer Analysis- Cr. Memo - MC+I
Deliveries-Due list - VL04
Billing due list - VF04
Incomplete Billing documents - MCV9
Customer Analysis-Basic List - MCTA
Material Analysis(SIS) - MCTC
Sales org analysis - MCTE
Sales org analysis-Invoiced sales - MC+2
Material Analysis-Incoming orders - MC(E
General- List of Outbound deliveries - VL06f
Material Returns-Analysis - MC+M
Material Analysis- Invoiced Sales - MC+Q
Variant configuration Analysis - MC(B
Sales org analysis-Incoming orders - MC(I
Sales org analysis-Returns - MC+Y
Sales office Analysis- Invoiced Sales - MC-E
Sales office Analysis- Returns - MC-A
Shipping point Analysis - MC(U
Shipping point Analysis-Returns - MC-O
Blocked orders - V.14
Order Within time period - SD01
Duplicate Sales orders in period - SDD1
Display Delivery Changes - VL22

Duplicate Payment Order

Hi,
After making sucessfull payment run duplicate payment order genearting in backround. Can anyone advise reason.
Regards
MRS.

Hi,
Select the checkbox "Payment Document Check" in the printout program variant used in F110.
Regards,
SDNer

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

How to add STRS2 value in the EDI order

Hi Friends,
I have to add one extra field STRS2 in the Idoc segment
Field STRS2 ( CHAR 35 ) - "This field represents the second line of street address for vendor."
We are not getting the value of STRS2 on the EDI Order.
If we need it, how we have to proceed.
Any one can guide with detaild information including where to change the code and all.
Regards
Kumar

go to table TBDME and then pass the message class and execute then you will be getting the function module name.
Then get into the source code of function module and search for call customer, it will give you the available exits..Then check out whether you will be getting that segment values in that exit.
Hope it helps.
Reward if it is useful.
Thanks,
Srinivas

[SAP XI] EDI orders posting job to SAP R/3

Hi everyone!
I would like to know if SAP XI has the capability to directly post EDI orders in SAP R/3 wherein IDocs are placed. If yes, how? (Please describe the process in detail)
In normal EDI implementation (AI, 3rd party translator used), batchjobs are created to be able to post EDI orders. The AI/3rd party translator are sending the IDocs after conversion from customer format order file to the specified UNIX directory in SAP and batchjobs will post these as EDI orders that can be viewed in WE02/WE05.
In SAP XI direct connection case, all IDocs received are automatically posted in SAP R/3 without having a batchjob executing this. However, orders are not successfully posted as there is an authorization issue** (user/system/technology posting EDI orders are not allowed to create an EDI order) so we need to determine which user/system/technology are executing the job (posting of IDocs to an EDI order).
Please advise. Thank you very much!
Fred

Hi,
U can do the send EDI data into SAP using third party tool or adapter(Seeburger) or by using the conversion agant.
U need to have the XSD for the EDI structure and EDI data should be flat file.
Check some links on Conversionagant and Seeburger.
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/43/6d95e0ac846fcbe10000000a1553f6/CMGetStart.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/content.htm
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
/people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi
/people/paul.medaille/blog/2005/11/18/conversion-agent-a-free-lunch
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
Regards,
Phani
Reward points if Helpful

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

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

EDI order creation

Dear friends,
I have used MV45FZZ program to add/activate 'ZD03' pricing condition at the sales order item level, based on some condition. I have included the logic in form, <b>USEREXIT_SAVE_DOCUMENT_PREPARE</b> . This logic is working fine for VA01/VA02; if we created orders manually. But, ZD03 pricing condition is not getting activated for EDI orders. I have tested by processing Idocs through WE19.
Kindly let me know ur suggestions regarding this issue.
Thanks in advance.
Regards,
Bharat.

Hi,
I think u are triggering the idoc from va02 tcode, by going to extras->output->header->edit...u also need to configure the medium to be EDI..now check if it is firing or not.
Regards,
nagaraj

EDI order on quota block before EDI block

Hi,
Order xxxx is received via EDI. Checking the order in VA14L shows that the order is on quota block where it is expected to be on EDI block first. Checking the change log of the order shows there was no release of the order from EDI block.
Please investigate why this order was not on EDI block initially.

hi rohit,
Correct me if i am wrong...
ur requirement is not to trigger the IDOC message for changes in the PO for certain vendor ?
if it is so then,to my knowladge it is not avallable in stadard as we can conrol the same by condition record.
u can apply the logic in such a way the if there is no condition record available for message triggering for change of PO then loop should be ending.thet means no generation of IDOC or error message.
regards,
SNB

EDI order Segregation

Hi i'm new to EDI environment!
The requirement is to make EDI robust enough to handle software orders(ZSW order type) in addition to the regular orders(ZEDI and ZCAT).We have a third party tool which submits order to Sap from sources like(customers or WEB) and defaults every order type ZEDI or ZCAT.So if the same or new customers submit a software order, it would still come in as standard EDI order.
I need to split the order into 2 categories when applicable in SAP system.I know that firstly i need to perform customer level check from KNVV and seperate the Sales organisation with its corresponding order type and then check out the line item level check from MARA and MVKE.Then get the contract information and header information and i do this coding with the help of idoc_input_orders FM.I'm creating a user defined FM which is exactly the replica of Standard FM and i've been advised to write the corresponding code for the above check in the user defined FM and i need to call the Standard FM when applicable.
Can any one please help me regarding this i can still give a detail explanation of my project if needed.

Hi Roja,
After seeing your query it can be done through user exit only,there is no option in standard.
User exit in program MV45AFZZ - USEREXIT_MOVE_FIELD_TO_VBAP or
MV45AFZZ - USEREXIT_SAVE_DOCUMENT
take ABAPer help he can fix the problem
in the program you can tell in which conditions the order should be created with automatic reason for rejection.
Regards
Ram

Duplicate EDI Order Check

Similar Messages

Maybe you are looking for