Reg : SAP Idoc's
Hi all,
What is the difference between Generate Idoc and Process Idoc. Where it is used. Please give me the info with an Example.
Thanks
Hi,
Generate IDoc : New IDoc creation, normally occurs when idoc is being resent from one system to another system. It could be a Master data or a Transactional data.
Process IDoc: After IDoc generation, the IDoc might or might not be processed successfully in which case by using either standard programs or BD87 we can push the IDoc instead of waiting for the status change to occur.
Thanks
Krithika
Similar Messages
-
Issues in SAP(Idoc)-XI-File scenario
Dear All,
I am working on SAP(Idoc)-XI-File scenario. But in the Receiver agreement i am not able to see the idoc in order to specify some conditions there.
Please suggest if I have to do any settings in order to specify some conditions in the idoc.
Warm Regards,
N.JainHi nishu jain ,
U can specify the conditions in Reciever Determination.
1.Go to Scenarios
2.Choose your business scenario
3.Click Service without party
4.Double click Reciever Determination
5.U wil get screen in which there is a option called Configured Recievers.
6.Click there.then u wil get the screen with
Left Operand Op Right Operand
7.There u can specify the condition.
Reward points if u find this useful.......
Regards,
gyanaraj -
Pairing of EDI ASNI X.12 Transactions set with suitalbe SAP IDoc types
Hello,
I am looking to pair the following EDI ASNI X.12 Transactions set with suitalbe SAP IDoc types, for our EDI Integration.
Can some one help me to identify which suitable IDoc type, should I use? Your help is greatly appreciated.
142
824
830
846
853
861
862
864
866
I am not sure, I am seeking the help in the righr forum -:)
Thanks in advance.
NamadevHi namadev
Please you can check this link.
http://www.erpgenie.com/sap/sapedi/ansi.htm#Mapping_x12_to_SAP
thanks. -
Read/write operation on SAP IDOC file
Hi All,
We are developing an application, which will be used for registering and processing of travel data for a client.One of itu2019s functionality is to get the data from external system in different format(like CSV, Excel, Fixed Flat file, XML, main frame file, DBF and SAP IDOC) and import it into Oracle databases.
One of the design considerations for it, is to read these files and convert it into predefined XML format
and then import these data from XML to oracle database.
Currently we are analyzing the requirement and trying to find out all the Open Source JAVA API which can convert these different format files to predefined XML format, using some mapping file.
We have found out Open Source JAVA API for all the file format, except SAP IDOC files.
Any Java API to read/write the SAP IDOC file, Please advise
Regards,
Madhu
Edited by: Madhu Sudhan on Feb 17, 2009 12:06 PMHi All,
We are developing an application, which will be used for registering and processing of travel data for a client.One of itu2019s functionality is to get the data from external system in different format(like CSV, Excel, Fixed Flat file, XML, main frame file, DBF and SAP IDOC) and import it into Oracle databases.
One of the design considerations for it, is to read these files and convert it into predefined XML format
and then import these data from XML to oracle database.
Currently we are analyzing the requirement and trying to find out all the Open Source JAVA API which can convert these different format files to predefined XML format, using some mapping file.
We have found out Open Source JAVA API for all the file format, except SAP IDOC files.
Any Java API to read/write the SAP IDOC file, Please advise
Regards,
Madhu
Edited by: Madhu Sudhan on Feb 17, 2009 12:06 PM -
How can i use C# method to SAP IDoc
Dear Friends
i have to do one scenario in which i have to connect to database let us say SQL Server but i can't touch Database directly i can call a C# method(3rd party application is in .NET) and using XI i have to send it to SAP iDOC.
can any one help me in this how to proceed
Thanks in Advance.
Ishika<i>Do you have any document for that on how to do it with webservices.</i>
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79
See this
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Regards,
Prateek -
SAP(Idoc) = XI = ThirdPart(WebService)
Hello friends!
I have a problem with development of acknowledgement system with SAP(Idoc) <=> XI <=> ThirdPart(WebService) scenario.
My case:
Scenario looks like:
SAP(Idoc) <=>(Idoc adapter) XI (SOAP adapter)<=> ThirdPart(WebService)
It must work this way:
SAP system send IDOC, then XI map it and send it via SOAP-adapter to third part webservice. Then webservice answer to XI with structure сontains "TRUE" or "FALSE",
and then XI must inform SAP ALE/IDOC system if current information from idoc was successfully added to webservice or not.
But how can I get it? As far as I understand ALE/IDOC system I have to create ALEAUD by myself, put status of idoc depends on webservice return and send ALEAUD idoc to SAP.
I'am right?Hi,
You can use BPM for this Idoc--Soap Sync Process
Design objects:
Data type & Message Type
1) Import the IDOC and Later you import the Idoc, doble click on it a export it to your driver, next import it as External Definition for reason becouse if not, you wont be able to create a MI type synch with IDOC and genericResponse structure
2) Create data type for your Response Type of IDOC
3) Import the WSDL File For Request and the Response Type
4) Create the Message types according to the Data types which we created
Messgae Interface:
1) Outbound synchronous:
output message will be ur idoc external definition file
input message will be ur message type that u have created.
2) Abstract Outbound Synchronous:
use the same as in Outbound Synchronous
3) Inbound Synchronous:
input message will be ur request message of RFC/WebService
output message will be ur response message of RFC/Webservice
4)Abstract Inbound Sunchronous:
input message will be ur request message of RFC/WebService
output message will be ur response message of RFC/Webservice
Mapping
Request Message Mapping:
b/w ur idoc external definiton and request message of RFC/WS
response Message Mapping:
b/w ur Response message of RFC/WS and ur message type
Interface Mapping
Import MI(abstract) of IDOC
Import MI of WS
select the mapping for request and response Tab
BPM
1) In container window define a variable named IDoc_ABS with category abstract interface and
type (select the MI of IDOC alone)
define a variable named GenericRespnse_abs with category abstract interface and type (select
MI of genericResponse alone)
2) Create a Recieve Step --> in property message select the container you define before of idoc.
3) Define a Send Step--> mode synchronous
select MI type abstract and sync (idoc and genericResponse)
for property request message selects container Idoc_ABS
for property response message selects container GenericRespnse_abs.
Save your Changes and thats all for BPM
*Configuration *
1) Create scenario
Assign BS and create comunication channels with QoS (quality of service) type BE
2) Import your BPM
Create a Receiver Determination
-->in the target service select the BPM. Save
-->In overview windown at foot windowns select MI IDoc_abs only. nothing else
Create a Receiver Determination
-->here the system who send data is BPM
-->in the target service select the BS of receiver system.Save
-->In overview windown at foot windowns select interface mapping and assing communication channel
what we do here. the flow is next
1) Receive data from sender system and send it to BPM
2) BPM call bs of target system (WS). how? because in interface determination you selected
before the interface mapping
Regards
Seshagiri -
Hi Friends,
Can any one tell me what is the difference between SAP XML and SAP IDOC XML?
Regards,
KumarHi,
Various XML standards are supported by SAP. It presents data according to an SAP specification either in IDoc-XML or BAPI-XML, the SAP XML extensions for IDocs and BAPIs. It uses preprepared representations of the SAP interfaces to XML Commerce Business Language (xCBL) messages to facilitate communication with the MarketSet marketplaces.
Messages are stored in a generic envelope. This envelope contains metadata that controls, among other things, the routing of the messages. SAP supports two different standards for these envelopes - Microsoft BizTalk and a format similar to Simple Object Access Protocol (SOAP). Packaging SAP BAPIs in a standard envelope offers several advantages, including direct processing of messages by external applications and a uniform system of error handling.
Regards'
Aashish Sinha
PS : reward points if helpful -
Hello All,
I have a scenario where I need to pass IDOC.xml from SAP to Legacy system: we need to pass Customer Master and Material Master to the same server.. I am using same File CC to send the IDOC.xml file to the location....
Is it possible to send the name of the file with respec to IDOC type? Suppose if MATERIAL is sending then Material.xml and if Customer then Customer.xml
How can I achieve it?? I am not using any ESA objects as I am just passing message from SAP IDOC to Legacy IDOC.xml.
Thanks
RajeevHi,
I configured what you mentioend... But I am getting test.xml as I used a dummy interface name and name space as I didnt used any ESA (IR) objects.... I am jsut passing the ECC IDOC.xml to IDOC.xml to legacy applicaiton...
MATMAS01 released from ECC to sap pi.... SAP PI will pass this IDOC to Legacy applicaiton as MATMAS01.xml
DEBMAS01 released from ECC to sap pi.... SAP PI will pass this IDOC to Legacy applicaiton as DEDMAS01.xml
As I am not using any transformations and the format target system needed is idoc.xml .. I am using ID objects to forward the IDOC.xml files..
Please let me know is there any way to dynamically change the file name?
Thanks
Rajeev -
SAP IDOC's, interfaces and BAPI's
Hi i am new to SD, can anyone give me documentation or reading material for SAP IDOC's, interfaces and BAPI's .
Help would be greatly appreciated.
Thanking youHi Reddy,
Very general question, I don't think you will find the answer in one document.
BAPIs are normal function modules, with predefined input and output structures to perform standard business transactions.
IDOCs are standardised interface documents to transfer data.
Once the IDOC is read, it almost always calls a BAPI to perform the business transaction.
Therefore start with reading about BAPIs since you will definately have to master those when starting to work on interfaces.
There are hundreds of BAPIs so best is to start with a specific process, example sales order create or material master create.
Try transaction BAPI, this lists most of the BAPIs and contains excellent documentation.
Thanks for your points,
Filip -
SAP IDOC ORDERS04 Doc type support ?
How do I get an update for specbuilder that has the SAP-IDOC ORDERS04 document type ?
Hello,
It is not available in B2B Document editor standards library.
SAP used to provide these on their website at http://ifr.sap.com/catalog/query.asp
However, that page was removed about a year ago. There is an article about it here
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5520
Rgds,Ramesh -
Hi All,
I have few questions on SAP IDOC's
1. If we are using Standard IDOC, then is it only the config or any coding is required to populate the IDOC. Examaple Order03
2. If we Customize, then only customize fields needs to be populated or all the fields (SAP Standard and Custom fields)
Thanks & Regards
SMHi
1.. If we are using Standard IDOC, then is it only the config or any coding is required to populate the IDOC. Examaple Order03
Have to do complete configuration in the system.if required very less code in the fun module can be written.
see the below doc
2. If we Customize, then only customize fields needs to be populated or all the fields (SAP Standard and Custom fields)
Only code has to be written for the population of the custome fields in the custom segments of the Idoc extension in the user exit of the 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)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
<b>Reward points for useful Answers</b>
Regards
Anji
Message was edited by:
Anji Reddy Vangala -
SAP IDoc mapping to Quadrem xCBL 3.0 format?
Hi there,
We currently have an XI scenario whereby PO's and RFQ's are sent to a Quadrem system that requires the message to be in xCBL 3.0 format. I have seen that SAP provide some standard XSLT's that can convert the SAP IDoc into xCBL 3.5. (namespace - http://sap.com/xi/EBP)
To counter this currently we first run the SAP standard XSLT mapping to xCBL 3.5 and then run a Java mapping to convert that result into xCBL 3.0.......
My question is: Is there a SAP standard XSLT that can convert into the xCBL 3.0 format?
Would you recommend enhancing the SAP standard XSLT from SAP so that it caters for the xCBL 3.0 format? Obvioulsy I would prefer to just use standard SAP though....
Any ideas?
I would appreciate any advise or push in the right direction...thanks
Regards
LyntonHi Chris,
Sorry for the late response....I work at multiple clients.
What we currently do is use the standard mappings from SAP to get the IDoc into xCBL 3.5 format and use some Java mappings to take out or add in any other fields to that mapping....
To be honest I would love to have a GRAPHICAL mappings for this, it would be so much easier to maintain.......
Any ideas on what you think would be the easiest way to get this right?
Thanks
Lynton -
SAP Idocs -How to handle response from target system
Hi,
I am working on a scenario in which I will send Idocs asynchronously from SAP thro a SOAP adapter to a webservice deployed on the target system.
After the Idoc data is posted in the target system,the target system will send the acknowledgement for the receipt(basically response message).How to handle this scenario?
SAP Idoc( outbound asynchronous)---> SAP XI3.0(soap adapter) ---> Target system(inbound synchronous)
Do I need to go for BPM to handle this situation?
Is there any alterantive to BPM.
If any of the forum members who have worked on the similar scenario could help me in finding a better solution,I will be thankful to them.
Thanks,
LeoHi Udo,
Thanks for the info.My scenario is like this.
SAP R/3 Idoc -> SAP XI 3.0 <-> Webservice in the target system.
The webservice in the target system will receive the Idoc as a request messsage and send a response message synchronously.
Since Idoc is sent asynchronously( I believe Idocs sent from SAP are always asynchronous),there is no Proxy waiting in SAP R/3 to receive the response message from the target system.
If I go for BPM for the above scenario,will the BPM steps look like the following.
1)Receive Idoc from SAP.
2)Send Idoc sysnchronously to webservice
3)Receive the response from the webservice synchronously.
4.Post the response message to a proxy which can handle it further in SAP R/3.
Please note that my knowledge in BPM is limited and correct me if I am wrong.
Thanks in advance
S.Banukumar -
Release? while assigning Z Message Type to a Standard SAP IDOC Basic type
Hi Experts,
Am trying to assign a custom Message Type to a Standard SAP IDOC Basic type in WE82 transaction, but am not sure How to find the Release(last column of WE82 Tx)? Pls. let me know.
Thank youHello,
In case of IDOC, Go to Transaction WE30, type your IDOC name & select basic type & extension.
After that select Go to -> Header data (Shift+F7), you will Idoc header info. In the same pop-up you will find IDOC release for which version.
Regards,
Sameer -
Is it possible to import SAP IDOCS (e.g. ORDERS05) in B1? Is extra software needed?
Hi Johan,
Electronic File Format: the Tools is provided, and used to do most of the file transformations and imports.
It is used for all bank statements (import and export), is used to generate specific reports (Intrastat) and by SAP for specific legal requirements (i.e.the one asked by the French Legals to provide an electronic export on a specific format during controls).
Not the easiest thing to master, but a standard tool for file transformation from Inside the client (B1if will run on the server only, as you know).
sthat you are not restricted regarding the source format (you can even use a .rpt file as a source ).
If you search Inside the SCN, you'll find posts explaining how to use it.
Regards,
Eric
Maybe you are looking for
-
Can watching videos too often on Macbook Pro "wear down" the screen?
I watch most of my TV shows on my new macbook pro, and my mother just informed me that if you watch videos too often on a mac, that the screen can apparently wear down and die. Is this true? I'm not sure exactly what she meant by that or what could h
-
How can i delete an icloud account with out password or access to old email
how can i delete an icloud account with out password or access to old email
-
User Exit in F110 ( Automatic Payment Run Transaction )
HI all, I trying to find an User Exit, where i can get the 1. Run Date 2. Identification used in F110 transaction. I needed this to code for a 'Change Variant' for my custom program which is added to F110( PrintOut/data Medum). I tried to use Exit :
-
Example -- double-click to rotate shape 36 degrees
This is my first attempt to cause Visio to handle double-click on a shape. I need to rotate the shape 36 degrees each time it's double-clicked. Here's what I have right now: Enable developer tab in ribbon Select shape in developer tab, click "Show Sh
-
Send tcode ale and idoc required
Hi , Plz any body can send me all tcode used in ale and idoc Message was edited by: anil kumar