2/4/2016 9:05:02 PM

Introduction to IDoc Overview in SAP FI

This blog is intended as an overview into IDoc implementation in FI-FIDCMT, FIROLL, FIDCCH, FIDCC1, FIDCC2, GLMAST, GLROLL, INVOIC, REMADV, PAYEXT,  DIRDEB, CREEXT, DEBADV, FINSTA, LOCKBOX, ACLREC, ACLPAY, ACLJOU, EXCHANGE_RATE, ACC_BILLING,  ACC_INVOICE_RECEIPT, ACC_GOODS_MOVEMENT.

An IDOC (Intermediate Document) is simply a container that is used to Exchange information between any two processes that can understand the syntax of the data. An IDoc consists of the following three types of records. 

1) One control record, this has all information i.e. number, sender and receiver message type, IDoc type 

2) One or many data records, this is where the application data is store 

3) One or many status records. Several SAP applications use the IDoc interface. Two very common terms that get used a lot with IDocs are EDI and ALE. EDI is the electronic exchange of documents via industry standard such as ANSI X.12 or EDIFACT. EDI allows communication between SAP and non SAP systems. ALE (Application link enabling) on the other hand enables the exchange of data between two SAP systems, but also has been known to be employed into legacy system integration.

The following is a list of the FI IDocs in SAP

Message Type Description(Message type) Basic type Description(Basic type) Release
CREADV Credit memo display PEXR2001 Payment/payment advice note/credit
memo/debit advice
30A
CREADV Credit memo display PEXR2002 Payment/payment advice note/credit
memo/debit advice
45A
CRESTA Copy credit status (DebtorCreditAccount) CRESTA01 Copy credit status (DebtorCreditAccount) 40A
DEBADV Debit display PEXR2001 Payment/payment advice note/credit
memo/debit advice
30A
DEBADV Debit display PEXR2002 Payment/payment advice note/credit
memo/debit advice
45A
DIRDEB Preauthorized withdrawal PEXFI03 FI-CA Payment Media 620
DIRDEB Preauthorized withdrawal PEXR2001 Payment/payment advice note/credit
memo/debit advice
30D
DIRDEB Preauthorized withdrawal PEXR2002 Payment/payment advice note/credit
memo/debit advice
45A
FIDCC1 Send entire FI documents (user exit 003/4) FIDCCP01 IDoc: Complete FI document 31I
FIDCC1 Send entire FI documents (user exit 003/4) FIDCCP02 FI IDoc: Complete FI Document 46C
FIDCC2 Send entire FI documents (user exit 005/6) FIDCCP01 IDoc: Complete FI document 31I
FIDCC2 Send entire FI documents (user exit 005/6) FIDCCP02 FI IDoc: Complete FI Document 46C
FIDCCH Change in FI document FIDCCH01 IDoc for FI document changes
(dunning block)
30A
FIDCMT Sending single items for FI-GL FIDCMT01 IDoc type for GLX rollups 30A
FINSTA Bank statement FINSTA01 IDoc for FI documents 40A
FIROLL General ledger rollup for FI-GL
(delta f. line items FIDCMT)
FIDCMT01 IDoc type for GLX rollups 30A
GLM000 Test reduction GLMAST GLMAST01 IDoc type for GLX rollups 30A
GLMAST Master data G/L accounts (master IDOC) GLMAST01 IDoc type for GLX rollups 30A
GLROLL FI-GLX message type rollup GLDCMT01 IDoc type for GLX rollups 30A
INVOIC Invoice/Billing Document /NFM/INVOIC02 INVOIC02 with NF Segment 470
INVOIC Invoice/Billing Document /SAPCEM/INVOIC CEM Invoice/Billing Document 40B
INVOIC Invoice/Billing Document INVOIC01 Invoice/Billing document 30A
INVOIC Invoice/Billing Document INVOIC02 Invoice/Billing document 40A
INVOIC Invoice/Billing Document INV_ID01 Invoice 21A
ISU_REMADV IS-U: Payment Advice Note PEXR2002 Payment/payment advice note/credit
memo/debit advice
46C
LCROLL Legal consolidation GLDCMT01 IDoc type for GLX rollups 30A
LOCKBX Lockbox FINSTA01 IDoc for FI documents 40A
PAYEXT Extended payment order PEXFI03 FI-CA Payment Media 620
PAYEXT Extended payment order PEXR2001 Payment/payment advice note/credit
memo/debit advice
30D
PAYEXT Extended payment order PEXR2002 Payment/payment advice note/credit
memo/debit advice
45A
PCROLL Profit center rollup GLDCMT01 IDoc type for GLX rollups 31G
RCLROL Reconciliation ledger rollup GLDCMT01 IDoc type for GLX rollups 30A
REMADV Payment advice PEXR2001 Payment/payment advice note/credit
memo/debit advice
30A
REMADV Payment advice PEXR2002 Payment/payment advice note/credit
memo/debit advice
45A


Common Customizing issues

When it comes to IDoc customizing it is impossible to be able to give exact steps to follow as the Customizing changes with message type and also with business scenario. There are however a few common things that are needed for it to work.

A)The partner profile needs to be established.

Transaction WE20

A large Corporation can have many partners so we need a way of maintaining and creating (other than entering them manually)

A partner profile has to be defined for every business partner with whom you exchange documents.  Partner profile is an important element in customizing the ALE/EDI interface. Program RSECHK07 is available to carry out the following checks on values specified in the partner profile

a) Process code

b) User to be notified and

c) Consistency of message control parameters with outbound parameters

General

Partner number, type and status. This data is stored in table EDPP1 EDI Partner general partner profiles - inb. and outb.). Partner Number could be the customer number Partner type is usally customer "KU", vendor "LI",   and Logical system "LS" the most widely used. Partner status can be active or inactive), if it is  inactive no documents can be passed to it.


Message Control View 

Maintained for Outbound messages i.e. Payment advice The process code points to a function module that reads the application data and formats the data into IDOC format. If you go to WE41. The test flag is important for certain FI messages  such as Remittance advice or payment advice, usually where verification is needed.

Outbound

These are stored in table EDP13

Inbound

These are stored in table EDP12

B) Creating the Communication Ports

Tranaction WE21

A port is used in an outbound system to define the medium in which documents are transferred to the destination system. ALE uses a tRFC (transnational remote functional call) which transfers the data in memory buffers. The RFC is a logical name used to define the characteristics of a communication link to a remote system. The EDI process uses file ports to transfer data to the subsystem. File could be viewed via AL11, its location can be found in WE21. An important point is that in EDI idoc data is is transferred using files whereas in ALE it is done via memory.

Some important Transaction Codes

Main Menus

WEDI    Mainatain menu for EDI related activities

BALE    Main menu for ALE related activities

SWLD    Main menu for Workflow related activities

SALE    Main menu for ALE configuration

NACE    Main menu for messge control


Idoc Definition

SE11    Data Dictionary

WE31    Segment editor

WE30    Idoc editor to create and extend Idoc type

BD53    Reduce Idoc types for master data

WE60    Idoc documenataion (structure and segment definition)

WE61    Idoc documenataion (control, data and status records)


Configuration

WE20    Maintain partner profile manually

WE21    Port definitions

BD82    Maintain partner profile automatically

SM59    RFC destination

BD64    Maintain customer model

BD71    Distibute customer model


Monitoring

WE02    Idoc display

WE05    Idoc list

WE07    Idoc statistics


Testing

WE19    Test tool for IDOC

WE12    Create an inbound into an outbound

WE16    Process an incoming Idoc file

WE17    Process an incoming status file


Reprocessing Idocs

BD87    Outbound

BD88    Inbound


If you like this blog, please share (Facebook/LinkedIn/Google+) to click below links so it will reach to others.


COMMENTS

  • Coycurrin -8/18/2016 5:30:52 PM

    Thanks for good information about SAP FICO Online Training. It was so nice article and useful to SAP learners.

  • Coycurrin -6/10/2016 2:39:15 PM

    Nice article, very helpful for us and thank's for sharing.