If you want to receive and send warranty claims via IDocs/EDI within the framework of message determination, you must maintain partner profiles for the partners with whom you wish to communicate via IDocs . In these partner profiles you define the general conditions for electronic data exchange with business partners via IDoc interfaces, i.e.: you define which messages are exchanged, how and in which direction.
Message determination (component: CA-GTF-BS) is a cross-application component that can be called by warranty claim processing functions using the IDoc interface (component: BC-SRV-EDI).
You can find further information in the standard documentation under Message Control (CA-GTF-BS) , IDoc Interface / Electronic Data Interchange (BC-SRV-EDI) and Defining Partners .
You have set up the logical systemand maintained the recipient ports.
You have created the master data for your warranty processing partners (claimant, reimburser).
Partners of partner type KU (customer; in Warranty Claim Processing: claimant )
Inbound parameters: partner function AS (claimant), message type WNTYRQ (Warranty Processing: claim request for IDocs for category
Versions from Claimant
)
Message type WNTYRQ: inbound options: process code WTYIC (Warranty Claim Processing: claim in category
Versions from Claimant
)
Outbound parameters: partner function AS (claimant), message type WNTYCF (Warranty Processing: claim confirmation for IDocs for category
Versions to Claimant
)
Message type WNTYCF:
outbound options:
IDoc basic type WRANTY02
(warranty claim),
message control:
application RW (Warranty Claim Processing), message type as defined in Customizing for output/message determination, process code WTYOC (Warranty Claim Processing: claim for category
Versions to Claimant
)
Note
IDoc basic type WRANTY02 is the direct successor of type WRANTY01 and differentiates itself from the latter in that it contains an additional segment for header conditions.
Partners of partner type LI (vendor; in Warranty Claim Processing: reimburser ):
Outbound parameters: partner function VN (vendor), message type WNTYRQ (Warranty Processing: claim request for IDocs for category
Versions to Reimburser
)
Message type WNTYRQ:
outbound options:
IDoc basic type
WRANTY02
(warranty claim),
message control:
application RW (Warranty Claim Processing), message type as defined in Customizing for output/message determination, process code WTYOV (Warranty Claim Processing: claim for category
Versions to Reimburser
)
Inbound parameters: partner function VN (vendor), message type WNTYCF (Warranty Processing: claim confirmation for IDocs for category
Versions from Reimburser
)
Message type WNTYCF: inbound options: process code WTYIV (Warranty Claim Processing: claim in category
Versions from Reimburser
)
Note
You can enter additional partner functions with partner numbers on header and version level in the warranty claim.
Use transaction code WE20 to create partner profiles.
Note
You can use transaction WE60 to display the structure and documentation for the IDoc basic type WRANTY02.