Purchasing operation through edi

hello Gurus,
Can any one tell me how can we carry out purchasing operations through EDI,
step by step?
Thanks in advance

I just fixed that today... so I'm not sure what I'm supposed to use for Itunes, as the credit card company JUST got my current address

Similar Messages

Create Purchase Order through EDI

Hello Everybody,
I want to know how to create Purchase order through EDI. I will receive text file from third party system. I have made most of the configuration related to EDI like Port -File, Partner Function etc. I am using message type PORDCR and Idoc type PORDCR05.
But i do not know how the SAP first will convert the text file into IDoc and then create Purchase order. Can any body help me how to go about it? What steps i have to follow. I will have text file from that i have to create Purchase order through EDI.
Thanks in advance.
Regards,
Manish

Hi,
Create Purchase Order through EDI
Regarding on your query,
You can use the standard ORDERS05 idoc type itself to send outbound idocs.
It will be the middleware or the integration team that will send this IDOC to the receiving system.
or
Maintain Partner Profile in WE20, RFC Connection to the Middleware in SM59 and Port in WE21.
Maintain Output Procedure/Output Type/Access Sequences/Condition Records from NACE
Generate the Outbound 850 (PO) from ME21N
Regards,
Sekhar

How to Send Purchase Order through EDI/IDOC.

Hi Experts,
We are using SAP ECC.5. And intending to send the Purchase Order to Supplier through EDI/IDOC and Receive the Inbound Acknowledgement.
Appreciate, if you could help me, the required Configuration details for outbound and inbound (PO & Acknowledgement).
Reg
Kumar

Hi Kiran
Many thanks for the response. It is true that by changing the message type to EDI can generate idoc. What is not clear is any other config we need to do interms of Message generation, Resubmitting failed IDOC etc..
Out requirement is that we would generate the IDOC for New and changed docs and send to external EDI converter.
Inbound, receive the IDoc and post the acknowledgement.
Appreciate, if you could forward any document link which can explain the details.
Reg
Kumar

Purchase Order through EDI

Dear Experts,
I got a requirement recently for sending PO from SAP to vendor system (non SAP) through EDI interface.
Clients all purchasing and inventory is handling an out side vendor.
Anybody can help me with how SAP can link other system throuh EDI.
Thanks for your help
John K.

Hi,
You can use the standard ORDERS05 idoc type itself to send outbound idocs.
It will be the middleware or the integration team that will send this IDOC to the receiving system.
Regards,
Subramanian

Posting an 850 Purchase Order through EDI

Heyy Guys,
I am trying to post an 850 from translator and I am struck at the control record mapping.
I maintained VOE4 entries for mapping external partner number to internal partner number.
But doesn't the SNDPRN field in the control record use that table?? Can we populate the SNDPRN field with external partner number?
I tried to do it and it is not determining the partner profile.
My other issue is if we have to populate SNDPRN field with the actual SAP customer number, do we need to maintain a cross reference in translator again? Doesn't that defeat the basic purpose of SAP's VOE4 table?

Dear,
Check: http://help.sap.com/saphelp_sm32/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/frameset.htm
and
Sending PO through EDI
Anybody can help me with how SAP can link other system throuh EDI.
http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/100e954a-0f36-2b10-dfa9-9c3880da7ff3&prtmode=print [original link is broken]
Regards,
Syed Hussain.

Purchase order changes through EDI

Hi All,
Is it possible to transmit only changes made againt each purchase order through EDI. If so how that can be done.
For example if the quanity of purchase order changed then only changed quanity field should be transmitted through EDI.
Thanks & Regards,
N. Laxman

Hi Laxman.
What do you have on WE20?
Usually you have two records. One to send the PO when you create and another one for changes;
Partner role | Message Type | Message Function
OA              | ORDERS           | 850
OA              | ORDCHG          | 850
For the message type ORDCHG in the config you have to set the message control as follow
Application | Message type | Process code | Change
EF               | NEU                 | ME11              | checked
Hope this helps.
Regards
Eduardo

Goods Supplier details through EDI - Purchase Order

Hi All,
We are sending purchase orders to vendor through EDI. Generally we do not have details of the Partner - Goods Supplier (GS) in the idoc in the segment E1EDKA1. .
Now our client wants to show the details of GS also in the segment of the idoc. As per SAP note 456127 , SAP has not given provision for it.
Has anyone got this type of requirement , and has someone any idea on adding a new segment showing Goods Supplier in it.
Thanks in advance.
Regards,
Vengal Rao.

Hi,
Please check the below links...
http://help.sap.com/saphelp_sm40/helpdata/en/af/5f28a7669648dfb71b418d243f2a82/content.htm
http://help.sap.com/saphelp_sm32/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/content.htm
Hope it may helps you.
Kuber

Purchase Order sending through EDI

Dear Experts,
I got a requirement recently for sending PO from SAP to vendor system (non SAP) through EDI interface.
Clients all purchasing and inventory is handling an out side vendor.
Anybody can help me with how SAP can link other system throuh EDI and make data transfers.
Thanks for your help
John K.

Hi,
As you are saying that the vendor is interested in reciving the PO through EDI, then you need to check all the below mentioned aspets when you are going to construct an interface:-
1. Which EDI message format (TRADACOM, ANSI or EDIFACT)
2. how are they going to receive it?
3. What fields needs to be mapped into the EDI message
4. Which version are they expecting.
5. What type of message are they expecting (like PO, GR or IR)
First check out on all the above questions, setting up an interface from SAP is easy the only thing which you need to do is going to on the EDI front.
I have used TLE, Harbinger, Gentran, XI and Pathfinder EDI sub systems to transmit the purchase and sales related information.
Thanks,
Mahesh.

How to check a Purchase order sent through EDI?

Dear All ,
I have created a P.O and in Message tab there is a green indicator which shows that this P.Ois succsfully sent through EDI , also Condition records are well created before creating this P.O , but vendor says that he does not recoeved the P.O by EDI Process.
can you please help me out that how n where to check that this P.O is sent through EDI. I had then manuallly given the condition in Message for sending this P.O by E MAIL and it had worked , also i did chkd in trxn in SOST , this p.o sent through e mail.
Thanx in advance.
Rgds,
sap11

Dear,
For SCOT settings check with BASIS team..
OR
Use SCOT, double-click the INT node.
Use the 'Set' button in the supported address types section.
In the 'address area' enter the pattern you want, like email@removed as per
your example. "*" is a wildcard.
Any email sent which does not match the pattern will fail with a "no
route" error (seen in SOST).
Have you checked WE02 Tcode...??
Utsav

Creation of Sales orders through EDI

Hello,
We have a problem when creating sales orders through EDI.
We are getting IDOCs with a delay of 1 second.Before
creating sales orders through the posting function
module IDOC_INPUT_ORDERS, we need to validate for
reference Purchase order number in the IDOC. If there is
any sales order in the database with the Purchase order
number in the current IDOC that sales order should be
blocked.
We already put a validation in the User-Exit of the
posting function module. Because of the frequency of
IDOCs we receive, this validation is getting failed.
Can anybody tell me, how to process only 1 IDOC at any
given point of time before the Posting process.
Thanks,
Madhusudan.

Hi Sanjeev,
Thank you very much for helping me out in this problem.Still I haven't got the solution.
I tested the above mentioned configuration option by putting the Check Purchase Order Number field to 'A' in the transaction VOV8. But while creating sales orders, it is giving only information message. Is there any other way, to restrict the Duplicate PO value through configuration setup.
can you also explain how to use Enqueue and Dequeue FMs in the inbound posting function module.
Regards,
Madhusudan.
Message was edited by: Madhusudan Budati
Message was edited by: Madhusudan Budati

Changed PO through EDI

Hello,
We have a scenario in which we want to sent complete PO after making some changes through EDI.
An output message gets created when new PO is created and same is sent to the vendor through EDI. When some changes are done to any of the line item in PO then we want to send the complete PO again to the vendor through EDI by triggering the output message.
Could you please let me know how this can be achieve ?

Hello,
do the following,
Under the output type config>> Change output>>, enter FM06AEND as the program and CHANGE_FLAG as the routine.
Under Fine tuning for message control, copy teh existing ones withb operation 1 and amend it to operation 2.
Under asssign schema for PO, make sure teh check box under "N" is checked- New message determination. You are set.

Setting for Sending the purchase order via EDI

Hi,
I have no knowledge on the Sending the Purchase Order via EDI.
What is the setting that need to do in MM side?
Anyone has any idea?

Hello Janice,
Please refer the below LINKs which would provide you clear approach for configurational task of sending PO through EDI.
[LINK|http://help.sap.com/saphelp_46c/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/frameset.htm]
[LINK 2|http://www.erpgenie.com/sapgenie/docs/advanced_guide_to_edi_configuration.doc]
Regards,
SARTHAK

Re : Inter company stock transfer through EDI

Hi
 How to do the intercompany stock transfer through EDI. In this if Purchase order is created from one comapny a sales order should created automaticall in another Company. Fot this what is the SPRO settings.
How to do this.
Thanks
Anto

Hi,
continues from here,
Inbound file: edi_in
Function module: See text below.
Status file parameters
Directory: /home/edi/<portname>/
Outbound file: status.idoc
Function module: Leave blank if using above
u2022 Both the portname and the exchange directory should be created according to the same naming convention. However, the portname should be in upper case whereas the corresponding directory name should be in lower case (see examples below).
 Portname (upper case):
 <portname>
 Exchange directory name (lower case):
 /home/edi/<portname>
 where <portname> consists of:
 EDI<system name><client number><id char>
 <system name> is the name of system on which port exists eg. F01, PG1 etc.;
 <client number> is name of client on system which will use this port; and
 <id char> is a single alphabetical character such as u2018au2019,u2019bu2019 etc. typically, u2018au2019 will denote dynamic outbound file naming (used for testing) whereas u2018bu2019 will denote static outbound file naming. All ports will use static inbound filenames.
For example, the name of a port using dynamic file naming on system F01, client 610 would be named EDIF01610A. The exchange directory would be named edif01610a. Similarly, the name of port using static file naming on system PG1, client 600 would be EDIPG1600B. The exchange directory name would be edipg1600b.
Note that the function u201CEDI_PATH_CREATE_USERNAME_DT_TMu201D can be used in the u201CFunction moduleu201D field of the Outbound file parameters if IDocs are to be written to multiple files. In this case, the corresponding outbound filename field should be left blank. The standard IDoc exchange interface between the SAP EDI component and the EDI subsystem uses a single file for each transfer direction. However, should the exchange interface change, or for testing purposes, the function modules for dynamic naming can be used.
2.4.2. Control of EDI processes in R/3
2.4.2.1. Maintain: Outbound Process Code (WE41)
IMGCross-Application ComponentsALE Extensions  Outbound
Check that the outbound EDI processes in the R/3 system are defined. Indicates which ABAP/4 function module to execute in order to create an outbound IDoc.
The following assignments are available for R/3:
2.4.2.2. Maintain: Inbound Process Code (WE42)
IMGCross-Application Components  ALE  Extensions  Inbound
Check that the inbound EDI processes in the R/3 system are defined. Indicates what kind of inbound processing to execute.
 A long list of options is available under Processing by function module, relevant ones are:
INVF INVOIC FI Invoice receipt (Financial Accounting)
INVM INVOIC MM Invoice verification (Mat Management)
ORDC ORDCHG Change customer order
ORDE ORDERS Create customer order
ORDR ORDRSP Purchase order confirmation
2.4.2.3. Control: System Process Codes (WE40)
 Choose Processing by task. Check that the codes indicating the type of EDI processing error are defined. The only valid entries are the entries shown on the screen, as they are directly called via the EDI basis module.
2.4.2.4. Control: Status maintenance (WE47)
 Check that the codes indicating status of IDoc processing are defined. The status values for outbound IDocs are between 01 and 39, while the status values for inbound IDocs begin with 50. These values are delivered by SAP and cannot be customised.
2.4.2.5. Control: Partner Types (WE44)
 Check that the codes that identify the commercial relationships between the receiver and sender are defined. Values are delivered by SAP. Names of the programs and routines that validates the entry of the EDI trading partner ID:
Partner type Report name Form routine
B - Bank RFETESTP READ_T012
KU - customer RSETESTP READ_KNA1
LI - vendors RSETESTP READ_LFA1
LS - logical system ( ALE) RSETESTP LOGSYS
2.4.2.6. Control: Forward Inbound (WE45)
Allows for the forwarding of IDocs to a specific application. Contains the exactly defined destination of an inbound IDoc within the SAP system. Usually no changes are required.
2.4.2.7. Control: Status Process code (WE56)
Choose Processing by task: The following set-up has been provided as default:
Process code: EDIS
Identification: TS30000078
Description: EDI-IDoc status record processing
The process code is for inbound status, The ID type is an identification code for inbound processing method (workflow or standard task) of the status record.
3. MM IMG CONFIGURATION
3.1. Global settings (IMG):
3.1.1. Units of measure (IMG  Global settings):
The ISO code is important for EDI. It is used to convert the internal SAP units of measure into standard units.
The MM configurer must link the Unit Of Measure, EACH, with the ISO code PCE (Piece).
3.2. Link Schema to Purchase order
Check the following:
IMG  MM  Purchasing  Message determination  Message determination  Message Schemas
Execute transaction u201CDefine Message Schemas for Purchase Orderu201D
Select transaction: Assign Schema to purchase order
Add: Usage =B for output
 Application = EF for purchase order
 Procedure = RMBEF1 for purchase order
3.3. Link application to EDI interface via message control:
IMG  MM  Purchasing  Messages  Output Control
Check following under Output Control:
 Condition table
 Access sequence
 Message types
 Message schema
 Output control
3.4. Enabling Multiple Output for Purchase Orders (Optional)
For example: EDI & Printing
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022 Create new access sequence (e.g. ZPUR), copy the access sequence 0001 but leaving the ''E'' flag blank (Exclusive is off). (Transaction M/50)
u2022 Goto Define message types  maintain message types:
 Create a new message type (e.g. NEU1), setting the output type to 1 for printed output and using ZPUR as access sequence. (Transaction M/34)
u2022 Goto Message Schema  define message schema  maintain output determination procedure:
 Update procedure RMBEF1 by adding a step for the new condition type (e.g. NEU1) prior to the standard delivered step for NEU. (Transaction M/36)
u2022 Goto Processing program  Define Processing program  Output program: Purchase Order.
 - Add a NEU1 record to table TNAPR. The program FORM Routine and layout must be specified. (Copy an existing NEU record). (Transaction OMTB)
u2022 Goto Processing program  Define Processing program  Output by partner type.
 - Add NEU1 record for VN (vendor). (Transaction OMTG)
3.5. Link Output type (fax=2, E-mail=7) to NEU (Purchasing)
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022 Goto Processing program  Define Processing program  Output program: Purchase Order.
 - Add another NEU record to table TNAPR with the appropriate output medium. Copy an existing NEU record. (Transaction OMTB)
u2022 Goto Processing program  Define Processing program  Output by partner type.
 - Add NEU record for VN (vendor). (Transaction OMTG)
4. SD APPLICATION REQUIREMENTS
Assumption: SD is only used for testing purposes and configuration is based on a need basis - only configure the minimum.
Reference SAP Course manual Chapter 11.
4.1. EDI Configurations
4.1.1. Conversion of SAP item categories to IDOC item categories (VOE1)
IMG  S&D  EDI  EDI Messages  Conversion of SAP item categories to IDOC item categories
Add the following entry:
For Standard Item description : 0 OR LDN
Typically error message: ''Transaction LDN is not defined".
4.1.2. Partner functions
IMG  S&D  EDI  EDI Messages  Configure EDI Partners Partner  Application  Partner function
Check that the following partner functions exist: (at least)
SP Sold-to party
VN Vendor
BP Bill-to party
SH Ship-to party
Note - the German abbreviation is passed to the IDoc.
4.2. S&D Sales Configurations
4.2.1. Maintain Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Define item categories
Add LDN for standard item:
 Item type = B
 Relev for billing = B
 Tick following: Bus data item
 Sched line allowed
 Credit active
 Pricing
 Screen seq. grp = N
4.2.2. Assign Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Assign item categories
Add/Update the following entries:
 1 2 3
Sales doc type OR OR OR
Item category group NORM DIEN LEIS
Item category LDN TAD
LDN LDN
4.2.3. Assign Schedule line categories
IMG  S&D  Sales  Sales document  Schedule lines  Assign Schedule line categories
Add Item category LDN to table (with no other parameters).
4.3. S&D Pricing Configurations
4.3.1. EDI pricing condition types
IMG  S&D  Basic functions  Pricing  Pricing control  Define condition types  Maintain condition types
Maintain the following condition types:
 EDI 1 - Calculate type =C for Quantity
 EDI 2 - Calculate type = B for Fixed amount
4.3.2. SD Pricing procedures (V/08)
IMG  S&D  Basic functions  Pricing  Pricing control  Define & Assign pricing procedures
Maintain pricing procedure for ZVAA01 (Standard).
Select control and add EDI1 and EDI2 as steps 1 and 5 respectively with no other parameters.
5. INVOICE IMG CONFIGURATION
No additional IMG configuration (not partner specific) was needed for Inbound Invoice processing.
Thanks,
Swamy H P

I have a Problem in print the long description data through EDI.

I have a Problem in print the long description data through EDI:Actually we want to print the long description data through EDI, but it not handling our huge long description data. Here is the example of that>We can print the first two lines into EDI output, but it is failing to print the below text:
EPSON, TM-U590 Series: Reliable 88 column slip printer. Operator friendly dot matrix impact printing. Ideal for hotel, bank, restaurant and many more applications . Includes: Printer, Black ribbon & a Connect-It Interface. Power Supply & interface cable sold separately. All printers are RoHS compliant & have a standard 1 year depot warranty. 
 -------------------------------------Failing to print this lines------------------------------------------------------------------
COLORS: Epson Cool White (ECW) Only Click links below for helpful Information <table border="0" bordercolor="" style="" width="100%" cellpadding="5" cellspacing="5"><tr><td><CENTER><A HREF="www.sample.com"f.2605" target="_blank">Spec Sheet</a></CENTER></td><td><CENTER><A HREF="www.sample.com"f.2606" target="_blank">MSRP Price List</a></CENTER></td><TD><CENTER><A HREF="www.sample.com"f.2868" target="_blank">Product Information Guide</a></CENTER></TD></TR><TR><td>Warranty Information</td></tr><Tr><td><CENTER><A HREF="www.sample.com"f.2554" target="_blank">Depot Warranty</a></CENTER></td><td><CENTER><A HREF="www.sample.com"f.2555" target="_blank">Spare In the Air Warranty</a></CENTER></td><td></td></tr></table> 
Please provide some useful thoughts on this EDI issue.
Thanks
Ameer

Try using the FM:
ENQUE_READ2
Passing the follwing values:
GNAME --> VBAK (Sales Order header table)
GARG --> The lock argument
 (This will be a combination of client number anb Sales Order No.
 Eg: '3001210000054' where the first three digit i,e 300 is the client No
 and 1210000054 is the sales order no.)
Regards,
Firoz.

Automaticf creation of purchase order through pr

Dear Consultants,
system is not creating automatic purchase order. in me59n i am getting the following error
Requisition could not be converted
i have done the following setting for automatic creation of purchase order
1. in materil master record i have checked auto po.
2. in vendor master record i have checked automatic purchase order
3. i have created purchase info record with the combination of material vendor purchase organization.
4. in source list i have fixed the vendor in me01
5. in source determination under define regular vendor i have checked the box against the required plant.
kindly let me know what all other configurations are required for creating automatic purchase order through purchase requisition
Regards/ Siri

Hi
Is this purchase requisition created during MRP run??
If yes then have you marked the sourcelist record for this vendor as MRP relevant??
If the purchase requisition is generated manually then whether the source of supply was assigned in the PR??
In ME59N, the PR would be converted to PO if the PR has the assigned source of supply.
Regards
Prasad

Purchasing operation through edi

Similar Messages

Maybe you are looking for