EDI output triggered for old PO

Hello All,
on 09.09.2014, EDI ( output type NEU, transmission medium 6) output type has triggered for more than 700 PO's which has been created in 2012 for several vendors and sent to supplier again as a duplicate copy. Suppliers are reaching client for this and some suppliers started sending goods which client has not ordered. There are no changes available in PO and users have not edited those PO's. There is no batch job scheduled to trigger output type. How else is possible for triggering output type in old PO. Please share your ideas.
Regards,
Prasath J

Ask your basis team when the last copy was done. if the copy was done between creation date and now, then the PO in the copy system will show how the PO was before the incident happened.
This way you can see if there were unprocessed messages.
Message records do not create by itself in old POs, And 700 cases do not speak for a manual activity either,especially as you are saying that you have no change records.
Maybe there was something done programatically to solve an earlier problem from you:
PO Output Message Disappears

Similar Messages

EDI output message for Outbound Deliv send with application own transaction

Dear All,
I encountering a problem with the output message "WSOR" via EDI.
What i want:
I would to configure this message output without the Dispatch time " 3: Send with application own transaction".
What is encountering now:
I have done the setting in "VV22" or VV21, with the conbination of Delivery type and Shipping point. and the setting is EDI with dispatch time 3: Send with application own transaction.
But When i use ME2O to create the outbound delivery for subcontractor, the message output "WSOR" process automatically and the dispatch time is 4: Send immediately (When application save).
Can anyone please advice me what are the setting or area that i need to check!!
Thank you very much,
Regards,
Chee Wee

Hi
Try here...
Logistics Execution -> Shipping -> Basic Shipping Functions -> Output Control -> Output Determination -> Maintain Output Determination for Outbound Deliveries
Regards
Eduardo

DOC_CHANGE_BADI not triggered for OLD SC-SAVE mode for EDIT- SAVE steps

Hi Experts ,
We have SRM7.0 ( SP08) with ECC6 ( Ehp4) having Classic Scenario.
In our business Price list ( Price in ECC Contract) will be always change so, we have done small enhancement in BBP_DOC_CHANGE_BADI in method BBP_SC_CHANGE, to get latest Price of the already assigned SoS ( ECC Contract ).
When we create new SC/Template from scratch or copying old SC or Template it brings latest prices correctly .
Case 1)Template - If we EDIT Template & just click on u201CSAVE AS TEMPLATEu201D button (w/o any change!) .. Doc Change BADi called & Template items updates with latest Prices .
Case 2) OLD SC in SAVE Mode -But exactly same is not happening with OLD SC with SAVE mode ? i.e. When we open Old SC in EDIT Mode and SAVE it ( or even Check and refresh it) ..it do not updates items with latest Prices of Contract. It means Doc Change BADi is not getting called..by clicking on just EDIT and SAVE buttons, unlike Template .
If we have to change something i.e. enter some Text or add one line Item and deleted it again..etc, then only Doc Change BADi is getting called and updated with latest pricesu2026which is not recommendable ..to change the OLD SC in SAVE mode every time.
Can anyone please suggest/confirm, why DOC_CHANGE_BADI is not getting triggered in case of Mode , if we open OLD SC( SAVE status) in EDIT Mode and just SAVE it..just like Template ?
What can be done to achieve above ?
Thank you .
NAP

We are having the same SRM release and SP level. I did a brief test for the two scenarios you mentioned. There was no difference for me: neither template edit/save without change or old SC edit/save without change went through BBP_DOC_CHANGE_BADI implementation. And I wouldn't expect there is a different behavior here as an SC template is also technically an SC document. I would suggest that you make an attempt to change the price in BBP_DOC_SAVE_BADI implementation instead.

New EDI Output Message for Existing Purchase Order

Hi Everyone,
We have existing POs in our system for vendors that we are turning on SRM Supplier Self Services for. When we configure the new output type, and then we change the purchase order, we are looking for the first SUS output type to come out as an ORDERS message, instead of an ORDCHG.
Is this possible?
Tx
Peter

Dear Peter,
The system automatically creates change messages with message type ORDERS if a second entry for that message type is maintained in the outbound parameters of the vendor's partner profile on tab page "Message Control". In that second entry, set the indicator "Change message". However, all change messages will be ORDERS, not only the first.
Best regards,
Christiane

Message type EDI is not triggering for outbound deliveries

Hello,
When ever the shipment status is completed message type EDI is triggered for the outbound delivery.
However, in spite of the shipment completion the DESADV EDI message is not created in the outbound delivery.
So, i request you to help me in this issue.
Regards,
Anil

Hi,
1st please check the partner porfile for whom it is sent ( Eg -- Ship to party) using T.code WE20 in partner type ku, look for the customer for whom it is sent.
Check for the message type wheter it is add in outbound parameteres.
Finally check the varaint of shipment whether the required output is maintained in the shipment varaint and also make sure that condition record is maintained for the output.
You find some solution with this.
Regards
vk

Debugging EDI output (IDOC creation) for purchase order...

Hi,
We have a EDI output type defined for Purchase order. When I go to Messages tab in ME22N transaction and repeat the EDI output and save it, it creates a IDOC which I can see using transaction WE02.
Now the problem is there is a user exit which I know gets triggered, when the IDOC is created for this PO. When we do some changes in this user exit, I see those changes are reflected when new IDOC is created. But if I put breakpoint, and do repeat output -> save, the debugger does not stop there.
Is there is some technique I can see the breakpoint stoppage in user exit for IDOC creation during EDI output for Purchase order ?
Regards,
Rajesh

Hi
Youc can set the output Peridoically (After Giving the output type, set the furthere data as periodic).
Save.
Set the break point in your user exit.
Go to se 38 -> Run RSNAST00,
Give the object id (Your PO #)
Give the output type and execute, the control will stop at break point.
Regards,
Baburaj

Output message type triggering for all

Hi,
I want the output messages to be triggered for particular Vendor and doc type with ALE config.
Now the config is such tht whenever the PO is created for doc type, the output type gets triggered for ALE partner .
So need guidance.
Thanks

hi,
Please check whether the access sequence attached to your Condition type has a condition table with Document type and vendor field, if not then you can add one or create a new Access sequence and attach it to you condition type.
Next you maintain the Condition Records for the doc type and vendor combination, and the system shall trigger the message type automatically.

Automatic triggering of EDI output on sales order change

Hi everyone,
I need to trigger edi output whenever i make changes to sales order and save.
Can anyone please help...
Regards,
Srikar

Hi,
Using change pointers you can create an IDOC when ever a specific field in the sales order line item is changed. activate the change pointer for message type ORDERS. Also maintained the entries in BD52
After this when you change this field at the sales order line item, it inserts entries into change pointer table.
Use Change Pointers properly so that idoc will trigger automatically.
Reward points
Regards

EDI Output for Material Document(Application ME)

Does anybody have the experience of having set up an EDI putput for a Mmaterial Document( Application "ME")?
I tried to configure a new output type by assigning it with Program RSNASTED and routine EDI_PROCESSING.
Setting up the partner profile is still pending but when i created a test document by creating a condition record i get an error message "Purchasing document XXXXX does not exist" where XXXXX happens to be the Material document number in this case.
Before proceeding further i just want to ensure if i am using the correct programs and Routines and i havent seen any available EDI output type provided by SAP for application ME.
Appreciate your response and inputs to proceed further.
Suman

Does anybody have the experience of having set up an EDI putput for a Mmaterial Document( Application "ME")?
I tried to configure a new output type by assigning it with Program RSNASTED and routine EDI_PROCESSING.
Setting up the partner profile is still pending but when i created a test document by creating a condition record i get an error message "Purchasing document XXXXX does not exist" where XXXXX happens to be the Material document number in this case.
Before proceeding further i just want to ensure if i am using the correct programs and Routines and i havent seen any available EDI output type provided by SAP for application ME.
Appreciate your response and inputs to proceed further.
Suman

What is Ale, Edi,IDoc tech for sap

Hi all,
What is Ale, Edi,IDoc tech for sap?
Thanks.

hi deniz,
ALE
ALE
Triggering OB via Change Pointers:
 When an application make a changes in any object an entry is made in CDHDR and CDPOS tables. When any change is made the SMD(Shared Master Data) Tool checks that ALE setting and create a change pointer in the BDCP table that will point to CDHDR table. A standard program RBDMIDOC is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process to distribute to the appropriate destinations. The program will read the table TBDME to determine the IDoc selection program it is MASTERIDOC_CREATE_SMD_MATMAS in the case of MATMAS.
Outbound Process:
When the stand-alone program or the Transaction(BD10) is run, it calls the Idoc
Selection program MASTERIDOC_CREATE_REQ_MATCOR in the case of MATMAS, which is hard coded in the program. The Idoc Selection program reads the master data and create a master Idoc and stores it in the memory. The function module then calls ALE layer by using another function module MASTER_IDOC_DISTRIBUTE which is invoked inside it. Then Idoc filtering, Segment filtering etc.. are done in the ALE layer.
 To dispatch the Idoc to the destination system, the system reads the partner profile to determine the destination system. Then the sending system calls the function module INBOUND_IDOC_PROCESS asynchronously on the remote system and passes the Idoc via memory buffer.
Asynchronous Communication:
The data that is IDocs and the function module are stored in ARFCDATA and ARFCSSTATE tables. The function module ARFC_DEST_SHIP will transports data to target System and the program ARFC_EXCUTE will execute the stored function Module. If communication problem occurs RSARFCSE program is automatically scheduled., if successful, entries in the tables ARFCSSTATE and ARFCDATA will be deleted.
Inbound Process:
The INBOUND_IDOC_PROCESS program is triggered as a result of RFC from the Sending System, the Idoc to be sent is passed as parameter for the function module
In the partner profile if Process immediately is selected then RBDAPP01 program is executed. It will read the process code(MATM) from the Partner profile, which in turn invoke the function module IDOC_INPUT_MATMAS for MATMAS
 Function module will call the corresponding SAP transaction using call transaction or uses direct programs to convert the Idoc to Application document .
In the table TBD51 there will be entries to find which option is used.
Transactions:
SALE - IMG ALE Configuration root
 WE20 - Manually maintain partner profiles
 BD64 - Maintain customer distribution model
 BD71 - Distribute customer distribution model
 SM59 - Create RFC Destinations
 BDM5 - Consistency check (Transaction scenarios)
 BD82 Generate Partner Profiles
 BD61 Activate Change Pointers - Globally
 BD50 Activate Change Pointer for Msg Type
 BD52 Activate change pointer per change.doc object
 BD59 Allocation object type -> IDOC type
 BD56 Maintain IDOC Segment Filters
 BD53 Reduction of Message Types
 BD21 Select Change Pointer
 BD87 Status Monitor for ALE Messages
 SALE Display ALE Customizing WEDI - ALE IDoc Administration
 WE60 - IDoc documentation
 SARA - IDoc archiving (Object type IDOC)
 WE47 - IDoc status maintenance
 WE07 - IDoc statistics
BALE - ALE Distribution Administration
 WE05 - IDoc overview
 BD87 - Inbound IDoc reprocessing
 BD88 - Outbound IDoc reprocessing
 BDM2 - IDoc Trace
 BDM7 - IDoc Audit Analysis
 BD21 - Create IDocs from change pointers
 SM58 - Schedule RFC Failures
EDI
EDI(Electronic Data Interchange )
RFC DESTINATION:
 A logical name used to identify the remote system on which a function needs to be executed.
Partner Profile:
 It defines the characteristics of data being exchanged with the business partner.
Partner Function:
 Role of the partner Eg:Ship-to-party,bill-to-party,etc in EDI and in ALE legacy system or remote SAP system.
Partner type:
 The type of your business partner .
 EDI KU/LI
 ALE -- LS.
Archiving:
 -Need to archive the important transmitted document
-Created in SARA
 -Assigned in WE20.
PartnerProfile Tips:
 RSECHK07- Consistency check for Partner Profile.
 If you want to modify partner profile; copy it and then modify. If you cant modify it , u have to delete it.
 To move partner profile to production system choose Partner -> Transport
Port defintion:
 It defines the medium through which data is exchanged between systems.
 tRFC - Used by ALE
 FILe - Used by EDI
 R/2 system system port For R/2 system
 Internet port - to connect with internet applications
 It also depends on the receiving side. If the receiving subsystem accepts tRFC, EDI also can use tRFC.
Remote Function modules required by Subsystem to send status and inbound idoc to SAP:
Startrfc - Program to execute RFC enabled Fun.mod. in SAP
EDI_DATA_INCOMING - To send data as inbound
EDI_STATUS_INCOMING - To send status to SAP
RSPARAM - To know the gateway service of the SAP system.
Message Control:
 Output controller
 A service program for determining the output type
 To generate and manage various outputs from an application and control their medium and timing of exchange.
 To retransmit the document without duplicating it
Procedure:
 A procedure defines a set of possible outputs for an application
 There may be more than one procedure but only one can be active
 Requirement field in procedure specifies the condition which the sales docu. should reach,for sending the sales order response.
Output type:
Defines the characteristics and attributes of the output.
Access Sequence :
Defines a sequence in which the business rules are checked using condition record of the condition table for proposing output type.
Sapfans Q & A
SREL_GET_NEXT_RELATIONS -
Function Module that will provide me the number of the document that was created by an IDoc
RLSUB020
Program which uses the above function module.
Upgradation problem
When the old version program is upgraded in to newer version(4.0b  4.6c) the SE38 editor wont allow u get thru the programs normally to get rid of this.
Solution:
EDIT > MODIFICATION OPERATIONS > SWITCH OFF ASSISTANT. Hit Enter on the subsequently shown Warnings window. You should now be able to maintain the code as before.
When transporting the dialog program sometimes the links may be missing in the testing and production area. To overcome just check u have properly save your all includes and other stuff in the same request if not, do so. Other options In ver 4.6c -> Within ABAP editor try utilities/Update navigation index
this fixes the links
ALE( Application Link Enabling )
Disk Mirroring:
Changes occurring in the database should reflected to another disk that maintains a mirror image of the main disks contents.
Replicas:
Maintaining redundant data across multiple systems.
ALE:
It provides distributed environment to integrate non-SAP systems
Provides guaranteed delivery of data regardless of network problem to application.
Logical system :
 The systems involved in distributed environment are assigned a logical name which uniquely identifies a system in a distributed environment.
Data Mapping:
 Conversion of a business document in IDoc format to an EDI format (and vice versa) which is performed in the subsystem.
Message Types:
 Represents a business function
 Technical structure is the IDoc type
 Or can say an instance of IDoc.
IDoc :
 They are containers used to exchange data between any two process.
 It represents an IDoc type and IDoc data
 IDoc type is structure and IDoc data is an instance of it.
Pls reward if helpful.

EDI Output ZB00 not getting determined in case of Split Deliveries.

Hello All,
A very Good Morning to you,
Hope you are doing good,
We have come across one critical Issue where the EDI Output ZB00 Dispatch Advice is not getting determined in case of few Split Deliveries in PROD.
Issue : On a daily basis our Client is generating Split Delivery Process used for some specific customers only.
These specific customers we are maintaining in ZPARAMS Table. The Flow of the Process is as below.
Sales Order -->Parent Delivery ZLF--> Split Delivery ZLS--> Invoice ZF2.
First the Sales Order ZOR is created through VA01 or EDI.
This ZOR is processed via ZVL10A to create parent delivery ZLF.
Once the parent delivery ZLF is created an Outbound IDoc SHPOD gets triggered which goes to the Distribution Centre Technicolor UK to check the confirmed qty and materials that needs to be delivered.
Once the Quantity is verified and confirmed from DC an Inbound IDoc SHCON interface SAP.
This Inbound SHPCON IDoc checks the entry in ZPARAMS for that customer. If the entry is found it creates one more Split Delivery ZLS doing picking and post Goods Issue in one step. This is the point where the ZB00 output is determined automatically in ZLS Delivery and processed successfully immediately.
After that the Normal Invoice ZF2 is created.
We have given the process flow details in the attachment along with Functional Modules used by the EDI Team.
Now the Issue we are currently facing on a daily basis in PRD Out of the Total Count of ZLS Deliveries in few of ZLS Deliveries ZB00 Output is not getting determined at all which is causing a huge revenue loss. For remaining ZLS Deliveries it is getting determined correctly and processed.For Split Delivery we have only 2 Customers.
We would like to know why this is happening in case of only few ZLS Deliveries.
As a work around we have just write one program for these disputed deliveries where it will go in VL02N of these deliveries and save it without doing any changes. This will make ZB00 determined and processed immediately.
We have even check the scenario in Quality Client no Issues at all. It is getting determined and processed successfully for all the test cases we created.
Please could you help us on this so that we can fix this critical Issue.
Many Thanks,
Farhan.

if QA system works correct
you probably need to find the difference between it and PRD client.
I guess it is a huge job.
but who does if not you?
because you have a lot of custom things included coding
also request abaper.

Want to change output type for 10000 sales orders through MASS

Hi Friends,
I would like to change the Output type in the sales order for 10000 sales orders.
Can I do with MASS transaction. If so, Plz let me know how ?
Is there any other process to change the output type for 10000 sales orders, as its difficult to manually in each and every sales order.
Its very urgent issue, Plz let me know at the earliest.
Thanks & Regards,
Praveen Kumar. A

This may be little tough for 10000 sales orders.
1. You have to remove the output record for the irrelevant output record using tcode VV12 for the relevant document type. So now for the document type, the old output wont be triggered.
2. Now, create output records for hte correct output type in VV11 tcode(for the output type BA03) for the document type. Now this output will be triggered for all the document types you are creating from now onwards.
3. To trigger the output type BA03, in all the old orders, you just have to open these sales orders in change mode (VA02), and just save it. When u open it the output type BA03 will be automatically triggered as the master data is maintained in VV11. But because just opening all the 10000 sales orders in VA02 one by one be a mechanical task, you have to think of some tool for this.
May be a CATT procedure can do the trick. Else, you can just create a small program, where you can upload these sales orders and the program will just open these orders in change mode and just saves it (without making any changes). Then the output will be retriggered.
Here again, if you are printing the output directly, it is advisable to trigger the output in batch mode(Date/Time field is 1 in VV11), and then you can again trigger the printing again using the program RSNAST00 after office hours for these 10k orders.
I hope I answered ur query.
Pls lemme know if you need some more info. (You can reward me too...)

Output determination for Sub-Shipment

Hello All,
I have a unique situation and need your inputs to identify possibilities in resolving it.
Here is the situation:
The transportation planning (TPE system) at our client is done by a 3rd party software. Now, we receive a Sales Order from a customer; create a delivery. TPE system creates the shipments and we PGI it and the sales order follows through the next steps. The shipments created from TPE go to Carriers and they carry the product from our warehouse to pool points from where customers pick it up. We have to pay the carriers from moving our goods from our warehouse to pool points. Thus whenever a shipment is created, we check-in...do the next steps in WM and finally when the shipment is ready, it triggers a payment IDOC to be sent to finance (an external system) so that it can be matched with Carrier invoices and then paid.
Our unique problem: There is a carrier (lets call it NCP) who is moving our goods from warehouse to pool point. We got a sales order from customer. This customer doesn't pick up goods from the pool point. He wants it to be delivered to his distribution center and to do this he is using the same transportation carrier (NCP). Thus when we received the sales order from customer, TPE system created a master shipment (5000001M) for NCP to pick up from our warehouse and deliver to pool point. You might be aware that TPE optimizes the route and thus combines multiple deliveries into one master shipment. From here NCP should pick up a part of the master shipment and deliver it to client. Thus SAP automatically created a sub-shipment (5000002S). This sub-shipment is a part of the master shipment and thus will not be separetely processed in WMS. The master shipment is checked-in, loaded and shipment ready - thus creating a payment IDOC to the external payee system. As the Sub-system is a part of master shipment, it is not touched and thus no payment IDOC is created.
Now the carrier sents two invoices - one for master to pick up goods from our warehouse and deliver it to pool point and the second one - to deliver a part of this shipment to customer's DC. Our payment system is unable to match it up with any IDOC's as we didn't send them out from SAP.
So this is where I'm struck. How should I configure the output for a sub-shipment so that it'll be triggered as soon as the delivery is PGI'ed? Could anyone give some inputs here?
Please let me know if more clarification is needed. Thanks in advance for looking into this

Dear VGR,
Do the configuration settings for the shipment output determination through this IMG path
IMG>Logistics Execution>Transportation>Basic Transportation Functions>Output Control-->Maintain Output Determination for Shipments
-->Maintain Condition Tables
-->Maintain Output Types
-->Maintain Access Sequences
-->Assign Output Types To Partner Functions
-->Maintain Output Determination Procedure
-->Assign Output Determination Procedures
I wanted to send an EDI to carrier when my planning is done and email to customers when loading takes place.
For he above requirement you take help of ABAPer to develop the output program in such way and assign that program to your shipment output type.
Maintain the condition records through VV71 transaction with Transm. Medium EDI and Email
I hope this will help you,
Regards,
Murali.

PO Change O/P error- Maintain outgoing EDI-connection data for partner for

Hi Experts ,
We are connecting our SAP ECC 6 ( Ehp 4) sytem to 3rd party system via SAP PI. We already done all the settings..line Output detemination procedure, Partner Profile ( WE20) , Port creation , Condition Records..etc.
We have PO Creation ( ZCRE) and PO Change ( ZPOC) Outbound messages to go from our system. Both have sepate message Types, since PO Creation IDOc should go immidiatly ( Dispatch time 4-Send immediately (when saving the application)
and PO Change IDoC should send as per wish manully in ME9F ( Dispatch time -3 Send with application own transaction).
Once PO Created , Output Message successfully triggering and IDoC is creating ( Green Color) ..so it is working fine .
Fo PO Change Message we had selcted Program -FM06AEND & FORM routine -CHANGE_FLAG.
We also set "Multiple issuing " checkbox in the Output Type and no requierment is assigned.
In WE 20, for Logical system ( LS) Partner XYZ, we set Process code ME11 and checked "Change Message"
1. But when I change PO Qty , output is not automaticaly triggering .After changing PO, if we see determination Analysis, in Procedure RMBEF1, this output ZPOC shows 2 times. First, it shows green color,...Output Found , and second times, it displays, "partner XYZ is not an EDI partner"
2. If we try to manually enter the Output ZPOC in PO Header, then system gives the Error - Maintain outgoing EDI-connection data for partner XYZ.
Can anyone pls suggest what should be the reason for above?
Thanks
NAP

Issue Resolved .
The reason for this system behaviour is in fine-tuned control: We was
using ZMIN only for new message output and ZCHG only for change messagesNevertheless, you can maintain two entries in WE20 for ORDCHG:
EF ZCHG ME11 w/o Change message flag
EF ZCHG ME11 with Change message flag
Thanks

Regd:Error in Output determination for Delievry document

Hi,
we have set the output determination ~ Condition record for Ship-to-party Partner function for the delivery document.
The condn is set by using LAVA as the Output type and when we save the delivery doc, output is not getting triggered and when we try to enter the output details manually we get the below error
"Maintain outgoing EDI-connection data for partner XXXX " .
Could you please tell me what settings that I might have missed ?
RGds,
Vasanth.
Edited by: Vasantha Kumar Balasubramani on Jun 25, 2008 3:31 PM

Hi John & Sharath,
I have the partner profile defined in We20 for the Ship-To-Party for whom I am sending the delivery.I have set him as my customer(KU) in partner profile John.
Sharath, I know we have 2 EDI settings at VOE2 and VOE4 but both of them are for inbound messages. Could you please tell me what else EDI settings do i need to do ?
Thanks in advance.
RGds,
Vasanth.

EDI output triggered for old PO

Similar Messages

Maybe you are looking for