SAP CROSS APPLICATIONS

CROSS APPLICATIONS ARE USED TO DISTRIBUTE THE DATA AMONG THE SYSTEM.
ALE (APPLICATION LINK ENABLING) IS AN SAP TECHNOLOGY TO SUPPORT THE CROSS APPLICATIONS.
 ALE USES IDOC( INTERMEDIATE DOCUMENT ) TO SUPPORT THE CROSS APPLICATIONS.
IDOC IS THE CARRIER TO CARRY THE DATA FROM ONE SYSTEM TO AN OTHER SYSTEM.
SAP CAN UNDERSTAND ONLY THE IDOC FORMAT WHEN IT COMMUNICATION WITH OTHER SYSTEM.
IRRESPECTIVE OF THE RECEIVERS, THE ABAPER JOB IN SENDER SYSTEM IS ‘TO GENERATE THE IDOC’.
 THE PROCESS OF GENERATING IDOC IS NOTHING BUT ‘OUTBOUND PROCESS’
IRRESPECTIVE OF THE SENDERS, THE ABAPER JOB IN RECEIVER SYSTEM IS TO “COLLECT THE DATA” FROM
IDOC.
THE PROCESS OF COLLECT THE DATA FROM IDOC IS NOTHING BUT ‘INBOUND PROCESS’.
IN 1972 THERE IS NO IDOC CONCEPT.
RUNTIME COMPONENTS OF IDOC:-
1. IT GENERATES AN UNIQUE IDOC NUMBER WHICH IS 16DIGIT NUMBER
2. IT GENERATES 3 TYPES OF RECORDS
1. CONTROL RECORDS (EDIDC)
2. DATA RECORDS (EDIDD/4)
3. STATUS RECORDS (EDIDS)
1. CONTROL RECORDS :-
1. CONTROL RECORDS SPECIFY SENDER AS WELL AS RECEIVER INFORMATION
2. IT GENERATES ONLY ONE CONTROL RECORD
3. THIS INFORMATION WILL BE SAVED IN “EDIDC” TABLE
2. DATA RECORDS :-
1. DATA RECORD SPECIFY THE DATA WHICH IS SEND BY THE SENDER SYSTEM.
2. IT GENERATES ANY NO.OF DATA RECORDS
3. THIS INFORMATION WILL BE SAVED ON “EDIDD/EDID4” TABLE
3. STATUS RECORD :-
1. IT GENERATES THE STATUS CODES FOR EACH AND EVERY STAGE OF TRANSFERRING THE DATE
2. IT GENERATE ANY NO.OF STATUS RECORDS
3. THIS INFORMATION WILL BE SAVED ON “EDIDS” TABLE
STATUS CODES :-
THESE ARE 2 TYPES

OUTBOUND STATUS CODES INBOUND STATUS CODES

(0-49) (50-75)
NOTE :- THE LINKING BETWEEN ABOVE 3 TABLES ARE “IDOC NUMBER”
TYPES OF IDOC :- THESE ARE 2 TYPES
STANDARD
1. BASIC TYPE
CUSTOM
2. EXTENSION STANDARD + CUSTOM
I STANDARD IDOC :- IT WE WANT TO SEND AS WELL AS RECEIVES THE STANDARD DATABASE TABLES
INFORMATION THEN WE GO FOR STANDARD IDOC.
LFAI
KUNNR
NAME1

II CUSTOM IDOC :- IF WE WANT TO SEND AS WELL AS RECEIVES THE CUSTOM TABLE INFORMATION THEN
WE GO FOR CUSTOM IDOC.
2. EXTENDED IDOC :- IF WE WANT TO SEND AS WELL AS RECEIVES THE CUSTOM FIELDS INFORMATION OF
STANDARD DATA BASE TABLE ALONG WITH STANDANDARD FIELDS INFORMATION THEN WE GO FOR
EXTENDED IDOC.

NOTE :- IDOC IS THE COLLECTION OF SEGMENTS EACH SEGMENT IS COLLECTION OF FIELDS.

CHARACTERISTICS OF AN IDOC :-
1. NAME OF THE IDOC
2. LIST OF SEGMENTS IN THE IDOC
3. HIERARCHY (ORDER) OF THE SEGMENTS IN THE IDOC
4. OPTIONAL VS MANDATORY FOR THE SEGMENTS IN THE IDOC (IF IT IS MANDATORY AND FILL THE DATA
THE SEGMENT CAN BE TRANSFERRED TO RECEIVES SYSTEM)
5. PROVIDE PARENT AND CHILD RELATION SHIP BETWEEN SEGMENT
6. EACH SEGMENT CAN CARRY UPTO 1000 BYTES (LENGTH)
7. PROVIDE MINIMUM AND MAX NO.OF REPETITIONS FOR THE SEGMENT.
NOTE :-
‘WE30’ IS THE TRANSACTION CODE FOR TO CREATE AS WELL AS DISPLAY THE IDOC
‘WE31’ IS THE TRANSACTION CODE TO CREATE AS WELL AS DISPLAY THE SEGMENT
NOTE :-
THE NAME OF THE STANDARD SEGMENT STARTS WITH ‘E1’
THE NAME OF THE CUSTOM SEGMENT STARTS WITH ‘Z1’
THE DEFINITION NAME OF THE STANDARD SEGMENT STARTS WITH ‘E2’
THE DEFINITION NAME OF THE CUSTOM SEGMENT STARTS WITH ‘Z2’
NOTE :- IN THE REAL TIME THE COMMUNICATION SETTINGS ARE ESTABLISHED BY ‘BASIS PEOPLE’.
 COMMUNICATION BETWEEN ONE SYSTEM TO AN OTHER SYSTEM IS NOTHING BUT COMMUNICATION
B/W ONE CLIENT OF SENDER SYSTEM TO AN OTHER CLIENT OF RECEIVER SYSTEM.
 EACH PARTICIPATED SYSTEM IS CALLED ONE LOGICAL SYSTEM.
STEPS TO ESTABLISH THE COMMUNICATION SETTINGS :-
1. DEFINE THE LOGICAL SYSTEMS (SALE)
2. ASSIGN THE CLIENT TO LOGICAL SYSTEM (SCC4)
3. MAINTAIN RFC DESTINATION DETAILS (SM59)
 THE RECEIVER IS AVAILABLE IN THE FOLLOWING ADDRESS AND BE WANTS THE VENDOR DETAILS M2090
RECEIVER DETAILS SENDER DETAILS
CLIENT 810 CLIENT  800
USER  SAPUSER USER  SAPUSER
PASSWORD  INDIA123 PASSWORD  INDIA123
LOGIC SYSTEM  PT810 LOGIC SYSTEM  PT800

 BEFORE SENDING THE VENDOR DETAILS FIRST WE NEED TO ESTABLE THE COMMUNICATION SETTINGS
B/W FROM SENDER AND RECEIVER.
 STEPS TO ESTABLISH THE COMMUNICATION SETTINGS :-
1. STEPS TO DEFINE LOGICAL SYSTEMS (SALE) :-
 EXECUTE SALE
 EXPAND BASIC SETTINGS
 EXPAND LOGICAL SYSTEMS
 EXECUTE DEFINE LOGICAL SYSTEMS
 ENTER
 CLICK ON NEW ENTRIES IN THE APPLICATION TOOL BAR
 PROVIDE THE SENDER, RECEIVER LOGICAL SYSTEM NAMES & SHORT DESCRIPTIONS.
LOG.SYSTEM NAME
PT 800 SENDER LOGICAL SYSTEM
PT810 RECEIVER LOGICAL SYSTEM
 CLICK ON SAVE
 ENTER
2. STEPS TO ASSIGN THE CLIENT TO THE LOGICAL SYSTEM :-
EXECUTE SCC4
 CLICK ON CHANGE MODE (PENCIL SYMBOL)
 SELECT THE CLIENT 800
 CLICK ON DETAILS AFTER PENCIL SYSTEM
 PROVIDE LOGICAL SYSTEM NAME PT800
 CLICK ON SAVE
 ENTER
3. STEPS TO MAINTAIN RFC DESTINATION DETAILS (SM59) :-
EXECUTE SM59
 SELECT THE ABAP CONNECTIONS
CLICK ON CREATE
PROVIDE THE RFC DESTINATION PT810
 SELECT CONNECTION TYPE
 PROVIDE SHORT DESCRIPTION
DESCRIPTION / SENDER TO RECEIVER
CLICK ON LOGON & SECURITY TAB
PROVIDE THE RECEIVER LOGIN DETAILS
CLIENT 810
USER SAPUSER
PW STATUS IS INIT AL (DEFAULT)
PWD INDIA123
 CLICK ON SAVE
CLICK ON CONNECTION TEXT IN THE APPLICATION TOOL BAR (THERE IS NO ERRORS)
CLICK ON BACK
CLICK ON REMOTE LOG ON (810 CLIENT) IN THE APPLICATION TOOL BAR.
 BASED ON THE GIVEN INPUT ONE OUTBOUND PROGRAM WILL BE TRIGGERED AND FETCH THE
APPLICATION DATA (EG: VENDOR) FROM THE DATABASE AND GENERATE THE MASTER IDOC (NOT BUT
INTERNAL TABLE).
 MASTER IDOC IS NOTHING BUT DATA IN AN INTERNAL TABLE . MASTER IDOC WILL NOT SAVE ANY
WHERE IN THE SAP.
ALE SERVICE LAYER : READS THE DISTRIBUTION MODEL AND IDENTIFIES THE INTERESTED RECEIVERS. BASED
ON THE RECEIVERS IT GENERATE THE COMMUNICATION IDOC (EG : CIDOC1 , CIDOC2)
DISTRIBUTION MODEL : IS THE COLLECTION OF SENDERS , RECEIVERS , AND MESSAGE TYPE.
MESSAGE TYPE : IS USED TO IDENTIFY THE TYPE OF THE APPLICATION [VENDOR, CUSTOMER,MATERIAL….]
COMMUNICATION IDOC : IS THE PHYSICAL IDOC WHICH IS RECEIVERS SPECIFIC.
ALE COMMUNICATION LAYER : DISPATCH THESE COMMUNICATION IDOCS TO THEIR RELAVENT RECEIVERS
SYSTEM.
NOTE : IF WE GET THE ZERO MASTER IDOC THE REASON IS THE GIVEN INPUT HAVING NO DATA IN THE
DATA BASE.
IF WE GET THE ZERO COMMUNICATION IDOC’S THE REASONS ARE..
1. THERE IS NO INTERESTED RECEIVERS IN THE DISTRIBUTION MODEL
2. COMMUNICATION SETTINGS PROBLEMS .
SOME OF THE STANDARD MESSAGE TYPE :
TCODE MESSAGE TYPE IDOC TYPE SHORT DESCRIPTION
BD10 MATMAS MATMAS01 SEND MATERIAL
MATMAS02
MATMAS07
BD11 MATMAS “” GET MATERIAL
BD12 DEBMAS DEBMAS01 SEND CUSTOMER
DEBMAS 06
BD13 DEBMAS “” GET CUSTOMER
BD14 CREMAS CREMAS SEND VENDOR
CREMAS05
BD15 CREMAS “” GET VENDOR
NOTE : EDIMSG IS THE STANDARD DB TABLE WHICH CONTAINS ALL THE MESSAGE TYPES & IDOC TYPES.
STEPS TO IDENTIFY THE STANDARD TCODES BASED ON SHORT DESCRIPTION :
EXECUTE ‘SDMO’
PROVIDE SHORT DESCRIPTION (EG : SEARCH TEXT FOR  SEND VENDOR)
CLICK ON EXECUTE  IDENTIFY THE TRANSACTION CODES.
STEPS TO CREATE DISTRIBUTION MODEL :-
EXECUTE BD64
CLICK ON CHANGE MODE (PENCIL SYMBOL)
CLICK ON CREATE MODEL VIEW IN THE APPLICATION TOOL BAR
PROVIDE SHORT TEXT DISTRIBUTION MODEL
TECHNICAL NAME DBMVVENDOR
ENTER
SELECT THE DISTRIBUTION MODEL IN THE LAST
CLICK ON ADD MESSAGE TYPE IN THE APPLICATION TOOL BAR
ADD MESSAGE TYPE
SENDER PT800
RECEIVER PT810
MESSAGE TYPE CREMAS
ENTER
REPEAT THE SAME STEPS FOR ALL THE RECEIVERS.
PORT NUMBER : PORT NUMBER IS USED TO SPECIFY THE WAY OF TRANSFERRING THE DATA.
DIFFERENT TYPES OF PORTS ARE
1. TRFC PORT (TRANSACTIONAL RFC)  ALE/IDOC
2. FILE PORT  EDI/IDOC (OLD), LSMW
3. XML PORT  JAVA
4. INTERNET PORT  WEB APPLICATIONS.
STEPS TO CREATE PORT NUMBER :
EXECUTE WE21  SELECT THE TRANSACTIONAL RFC
 CLICK ON CREATE IN THE APPLICATION TOOL BAR
 CLICK ON ENTER  THEN AUTOMATICALLY GENERATE PORT NUMBER  PORT : A00000035
 PROVIDE RFC DESTINATION PT810
 CKICL ON SAVE.
STEP TO CREATE THE OUTBOUND PARTNER PROFILE : -
EXECUTE WE20
SELECT THE PARTNER TYPE LS (LOGICAL SYSTEM)
CLICK ON CREATE
PROVIDE PARTNER NO PT810
CLICK ON SAVE
CLICK ON CREATE OUTBOUND PARAMETER (+) SYMBOL
PROVIDE THE MESSAGE TYPE CREMAS PROVIDE THE PORT NUMBER A00000035
SELECT RADIO BUTTON TRANSFER IDOC IMMEDIATE
SELECT THE IDOC TYPE
BASIC TYPE CREMAS05
CLICK ON SAVE
SAVE
STEPS TO CREATE THE VENDOR :-
EXECUTE XK01
PROVIDE VENDOR NUMBER M2090

ACCOUNT GROUP 0004

ENTER
PROVIDE THE NAME
TITLE
NAME BIG BAZAR
SEARCH TERM BB
COUNTRY IN
CLICK ON SAVE

800 M2090 BIG BAZAR BB IN

STEPS TO SEND THE VENDOR DETAILS :
EXECUTE BD14
PROVIDE THE ACCOUNT NO OF VENDOR M2090
MESSAGE TYPE CREMAS
TARGET SYSTEM PT810
CLICK ON EXECUTE.
(1 MASTER IDOC, 1 COMMUNICATION IDOC GENERATED)
STEPS TO CHECK OR TEST THE IDOC
GO TO WE02 OR WE05
PROVIDE THE MESSAGE TYPE CREMAS
PROVIDE PARTNER NUMBET PT810
CLICK ON EXECUTE
NOTE : AFTER WE GET THE STATUS CODE 03 WE EXECUTE “RBDMOIND” STANDARD PROGRAM.
IF THE STATUS CODE 03 TURN TO 12 ( IDOC IS SUCCESSFULLY RECEIVED TO DESTINATION ).
IF THE STATUS CODE REMAINS 03 ( THEN THE IDOC IS IN THE TRFC QUEUE )
IF THE STATUS CODE 05 TURN TO 11 ( THEN THE IDOC IS DAMAGED IN THE TRFC QUEUE ).
NOTE : AT THE FIRST TIME, BEFORE PERFORMING THE INBOUND SETTINGS WEE MUST PERFORM THE
FOLLOWING THINGS IN RECEIVER SYSTEM.
1. DEFINE LOGICAL SYSTEM (THIS STEP IS NOT REQUIRED , IF WE ARE WORKING WITH THE SAME SERVER )
2. ASSIGN CLIENT TO LOGICAL SYSTEM.
NOTE : IN THE REAL TIME THE ABOVE 2 STEPS ARE DONE BY BASIS PEOPLE.
NOTE : PROCESS CODE IS USED TO IDENTIFY THE FUNCTION MODULE.
NOTE : OUTBOUND PROGRAM CAN BE DEVELOPED EITHED THROUGH EXECUTABLE PROGRAM OR
THROUGH FUNCTION MODULE WHERE AS INBOUND PROGRAM MUST BE DEVELOPED THROUGH
“FUNCTION MODULE” ONLY. BECAUSE .,THE INTERFACE PARAMETERS (IMPORT, EXPORT..) ARE SAME FOR
ANY MESSAGE TYPE.
1. STEPS TO ASSIGN CLIENT TO THE LOGICAL SYSTEM :-
 EXECUTE SCC4
 CLICK ON CHANGE MODE (PENCIL SYMBOL)
 SELECT THE CLIENT 810 PEERS TECH
 CLICK ON DETAILS (AFTER PENCIL)
 PROVIDE THE LOGIC SYSTEM NAME PT810
 ENTER
2. STEPS TO CREATE INBOUND PARTNER PROFILE :-
 EXECUTE WE20  SELECT THE PARTNER TYPE LS
 CLICK ON CREATE  PROVIDE THE PARTNER NUMBER TEAM800
 CLICK ON SAVE  CLICK ON CREATE INBOUND PARAMETER (+) SYMBOL.
 PROVIDE THE MESSAGE TYPE CREMAS
 SELECT THE PROCESS CODE CRE1  SELECT RADIO BUTTON TRIGGER IMMEDIATELY
 SAVE
STEP TO CHECK / TEST THE IDOC :-
EXECUTE WE02/WE05
PROVIDE THE MESSAGE TYPE CREMAS
PARTNER NO PT800
EXECUTE
NOTE : IF WE GET THE ERROR 56  PARTNER PROFILE IS NOT AVAILABLE
THEN WE MUST REPROCESS THE IDOC.
IDOC NO : 81001
STEPS TO REPROCESS THE IDOC :-
EXECUTE BD87
PROVIDE THE IDOC NUMBER 81001
EXECUTE
SELECT THE ERROR (RED COLOR)
IDOC WITH ERRORS ADDED
CLICK ON PROCESS IN THE APPLICATION TOOL BAR
OLD PROCESS NEW PROCESS STATUS
56 51 APPLICATION DOCUMENT NOT POSTED.
INBOUND PROCESS :-
AFTER IDOC IS REACHED TO RECEIVER SYSTEM THEN IT GOES TO INBOUND PARTNER PROFILE WE20 AND
CHECK THE MESSAGE TYPE.
IF THE MESSAGE TYPE IS AVAILABLE THEN IT GOES TO PROCESS CODE.
AGAINST THE PROCESS CODE IT TRIGGERS THE FUNCTION MODULE / INBOUND PROGRAM.
THE INBOUND PROGRAM COLLECT THE DATA FROM THE IDOC & PLACED INTO INTERNAL TABLE.
FROM THE INTERNAL TABLE THE DATA IS TRANSFERRED TO THEIR RESPECTIVE APPLICATION (VENDOR, CUS).
FROM THE APPLICATION THE DATA IS POSTED TO THEIR RELEVANT DATABASE TABLE .
NOTE :- IF THE MODE OF DISPATCH IS IMMEDIATE THEN WE MUST EXECUTE RSEOUT00 STANDARD
PROGRAM.
THEN ONLY THE COLLECTED IDOCS WILL BE DISPATCHED TO THEIR PARTICULAR RECEIVER SYSTEM.
NOTE : IF THE MODE OF POSTING IS TRIGGER BY BACKGROUND / COLLECT THEN WE MUST EXECUTE
RBDAPP01 STANDARD PROGRAM THEN ONLY THE COLLECTED IDOCS WILL BE POSTED TO THEIR
RELAVENT DB TABLES.
TYPES OF DISTRIBUITING THE DATA :-
1. SEND ENTIRE INFORMATION
2. SEND CHANGES ONLY (CHANGE POINTER TECHNIQUE)
3. GET ENTIRE INFORMATION (TWO WAY COMMUNICATION)
WHEN EVER CHANGE OCCURRED IN THE MASTER DATA THEN THE STANDARD SAP IT SELF PREPARE ONE
CHANGE DOCUMENT .
ALE SERVICE LAYER INVOKE THE SMD (SHARED MASTER DATA)
THE SMD READS THE DISTRIBUTION MODEL AND IDENTIFY THE INTRESTED RECEIVERS.
IF THE RECEIVER IS AVAILABLE THEN IT GENERATES CHANGE POINTERS FOR THE CHANGE DOCUMENT.
THE CHANGE POINTER TECHNIQUE READS THE CHANGE POINTERS AND GENERATE AS WELL AS DISPATCH
THE IDOC.
ALE CONFIGURATION STEPS FOR CHANGE POINTER TECHNIQUE :-
1. ALE CONFIGURATION SETTINGS FOR OUTBOUND
CREATE DISTRIBUTION MODEL (BD64) CREATE OUTBOUND PARTNER PROFILE (WE20)
2. ACTIVATE THE CHANGE POINTER TECHIQUE (BD61)
3. ACTIVATE THE MESSAGE TYPE (BD50)
4. GENERATE AS WELL AS DISPATCH THE CHANGED IDOC (BD21).
OBJECT :- CONFIGURE ALV TO SEND CHANGE OF VENDORS MASTER DATA FROM SENDER TO RECEIVER
SYSTEM.
STEPS TO ACTIVATE CHANGE POINTER TECHNIQUE : (FIRST WE DO CHANGES IN XK02 WITH SAME VENDOR)
EXECUTE BD61
SELECT THE CHECK BOX CHANGE POINTERS
ACTIVATED
CLICK ON SAVE
STEPS TO ACTIVATE MESSAGE TYPE :-
EXECUTE BD50
CLICK ON POSITION
PROVIDE MESSAGE TYPE
ENTER
SELECT THE CHECK BOX ACTIVATE (CREMAS)  SAVE.
STEPS TO CHANGE VENDORS :
EXECUTE XK02
PROVIDE THE VENDOR NUMBER
SELECT ADDRESS CHECK BOX
ENTER (CHANGE SOME FIELDS)
SAVE.
STEPS TO GENERATE AS WELL AS DISPATCH THE IDOC:-
EXECUTE BD21
PROVIDE MESSAGE TYPE
EXECUTE
STEPS TO CHECK / TEST IDOC:
EXECUTE WE05  PROVIDE MESSAGE TYPE CREMAS
PROVIDE PARTNER NUMBER PT810  EXECUTE
NOTE : CHANGE POINTER TECHNIQUE ALWAYS AT SENDER SYSTEM (800) .
SOME OF THE STANDARD REQUESTING MESSAGE TYPES :-
APPLICATION MESSAGE TYPE REQUESTING MESSAGE TYPE
1.VENDOR CREMAS CREFET
2.CUSTOMER DEBMAS DEBFET
3.MATERIAL MATMAS MATFET
NOTE : EDIMSG IS THE STANDARD DB TABLE, WHICH CONTAINS ALL MESSAGE TYPES AND REQUESSTING
MESSAGE TYPES.
NOTE : BEFORE PERFORMING GET ENTIRE INFORMATION WE NEED TO ESTABLISH “COMMUNICATION
SETTINGS ” FOR RECEIVER TO SENDER.
IN RECEIVER SYSTEM 810 CLIENT :-
1) DEFINE LOGICAL SYSTEM 2) ASSIGN LOGICAL SYSTEM FOR CLIENT
3) STEPS TO MAINTAIN RFC DESTINATION FROM RECEIVER TO SENDER
 EXECUTE SM59  ABAP CONNECTIONS  CREATE
 PROVIDE RFC DESTINATION (PT800)
 PROVIDE SHORT DESCRIPTION RECEIVER TO SENDER
 CLICK ON LOGON & SEARCH TAB  CLIENT : 800 , USER : SAPUSER , PW STATUS : INITIAL , PWD: IND
 PROVIDE LOGIN DETAILS OF RECEIVER  SAVE
 CLICK ON CONNECTION TEST  CLICK ON BACK
 CLICK ON REMOTE LOGIN IN APPLICATION TOOL BAR
OUTBOUND SETTINGS IN RECEIVER SYSTEM IN 810 CLIENT :-
STEP TO CREATE DISTRIBUTION MODEL :-
EXECUTE BD64 CLICK ON CHANGE MODE  CREATE MODEL VIEW
PROVIDE SHORT TEXT :
PROVIDE TECHNICAL NAME :
ENTER
SELECT DISTRIBUTION MODEL CREFET
CLICK ON ADD MESSAGE TYPE IN APPLICATION TOOL BAR
PROVIDE SENDER PT810
RECEIVER PT800
MESSAGE TYPE CREFET  ENTER  SAVE
STEPS TO CREATE PORT NUMBER :-
EXECUTE WE21  SELECT TRANSACTION RFC
CLICK ON CREATE - ENTER
PROVIDE SHORT DESCRIPTION & RFC DESTINATIONS PT800
SAVE
STEPS TO CREATE OUTBOUND PARTNER PROFILE :-
EXECUTE WE20 (IF THE PARTNER IS ALREADY AVAILABLE SELECT PORT NUMBER)
SELECT PARTNER PT800 CLICK ON CREATE OUTBOUND PARAMETER
PROVIDE MESSAGE TYPE : CREFET
PROVIDE PORT NUMBER : A00000017
SELECT TRANSFER IDOC : IMMEDIATE
SELECT BASIC TYPE (IDOC TYPE) : ALERQ01  SAVE
STEPS TO GET VENDOR :-
EXECUTE BD15
PROVIDE VENDOR NUMBER M2095
MESSAGE TYPE CREMAS
EXECUTE  ENTER
STEP TO CHECK / TEST IDOC :-
EXECUTE WE05
PROVIDE MESSAGE TYPE CREFET
PARTNER NUMBER PT800
EXECUTE
INBOUND SETTINGS IN SENDER SYSTEM (PT800) :-
STEPS TO CREATE INBOUND PARTNER PROFILE :-
EXECUTE WE20 SELECT PARTNER (PT810)
CLICK ON CREATE INBOUND PARAMETER
PROVIDE MESSAGE TYPE CREFET
SELECT PROCESS CODE CREF  SAVE
STEPS TO TEST IDOC :-
EXECUTE WE05
PROVIDE MESSAGE TYPE CREFET
PROVIDE PARTNER PT810
EXECUTE
NOTE :- IF WE GET ERROR “NO OBJECT REQUESTED IDOCS SELECTED FOR SENDING” THE REASON IS THE
REQUESTED DATA IS NOT AVAILABLE IN SENDER SYSTEM.
NOTE : WE ALREADY DONE THE 3RD & 4TH STEPS. WHEN EVER RECEIVER REQUEST THE DATA THROUGH BD15
THEN DATA AUTOMATICALLY RECEIVED FROM SENDER SYSTEM.
FILTERING TECHNIQUES : @SENDER SYSTEM ONLY.
FILTERING TECHNIQUES ARE USER TO SEND THE IDOC BASED ON THE CONDITIONS.
TYPES OF FILTERING TECHNIQUES :
1. IDOC FILTERING TECHNIQUES
2. SEGMENT FILTERING TECHNIQUES
3. REDUCED IDOC.
NOTE : FILTERING TECHNIQUES ARE ALWAYS @ SENDER SYSTEM.
IDOC FILTERING : IDOC FILTERING IS USED TO DROP THE IDOC AT RUNTIME.
 IDOC FILTERING CONDITIONS ARE PLACED IN DISTRIBUTION MODEL.
 BEFORE GENERATING THE COMMUNICATION IDOC ALE SERVICE LAYER READS THE DISTRIBUTION MODEL
AND IDENTIFY THE INTERESTED RECEIVERS.
IF THE RECEIVER IS AVAILABLE THEN IT CHECK THE GIVEN INPUT SATISFIES THE FILTERING CONDITIONS ARE
NOT . IF IT SATISFIES THEN ONLY IT GENERATE THE COMMUNICATION IDOC. OTHER WISE IT WON’T
GENERATE THE COMMUNICATION IDOC.
OBJECT :- CONFIGURE THE ALE TO SEND ONLY RAW MATERIAL INFORMATION TO THE RECEIVER SYSTEM.
IN THIS OBJECT WE USE THE IDOC FILTERING TO SEND ONLY RAW MATERIAL INFORMATION.
STEPS TO CREATE DISTRIBUTION MODEL :- @ SEND SYSTEM
EXECUTE BD64
CLICK ON CHANGE MODE  CLICK ON CREATE MODEL VIEW.
PROVIDE SHORT TEXT DISTRIBUTION MODEL FOR IDOC FILTERING
TECHNICAL NAME DBMIF
ENTER  SELECT THE DISTRIBUTION MODEL
CLICK ON ADD MESSAGE TYPE
PROVIDE THE SENDER PT800 , RECEIVER PY810 , MESSAGE TYPE MATMAS  ENTER
EXPAND THE –DISTRIBUTION MODEL
-- MATMAS
--NO FILTER SET --(DOUBLE CLICK ON IT)
 CLICK ON CREATE FILTER GROUP AT BOTTOM .
-- DATA FILTERING
EXPAND THE DATA FILTERING  EXPAND THE FILTER GROUP
DOUBLE CLICK ON MATERIAL TYPE CONDITION
CLICK ON INSERT ROW (+) BUTTON
SELECT THE VALUE ROH
ENTER
CLICK ON OK
SAVE THE DISTRIBUTION MODEL.
STEPS TO CREATE OUTBOUND PARTNER PROFILE :-
EXECUTE WE20
SELECT THE PARTNER PT810(LS)
CLICK ON CREATE OUT BOUND PARAMETERS (+)
PROVIDE THE MESSAGE TYPE MATMAS
PORT NUMBER A00000035
SELECT RADIO BUTTON TRANSFER IDOC IMMEDICATE
SELECT THE BASIC TYPE MATMAS05
CLICK ON SAVE.
STEP TO SEND THE MATERIAL :-
GO TO BD10
PROVIDE MATERIAL NO 100 – 110
MESSAGE TYPE MATMAS
LOGICAL SYSTEM PT810
EXECUTE
IF THE GIVEN INPUT SATISFIES THE FILTERING TECHNIQUE THEN ONLY IT GENERATE THE COMMUNICATION
IDOC.
SEGMENT FILTERING :-
SEGMENT FILTERING IS USED TO DROP THE SEGMENTS PERMANENTLY TO THE PARTICULAR RECEIVER SYSTEM.
THE TRANSACTION CODE FOR SEGMENT FILTERING IS BD56
WHEN EVER WE ARE WORKING WITH SEGMENT FILTERING THEN WE MUST CREATE DUMMY PARTNER
PROFILE FOR SENDER SYSTEM ITSELF.
STEPS TO CREATE DUMMY PARTNER PROFILE :-
EXECUTE WE20
SELECT THE PARTNER TYPE LS (UNDER PARTNER TYPE LS THERE IS NO PT800 ONLY PT810)
CLICK ON CREATE  PROVIDE THE PARTNER PT800
CLICK ON SAVE
OBJECT : CONFIGURE THE ALE TO DROP THE E1LFA1A SEGMENT INFORMATION TO THE RECEIVER SYSTEM
PT810 PERMANENTLY . IN THIS OBJECT WEE USE SEGMENT FILTERING TO DROP THE SEGMENTS
PERMANENTLY .
STEPS TO WORK WITH SEGMENT FILTERING : -
EXECUTE BD56
PROVIDE THE MESSAGE TYPE CREMAS  ENTER
CLICK ON NEW ENTRIES IN THE APPLICATION TOOL BAR
SELECT SENDER
SENDER TYPE SENDER RECEIVER TYPE RECEIVER SEGMENT TYPE
LS PT800 LS PT810 E1LFA1A
REPEAT THE SAME STEPS FOR ALL OTHER SEGMENTS
SAVE
STEPS TO SEND THE VENDOR DETAILS :-
EXECUTE BD14
VENDOR NO M2097
MESSAGE TYPE CREMAS
TARGET SYSTEM PT810
EXECUTE. (1 MASTER IDOC, I COMM IDOC )
GO TO WE05
 NOW IT WILL DROP THE E1LFA1 SEGMENT INFORMATION.
3 REDUCED IDOC :-
REDUCED IDOC IS USED TO DROP THE SEGMENTS AS WELL AS FIELDS INFORMATION PERMINANTELY TO
THE PARTICULAR RECEIVER SYSTEM.
 THE TRANSACTION CODE FOR REDUCED IDOC IS BD53.
NOTE : WE CAN’T DROP THE MANDATARY SEGMENTS AS WELL AS MANDATARY FIELDS WHICH ARE IN LIGHT
GREEN COLOR.
IN THE REDUCED IDOC WEE CREATE A NEW MESSAGE TYPE BASED ON THE EXISTING MESSAGE TYPE.
BASED ON THE NEW MESSAGE TYPE WE CONFIGURE THE ALE . (CREATE DISTRIBUTION MODEL , CREATE
OUTBOUND PARTNER PROFILE)
STEPS TO WORK WITH REDUCED IDOC :-
EXECUTE BD53  PROVIDE NEW MESSAGE TYPE ZPTCM  CLICK ON CREATE
PROVIDE THE EXISTING MESSAGE TYPE REFERENCE CREMAS  ENTER
PROVIDE SHORT DESCRIPTION NEW MESSAGE  ENTER
SELECT THE OUR REQUIRED SEGMENT E1LFA1B
CLICK ON SELECT IN THE APPLICATION TOOL BAR
DOUBLE CLICK ON SEGMENT E1LFA1B
SELECT THE REQUIRED FIELDS
-- SELECT THE CHECK BOXES LIKE : REN DATE
ENTER  REPEAT THE SAME STEPS FOR ALL OTHER SEGMENTS.
CLICK ON SAVE.
BASED ON THIS NEW MESSAGE TYPE (ZPTCM) WE CREATE THE DISTRIBUTION MODEL AND OUTBOUND
PARTNER PROFILE.
 DIFF B/W SEGMENT FILTERING AND REDUCED IDOC :-
SEGMENT FILTERING REDUCED IDOC
SEGMENT FILTERING IS USED TO DROP THE REDUCED IDOC IS USED TO DROP THE SEGMENTS
SEGMENTS PERMANENTLY . AND FIELDS PERMANENTLY .
THE T CODE FOR SEGMENT FILTERING IS BD56 THE T CODE BD53
IN THE SEGMENT FILTERING THE SELECTED IN THIS THE SELECTED SEGMENTS AND FIELDS
SEGMENTS INFORMATION ONLY DROPPED. INFORMATION ONLY SEND TO RECEIVER SYSTEM.
IN THIS WE NO NEED TO CONFIGURE THE ALE IN THIS BASED ON THE NEW MESSAGE TYPE WE
ONCE AGAIN. CONFIGURE THE ALE.
CUSTOM IDOC : CUSTOM IDOC IS USED TO SEND AS WELL AS RECEIVES THE CUSTOM TABLE INFORMATION
SOME OF THE REAL TIME SCENARIO’S RELATED TO CUSTOM IDOC :-
SCENARIO -1 :-
AGAINST VENDOR SUPPLIES THE WARE HOUSE DEPORTMENT CREATE THE GOODS RECEIPT WITH MIGO
TRANSACTION WITH 101 MOMENT TYPE.
AGAINST GOODS RECEIPT THE PLANT FINANCE PEOPLE PHYSICALLY VERIFY THE STOCK AND PREPARES
THE INVOICE RECEIPT.
AGAINST INVOICE RECEIPT THE ACCOUNT PAYABLE DEPORTMENT PAY THE AMOUNT TO THE VENDOR
WITH DEDUCTION OF TDS AMOUNT.
AFTER FEW DAYS THE VENDOR ASKS THE FORM 16A TO THE TAXATION DEPORTMENT / FINANCE
DEPORTMENT.
WHEN EVER THE FINANCE DEPORTMENT GENERATE THE FORM 16 THEN THEY NEED TO ENTER THE LR NO,
LORRY RECEIPT , VEHICLE NO , TRANSPORTER NAME. THESE INFORMATION IS NOT CAPTURED IN THE
ENTIRE MM LIFE CYCLE.
HERE WE IMPLEMENT A BADI TO ATTACH ONE ADDITIONAL SCREE TO THE MIGO TRANSACTION WHICH
CONTAINS ABOVE FIELDS.
WHEN EVER THE WARE HOUSE PEOPLE CREATE THE GR THEN THEY FILLL THE ADDITION SCREEN
INFORMATION ASLO. THESE INFORMATION IS STORED IN SEPARATE Z- TABLE.
IF WE WANT TO SEND AS WELL AS RECEIVE THIS Z- TABLE INFORMATION THEN WE GO FOR CUSTOM
IDOC.
SCENARIO -2 :- IN THE REAL TIME COMPANY PROVIDE THE TRAININGS
TO THE EMPLOYESS IN VARIOUES MODULES AND MAINTAIN THOSE
INFORMATION IN A SEPARATE Z- TABLE.
IF WE WANT TO SEND AS WELL AS RECEIVE THIS Z – TABLE
INFORMATION THEN WE GO FOR CUSTOM IDOC.
SCENARIO -3 :- EACH MATERIAL HAVING THEIR OWN CHARACTERISTICS DETAILS THOSE ARE MAINTAIN
IN A SEPARATE Z TABLE.
IF WE WANT TO SEND AS WELL AS RECEIVE THIS Z-TABLE INFORMATION THEN WE GO FOR CUSTOM
IDOC.
OBJECT : CONFIGURE THE ALE TO SEND AS WELL AS RECEIVES THE
GR ADDITIONAL INFORMATION FRIM Z TABLE AS SHOWN BELOW.
ALE CONFIGURATION STEPS FOR CUSTOM IDOC OUTBOUND :
1. CREATE THE SEGMENTS (WE31)
2. CRE ATE THE IDOC (WE30)
3. CREATE THE MESSAGE TYPE (WE81)
4. LINK THE MESSAGE TYPE TO IDOC TYPE (WE82)
5. CREATE THE PORT NUMBER (WE21)
6. CREATE THE OUTBOUND PARTNER PROFILE (WE20)
7. DISTRIBUTION MODEL IS NOT REQUIRED , IF WE PASS CONTROL RECORDS INFORMATION IN THE
PROGRAM (SENDER + RECEIVER + MESSAGE TYPE)
NOTE : BEFORE PERFORMING THE OUTBOUND SETTINGS FIRST WEE NEED TO CREATE THE DATABASE TABLE.
NOTE : BEFORE PERFORMING THE OUTBOUND SETTINGS
FIRST WEE NEED TO CREATE THE DATABASE TABLE.
OUTBOUND SETTINGS :-
1. STEPS TO CREATE SEGMENT :-
 EXECUTE WE31  PROVIDE THE SEGMENT TYPE Z17GRS1
 CLICK ON CREATE  PROVIDE SHORT DESCRIPTION GR ADDITIONAL DATA SEGMENT
 PROVIDE FIELD NAME AS WELL AS DATA ELEMENT
FIELD NAME DATA ELEMENT
GRNO MBLNR
GRYEAR MJAHR
LRNO ZS7LRNO
VNO ZS7VNO
TNAME NAME1
 CLICK ON SAVE  ENTER
 GO BACK AND GOTO EIDT UNDER SET RELESE
 REPEAT THE STEPS FOR ALL OTHER SEGMENTS.
NOTE : WHEN EVER WE CREATE THE SEGMENT THEN IT AUTOMATICALLY CREATE ONE EQUALENT STRUCTURE
IN THE DATA DICTIONARY AND ALSO IT CREATE A SEGMENT DEFINITION.
SEGMENT DEFINATION : IT IS USEFUL IN WHEN WE COMMUNICATE WITH NON SAP SYSTEM. THE MIDDLE
WARE CONVERTERS , BASED ON THE SEGMENT DEFINITION ONLY THEY TRANSLATE THE SENDERS FORMAT
TO RECEIVERS UNDERSTANDABLE FORMAT.
2. STEP TO CREATE IDOC :-
EXECUTE WE30 PROVIDE THE OBJ. NAME AS IDOC NAME Z7GRI
CLICK ON CREATE  PROVIDE SHORT DESCRIPTION GR ADDITIONAL DATA
IDOC ENTER
SELECT THE IDOC NAME
Z7GRI GR ADDITIONAL DATA IDOC
CLICK ON CREATE SEGMENT  PROVIDE THE SEGMENT NAME/ TYPE Z17GRS1
IF SEGMENT IS MANDATORY MANDATORY SEG
PROVIDE THE MINIMUM NUMBER 1
MAXIMUM NO.OF REPETATIONS 99
ENTER
REPEAT THE SAME STEPS FOR ALL OTHER SEGMENTS
CLICK ON SAVE
3. STEPS TO CREATE MESSAGE TYPE :-
EXECUTE WE81  CLICK ON CHANGE MODE  ENTER
CLICK ON NEW ENTRIES IN THE APPLICATION TOOL BAR
PROVIDE THE MESSAGE TYPE , SHORT TEXT
MESSAGE TYPE SHORT TEXT
GRIMAS GR MESSAGE TYPE
 SAVE  ENTER.
4. STEPS TO LINK THE MESSAGE TYPE TO IDOC TYPE :-
EXECUTE WE82  CLICK ON CHANGE MODE  ENTER CLICKON NEW ENTRIES
PROVIDE THE MESSAGE TYPE
MESSAGE TYPE BASIC TYPE RELEASE
GRIMAS Z7GRI 700
SAVE  ENTER.
STEP TO IDENTIFY THE RELEASE :
EXECUTE SE11  SELECT THE RADIO BUTTON DB TABLE EDIMSG(PROVIDE THE TABLE NAME)
DISPLAY  CLICK ON CONTENTS  EXECUTE
SELECT THE RELEASE FIELD
CLICK ON SORT DESCRIPTION AND IDENTIFY THE LATEST RELEASE.
5. STEP TO CREATE PORT NUMBER :-
EXECUTE WE21  SELECT THE TRANSACTION RFC
CLICK ON CREATE  SELECT THE RADIO BUTTON OWN PORT NAME
PROVIDE THE PORT NAME GRIPORT
ENTER PROVIDE SHORT DESCRIPTIION PORT NUMBER
PROVIDE RFC DESTINATION PT810  SAVE  ENTER.
6. STEPS TO CREATE OUTBOUND PARTNER PROFILE :-
EXECUTE WE20  SELECT THE PARTNER PT810
CLICK ON CREATE OUTBOUND PARAMETER
PROVIDE THE MESSAGE TYPE GRIMAS  PROVIDE THE PORT NO GRIPORT
SELECT RADIO BUTTON TRANSFER IDOC IMMEDIATE
SELECT THE BASIC TYPE Z7GRI
SAVE
STEPS TO DEVELOP CUSTOM IDOC OUTBOUND PROGRAM:-
1. DESIGN THE SCREEN AS SHOWN IN THE BELOW.
2. GENERATE THE MASTER IDOC (BASED ON THE GIVEN I/P, WE WILL FETCH THE DATA FORM DB AND
PLACED INTO A INTERNAL TABLE)
3. COLLECT THE CONTROL RECORD INFORMATION (SENDER, RECEIVER, MESSAGE TYPE….)
4. FOR EACH RECEIVER (PT810, PT811) IN THE CONTROL RECORD INTERNAL TABLE, WE GENERATE AS WELL
AS DISPATCH THE COMMUNICATION IDOC.
STEPS TO IDENTIFY THE FIELD NAME , OR DATA ELEMENT OF MESSAGE TYPE AND LOGICAL SYSTEM:-
EXECUTE BD14 OR ANY TCODE
PLACE THE CURSOR ON MESSAGE TYPE  CLICK ON ‘F1’
CLICK ON TECHNICAL INFORMATION  IDENTIFY THE DATA ELEMENT EDI_MESTYP (FOR MESSAGE TYPE)
PLACE THE CURSOR ON TARGET / LOGICAL SYSTEM I/P FIELD
CLICK ON F1  CLICK ON TECHNICAL INFORMATION.
IDENTIFY THE DATA ELEMENT LOGSYS.
TABLES ZS7GRAI.
SELECTION-SCREEN BEGIN OF BLOCK A WITH FRAME.
SELECTION-OPTIONS S_GRNO FOR ZS7GRAI-GRNO.
PARAMETER : P_MESTYP TYPE EDI_MESTYP OBLIGATORY,
P_LOGSYS TYPE LOGSYS.
SELECTION-SCREEN END OF BLOCK A
2. GENERATE THE MASTER IDOC :- . GENERATE THE MASTER IDOC IS NOTING BUT FILL AN INTERNAL TABLE
WHICH CONTAINS 2 FIELDS (SEGNAM , SDATA)
INTERNAL TABLE
SEGMENT NAME (SEGNAM)
SEGMENT DATA (SDATA)
NOTE : IN IDOC , WE HAVE ONE STRUCTURE / TABLE I.E, “EDIDD”, WHICH CONTAINS ABOVE TWO FIELDS .
SO WE SIMPLY DECLARE OUR INTERNAL TABLE BY REFERING “EDIDD” STRUCTURE / TABLE.
 WHEN EVER WE ARE WORKING WITH CUSTOM IDOC THEN WE MUST DECLARE “3 INTERNAL TABLES”
ONE IS FOR DATA, ONE IS FOR CONTROL RECORDS INFORMATION ,ONE IS FOR COMMUNICATION . AND
ALSO NEED TO DECLARE ONE WORKAREA AND INTERNAL TABLE FOR EACH SEGMENT IN THE IDOC .
[IF WE ARE WORKING WITH SEGMENTS LIKE SEG1,SEG2…SEG10 WE DELARE 10 SEGMENT INTERNAL
TABLES]
PROCEDURE TO FILL MASTER IDOC:-
BASED ON THE GIVEN INPUT WE WILL FETCH THE DATA FROM THE DATABASE AND FILL THE SEGMENT INTERNAL
TABLES.
LOOP THE EACH SEGMENT INTERNAL TABLE DATA AND FILL THE MASTER IDOC.
DATA : WA_DATA LIKE EDIDD, (FOR DATA)
IT_DATA LIKE TABLE OF WA_DATA.
DATA : WA_SEG1 LIKE Z17GRS1, (FOR SEG)
IT_SEG LIKE TABLE OF WA_SEG1.
SELECT GRNO GRYEAR LRNO VNO TNAME FROM ZS7GRAI INTO TABLE IT_SEG1 WHERE GRNO IN S_GRNO.
LOOP AT IT_SEG1 INTO WA_SEG1.
WA_DATA-SEGNAM = ‘Z17GRS1’.
WA_DATA-SDATA = WA_SEG1.
APPEND WA_DATA TO IT_DATA.
CLEAR WA_DATA.
ENDLOOP.
[IF WE HAVE AN OTHER SEGMENT SEG2 … SEG10]
LOOP AT IT_SEG2 INTO WA_SEG2.
WA_DATA-SEGNAM = ‘Z17GRS1’.
WA_DATA-SDATA = WA_SEG2.
APPEND WA_DATA TO IT_DATA.
CLEAR WA_DATA.
ENDLOOP.
3. COLLECT THE CONTROL RECORD INFORMATION :-
COLLECT THE CONTROL RECORD INFORMATION IS NOTHING BUT FILL AN INTERNAL TABLE WHICH
CONTAINS THE FOLLOWING FIELDS.
1. SNDPRT  SENDER PARTNER TYPE
2. SNDPRN  SENDER PARTNER NUMBER
3. RCVPRT  RECEIVER PARTNER TYPE
4. RCVPRN  RECEIVER PARTNER NUMBER
5. RCVPOR  RECEIVER PORT NUMBER
6. MESTYP  MESSAGE TYPE
7. DOC TYPE  IDOC TYPE
NOTE : IN THE DDIC, WE HAVE ONE STRUCTURE / TABLE, I.E , “EDIDC” WHICH CONTAINS ABOVE FIELDS SO
WE SIMPLY DECLARE OUR INTERNAL TABLE BY REFERING “EDIDC” STRUCTURE / TABLE.
DATA : WA_CONT LIKE EDIDC, (FOR CONTROL RECORD)
IT_CONT LIKE TABLE OF WA_CONT.
*FILL THE CONTROL RECORD INFORMATION
WA_CONT-SNDPRT = ‘LS’.
WA_CONT-SNDPRN = ‘PT800’.
WA_CONT-RCVPRT = ‘LS’.
WA_CONT-RCVPRN = ‘PT810’.
WA_CONT-RCVPOR = ‘GRIPORT’.
WA_CONT-MESTYP = ‘GRIMAS’.
WA_CONT-DOCTYP = ‘Z7GRI’.
APPEND WA_CONT TO IT_CONT.
REPEAT THE SAME STEP FOR EACH RECEIVER (LIKE PT811…)
4. FOR EACH RECEIVER IN THE CONTROL RECORD INTERNAL TABLE WE GENERATE AS WELL AS DISPATCH THE
COMMUNICATION IDOC :-
“MASTER_IDOC_DISTRIBUTE” IS THE FM WHICH IS USED TO GENERATE AS WELL AS DISPATCH THE
COMMUNICATION IDOC TO THEIR PARTICULAR RECEIVER SYSTEM.
THE INPUT FOR THE ABOVE F.M IS
1. <CONTROL RECORD WORKAREA >
2. <DATA INTERNAL TABLE / MASTER IDOC>
THE OUTPUT FOR THE ABOVE F.M IS,
1. <COMMUNICATION IDOC INTERNAL TABLE>.
*DECLARE THE COMMUNICATION IDOC IT
DATA : WA_COMM LIKE EDIDC,
IT_COMM LIKE TABLE OF WA_COMM.
*GENERATE AS WELL AS DISPATCH COMMUNICATION IDOC FOR EACH RECEIVER
LOOP AT IT_CONT INTO WA_CONT.
CALL FUNCTION ‘MASTER_IDOC_DISTRIBUTE’
EXPORTING
MASTER_IDOC_CONTROL = WA_CONT
TABLES
COMMUNICATION_IDOC_CONTROL = IT_COMM
MASTER_IDOC_DATA = IT_DATA.
COMMIT WORK.
ENDLOOP.
CALL FUNCTION ‘DEQUEUE_ALL’. (WITH OUT QUEUE IDOC WILL BE SEND TO RECEIVER SYSTEM)
• DISPLAY THE COMMUNICATION IDOC INTERNAL TABLE.
CALL FUNCTION ‘REUSE_ALV_GRID_DISPLAY’
EXPORTING
I_STRUCTURENAME = ‘EDIDC’ (WE ARE WORKING WITH ALL THE FIELDS OF EDIDC WE NO NEED
TO CREATE FCAT)
TABLES
T_OUTTAB = IT_COMM.
EXECUTE OR CHECK IDOC IN WE02/WE05.
STEP TO CREATE T-CODE FOR OUTBOUND PROGRAM :-
GOTO SE93  PROVIDE TCODE  CLICK ON CREATE
PROVIDE SHORT DESCRIPTION SEND GR INFO
SELECT RADIO BUTTON PROGRAM AND SELECTION SCREEN (REPORT TRANSACTION)
ENTER  PROVIDE THE PROGRAM NAME ………..
SELECT ALL CHECK BOXES GUI_CHECKBOX  SAVE.
STEPS TO SEND THE GR INFORMATION :-
EXECUTE TOCDE……
PROVIDE GRNO 3000001
MESSAGE TYPE GRIMAS
LOGICAL SYSTEM PT810
EXECUTE
STEPS TO TEXT THE IDOC:-
EXECUTE WE05
PROVIDE THE MESSAGE TYPE GRIMAS
“ “ “ PARTNER NO PT810
EXECUTE
ALE CONFIGURATION STEPS FOR CUSTOM IDOC INBOUND @ RECEIVER (PT810)
1. CREATE THE SEGMENT (WE31) 2. CREATE THE IDOC (WE30)
3. CREATE THE MESSAGE TYPE (WE81) 4.LINK THE MESSAGE TYPE AND IDOC TYPE(WE82)
(THESE 4 STEPS ARE NOT RAQUIRED WHEN WE ARE WORING WITH THE SAME SERVER)
5.CREATE FM(SE37) NOTE : IN THE REAL TIME WE NEVER CREATE FM, WE ALWAYS COPY THE EXISTING FM’S,
BECAUSE, THE INTERFACE PARAMETERS ARE SAME FOR ANY MESSAGE TYPE.(IMPORT,EXPORT..)
6. LINK THE MESSAGE TYPE TO FM AND IDOC (WE57)
7. CREATE MODE OF POSTING (BD51) 8.CREATE THE PROCESS CODE (WE42)
9. LINK THE PROCESS CODE TO FM (WE42) 10.CREATE INBOUND PARTNER PROFILE (WE20).
LOGIC IN 810: IN THE RECEIVER SYSTEM 810 CLIENT :-
STEPS TO IDENTITY EXISTING F.M :-
GO TO WE42 - CLICK ON POSITION
PROVIDE THE KNOWN PROCESS CODE CRE1  ENTER
DOUBLE CLICK ON THE PROCESS CODE CRE1
IDENTIFY THE IDENTIFICATION OF FM IDOC_INPUT_CREDITOR.
STEPS TO CREATE FG:-
GOTO SE37 - IN THE MENU BAR CLICK ON GOTO  FUNCTION GROUPS
CREATE GROUP
PROVIDE THE FG NAME ZPEERS_8_FG1
SHORT TEXT FUNCTION GROUP
 CLICK ON SAVE
STEPS TO ACTIVATE THE FG:
IN MENU BAR CLICK ON ENVIRONMENT INACTIVE OBJECTS
EXPAND THE FG UNDER LOCAL OBJECT
SELECT THE FG ZPEERS_8_FG1.
SELECT THE F.G->RIGHT CLICK ACTIVATE ENTER.
STEPS TO COPY THE F.M
GOTO SE37
CLICK ON COPY ICON IN THE APPLICATION TOOL BAR
PROVIDE FROM FM IDOC_INPUT_CREDETOR
TO FM Z IDOC_INPUT_CREDETOR
FUNCTION GROUP ZPEERS_8_FG1
CLICK ON COPY OR ENTER.
OPEN OUR FM IN CHANGE MODE -PROVIDE FM Z IDOC_INPUT_CREDETOR  CLICK ON CHANGE
CLICK ON SOURCE CODE REMOVE SOURCE CODE UNTILL END FUNCTION.
SAVE , CHECK, ACTIVATE THE F.M
6. STEPS TO LINK THE MESSAGE TYPE TO FUNCTION MODULE AND IDOC.
GO TO WE57 CLCIK ON CHANGE MODE ENTER,ENTER
CLICK ON NEW ENTRIES IN THE APPLICATION TOOL BAR
PROVIDE THE FM NAME ZIDOC_INPUT_CREDETOR
SELECT THE FUNCTION TYPE AS FUNCTION MODULE
PROVIDE THE BASIC TYPE Z7GRI
PROVIDE THE MESSAGE TYPE GRIMAS
SELECT THE DIRECTION INBOUND - SAVE
7.STEPS TO CREATE MODE OF POSTING:-
GO TO BD51 ENTER  CLICK ON NEW ENTRIES
PROVIDE F.M NAME , INPUT TYPE
F.M(INBOUND) INPUT TYPE
Z IDOC_INPUT_CREDETOR 0
CLICK ON SAVE.
8.STEPS TO CREATE THE PROCESS CODE AS WELL AS LINK THE PROCESS CODE TO F.M.
GOTO WE42 CLICK ON CHANGE MODE  CLICK ON NEW ENTRIES
PROVIDE THE PROCESS CODE ZGRI
DESCCRIPTION PROCESS CODE
PROVIDE IDENTIFICATION AS F.M Z IDOC_INPUT_CREDETOR
SELECT THE PROCESS TYPE AS PROCESSING BY FM.
CLICK ON SAVE (ENTER,ENTER)
SELECT THE F.M FROM TE DROPDOWN Z IDOC_INPUT_CREDETOR
CLICK ON SAVE
9.STEPS TO CREATE INBOUND PARTNER PROFILE :-
EXECUTE WE20  EXPAND THE PARTNER TYPES LS
SELECT THE PARTNER PT800
CLICK ON CREATE INBOUND PARAMETER (+)
PROVIDE THE MESSAGE TYPE GRIMAS
PROVIDE THE PROCESS CODE ZGRI
CLICK ON SAVE.
WHENEVER SENDER SENDS THE IDOC THEN IT REACHES TO RECEIVER SYSTEM AND GOES TO INBOUND
PARTNER PROFILE (WE20) AND CLICK THE MESSAGE TYPE ‘GRIMAS’ IS AVAILABLE OR NOT. IF IT IS
AVAILABLE THEN IT GOES TO PROCESS CODE ’ZGRI’ AGAINST THE PROCESS CODE IT TRIGGERS THE F.M
Z IDOC_INPUT_CREDETOR IN THAT F.M THE DATA IS LOADED INTO ‘IDOC_DATA’ INTERNAL TABLE.
 IN THIS F.M WE DEVELOP THE LOGIC TO GET THE DATA FROM IDOC_DATA INTERNAL AND POSTED TO
THEIR RESPECTIVE DATABASE TABLES.
F.M : ZIDOC_INPUT_GRITOR.
DATA : WA_DATA LIKE LINE OF IDOC_DATA,
WA_RSG1 LIKE Z17GRS1, (SEGMENT)
WA LIKE ZS7GRAI, (CUSTOM TABLE)
WA_STAT LIKE LINE OF IDOC_STSTUS.
LOOP AT IDOC_DATA INTO WA_DATA.
IF WA_DATA-SEGNAM = ‘Z17GRS1’.
WA_RSEG1 = WA_DATA-SDATA.
MOVE-CORRESPONDING WA_RSG1 TO WA.
INSERT ZS7GRAI FROM WA.
IF SY-SUBRC = 0.
WA_STAT-DOCNUM = WA_DATA-DOCNUM.
WA_STAT-STATUS = ‘53’.
APPEND WA_STAT TO IDOC_STATUS.
ELSE.
WA_STAT-DOCNUM = WA_DATA-DOCNUM.
WA_STAT-STATUS = ’51’.
APPEND WA_STAT TO IDOC_STATUS.
ENDIF.
ENDIF.
ENDLOOP.
STEPS TO TEST THE INBOUND PROGRAM BY USING INBOUND TEST TOOL WE19 :-
GOTO WE19 - SELECT THE RADIO BUTTON VIA MESSAGE TYPE GRIMAS
EXECUTE  DOUBLE CLICK ON SEGMENT Z17GRS1
PROVIDE THE SAMPLE DATA
GRNO 500000001
GRYEAR 2015
LRNO LR12 959595
VNO AP12 959595
TNAME RAVI
ENTER  CLICK ON INBOUND FUNCTION MODULE IN THE APPLICATION TOOL BAR
PROVIDDE THE F.M NAME ZIDOC_INPUT_GRITOR
SELECT CHECK BOK CALL IN DEBUGGING MODE  SELECT THE RADIO BUTTON IN FOREGROUND
ENTER
IN THE MENU BAR CLICK ON DEBUGGER  SWITCH TO CLASSIC DEBUGGERS
CONTINUOUSLY CLICK ON F5 IDENTIFY THE PROCESS FLOW AND TEST THE IDOC IN WE02/05
WHEN EVER SENDER SENDS THE DATA THEN THE DATA IS AUTOMATICALLY SEND TO THE RECEIVER SYSTEM
AND UPLOADED IN THE DB.
EXTENDED IDOC / ENHANCED IDOC :-
EXTENDED IDOC IS USED TO SEND AS WELL AS RECEIVE THE ADDITIONAL SEGMENT INFORMATION ALONG
WITH STANDARD IDOC.
SCENARIO:- AS PER CLIENT REQUIREMENT WE ADD THE CSTNO,LSTNO,PANNO TO LFA1 TABLE THROUGH
APPEND STRUCTURE . IF WE WANT TO SEND AS WELL AS RECEIVE THESE ADDITIONAL FIELD INFORMATION
THEN WE GO FOR EXTENDED IDOC.

CSTNO : CENTRAL SALES TAX NUMBER

LSTNO : LOCAL SALES TAX NUMBER
PANNO : PERMANENT NUMBER.
ALE CONFIGURATION STEPS FOR EXTENDED IDOC OUTBOUND :-
1. CREATE THE SEGMENTS (WE31)
2. CRE ATE THE IDOC (WE30)
3. LINK THE MESSAGE TYPE TO IDOC TYPE (WE82)
4. CREATE THE PORT NUMBER (WE21)
5. CREATE THE OUTBOUND PARTNER PROFILE (WE20)
6. DISTRIBUTION MODEL IS REQUIRED , IF WE PASS CONTROL RECORDS INFORMATION IN THE PROGRAM
(SENDER + RECEIVER + MESSAGE TYPE)
NOTE : BEFORE CONFIGURE THE ALE WE ADD THE ADDITIONAL FIELDS TO LFA1 TABLE THROUGH APPEND
STRUCTURE AS SHOWN IN THE BELOW.
FIELD NAME DATA ELEMENT
CSTNO ZCSTNO
LSTNO ZLSTNO
PANNO ZPANNO
1. STEPS TO CREATE SEGMENT :-
 EXECUTE WE31  PROVIDE THE SEGMENT TYPE Z17VES1
 CLICK ON CREATE  PROVIDE SHORT DESCRIPTION VENDOR ADDITIONAL DATA SEGMENT
 PROVIDE FIELD NAME AS WELL AS DATA ELEMENT
FIELD NAME DATA ELEMENT
CSTNO ZCSTNO
LSTNO ZLSTNO
PANNO ZPANNO
CLICK ON SAVE  ENTER
 REPEAT THE STEPS FOR ALL OTHER SEGMENTS.
2. STEP TO CREATE EXTENDED IDOC :-
EXECUTE WE30 PROVIDE THE EXTENDED/OBJ. NAME AS IDOC NAME Z7VEI
SELECT THE RADIO BUTTON EXTENSION
CLICK ON CREATE PROVIDE THE LINKED BASIC TYPE CREMAS05
 PROVIDE SHORT DESCRIPTION VENDOR ADDITIONAL DATA
ENTER
SELECT THE ANT ONE OF THE REFERENCE SEGMENT LIKE E1LFA1M
CLICK ON CREATE SEGMENT ENTER PROVIDE THE SEGMENT NAME/ TYPE Z17VES1
PROVIDE MINIMUM 1 MAX 99
 ENTER  CLICK ON SAVE  CLICK ON SAVE
3. STEPS TO LINK THE MESSAGE TYPE TO IDOC TYPE :-
EXECUTE WE82  CLICK ON CHANGE MODE  ENTER CLICKON NEW ENTRIES
PROVIDE THE MESSAGE TYPE
MESSAGE TYPE BASIC TYPE EXTENSION RELEASE
CREMAS CREMAS05 Z7VE1 700
SAVE  ENTER.
4. STEP TO CREATE PORT NUMBER :-
EXECUTE WE21  SELECT THE TRANSACTION RFC
CLICK ON CREATE  SELECT THE RADIO BUTTON OWN PORT NAME
PROVIDE THE PORT NAME A000000061
ENTER PROVIDE SHORT DESCRIPTIION PORT NUMBER
PROVIDE RFC DESTINATION PT810  SAVE  ENTER.
5. STEPS TO CREATE OUTBOUND PARTNER PROFILE :-
EXECUTE WE20  SELECT THE PARTNER PT810
CLICK ON CREATE OUTBOUND PARAMETER
PROVIDE THE MESSAGE TYPE GRIMAS  PROVIDE THE PORT NO GRIPORT
SELECT RADIO BUTTON TRANSFER IDOC IMMEDIATE
SELECT THE BASIC TYPE CREMAS05 AND EXTENSION Z7VEI
SAVE
6.CREATE DISTRIBUTION MODEL (BD64).
DEVELOPING THE EXTENDED IDOC OUTBOUND PROGRAM IS NOTHING BUT FILL, THE ADDITIONAL SEGMENT
INFORMATION ONLY (Z17VES1)
THE STANDARD SEGMENT ARE FIELD BY STANDARD PROGRAM.
WHEN EVER WE EXECUTE BD14 BASED ON THE GIVEN INPUT ONE OUTBOUND PROGRAM WILL BE TRIGGER AND
FETCH THE DATA FROM THE DATA BASE AND FILL THE STANDARD SEGMENTS.
HERE WE ADD THE FILLING OF ADDITIONAL SEGMENTS LOGIC TO THE [Z17VES1] BD14 STANDARD PROGRAM
ADDING SOME ADDITIONAL FUNCTIONALITY TO THE STANDARD FUNCTIONALITY IS ALWAYS THROUGH
“ENHANCEMENTS”.
 ENHANCEMENTS
ENHANCEMENT SPOT IS THE COLLECTION OF ‘BADI DEFINITIONS’
 IF WE WANT TO CREATE THE CUSTOM BADI FIRST WE CREATE ,
‘ENHANCEMENT SPOT’ . IN THAT WE CREATE CUSTOM BADI.
 ENHANCEMENTS
TWO TYPES
1.PROCEDURAL APPROACH 2.OBJECT ORIENTED APPROACH(BADI)
1.PROCEDURAL APPROACH IS TWO TYPES
1.USER EXISTS 2.CUSTOMER EXISTS
CUSTOMER EXISTS :- IS USED TO ADDING SOME ADDITIONAL FUNCTIONALITY TO THE STANDARD
FUNCTIONALITY IS ALWAYS THROUGH “FUNCTION MODULES”. CUSTOMER EXISTS ARE FOUR TYPES
1.SCREEN EXITS :- USED TO ADDING SOME ADDITIONAL SCREEN TO STANDARD TRANSACTION (SE38)
2.MENU EXIT :-USED TO ADDING SOME ADDITIONAL MENUS TO THE STANDARD GUI.
3.FUNCTION EXIT :- :-USED TO ADDING SOME ADDITIONAL LOGIC TO STANDARD PROGRAM.
4.FIELD EXIT : NOT USED.(THIS IS USED TO PERFORM THE ADDITIONAL VALIDATION ON INPUT FIELD)
USER EXIT :- IT IS NOTHING BUT ADDING SOME ADDITIONAL FUNCTIONALITY TO STANDARD
FUNCTIONALITY IS ALWAYS THROUGH ‘SUBROUTINES’ (FORM… ENDFORM)
NOTE :- IN OUR OBJECT [EXTENDED IDOC OUTBOUND] WE IDENTIFY THE RIGHT “FUNCTION-EXIT” TO ADD
THE FILLING OF ADDITIONAL SEGMENTS (Z17VES1) LOGIC TO THE STANDARD PROGRAM BD14.
”FUNCTION-EXIT” IS ALWAYS IDENTIFY THROUGH “CUSTOMERR-EXIT”
”CUSTOMER-EXIT” IS ALWAYS IDENTIFY THROUGH “PACKAGE” OF THE TRANSACTION.(BD14)
”CUSTOMER-EXIT” IS ALWAYS IMPLEMENTED THROUGH “PROJECT” [CMOD TRANSACTION]
NOTE : ‘OUTBOUND-EXIT’ WILL BE TRIGGERED AFTER FILLING OF EACH AND EVERY ‘STANDARD SEGMENT’.
STEPS TO IDENTIFY THE PACKAGE OF THE TRANSACTION :-
EXECUTE SE93  PROVIDE THE TRANSACTION BD14
CLICK ON DISPLAY IDENTIFY THE PACKAGE CGV
STEPS TO IDENTIFY THE CUSTOMER EXIT :
GOTO SMOD  CLCIK ON FIND FUNCTION KEY IN THE STANDARD TOOL BAR
PROVIDE THE PACKAGE NAME CGV  EXECUTE
IDENTIFY THE CUSTOMER EXIT VSV00002 AND ALSO VSV00001
STEPS TO IDENTIFY THE FUNCTION-EXIT :-
GOTO SMOD  PROVIDE THE EACH & EVERY CUSTOMER EXIT IN THE ENHANCEMENT
ENHANCEMENT VSV00001
CLICK ON DISPLAY  CLICK ON COMPONENTS READ THE SHORT DESCRIPTION OF EACH & EVERY FUNCTION-EXIT
& IDENFIFY THE RIGHT FUNCTION-EXIT.
NOTE : SOME TIMES WE CAN’T IDENTIFY THE RIGHT FUNCTION-EXIT BASED ON THE SHORT DESCRIPTION THEN WE
IDENTIFY THROUGH “BREAK-POINTS”.
STEPS TO IDENTIFY THE RIGHT FUNCTION EXIT BY USING BREAK-POINTS :-
EXECUTE CMOD  PROVIDE THE PROJECT NAME Z7VE1  CLICK ON CREATE
PROVIDE SHORT DESCRIPTION VENDOR ADDITION SEGMENT EXIT
CLICK ON ENHANCEMENT ASSIGNMENT IN THE APPLICATION TOOL BAR
PROVIDE THE ENHANCEMENT AS CUSTOMERR EXIT NAMES.
ENHANCEMENTS
VSV00001
VSV00002
ENTER  CLCIK ON SAVE
CLICK ON COMPONENTS IN THE APPLICATION TOOL BAR
DOUBLE CLICK ON EACH & EVERY FUNCTION EXIT
PLACE THE BREAK POINT (PLACE THE CURSOR ON INCLUDE ZXVSVU03 CLICK ON STOPN BUTTON IN THE
APPLICATION TOOL BAR)
CLICK ON BACK CLICK ON CHANGE MODE
ACTIVATE THE COMPONENTS (NOW 5 EXITS ARE ACTIVATED)
CLICK ON BACK ACTIVATE THE PROJECT Z7VE1
NOW WE EXECUTE BD14 IN A NEW SESSION/ SEPARATE SESSION
PROVIDE THE VENDOR NUMBER M2090
MESSAGE TYPE CREMAS
TARGET SYSTEM PT810
EXECUTE
WHEN WE EXECUTE BASED ON THE GIVEN INPUT BD14 OUTBOUND PROGRAM WILL BE TRIGGERED AND
FETCH THE DATA FROM THE DATA BASE AND FILL THE FIST STANDED SEGMENT (E1LFA1A) AFTER IF GOES
TO RIGHT FUNCTION – EXIT AND CURSOR IS STOPPED DUE TO BREAK-POINT AND IDENTIFY OUR RIGHT
EXIT.
INCLUDE ZXVSVU03 F.M EXIT_SAPLKD01_001
SYNTAX RULES OF IDOC :
1. THE DATA FOR THE SEGMENT MUST EXISTS , IF IT SPECIFIED AS A MANDATORY.
2. WE SHOULD NOT EXCEEDS MAXIMUM NO.OF REPEATATIONS OF SEGEMENT
3. THE DATA FOR THE SEGMENTS MUST EXISTS, IN THE SAME PHYSICAL SEQUENCE OF THE SEGMENTS IN
THE IDOC.
4. THE DATA FOR THE CHILD SEGMENT CAN’T EXISTS, WITH OUT HAVING DATA IN PARENT SEGMENTS.
NOTE : AT THE TIME OF WORKING WITH IDOC , WE MUST FOLLOW THE ABOVE SYNTAX RULES , OTHER
WISE WE GET SYNTAX ERROR ‘26’
DATA : WA_DATA LIKE LINE OF IDOC_DATA,
WA_SEG1 LIKE Z17VESI,
IT_SEG1 LIKE TABLE OF WA_SEG1,
WA LIKE EILFA1M.
IF SEGMENT_NAME = ‘E1LFA1M’(REFERENCE SEG)
READ TABLE IDOC_DATA INTO WA_DATA INDEX 1.
WA = WA_DATA-SDATA. (FILL STANDARD SEG)
SELECT CSTNO LSTNO PANNO FROM LFA1 INTO TABLE IT_LFA1 WHERE LIFNR = WA_LIFNR.
LOOP AT IT_LFA1 INTO WA_SEG1.
WA_DATA-SEGNAM = ‘Z17VES1’.
WA_DATA-SDATA = WA_SEG1.
APPEND WA_DATA TO IDOC_DATA.
ENDLOOP.
ENDIF.
IDOC_CIMTYPE = ‘Z7VEI’.
EXTENDED IDOC INBOUND @(810) RECEIVER :-
WRITING / DEVELOPING AN INBOUND PROGRAM IS NOTING BUT READ & POST THE ADDITIONAL SEGMENT
INFORMATION ONLY AND STANDARD SEGMENTS INFORMATION IS READ & POSTED BY STANDARD
FUNCTION MODULE “IDOC_INPUT_CREDITOR”.
ALE CONFIGURATION STEPS FOR EXTENDED IDOC INBOUND :-
1. CREATE THE ADDITIONAL SEGMENT (WE31).
2. CREATE THE EXTENDED IDOC (WE30)
3. LINK THE MESSAGE TYPE TO EXTENDED IDOC (WE82)
4. LINK THE MESSAGE TYPE TO FUNCTION MODULE AND EXTENDED IDOC (WE57)
5. CREATE THE INBOUND PARTNER PROFILE (WE20)
STEPS TO LINK THE MESSAGE TYPE TO F.M AND EXTENDED IDOC :-
EXECUTE WE57
CLICK ON CHANGE MODE  CLICK ON NEW ENTRIES IN THE APPLICATION TOOL BAR
PROVIDE THE FUNCTION MODULE IDOC_INPUT_CREDITOR (IDENTIFY THROUGH WE42)
SELECT THE FUNCTION TYPE AS FUNCTION MODULE
PROVIDE THE BASIC TYPE CREMAS05
 EXTENSION Z7VEI
 MESSAGE TYPE CREMAS
SELECT THE DIRECTION IS INBOUND
SAVE
CREATE INBOUND PARTNER PROFILE :-
NOTE: -INBOUND EXIT WILL BE TRIGGERED AFTER IT REACHES TO EACH AND EVERY CUSTOM SEGMENT .
OUTBOUND EXIT IS ’01’ AND INBOUND EXIT IS ‘02’
EG : EXIT_SAPLKD01_001  OUTBOUND
 EXIT_SAPLKD02_001  INBOUND
CMOD  COMPONENTS  EXIT_SAPLKD02_001  DOUBLE CLICK  WRITE
AFTER IDOC IS REACHED TO RECEIVER SYSTEM THEN IT GOES TO INBOUND PARTNER PROFILE WE20 AND
CHECK THE MESSAGE TYPE (CREMAS). IF THE MESSAGE TYPE IS AVAILABLE THEN IT GOES TO PROCESS CODE
AGAINST THE PROCESS CODE IT TRIGGERS THE FUNCTION MODULE.
THEN THE FUNCTION MODULE COLLECT THE DATA FROM THE STANDARD SEGMENT AND POSTED TO DATA
BASE WHEN EVER IT REACHES TO CUSTOM SEGMENT (Z17VES1) THEN IT GOES TO INBOUND EXIT.
IN THE INBOUND EXIT WE DEVELOP THE CODE TO COLLECT THE DATA FROM CUSTOM SEGMENT AND
POSTED TO DATABASE.
CMOD  PROJECT Z7VE (COMPONENTS )  EXIT_SAPLKD02_001  DOUBLE CLICK  WRITE
DATA : WA_DATA LIKE LINE OF IDOC_DATA, WA_RSEG1 LIKE Z17VES1, WA LIKE EILFA1M, WA_STAT LIKE LINE OF IDOC_STATUS.

LOOP AT IDOC_DATA INTO WA_DATA.

IF WA_DATA-SEGNAM = ‘E1LFA1M’.

WA = WA_DATA-SDATA.

ELSEIF WA_DATA-SEGMENT = ‘Z17VES1’.

WA_RSEG1 = WA_DATA-SDATA.

UPDATA LFA1 SET CSTNO = WA_RSEG1-CSTNO

LSTNO = WA_RSEG1-LSTNO

PANNO = WA_RSEG1-PANNO WHERE LIFNR = WA_LIFNR.

IF SY-SUBRC = 0.

WA_STAT-DOCNUM = WA_DATA-DOCNUM.

WA_STAT-STATUS = ‘53’.

APPEND WA_STAT TO IDOC_STATUS.

ELSE

WA_STAT-DOCNUM = WA_DATA-DOCNUM.

WA_STAT-STATUS = ‘51’.

APPEND WA_STAT TO IDOC_STATUS.

ENDIF.

ENDIF.

ENDLOOP.
STEPS TO DOWNLOAD THE IDOC VALUES :-
EXECUTE IDOC  SELECT THE RADIO BUTTON ANALYSE IDOC FIELD VALUES  EXECUTE
PROVIDE IDOC NAMBER 797745 (WHICH IDOC WE WANT)
SELECT CHECK BOX ALSO OUTPUT EMPTY FIELDS  CLICK ON EXECUTE
 IN THE MENU BAR CLICK ON SYSTEM  LIST  SAVE  LOCAL FILE
SELECT RADIO BUTTON SPREAD SHEET
ENTER  PROVIDE THE FILE NAME IDOC.XLS
GENERATE
WORKING WITH TRANSACTIONAL DATA :-
BY USING “MESSAGE CONTROL TECHNIQUE” WE CAN SEND THE TRANSACTION DATA.
 WHEN EVER THE END USER OR FUNCTIONAL PEOPLE CREATE AND SAVE THE TRANSACTIONAL DATA THEN
AUTOMATICALLY ONE IDOC IS GENERATED AND DISPATCHED TO RECEIVER SYSTEM . [THEY NO NEED TO
EXECUTE ANY SEPARATE TRANSACTION TO SEND THE TRANSACTION DATA ].
 ALE CONFIGURATION STEPS FOR TRANSACTIONAL DATA OUTBOUND :-
1. PROVIDE THE OUTPUT MEDIUM AS ALE FOR THE APPLICATION (NACE)
2. CREATE THE DISTRIBUTION MODEL (BD64)
3. CREATE THE OUTBOUND PARTNER PROFILE WITH MESSAGE CONTROL INFORMATION (WE20).
OBJECT : CONFIGURE THE ALE TO SEND THE PURCHASE ORDER INFORMATION TO THE RECEIVER SYSTEM.
1. STEP TO PROVIDE OUTPUT MEDIUM AS ALE :-
 EXECUTE NACE
SELECT THE PURCHASE ORDER APPLICATION
 APPLLICTION DESCRIPTION
(EF) (PURCHASE ORDER)
CLICK ON OUTPUT TYPES IN THE APPLICATION TOOL BAR
SELECT THE OUTPUT TYPE WHICH IS PROVIDED BY FUCNCTION PEOPLE
OUTPUT TYPE NAME
NEU NEW PO PRINTOUT
DOUBLE CLCIK ON PROCESSING ROUTINE IN THE LEFT PANNEL
CLICK ON CHANGE MODE IF THE O/P MEDIUM ALE IS NOT AVAILABLE
THEN SELECT THE EDI CLICK ON COPY AS IN THE APPLICATION TOOL BAR
SELECT THE TRANSM . MEDIUM AS ALE INSTEAD OF EDI
CLICK ON ENETR
2 . CREATE THE DISTRIBUTION MODEL :-
EXECUTE BD64

3. STEPS TO CREATE OUTBOUND PARTNER PROFILE :-

EXECUTE WE20
SELECT THE PARTNER (EXPAND THE PARTNER TYPE LS) IF THE PARTNER IS AVAILABLE THEN SELECT THE PARTNER
PT810
CLICK ON CREATE OUTBOUND PARAMETER
PROVIDE THE MESSAGE TYPE ORDERS
 PORT NUMBER A00000000082
SELECT RADIO BUTTON TRANSFER IDOC IMMEDIATE
SELECT THE BASIC TYPE ORDERS05
CLICK ON MESSAGE CONTROL TAB
CLICK ON INSERT ROW (+) BUTTON  SELECT THE APPL’N , MESSAGE TYPE , PROCESS CODE
APPLICATION MESSAGE TYPE PROCESS CODE
EF NEU ME10
IF WE WANT TO SEND CHANGES ALSO THEN CLICK ON INSERT ROE (+)
PROVIDE THE SAME APPL’N , SAME MESSAGE TYPE , SAME PROCESS CODE
APPLICATION MESSAGE TYPE PROCESS CODE CHANGE MESSAGE
EF NEU ME10 NO CHECK BOX
EF NEU ME10 SELECT CHECK BOX
CLICK ON SAVE
NOTE : WHEN EVER THE FUNCTIONAL PEOPLE OR END-USER CREATE AND SAVE THE PURCHASE ORDER DATA
THROUGH “ME21N” TRANSACTION THEN IT GOES TO OUTBOUND PARTNER PROFILE “WE20” AND CHECK
THE MESSAGE TYPE “ORDERS” IS AVAILABLE THEN IT GOES TO PROCESS CODE “ME10” AGAINST THE
PROCESS CODE IT TRIGGERS THE FUNCTION MODULE “IDOC_OUTPUT_ORDERS”. THEN THE FUNCTION
MODULE COLLECT THE DATA FROM THE DATA BASE AND GENERATE AS WELL AS DISPATCH THE IDOC.
IF WE WANT TO SEND THE PURCHASE ORDER DETAILS TO THE VENDOR THEN WE CREATE OUTBOUND
PARTNER PROFILE UNDER “PARTNER TYPE LI”
IF WE WANT TO SEND THE SALES ORDER DETAILS TO THE CUSTOMER THEN WE CREATE OUTBOUND
PARTNER PROFILE UNDER “PARTNER TYPE KU”
IF WE WANT TO SEND THE ACCOUNTING/ PAYMENT DETAILS TO THE BANK THEN WE CREATE OUTBOUND
PARTNER PROFILE UNDER “PARTNER TYPE B”
STATUS CODE EXPLANATION / ERROR HANDLING IN THE IDOC .
2 TYPES OF STATUS CODES :
OUTBOUND STATUS CODES (0-49)
INBOUND STATUS CODES (50-75)
NOTE :- WE47 IS THE TCODE WHICH CONTAINS ALL THE STATUS CODES AND THEIR SHORT DESCRIPTIONS.
OUTBOUND STATUS CODES : -
STATUS CODE 03 (DATA PASSED TO PORT OK):- AFTER WE GET THE STATUS CODE ‘03’ WE EXECUTE
“RBDMOIND” STANDARD PROGRAM IF THE STATUS CODE 03 TURN TO 12 THEN THE IDOC IS SUCCESSFULLY
REACHED TO DESTINATION.
IF THE STATUS CODE 03 REMAINS SAME (03-03) THEN THE IDOC IS IN THE TRFC QUEUE.
IF THE STATUS CODE 03 TURN TO 11 THEN THE IDOC IS DAMAGED IN THE TRFC QUEUE.
STATUS CODE 30 (IDOC READY FOR DISPATCH (ALE SERVICE):-
IF THE STATUS CODE REMAINS 30 THEN WE MUST CHECK THE MODE OF DISPATCH IN THE OUTBOUND PARTNER
PROFILE ‘WE20’
IF THE MODE OF DISPATCH IS “COLLECT” THEN WE MUST EXECUTE “RSEOUT00” STANDARD PROGRAM . THEN
ONLY THE COLLECTED IDOCS WILL BE DISPATCHED TO THEIR RELAVENT RECEIVER SYSTEM.
IF THE MODE OF DISPATCH IS “IMMEDIATE”.I.E DUE TO TRAFFIC.
STATUS CODE 29 (ERROR IN ALE SERVICE):-
AN ENTRY IN THE OUTBOUND TABLE IS NOT FOUND (ABAPER JOB)(LIKE PARTNER PROFILE IS NOT THERE)
DATA MISS MATCH (FUNCTIONAL PEOPLE JOB)
SYNCHRONIZATION AND CONFIGURATION PROBLEM (BASIS PEOPLE JOB)
STATUS CODE 26( ERROR DURING SYNTAX CHECK OF IDOC (OUTBOUND))
WHEN EVER , WE ARE NOT FOLLOW THE SYNTAX RULES THEN WE GET THE SYNTAX ERROR 26.
STATUS CODE 42(IDOC WAS CREATED BY TEST TRANSACTION)
WHEN EVER , WE GENERATE THE IDOC BY USING TEST TRANSACTION WE19 . THEN WE GET THE STATUS CODE
42.
STATUS CODE 01 (IDOC GENERATED) :
WHEN EVER THE COMMUNICATION IDOC IS GENERATED THEN WE GET THE STATUS CODE “01”.
STATUS CODE 00 (NOT USED, ONLY R/2)
THIS IS NOT USED IN R/3 SYSTEM . ONLY USED IN ‘R/2’ SYSTEM.
INBOUND STATUS CODES (50-75)
STATUS CODE 64 : IDOC READY TO BE TRANSFERRED TO APPLICATION
IF THE STATUS CODE REMAINS 64 THEN WE MUST CHECK THE MODE OF POSTING IN THE INBOUND
PARTNER PROFILE (WE20).
IF THE MODE OF POSTING IS TRIGGER BY BACKGROUND [COLLECT] THEN WE MUST ECECUTE
“RBDAPP01” STANDARD PROGRAM. THEN ONLY THE COLLECTED IDOC’S WILL BE POSTED TO DATABASE.
IF THE MODE OF POSTING IS TRIGGER IMMEDIATE I.E, DUE TO “TRAFFIC”.
STATUS CODE 51 : APPLICATION DOCUMENT NOT POSTED
DATA MISS MATCHED (FUNCTIONAL PEOPLE JOB)
EG:- GIVEN COUNTRY ‘IN’ IS NOT DEFINED
SYNCHRONIZATION AND CONFIGURATION PROBLEM (BASIS PEOPLE JOB)
STATUS CODE 56 : IDOC WITH ERRORS ADDED
AN ENTRY IN THE INBOUND TABLE IS NOT FOUND (ABAPER JOB) (INBOUND PARTNER PROFILE IS NOT
AVAILABLE)
STATUS CODE 53 : APPLICATION DOCUMENT POSTED
WHEN EVER THE DATA IS POSTED TO FROM THEIR DATABASE FROM THE APPLICATION THEN WE GET THE
STATUS CODE ‘53’
STATUS CODE 62 : IDOC PASSED TO APPLICATION
WHEN EVER THE INBOUND PROGRAM COLLECT THE DATA FROM THE IDOC AND TRANSFERED TO THEIR
APPLICATION SUCCESSFULLY , THEN WE GET THE STATUS CODE ‘62’.
STATUS CODE 50 : IDOC ADDED
WHEN EVER THE IDOC REACHED TO RECEIVER SYSTEM THEN WE GET THE STATUS CODE 50
NOTE : “WE11” IS THE TRANSACTION CODE TO DELECT THE IDOC’S.