Edit Idoc data and reprocess..?

I have created one inboubd idoc this idoc is failed..
i want to change some data in the idoc and reprocess the idoc ..how can i do this..?

Hi,
You can right click on the Idoc and then open the same in edit mode.
Also in the menu tabs, you will find an option EDIT AND REPROCESS.
This way you can process the idoc and post the same with correct values.
PS: Not infront of SAP system so not able to tell the exact path. But do some R&D you will get the same.
Hope this wud be of help!!!
Regards,
Lalit Kabra

Similar Messages

How to edit Idoc data in inbound processing

Moved to correct forum by moderator
Hi All,
How to edit idoc data in inbound processing ? We have a custom FM in inbound scenario and requirement is to update a value in idoc, this value comes after certain processing in custom FM.
I tried editing it through
EDI_DOCUMENT_OPEN_FOR_EDIT
EDI_CHANGE_DATA_SEGMENTS
EDI_DOCUMENT_CLOSE_EDIT
but there is problem in this approach. By this procedure two idocs are created in system, one with original data and one with modified data. We want only one with modified data.
We do not want any direct database table updates.
Please provide appropriate solution.
Note : We are not changing status record. Please do not post replies related to status change
Edited by: Matt on Nov 19, 2008 2:24 PM

Hi,
You can edit the idoc by doing the following steps:-
1. Goto WE02 transaction and give the IDOC number and execute
2. Once the required IDOC gets retrieved then double on the text pad icon beside the segment which you wanted to change.
3. Select the Data Record at the top and click Display <-> Change option, which will enable you to change the data in that segment.
4. After doing the step 3 then click the save button to save your changes.
5. Then system will generate a new idoc number to store the actual data and your current idoc will hold the new data and the idoc will be in 69 status.
6. Execute the Program RC1_IDOC_SET_STATUS by giving your idoc number and status as 69 and new status 64 and remove the test flag
7. Then the IDOC will be in 64 status and you can reprocess the idoc with the help of the program RBDAPP01 by giving the idoc number.
The above is the entire process for editing the error idoc and reprocessing it again.
I hope I am clear and you understood the entire flow of editing and reprocessing an idoc.
Thanks,
Mahesh.

Preserving edited titles, dates and comments

Via batch changes and individual editing, I managed to organize all of my photos chronologically on my Macbook - to the best of my knowledge. However, when I try to import them to my iMac, all the edited data is lost and it reverts to either the current date of import or the old incorrect data. Is there software or a technique that will help me preserve my edited dates, titles and comments during import or export?

I have a couple of questions:
1) the edited dates, titles and comments are not remaining intact during the import, even with iPhoto Library manager. I only imported the "Modified" pics and received duplicates of every one.
2) During a ProCare one on one training, I was told not to mess with the "Originals" folder, so I didn't import it. What will happen if I do?
By the way, I put iPhoto Library Manager on my Macbook and my iMac. Is there a way to merge the libraries together and preserve the corrected dates, titles and comments? I may need a play-by-play on this.

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

Process and reprocess

Hi experts I have One doubt in ALEIdoc
If any One ask me in interview ,
How do u process Idoc in inbound side what I have to tell
and If they ask me how do u reprocess idoc at inbound side what I have to tell please guide me
Points will be rewarded
Thanks,
Durga .

Hi,
searchsap.techtarget.com/tip/0,289483,sid21_gci1268508,00.html - 68k - Cached - Similar pages
Sample Processing Routines
Last edited:
Creating and processing IDocs are a widely mechanical task, as it is true for all interface programming. We will show a short example that packs SAP R/3 SapScript standard text elements into IDocs and stores them back to texts in a second routine. The text elements can be edited with SO10.
Outbound function     IDoc outbound functions are function modules with a standard interface which will read data from an application database and convert the data into IDoc format.
     The interface parameters need to be compatible with a well defined standard, because the function module will be called from within another program.
Inbound function     IDoc inbound functions are function modules with a standard interface, which will interpret the received IDoc data and prepare for processing by an application.
     The received IDoc data is processed record by record and interpreted according the segment information provided with each record. The prepared data can then be processed by an application, a function module or a self-written program.
     The example programs in the following chapters will show you how texts from the text pool can be converted into an IDoc and processed by an inbound routine to be stored into another system. The following will give you the basics to understand the example.
Text from READ_TEXT     SAP R/3 allows the creation of text elements, e.g. with transaction SO10. Each standard text elements has a header record which is stored in table STXH. The text lines itself are stored in a special cluster table. To retrieve the text from the cluster, you will use the standard function module function READ_TEXT . We will read such a text and pack it into an IDoc. That is what the following simple function module does.
     If there is no convenient routine to process data, the easiest way to hand over the data to an apllication is to record a transaction with transaction SHDB and create a simple processing function module from that recording.
Sample Inbound Routines
Last edited:
Inbound processing is widely the reverse process of an outbound.. The received IDoc has to be unpacked, interpreted and transferred to an application for further processing.
Inbound processing function module     Below is the example of an inbound function module. This module expects an IDoc with rows of plain text and will save this text under a given name to SAP's text database. The procedure will extract the text name and the text line from the IDoc and hand over the text data to the function module READ_TEXT which will store the text in the text pool.
FUNCTION
""Lokale Schnittstelle:
*"       IMPORTING
*"             VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"             VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*"       EXPORTING
*"             VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"             VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"             VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"             VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*"       TABLES
*"              IDOC_CONTRL STRUCTURE EDIDC
*"              IDOC_DATA STRUCTURE EDIDD
*"              IDOC_STATUS STRUCTURE BDIDOCSTAT
*"              RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"              SERIALIZATION_INFO STRUCTURE BDI_SER
DATA: XTHEAD   LIKE THEAD .
DATA: TLINES LIKE TLINE    OCCURS 0 WITH HEADER LINE.
CLEAR XTHEAD.
REFRESH TLINES.
*** --- Unpacking the IDoc --- ***
LOOP AT IDOC_DATA.
     CASE IDOC_DATA-SEGNAM.
       WHEN 'YAXX_THEAD'.
            MOVE IDOC_DATA-SDATA TO XTHEAD.
       WHEN 'YAXX_TLINE'.
            MOVE IDOC_DATA-SDATA TO TLINES.
     ENDCASE.
ENDLOOP.
*** --- Calling the application to process the received data --- ***
CALL FUNCTION 'SAVE_TEXT'
       EXPORTING
            HEADER          = XTHEAD
            SAVEMODE_DIRECT = 'X'
       TABLES
            LINES           = TLINES.
    ADD SY-SUBRC TO OK.
füllen IDOC_Status
fill IDOC_Status
    IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
    IDOC_STATUS-MSGV1 = IDOC_CONTRL-IDOCTP.
    IDOC_STATUS-MSGV2 = XTHEAD.
    IDOC_STATUS-MSGID = '38'.
    IDOC_STATUS-MSGNO = '000'.
    IF OK NE 0.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
    ELSE.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'S'.
      CALL_TRANSACTION_DONE = 'X'.
    ENDIF.
    APPEND IDOC_STATUS.
ENDFUNCTION.
Unpacking the IDoc data     The received IDoc data is processed record by record and unpacking is a simple discrimination by case according the segment name provided with each record..
*** --- Unpacking the IDoc --- ***
LOOP AT IDOC_DATA.bb
     CASE IDOC_DATA-SEGNAM.
      WHEN 'YAXX_THEAD'.
            PERFORM UNPACK_IDOC TABLES IDOC_DATA USING XTHEAD.
      WHEN 'YAXX_TLINE'.
            PERFORM UNPACK_TAB TABLES IDOC_DATA TLINES.
       ENDCASE.
ENDLOOP.
Application processing     When the IDoc is unpacked it needs to be passed to the application. In our case this will be a simple call to a standard function which is going to store the data to the text database.
*** --- Calling the application to process the received data --- ***
CALL FUNCTION 'SAVE_TEXT'
       EXPORTING
            HEADER          = XTHEAD
            SAVEMODE_DIRECT = 'X'
       TABLES
            LINES           = TLINES.
Writing a status log     Finally the processing routine needs to pass a status record to the IDoc processor. This status indicates successful or unsuccessful processing and will be added as a log entry to the table EDIDS.
fill IDOC_Status
    IF OK NE 0.
      IDOC_STATUS-STATUS = '51'.
    ELSE.
      IDOC_STATUS-STATUS = '53'.
    ENDIF.
    APPEND IDOC_STATUS.
     The status value '51' indicates a general error during application processing and the status '53' indicates everything is OK. There are numerous other status values, with distinct meanings, but '51' and '53' are the most common ones.
http://idocs.de/www3/cookbooks/id
verify if it helps
Thanks & regards,
sravani yendru

How can you determine a file creation date and know if it's been altered since the creation date

I need to know how to determine a file creation date on an ipad. If someone creates a document/note on an ipad how can you tell when it was created and if it has been altered since?

Unless you are using a third party app that provides that functionality, in iOS the only thing youcan access is the last edit/save date and time, which is fairly evident in the user interface for documents and notes. Some apps that handle MS Office files may provide that, but ican't say first hand.

What is the best way to edit meta data..

What is the best way to edit meta data and tag photos, faces, places etc. and have the data saved to the original photo.
On a PC I would just use Windows Gallery. iPhoto on the Mac allows for some tagging, but it doesn't save to the original file.
I like to have my photos in a folder, edit them and save the changes.
What software would work best on a MAC to accomplish this?
Thanks for any help,
Nick

iPhoto is a database and any metadata you add or edit is available in any app - if you learn how to use it.
iPhoto is a non-destructive processor. It never touches the original file - it treats it like a film shooter treats the negative.
If you want a copy of the original file with the metadata included simply export a copy.
This User Tip
https://discussions.apple.com/docs/DOC-4921
has details of the options in the Export dialogue.
As an FYI:
For help accessing your photos in iPhoto see this user tip:
https://discussions.apple.com/docs/DOC-4491

Aperture 3.0.3 Adjust Date and Time

Working on a batch (~3K) scanned images that all need to be adjusted for date and time, the adjustments and so forth. All notes below is with Master images.
My observations so far with the unpredictable "Adjust Date and Time" function, "D&T" hereafter and some suggestions on improving Aperture.
0. Always make sure that you start by "edit->deselect all" - even if nothing is selected.
APPLE: PLEASE MAKE IT SIMPLER TO SEE WHAT IS SELECTED (MASTERS, VERSIONS, etc).
1. Always use US language selection - Language selection seems to matter for D&T. I am from Denmark, living in US but often switch between US and DK language (to get some special characters). In Denmark we use dd-mmm-yyyy and in use we use mmm-dd-yyyy. When i use the danish locale with the "D&T" function Aperture D&T is totally unpredictable - so stick with US.
APPLE: PLEASE DONT BE TOO SMART BUT USE THE D&T FORMAT LISTED IN THE D&T DIALOG BOX
2. D&T time-shift does not work. Unfortunately this 'capability' cannot be disabled - Somehow Aperture check what the time was originally stamped on the image and use this for the new "D&T" - first i though that this was adjusting ~1 sec between images but it seems that Aperture do something like the following (sorry for my non-applescript'ish examples below)
newTime = "edit->adjust date and time"
foreach image do
set time to image.D&T.time
try() change image.D&T.time newTime+image.D&T.time
catch () newTime image.D&T.time
Not good as it time-shift from the original picture - if the time is good this is not a problem but if time (from the stamp) is off (like all of mine) most likely the time will get the date to wrap into the next day (or year if you got a bunch of images)..
APPLE: PLEASE ADD AN OPTION TO DISABLE TIME-SHIFT in D&T
3. Dont include DNG - Aperture cannot change the date for a dng and it seems to screw up the time-shift in "D&T" - i think the algorithm do something like
newD&T = "edit->adjust date and time"
for each image do
set D&T to image.D&T
try() change image.D&T to newD&T
catch() newD&T = image.D&T
The problem seems to be that when Aperture work on a image it cannot change it use this images (that it cannot change) D&T for the next images D&T, i got a bunch (a ton actually) of examples
1994
1994
2008.dng
2008
When using a different language locale it gets even worse.
APPLE: PLEASE DO NOT CHANGE THE D&T COUNTERS WHEN WORKING ON A FORMAT NOT (WELL) SUPPORTED.
4. Always check your trash for images - after i deleted projects (empty, no images) i have found images for those projects in the trash. Cannot explain why this is but i am happy that i checked the trash before emptying - put back works just fine.
I am currently using the following methodology for my scans.
1. load in all pics, create albums for years and projects for months - e.g. 1993.0201 <text>, 1998.0327 <text> and sort scans to the correct albums and projects
2. export each album as separate libraries, open library, fix D&Ts, places and faces. Exit, reopen and check trash for images that should not have been deleted. Clean trash, close.
- For faces i add a few pics' of recognizable folks - open faces and select from the many suggestions aperture offers - very fast.
3. Open or import library to master (my master got ~20K pics currently)
I am interested in learning if i am the 'only one' with Aperture D&T 'problems' or if i am using the tool incorrectly.
Kenneth

nathan:
What type of edit were you making. Have been trying to duplicate that and cannot. I've changed the date and selected the original file to be changed also. Then I edited the file by cropping, changing the exposure and shadows and saving. Both versions are still tiff files.
Now these are tiff files that I converted over from jpgs with Photoshop as my camera doesn't take tiffs. Don't know if that will make any difference.
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

Variant Data and Data (Type)

I'm on my way to build a XML parser for my program.
How do you make Variant display it's Data and Data (Type) like the one on my screenshot?
I dont want my data type be a string. I want it to be the same as my cluster.
Is there a way to edit the data and data type for a variant control and return the same data for it's indicator?
Thanks!
Attachments:
aaa.jpg ‏23 KB
BBB.jpg ‏32 KB
CCC.jpg ‏19 KB

Can you demonstrate how exactly you're editing the Variant data type, as string...!!
Below is an example, where I converted a cluster (Error data type) into variant and also displayed it on the Front Panel.
Now if you wanna edit the original cluster data, by editing the string displayed in Variant indicator, this is not a good idea. Ideally you should convert the Variant data type to its original data type and thendo modification and convert it back to Variant.
saintalan94 wrote:
the VI at the link you provided have a password, I cant even look into the VI.
Those VIs are provided as it is from its developer and even I don't have the password.
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT.

Date and time inidacator not showing up

I have recorded on mini DV tape with the date and time indicator on, but when I try to log and capture it into FCP for editing, the date and time is not there. I'm sure it's on the tape as I have played it back on several several different tvs and monitors, but for some reason I can't get FCP to read it.
Please advise if you can.
Chorine
G 4 Mac OS X (10.4.8)

Playing back the tape in the camcorder that originally recorded the tape with the display output activated, doesn't mean that you actually recorded the date & time as part of the video. Check the user's manual of your camcorder to find out how to record date & time as part of the image - not just to a data track. FCP doesn't access the data code info.
-DH

How to edit data from an IDOC with errors and reprocess it

Hi,
We are working with SAP XI for communicate with an external systems by files (external) to IDOCS (SAP R/3).
Sometimes we need to edit the data from an inbound IDOC, because the external system generates wrong information and that can't be processed directly.
We had seen posts like:
But we wanna to do it with no ABAP editor.
¿Can we change the data from the IDOC in other way (transaction) and reprocess it?
We tried with /WE05, pushing EDIT button, but can't edit the data from the IDOC.
Thanks in advance for your help
Regards,
Federico Martin

Keep Looking at forums i founded:
change idoc data
To change the Inbound IDoc,
1)Go to WE05/WE02, enter the Inbound IDoc number and Execute.
2)Double Click on the segment (Page Icon) where you want to change the Data.
3)In the Screen 'Display data record for IDoc' , Go to menu 'Data record' and click on 'Display - > Change'. Then it display a popup information 'Changes to the IDoc are written to the database' , then press enter .
To Process the Edited Inbound Idoc , execute the program 'RBDAGAIE' in SE38 and enter the IDoc number.
Thanks
Sekhar
AND
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
Also if you have something to say about it will be appreciated
thanks

Status for idoc to edit and reprocess it

Hi ,
I have a senario in which i need to hold the idocs for invoice coming as inbound in SAP .
Then once the PO is created editing the Invoice idocs to add PO by editing the IDOC and reprocess the same idoc and post invoice corresponding to PO in SAP and then change the status of that idoc to 53.
Can someone help me,with the status that i need to set to only have the idocs in SAP .
And then use those idocs to edit anf add PO and save it for status 32 (idoc edited).
And run some standard program to change the status to 53 with invoice created.
Thanks,
Richa

Richa,
You can set the idoc status to '51' in the customer exit of inbound idoc processing function module . Check the TABLES/CHANGING/EXPORT parameter of FM for something like EX_PROTT .. here you can pass the error message after checking the PO number ..
I'm not sure how are you linking Accounting document to PO.. you can use your logic to update the PO/set the idoc in error status in customer exit .
-Tushar Shukla

Update Excel to sharepoint and edit the data.

Hi experts,
Happy New Year to all,
I would like to know is it possible to update my excel sheet having 10 different fields (Columns) to share point, and edit them as a list. Want to know step by step procedure.
My requirement is as below
I want to update the list of activities for each member of my team, in a excel in the first 5 columns and then upload to the share point daily, as my team members were placed in different locations, I want them to update their achivements
for the day in the next 5 respctive columns. By filtering on their names respectively. So that I can check online and take the report back to excel whenevery i required.
I want to know
1) Step by step procedure I can upload the excel to share point
2) is it possible to restrict the data on particular field, to respective users.
Request to let me know how i can achive.

Excel and SharePoint List does not allow two way sync it is only unidirectional.
You have to go by Scott's suggestions or else Office Web Apps which will allow excel Semiformal co-authoring (http://office.microsoft.com/en-us/sharepoint-server-help/document-collaboration-and-co-authoring-HA101812148.aspx).
Here is how you can use the import Excel funcationality in SharePoint custom list.
1. Define a table to your Excel Data and Save the excel file
2. Go to your site, create a new list either using Site Settings or All site content menu, by selecting Import SpreedSheet
3. select table in the import dialog box
SharePoint will create a new list with the excel data.
As per your requirement , the challenges that we have are -
"a excel in the first 5 columns and then upload to the share point daily"
You cannot reimport excel to a list as per your above requirement, there is only one way of importing to a list library and every time it will create a new list.
" I can check online and take the report back to excel whenevery i required."
You can export the list to excel file for processing offline and again there is no resync between Excel and List.
"is it possible to restrict the data on particular field, to respective users"
You can use item level permission for restricting user access to a list item or use SharePoint designer custom workflow to give item level access.
http://www.sharepointbriefing.com/spcode/article.php/3911751/Implementing-ItemLevel-Security-in-SharePoint-2010-and-2007.htm
http://social.msdn.microsoft.com/Forums/en-US/1911c999-8083-4d35-9cdc-3b9c3a7242a7/how-to-create-item-level-permission-for-list-in-sharepoint-2010?forum=sharepointgeneralprevious
Hope this helps!
MCITP: SharePoint 2010 Administrator
MCTS - MOSS 2007 Configuring, .NET 2.0
| SharePoint Architect | Evangelist |
http://www.sharepointdeveloper.in/
http://ramakrishnaraja.blogspot.com/

HT4910 I have a simple question or 2. 1) how can I see what is on my icloud and how do I edit the data if I do not want it on icloud. 2) I have an app that I would like to update data - it doesn't appear to be doing that, how can I fix that? It is the mob

1) how can I see what is on my icloud and how would I edit the data that is on it?
2) I am having problems with an app syncing data with pc - how can I fix that? It is mobile noter.

Welcome to the Apple Community.
You can see what's in iCloud collectively at settings > iCloud > storage & back up > manage.... You can only edit the data through the appropriate app (contacts, calendars etc)
For problems with 3rd party apps, contact the developer.

How do you edit out the date and time stamp from a photo

How do you edit out the date and time stamp from a photo

You can blur it out with retouch
The built-in "Retouch" brush in "Edit" mode should suffice, if the background is mostly uniform, and if you set the size of the brush to slightly wider than the bar width of the letters. For example, in this picture I removed the year from the date (in the lower right corner) by using the "retouch" brush and following the contours of the letters. (the screen shot is from iPhoto '11, but iPhoto 9 should give similar results).
Regards
Léonie

Edit Idoc data and reprocess..?

Similar Messages

Maybe you are looking for