EDI setting

hi all,
any one have step by step procedure to send IDoc to External System[outbound EDI process] using EDI.
how will do configuration for EDI .it is same as ALE or some thing different.If it is different then what are the T-codes for configuration.
Thanks in Advance,
with regards
Lokesh.

Hi Lokesh,
Please check these links
Outbound Processing
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7e7943d711d1893e0000e8323c4f/frameset.htm
Creating an Outbound Partner Profile
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b809b43d711d1893e0000e8323c4f/frameset.htm
Outbound Processing under Message Control: Procedure
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7e9343d711d1893e0000e8323c4f/frameset.htm
Advanced guide to EDI configuration
http://www.erpgenie.com/sapgenie/docs/advanced_guide_to_edi_configuration.doc
Creating an Outbound Partner Profile
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b809b43d711d1893e0000e8323c4f/content.htm
best regards,
raam

Similar Messages

EDI Message for Scheduling Agreement Schedule Lines

Hi Experts,
My client has the EDI set up for the SASL and is running fine.
Currently we have scheduled background program to trigger the IDOC and convert the IDOC into XML to send the information to the external system via interface after MRP run.Output type in the SASL will be triggered at header level (Without release documentation) whenever there is a new or change in the schedule line. Schedule line will be fixed automatically for every MRP run based on the Firm zone maintained in scheduling agreement.
Now the requirement is, Client wants to send the schedule lines regardless of New or change after MRP run sothat all the information will be sent to the suppliers. This requirement may be contradictory one but the client needs it.
1) For the New schedule line creation the output type will be triggered so no issues the program will take care
2) For the change schedule line also the output type will be triggered so No problem.
Requirement :
1) When there is no new & change in the schedule lines , how we can handle this???
2) Client wants to fix the schedule lines based on the planned delivery time and they do not want to maintain this PDT in the Firm zone field.??
Kindle explore and provide me the inputs. Appreciate your help.
Thanks /Karthik

Can you elaborate bit more on the issue.
see if you are not mentioning the PDT in the firm zone field. then it means the schedule lines can be changed and once they are changed the change idoc will get trigger.
however if there is no change in the schedule line and since its a old one there will not be any idoc generation for this.
seems as per your requirement you want to get the idoc generated for the old line as welll then u need to look for the anhancement badi/uer exit to map this.
need more insight of the issue to resolve it

Check Payment advice through EDI

Hi,
I need a solution to send the payment advice to bank through EDI.
For that i created partner profiles for vendor and bank. I activated EDI in vendor master also.
And i attached EDI accompaying sheet also to the FBZP t code.
for this we created a new payment method and testing. it is working.
our client is asking: He want to send the payment advice for the payment method 'C' - Check to his bank through EDI. What we have to do for this.
For this if we give C in payment method in F110 we have to use payment method program only not EDI program.
Please guide me
sateesh kumar

Hi Sateesh,
Generally payment advices are directly sent to Vendor, but sometimes clients will sent the payment details and payment advice to the bank.
In your case, if u want to select the Payment Method C, then if u give RFFOEDI1 program for EDI setting, then u cant print your cheques locally.
One Alternative is that use Payment Medium Workbench (PMW) in that check management option is present, try with that.
I am not sure how far it is going to be successful.
Regards
srikanth

Payment run F110-EDI

Hello,
while doing payment run, I am getting this error "
The following documents were not processed since they will be sent by EDI"
please suggest.
Thanks

Hello,
as usggested, checked the payment method - its the same "C" everywehere but still getting the error.
is this comin from EDI setting, do i need to changed somethin in SPRO......olease suggest.

EDI Transaction

Hi Any body plz give me EDI transaction flow

Ash,
Can anybody give more head on EDI sets and examples?.
>> following are transaction sets
180 - Return Merchandise
210 - Freight Invoice
503 - Pricing History
805 - Contract Pricing
810 - Invoice
811 - Invoice Summary
812 - Credit/Debit Adjustments
820 - Payment/Remittance Advice
823 - Lockbox
824 - Application Advice
830 - Production Schedule & Release
832 - Price/Sales Catalog
836 - Contract Award
840 - Request for Quotation
842 - Nonconformance Report
843 - Request for Quotation Response
844 - Product Transfer Adjustment
845 - Price Authorization
846 - Inventory Inquiry
847 - Material Claim
850 - Purchase Order
853 - Routing and Carrier Instruction
855 - PO Acknowledgment
856 - ASN
857 - Shipment & Billing Notification
858 - Shipment Information
860 - Purchase Order Change
861 - Receiving Advice
862 - Shipment Schedule/Release
864 - Text Message
865 - Purchase Order Change Acknowledgment
866 - Production Sequence
867 - Resale Report
869 - Order Status Inquiry
870 - Order Status Report
879 - Price Change
997 - Functional Acknowledgment

Steps for Idoc to EDI Subsystem

Hi all,
Can anyone tell me the steps that i have to worry about to send an idoc immediately to EDI Subsystem
I mean what all things i have to specify while creating ports and partner profiles etc
Thanks

Sending Order Confirmations by EDI (SD-SLS)
Use
By setting up and using the Electronic Data Interchange functions in the R/3 System, you eliminate the need to print documents and send them through the standard mail system. Instead, you send the information electronically. This method is more practical, convenient, and allows you and your customer to process data faster.
In this EDI scenario, you process and send order confirmations to a customer's R/3 Purchasing system.
Prerequisites
Application
Customizing
To process outbound order confirmations, you need to make all of the necessary EDI settings in Customizing for Basis. You make settings for output control in Customizing for Sales and Distribution.
Output Control
The standard SD condition components are:
Condition component     Value
Sales document type     AA
Output determination procedure     V10000
Condition type     BA00
Transmission medium     6 (EDI)
Access sequence     0001
Processing subroutine     Program RSNASTED, form routine EDI_PROCESSING
Partner function     SP (sold-to party)
Application     V1
Condition records for outbound order confirmations are maintained in Customizing for Sales and Distribution. Choose Basic Functions  Output Control  Output Determination  Output Determination Using the Condition Technique  Maintain Output Determination for Sales Documents.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data for the outbound parameters for partner profiles and the additional profiles for message control:
Field     Value
Message type     ORDRSP
Partner type     KU (customer)
Partner function     SP (sold-to party)
Receiver port     e.g. SUBSYSTEM
Output mode     e.g. Transfer IDoc immediately
Basic type     ORDERS04
Process code     SD10
Activities
Create an order. When you save the document, the system uses your settings in output control to find the appropriate condition record and send confirmation of the order by EDI. To review and maintain output data in the document, choose Extras  Output  Header.
Receiving Acknowledgments via EDI (MM-PUR-GF-CON)
Use
You have arranged with your vendor that that latter is to send you acknowledgments in respect of purchase orders or outline agreements received from your company. (Note: both kinds of acknowledgment are generally referred to as "order acknowledgments" in the system. The corresponding EDIFACT term is "order response" (ORDRSP).)
You have the option of working exclusively with acknowledgments. The acknowledgment is then purely informative in nature, since only the acknowledgment number is recorded in the system.
If you wish to receive different kinds of vendor confirmation, such as both order acknowledgments and shipping notifications (also known as advance shipping notices - ASNs), it is possible for quantities and dates to be entered in the system automatically).
For more information on this topic, refer to the MM Purchasing documentation ( Confirmations from the Purchasing Viewpoint and Receiving Confirmations via EDI).
Prerequisites
Application
To work with several categories of vendor confirmation, you must:
u2022     Enter a confirmation control key on the item detail screen
u2022     Set up the confirmation control facility in Customizing for Purchasing (Purchasing  Confirmations  Set up Confirmation Control). There you can specify the order in which you expect confirmations from your vendors, for example.
Under Confirmation sequence, you can:
u2022     Specify tolerances for date and price checks
u2022     Allow vendor material changes (VMat indicator)
u2022     Adopt vendor price changes (Price indicator)
Do not use a confirmation control key if you work exclusively with acknowledgments.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  EDI  Set up Partner Profile):
Parameters for Inbound Messages
Field     Value
Partner type     LI
Partner role     LF
Message category     ORDRSP
Process code     ORDR
Processing     Initiate immediately or process via background program
Activities
When an acknowledgment is received in the form of an incoming EDI message, the system checks whether a confirmation control key has been entered in the relevant PO or outline purchase agreement.
u2022     If there is no confirmation control key, only the acknowledgment number is entered on the item detail screen.
u2022     If there is a confirmation control key, the system updates the confirmation overview. That is to say, the dates and quantities set out in the acknowledgment that has just been received are recorded and taken into account in the overview. To view acknowledgments that have been received, choose Item  Confirmations  Overview from the item overview. Column C (creation indicator) contains the value 3, meaning that the acknowledgment was received via EDI. The system also enters the IDoc number in the External document column.
An IDoc can always acknowledge one purchase order only. The acknowledgment relates to the PO item, not to any individual schedule lines.
Exceptions
When an acknowledgment is received via EDI, the system automatically checks quantities, prices, and dates. In checking quantities, it applies the over- and underdelivery tolerances set for the item. You can set tolerances for prices and delivery dates in Customizing for Purchasing under Set up Confirmation Control.
The tolerances you define apply to all vendors. Using the enhancement MM06E001 provided by SAP, you can specify that the tolerances do not apply to certain vendors.
If the acknowledged quantities, prices, and dates vary from those set out in the PO or purchase agreement, the system issues a warning message. In this case, the purchasing document is not updated.
For more information on this topic, refer to the section Error Correction (Receiving Confirmations via EDI) of the MM Purchasing documentation.
Sending PO Change Notices via EDI (MM-PUR-PO)
Use
This section describes how to transmit a change notice relating to a purchase order that has already been sent to a vendor.
The function corresponds to the transmission of a purchase order via EDI.
Prerequisites
Application
You have already successfully transmitted the original purchase order to the vendor via EDI.
Message Control
You have created message condition records for your EDI vendors (Purchasing  Master data  Messages  Purchase order  Create).
Use the message type NEU to transmit PO change notices.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  Set up Partner Profile):
Parameters for Outbound Messages
Field     Value
Application     EF ( Purchasing: purchase order)
Message category     ORDCHG
IDoc type     ORDERS02 or ORDERS04
Process code     ME 11 (ORDCHG: PO change notice)
If you wish to transmit PO conditions or texts to your vendor, you must create an IDoc view. For more information on this topic, see Sending a Purchase Order via EDI.
Activities
Change an existing purchase order via Purchasing  Purchase order  Change. Make the necessary changes and save the PO.
The new message is compared with the last successfully transmitted message. PO change notices indicate whether any new items have been added to the PO, and/or whether any already transmitted items have been changed.
When the message is transmitted, only those changes that are simultaneously new and print-relevant are included. The system sets the change indicator for the new message. To check the change indicator, choose Header  Messages in the PO item overview.
See also:
MM Purchasing: Creating a Purchase Order
Cross-Application Components: Customizing Message Control in Purchasing (MM): Example: Purchase Order
Receiving Order Changes by EDI (SD-SLS)
Use
In this EDI scenario, you receive and process order changes sent by a customer from an R/3 Purchasing system.
Prerequisites
Application
General
You can receive and process order changes in your system only on the basis of an existing order.
Customizing
To process incoming order changes, you need to make all of the necessary settings in Customizing for Basis. There are no special settings for Sales and Distribution.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data in the header and detail screen for inbound parameters:
Parameter     Value
Partner type     KU (customer); if the IDoc is sent from an R/3 system via tRFC (in a typical case with ALE scenarios), enter LS for logical system!
Message type     ORDCHG
Process code     ORDC
Processing     Process immediately
Allowed Agents     Enter an R/3 user or an organizational unit, for example.
Activities
Inbound Processing
The IDoc interface receives the IDoc and reviews its control record. According to this record and the corresponding partner profile, the IDoc is transferred to the function module IDOC_INPUT_ORDCHG in Sales and Distribution. The ALE services are called.
The system processes the IDoc in the background, using the data records in the IDoc to determine the relevant order.
If processing is successful, the system updates the sales order. The IDoc is sent back to the IDoc interface which updates the status records in the IDoc.
Exception Handling
If it cannot determine an order, or if an error occurs in processing, the system determines the relevant agent(s) and sends a workitem to the integrated inbox(es). An agent can pick up the workitem to process the IDoc or simply end processing.
To display an IDoc for order changes, choose Environment  Display facsimiles in the order. The system displays a dialog box of object links where you can choose Linked IDocs.

EDI Transactions

Hi, Can anyone explain about the list of EDI Transactions below. I need the steps and flow of those EDI Transactions. Please help me out in the below...
846 Inventory Advice (inbound)
870 Order Status Report (inbound)
888 Item Maintenance (outbound)
940 Warehouse Shipping Order (outbound)
943 Warehouse Stock Transfer Shipping Advice (outbound)
944 Warehouse Stock Transfer Receipt Advice (inbound)
945 Warehouse Shipping Advice (inbound)
946 Warehouse Inventory Adjustment (inbound & outbound)
Thanks,
Priya

Please visit these links for information:
http://xml.coverpages.org/ASCX12-EDI-Transactions200206.html
>>EDI transaction sets such as 850 orders, 810 invoice, 214 ASN.
>>Can anybody give more head on EDI sets and examples?.
http://www.tea.state.tx.us/textbooks/emat/edistd.html
http://www.tgiltd.com/supported_edi_transaction_sets.html
http://www.erpgenie.com/saptech/transactions.htm
http://www.erpgenie.com/sapedi/index.htm
Transaction Set for EDIFACT
http://msdn2.microsoft.com/en-us/library/aa560100(d=printer).aspx
Transaction Set for ANSI X12
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00415e14-0b01-0010-10a5-97e2cebb167c
http://www.erpgenie.com/sapedi/ansix12transactionsets.htm
Points rewarded if it is useful..

Sending PO to vendor without EDI

Hi All,
I have a requirement to send PO details to Vendor as a flat file or XML file (Any format other than IDOC and PDF) without using EDI. The reason is these are small level vendors and they don't have EDI set up and they want to receive PO in a user friendly format from which they can simply copy, paste the data or upload directly into their system. I have come up with the following options according to my knowledge.
Trigger options:
1.       Instant trigger using output control - Creating a new output type and assigning a custom program to the processing routine, which will be used to create a file.
2.       Overnight Job - Collective - Program which can be scheduled in background and check for the POs created on a given day and extract all of them in a single file and send to vendor in one go.
Formatting options:
1.       Flat file (Word document, Excel or Text pad)
2.       XML
Sending options:
1.       FTP
2.       EMAIL
3.       Middle ware (Webmethod) - Again 2 options in this, one placing the flat file in SAP application directory and Middleware application picking up the file and sending to Vendor. Option 2 is sending an IDOC to middleware and middleware converting the IDOC to XML format and dispatching to vendor.
Please let me know which will be the most suitable option for the given scenario. Also let me know your views on the options whether these are workable and the difficulties in achieving them technically.
Thanks in advance for your suggestions...

Hi,
There are some points needs to considered while designing the system:
1) Volume of POs that needs to be sent to vendor.
2) Frequency of the transmission.
3) How do you want to handle the changes done to POs(I am sure there will be changes to PO).
4) Future expansion to other vendors.
As you mentioned option of overnight job will be easier. You can capture the POs created in to a z-table via
user exit and write a program which runs daily pulls the POs in the z-table. Then you can FTP the file to vendor.
Hope this helps.
Ramesh

Inbound idoc for updating delivery date of purchase order

Hi All,
Our vendor sends a delivery file consisting of delivery date and quantity(could be partial) for line items of a purchase order.
I need to update the Purchase order line item with the delivery date and quantity sent from the Vendor. It should add a new confirmation line with custom confirmation category in the confirmation tab of the line item in the Purchase order.
Each time we get a delivery file we need to add a new confirmation line in the confirmation tab of the purchase order line item.
How can I get this working using inbound idoc processing? Which Idoc type should I use to solve my issue. Will ORDERSP work for my scenario?
Thank you,
Sonali.

>
sonali ashi wrote:
> We have all EDI set up done for ORDERSP idoc in our system. Problem when I use this idoc type by default system is always adding confirmation catgeory 'AB' but we want our custom category to be added instead of 'AB'.
> Edited by: sonali ashi on Dec 23, 2010 9:47 PM
Confirmation category used for order acknowledgement is define in configuation. You can change that from AB to your custom condition and EDI should pickup that.
SPRO->Material Management->Purchasing->Confirmation->Define Internal Confirmation Category
>
sonali ashi wrote:
> I have also noticed that 'AB' confirmation accepts only full quantity order acknowledgement through Idoc processing.
> Manually I can add a "AB" confirmation for partial quantity but in the idoc processing it fails.
> Edited by: sonali ashi on Dec 23, 2010 9:47 PM
Check tolerance limit defined for confirmation category in 'Conformation Control' Node in SPRO at same level as above.
Regards,
Pawan.

How to configure ME38 and Message Output

topic:EDI in procurement - delivery forecast (DELINS)
ME38 - ERROR:Output LPH1 for partner cannot be processed
How would I configure the same in ME38 and the resultant PrintOuts and EDI messages?
I've had a look in SPRO, andthis is the standard step by step procedure for Message determination that I done in SPRO:
SPRO > Material Management-> Purchasing -> Message -> Output Control->MESSAGE TYPE->Maintain
Message Types for Forecast Delivery Schedule/Expediter ->OK
109-LP->EL document
SPRO > Material Management-> Purchasing -> Message -> Output Control-> Maintain Requirements for
Message Control
LPH1->109
SPRO > Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message
Type-> Define Partner Roles for Scheduling Agreement Release/Exped
LPH1-6->OA
WE20
SPRO > Material Management-> Purchasing -> Message -> Output Control-> EDI->Set Up Partner Profile
defined Partner LI, message DELINS
SPRO > Material Management-> Purchasing -> scheduling agreements->set up stock transport sc.ag-> maint.REL.crea.profile for sc.agr.w rel.docu
MN12
LPH1-doc.Type-PurchORG-Vendor
ME32L
in Additional DATA      -> Scheduling Control (Firm zone=90&TradeOff-Zone=90
               -> output control -> Plant-Profile
ME38
create schedules
ME84
run
but in ME38 don't exist the message iDoc "LPH1"
if I tried to create manually the system show the following message:ù
OUTPUT LPH1 for partner cannot be processed
message n.VN043
Diagnosis
    The proposed output cannot be processed. You can only display details.
but I am not an MM configuration specialist (we don't have one at our company at present) and am therefore a little lost, any / all help appreciated.
Best Regards
Antonio Giovanniello

Hi
have you maintained the Partner Profile for the Partner role OA in the Outbound Parameters. Please maintain
Thanks & Regards
Kishore

Anyone experience with Oracle Release Management?

Hi,
I don't know in which forum to post this, but Order Management seems to be most appropriate.
I am looking for someone with experience in Oracle Release Management. We are an Automotive company and a couple of our customers use EDI and we have many repeating orders / schedules. We don't have EDI set up yet, that's planned for later. We were wondering if it makes sense to start using Release Management. What we have in mind is to use the Release Workbench to enter Order Schedules faster than in OE/OM.
However, even after reading the implementation & user manual this is still very unclear to me... What features are worth to be used with and without EDI etc. How does it fit in the whole concept and what benefits it can bring.
I am looking for someone who has experience in this area and is willing to share some knowledge. Anyone here from companies that use this module?
Btw., we are using eBusiness Suite 11i (11.5.10.2) and have Order Management and a couple of other modules heavily used.
Thanks,
David.

Well your question is from a few years back, but I am still curious if you had any answers? If so would you be so kind to share those with me? I am currently more or less in a same position. We want to use Release Management to prefent of releasing orders when a customer is beyond his forecast, but I have no idea if we can do it with this module.
Thanks: Pum van der Lit

Acknowledgement Required in Purchase value key

Hi
Can any one tell what is this Acknowledgement Required in Purchase value key
where it will be help ful in which case???

Hi,
You can use this key while creating a PO when you want the Vendor to confirm the Quantities and the Date/time of the Delivery after they have received your order and the vendor will supply the material according to your requirement.
After the Vendor confirms the delivery Qty and schedule dates, the user will need to Update the same in the Confirmation TAB. Also used in for EDI cases.
If you check the Acknowledgement required in Pur Val key, (in the Material Master), like other Values, the Tolerance, Reminders etc. , this Confirmation Check will be enabled in PO Confirmation TAB using Material Master Settings. (Used for EDI)
Some companies use this requirement to plan their Logistics and MPS (Master Production Schedule) for the availability of Material or use it as to plan Inbound Deliveries or Rough GR depending upon the Business Scenario using EDI set up.
Please check the following links :
[http://help.sap.com/saphelp_45b/helpdata/en/75/ee140f55c811d189900000e8322d00/content.htm]
[http://help.sap.com/saphelp_46c/helpdata/en/1c/deffb0844f11d2b471006094b9476a/content.htm]
Hope this helps,
Best regards
Amit Bakshi

How to parse the URI in ESB?

Hi,
Can we parse the stream of message sent as a "URI"?
Basically from the remote machine PIPServelet is receiving a stream of message in the form of URI.
as https://xxx.xxx.xxx:5555/<XMl>message_stream</XML>
Message_stream : Any PIP or EDI sets.
Now I need to parse this URI and read it and further process it in ESB and sent to the destination system.
How can we parse that URI?
Can anyone please help me on this?
Thanks
Ramana.

Actually, the Business Partner Data is almost empty for employees in my use case.
So only the Employee Data is maitained. So if I query the Business Partners, I find no AdressInformation at all. Neither AdressSnapshot; they are both empty.
Anyway, when I tried to implement the BusinessPartnerInternalID, it seems the email is sent.
But even if I have the confirmation message "email sent", I see nothing in my mailbox.
I thought it was due to the Business Configuration redirecting everything to a single address (as I am on a test tenant). So I did change it to "Send email to business partners", but nothing happens.
Does somebody know how we can check where the email is going?
Thank you very much for your attention Uldis.
Best regards.
Jacques-Antoine

No output type

Hi,
If there is not output type setup is done as it is not required because there is nothing real time happening. Hence I will have to schedule background job for posting the IDOC, can anyone tell me if still I can send IDOC instead of file directly to the vendor.
Can anyone tell me the steps to follow the same.
Regards
Rinku

Thanks Ravi for your reply it really helped. I would appriciate if you can confirm me the steps as follows for EDI setting. Also I will have to write a custom function module as I need to fill IDOC fileds from custom table and from VBAK, VBAP and LIPS so was wondering if have to write the logic in Z functyion module.
     Idoc type DESADV01 Transaction WE30.
     Message Type DESADV Transaction WE81.
     Assign Message Type to Idoc type Transaction WE82.
     Create a distribution Model - Transaction BD64.
     Update outbound parameters of the Partner profile Transaction WE20.
     Assign custom function module to Message type.
     For the Logical system A for the above message types update the partner profile.
For each message type specify the Port and the IDoc types. ( Note : Port definition need to maintained using transaction WE21 and it has to be defined as a Transactional RFC port with RFC destination for system specified, which need to be maintained using SM59 ).

Orders outbound Idoc O/P proposal doubt

Hello,
I need to send Outbound orders Idocs when the Purchase order is released..Can any one tell me whether any standard requirement available to propose the o/p or do i need to write a custom requirement..If i need to write one which field i need to chk in the requirement...?
Thanks,
Larry

Hi,
Go to SPRO > MM > Purchasing > Messages > EDI > Set Up Partner Profile (WE20) - here create partner profile with following details;
Partner Type - "LI"
Under Outbound parmtrs.: -
Partner Role EI + Message Type ORDERS and double click on this and maintain following;
Output options: -
Receiver port        SAPGED
Basic type           ORDERS05
View                 ORDERSWOCON1
Activate "Cancel process after syntax error"
Message Control: -
    Application        EF : Purchase Order
    Message Type:      ZEDI : EDI PO Output
    Process Code       ME10 : ORDERS: Purchase order
Go to SPRO > MM > Purchasing > Messages > Output Control > Message Types > Define Message Types for Purchase Order
> Maintain Message Types for PO - Here Take copy of NEU and create your own Output Type as "ZEDI" for EDI Processing and maintain following parameters;
Dialog Structure - Under "Processing Routines", maintain Program - "RSNASTED" and Form Routine - "EDI_PROCESSING"
Dialog Structure - Under "Partner Roles", maintain Medium as "6" and Function as "EI"
Under Default Values Tab;
Dispatch time - 4
Transmission Medium - 6
Partner Function - EI
> Fine-Tuned Control: Purchase Order - Here add o/p type "ZEDI" with operation "1" and save.
Go to SPRO > MM > Purchasing > Messages > Output Control > Message Determination Schemas > Define Message Schema for Purchase Order - Maintain Message Determination Schema: Purchase Order - here add o/p type "ZEDI' in schema grp "RMBEF1"
Now maintain Po o/p condition record for ZEDI in MN04.
Create PO and check the output.

EDI setting

Similar Messages

Maybe you are looking for