Difference btw OBI and BO

Hi,
We are very big financial institution in europe, we are in transition period of migrating our core banking platform to new platform. We are currently using Business Objects(BO) as our REPORTING tool for our oracle database, Our new core banking application is FLEXCUBE which is again from Oracle Financial services (formerly known as iflex).
Now that we need to make a decision and comparision between the features of OBI and BO.
Could anyone give us PRO's and CON's on OBI and BO ?
Thanks in advance
Shankar.

Shankar,
It's one thing to ask for a specific question - another to request a free gap-analysis.
Most people here volunteer their time , because it helps them to learn.
not to diss you or anything - but it seems as you're trying to make someone else do the work for you.
Good luck.
so you don't feel bad - there's a link to the comparison
http://businessintelligence.ittoolbox.com/groups/select/bi-select/oracle-bi-server-ee-vs-cognos-8-bi-1426419
Edited by: wildmight on Sep 25, 2008 8:16 AM

Similar Messages

Difference btw BOE and LC ?

Hi all,
Whats the difference btw BOE and LC ?? As I am not having good domain, plz if anyone having some good documenattion regarding general workflow in companies, plz send me to [email protected] or paste here.
Suresh

Check the below link .May be useful.
http://www.netmba.com/accounting/
Regards
Aravind

Difference btw J2ME and SAP MI

Hi All,
I have a basic doubt , what is difference btw J2ME and SAP MI.
I understand while J2ME devlopment we develop MIDLET and how do we call the Midlet in Mibile ??
What is the advantages of both and limitation of j2me , stopping me not use that and go for SAP MI
Advantages of sap mi in a nustshell would be appreciated.
Thanks for reply
Regards
Srinivas

Hi Srinivas,
SAP MI currently known as NetWeaver Mobile 7.10] could be seen as a technology platform to mobilise enterprise applications(for occassionaly connected / disconnected scenarios)
Mobile consists of a server component named Data Orchestration Engine [DOE] and a java based Mobile client for Windows Mobile devices. DOE is an ABAP component that acts as an interface between your SAP/non-SAP Backend [like ERP, CRM etc] and the Mobile device by staging the data , distributing it to relevant receivers with extensive monitoring capabilities with a model driven approach.
DOE talks to backend via Bapiwrappers / webservices and talks to mobile device (client running on the device) with a messaging protocol over http(s).
Apart from the default java mobile client that is shipped from SAP , any custom client written in any native client technology could be integrated to DOE.
There is also a co-innovation model along with partners like sybase where there are some mobile solutions already available in market like mobile sales that could be run on smart phones like iphone,blackberry etc.
You can checkout several articles and blogs available in sdn itself for Mobile for understanding more about this .
Regards,
Liji

What's the difference btw JDK and SDK?

I went to the download page,some of the download are for J2SE Development Kit (JDK) ,some others are J2SE Software Development
Kit (SDK)?Are there any difference btw them?

Sun changed the label from SDK to JDK when Java 5 was
released.There was at least one earlier change, I believe, so it seems it was JDK, then became SDK (or J2SDK) and now back to JDK.
In the context of Java, if you're not a purist about matching a particular acronym with a particular version, then the two are interchangeable.

Difference btw table and structure???

Hi all guru's
What is the difference between table and structure??
culd you explain me???
regards
ss

hi Supriya,
structure is one single line, while a table can have as many lines as you wish.
hope this helps
ec

Difference btw utl_file and dbms_lob

hi,
what is the difference between utl_file and dbms_lob , is that doing same acess file or difference?

797525 wrote:
what is the difference between utl_file and dbms_lob , is that doing same acess file or difference?
UTL_FILE is a PL/SQL package that provides PL/SQL code with the standard operating system I/O interface. You will find this same interface in languages like C, C++, Pascal, PHP, Perl and others.
DBMS_LOB is a PL/SQL package that enables you to manage a LOB data type in Oracle. This data type is "special" in that it can contain large data objects (like video, sound, images, documents, spreadsheets, etc).
So technically, there is very little that is the same between the two.
Conceptually however, both are interfaces to "files". The only difference is that UTL_FILE access external files (on an operating system's file system). Whereas DBMS_LOB provides the ability to create and store and manage "files" directly in the database. (there is also a BFILE data type that looks like a LOB but is actually an external file)
It is seldom a good idea to step outside the database into an o/s file system using UTL_FILE. There are security and access control issues. Issues with concurrency and transactions. Issues with data integrity. Issues with backup of such data. Etc.
So in general, when you deal with the concept of "+files+" in Oracle, you should be looking first at using the Oracle database itself - and deal with files as LOBs using DBMS_LOB.

Difference btw Shuffle and Shuffle/Repe

This may sound like a dumb question, but what is the difference between the Shuffle mode and the Shuffle/Repeat mode?

In theory, Shuffle will play all songs in the queue once in random order then stop. Shuffle Repeat will play all songs in the queue once, then repeat.
In reality if you have a LOT of tracks in the queue it may well repeat before it gets to the end of the list, as the shuffle memory is limited.

I do not what tech. is lacking in iphone 4 that prevents it to be able to support turn by turn navi. I do not see any difference btw 4 and 4s and yet 4S can support turn by turn. very disappointed with apple and i will not purchase iphone5.

I do not know what tech. s lacking in iphone 4 that prevents it to be able to use turn by turn navi. I do not see any difference between 4 vs 4S and yet 4S is able to support it. I am very disappointed with apple as i was when 4S was released. I will not purchase iphone5 becuase i think its nowhere near what apple calls it "perfect". there are plenty of other phone around. Lumia 920 for example is a much better phone. Just disappointed with apple...

http://www.apple.com/ios/whats-new/
the fine print in the map section states that turn by turn is only available for 4S and up.

Difference btw simulator and actual disc behavior

Okay, so I have a project in which the buttons behave properly in the simulator, but then on the finihsed disc it's all wonky!
To be specific, I have it so that, if you're playing a track and are up to chapter 10 when you hit MENU, it takes you to chapter 10 in the chapter listing. And in the simulator, it does this.
However, when I burn the disc, or otherwise watch the TS folder in DVD Player, when I hit MENU, instead of going to the current chapter, it goes back to the first chapter in the first MENU, regardless of where I am. Anyone know what I'm overlooking?

I use this method all the time, specifying the chapter index buttons as the menu jumps for markers in a track, and it usually works both places. (Simulator, build in DVD Player, burned disc...)
I can imagine a few things that might have this effect:
are there any stories, etc., attached to your track? markers in a track can overrride the default menu jump for the track, but stories will override default behaviors for both the track and its markers.
Are there any pre-scripts on your menus or tracks? Assigning pre-scripts can sometimes supersede other DVDSP commands, such as button selection. In the DVD spec, commands that are processed before a menu or title are referred to as pre-commands. Specifying a button on a menu as a target winds up using the pre-command on the menu to select the specific button, but if you set a pre-SCRIPT for the menu in DVDSP, DVDSP will apply that to the menus pre-command instead of the button selection specification. One of the few remaining ways in which DVDSP is not a completely spec-based tool.
Try assembling a quick plain-vanilla test with a new project and check a build in DVD Player to make sure it's not something specific to your project.
Hope this helps -
Max Average

What is the difference btw EXPINV and INVOIC

INVOIC :Invoice / Billing document
EXPINV : Export invoice
What is the fifference between these two message types.
I need to trigger Idoc once the INvoice verification is done using MIRO t-code. I mean I need to send Actual cost of the material to 3rd party application using XI after Invoice is verified. Iam just wondering which Idoc I need to trigger? Please help..
Message was edited by: Ram Krish

Hi Ram,
Message type <b>INVOIC</b> is used to transmit the invoice to the customer for the shipped goods.
Message type <b>EXPINV</b> is used to transfer foreign trade information from R/3 to an external system.
For more information, please check this link.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDFTCOM/SDFTCOM.pdf
For your case, you can use message type INVOIC to send actual cost of the material to 3rd party system.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

What is exactly difference btw individual collective call blank and 1?

Hello all
Could you please to help me get ride of that what is exactly difference btw blank and 1 in MTO scenario?
it is better if you guy can show me a example.
Thanks

Hi,
In case of any requirement through sales order, it will be the special stock categoery E and material should have Individual and Collective Indicator as 1 in MRP4 view .It depends on what item category you are going to use in the sales order .
In MTS strategy, You can't achieve based on each requirement But you can get the plan order( system will combine all the requirement ) generated.
Example
If you have Asembly Material A, and components X,Y & Z for A.
For MTO
MRP generates the Planned Order for the Assembly and components with respect to the sale order requriement.
Fot MTS
MRP generates the Planned Order for the assembly and components based on the stock requirement.
Regards,
Sundhu

Difference btw cf8 standard and enterprise

hi,
i've downloaded the pdf from adobe website stating the
difference btw standard and enterprise edition. But i'm quite
puzzled on this:
Enterprise feature that runs through the Enterprise Feature
Router (EFR). These features will run in the Standard
Edition. However, all features running through the EFR will
be limited to one shared simultaneous request.
What is EFR? And does it mean that for standard edition, all
the tags fucntion remains the same except that it only allow 1
request of such tag at 1 time?

"What is EFR? And does it mean that for standard edition, all
the tags
fucntion remains the same except that it only allow 1 request
of such
tag at 1 time?"
For the effected functionality. This does not apply to all
Standard
Functions, just new Standard Functions that previously where
Enterprise
only such as gateways. Standard not has gateways, but only
one at a
time. I believe the same applies to some of the advanced PDF
functionality and similar features.

What is difference btw project Assignment, Resource Assignment and task Assignment.

Hi,
I am new project accounting Module .
what is difference btw project Assignment, Resource Assignment and task Assignment.

Project Assignment, Resource Assignment refers to the resource management part and Task assignment is basically the work assignment to the resource.
An assignment/requirement is created in PJR for create demand for the resource requirement of the project and when the resource is aligned he can be assigned to the task in the work plan.
Refers to the top down approach in this case.
Additionally a resource can be assigned to the work plan and a assignment can be created to get the resource allocated to the project.
Refers to the bottom up approach in this case

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

Key differences in OBI Apps Spend Procurement and Spend Classification

Hi,
Can someone please explain the key differences in OBI Apps Spend Procurement and Spend Classification version 7.9.6.2 vs. version 7.9.6.3?
Regards
Vanaja

There doesnt seem to be much diferences in terms of functionality or features. If you check the release notes..there are a few differences in the 7963 release related to bugs or packaging:
If this is helpful or correct, please mark the response as correct or helpful.
Here are some of the sections from the release notes:
Section 1.3.28, "Currency Conversion Not Done in Purchase Agreement for Oracle Procurement and Spend Analytics"
*1.3.32 'Days Payables Outstanding' and 'AP Turnover' Columns Are Missing*This issue applies to only those Oracle BI Applications customers who have implemented Procurement and Spend Analytics without implementing Financial Analytics.
*1.3.43 Oracle EBS 12.1.3 - Contract Lifecycle Management Impact on Oracle BI Applications Release 7.9.6.3*This issue applies to only those Oracle BI Applications customers who have implemented Procurement and Spend Analytics for E-Business Suite (EBS) 12.1.3 along with Feature Pack for Oracle Contract Lifecycle Management (CLM) for Public Sector. CLM Feature Pack is deployed as an add-on to Oracle EBS 12.1.3 for delivering an integrated acquisition management solution for federal government procurement.
CLM functionality has introduced changes to the Oracle EBS data model that affects data extraction and loading for Oracle Procurement and Spend Analytics. Customers with Oracle EBS 12.1.3 and the CLM feature pack must apply additional filters to exclude CLM records and to ensure that it does not interfere with V7.9.6.3 Procurement and Spend Analytics functionality.
Workaround
No work-around is available for this issue.
*1.3.56 EXPENSE_INVOICE_POSTED_DT Not Pulled From AP_CHECKS_ALL.CHECK_DATE for Oracle E-Business Suite*This issue affects Oracle Procurement and Spend Analytics. The measure 'Expense Reimbursement Cycle Time' as shipped with this release does not work in the subject area Employee Expenses – Overview. The measure uses the column EXPENSE_INVOICE_POSTED_DT_WID in the fact table W_EXPENSE_F fact, but this column is sourced from AP_EXPENSE_REPORT_HEADERS_ALL.EXPENSE_LAST_STATUS_DATE during ETL.
Workaround
This issue is addressed by Oracle E-Business Suite patch 10038359.

Difference btw OBI and BO

Similar Messages

Maybe you are looking for