GU SAP S4 HANA Configure EDI Partners Docx 1713327769

Mickael QUESNOT © https://s4hclub.
com/
http://www.youtube.com/user/MrSharesap
SAP SPRO Electronic Data Interchange for Dummies

Configure EDI Partners (Purchase Order > Sales Order with Material KMAT)
Here's a condensed guide to configure EDI partners for purchase orders turning into sales
orders with Material KMAT using IDoc ORDERS in SAP:
Steps:
1. Partner Profiles (WE20): Define partner profiles (WE20) for your vendor (LI type) and
optionally your company (LE type) for order confirmations.
2. Ports (WE21): Create ports (WE21) to specify communication channels for receiving
and (optionally) sending IDocs.
3. Message Type (WE21): Set the "Process code" in message type ORDERS (WE21) to
the sales order creation process (e.g., ORDS).
4. Conversion Rules (BD62 - Optional): Create conversion rules (BD62) if data mapping
between your vendor and SAP is needed.
5. Partner Determination : Define procedures (if needed) to automatically determine
sales order type, sales org, distribution channel, and division for the sales order.
6. Test: Send a test purchase order from your vendor and monitor IDoc processing
(WE02, WE05) to ensure successful conversion into a sales order with Material KMAT.
In this IMG activity, you configure EDI partners.

Notes
You do not maintain partner profiles in Customizing; you maintain them in the application by
choosing Tools -> Business Communication -> IDoc -> Partner profile.
1.1.1 Convert External to Internal Partner Numbers

Convert an external partner number into an internal number.
Use
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
1
Mickael QUESNOT © https://s4hclub.com/
In each customer's external system, several partners with external numbers might exist. In
the EDI message, the customer does not necessarily send the partner numbers that you
internally use in your system. In this case, you must convert the external number belonging
to a partner into an internal number.
In addition, multiple addresses may be assigned to a single partner. In this case, each external
partner number must be mapped with the combination of an internal partner number and an
address ID. However, note that no address ID should be maintained for the partner with
partner function Payer.
For more information about multiple address handling for business partners in sales and
distribution and how to enable it, see Multiple Address Handling in SD Documents Using SAP
Business Partner.
Example
In your system, you have a customer ABC. In this customer's external system, several partners
with external numbers exist:
Partner Function External Number Internal Number

Sold-to party 01 10100080
Bill-to party 02 10100011
You then have to enter the following data:
Customer Partner Function External Partner Internal Number

ABC SP (sold-to) 01 10100080
ABC BP (bill-to) 02 10100011
When multiple address handling is enabled, you must also enter address IDs, for example:
Customer Partner Function External Partner Internal Number Address ID

ABC SP (sold-to) 01 10100080 41000
ABC BP (bill-to) 02 10100011 75000
2
3
Address Number
4
Internal key for identifying a Business Address Services address.

For more information about the meaning and use of the address number and the Business
Address Services concepts, see the function group SZA0 documentation.
5
1.1.2 Assign Customer/Supplier to Sales Organization Data

Assign customer or supplier to sales organization data.
6
Use
You can assign a customer or a supplier to sales organization data for the Electronic Data
Interchange (EDI) process.
The order type is automatically proposed by the system if it is not already in the IDoc.
Notes
Note that no matter the sales area data are provided or not by the customer in the inbound
EDI message, return order type and discrepancy allowance of payment terms are always
determined from the assignments in this activity. For more details, see the example below.
Example
As a key user for Customizing, you maintain the following entry in this Customizing activity:
Dscrcy
Customer Supplier Sales Org Distr. Channel Division SaTy Ret. Order
.
10100080 10300080 1010 10 00 OR <blank> B
Scenario A: You receive from customer 10100080 a sales order inbound EDI message for
creation, where the sales area information is not provided, the system then reads this
Customizing activity and uses the data determined by this assignment to create a sales
document, in this case, a standard order with sales organization 1010, distribution channel
10, division 00, and discrepancy not allowed for payment terms.
Scenario B: You receive from customer 10100080 a sales order inbound EDI message for
creation, where the sales area and sales document types are already provided (for example,
1710, 10, 00, OR), the system then reads this Customizing activity for return order type and
discrepancy allowance for payment terms. In this case, the system creates a standard order
with sales organization 1710, distribution channel 10, division 00, and
discrepancy not allowed for payment terms.
7
8
9
10
1.1.3 Determine Partner Functions For EDI Outbound Processing

In this IMG activity, you specify partner functions that should appear in the IDoc. If the field
in the "System" column is selected, the partner is obligatory for the EDI outgoing message.
1.1.4 Notes
You cannot delete obligatory partners from the table.
11
1.2 SAP IDoc Configuration for Purchase Orders and Sales Orders (WE20)
In SAP, IDocs (Intermediate Documents) facilitate electronic data interchange (EDI) between
your system and external partners. They allow you to exchange business documents like
purchase orders and sales orders electronically. Here's how WE20 fits into the configuration
process:
WE20: Partner Profile Configuration
WE20 is the transaction code for configuring partner profiles in SAP. These profiles define the
communication settings for exchanging data with your business partners electronically. When
dealing with IDocs for purchase and sales orders, WE20 plays a crucial role:
1. Inbound and Outbound Communication: You create separate partner profiles for
inbound (receiving IDocs) and outbound (sending IDocs) communication with your
partners (vendors for purchase orders, customers for sales orders).
12
2. Message Type and IDoc Type: Within the partner profile, you specify the message
type (e.g., ORDERS) and the corresponding IDoc type (e.g., ORDERS05) used for
purchase and sales orders.
3. Process Codes: You also define the process code, which determines how the
received IDoc data is processed within SAP. (e.g., ME10 for purchase orders, ORDS for
sales orders).
4. Ports and RFC Connections: WE20 might involve configuring ports (communication
channels) and RFC connections (remote function calls) depending on your specific EDI
setup.
Overall Process Flow:
1. Partner Sends Order (Electronic): Your vendor or customer sends a purchase or sales
order electronically in an IDoc format.
2. WE20 Configuration: The partner profile in WE20 defines how to process the
received IDoc.
3. Data Mapping and Processing: Based on the configuration, the IDoc data is mapped
to the corresponding SAP fields and processed using the specified process code (e.g.,
creating a purchase order in ME22N).
4. Order Creation in SAP: The relevant order (purchase or sales) is created in your SAP
system.
Additional Notes:
• WE20 configuration is a complex task and typically requires expertise in SAP EDI.
• This is a simplified overview. The specific configuration steps might vary depending on
your SAP version and EDI setup.
• Consider referring to SAP documentation or consulting an EDI specialist for detailed
configuration guides.
For further learning, you can explore these resources:
13
• SAP Help Portal: Search for "WE20" or "IDoc configuration" in the SAP Help Portal for
detailed information.
• Community Forums: Search online forums like the SAP Community
https://community.sap.com/ for discussions and solutions related to IDoc
configuration.
• Video Tutorials: There are video tutorials available online (e.g., YouTube) that
demonstrate the WE20 configuration process for purchase and sales orders using
IDocs YouTube: https://m.youtube.com/watch?v=HlOP1YIDbzA.
14
15
16
17
18
19
WE05
20
EDI: Inbound partner profile does not exist
21
22
23
1.3 Converting Data Between Sender and Receiver IDocs in SAP
SAP provides functionalities within the ALE (Application Link Enabling) framework to handle
data conversion between sender and receiver systems when using IDocs (Intermediate
Documents) for data exchange. Here's a breakdown of the key methods:
1. Conversion Rules (Transaction BD62):
This is the primary method for data conversion during IDoc processing. Here's how it works:
• Define Mapping: In BD62, you define rules that map data elements from the sender
IDoc segment to the corresponding receiver (SAP system) field.
• Techniques: You can leverage various techniques within conversion rules, including:
24
o Search tables: Reference existing SAP tables to translate codes or perform

lookups (e.g., convert vendor codes from partner system to your internal SAP
codes).
o Formulas: Implement calculations or data manipulation logic using formulas
(e.g., convert units from inches to centimeters).
o User exits: Develop custom code (ABAP) for specific data transformations not
achievable with standard functionalities.
2. Partner Profile Configuration (Transaction WE20):
WE20 plays a crucial role in assigning conversion rules:
• Message Type Assignment: Within the partner profile for your business partner
(vendor/customer), you specify the message type used for the data exchange (e.g.,
ORDERS for purchase/sales orders).
• Conversion Rule Assignment: You then assign the relevant conversion rule(s) to the
specific message type. This determines which rules are applied when processing
inbound IDocs from that partner for that particular message type.
Benefits of Conversion Rules:
• Standardize data format: Ensure data from external partners conforms to your SAP
system's expectations.
• Data validation: Validate incoming data based on pre-defined criteria (e.g., checking
material number existence).
• Data manipulation: Perform complex transformations, calculations, or
splitting/combining data from different segments.
Additional Considerations:
• Expertise Required: Configuring conversion rules effectively often requires
knowledge of SAP data structures, ABAP programming (for user exits), and business
logic.
25
• Testing: Thoroughly test conversion rules to ensure accurate data transformation

during IDoc processing.
Alternative Methods (Less Common):
• Outbound Parameter Mapping: In specific scenarios, you can define outbound
parameter mapping within message types (WE21) to manipulate data before sending
an IDoc from your SAP system.
• ALE Business Add-Ins (BADIs): For highly customized data transformations, consider
using ALE BADIs, but this approach requires advanced ABAP development skills.
By effectively utilizing conversion rules and partner profile configuration, you can ensure
seamless data exchange between your SAP system and external partners through IDocs.
26
27
1.3.1 Create Rule

The tool Converting Data Between Sender and Receiver enables you to convert and map field
content from a sender field to a receiver field. In this way, you can map organizational units,
units of measurement, or your own, customer-specific field content from one system to
another.
This is a general tool used for the definition and maintenance of rules in ALE.
To do this, you must perform the following steps in this order:
1. Create the rule: The rules are defined by segment.
2. Maintain the rule: When you maintain rules, the conversion at the field level is determined
according to defined rules.
3. Assign the rule to a message type: The assignment defines when the rule is used. This can
be sender-specific, receiver-specific, and message type-specific.
__________________________________________________________________________
____________________
Note: You can use this tool only if you are using the Web Application Server (SAP_BASIS)
together with SAP application components.
__________________________________________________________________________
____________________
In this section, the rule is created. You define a rule for mapping the field content for each
segment type.
Example
Definition of the rule E1MARRG for the segment type E1MARAM.
Activities
1. Perform the function.
2. Switch to change mode.
3. Enter a name for the rule, its meaning, and the IDoc for which the rule applies.
4. Save your entries.
28
29
1.3.2 Maintain Rules

In this section, you perform the second step for the rule. The rules are determined for each
field.
__________________________________________________________________________
____________________
Note: You can use this tool only if you are using the Web Application Server (SAP NetWeaver)
__________________________________________________________________________
____________________
You specify how the fields of a source object are converted and mapped to a target object.
This object could be a master record, a transaction data record, or an IDoc segment. The rule
maintenance functions are used for various purposes. For example, you might want to define
how records from a file are mapped to master data, or want to define derivation rules for
transaction data. In a derivation, any missing characteristic values are added to a transaction
data record. Another application is the definition of an IDoc segment mapping in which the
values of the fields of a segment are changed.
Different Options for Each Object
30
The options have different structural properties. For example, the validity of transaction data
depends on the master data. For this reason, when you maintain the rules for transaction
data, you have the option of testing the values against the master data. This option is not
required when you maintain rules for master data. This means that you see different options
depending on which object's rules you are maintaining.
Sender and Receiver Structure
You define how fields in the sender structure are mapped to fields in a receiver structure. The
receiver structure is a set of selected fields that defines an object in the SAP system. The
sender structure is the layout of records for the mapped data. It describes the structure of
the mapped data, byte by byte. Unlike the sender structure, the fields in a receiver structure
are derived from the object that you want to update. You either enter this object yourself
when you maintain the sender structure, or it is predefined for certain applications. This
means that some fields do not appear, such as the client, the last user to change the object,
the date of the last change, or the currency key. These fields are application-specific. You
assign a variable to the receiver field. This allows you to enter the field when the data is
transferred. For example, you can specify the company or company code for each file.
In this step, you define which fields in the sender structure are mapped to the fields of the
receiver structure, and how.
Prerequisites
You must define the sender structure before you define the mapping rules.
Initial Screen
On this screen, you assign the mapping rules to the sender structure. Enter the name of the
sender structure for which you want to define or modify the mapping rules. Choose Rules -
> Maintain to see the screen Maintain Rules for <Name of Sender Structure> .
Overview
The table is split into two logical parts.
The left part shows the fields of the receiver structure, is grayed out, and cannot be changed.
The receiver structure is determined from the data you specified when you defined the
sender structure.
The right part shows the fields of the sender structure, and other fields for the definition of
the rules.
31
If the sender structure of the data you want to map matches the receiver structure, then you
can generate an explicit MOVE rule (choose Rules -> Create Proposal for Rule). Any fields for
which no assignment could be generated are highlighted in color.
Otherwise, in the Sender Field column, you can enter the name of the sender field that you
want to assign to the receiver field.
You can specify that the receiver field only gets a value if the sender field has a value defined
by you. Enter the required information.
You can define more rules on a detail screen. To do this, select the line of the receiver field
for which you want to define special rules.
Detail Screen
The detail screen for defining mapping rules varies according to whether the field for which
you want to define a rule is filled with a characteristic or a key figure:
Characteristic fields are fields that have the role of characteristics, attributes, or classification
keys in the SAP system (company code, posting date, order number, for example). From a
technical perspective, these are fields with the data type C, N, D, or T, which are not usually
unit keys or currency keys, and which do not have a purely technical meaning (like, for
example, the client number).
Key figure fields are fields that have the role of key figures, values, or balances in the SAP
system (sales, revenue, headcount, for example). From a technical perspective, these are
usually fields with the data type P, which can be used for calculations.
Detail screen for maintaining rules for characteristics
You can use the following rules for characteristics:
1. Copy Sender Field

You assign the values of the sender field to the receiver field. However, you can only assign
those sender fields whose type is compatible with the type of the receiver field. For example,
you cannot assign a field with type C (any character string) to a field of type T (used to store
times). This prevents the field from containing invalid values. You can use the Restrict Value
Range function to specify that only those values specified by you in the sender field can be
copied to the receiver field. You can also specify conditions for other fields in the sender
structure, so that the fields are copied only if the data record contains certain values.
2. Set Constant
32
You assign a fixed value from the set of valid characteristic values to the receiver field. This
value is then used for each mapped data record.
1. Set Variable
You assign a variable (see Create Variable below) to the receiver field. This enables you to
enter the field when the data is mapped. For example, you can specify the company or
company code for each file that is to be read.
You can also assign a fixed value to the variable. In this case, the mapping works in the same
way as with a constant. The difference is that the constant fixed value can be used in other
locations in the system, with the variable name. In this way, you can improve the consistency
of data mappings.
2. Convert Sender Fields

You assign certain values of the sender field to a single value of the receiver field. To do this,
you specify the sender fields from the list that you want to include in the conversion.
You can specify an offset and length if you only want to use part of the sender field.
You can also specify a conversion routine. This is executed before the conversion in the sender
field value. You might need this conversion routine to fill fields with leading zeros.
Choose Conditions to display a screen where you specify which values the sender fields need
to have before they are converted to a specific value of the receiver field. In the left column,
specify the target values of the receiver field. In the following columns, specify the individual
values or intervals for the sender fields. To enable a receiver field to contain the specified
value, all sender fields must have the specified values. If you want to convert different sender
fields to the same value of the receiver field, then select the line and choose the pushbutton
on the right of the field. A symbol on the right of the field, or the color of the pushbutton
indicates that multiple conditions exist.
You can specify complex rules in multiple lines for a receiver field value. When the rules are
processed, the first suitable rule is used, however, the rules are not processed in a defined
order. You can also set the initial value explicitly for a receiver field value.
3. Use General Rule

You specify a previously defined general rule that you want to use in the data mapping. You
can define general rules by declaring the settings made with one of the previous options as a
general rule. To do this, enter a unique technical name and a description in the field Use Rule
Defined Here as General Rule. After you have saved this general rule, you can use it for other
mappings.
You might, for example, always want to assign the company code 0003 to the company code
0002 when you map data. To enable this, you have created a general rule that you can
reference for the Company Code characteristic. If you select this rule, the sender fields of the
general rule that need to be converted are displayed.
33
Remember that once you have referenced a general rule, you can no longer delete it. If you
still want to delete the rule, you can reassign the rule to the referencing rule.
Application-Specific Options
In some applications, you can decide what happens if a characteristic value does not contain
a value, despite the rules.
• Clear Field
The field contains the initial value.
• Classify as Error
The field is classified as an error. The mapping terminates.
• Set Constant
You assign a constant value from the set of valid characteristic values to the field.
• Copy Sender Field

You assign the value of a sender field specified by you to the field.
• EC-EIS only:
You have the option of specifying whether a receiver field value is checked, or whether
it needs to undergo a special (output) conversion routine. For more detailed
information on the conversion routines, see the F1 help.
Detail Screen for Rule Maintenance of Key Figures
On the detail screen, you specify how the key figure values are aggregated, how currencies
or units are translated, and how the key figure is mapped to the receiver key figure.
• EC-EIS Only:
You can specify whether the key figure is overwritten in the database or not. If you want to
overwrite the key figure in the database, then the value determined from the sender records
overwrites the value in the database. If you do not want to overwrite the key figure, then the
key figure is read from the database. It is used as the start value in the total operation.
Whether this option is required depends on the application. Enter one of the following total
operations:
o SUM
The total of the sender field values is mapped to the receiver record.
o MIN
The smallest mapped sender field value is entered in the receiver record.
34
o MAX
The largest mapped sender field value is entered in the receiver record.
o FIRST
The first mapped sender field value is entered in the receiver record.
o LAST
The last mapped sender field value is entered in the receiver record.
o COUNT
The number of mapped sender field values is entered in the receiver record.
This option usually only makes sense if combined with the
formula 1 (see Formulas below).
• Other Applications (Not EC-EIS):
Enter SUM as the total operation. The value of the sender field is mapped to the receiver
record (the other total operations in the EC-EIS component are not available, since data is not
compressed when it is mapped in other components).
You can use conditions to specify that a key figure is filled only if a sender field has certain
values. This function is required in the following example:
The sender structure contains the fields Balance Sheet Item and Balance. The receiver
structure contains the key figures ASSETS and LIABILITIES. You can now specify that the key
figure ASSETS is filled only if the field Balance Sheet Item contains the value 10000000.
Units and Currencies
Enter a unit in quantity fields, if no default exists.
You have the option of performing a unit conversion for quantity fields or a currency
translation for currency fields.
You can specify the exchange rate type, the exchange rate, and the currency for a translation
into a target currency. You can either specify fixed values for the currency and translation
date, or specify reference fields that contain the currency and date. You can also use a
variable for the translation type.
Note: The following applies to amount fields for users of the external data transfer tool, with
the exception of the CO-PA application:
The SAP system always saves currency amounts to the database with two decimal places.
Amounts of any currencies whose definition includes a number of decimal places other than
two need to be transformed to the SAP format.
35
SAP expects that currency amounts are provided with the usual amount of decimal places.
However, when currency amounts are saved to the database in SAP format, the Reference
Sender Field must be filled in the mapping rule for currency amounts (this also applies when
you map fields according to similar names, without explicit rules). This guarantees that the
amount is available in the SAP system with the correct number of decimal places for the
specified currency, after the conversion. If you import currency amounts from an SAP system
(data in binary format), then the database expects that the data is already in the correct
format.
Formulas
You define the formula in the Key Figure Formula Line field. The key figure formulas are
formed according to the ABAP rules that are valid for expressions. You can calculate with the
sender fields. For an overview of the valid sender fields, position the cursor on the input field
and choose F4. You can also use formula variables in the formula.
As with the mapping rules for characteristics, you can save the current rule as a general rule.
To do this, enter a name for the rule in the field Use as General Rule.
If you want to use a general rule for the mapping, then enter the name of a rule stored in the
system in the field General Rule. The sender fields that you want to convert are shown.
Creating Variables
You can create variables for characteristic values, formulas, and translation keys. These
variables can then be used in mapping rules. Variables for formulas and translation types can
be used globally. Variables for characteristic values can only be used for the object you are
processing. To create variables from the detail screen, choose Goto -> Variables -
> Translation Key or Goto -> Variables -> Formula Variables. On the next screen, choose Edit -
> Insert Line or use any empty line that exists. To define a variable, proceed as follows:
1. Enter the name of the variable in the Variable Name column. The first character of
the variable name must be a &, followed by a letter (the system inserts
the & automatically, if you forget it) The total length of the name cannot be greater
than 10 characters (including the &).
2. Select a replacement type. The replacement type specifies the way a variable is
replaced by a value. You can use replacement type 2 to specify the variables when you
start the data transfer (this is currently supported for the reading of files and for
aspect summarization only). If you select replacement type 5, you must also enter a
fixed value in the next column. To be able to use replacement type 3, you must
activate the function module EXIT_SAPFKCIM_003 in a user exit.
3. Enter a description of the variable.
36
4. Save your entries.
37
38
1.3.3 Assign Rule to Message Type

In this section, you perform the third step for the rule.
39
__________________________________________________________________________
____________________
Note: You can use this tool only if you are using the Web Application Server (SAP_BASIS)
__________________________________________________________________________
____________________
The rules are defined for a message type.
The rule is assigned to the segment type by sender system and receiver system.
Example
For the message type MATMAS, you assign the rule E1MARRG for the segment type
E1MARAM with a sender system and receiver system.
Prerequisites
The rules must have been created and maintained in the first two steps.
Activities
1. Perform the function. Enter the message type to which you want to assign a rule.
2. Enter the sender system and receiver system with the partner type.
3. Enter the segment type and the rule defined for it.
4. Repeat steps two and three for all other rules.
5. Save your assignments.
40
41
Result
42
43
44
There are two main ways to display an IDoc in SAP, depending on whether you know the
specific IDoc number or not:
45
1. Using Transaction WE02 (Display IDoc):

• This is the most common method for displaying a specific IDoc.
• Steps:
1. Open transaction WE02 in SAP.
2. Enter the IDoc number you want to display in the designated field.
3. Click Execute.
• The system will display the details of the IDoc, including:
o Header information: Basic details like IDoc number, creation date, status,
message type, and partner information.
o Segment data: The data itself is structured in a hierarchical tree format with
segments, data records, and status records. You can expand/collapse sections
to view specific details.
2. Using Transaction WE05 (List of Idocs):
• This method is useful if you don't know the specific IDoc number but want to search
for relevant ones based on selection criteria.
• Steps:
1. Open transaction WE05 in SAP.
2. Define your search criteria using various filters like:
▪ Date range
▪ IDoc type
▪ Status (e.g., waiting for processing, error)
▪ Partner information
▪ Message type
3. Click Execute.
• The system will display a list of IDocs matching your criteria. You can then double-click
on a specific IDoc number to view its details similar to WE02.
46
Additional Notes:
• You might require specific authorizations in your SAP profile to access and display
IDocs.
• The IDoc display provides functionalities to navigate through the data structure, view
segment details, and analyze processing statuses.
For further reference, you can explore the SAP Help Portal for detailed information on WE02
and WE05 transactions: https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/en-
US/4b/4c78b74a712597e10000000a42189b/content.htm
47
Before
48
After
49
1.3.4 Receiver exists , No filters , Fields converted , No version change

Message No. B1006
50
1.3.5 IDoc successfully processed in ALE outbox

The IDoc has passed through the ALE layer successfully and can be sent. It can either be sent
online or as a batch job, depending on the settings in the partner profile.
If there are no further status records then the IDoc waits for the next dispatch report run.
Success/failure of transmission is documented in subsequent status records.
1.3.6 ALE layer actions

The 'Receiver exists' parameter specifies whether the recipient of the IDoc has already been
entered by the calling application or by the ALE layer. In the latter case the settings of the
distribution model are used for the receiver determination.
The 'No filters' parameter specifies whether the processing in the ALE layer has led to
segments of the IDoc created by the application being left out. The settings in the segment
filter and in the distribution model for this recipient are decisive here.
The 'Fields converted' parameter specifies whether field values have been converted in the
ALE layer. This is the case if the IDoc contains organizational units to be converted or if the
ALE conversion tool has been activated for this recipient.
The 'No version change' parameter specifies whether the IDoc has been converted into an
earlier version of the IDoc type. This happens if the IDoc type in the outbound partner profile
for this recipient differs from the IDoc type which was created.
Status: Application document not posted (51)
VKORG, VTWEG, SPART cannot be determined for customer 0000002200 , supplier

0099991000
Message No. VG204
Diagnosis
No sales organization, distribution channel or division were sent to the IDOC. This data is
necessary if a sales order is to be added automatically. If this data is unavailable, you cannot
create a sales order document.
Procedure
51
If data on the sales organization, distribution channel and division have not been entered in
the IDOC, it must be determined using a user exit defined in the program.
Compare value segments E1EDKA1 AG and LF with table EDSDC
52
Condition EDI1 is missing in pricing procedure A V ZLDG01

Message No. V1206
53
Diagnosis
The condition issued is not in pricing procedure A V ZLDG01.
System Response
The system does not allow further processing of the document.
Procedure
Supply the missing entry in the pricing procedure or delete condition EDI1 from the
document.
If you do not have the authorization to do this yourself, contact your system administrator.
Check values table EDSDC with Define And Assign Pricing Procedures
54
55
Material CM-FL-V01 is not defined for sales org.1100 , distr.chan.10 , language DE

Message No. V1382
56
Diagnosis
Material CM-FL-V01 is not defined for the following combination of requirements:
Sales organization 1100
Distribution channel 10
Language DE
System Response
The system allows no further processing.
Procedure
You can check whether
the material number that you entered is correct
the material has been created for the sales organization and distribution channel
a short text with the appropriate language exists in the material master record (a short text
must be available in the language of either the customer or the sales organization)
The material must meet all three of the above requirements before you can process it further.
57
58
Sold-to party 10000004 not maintained for sales area 1100 10 00

Message No. VP197
Diagnosis
The sales and distribution master data for the customer 10000004 is not maintained in the
sales area 1100, 10, 00.
An order entry is therefore not possible.
Procedure
Create the customer master record in the sales area 1100, 10, 00.
Enter the following data:
Customer: 10000004
Sales organization: 1100
Distribution channel: 10
Division: 00
59
60
61
Result
62
63
64
65

GU SAP S4 HANA Configure EDI Partners Docx 1713327769

Uploaded by

Copyright:

Available Formats

GU SAP S4 HANA Configure EDI Partners Docx 1713327769

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GU SAP S4 HANA Configure EDI Partners Docx 1713327769

Uploaded by

Copyright:

Available Formats

Mickael QUESNOT © https://s4hclub.

SAP SPRO Electronic Data Interchange for Dummies

In this IMG activity, you configure EDI partners.

1.1.1 Convert External to Internal Partner Numbers

Mickaël QUESNOT © - Copyright

Partner Function External Number Internal Number

You then have to enter the following data:

Customer Partner Function External Partner Internal Number

Customer Partner Function External Partner Internal Number Address ID

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Internal key for identifying a Business Address Services address.

Mickaël QUESNOT © - Copyright

1.1.2 Assign Customer/Supplier to Sales Organization Data

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

1.1.3 Determine Partner Functions For EDI Outbound Processing

Mickaël QUESNOT © - Copyright

WE20: Partner Profile Configuration

Mickaël QUESNOT © - Copyright

For further learning, you can explore these resources:

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

EDI: Inbound partner profile does not exist

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

1.3 Converting Data Between Sender and Receiver IDocs in SAP

1. Conversion Rules (Transaction BD62):

Mickaël QUESNOT © - Copyright

o Search tables: Reference existing SAP tables to translate codes or perform

WE20 plays a crucial role in assigning conversion rules:

Mickaël QUESNOT © - Copyright

• Testing: Thoroughly test conversion rules to ensure accurate data transformation

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

1.3.1 Create Rule

To do this, you must perform the following steps in this order:

1. Create the rule: The rules are defined by segment.

Definition of the rule E1MARRG for the segment type E1MARAM.

Mickaël QUESNOT © - Copyright

Mickaël QUESNOT © - Copyright

1.3.2 Maintain Rules

Different Options for Each Object

Mickaël QUESNOT © - Copyright

Sender and Receiver Structure

The table is split into two logical parts.

Mickaël QUESNOT © - Copyright

Detail screen for maintaining rules for characteristics

You can use the following rules for characteristics: