Workflow and EDI - relation

Hi experts,
Is workflow in any way related to EDI ?
How good is workflow related to EDI? Can you please suggest some good books/ material on workflow?
Please give your input.
Thanks.

Similar Messages

Is there any certification exam only related to workflow and workflow/cross

Is there any certification exam only related to workflow and workflow/cross apps

Hi KR,
to my knowledge SAP has stopped certifications for WF.
But Please check on sap.com
Aditya

Relation between idoc and EDI,ALE

Hi,
I am new to IDOC. Can u please tell me whether there is any relation between IDOC and ALE or IDOC and EDI. If so what is the relation between them.

Hi Buvana,
ALE is a means of migrating DATA between SAP systems. You configure logical destinations, establish some migrating criteria and the system takes care of getting your data from point A to point B.
EDI ->
EDI is described as the interchange of structured data according to agreed message standards between computer systems, by electronic means. Structured data equates to a simple and direct method of presenting the data content of a document. The method of ensuring the correct interpretation of the information by the computer system is defined by the EDI standard."
EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
Info shuttle - "I was implementing EDI at a customer and I wanted some real data to test with in Development, so I asked the Project Manager to see if he could arrange something. Literally, 20 minutes later he came back and said that there were 10 new orders in Development, together with the customer master records related to the order, the carrier vendor master record, the material master records, ... were all there. I asked him how he had done it so quickly which led me to my first exposure with Infoshuttle, a tool that does this for you using the ALE functionality. As an ALE consultant I know how to do this stuff but I also know how long it would take to set that up.
www.sapgenie.com/sapedi/edi_sap_training.htm
www.sap-img.com/basis/ difference-between-edi-and-idoc.htm
www.help.sap.com/saphelp_nw04/helpdata/ en/35/26b592afab52b9e10000009b38f974/content.htm
www.help.sap.com/saphelp_nw04/helpdata/ en/35/26b594afab52b9e10000009b38f974/content.htm
http://www.onestopsap.com/interview-Question/edi/
IDocs act as data containers in an ALE scenario. They are just a format of storing application data and then transferred using ALE. Take a look at http://www.sapgenie.com/ale/why_ale.htm and http://www.sapgenie.com/sapgenie/docs/ale_whitepaper.doc for further details on ALE.
Check this link.
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.henrikfrank.dk/abapexamples/IDOC/IDOC.htm
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
http://help.sap.com/saphelp_47x200/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
Regards,
Priyanka.

Difference btw idoc ale and edi

Hi all,
I'm a beginner in abap, can anyone send me the concepts of ALE, IDOC and EDI and the difference btw all the three.
Also do send some materials for the same.

Hi,
ALE (Application Linking and Enabling)
Ale Technology is SAPs technology to support distributed yet integrated processes across several SAP systems.
Distributed Process:
A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.
Need for Distributed Process:
Business in Different Geographical Locations.
Non availability of dedicated network.
Cultural and language differences in Geographical locations.
Running of Mission-critical Applications (Like Maintenance downtime etc.).
Separate up gradation of Modules.
Distributed SAP SYSTEM CHALLENGES
A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.
Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.
Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.
Receiving systems that can handle their own problems and not tie up the sending system.
Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.
A sound technology and methodology that can be used in all distribution scenarios.
SAP Distributed environment:
ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
Benefits of ALE:
Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocs definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch ALE Service).
IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
Basic integrity check: A basic integrity check is performed on the control record.
Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function modules output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).
IDOC:
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404]
[http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm]
[http://www.sappoint.com/presentation.html]
[http://www.allsaplinks.com/idoc_search.html]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://www.erpgenie.com/sapedi/idoc_abap.htm]
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
[Re: How to create IDOC;
Check below link. It will give the step by step procedure for IDOC creation.
[http://www.supinfo-projects.com/cn/2005/idocs_en/2/]
ALE/ IDOC
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.sappoint.com/abap/ale.pdf]
[http://www.sappoint.com/abap/ale2.pdf]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sappoint.com/abap.html]
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs]
go trough these links.
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.sappoint.com/abap/ale.pdf]
[http://www.sappoint.com/abap/ale2.pdf]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sappoint.com/abap.html]
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[www.sappoint.com]
--here u can find the ppts and basic seetings for ALE
[http://sappoint.com/presentation.html]
[www.sapgenie.com]
[http://www.sapgenie.com/ale/index.htm]
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
RFC:
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
[http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm]
check out the following link it might help you
[http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf]
EDI:
Electronic Data Interchange
Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
Refer
[http://www.erpgenie.com/sapedi/index.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
[https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
[http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
[http://www.erpgenie.com/sapedi/index.htm]
[http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
EDI FLOW :
Here is some thing which helps you and here the purchase order is taken as example too..
Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
What parts of the business cycle can be supported by EDI?
Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
How does EDI get started?
EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
What is the flow of EDI?
The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
check this.
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
[https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
[http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
[http://www.erpgenie.com/sapedi/index.htm]
[http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
[ALE / IDOC / RFC / EDI]
[SAP ABAP and EDI/ALE/IDOC]
[Re: IDOC/BAPI/ALE/EDI]
Regards,
Dhruv Shah

Tapeless workflows and Sandy Bridge or other PC's: KISS or LOVE?

Tapeless workflows and Sandy Bridge or other PC's: KISS or LOVE?
Life used to be so simple when shooting video on a tape based camera. You shot your material, captured it for editing and stored your precious original footage on tape in a safe and dry place. Sure, it took time to capture, but the big advantage was that if you had a computer or drive failure, you would still have the original tape so everything could be recreated.
Now with tapeless workflows we have the significant advantage of much faster import of the original footage. Connect the flash card or disk drive to the computer over USB and copy the data to a HDD on the computer, ready for editing. The data on the flash card or disk drive can then be erased, so you can reuse it for more shots. But, like Johan Cruyff has said repeatedly, every advantage has its drawback. In this case it simply means that you no longer have the original material to fall back on, in case of computer or drive failures. That is a very unpleasant and insecure feeling.
The easy anwser to that problem is backups. Backup of the original media, backup of projects and backup of exports. This often means a bundle of externals for backup or NAS configurations. One thing is clear, it requires discipline to make regular backups and it costs time, as well as a number of disks. Four as a minimum: 1 for media, 1 for exports and at least 2 for projects. Note: This is excluding a backup drive for OS & programs.
There are different backup strategies in use. Some say backup daily and use one disk for monday, one for tuesday, and so on. Others say one disk for the first backup, the second for the second backup, then the first again for an incremental backup, etc. and once weekly a complete backup on a third disk. Whatever you choose, be aware that shelf live of a disk is far less than tape. There are horror stories everywhere about ball-bearings getting stuck after some time and without original tapes, you better be safe than sorry, so don't skimp on backups.
What is the relevancy of all this? I thought this was about Sandy Bridge and other PC's.
It is and let me try to explain.
Card based cameras are for the most part DSLR and AVCHD type cameras, and we all know how much muscle is required to edit that in a convenient way. Adobe suggests in the system requirements to use raid configurations for HD editing and practice has shown that raid arrays do give a significant performance boost and improve responsiveness, making for a nicer editing experience. The larger the project and the longer the time-line, the more a raid array will help maintain the responsiveness.
One thing you would not do is using a raid0 for projects, media and exports, even if you have backups. The simple reason is that the chance of disk failure multiplies by the number of disks in the raid0. Two disks double the chance of disk failure, three disks triple the chance, four disks quadruples the chance, etc.
Remember: Disaster always strikes when it is most inconvenient.
Imagine you have been working all day on a project, you decide to call it a day and to make your daily backup, but then the raid fails, before you made your backup. Gone is all of today's work. Then take into consideration the time and effort it takes to restore your backups to the state it was in yesterday. That does not make you happy.
Another thing to avoid is using a software or mobo based parity raid, for the simple reason that it is slooowww and puts a burden on the CPU, that you want to use for editing, not house keeping.
For temporary or easily recreated files, like the page-file, media cache, media cache database and preview files, it is very much advised to use a raid0. It makes everything a lot snappier and if disaster strikes, so what? These are easily recreated in a short time.
This was a general overview of what is required with tapeless workflows. Now let's get down to what this means in terms of system design.
Two approaches or train of thoughts
KISS: Keep it stupidly simple or LOVE: Laughing over video editing
The first one, the most economic one, is to use a system with 3 or 4 disks internally and 4 or more backup disks.
A typical disk setup can look like this:
This is a perfectly sensible approach if one does not have large or complex projects, long time-lines and is willing to take the risk of occasionally losing a whole days work, between backups. Many hobbyists and consumers fall in this category.
The KISS approach keeps it stupidly simple. The drawback is that there is no logical way to add more disks or storage. The discipline, diligence and effort required for regular backups make it far from a laughing matter. In fact it can quickly become a bore. Add to that the fact that the disk setup is simple but not very fast, so less suited for situations where lots of clips are involved, multi-cam is a regularly recurring situation or lots of video tracks are involved.
A number of video editors want more from their system than the occasional platonic KISS, they want to really LOVE their system, which lead to the other train of thought.
This is more costly than the KISS approach, but you all know a fiancée or wife is more costly and dear than the occasional kiss on the cheek by an old friend.
Let's start with a typical disk setup. It may look like this:
Two striking differences in comparison to the KISS approach:
1. Much easier disk organization and more disks and thus more space.
2. It requires a hardware raid controller, causing a higher investment cost. It is like an engagement ring. You don't get LOVE for free, one of the guiding principles of the oldest trade in the world.
These are easy statements to make, but what are the benefits or advantages, that you would fall in LOVE with such a system, and what are the drawbacks? Think back to Johan Cruyff's adage.
The only drawback is cost. The advantages are multiple, easier organization, more speed, more storage, snappier editing, no jerkiness, lesser requirements for regular backups and - this is the major benefit - hardly a chance of losing a day's work in case of a drive failure. Keep in mind that a parity raid keeps all your data intact in case of a drive failure, so lessens the need for up-to-date backups.
We all know, we get what we pay for: "If you pay peanuts, you get monkeys. OTOH, if you pay money to monkeys, you get rich monkeys". But in this case you get what you pay for, a much better editing experience with a much easier workflow.
Using a parity raid (be it raid 3/5/6/30/50/60) you get security, ease of mind that you are protected against losing precious media, that you need not worry about the last time you made a backup, that the editing you did today may be lost and you save valuable time editing and a lot of aggravation because of a much more responsive system.
How does this all relate to Sandy Bridge and other PC's?
First of all, the price difference between a Sandy Bridge / P67 platform and an i7-950+ / X58 platform is very small. Of course the new architecture is slightly more expensive than the older one, but the differences are small, almost not worth talking about.
So what are the differences? Look below:
The first thing to keep in mind is that the Sandy Bridge is the successor of the i7-8xx CPU and as such it is much more evolutionary than revolutionary. The CPU power has increased significantly over the i7-8xx due to new architecture and a smaller production process (32 nm), but in essence all the capabilities have remained unchanged. Same memory, same PCI-e lanes, same version, same L3 cache and no support for dedicated raid controllers.
It is great that the processor performs much better than the older i7-8xx CPU's, almost achieving the level of the i7-9xx range of processors, but is still limited:
The Sandy Bridge is unsuitable for anything more than a KISS system.
Why? Because it lacks the required PCI-e lanes to accomodate more than a 16 x PCI-e nVidia card with CUDA support to enable hardware MPE acceleration and the integrated graphics are not supported by CS5.
You may wonder if that is a bad thing. The plain and simple anser is NO. It is a great processor, it delivers great value for money, is a solid performer, but it has its limitations. Intel had a reason to position this CPU as a mid-level CPU, because that is what it is, a mid-level performer in comparison to what is to come.
The term mid-level performer may seem strange when compared to the old generation of i7-9xx CPU's, because they perform almost equally well, but keep in mind that there is a generation difference between them.
So what about the i7-9xx and X58 platform?
It still is going strong. About the same performance as a Sandy Bridge, with only the much more expensive hexa-cores clearly in the lead, both performance and price wise. The quad cores deliver about the same value for money. The main difference however is the platform that allows a dedicated raid controller to be installed, thus making it the platform of choice for those who want to go from a passing KISS to true LOVE.
And what lies ahead?
Sandy Bridge E on the Waimea platform (X68). Now that is revolutionary. More than double almost everything a processor can offer: double the cores, double the PCI-e lanes, triple the memory, more than double the L3 cache, increase the PCI-e support from 2.0 to 3.0, etc...
This is why Intel calls this a high-end CPU / platform.
So what now?
If you prefer a KISS approach, choose either a Sandy Bridge/P67 or an i7-950+/X58 platform.
If you wonder whether in the future you may need multi-cam more frequently, edit more complex projects and longer timelines or even progress to RED, look at KISS/LOVE solutions, meaning the i7-950+/X58.
If you can't have downtime, time pressure is high, delivery dates to clients are critical or you edit highly complex projects, lots of multi-cam situations or lengthy time-lines, choose a LOVE solution, an i7-950+/X58 platform.
If you have the time to wait till Q4/2011, Sandy Bridge E/Waimea looks to be worth the wait.
Hope this gives you some more insight into recent and future developments and helps you make wise investment decisions.

I'm upgrading from an AMD 3800+, cutting with Vegas 7 Pro. Usually shoot DSLR or HDV, sometimes P2, EX or RED. I have ridiculously cheap access to Macs, FCP/FCS, all kinds of software.
I've been agonizing over this for the last month, was originally hoping the UD7 mobo was the solution, read the read about the NF200/PCIe issue a few days ago, http://www.dvinfo.net/forum/non-linear-editing-pc/489424-i7-980x-now-wait-sandybridge-2.ht ml- and still decided to go for a 2600k.
My preference is to treat my video footage the same way as my digital imagery: I make (at least) duplicate back ups of everything before reformatting the cards, never delete the back ups, and only worry about the day-to-day stuff at night. Unless I'm rendering or involved in other long processes, in which case I'll back up the work in process the next day. If I am under a really really tight deadline I might back up as I go.
Yes, a RAID might make it easier, but I'm paranoid enough to prefer a slower, safer backup. You can always duplicate, and usually improve upon, a days work, but you can never get back original footage you lost. I have only ever had one hard drive die on me (a few enclosures crapped out, though)- it took a couple of (mostly unattended) hours to rectify. As a matter of act, I've had far more loss/damage from tapes than from hard drives.
I ordered the UD7, 2 F4s and 4 F3Rs, understanding I will probably want to upgrade to SBE when it comes out, or maybe next year. The 2600k/mobo/RAM will likely hold its value better than a 950/X58, likely because of the marketplace as much as merit.
The UD7 / RAID card issue is in it's early days, there may be a solution/mitigation. Probably not. But if I really really need a RAID card, then I probably really really need a 980, NAS, etc etc.
But Harm still rocks!

Workflow and Shopping Cart

Hi Colleagues,
I want to know how do we relate a shopping carts to the workflows created for it.
Example: When i create a shopping cart, an entry is created in CRMD_ORDERADM_H and workflows are created. Can you tell me which table to check the workflow and how. (Table links).
Regards,
Rishav Surana

Hi,
You can get WF details..
How to Get WorkItem ID
Saravanan

Comparison between split Adapter in Seeburger and EDI Separator

Hello All,
Currently we are designing EDI interfaces using B2B Add-On.
I am trying to compare the split Adapter of Seeburger and EDI Separator of B2B Add-on.
In Seeburger Splitter configuration:
The additional split configuration helps to map the Sender ID, (EDIType,Transaction,Version) combination to split channel and sender agreement.
I believe a List of Sender Id, Mappings (Standard, Transaction, Version) combinations can be added to the same Split channel and Sender Agreements.
In B2B Add-On:
The sender ids , EDI details are directly mentioned in the channel and it is bound to sender agreement.
Does it reduce the flexibility in EDI Scenarios.Is that a correct point of view?
Your inputs highly appreciated.
Thanks.
Regards,
Sudharshan N A

Dear Sudharshan,
yes, I would say that this is a correct point/observation. When the Seeburger Adapters were introduced many years ago, one focus was put on the flexibility by keeping all functionality related to the "format conversion" (Classifier/Bic/Splitter) completely separated from the "data transmission" functionality directly in the channel.
This way, the format conversion modules could be included in any adapter that was running on the AdapterEngine and not just to the See-Adapters.
In a typical setup on client side, almost all inbound channels were using the "AUTO" functionality to detect all required parameters to select the right Split-Channel...so all channels had the same module-chains included (no matter if it was an AS2-Channel or a simple FILE/FTP-channel.
This also allowed for easy reprocessing of any received file (via AS2, X400 , OFTP or else....) by just putting the file again to a file-channel with the same module-chain parameters.
Kind Regards
Stefan
Btw... I am not very familiar with the B2B AddOn, but if you have additional questions regarding the Seeburger-EDI-Adapters, feel free to ask...

Idoc and EDI for FI

Hi all,
Can anyoune help me out with the topics.
Idoc and EDI and how this are related to FI.
I was looking for some scenario.
How to process inbound idoc and outbound idoc.
Thanks advance for help.
Regards,
sha

Idocs can be triggered internally by standard coding logic. It can also be triggered by output.
For idocs in delivery processing:
http://help.sap.com/saphelp_erp60/helpdata/en/38/c1853488601e33e10000009b38f83b/frameset.htm
LE-SHp -> printing and communication -> Delivery interface. (here these idocs are generated by output).

Idocs ale and edi

Hello Experts,
       I am beginner in IDOCS,ALE AND EDI concepts, i would appreciate if some one can forward me material on these concepts, also some sample programs or examples on these.
Thanks.
Raghu

Hi,
ALE Process Steps:
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
IDOC
Check these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
EDI
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
http://www.erpgenie.com/sapedi/index.htm
http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
reward points if useful
regards,
ANJI
Message was edited by:
        Anji Reddy Vangala

RAW PHOTO WORKFLOW AND BACKUP?

i have a canon 20D which is set to shoot both jpegs and raw photos. when i plug my card reader into my mac, it automatically opens IPHOTO5 and then i download the images. i get two thumbnails, one says it is a raw, the other a jpeg. but:
1) i have no idea how to backup the raw images to a dvd or to my external hard drive. and (see below for related problem)
2) i don't know how to work with the raws. i do own photo shop, but tried dragging the thumbnail into photoshop, and it tells me it could not complete the task because it is the wrong kind of document. i had the same problem when just trying to drag those raws onto my desktop. is this because i am just dragging thumbnails, and if that's the case, where do my raws reside in IPHOTO?
3) and, even if i can figure out how to get the raws into photoshop, when i go to save them, how and where should i save them and if i want to use the corrected raw to send for printing, do i need to change to a different format? and should i save the new file in iphoto?
4) last, i get the feeling that maybe the raw photos i have imported from my cards into iphoto (then deleted the originals) now no longer exist as raws anywhere. does iphoto not actually import the raw, but just a raw thumbnail?
sorry for all the questions that might seem elementary, but i have never had a digital SLR and i really need to establish a proper workflow and make sure to backup my most important photos.
many thanks for all suggestions!

1. Click on the Finder icon on the Dock to open the Finder, open the Pictures folder, and you will see several dated folders (folders named as such: 2005-11-20, 2005-01-07, 2006-01-07, etc.). Each folder contains pictures you downloaded form your camera on those dates, but only photos you have not deleted.
2. Down the bottom somewhere (in the Pictures folder) you will see iPhoto Library. Open this folder and you will see more folders, but dated as follows: 2004, 2005, 2006, etc. Open one of these folders, and you will see other folders, but numbered as follows: 01, 02, 03, 04, 05, 06, 11, 10, etc.
Not every one of these numbered folder will have an "Originals" folder, but some will.
Whatever you do, don't change the folder's names, or structure of anything in the iPhoto's Library. I have no idea if you should drag the original photos out of the Originals folder, but I would think that you can duplicate the photos, and drag only the copies into another folder on the desktop.
Keep in mind that you can set the iPhoto Preferences so that PhotoShop Elements is set as the photo editing application. If you set iPhoto to do that for you, when you double-click on any of the photos on the iPhoto window or display, Elements will automatically launch and open the photo for you. If the photo is a RAW or JPEG, Elements will show it as such at the left bottom corner. If you want to leave the RAW photo intact, just rename the copy you are working with- before you save it (don't save any photo with it's original name to avoid changing the original). However, you can save an original that has been changed in a format such as TIFF, and in another folder, CD, another hard drive, etc. TIFF files are not compressed and take lots of space on the hard drive, but the photos does not degrade. Every time you work with a JPEG image it degrades.
Again, wait for others to respond to your post. They may have better ideas than mine.

IDOC and EDI

Hi,
Please send me some useful information on IDOC'S and EDI with relevance to SD module and comman errors with this documents.

Standard SAP format for electronic data interchange between systems (Intermediate Document).
Different message types (for example, delivery confirmations or purchase orders) normally represent the different specific formats, known as IDoc types. Multiple message types with related content can be assigned to one IDoc type
Example:
The IDoc type ORDERS01 transfers the logical message types ORDERS (purchase order) and ORDRSP (order confirmation).
Among other areas, IDocs are used in both Electronic Data Interchange (EDI) and for data distribution in a system group (ALE
Another
The EDI interface is used to connect an EDI subsystem to the SAP system. EDI subsystems perform all EDI-related tasks such as Converting the data Handling messages or interchanges Communications Managing the partner profiles Monitoring processing. The EDI interface is based on IDoc technology. IDoc technology is independent of EDI standards. All data is exchanged via files between the SAP System and the EDI subsystem. The synchronous RFC (remote function call) is used to define the time of transfer of the files between both systems. Via the EDI interface, the following data can be exchanged:
Outbound IDocs. IDocs are transferred from the SAP System to the EDI subsystem.
Inbound IDocs. IDocs are transferred from the EDI subsystem to the SAP System.
Status report. To inform the SAP System of the progress of processing of the outbound IDocs, the EDI subsystem transfers the status report to the SAP System.
The object of the certification is the technical test of the interface between SAP System and EDI subsystem. The transfer of outbound IDocs, inbound IDocs and the status report are tested. The test is performed for the EDI standard UN/EDIFACT. As an example, the messages used are:
Outgoing order (ORDERS)
Incoming order (ORDERS)
Outgoing order response (ORDRSP) and
Incoming order response (ORDRSP).
Regards

IDOC and EDI generation

Hello all,
I would like to know how IDOC and EDI gets generated. What is the purpose of using IDOC and EDI. which one gets triggered initially and is there any interface that has to be set for IDOC and EDI generation
Pl. post any docs/Link related to IDOCs and EDI.
Thanks,
Maxx

Idocs can be triggered internally by standard coding logic. It can also be triggered by output.
For idocs in delivery processing:
http://help.sap.com/saphelp_erp60/helpdata/en/38/c1853488601e33e10000009b38f83b/frameset.htm
LE-SHp -> printing and communication -> Delivery interface. (here these idocs are generated by output).

Data Fir IDOC ALE and EDI

Hello All,
    I am newly join in IT company (Name don't want to specify) . They have putted me in a consolidate project in which I do have to work on IDOC,ALE and EDI object.
yet in my career with SAP ABAP I haven't work on the above mention terms of SAP. Can some One please guide me and provide me some material to prepare my self best for the things.
Regards
Swati Namdev

Some use full Tcodes:
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
WE02     List Of All Idocs Created. (Default, Additional, EDI)
WE05     List Of Idocs Created.    (Standard, Additional)
WE06     Active Monitoring For Idoc Processing.
WE07     Idoc Statistics.
WE08     Display View u201CFile Statusu201D:Overview-Path Name.
WE09     Idoc Search For Business Contents (Database).
WE10     Idoc Search For Business Contents (Archive).
WE12     Modification Of Outbound File, Triggering Inbound Processing.
WE14     Process All Selected Idocs.
WE15     Selection Program For Issuing Output.
WE16     Trigger Inbound Processing.
WE17     Trigger Status Processing.
WE18     Generate Test Status File For Outbound Idocs.
WE19     Test Tool For Idoc Processing
WE20     Partner Profile.
WE21     Ports In Idoc Processing.
WE23     Display Test Catalog Test Idoc Interface.
WE24     Maintain Table View. Direction-1.(Outbound)
WE27     Maintain Table View. Direction-2.(Inbound)
WE30     Develop Idoc Type.
WE31     Develop Idoc Segments.
WE32     View Development.
WE33     Maintain Table Views.
WE34     Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
WE40     Display System Process Code.
WE41     Display View: Logical Msg Overview. For Outbund.
WE42     Display View: Logical Msg Overview. For Inbound.
WE43     Display Status Records.
WE44     Display Partner Types
WE45     Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
WE46     Global Parameter For Idoc Interface.
WE47     Status Maintenance.
WE50     Display Text For Process Code System.
WE54     Idoc Function Module For File Name
WE56     Display Status Process Code
WE57     Idoc Assignment Of FM To Log. Message And Idoc Type.
WE58     Text For Process Code Status.
WE60     Documentation For Idoc Type.
WE61     Documentation For Idoc Record Type.
WE62     Documentation For Idoc Segment Type.
WE63     Documentation For Idoc Record Types And Idoc Types (Parser).
WE64     Process Code In Idoc Inbound And Outbound.
WE70     Conversion Table For Basic Types.
WE71     Conversion Table For Extensions.
WE72     Conversion Table For Field DOCTYP.
WE73     Conversion Table For Logical Message Type.
WE81          EDI:Logical Message Type.
WE82     Message Types And Assignment To Idoc Types.
WE84     Assignment Table Between Idoc And Application Field.
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
BD10     Send Material (Matmas)
BD11     Get Material.
BD12     Send Customer.
BD13     Get Customers
BD14     Send Vendor.
BD15     Get Vendor.
BD16     Send Cost Center. (Cosmas)
BD17     Request Cost Center.
BD18     Send G/L Accounts.
BD19     Get Master Data G/L Accounts.
BD20     Inbound Processing Of Idocs Ready For Transfer.
BD21     Creating Idoc Types For Change Pointers.
BD22     Delete Change Pointers.
BD23     Serialization Using Time Stamp: Deletion Of Old Time Stamp.
BD24     Send Cost Elements.
BD25     Send Activity Type (COAMAS)
BD26     Request Activity Type
BD27     Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
BD28     Cost Center/ Cost Elements: Send Control Records.
BD30     Material Bom Distribution. (Bommat).
BD31     Document Structure Distribution. (Bomdoc)
BD32     Plant Allocation To Material Boms Distribution.
BD33     Distribution Of Material Variants. (STTMAT)
BD34     Distribution Of Boms (BOMORD)
BD35     ALE: Send Business Process Group.
BD36     ALE: Send Business Process.
BD37     ALE: Send Business Process Price.
BD40     Generate Idocs For Serialization Group From Change Pointers.
BD41     Dispatch Of Idocs Of Serialization Group.
BD42     Check Dispatch Status Of Idocs Of Serialization Group.
BD43     Processing Inbound Idocs Of Serialization Group.
BD44     Change View u201CSerialization Groupu201D.
BD47     Dependence Between Methods.
BD48     Dependence Between Methods And Message Type.
BD50     Activate Change Pointers For Message Type.
BD51     Characteristics Of Inbound Function Module.
BD52     Determine Work Area.
BD53     Reduce Message Type.
BD54     Change View: Logical Systems
BD55     Idoc Conversion.
BD56     Maintain Idoc Segment Filters.
BD57     Link Type And Serialization Type Of Message Type.
BD58     Convert Organizational Unit.
BD59     Allocation Of Object Type.
BD60     Additional Data For Message Type.
BD61     Activate Change Pointers Generally.
BD62     Display Conversion Rule.
BD63     Transport Of Ale Tables For A Message Type.
BD64     Display Distribution Model.
BD65     Maintain Idoc Type Required Fields.
BD66     Change Idoc Fields.
BD67     Function Module For ALE/EDI Overview.
BD68     Maintain List.
BD69     Assignment Of Idoc Type To Message Type.
BD70     Cross-System Comparison Of Number Range Objects.
BD71     Attributes For Receiver Determination.
BD72     Active Events For ALE/EDI
BD73     Start Error Handling For Non-Posted Idocs.
BD75     Status Conversion With Trfc Execution.
BD77     Generate Transport Requests For Distributing ALE Customizing Data.
BD78     Monitoring Ale Customizing Data Transport
BD79     ALE IDOC Segments - Conversion Rule
BD81     Filter Objects For BAPI Parameter Filtering
BD82     Generating Partner Profile
BD83     Re-Processing Incorrect Outbound Odocs.
BD84     Re-Processing Of Idocs After ALE Input Error.
BD85     Consistency Check: Reassignment Between Two System.
BD86     ALE Consistency Check: Create Purchase Order From Sales Order.
BD87     Select Idocs
BD89     Customizing Data Modeling For Distribution Model.
BD91     Distribute All Characteristics Via ALE.
BD92     Distribute Class Via ALE: Send Direct.
BD93     Distribution Of Classification Data Via ALE.
BD95     Ale Object View
BD96     Filter Object For Receiver Determination Of Methods.
BD97     Assign RFC Destination For Synchronous Method Calls.
BD98     Consistency Check With Workflow Link
BD99     Dependencies Between Message Types.
BD100     Display Serialized Idocs. (Serialization Using Object Types)
BD101     Serialization Using Object Types: Consistency Check.
BD102     Ale: Outbound Channel Registry.

BPM, Workflow and Netweaver - Need Clarification

Hi Guru,
I am new to workflow, BPM and Netweaver. I have several questions about those concepts.
1. What is/are the different between workflow and webflow. Which scenario should take workflow into consideration? Which scenario webflow can be applied to?
2. What is/are the different between workflow and BPM. If I am going to implement workflow in a company, do I need to implement business workflow as well as BPM?
3. I need clarification on Netweaver platform and concept.
4. What is/are the different between workflow in R/3 and workflow under Netweaver?
5. If I am going to implement workflow integrated with R/3 and Outlook email, do I need to buy new wrokflow for Netweaver and Netweaver platform or alternatively, I can use business workflow module under R/3 system?
Sorry for many questions asked. I am new to those products. I am now working on software selection for workflow technology. My company is going to implement new workflow to client. Thank you very much.
Cheers,

Please ask only one (or closely related) questions per thread. This makes it a lot easier to get a good structure in the database of previously answered questions. While we are on the subject of previously answered questions, I think you should have a look at them....
My suggestion is therefore:
1. Close this thread
2. Read the Frequently Answered Questions. Before you ask (here are many workflow answers)
3. Search the forum.
4. Create new threads if you have questions afterwards.

WorkFlow and Air Crashed Windows 7

Well installed Worksflow at work on an XP machine and I like it. So when I got home I installed it on a fresh install of Windows 7 via Firefox and it killed the user. I got a opaque white cover over all 3 of my LCD's. Did a hard re-boot and booted as normal to the login but after logining in the screen goers blue with an error msg. I can boot into safe mode fine. So some drive is either corrupt or it hashed my video drivers. I created a new user and it acts the same.
I tried to un-install WorkFlow and it give me an error saying that it is corrupt.
Any ideas?
theDogger

Well found the solution....It actually was Symantec Enterprise Ainti-Virus that was corrupted. Not sure how but after a re-install it is fine now. But now I have new issue. My PS4 is crashing. If I open PS4 and do nothing in under a minute it closes. Then looking at the error long in the admin cousel it show a ntdll.dll error. Looked on line and could not find anything in direct relation to this error. I dunped pref's...un-installed and re-installed but same issue. I do not even have a printer installed like some of the posts suggest. So I backup and dumped the entire machine and started from scratch again.
theDogger

Workflow and EDI - relation

Similar Messages

Maybe you are looking for