Partner Profile Maintenance in IDOC Tutorials
Here we sapabapiq.com presenting a useful idoc tutorial on how to create partner profile in Idoc using Tcode WE20. This is the second post in the series of idoc tutorials for the functional consultants. Before going to read this post please read first post in the idoc tutorials.
What is IDOC - Basic Understanding and Terminology
Read second post in the series of IDOC tutorials for the SAP functional consultants.
IDOC PARTNER PROFILE MAINTENANCE
PARTNER PROFILE (WE20)
Partner
profile must be maintained for all the business partners to whom we want to
send or receive the IDocs. The TCODE for maintaining the partner profile is
WE20.
Double
clicking on the Partner will show the following screen:
Partner
profile contains parameters for Inbound and Outbound processing of IDocs. For
each message type we can maintain, inbound/outbound options, message control,
post processing options and contact information within Inbound and outbound
parameters.
OUTBOUND
OPTIONS (OUTBOUND PARAMETERS)
This
involves sender/receiver port, Output mode and relation to IDoc type i.e. Basic
Type and extension.
MESSAGE
CONTROL (OUTBOUND PARAMETERS)
This
contains application for which IDoc will be created e.g. EF for Purchase order,
the message type of the application that will trigger the IDoc and Process Code
that will convert SAP document to an IDoc.
For example, if PO is to be sent to
the Vendor AXXXXZ, then in the outbound option of the partner AXXXXZ we need to
maintain the message type ZXX1 and link it to the Process Code ME10. So when
message type ZXX1 is triggered in the PO then an IDoc will be created for the
partner vendor AXXXXZ.
Process Code is linked to the
Function Module in SAP that converts application data into an IDoc. Standard
function modules are provided by SAP for this conversion however these can also
be customized as per business needs.
Change Message Indicator indicates whether the IDoc is sent as a notification of change.
For example, Purchase Order change messages are sent to vendor using EDI
standard message type 860.
Separate
message type should be triggered in the purchase order for PO change.
Additional line with change message type must be added in the Message control
tab with change
message indicator on.
INBOUND
OPTIONS (INBOUND PARAMETERS)
For
inbound options process code is maintained in the Inbound screen only. IDoc
processing can be triggered by background program and triggered immediately.
POST PROCESSING (INBOUND/OUTBOUND PARAMETERS)
In
the post processing option we can maintain the workflow details of the users or
positions to which an error notification will be sent if an IDoc processing
fails.
TELEPHONY
(INBOUND/OUTBOUND PARAMETERS)
We
can also maintain the contact details in the telephony option.
EDI
STANDARD (OUTBOUND PARAMETERS)
EDI
standard screen contains the details of the Standard EDI terminology used for
the IDoc transmission.
For
example, Message Type 850 is
an EDI standard for Purchase Order IDoc and is linked to IDoc Message Type Orders.
Dear SAP'ers keep visiting www.sapabapiq.com for next posts in the series of IDOC tutorials for the functional consultants.
"You found the information helpful and want to say thanks? Your donation is enough to inspire us to do more. Thanks a bunch!"
Posted in: 
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.