IDOC

1. SAP ECG to S4 HANA migration 
     What is the plan for S4 migration?

      

IDOC- Intermediate Document

The I doc structure consists of 3 parts:
===============================

1.  Control Record (Single Record)     - EDIDC table --idoc id,direction,sender id,receiver id,idoc type,logical message,date& time.

2.  Data Record (Multiple Records)    --EDIDD table --idoc-id,actual data,sequence/hierarchy.

    idoc segments

           ====header data

           -------item data
3. Status Record( Single Record)         - EDIDS table  ----status information,

           ----0---49  outbound 

                50--75  inbound

IDOC MONITORING:

----------------------------

    

1. WE02-- Idoc display
2. WE05-- Idoc lists
3.  WE06 ---Active idocs monitoring
4. WE09 ---idoc search

IDOC Testing

=================

1.    WE14 --Process IDOCs in Test mode
2.    WE19 -- Test modified inbound file 
3.    BD87  -- Reprocess idocs with same number 
4.    WE07 --- IDoc statics

What is handling unit ?

---- Handling units are simplify and optimized meterial flow and internal and external logistics process.

What are the communication protocals for inbound and outbound to SAP?

  Inbound Processing

  ====================   

        1.  ALE Based idoc

        2. BAPI  (Business Application Programming Interface) module to retrive and return 

             company information to SI.

       Sending an IDOC using ALE:

          ---------------------------------

                  1. SAP suite adaptor JCo 3.x 

SAP EDI step by step configuration with tcodes

Configuring SAP EDI involves several steps, from setting up communication partners to defining message types and configuring IDoc processing

1. Define Partner Profile (WE20):

   TCode: WE20

   Create partner profiles for your EDI communication partners (customers, vendors, etc.)

    Define inbound and outbound parameters, such as message types and port details.

2. Define Logical System (SALE):

   TCode: SALE

   Define logical systems for internal and external partners

   Assign client-specific logical system names and assign RFC destinations

3. Define Message Type (WE81):

   TCode: WE81

   Define message types for inbound and outbound communication

   Link message types to basic types and IDoc types

4. Assign Message Type to Partner (WE82):

   TCode: WE82

    Assign message types to partner profiles

    Define inbound and outbound message types for each partner

5. Define Ports (WE21):

    TCode: WE21

   Define ports for communication with external systems

    Assign communication method (e.g., File, RFC, HTTP) and specify additional parameters

6. Define Partner Function (WE19):

    TCode: WE19

    Define partner functions for inbound and outbound processing

    Assign partner functions to partner profiles

7. Create Distribution Model (BD64):

   TCode: BD64

   Create distribution models to define the flow of IDocs between logical systems

   Assign message types and logical systems to the distribution model

8. Define Change Pointers (BD61):

   TCode: BD61

   Define change pointers for master data and transactional data

   Activate change pointers for relevant message types

9. Configure Process Codes (WE41):

    TCode: WE41

    Define process codes for inbound and outbound processing

   Assign function modules to process codes for IDoc creation, posting, etc

10. Define Partner Agreement (WEA1):

    TCode: WEA1

     Define partner agreements to specify the exchange protocol, sender/receiver details, and additional settings

    Assign partner profiles and ports to partner agreements

11. Monitor IDoc Processing (WE02, WE05):

    TCodes: WE02, WE05

    Monitor inbound and outbound IDoc processing

    Check IDoc statuses, errors, and processing logs

12. Maintain Filters (BD64):

    TCode: BD64

    Define filters to control the distribution of IDocs based on message types, logical systems, etc

13. EDI Mapping (WE42):

     TCode: WE42

     Define EDI message mappings to convert external data formats (e.g., ANSI X12, EDIFACT) to internal IDoc format and vice versa

14. EDI Test (WE19):

    TCode: WE19

  Perform end-to-end testing of EDI scenarios with partner profiles and message types

Simulate inbound and outbound message processing to validate configurations

15. Activate Change Pointers (BD50):

    TCode: BD50

Activate change pointers for specific message types and IDocs

Ensure change pointers are active for relevant objects to trigger IDoc creation