Sunday, May 4, 2014

ALE Related Tables

  • BDAUDQUEUE  ALE Audit queue with not-processed Intermediate Documents
  • BDAUDSTATE   ; Statistical key figures for the ALE Audit
  • BDCP  Change pointer
  • BDCPS  Change pointer: Status
  • BDSER  Serialization: last date of object at sender
  • CIMHIS   EDI: Predecessors of Extension Types
  • CIMSYN   Table for Syntax Description of IDoc Type Extensions
  • EDADM   EDI client-specific system parameters
  • EDCIM   EDI: Value Table for Customer Extension Types
  • EDCIMT   EDI: Short Description of Extension Types
  • EDE1T  EDI: Text table for outbound process codes (TEDE1)
  • EDE2T  EDI: Text table for inbound process codes (TEDE2)
  • EDE5T  EDI: Text table for error processing process codes
  • EDE6T  IDOC: Text table for process codes for inbound statuses
  • EDFI2   EDI: Last processed document in file
  • EDFIL   EDI: Last processed document in file
  • EDI_MONIT WF  EDI: Structure for Default Values in EDI Monitoring
  • EDICONFIG CA  EDI: Parameter table for user-specific configuration
  • EDID2   Data segment (IDOC) from 3.0C
  • EDID3   Data segment table (EDI IDocs) from 3.0EDIDC    Control record (EDI Intermediate Document)
  • EDIDD  Data segment (EDI Intermediate Document)
  • EDIDO   Value table for IDoc types
  • EDIDOT  Short description of IDoc types
  • EDIDS   Status record (EDI IDoc)
  • EDIE5   Assign logical address to physical destination in SAP
  • EDIFCT   Assignment of FM to log. message and IDoc type
  • EDIFM   IDoc: Function modules for creating file names
  • EDIFMT   IDoc: Text table for EDIFM (funct. module for file names)
  • EDILOGADR   Assign logical address to physical destination (SAP)
  • EDIMAP     EDI: Assignment Table Between IDoc and Application Fields
  • EDIMSG   EDI: Message Types and Assignment to IDoc Types
  • EDIMSGT   Short description of SAP message types
  • EDIPHONE   CA-EDI: Telephony data for partner profiles
  • EDIPO    Table for description of ports for EDI
  • EDIPOI   Table for describing Internet ports
  • EDISEG   EDI: IDoc Type Segments with Assignment to Segment Type
  • EDISEGT   EDI: Short Description of Segments in EDSEA/EDISEG
  • EDISYN   Documentation Table for Generated Syntax of IDoc Types
  • EDIVAL   Reference From Check Table to Language-dependent Table
  • EDMAT EDI:  Texts for the 'Maturity Levels' in partner profile
  • EDMSG  Value table for SAP message types
  • EDP12 EDI PP:   Outbound Table 2 (Find Process Code)
  • EDP13 EDI PP:   Outbound Table 3 (Log. Message)
  • EDP21 EDI PP:   Inbound Table 1 (Find Code f. Process Type)
  • EDPI1 EDI:;   Partner profiles (inbound)
  • EDPO1 EDI  table for partner profiles (outbound), level 1
  • EDPP1 EDI PP:     List of EDI Partners (Inbound and Outbound)
  • EDSEA EDI:  Table of all segments of current release
  • EDSEG EDI:  Convert segments to 3.0
  • EDSVRS EDI:   Table of all segments of current release
  • EDSYN EDI:   Convert IDoc type syntax to 3.0
  • IDOCHIS EDI:   Predecessor of basic IDoc types
  • IDOCSYN CA-EDI: Syntax description for basis IDoc types
  • IDOCVRS EDI:  IDoc type versions created by customers
  • TBD00  customer models
  • TBD03  Communication relation between systems
  • TBD10    Def., out of which IDOC fields a filter object is to be read
  • TBD12   Mapping message type -> serialization and link type
  • TBD13   Organizational units to be converted in IDoc fields
  • TBD14   Message type -> object type
  • TBD20 ALE:  data for IDOC projection filter
  • TBD21 ALE:  IDOC reduction
  • TBD22 ALE:   mapping IDOC-fields to change document fields
  • TBD23 ALE:   definition of mandatory segments/fields
  • TBD30 ALE:  Conversion rules for IDOc segments
  • TBD50    Message-dependent attributes for IDOC input methods
  • TBD51   Attributes of IDOC input function modules
  • TBD52  Function modules for inbound ALE-EDI
  • TBD62  Assignment of change document field to message type
  • TBDA1     ALE active
  • TBDA2    ALE message active
  • TBDLI   Listings for a logical system
  • TBDLS  Logical system
  • TBDLST   Text for logical system
  • TBDLT  Lists for a logical system for ALE distribution
  • TBDME  ALE supplement data for EDI message type
  • TBDMS    Assignment of message type to IDoc type for ALE
  • TBDRCSTATE  Objects in Recovery environment (ALE)
  • TEDE1  EDI process types (outbound)
  • TEDE2  EDI process types (inbound)
  • TEDE3   Function module, which displays EDIDS record
  • TEDE5  EDI Process codes for error handling
  • TEDE6   IDOC process codes for inbound statuses
  • TEDEF   Assign proc. type to funct. module that processes proc. type
  • TEDS1   IDoc status values
  • TEDS2  Short description of IDoc status values
  • TEDS3  EDI status values: Importance/qualification
  • TEDST    SAP EDI Form routines to read master data
  • TEDTT  Partner Types - Language-dependent Names
  • TEDWL   Channel definition for transceiver
  • TEUDES   Configuration of upload files
  • TEUPL   Configuration of upload files
  • TEUPLT   Name of configuration IDoc for transceiver
  • TKANA   Entries for channel definitions
  • TKANAT  Descriptions for channel definitions

ALE SAP programs

         Name                   Description

  • MSEIDOC2  IDoc Statistics
  • MSEIDOC3  IDoc Lists
  • MSESTA00  Status Maintenance (Tables TEDS!, TEDS2, TEDS3) 
  • RBDAGAI2 Re-processing of intermediate docs after ALE input error
  • RBDAGAIE  Reprocessingof edited intermediate documents
  • RBDAGAIN   Re-processing incorrect intermediate docs. (outbound)
  • RBDAPP01   IDoc inbound processing ready for transfer
  • RBDAUD01  Statistical analyses for the ALE Audit
  • RBDAUD02  Reorganizing audit database - deleting table entries
  • RBDAUTHI  Include that contains all authorization checks
  • RBDAUTHO   Check authorizations
  • RBDCCMS1   IDocs for aRFC
  • RBDCHEC   Check IDOC Structure Against Database Tables
  • RBDCICO1 Monitoring Checkin/Checkout  ALE Customer Model
  • RBDCNST2   Constants for Consistency Check
  • RBDCPCLR   Delete Change Pointers
  • RBDCUS01   Direct Customer Model Maintenance
  • RBDCUS02   Transport of ALE Tables for a Message Type
  • RBDCUS03  Cross-System Comparison of Number Range Objects
  • RBDCUS04   Sending Model to Logical Systems
  • RBDCUS15   Generating the partner profiles
  • RBDCUS16   Data: Generating The Partner Protocols
  • RBDCUS17   Routines: Generating The Partner Protocols
  • RBDCUS19   ALE Consistency Checking
  • RBDCUS23   ALE Consistency Check: Transfer Between Two Systems
  • RBDCUS24  Parameters for Report RBDCUS23
  • RBDCUS25  Interface control for RBDCUS23
  • RBDCUS26  ALE Consistency Check Create PO from Sales Order
  • RBDCUS27  Data: Consistency Checking for SD Scenario
  • RBDCUS28  Routines: Consistency Checking for SD Scenario
  • RBDCUS31   Complete view of the message flow from view of one system.
  • RBDCUS33   Changing the Call Parameters for DA-OU
  • RBDCUS34   ALE Consistency Check
  • RBDCUS35   Modelling the control data distribution
  • RBDDATTR   Upload/Download Data from the OrgArchitect via Files
  • RBDEVACT   Activate Events for ALE/EDI
  • RBDFECLF    Fetch Classifications
  • RBDFECRE   Request Get Vendor Data
  • RBDIDOCA  Program for Object Type IDOC: EDI Intermediate Document
  • RBDIDOCR  IDOC Reduction
  • RBDINPUT    Processing of incoming intermediate docs.
  • RBDMANIN  Start Error Handling for Non-posted IDOCs
  • RBDMIDOC  Generate IDoc type from change pointers
  • RBDMMSD1  Consistency Check: Reassignment Between Two Systems
  • RBDMOIN1    IDoc list
  • RBDMOIN2  IDoc display
  • RBDMOIN3  IDoc overview
  • RBDMOIN4  Time Distribution of Intermediate Document Creation
  • RBDMOIN5  Statuses Reached
  • RBDMOIN6   Detailed Data on IDoc status
  • RBDMOIN7  Check: Customer model definitions <--> Partner profiles
  • RBDMOIN8  Cross-system IDOC Reporting
  • RBDMOIN9  Cross-system Analysis Whether IDOC Dispatch is Possible
  • RBDMOINB  Display: IDoc in sending system ==> IDoc in receiving system
  • RBDMOINC  Consistency check for input
  • RBDMOIND  Status Conversion for Successful RFC Execution
  • RBDMOINF  check for workflow for ALE/EDI inbound error processing
  • RBDMOINM   Model upload/download monitoring
  • RBDOUTPU  Processing outgoing intermediate documents
  • RBDPARPR   Conversion of process codes in existing partner protocols
  • RBDPRFTB  Value Tables for a Message Type
  • RBDPROSE  Converting ALE Settings for Productive Operation
  • RBDRCCLR  Reorganization of data in recovery objects
  • RBDRCLOG  Display application log of recovery process
  • RBDRCOBJ   ALE: Process recovery objects
  • RBDREO01   Reorganize Long-Term Links
  • RBDSALE   Message output, that SALE no longer exists
  • RBDSALE1  Call of ALE IMG
  • RBDSDMM1  Consistency Check: Create Purchase Order From Sales Order
  • RBDSECRE  Send creditor data
  • RBDSEDEB  Customers - send
  • RBDSTATE    Sending Confirmations For The ALE Audit
  • RBDSYNEI    Continue processing IDoc despite syntax error (inbound)
  • RBDSYNEO  Continue processing IDoc despite syntax error (outbound)
  • RBDSYNER   Process IDoc despite syntax error
  • RBDTABCO  Table Analyses
  • RBDTBD22  Mapping between change document and IDoc
  • RBDTBD23  Required IDoc fields
  • RBDTBDA1  Activate Change Pointer
  • RBDTRAN1    Generates transport requests for ALE control data distribution
  • RBDTRAN2   Monitoring transport of control data
  • RBDTRANS   Program for object type TRANSID: Transaction ID
  • RBDTXT01  Text elements for customizing checks in distributed contracts
  • RSEAUTPA  Central Routines for Auth. Check for 0EDS,0EDV,0EDY
  • RSEBASIS  INCLUDE for Alternative Structures and Access Routines
  • RSEBIDOC  Prog for Object Type IDOCBASIS: Basic Intermediate Document
  • RSEBSCHK   EDI: Check System Type (Basis or Application System)
  • RSECEDI1   EDI Constants/Exceptions
  • RSECHK01   Test IDoc Type Segments for Consistency
  • RSECHK02   IDoc Types: Consistency Check
  • RSECHK03   IDoc Type Consistency Test
  • RSECHK04   Break Down of IDoc Types into Segments
  • RSECHK05   Evaluate Occurrences of IDoc Type Segments
  • RSECHK07   Consistency Test for Partner Profiles
  • RSECODIN  IDoc: Display Program for Inbound Process Codes
  • RSECODOU   IDoc: Display Program for Outbound Process Codes
  • RSECODST   IDoc: Display Program for Status Process Codes
  • RSECODSY   IDoc: Display Program for System Process Codes
  • RSEIDC00     Program for object type IDOCSYIDOC : Meta-IDoc
  • RSEIDOC1  WF-EDI: Documentation record types
  • RSEIDOC2    IDoc list
  • RSEIDOC3  Documentation IDoc Record Types and IDoc Types (Parser)
  • RSEIDOC4   WF-EDI: Documentation Segments
  • RSEIDOC5   WF-EDI: Documentation Intermediate Document Type
  • RSEIDOC6   Documentation of IDoc Types (Overview)
  • RSEIDOC7   WF-EDI: Information System
  • RSEIDOCA   Main Program for Subprograms of the Program Group RSEIDOCx
  • RSEIDOCB   EDI Statistics - Extended Selection
  • RSEIDOCC  EDI Statistics - Error History
  • RSEIDOCD  IDoc Lists
  • RSEIDOCE   Detail Data on IDoc Status
  • RSEIDOCF   Time Distribution of IDoc Creation
  • RSEIDOCG nbsp;EDI: Convert current status in Intermediate Documents
  • RSEIDOCI    INCLUDE for List Formatting
  • RSEIDOCL   Global form routines for IDoc display
  • RSEIDOCM  CA-EDI: Active monitoring for IDoc processing
  • RSEINB00   Inbound Processing of Intermediate Documents (EDI)
  • RSEINB10  SAP-IDoc: Receiving IDocs from an R/2 System via CPI-C
  • RSEINB11   Transfer Inbound  IDocs from an R/2 System to the application
  • RSEINB50    Activate inbox and process IDocs with status '50'
  • RSEINBDT        EDI Inbound Processing (Global Data Declaration)
  • RSEINBEV  IDoc inbound: Customizing - Activate event-event receiver coupling
  • RSEINBF0   EDI Inbound Processing (FORM Routines)
  • RSEINBF1  EDI Inbound Processing (Other FORM Routines)
  • RSEINBT1  Include RSEINBT1
  • RSELINKD  Call display method for object
  • RSELOGAD  EDI: Selection of Maintenance Interface for EDILOGADR
  • RSEMASSA   EDI: Mass Activation of Partner Profiles
  • RSEOSTAT  Program for Object Type STATRECORD : Status Record
  • RSEOUT00  Process All Selected Intermediate Documents (EDI)
  • RSEPCON1  Print Control Record of an Intermediate Document
  • RSEPDAT1   Print a Data Record of an Intermediate Document
  • RSEPDATA   Print all Status Records of an Intermediate Document
  • RSEPORTA   IDoc: Tree display program for EDI and ALE ports
  • RSEPSEGA  Print List of all SAP Segments of an Intermediate Document
  • RSEPSTA1  Print a Status Record of an Intermediate Document
  • RSEPSTAA   Print all Status Records of an Intermediate Document
  • RSEREPSG  Repair IDoc Segments
  • RSESTA00   Inbound Processing of Status Records (EDI)
  • RSESTA02   Program for object type IDOCSTATUS : Status record
  • RSESTA11  Sending status records for inbound IDocs to R/2 System
  • RSESTADT  EDI Inbound Processing (Global Data Declaration)
  • RSESTAF0  EDI Inbound Processing (FORM Routines)
  • RSESTAF1   EDI Inbound Processing (Other FORM Routines)
  • RSESTAT1   Print a Status Record of an Intermediate Document
  • RSESTATA   Print all Status Records of an Intermediate Document
  • RSETESTP  Report for Test for Existence of Master Data
  • RSETEXT0  Program for Object Type IDOCTXTRAW: Text Message
  • RSEXARCA  Archiving Program for IDocs
  • RSEXARCB  IDoc archive prog for periodic implementation background
  • RSEXARCD  Delete Program for Archived IDocs
  • RSEXARCL nbsp;  Reload Program IDoc Archive
  • RSEXARCR   IDoc Archive Read Program
  • RSIDOCAM   Program for object type IDOCSTATIS : IDoc statistics
  • RSIDOCWF  Program for Object Type IDOC: EDI Intermediate Document
  • RSNASTED  Analysis of NAST Record for Output Type 6 (EDI)
  • SAPMSED0  WF-EDI: Maintain Partner Profiles
  • SAPMSED2  WF-EDI: Interface for Test Environment
  • SAPMSED3  EDI: IDoc - Segment Editor
  • SAPMSED5   EDI: Development of IDoc Types
  • SAPMSED7   IDoc: Test tool for IDoc inbound processing
  • SAPMSED8  IDoc documentation tools menu

Thursday, April 24, 2014

BDC

 Functional modules  in BDC
    BDC_OPEN_GROUP - Name of the client, sessions and user name given
    BDC_INSERT -Used to insert the data for one transaction into a session.  
    BDC_CLOSE_GROUP - Used to close the batch input session.

 Data input entered by user simulated in BDC by data packet.

 Data packet is an internal table has a structure of BDCDATA, it has fields:
            1. PROGRAM (program name)
            2. DYNPRO (screen number) 
            3. DYNBEGIN (New screen start) X=new screen
            4. FNAM (Field name)
            5. FVAL (Field value)


ABAP SD MM FICO TABLES




    BDC

    LSMW

    USER EXITS AND BADI