Error During Interchange Handling
and SafetyAsset NetworkAsset Operations and MaintenanceCommerceOverviewSubscription Billing and Revenue ManagementMaster Data Management for CommerceOmnichannel CommerceFinanceOverviewAccounting and Financial CloseCollaborative Finance OperationsEnterprise Risk and ComplianceFinancial Planning and AnalysisTreasury and Financial Risk ManagementHuman ResourcesOverviewCore Human Resources and PayrollHuman Capital AnalyticsTalent ManagementTime and Attendance ManagementManufacturingOverviewManufacturing NetworkManufacturing OperationsResponsive ManufacturingMarketingOverviewMarket with Speed and AgilityUnique Customer ExperiencesReal-Time Customer InsightsR&D/EngineeringOverviewDesign NetworkDesign OrchestrationProject and Portfolio ManagementSalesOverviewCollaborative Quote to CashSales Force AutomationSales Performance ManagementSelling Through Contact CentersServiceOverviewEfficient Field Service ManagementOmnichannel Customer ServiceTransparent Service Process and OperationsSourcing and ProcurementOverviewContingent Workforce ManagementDirect ProcurementSelf-Service ProcurementServices ProcurementStrategic Sourcing and Supplier ManagementSupply ChainOverviewDemand ManagementDemand NetworkLogistics NetworkManufacturing Planning and SchedulingResponse NetworkResponse and Supply ManagementSales, Inventory, and Operations PlanningTransportation ManagementWarehouse ManagementSustainabilityOverviewEnvironment, Health, and SafetyProduct Safety and Stewardship NetworkBrowse by IndustryAerospace and DefenseAutomotiveBankingChemicalsConsumer ProductsDefense and SecurityEngineering, Construction, and OperationsHealthcareHigh TechHigher Education and ResearchIndustrial Machinery and ComponentsInsuranceLife SciencesMediaMill ProductsMiningOil and GasProfessional ServicesPublic SectorRetailSports and EntertainmentTelecommunicationsTravel and TransportationUtilitiesWholesale DistributionBrowse Platform and TechnologyAnalyticsOverviewBusiness IntelligencePredictive AnalyticsGovernance, Risk, and ComplianceEnterprise Performance ManagementApplication Platform and InfrastructureOverviewApplication PlatformContent and CollaborationInterface ManagementProcess Management and IntegrationData ManagementOverviewBig Data on HadoopData WarehousingDatabase ManagementEnterprise Information ManagementIT ManagementOverviewApplication Lifecycle ManagementIT Infrastructure ManagementSecurity SoftwareOverviewApplication and IT Infrastructure SecurityIdentity, Access and Authentication ManagementBrowse by ProductAnalyticsContent and CollaborationCustomer Relationship ManagementD
a Customers EDI field in to and then out of SAPSAP EDI Related DocumentsSAP EDI Translator CertificationSAP IDoc Error WorkflowSAP Partner Profile DescribedCommunicationServicesImplementing EDIOutsourcingEDI RecruitersAbout EDIEDI Related PostsLearn about EDILooking for EDI experts to contribute to EDIGenie.COM Services > Implementing EDI > What is an SAP IDoc? An IDoc Type is SAP's format for data being moved between applications. Essentially, SAP has defined what a sales order, financial statement, invoice, etc will look like electronically. This includes how fields are grouped together (segments), the order and hierarchy of these groupings, and the format of each individual field.If you're familiar with EDI at all, then an IDoc will look https://scn.sap.com/thread/527141 very familiar to you. Nearly everything you're used to is there: from segment name to allowable codes to min/max occurs.It is important to note that an IDoc Type is really just a structure defined on the system and given a name (i.e., ORDERS04). An actual IDoc, however, consists of data, which fits within the defined structure of the IDoc Type. This IDoc is identified by a http://edi.erpgenie.com/services/implementing-edi/what-is-an-sap-idoc number rather than by a type.IDoc StructureThe "only once" ruleIt is valuable to note that SAP only allows one occurence of each segment type within the IDoc structure. For instance, the E1EDKA1 segment may only exist once within the IDoc type.Now, does that mean you can only have one E1EDKA1 segment in an actual IDoc? Of course not. Segments may occur multiple times if the "max occurs" setting for that segment is greater than one. This is how the E1EDKA1 segment can appear multiple times in the ORDERS04 IDoc.This isn't a big deal if you're just using canned IDocs from SAP; but it is a useful consideration if you need to extend an existing IDoc substantially or create your own.Generic StructureData within an IDoc is divided into three sectionsControl Record, which contains (Table EDIDC) Key Fields (for inbound) Receiving Partner Type/ID (RCVPRT, RCVPRN) Logical Message Type Test Flag Other Fields IDoc Number (DOCNUM) Direction (1=Outbound; 2=Inbound) Sending Partner Type/ID (SNDPRT, SNDPRN) Status Receiver/Sender Port Created Timestamp Changed Timestamp etc. Data Records (Table EDID4 in 4.6C) Admin Data (39 bytes) IDoc Number (DOCNUM) Segment Number Segment Name (SEGNAM) (e.g., E1EDK01, E1EDK03, etc) etc Actual Data (SDATA – 1,000 b
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio http://it.toolbox.com/blogs/ehadzipetros/tracking-edi-status-in-outbound-idocs-34841 Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX Inside-ERP VoIP_News Inside-CRM maxwellarnold I_am_the_dragon PCMag Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker JoeTorre bracke Locutus Ramnath.Awate Dennis Stevenson Craig Borysowich DukeGanote Richard mircea_luca AbhaiTripathi Nikki error during Klein knowscognosdoi Clinton Jones blrvenkat Iqbalyk bluesguyAZ59 COMPANIES Hewlett Packard Hitachi America, LTD Compuware Fiberlink Communications View All Topics View All Members View All Companies Toolbox for IT Topics SAP Blogs Tracking EDI Status in Outbound IDOCs Emmanuel Hadzipetros Oct 19, 2009 | Comments (2) Tweet 1 Please Sign In or Register to like this blog. It's a little error during interchange recorded fact that one day wily Odysseus visited the Delphic Oracle to ask about whether he should participate in the Trojan War. His wife Penelope had been nagging him with a long honey-do list and poor Odysseus was feeling like he needed a break, especially since his in-laws were coming for their annual visit, which generally lasted about six months. Odysseus had heard that some of the other kings were planning an expedition to Troy to return Helen to her husband Menelaus, who was the King of Sparta and brother of Agamemnon, who in those days was the head king, the big boss, the capo di capo. Helen had run off with some Trojan prince named Paris and there was a big family scandal. All the other kings were talking about it. As they were a pretty macho group some saw it as a good excuse for a little pillaging and plundering. Since Agamemnon was the boss, Odysseus felt a certain obligation to join the expedition. But he needed a cover story for his wife Penelope.