Search

Home Trai ni ngs Qui z Ti ps Tutori al s Functi onal Cert Q's I ntervi ew Q's Jobs Testi moni al s Adverti se Contact Us

SAP Virtual/Onsite Stepbystep guide to ALE and IDOCs

IntroductiontoEDIandALE:
Document Categories:
EDI(ElectronicDocumentinterchange)EDIistheelectronicexchangeofbusiness
documents between the computer systems of business partners, using a standard
ABAPTM
formatoveracommunicationnetwork.
AdobeForms
ABAPHR
EDIisalsocalledpaperlessexchange.
ALE&IDocs
ALV
Advantages:
BAPI
ReducedDataentryerrors
BASIS
BSP
Reducedprocessingtime
BusinessObjects Availabilityofdatainelectronicform
BusinessWorkflow Reducedpaperwork
CRMNEW ReducedCost
LSMW Reducedinventoriesandbetterplanning
SAPScript/SmartForms Standardmeansofcommunications
BI/BW Betterbusinessprocess
eXchangeInfrastructure(XI)
EnterprisePortals(EP) EDIhastwoprocess
eCATT 1.Outboundprocess
ObjectOrientedProgramming 2.Inboundprocess
SAPQuery
Userexits/BADIs
OutboundProcess:
WebDynproforJava/ABAPTM
1.Applicationdocumentiscreated.
Others
2.IDOCisgenerated
3.IdocistransferredfromSAPtoOperatingsystemlayer
What's New? 4.IdocisconvertedintoEDIstandards
5.Edidocumentistransmittedtothebusinesspartner
6.TheEdiSubsystemreportstatustoSAP
ABAPTestCockpitHOT
SAPABAPPragmas InboundProcess:
UnderstandingSE32(ABAPText 1.EDItransmissionreceived
ElementMaintenance) 2.EDIdocumentisconvertedintoanIDOC
CreatinganIDocFileonSAP
ApplicationServer
3.IDOCistransferredtotheSAPlayer
UnderstandingAdvancewith 4.Theapplicationdocumentiscreated
dialogoptionofSAPWorkflow 5.Theapplicationdocumentcanbeviewed.
SAPWorkflowScenario:
MaintenanceNotificationApproval IDOC:
Enhancementstoastandardclass IDOCisacontainerthatcanbeusedtoexchangedatabetweenanytwoprocesses.
WorkingwithFloatingFieldin
AdobeForms EachIDOCisassignedauniquenumberfortrackingandfuturereference.
InsertingdatafromInternalTable
intothestepSendMail IDOCconsistsofseveralsegments,andsegmentscontainseveralfields.
DisplayGLAccountlongtextusing
enhancementframework
IDOCcontainsthefollowingthreetypesofrecords...
Differencesbetweenpolymorphism
inJAVAandABAP 1.OneControlRecord.
Passingmultilineparametersfrom 2.OneormanyDataRecord
anABAPClasseventtoaWorkflow 3.OneormanyStatusrecord.
container
ConceptofReevaluateagentsfor InIDOCsthefollowingtermsaretobeknown.
activeworkitemsinSAPWorkflow PORT:
Dynamiccreationofcomponent Port is used in the outbound process to determine the name of the EDI subsystem
usageinABAPWebDynpro
AdobeForms:Displaysymbolslike
program, the directory path where the IDOC file will be created at the operating
copyrightandothers systemlevel,theIDOCfilenamesandtheRFCdestinations.
DeactivateHoldfunctionalityin
Purchaseorder(ME21N) RFCDestination:
QuizonOOABAP Used to define the characteristics of communication links to a remote system on
AddfieldsinFBL5NusingBADIs whichafunctionsneedstobeexecuted.
TutorialonWidecasting
DefiningaRangeinModulePool PartnerProfile:
Program
Copyfieldsfromone
Partner profile specified the various components used in an outbound process
structure/tableintoanother (Partnernumber,IDOCtype,messagetype,Port,Processcode),themodeinwhich
structure/table it communicates with the subsystem (batch or immediate) and the person to be
SidePanelUsageinNWBC notifiedincaseoferrors.

MessageControl
Contribute? Used in pricing, account determination, material determination, and output
determination. The message control component enables you to encapsulate
businessruleswithouthavingtowriteABAPprograms.
Sample Specs
TOProcessIDOCSthefollowingTCODESwillbeused.

What's Hot? Onbothsides:

LogicalSystemNamesSALE
WebDynproforABAPTutorials SetupRFCdestinationsSM59
PortDestinationsWE21
JointheMailingList
InSourcesystem:
Enternameandemailaddressbelow:
Name:
SegmentCreationWE31

BasicIDOCTypeCreationWE30
Email:
MessageTypeCreationWE81
Subscribe Unsubscribe AssignMessageTypeToBasicIDOCTypeWE82
GO
DistributionModelBD64

WritingReportProgramSE38
PartnerProfileWE20
MessagecontrolNACE

CheckIDOCsWE02,WE05

InDestinationSystem:

CreatingFMSE37

AssignFMtoLogicalMessageWE57

DefineI/PmethodforInboundFMBD51

CreateProcessCodeWE42

GeneratePartnerProfileBD64

IDOCprocessinginthesameinstanceofR/3Clients.

ForexampletwoclientsinthesameR/3instance.

Client900.

Client800.

To transfer the data between two clients the table structures and their data types
shouldbematch.

Inthisexample,Client900isSourcesystem,andClient800isdestinationsystem.

InClient900Ihavecreatedacustomizedtableandinsertedsomerecords.

InClient800Ihavecreatedonlytable.

CommonStepsinBothClients:

CreatingtheLogicalSystemNamesandAssigningtoClients:

GotoTCODESALE.

IMG path IDoc Interface / Application Link Enabling (ALE) > Basic Settings >
LogicalSystems>DefineLogicalSystem

ClickonDisplay/ChangeButton

ClickonNewEntries


SpecifytheLogicalSystemnameanddescription.

Note:LogicalSystemNamingconventionis<SID>CLNT<NNN>

ClickonSaveandBackbuttons

NowyouwillcomebacktotheIMGpathscreen.ClickonAssignLogicalSystemto
client.

ClickonDisplay/ChangeButton

ClickonNewEntries


ClickonSaveandBack.

Clickheretocontinue...

Pleasesendusyourfeedback/[email protected]
HomeContributeAboutUsPrivacyTermsOfUseDisclaimerSafeCompanies:AdvertiseonSAPTechnical.COM|PostJobContactUs
SAPTechnical.COM.Allrightsreserved.
Allproductnamesaretrademarksoftheirrespectivecompanies.SAPTechnical.COMisinnowayaffiliatedwithSAPAG.
SAP,SAPR/3,R/3software,mySAP,ABAP,BAPI,xApps,SAPNetWeaver,andandanyotherSAPtrademarksareregisteredtrademarksofSAPAGinGermanyandinseveralothercountries.
Everyeffortismadetoensurecontentintegrity.Useinformationonthissiteatyourownrisk.

GraphicDesignbyRoundtheBendWizards