Logistics and CO-PA
what is the difference between logistic extraction and CO-PA extraction with an example plz?
Edited by: merugu arun on Feb 27, 2008 9:48 AM
Hi,
BW Extraction
we have two types of extractions 1) Application specific 2)cross application
under applicatin specific -->we have customer genenrated and business content extractions
under customer generated means LIS, CO-PA, FI-SL(i.e no ready made data source in business content so we have to generate datasource)
Business content means there is ready made business content datasource so we can use it
LIS,LO --> when ever we go for extracting logistics informatin
CO-PA--> for financial info
LO extraction works based on Update Tables where as FI extraction works based on Timestamp table.
For updating the extraction of transactional data from the different logistics applications (MM, PP, SD and so on), the technology for collective updates (V3 updates) is used (until PI 2003.1). This means that the data is collected in the R/3 update tables before the transfer to the interface: the data is retrieved there by means of a periodic update process that needs to be started in order to transfer delta records to the the BW system delta queue.During this V3 collective run (that you can start and schedule from LBWE for each application component), the data is transferred to the BW delta queue (that you can see from RSA7or LBWQ transactions, from which they are retrieved by means of (delta) requests from the BW system.
COPA
Basically COPA- Profitability Analysis enables you to evaluate market segments, which can be classified according to products, customers, orders or any combination of these, or strategic business units, such as sales organizations or business areas, with respect to your company's profit or contribution margin.
The aim of COPA system is to provide your sales, marketing, product management and corporate planning departments with information to support internal accounting and decision-making.
Thanks,
JituK
Similar Messages
-
What are logistics and setup tables?
Hi,
What are logistics and setup tables?? How are these two related?
Regards,
SnehHi,
Logistics is the management of the flow of goods, information and other resources, including energy and people, between the point of origin and the point of consumption in order to meet the requirements of consumers (frequently, and originally, military organizations). Logistics involves the integration of information, transportation, inventory, warehousing, material-handling, and packaging, and occasionally security. Logistics is a channel of the supply chain which adds the value of time and place utility.
setup tables- are used to full the data for logistic applications.setup table are used for initialization and full loads.As there will be large number of data for logistic application first it will be fetched into setup tables then from there it will be used for initialization and full loads.
Regards,
Ravi -
Inbound logistics and Outbound logistics
Can anyone
1).list what all processes come under Inbound logistics and Outbound logistics
2).what is Backorder processing in Inbound logistics and its implications in the business
-Pallu1).list what all processes come under Inbound logistics and Outbound logistics
Config:
go to SPRO-MM-purchasing-Confirmation-setup confirmation control
here select the 10 and check the check box Create inb delivery
then select the line and click on the confirmation seq and make GR relevant, MRP relevant and GR assign (all three box checked)
Process Flow: -
1. ME21N - In PO, Confirmation Tab, select the confirmation control key as "Shipping Notification" or "Inbound Delivery"
2. VL31N - Create Inbound Delivery w.r.t. PO
3. MIGO - Goods Receipt > Inbound Delivery
Outbound:
Create the sale order delivery using VL01N
post goods issue -
Limited Logistics and Finance User details differentiation
Hi All,
The following detail has given at the time of requesting the License for one of my customer.
Professional User - 4
Limited CRM User - 1
Limited Logistics - 4
Limited Finance - 3
I have downloaded the license from SAP Portal in which i have got 11 - Professional, 1- CRM Sales, and 1- CRM Service.
How do we differentiate the Limited Logistics and Finance from the Professional Users?
Kindly clarify the same.
Regards,
Vikram ReddyHi Challa
Due to backward compatibility, SAP is still issuing Professional licenses for the limited licenses at this time. This will be changed in the 8.8 release due end of this year/beginning of next year. It will only therefore affect your customer when the new license manager is installed with the new version. In the interim the limited licenses will function as full professional licenses and cannot be differentiated at this time.
Kind regards
Peter Juby -
Third Party logistics and scenario
Hello all,
I am working on WM and would like to know more about third party processing. i would like to know the WM scenarios in which third party
logistics is used. is there any specific examples for third party logistics. Pl. advise in detail.
Thanks,
MaxxHi,
The meaning of Third party process in SAP is that you fulfill the demand of your customer by ordering the goods from your vendor and arranging the shipment from your vendor directly to your customer.
Since in this process your goods won't received in your WH, there's no point in speaking about WM scenario of third party processing.
Did you think of this third party process:
http://help.sap.com/saphelp_47x200/helpdata/en/dd/560287545a11d1a7020000e829fd11/frameset.htm
Csaba -
BO software logistics and landscape recomendations
Hello Experts,
We are implementing a BI solution (BW + BOBJ) and in the process of defining our client strategy we know that its sufficient to have a two system landscape for our bw server. Software logistics in BW is just like any other ABAP server, we set up TMS. Customizing & development is performed in BW dev and the use the TMS to transfer customizing and repository objects to BW prod. It should be noted that BW provides a means for mapping source system dependent object to the target (production) system.
Nothing new so far; but what happens with BOBJ BI?.
To start with, we supposed that a two system landscape was a good design but what we are know facing is regarding with how to move objects from dev to prod.
Take for example a Dashboard which was several dozens of QAWS connectios which URLs contains "hard coded" the development system name. When this dashboard is manually imported to the CMC in production the dashboard document is just pointing to the original system, namely, development system. Whit universes something similar is happening.
Please advice or refer to documentation where "Software lifecycle management" and "software logistics" for BOBJ BI and the above scenario is addressed.
Does CTS+ would do the trick?
Does BI 4.x has enhancements in this area?
please advice
thank youDear Anbu,
long time ago since I did the initial configuration.
When I remember right, there was an additional parameter in one of the *ini files on the Trex Server, but when I searched I was not able to find any additional parameter - so I guess there is none.
One thing that I remember is, that we had to use the IP-adress on the BO server configuration instead the server name, as otherwiese the BO server was not able to reach the BWA (but his might be due to our internal configuration).
Regards,
Andreas -
Hi,
Does anyone knows where to find Best Practice documentation on this area?
Thanks,
RoseHello Rose,
Please check <a href="http://help.sap.com/bp_biv270/html/bw.htm">this</a> for preconfigured best practices scenarios on PLM and logistics.
regards,
Sumit -
Extraction from logistics and different ecc tables
Hi
I want to get the data from 2lis_11_vahdr and 2lis_11_vaitm and also from tables of too1,tvakt,vbkd,knvI,VBKD,KONP.So
Please let me know how many datasources I have to create and on what basis I have to make join...or how we can make relations. or is there any alternative to do.
How to club the tables
How to get the data from all these to dso and infocube.
Thanks
SajithHi,
Have you received your technical specs?
if yes then please read them and find the required data sources.
Number of data sources is not the main important. But we need to get all fields into bw side(targets) as per your needs.
First find the existing data sources based on your tables - too1,tvakt,vbkd,knvI,VBKD,KONP.
After that cors check what fields you want as per needs and later do the test at RSA3 for standard or cusotm data sources.
Late implement bw data flow at bw side.
T001 - is company code table. so you can use comp code master data sources to load data into bw side.
TVAK - its sales doc type table. so you can explore LO Data sources which name starts with 2LIS_11*
About tables and relations - please check with ABAP TEeam or functional team. You my get more help about them.
Thanks -
What is the best way to find and apply the samples in the sap library
I am a fresh man in the process of learning sap .
Mainly aim at the MM and SD model .
They all say that the best way to accomplish the task is to follow the sap on-line help.
because i don`t know the struts of the library , so to find what i need in the library becomes impossible for me as the library includes a lot of files .
so please some one help me to direct the struts of the library and teach me the way how to find what i want ?
thanksHi,
This forum is for BPX. Post Solution related quries in SAP Solution Forums.
You can access MM and SD help at:
http://help.sap.com/erp2005_ehp_02/helpdata/en/80/ea89395eb58c4f9d0c3e837cf0909d/frameset.htm under Logistics
or http://help.sap.com/ -> SAP ERP -> Choose Release (for example SAP enhancement package 2 for SAP ERP 6.0) -> SAP ERP Central Compoennt (MM and SD under Logistics)
From Materials Management Link you can navigate further to Purchasing, Inventory Management etc. From Sales and Distribution you can naviate further: Sales, Billing etc.
For example to see help regarding Purchase Orders:
You would first expand Logistics and choose Materials Management in Help Link for ERP Central Component. Here, choose Purchasing Node which will take you Purchasing Help screen -> Click and Purchase Orders Node and Expand the same for more information regarding Purchase Orders.
You should be comfortable with SAP help link.
Regards,
Naveen.
Search the forum with keywords before posting the query. -
How to create a new transaction and add it to Area Menu
Hi.
I have to create a report and run the report using the Tcode and Tcode has to be added in the Area Menu at the initial screen.
Please tell me how can i do that.
Thank you in advanceYou can add additional menu transaction in the SAP main menu without affecting the original SAP default area menu S000.
For example, you have created a transaction code called ( z123 - ABC Own Report ) and you want to insert it under Logistics. The specific user will be able to access ABC Own Report by clicking Logistics -> ABC Own Report.
Steps :-
Goto Transaction SE43 - Area Menu
Click the copy button. Copy from S000 to ZXXX
After copying, click Change (area menu ZXXX)
Double click on Logistics and add in your transaction code in the AreaMenu.
Remembers to Activate it.
Next Goto Transaction SU01 - Maintain users
Type in the user name and click the Defaults button
Type in the area menu (ZXXX) in the Start Menu field.
Click Save
The user will be able to see the additional transaction on the next logon.
The CUA area menus are converted to tree navigation in Release 4.6A. The menu contents are automatically copied into a new data structure in Upgrade to Release 4.6A or higher. You can edit Area Menus with a new maintenance interface (Area Menu maintenance transaction: SE43 ).
Reporting Tree Integration - Only transactions could previously be put in Area Menus. From Release 4.6A you can also put all the types of reports which are in reporting trees, in Area Menus. The system automatically assigns a transaction code to call the report from the menu. If you have already put the report in another Area Menu, no new transaction code is generated, the unique transaction code already assigned is used.
You can create Area Menus from complete reporting trees with the migration transaction RTTREE_MIGRATION . The report transaction codes are generated automatically.
Reporting trees can only be displayed. They cannot be maintained. To modify the contents of reporting trees, you must convert them with the migration transaction. You can then modify the contents with the Area Menu maintenance. -
Exchange rate differences between GR and IR
Hi Gurus,
i have a problem about a exchange rate differences beetween GR and IR. Customizing setting is done based on this logic (transaction OMRW, ERD setting = blank).
For example: Goods Receipt amount is $100 and the posting is made with exchange rate 0,8. When busy with MIRO the user change manually exchange rate from 0,8 to 1,0. Moreover, the user change item amount from $100 to $150.
When the user simulate the posting in MIRO, transaction KDM is not activated (used).
Is to be underline that if item amount is not change but it remains untouched, transaction KDM is used correctly.
The system is:
SAP ECC 6.0
Software component: SAP_APPL
Release: 600
Level: 0016
Highest support package: SAPKH60016
Short description of software component: Logistics and Accounting
Have you any ideas about the reason of this malfunction?
Many thanks already in advance.
StefanoHi Gurus,
i have a problem about a exchange rate differences beetween GR and IR. Customizing setting is done based on this logic (transaction OMRW, ERD setting = blank).
For example: Goods Receipt amount is $100 and the posting is made with exchange rate 0,8. When busy with MIRO the user change manually exchange rate from 0,8 to 1,0. Moreover, the user change item amount from $100 to $150.
When the user simulate the posting in MIRO, transaction KDM is not activated (used).
Is to be underline that if item amount is not change but it remains untouched, transaction KDM is used correctly.
The system is:
SAP ECC 6.0
Software component: SAP_APPL
Release: 600
Level: 0016
Highest support package: SAPKH60016
Short description of software component: Logistics and Accounting
Have you any ideas about the reason of this malfunction?
Many thanks already in advance.
Stefano -
T.c FF7B: planning levels for Logistics
Hi All,
With reference to the Report FF7B and the CM data from Logistics,
I've defined the planning levels for logistics and the others steps under the CASH MANAGEMENT menù of SPRO.
But the report FF7A doesn't prodide me the logistic data... are there other customizing steps out of the CASH MANAGEMENT menù of SPRO.
ThanksHi,
If you have done the config as mentioned by Kalyan, i.e. define planning groups, assign/link them to planning levels and assign the appropriate planning level in customer/vendor master data either you run FF7B (for liquidity forecast) or even you can run FF7A, but need to tick the check box for liquidity forecast.
thanks,
Kumar -
HR context structural auths and unrelated personnel IDs
Hi,
we are working on HR SAP 4.7 SAP R/3 Enterprise with these patch levels:
COMPONENT Rel Liv. Supp.Pack. Descr.
SAP_BASIS 620 0038 SAPKB62038 SAP Basis Component
SAP_ABA 620 0038 SAPKA62038 Cross-Application Component
SAP_APPL 470 0020 SAPKH47020 Logistics and Accounting
SAP_HR 470 0028 SAPKE47028 Human Resources
EA-HR 200 0009 SAPKGPHB09 SAP R/3 Enterprise HR Extension
We are using only context structural authorizations (P_ORGINCON) with these switches:
ADAYS 15 HR: tolerance time for authorization check
APPRO 0 HR: Test procedures
DFCON 4 HR: Default Position (Context)
INCON 1 HR: Master Data (Context)
NNCON 0 HR:Customer-Specific Authorization Check (Context)
NNNNN 0 HR: Customer-specific authorization check
ORGIN 0 HR: Master data
ORGPD 4 HR: Structural authorization check
ORGXX 0 HR: Master data - Extended check
PERNR 1 HR: Master data - Personnel number check
XXCON 0 HR: Master Data - Enhanced Check (Context)
Everything works fine except for personnel IDs not linked to OM.
If we use PA40 to assigne an "unrelated object" (personnel IDs) to the OM structure, the
action works correctly.
We are not able to assign a unrelated personnel IDs to OM using PPOM.
Even if we have assigned the value 4 to both DFCON and ORGPD, we have to create a large
structural autorization with maintain flag active (the same as ALL in OOSP) and assign it to
the user in order to see the button "unrelated object" in PPOM.
In other words: it seems that unrelated personnel IDs need structural authorizations in order
to be assigned in OM.
Any idea ?
Is this a bug ?
Thanks
Andrea CavalleriThere are many ways of doing this depends which one you like....
1. Create a custom Function Module which will perform end to end extraction of desired Objects. There is no need to pass on some inputs for evaluation path. Just while creating structural, keep everything blank except for the last column to put your custom FM. This is a technique to control Structural using FM only.
2. In a structural use two lines...one might be with standard FM, other one should pick specific objects which you don't want user to have access. Ensure to check exclude beside that line. The Intention is to remove undesired objects from populating in OOSB.
3. Implement a BADI which will be executed after RHBAUS* programs are run, whose objective should be to identify these CIDs and remove them from T77UU table or INDX or from OOSB.
Please do not confuse P_ORGINCON with structural authorization. The integration of PA and structural authorization is to provide different level of access to set of objects pulled by structural auth.
There can be plenty other ways to do it.....HR Security is a playground where multiple games can be played at a time -
XI and R/3 Installation on One System
Hi,
I am new To XI and I want to install XI and R/3 in My Local System. Can i install both in one system (OS)? If yes, what is the minimum requirement for this?
If any one have did this, please help me.
Thanks,
SridharHi Sridhar,
Download this Doc and Fallow...
http://help.sap.com/bp_scmv150/documentation/SCM50_system_reqs.doc
Fallow the below documentation...
System Requirements for
SAP Best Practices for SCM 5.0 Scenarios
Use
The objective of this document is to help system administrators to prepare an SAP SCM system for the installation of one or more SAP Best Practices scenarios and to ensure the system setup meets the requirements for the installation.
This document does not provide information on how to set up the entire SAP SCM system, itself, but provides you with useful additional information and troubleshooting tips.
System Landscape
To install one or more of the SAP Best Practices for SCM scenarios from this CD, you should refer to the system landscape described below and compare it with your own existing system landscape as an installation prerequisite.
Please note that the support package levels indicate the minimum support package level your system landscape should have. If higher support packages exist, we recommend that you install the highest available support package.
To install and use any SAP Best Practices scenario, you must have installed an SAP R/3 and an SAP SCM system.
SCM 5.0: Complete Version
SAP SCM 5.0 contains the following business application components on one system platform:
SAP APO 5.0
SAP EM 5.0
SAP ICH 5.0
The following table provides an overview of the software component details of the SAP SCM system:
Software Component Release Level Highest Support Package Short description of Software Component
SAP_BASIS 700 0007 SAPKB70007 SAP Basis Component
SAP_ABA 700 0007 SAPKA70007 Cross-Application Component
ST-PI 2005_1_700 0001 SAPKITLQI1 SAP Solution Tools Plug-In
PI_BASIS 2005_1_700 0007 SAPKIPYI77 Basis Plug-In (PI_BASIS) 2005_1_700
SAP_BW 700 0007 SAPKW70007 SAP NetWeaver BI 7.0
SAP_AP 700 0004 SAPKNA7004 SAP Application Platform 7.00
LCAPPS 2005_700 0002 SAPKIBHD02 LCAPPS 2005_700 : Add-On Installation
EA-IPPE 400 0003 SAPKGPID03 SAP iPPE (EA-IPPE) 400
SCM 500 0004 SAPKY50004 Supply Chain Management 5.0
SCM_BASIS 500 0004 SAPK-50004INSCMBASIS SCM Basis 5.0
QIE 200 0004 SAPK-20004INQIE Quality Inspection Engine 2.00
BI_CONT 702 0002 SAPKIBIHP2 Business Intelligence Content
Optimization Server Version:
Identifier Version
CTM01 5.0_REL SP04, 356375
DPS01 5.0_REL SP04, 356375
CS01 5.0_REL SP04, 356375
SEQ01 5.0_REL SP04, 356375
SNP01 5.0_REL SP04, 356375
VSR01 5.0_REL SP04, 356375
Live Cache SP05 (LCA50.05, LC 7.6.00.22)
LiveCache version: KERNEL 7.6.00 Build 022-123-119-055
DBM server version: DBMServer 7.6.00 Build 022-123-119-055
Operating system: SunOS
LCA version: Module 50 Build 05
SAP APO GUI
We recommend that you install the SAP APO specific SAPGUI add-on, which is required for certain business transactions.
SAP ECC System
SAP ECC Enterprise with Extension Set 1 (for the SAP Best Practices scenario Fulfillment Visibility we used an SAP R/3 Enterprise system with Extension Set 2)
Software Component Release Level Highest Support Package Short description of Software Component
SAP_ABA 700 0007 SAPKA70007 Cross-Application Component
SAP_BASIS 700 0007 SAPKB70007 SAP Basis Component
ST-PI 2005_1_700 0001 SAPKITLQI1 SAP Solution Tools Plug-In
PI_BASIS 2005_1_700 0007 SAPKIPYJ77 PI_BASIS 2005_1_700
SAP_AP 700 0004 SAPKNA7004 SAP Application Platform
SAP_APPL 600 0004 SAPKH60004 Logistics and Accounting
EA-IPPE 400 0004 SAPKGPID04 SAP iPPE
EA-APPL 600 0004 SAPKGPAD04 SAP R/3 Enterprise Add-On PLM, SCM, Financials
FINBASIS 600 0004 SAPK-60004INFINBASIS Fin. Basis
BP-ERP05 600V2 0000 SAP Best Practices All-in-One based on ERP 2005 (ECC 600)
SAP XI System
If you want to install the SAP Best Practices scenario Supplier Managed Inventory, Release Processing, Responsive Replenishment, Contract Manufacturing Procurement & Supply Network Inventory, Kanban-based Replenishment, you also need to implement an SAP XI system.
Software Component / PI Content Release Level Highest Support Package Short description of Software Component / PI Content
SAP_BASIS 700 0007 SAPKB70007 SAP Basis Component
Content for SAP BASIS 700 0007 XI content for SAP BASIS 7.0
Content for SCM 500 0004 XI content for SCM 5.0
Content for SCM BASIS 500 0004 XI content for SCM BASIS 5.0
Non-ABAP components, such as the Integration Builder and the Integration Repository, must also be installed and have the respective support package levels.
For uploading the content in the XI System, refer to SAP note 836200.
Checklist after the System Setup
SCM Menu
After you have installed the SCM System, you may have to set up the menu that you want to use.
To do this, access transaction SE38 and run the report /SCMB/SM_VERS.
Choose Full Version and then, choose Execute.
Check Planning Version 000
In your SAP SCM system, use the following path:
SAP Menu  Advanced Planning and Optimization  Master Data  Planning Version Management  Model and Version Management
Make sure that the planning version 000 Active Version is available.
If this planning version is not available, this means that the LiveCache has not been initialized. Proceed with the LiveCache initialization before you start with the installation of any SAP Best Practices scenario.
Check that PSE services have been activated
Use transaction strust in your SCM system. All services should have a green light. If it is red, activate all of them. There is no need to reboot the system afterwards.
OPTIMIZER
1. Checking that the Optimizer has been installed
Transaction SM59  RFC Destination  OPTSERVER_CTM01  Test Connection
If the connection cannot be established, this may be due to the following reasons:
the Optimizer has not been installed
an error occurred during the installation of the Optimizer
2. Checking that the Optimizer SPs have been installed
Open transaction /SAPAPO/OPT09. The Optimizer Support Packages should be identical to the Support Packages of the SCM system.
Ensuring that the APO relevant PI Settings are activated in SAP ECC
You have to make sure that the business transaction events are active in the SAP ECC system. Only if these events are active for the SAP APO integration, will changes to the transaction data be transferred from the SAP ECC system to the SAP APO system. This setting should have already been performed; this is just a reminder in order to avoid possible problems later on. Use the following procedure:
In your SAP ECC system, open the transaction BF11.
Confirm the message The table is cross client.
On the Change View: Application Indicator: Overview screen, check that the applications ND-APO, PI-EM and NDI are active, i.e. selected. If they are inactive, select the check box to activate them.
Choose Save and go back.
Web Communication Layer (WCL)
Ensure that the WCL is installed correctly: Usually the WCL should be connected to the client 001 of the SCM system. Use transaction /saptrx/wcl_search in the SCM system to open the WCL. If a logon pop-up appears, then the WCL is set up correctly. If the message WCL is not installed... appears, the respective set up settings should be checked and corrected, if necessary.
Additional Information
For additional information on issues such as architecture, sizing, platforms, and upgrades, refer to following page on the Service Marketplace:
alias /SCM  SCM Technology
For information on system monitoring, system administration, volume testing etc., check SAP note 572003. You can also refer to the Service Marketplace, using the alias /SCM  SCM Technology  Table of Contents  Solution Management  Best Practices for mySAP SCM Solution Management.
Thanks,
Satya Kumar.. -
Study material on ALE and IDOCS
Hi
If anyone has some study material on ALE and IDOCS ,if you can please send it across to me , it would be very helpful to me .
My mail id is : [email protected]
Thanks in advance
Ankit1. What is ALE?
Application Link Enabling (ALE) is a set of business processes and tools that allow applications on different computer systems to be linked. This can be done between different SAP systems as well as between SAP and non-SAP systems.
In a single SAP system different applications are integrated via a single database (e.g. finance, sales, production, human resources). However, many companies do not have just one integrated system but a distributed environment with different applications running on different systems. To run the whole business in such an environment the distributed applications have to be linked. This can be done through Application Link Enabling (ALE).
ALE provides distributed business processes that can be used to link the applications on different platforms. There are some ALE business processes delivered in the standard SAP system. Furthermore, there are tools that can be used to change the existing ALE business processes or to implement new distributed business processes.
Besides the business processes there are special ALE services that are required to set up and control a distributed environment. These services include a distribution model, business object synchronization and tools for monitoring or error handling.
ALE is a major part of SAP's Business Framework Architecture. Besides the basis middleware, that provides the communication between components, and the interfaces (BAPIs), ALE business processes and ALE services enable the cooperation of the single components within the framework. That makes ALE the glue of the Business Framework.
2. What are the benefits of ALE?
With ALE companies get the opportunity to improve business performance and to solve organizational or technical issues.
Through distribution you can decentralize your business, enabling local units to operate independently from each other. This flexibility enables the local units to return better business results than in a centralized environment. They have the necessary flexibility to optimize business processes in different organizational units and can ensure that information systems can handle the speed of change in rapidly expanding markets. Distribution allows a high level of freedom, provided that this level of freedom has been clearly defined.
On the other hand, some companies, that already have a distributed organization with different computer systems in the local units, have the opportunity to link their units through ALE business processes. This enables them for example to provide a 'one face to the customer' approach. Another area that can benefit through ALE are virtual organizations (partnerships between independent companies, joint ventures and mergers and acquisitions).
Of course, in many cases an integrated solution based on a single system is not possible at all. Some applications used by a company can not run on the same computer system. This includes legacy systems or complementary software. It may also be possible that a company uses different SAP industry solutions or specific country solutions, which do not run on the same SAP System. If these applications run on different systems they can not be linked by a central database but have to use a special integration mechanism like ALE. In this way ALE also links SAP Core Systems to other SAP components like CRM, Business Information Warehouse or APO.
Besides the benefits of having an improved flexibility in setting up the whole business processes, ALE may also reduce costs, in particular costs of upgrading. If the whole business is run on one integrated system you have to upgrade the whole system, even if only one part of your company (e.g. human resources) requires an update. So the entire company is affected by the upgrade project and all users have to be trained for the new release. Within a distributed environment with release independent interfaces, like those provided by ALE, you can focus the upgrade project on that part of the company that has to be upgraded. The other parts of the company are not involved and need no training. This can save a lot of money. Furthermore, existing investments are protected.
Another cost factor for distribution might be communication costs. For an overseas connection it can be more expensive to provide online access to one central system (T1) than to connect distributed systems to each other (64K line).
There might also be some technical reasons for distributed systems. If some parts of the business have special requirements for security of data access (e.g. human resources), this can be set up much safer on a standalone system, which is, however, linked to other parts of the company through distributed business processes. A similar example is high availability. High availability is usually required by the operations part of the company (production, logistics) but not by other areas (e.g. financials, human resources). In a distributed environment high availability can be set up for specific parts of the environment instead of for the whole business. This can also reduce costs.
In a distributed environment you can not decrease the overall workload of the systems but you can separate the user workloads on different systems. Through this scalability you can improve performance. Another benefit of distributed systems is that if a technical failure occurs on one system, all other systems continue to operate. Only a small part of the business is disrupted by the error. On one central system such an error would disrupt the entire business.
3. When should ALE be used?
Besides the benefits of ALE there are also reasons not to distribute:
The functional scope in a distributed environment is restricted. Not all functionality that is available in an integrated SAP system can be used with distributed systems in the standard yet. Although ALE provides tools to create new ALE business processes or to enhance existing business processes, this does involve additional expenditure.
Each company needs some organizational standards and data harmonization. In a distributed environment less standards are required than on a single integrated system. However, in a distributed environment the maintenance of the standards and the data harmonization is more difficult than on a single system.
The administration of decentralized systems is more expensive. Support and service costs for hardware and software in decentralized systems are higher than these costs in a single centralized system.
ALE should be used in a company if the benefits of ALE for this company outweigh the reasons against distribution. For this you always need to carry out a company specific investigation, in which you also should consider the culture of the company. ALE is good for some companies but not for all.
4. What is the relationship between ALE and Middleware?
Electronic Data Interchange (EDI) is a term for the transfer of business messages between two systems. There are many such messages, the most common of these include a customer sending a purchase order message to a vendor, or a vendor sending an invoice message to a customer. Classic EDI is mainly restricted on the exchange of transactional data, no master data or configuration data. In most cases, EDI replaces the transfer of paper copies of these documents. Via the messages ALE business processes can be implemented between business partners. The EDI messages also use the ALE services.
For the communication between different types of systems special EDI messages are defined as standards for inter company communication. There are many standards for these messages - in the United States, the ANSI X.12 standard is the most prevalent, in Europe, the UN/EDIFACT standard is used. For sending EDI messages the information has to be converted into an EDI standard. With SAP systems this is done by EDI subsystems. This conversion is the only difference between EDI messages and other messages used in ALE business processes. The processing of these messages on the SAP System is the same as the processing of other ALE messages.
5. Which ALE business processes are available?
IDoc Types - Message Types
ALE business processes are integrated business processes that run across distributed systems. This can be two different SAP systems, links between SAP and non-SAP systems, SAP and Web-servers (Internet Application Components) or SAP and desktop applications. The links between the systems may be loosely (asynchronous) or tightly (synchronous) coupled. These business processes are release independent and can run between different release levels of the systems.
Many SAP applications offer ALE distribution processes. The following list gives some examples:
Master data replication (IDoc Types - Message Types - Master Data)
- Material
- Customer
- Vendor
- General Ledger accounts
- Bill of materials
Accounting (IDoc Types - Message Types -Accounting Business Processes)
- Links to logistic systems
- Distributed financial accounting
- Distributed cost center accounting
- Distributed special ledger
- Profitability analysis
- Distributed profit center accounting
- Consolidation
- Treasury
Logistics(IDoc Types - Message Types - Logistics Business Processes)
- Reallocation of materials
- Distribution of sales and shipping
- Product data management
- Purchasing contracts
- Sales and operations planning
- Warehouse management
- Links to warehouse control systems
- Links to production optimization systems
- Links to transport planning systems
Information systems (IDoc Types - Message Types - Logistics Business Processes)
- SAP Business Information Warehouse (BW)
- Exchange of data between information systems
- Web reporting
Human resources (IDoc Types - Message Types - HR Business Processes)
- Human resources as a single component
- Payroll results
- Travel expense accounting
- Links to time collecting systems
However, these standard solutions may not fit 100% for a company. There may be differentiation in the business process or a required distributed business process is not supported in the standard. If this happens, ALE provides tools that can be used to adapt a standard ALE business process or to create a new distributed business process.
6. Which ALE services are available and what do they do?
To integrate distributed systems you need more than a communication infrastructure and interfaces. Some additional services are required that are provided by ALE:
Business process harmonization:
Within system overlapping business processes multiple functions running on multiple systems are involved and connected through multiple interfaces. The processes are combinations of functions (sub-processes) running on the single systems.
(Example: A business process for customer order management involves functions in sales, manufacturing, warehouse management, finance, and so on. It is possible that the sales functions are carried out on another system than the manufacturing, the warehouse management or the accounting. Furthermore, some information exchange with the customer, a supplier or a bank may be involved in the process.)
ALE helps to coordinate the whole business process by defining it within a global model. In this model the business rules for the distribution are defined. Via the model the sub-processes get to know which part of the overall process they have to do themselves and when they have to pass the process over to another system. Through this the whole business process gets harmonized.
Receiver determination:
For distributed business processes a sub-process on one application (client) has to start another sub-process on another application (server). It is important that the new sub-process is started on the right server. Which server is the right one can not be defined by technical values, it depends on the business content of the process.
(Example: A sales system forwards customer orders to two different production systems. To which system a special sales order is forwarded depends on the entries in the sales order (this may depend, for instance, on the ordered material or on the customer). One sales order may also be split into two or more different orders that may be forwarded to different production systems.)
To notify the client which system is the receiver of the communication (server), ALE uses a distribution model. From this model the applications get the information about the right server. There are special ALE BAPIs and function modules available for this. The receiver determination makes sure that the information is sent to the right places.
Business object synchronization (semantic synchronization):
If business processes run across distributed systems, they have to share some data to be harmonized. This is data like business information data, master data or customizing data. If this data is changed in any of the distributed systems, other systems have to be informed about the change. There has to be some kind of subscription of the data.
ALE provides a special service for this data synchronization. This service can detect data changes and distribute the information to those systems that need to know about the change. This service also defines which data is shared. You can determine which fields of a data object shall be common and which fields may vary locally.
Consistency checks:
For a business process running across two distributed applications there has to be some harmonization of the sub-processes in the single applications. For making sure that the sub processes are harmonized there are special ALE consistency check tools. These tools help to find and repair inconsistencies. By this it can be ensured that the whole ALE business process works in the right way.
Monitoring:
For the monitoring of distributed processes it is not enough to monitor all activities on the single systems. The overall business process has to be monitored. The ALE monitoring services provide detailed information about the communication process, the sub-process on the other systems and its results. Database links are created between the business objects in question on the client and the server. This is especially important for loosely coupled applications with asynchronous links. In this case the server can not give return values back to the client directly so that the ALE monitoring is the only channel for feedback.
Error handling:
Another problem with asynchronous communication is error handling. If an error occurs on the server the calling process on the client may have finished already. So the server can not return the error message to the client. A special error handling process required. This process is one of the ALE services. It uses workflow functionality to identify the error and to start the required error handling.
7. Synchronous vs. asynchronous links?
When distributed applications are linked by ALE business processes, the question often arises as to how tight the link should be. Synchronous and asynchronous links have both advantages and disadvantages.
Synchronous links have the advantage that the sub-process on the server can return values to the sub-process on the client that has started the link. Problems with synchronous links occur if the communication line or the server is temporarily not available. If this happens, the sub-process on the client can not be finished (otherwise there would be data inconsistencies).
(Example: There is a logistics system and a financial system. Every stock movement in logistics has to be posted in the general ledger of the financial system. If the link between logistics and finance is synchronous, no stock movement can be recorded in the logistics system if the communication line to the financial system is down.)
Because of this, synchronous links are usually used if the client only wants to get some data from the server and the sub-processes on the server do not have to write any data to the database.
With asynchronous links the sub-process on the client can be finished even if the communication line or the server is not available. In this case the message is stored in the database and the communication can be done later. The disadvantage of asynchronous links is that the sub-process on the server can not return information to the calling sub-process on the client. A special way for sending information back to the client is required. In addition, a special error handling mechanism is required to handle errors on the receiving side.
Asynchronous links are used if a synchronous link is not applicable. For the problems with sending return information to the client and with error handling there is some support from the ALE services.
8. Which kind of interfaces do ALE business processes use?
ALE business processes are integrated processes across distributed systems, requiring interfaces between the systems. These interfaces have to be stable to enable the communication between different releases and to reduce the impact of release changes within the distributed environment.
In SAP R/3 release 3.0 and 3.1 ALE uses IDocs as interfaces. An IDocs is a data container for transferring messages asynchronously. They are release independent. Since SAP Release 3.1G BAPIs are a new type of object oriented, stable interfaces that can be called synchronously or asynchronously. Asynchronous BAPIs use IDocs as data containers. ALE business processes can use BAPIs as well. In the future new ALE business processes will use BAPIs as interfaces. But the existing IDocs will still be supported. In time, BAPIs will be created with similar functionality to existing IDoc interfaces.
9. Why does SAP uses ALE instead of database replication or distributed databases?
Database replication is another possibility for doing business object synchronization. However, there are some major disadvantages with database replication. At the moment database replication is database dependent and release dependent within one database. This makes database replication impossible for the use with non-SAP systems and even for the replication between SAP Systems you have to make sure that all systems are running on the same SAP release and the same database release of a single database vendor. Furthermore, with database replication you cannot do things like field conversions or version changes. ALE does not have these shortcomings because it offers application driven data replication independent of the underlying database.
Another technology, distributed databases, is no alternative for ALE at the moment, either. There are some good results of distributed databases available, but the performance is far from sufficient for using it with larger applications like SAP.
10. What is the relationship between ALE and middleware?
For distributed business processes many different services are required. Most of these services are offered by SAP. For some of these services you can also use products that are provided by SAP's complementary software partners or by other companies:
The communication service for doing the pure communication is usually done via Remote Function Call (RFC). RFC is provided by SAP for most platforms both for synchronous and asynchronous communication. There are other messaging systems for the communication service available as well, like IBM's MQSeries. However, the communication between SAP and the messaging system is still done via RFC.
For the serialization of asynchronous communication the RFC provides little functionality at the moment. The serialization has to be checked by the application. ALE offers some support to do these checks. The serialization of the RFC communication will be improved in the future. Serialization services are provided by some of the existing messaging systems, but even they can not guaranty a 100% serialization of the communication, since they use RFC for the connection to SAP.
The monitoring and error handling of the communication is done via services provided by the RFC and ALE. If messaging systems are used for the communication they also offer some monitoring and error handling functionality.
If a non-SAP system is involved in the ALE business scenario and this system does not understand SAP's BAPI or IDoc interfaces, the data has to be mapped to any interface structure that this system offers. For this mapping SAP does not provide a service but it certifies mapping tools from software partners. These tools are called ALE translator. The most known product in this area is probably Mercator from TSI International Software. The same kind of mapping can also be done by 'EDI converters'.
Another type of middleware products offer process ware. This is mainly a combination of the communication service, the mapping service and a set of rules for the mapping. Some ALE translator can be used for this as well.
Receiver determination is one of the ALE services (see above). Parts of this service can also be provided by some of the messaging systems, but you cannot use these systems without using ALE receiver determination.
For the other ALE services like application monitoring, application error handling, semantic synchronization and business process harmonization, there are no middleware products available as a replacement of ALE.
ALE is open for the use of middleware products for the distribution, but in most cases the additional middleware is not necessary. In a communication between different SAP systems usually the use of additional middleware makes no sense at all. For the communication between SAP and non-SAP systems there might be some benefits, especially if the middleware is used at the company already. The only middleware tool that is really required if the non-SAP system does not understand BAPIs or IDocs is an ALE translator.
Check different sites for more information.
Regards
Maybe you are looking for
-
Problem with variables in formulas when using CrystalReportViewer
Post Author: Aksu CA Forum: Formula Hi! I have a problem with variables in Crystal Reports formulas, when using CrystalDecisions.Windows.Forms.CrystalReportViewer class from VS2005-project. ReportViewer always gives error:*************Crystal Report
-
Can I use an Apple Cinema Display as a second monitor for my iMac?
I have a new 24" intel iMac and was wondering if I could use my old 20" Apple Cinema Display (aluminum) as a dual display. What cables do I need?
-
Hi guys. I am in a developing team for an app, so I would have a pasword to get a free download of this app. But where and when do I have to type it in while download?
-
Problem of setting version entry in �depend� file of package
I am working on creating a package pkg1 that depend on pkg2, so I added a �depend� config file in the prototype. From the man page of depend, I should add the following entries in the depend file: type pkg name (arch)version (arch)version So I added
-
Deleting the first word in a string
hi! i'm learning regex and with this code i would like to 1) print a string (from "Hi my name is SandraPandra. do not print this") 2) remove the first word and print the new, shorter string 3) remove the first word in the new, shorter string and prin