Basics for IDoc processing

::Initials/Basics for IDoc processing::
Message Type :: The message type defines the semantic context of an IDoc. The message type tells the processing routines, how the message has to be interpreted. The same IDoc data can be sent with different message types.

IDoc Type :: An IDoc type defines the syntax of the IDoc data. It tells which segments are found in an Idoc and what fields the segments are made of.

Processing Code :: The processing code is a logical name that determines the processing routine. This points usually to a function module, but the processing routine can also be a workflow or an event. The use of a logical processing code makes it easy to modify the processing routine for a series of partner profiles at once.

Partner profile :: Every sender-receiver relationship needs a profile defined. This one determines * The processing code * The processing times and conditions * In the case of outbound IDoc 1. The media port used to send the IDoc and 2. Triggers used to send the IDoc

Partner Type :: The IDoc partners are classified in logical groups. Such as : LS, KU, LI. LS - Logical Systems : It is meant to be a different computer and was primarily introduced for use with the ALE functionality. KU - Customer : The partner type customer is used in classical EDI transmission to designate a partner, that requires a service from your company or is in the role of a debtor with respect to your company, e.g. the payer, sold-to-party, ship-to-party. LI - Supplier : The partner type supplier is used in classical EDI transmission to designate a partner, that delivers a service to your company.

ALE comprises three layers:
• the applications services,
• the distribution services,
• the communications services

Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system

The functional configuration(Tcode: SALE)
• Create a Customer Distribution Model (CDM);
• Add appropriate message types and filters to the CDM;
• Generate outbound partner profiles;
• Distribute the CDM to the receiving systems; and
• Generate inbound partner profiles on each of the clients.

Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)

ProgramsRBDMIDOC – Creating IDoc Type from Change PointersRSEOUT00 – Process all selected IDocs (EDI)RBDAPP01 - Inbound Processing of IDocs Ready for TransferRSARFCEX - Execute Calls Not Yet ExecutedRBDMOIND - Status Conversion with Successful tRFC ExecutionRBDMANIN - Start error handling for non-posted IDocsRBDSTATE - Send Audit Confirmations

01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port okthen goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok

Good Luck :)