EDI requirements

Hi Experts,
My client wants to use EDI to transmit PO to Vendors.
What are the basic requirements to use EDI functionality in client place and vendor.
Do the vendor need to have SAP? If not SAP what software or hardware vendor needs to have to recieve EDI Docs.
Also what my client need to have other than SAP to send doc by EDI to vendors.
Thanks in advance.
Warm Regards
NDS

hi,
check the link:
[Send PO via EDI|http://help.sap.com/erp2005_ehp_04/helpdata/EN/dc/6b7c9f43d711d1893e0000e8323c4f/content.htm]
Shortly:
1. SM59: Create RFC destination.
2. WE21: Creation of Port
3. WE20 : Configure Partner Profile...
4. BD64: Create distribution Model...
The system generates an IDoc of type ORDERS01...
Regards
Priyanka.P

Similar Messages

Error on activating User Exit on EDI - SD

Hello,
In order to customized our EDI requirements for Incoming Sales Orders
for one of our customers, we need to activate a User Exit
(EXIT_SAPLEDI1_001 on enhacement ZSDIDOC). When doing this, all the
standard Sales Order entry processes are blocked, as well as other
transactions, such us VL12.
Any solution??
Thanks.

ABAP/4 Open SQL array insert results in duplicate database records.".
Error is due to inserting duplicate record in table which is already existing.Take help of abaper,debug,analyze
code which may be cause of error using ST22.If it is application error,apply appropriate sap note.

Convert between EDI order Unit of Measure to Base Unit of Measure

Hi all,
I am looking for a method whereby the following can be accomplished
- Customer orders certain products in LBS UOM...they have been quoted a per LB price and an equivalent CS price by sales and they choose to send EDI orders in LBS
- Base unit of measure for these products is in CS. Stocking unit is cases. Pricing also maintained in cases
- I've maintained alternative UOM in the MM records to convert LBS TO CASES
What i really want is for the customer to submit the EDI order specifying LBS but when the sales order is created i want the order lines in CS. I want to deliver and bill in CS as well. I do not want the sales units to be the units that the order was submitted in.
Any suggestions are appreciated.

Thomas,
We make creative use of the customer-material info record (CMIR) to do what you describe.
Standard functionality of the CMIR will allow the customer to send their internal SKU on an EDI PO, converting it to our SAP material number for use in the sales order.
We maintain a u201Cconversion factoru201D in the CMIR field called Search Term. We use an exit in the inbound IDoc processing code to apply the factor to the quantity ordered and the EDI1 price condition. For example, the factor u201C/006CASu201D would divide the customeru2019s order quantity by six and use CAS as the UOM on the sales order. The EDI1 price is multiplied by six, so that our CAS pricing matches up.
This allows any customer to order with their internal SKU and UOM, while we process the orders with our internal material numbers and preferred units.
An exit on the outbound process code allows us to use the same factor to change the values back into what the customer wants to see.
This works great in the consumer products industry, where we, the supplier, have to deal with inflexible customer EDI requirements.
Regards,
Ken

Difference between ale and edi

Hi experts,
I know this topic was discussed in the forum lot of times. i want to clarify one thing here.
1) can EDI be used to transfer the between tow SAP systems.
2) can ALE be used to transfer data between SAP and non SAP system.
if the answer to the questions is yes then is there any case where we can not use ALE in place of EDI and vice versa.
Also, in what situation we use the BAPI- ALE interface to distribute the data??
thanks
sankar

EDI, stands for Electronic Data Interchange, is the electronic exchange of structured business data between different applications. The EDI architecture consists of
EDI-enabled applications :They support the automatic processing of business transactions.
The IDoc interface: This was designed as an open interface. The IDoc interface consists of IDoc types and function modules that form the interface to the application.
The EDI subsystem: This converts the IDoc types into EDI message types and vice versa. This component of the EDI architecture is not supplied by SAP.
Advantages of the EDI Process
Reduced data Entry Errors
Reduced Processing cycle time
Availability of data electronic form
Reduced Paper Work
Reduced Cost
Reduced Inventories and Better Planning
Standard Means of Communicating
Better Business Processes
Competitive Advantage
ALE
PURPOSE
     ALE supports the distribution of the business functions and process across loosely coupled R/3 systems. Connections from   R/2 and non SAP systems is also supported.
IMPLEMENTATION CONSIDERATIONS
     Distributing business applications and at the same time ensuring data consistency is practical because:
The increasing globalization of markets has led to the physical division of organizational units.
Business processes are not restricted to one organization only and an increasing number of customers and vendors are involved.
The performance of an R/3 System can be improved by distributing the business applications.
Features
ALE supports:
Distribution of applications between different releases of R/3 Systems
Continued data exchange after a release upgrade without requiring special maintenance
Customer-specific extensions.
Communication interfaces that allow connections to non-SAP systems.
Coupling of R/3 and R/2 Systems.
     ALE has functions for controlling messages flows (Audit) and for eliminating malfunctions.
Differences between the two:
ALE is used to support distributed yet integrated processes across several SAP systems whereas EDI is used for the exchange of business documents between the systems of business partners
ALE is SAPu2019s technology for supporting a distributed environment whereas EDI is a process used for exchange of business documents which now have been given a standard format
     Both ALE and EDI require data exchange. An Idoc is a data container which is used for data exchange by both EDI and ALE processes.

Output Message Type MAHN not getting picked up in PO

Hello Experts
   I have configured customized output type ZMAH (similar to MAHN) for reminder process. When I am creating PO this output type is not getting picked up automatically. If I am maintaining it manually I am able to send message for ME9F (Purchase Order) and ME91F (Reminder) successfully. Upon deremination analysis I am getting this message 502 " Output ignored (requirement 103 not fulfilled) ". Reminder are getting picked up from Purchase Value Key to PO.
Any help is appreciated.
Thanks
Ankit

Hello Tej
I have maintained output device but same result.
Here I am listing all parameters that I have used for configuration can anyone please take a look and let me know if I am missing anything
Steps for new Message Type for PO Reminder (ZMAH)
1.     Defined new Table 026 Purchasing Output Determination: Document Type
                                                    (ii) 027 Purchasing Output Determination: Purch. Org./Vendor for EDI
2.     Defined new access sequence Z515 Access Sequence for Archiving.
Following are parameters to the Access Sequence
Access Sequence Number = 1
Table = 026
Description = Purchasing Output Determination: Document Type
Requirement = 103
Exclusive = Yes (box checked)
Access Sequence Number = 2
Table = 027
Description = Purchasing Output Determination: Purch. Org./Vendor for EDI
Requirement = 103
Exclusive = Yes (box checked)
3.     Maintain Output Type ZMAH for PO
General Data
Access Sequence = Z515
Access to condition (Checked)
Multiple Issuing (Checked)
Change Output
Program = SAPFM06P
FORM Routine = ENTRY_NEU
Replacement of Text Symbol
Program = SAPMM06E
FORM Routine = TEXT_SYMBOL_REPLACE
Default Values
Dispatch Time = Send Immediately (when saving application)
Transmission Medium = External Send
Communication Strategy = 0001 (E-mail Document)
Processing Routines
Transmission Medium = 5 (External Send)
Program = SAPFM06P
Form Routine = ENTRY_NEU
Form = MEDRUCK
Partner Roles
Medium = External Send
Funct = VN
Name = Vendor
4.     Fine-Tuned Control: Purchase Order
Oprat. = 3
CType = ZMAH
Name = Output for Reminder
Short Text = Urging letter (expediter)/reminder
Update Print Related Data = Yes (checked)
5.     Maintain Message Determination Schema: Purchase Order
Procedure RMBEF1 (Purchase Order)
Step = 101
Cntr = 3
CTyp = ZMAH
Description = Output for Reminder
Requirement = 103
6.     Assign Schema to Purchase Order
Procedure RMBEF1
7.     Define Partner Roles for Purchase Order
Out. = ZMAH
Med = 5 (External Send)
Funct = VN
Name = Output for Reminder
Name = Vendor
8.     Test Condition Maintained in MN04 (Master Data)
Purch. Org. = 0001
Vendor = 101281
Partner Funct = VN
Medium = 5 (External Send)
Date/Time = 4 Send immediately (when saving application)
Output Device = LP01
Cover Page Text = Reminder PO number &EKKO-EBELN&
Also I have configured Purchasing Value Key, reminders are coming to PO correctly.
Thanks
Ankit

IDOC INVOIC02

Hi ,
The INVOICE IDOC should contain only 50 fields as specified in the spec
when transaction VF01 will create the INVOICE IDOC for the message type INVOIC.
So how the IDOC for message type INVOIC should be created that contains only those required fields.
I have perception that when VF01 will create the Invoice then automatically as per configuration system will create the IDOC based on the message type and output type.
But how to filter only those 50 required fields for the Invoice IDOC that i have to sent EDI Middleware.
Thanks
Prince

Hi ,
In Standard idoc processing it will populate all the mandatory values for message type. If standard system not supporting some data and your EDI requirement needs more data then you have to go add custom segments.
Extra data can be resticted at EDI Subsystem level also.
Thanks

Business Connector Limitations

Hi,
My client wants to use business connector for mutual transfer of the EDI Documents with their customers. For some reason, they dont want to go with XI.
Just wanted to know if there are any limitations with SAP Business Connector? Would it be able to meet all the EDI requirements? What are the scenarios in which the Business Connector would fail?
Thank you in anticipation.

One of the options is to use JOLT.
Using Jolt will enable your Java application or applet to talk with Tuxedo
services in the backend. The Tuxedo service in your case could be the
Elink service, which will connect with your SAP application.
Please check out the latest Jolt documentation or consult BEA Jolt experts.
Baijun Lee
[email protected]
Tuxedo Consulting Service is available.
"Lakshmi Muralidharan" <[email protected]> wrote in message
news:3a405f54$[email protected]..
>
Hi,
We are in the process of web enabling our existing SAP application. Whatwe have right now is a jsp that invokes a BC(Business Connector) service
which calls a SAP function module.But since we have limitations with
Business Connector, we plan to replace the BC service with Elink service.
Now how to invoke the Elink service from my java application? If I have to
create a Tuxedo application for this, is Java version of Tuxedo ATMI
available? How to proceed? Please help.
>
>
Thanks
Lakshmi

Same ISO Code to multiple UOM

Hi Friends,
Can we assign same ISO code to multiple UOM's???. If so, what will be the efeect??
Thanks in advance,
Steve.

Hi,
Assignment of same ISO code to multiple UoM can be done, but the primary code checkbox must be ticked only for one, else would cause conflict for EDI.
The SAP help reads as below:
An ISO code can be assigned to several internal measurement units.
Use
The ISO code is important for EDI. It is used to convert the internal SAP
measurement units into standard measurement units. Data exchange
via EDI requires internal measurement units to be converted into standard
measurement units.
Hope the above answers your query.
Regards,
Vivek

Need Few answers

Hi Gurus...
Please help me for the below questions:
1.What are the different means of communicating with different systems in SAP?
2.Explain PO cycle?
3.Difference between a normal report program and Print program?
4.How do you link a Print program and SAP script?
5.What is use of Output Type in SAP ?
6.How is the Output Type assigned to a document?
7.What are the different SQL Statements in ABAP?
8.Oracle & SQL concepts.
Thanks In advance.

What are the different means of communicating with different systems in SAP?
The following are some of the ways for data exchange between SAP and NON-SAP SYSTEMS.
EDI
EDI, stands for Electronic Data Interchange, is the electronic exchange of structured business data between different applications. The EDI architecture consists of
1.EDI-enabled applications: They support the automatic processing of business transactions.
2.The IDoc interface: This was designed as an open interface. The IDoc interface consists of IDoc types and function modules that form the interface to the application.
3.The EDI subsystem: This converts the IDoc types into EDI message types and vice versa. This component of the EDI architecture is not supplied by SAP.
ALE
ALE supports the distribution of the business functions and process across loosely coupled R/3 systems. Connections from   R/2 and non SAP systems is also supported.
ALE supports:
     Distribution of applications between different releases of R/3 Systems
     Continued data exchange after a release upgrade without requiring special maintenance
     Customer-specific extensions.
     Communication interfaces that allow connections to non-SAP systems.
     Coupling of R/3 and R/2 Systems.
Differences between ALE and EDI
ALE is used to support distributed yet integrated processes across several SAP systems whereas EDI is used for the exchange of business documents between the systems of business partners
ALE is SAPs technology for supporting a distributed environment whereas EDI is a process used for exchange of business documents which now have been given a standard format
Both ALE and EDI require data exchange. An IDoc is a data container which is used for data exchange by both EDI and ALE processes.
IDOC is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data.
When we execute an outbound ALE or EDI Process, an IDOC is created
In an inbound ALE or EDI process, an IDOC serves as input to create an application document.
In the SAP System, IDocs are stored in database.
Every IDOC has a unique number (within a client).
IDOCs are independent of the sending and receiving systems.(SAP-to-SAP as well as Non-SAP)
IDOCs are based on EDI standards, ANSI ASC X12 and EDIFACT. In case of any conflict in data size, it adopts one with greater length
IDOCs are independent of the direction of data exchange e.g. ORDERS01 : Purchasing module : Inbound and Outbound
IDOCs can be viewed in a text editor. Data is stored in character format instead of binary format.
If this is not what you wanted check out this link:
http://delivery.acm.org/10.1145/610000/602250/p156-otto.pdf?key1=602250&key2=0574534911&coll=GUIDE&dl=GUIDE&CFID=5396613&CFTOKEN=99054736
Difference between a normal report program and Print program? And how do we link them.
Basically both same. In either cases you fetch records from the database table. Print programs are Report Programs which acts as data gatherer for SAP Script.
Once you create a Form in SE71 you need to call the following FMs in the Print program.
OPEN_FORM.
WRITE_FORM.
CLOSE_FORM.
The OPEN_FORM does the linking part. You pass the name of the form in the EXPORTING Parmeter FORM.
Inorder to trigger the SAP Script.
What are the different SQL Statements in ABAP?
The SQL statements in SAP are
There are two types of SQL:
Native SQL and Open SQL
Native SQL.
Native SQL allows you to use database-specific SQL statements in an ABAP/4 program. This means that you can use database tables that are not administered by ABAP dictionary, and therefore integrate data that is not part of the R/3 system.
Open SQL.
Open SQL Commands:
SELECT
INSERT
UPDATE
MODIFY
DELETE
OPEN CURSOR,
FETCH,
CLOSE CURSOR
Reward if useful.

ESB- Licensing issues and etc

Hi All,
I was wondering if i could have a few of my doubts cleared
1. According to my understanding since EDI requires licensing and certification, If i use ESB and make it transform the document to some other format. Then if i can post the same document through some 3rd party software whose only function is to post to a particular OXTA or HTTP URL for example.
Will there be any legal issues here ?
2. Where can i find a list of possible transformation which ESB supports. (cXML,OAG,EDI,Rossatenet, UBL etc)
3. Is there any possible comparision between ESB and B2B in terms of transformations and handling/processing documents?
Cheers
Ravi

ESB delivered with basic adapters, DB, AQ, JMS etc.
If you want to use for Rosettanet,EDI etc you need to buy the relevant adapters.
But ESB should not be used for this purpose as it does not have the relevant security and partner link definition stuff that B2B has, this is why they are two different products.
The adapters are just connection technology.

P-card clarifications

Hi all,
We are implementing SRM 7.0 in decoupled mode. I have few clarifications about P-card process
1.What purchasing document is transmitted to the vendor? Is it a PO? Who triggers this document to vendor: requisitioner or purchasing department?
2.Does Purchasing document go through (i.e. is triggered by) purchasing department?
3.Is EDI required to trigger the purchasing document to vendor? Are there alternate means of transmitting purchasing document?
4.Is EDI required to receive bank statements? Are there alternate means of receiving statement
5.When bank sends the bank statement to SRM and is converted to idoc for posting to SRM, does it trigger an accounts posting? Are the following accounts posted?
u2022Clearing account debit
u2022Bank (set up as a vendor) account credit?
6.When does the offset postings happen, i.e. when does the following postings happen:
u2022Clearing account credit
u2022Expense account debit?
Rgds
Sumendra

Hi Masa,
Our design is as follows:
1. ordering is done on phone with the user giving the vendor their P-card number.
2. The first system step is that p-card compant sends the card statement to SRM
3. P-card workflow is trigerred ( In this workflow, the requirement is to have 3 users - the P-card holder , the manager of the P-card holder , and the accounts payable person. The activities doen by each will be :
P-card holder : Change account assignments. Need to attach the receipts and other supporting documents to the workitem
Manager of the P-card holder: Just a business requirement
Accounts payable person : To monitor the account changes by the P-card holder
So I am reasking the questions:
1. If we use only the financial invoice process and not procurement process, is this desigh OK?
2. Can approval manager attach attachments when they get a workitem in P-Card workflow
3. Can P-card workflow pick up 3 approvers - P-Card holder, the manager, and the Finance person
Rgds
Sumendra

User defined Function Required for EDI 850 file fields.

Hi Guys,
I have an requirement where i need to check two fields in incoming EDI 850 file, based on those fields data should be populated to target side fields IDOC(ORDERS05).
here is the requirement
If Field.01 = "001" and field.02 exist then
   Set TDID = "31"
If Field.01 = "001" and field.02 exist then
   Set TSSPRAS = "A"
If field.01 = "001" and field.02 exist then
   Set TDLINE = Concat("XXXXXXX" + field.02 (mm/dd/yy))
If field.01 = "002" and field.02 exist then
   Set TDLINE = Concat("XXXXXXX: " +   field.02 (mm/dd/yy))
If field.01 = "010" and field.02 exist then
   Set TDLINE = Concat("XXXXXXX: " +   field.02 (mm/dd/yy))
If field.01 = "015" and field.02 exist then
   Set TDLINE = Concat("XXXXXXX: " +   field.02 (mm/dd/yy))
If field.01 = "037" and field.02 exist then
   Set TDLINE = Concat("XXXXXXX: " +   field.02 (mm/dd/yy))
If field.01 = "038" and field.02 exist then
   Set TDLINE = Concat("XXXXXXX: " + field.02 (mm/dd/yy))
If field.01 = "063" and field.02 exist then
   Set TDLINE = Concat("XXXXXXX: " +   field.02 (mm/dd/yy))
If field.01 = "064" and field.02 exist then
   Set TDLINE = Concat("XXXXXXX: " +   field.02 (mm/dd/yy))
Here Field01 and Field 02 are sender side fields.we need to check this two fields . I Know this can be created with graphical mapping but as per requirement i need to write UDF bcoz with graphical mapping this would be more complex.
so can any one please provide me UDF for this.
Regards,
Sandeep.

Hi,
you can do it with standard functions.
If_1 source -> length -> greater -> constant 2
then_1 if_2 substring source 0, 2 -> equals TN
then_2 -> constant ""
else_2 -> source
else_1 source
Regards
Patrick

What are the authorization requirements for an EDI communication user?

I'm trying to find documentation describing the authorization objects required for an EDI communication user to have appropriate RFC access.

Take a look in the FAQ thread at the top of the (security) forum...
Is there something in addition to the standard documentation which you would like to know?
Cheers,
Julius

Idoc to edi scenarios (mapping help is required)

hi expects ,
    i am working on idoc to edi scenarios in which i am using seeburger abapter.and i have to use java mapping with using some standard function.
INPUT IDOC :
                    Name                         M/C     Min Use      Max Use        Description
INPUT*                                              M               1           1
Record EDI_DC40*                                 C               0           1                       Control Record
Record E2EDK01*                                  C               0           1                       Document Header General Data
     Record E2EDK14*                                  C               0          12                       Header Organizational Data
     Record E2EDK03*                                  C               0          10                       Header Date Segment
Record TEMP_DATE*                                C               0           1                       Temporary Date Segment
     Record DEL_DATE*                                 C               0           1                       Temporary Date Segment
     Record E2EDK04*                                  C               0          10                       Header Taxes
Record E2EDK05*                                  C               0          16                       Header Conditions
Record E2EDKA1*                                  C               0       99999                       Header Partner Info
Record TEMP_SHIP_TO*                             C               0           1                       Ship-to Info
Record TEMP_SOLD_TO*                             C               0           1                       Sold-to Info
Record TEMP_PAYER*                               C               0           1                       Payer Info
Record TEMP_CARRIER*                             C               0           1                       Carrier Info
Record TEMP_DISCHARGE_PORT*                      C               0           1                       Port of Discharge info
     Record TEMP_NOTIFY*                              C               0           1                       Notify Info
Record TEMP_NOTIFY_ALSO*                         C               0           1                       Notify Also Info
Record TEMP_EXIT_PORT*                           C               0           1                       Port of Exit Info
Record TEMP_CONSIGNEE*                           C               0           1                       Consignee
Record TEMP_SHIPPER_INFO*                        C               0           1
Record E2EDK02*                                  C               0          10                       Header Reference Data
     Record TEMP_E2EDK02*                             C               0           1                       Temp E2EDK02
Record TEMP_PO_STRING*                           C               0           1                       TEMP PO STRING
Record E2EDK17*                                  C               0         999                       Header Terms of Delivery
     Record TEMP_E2EDK17*                             C               0           1                       Temp transportation terms
     Record E2EDK18*                                  C               0          99                       Header Terms of Payment
     Record TEMP_TERMS*                               C               0           1
Record E2EDK35*                                  C               0          10                       Additional Data
Group E2EDKT1:2*
OUTPUT FIELD:
Segment B2*                                      M               1           1                       BEGINNING SEGMENT FOR SHIPMENT INFORMATION TRANSACTION
     Segment B2A*                                     C               0           1                       SET PURPOSE
Segment N9:6*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:7*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:8*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:9*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:10*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:11*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment CUR*                                     C               0           1                       CURRENCY
Segment ITD*                                     C               0           1                       TERMS OF SALE/DEFERRED TERMS OF SALE
     Group DTM_GROUP*                                 C               0           1
Segment DTM*                                  C               0           1                       DATE/TIME REFERENCE
Segment DTM:2*                                C               0           1                       DATE/TIME REFERENCE
Segment DTM:3*

Hi,
To do the mapping,,,,even you can go for graphical mapping....
But some of the context handling issues you need to deal with,
like....
1.Never map set context of source fields to element level but Segment level.
2. Always you need to check for qualifiers while mapping it to Traget field.
Thanks & Regards
Akshay.
Dont Forget TO Give Points.

Many .sda files required,EDI,Seeburger?

hi,
do we need to create .sda files using Seeburger BIC Mapper for each mapping and deploy each <b>.sda</b> file on to XI server using SDM?

Hi Babu,
Let me tell you the step by step process of SDA creation and deployment.
1) Go to BIC Mapping designer tool
2) Create the maps of needed documents(For example if we know that we will be needed EDI 850, 810,855 etc transactions then we need to add E2X(EDI To XML) and X2E (XML to EDI maps in a project
3) Select that project folder
4)Right click on it
5)Create deployment (SDA) file.
6)Default name of the created SDA file is "Mapping_User.sda"
7)Deploy this .sda in to the J2EE side of XI server using SDM.
Now if you anticipate that you have to add some aditional EDI maps for transtions other then the one covered in the earlier SDA file ::
1) Add the new maps in the old project.
2) Create the new SDA file
3) Again name of the created SDA file is "Mapping_User.sda"
4) deploy this new SDA file.
5) It will over write the existing "Mapping_User.sda" .
Hope i have answered your question
Let me know if you need any further clarifications.
regards
Piyush

EDI requirements

Similar Messages

Maybe you are looking for