About ALE and BOM Positions

Hi Experts,
we're trying to make ALE Transfer of BOM Modifications.
In the source system, I change a BOM with another Position Typ (from R to L) and Quantity/Unit (from L to DM3).
But I got an error in the Target system (IDoc Status 51) :
(Resulting) item category cannot be changed
Any idea?
Regards,
David

Hi,
check whether someone is currently editing the BOM and therefore the IDoc cannot be processed. Also you could check SM12 for any system locks regarding the BOM.
Regards,
Kai
Edited by: Kai Lerch-Baier on Jun 15, 2009 11:26 AM

Similar Messages

About ale and idocs

hi all
i was asked in an interview when we will go for creation of an idoc.pls provide me some real time situaution when we use these idocs

HI,
IAM GIVING A DOCUMENT WHICH HELPS YOU TO UNDERSTAND THE PROCESS OF IDOCS BEING SENT BETWEEN TWO SYSTEMS AND IT COULD HELP YOU IF U GO FOR INTERVIEWS.
Application Linking and Enabling (ALE)
In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
For our purpose we have two clients
namely Client 100 and Client 200.
System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
Distribution of Material Master Data Between two Systems
1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
To do this follow the following steps
Execute SALE Transaction Code
On The Screen Click on Sending and Receiving Systems.
Then Click on Logical Systems.
Then Click Defining Logical Systems.
Click New Entries Button
(E.g. (LG100 sending system)
(LG200 receiving system))
Enter two logical system names and their description.
Save
Comeback to SALE Transaction Code screen.
2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
LG100 assign to client 100
LG200 assign to client 200
To do this, do the following.
Click Assigning Client to Logical System.
Ignore the message that comes up on the screen.
Select client 100
Click details button on the toolbar icon or press F2.
In the logical system box, enter LG100.
Click on the save Icon
Click the back button.
Now select client 200.
Click details icon or press f2.
In logical Systems box, enter LG200.
Save
Back.
Comeback to SALE Transaction Code screen.
3) Maintain RFC Destination: (TR.CODE:SM59)
(Note: Do Not Create This Step)
Click Create Button on the Screen
On the Screen Maintain RFC Destination i.e LG200.
Enter LG200 in RFC destination box.
Connection type is 3
Give a description for the RFC destination.
Maintain Technical Settings on Details on Technical Settings tab
Target Host as : SAPKDC (NOTE: Save it as a Host Name)
Maintain Logon Details on Logon/Security tab.
Language: EN.
User:      MMUSER200 (This is the logon for dist.)
Client :      200
Password:      MM1234.
Save.
Click on create to do the above process for Client 200 in
The client 200 system.
4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
Execute Maintain distribution model directly for
creating the model.
Click on change mode button on App tool bar of the Screen.
Create Model View pushbutton on App tool bar of the Screen.
A pop screen will appear in which you specify
Short text as Distribution for MM Data.
Enter Technical Name as LGMODEL.
Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG100.
Receiver as      LG200.
Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG200.
Receiver as      LG100.
SAVE.
On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Logical System as LG200.
Then execute the screen.
Click back.
Again On the same screen goto Menubar and select EDIT.
Again select Model View and then select Distribute.
****LOGIN to client 200.
Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Model View as LGMODEL
And Specify the Logical System as LG100.
Then execute the screen.
Click back.
*******Switch back to client 100 Session.
5) Create Material using MM03 Tr.Code.
Enter the material name as LGMATERIAL
Industry sector as      Mechanical Engineering
Material Type as           Finished Products.
And then Click on Data Pushbutton on the App tool bar.
Select views.
In the select views box for materials check basic data 1 AND 2.
Click enter icon.
In the next screen that you get
Give the text of the material as NEW MATERIAL.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
In the description area language (E) and material description.
Click Save.
Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
6) Execute BD10 to transfer the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client100).
Then a Screen will be displayed in which it shows that
1 Master Idoc Generated .. Enter
1 Communication Idoc Generated..Enter.
*******LOGIN to Client 200.
7) Execute BD11 to get the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client200).
8) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
If not follow these steps.
9) Execute Tr.code WE19( for rectification of errors in client200).
Specify the Existing Idoc Number and Executes it .
A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
10) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
Now the Material is correctly displayed in Client 200.
11) Monitoring of IDOCS.
Transaction Codes:
IDOC Display of Status: WE 05.
IDOC Date and Time:   WE07.

Question about Button and TextBox positions

Hello everybody,
I just started using Borland Together 6.1 extended with Java and I want to design a UserForm (an Application), especially a Online Bank terminal, where u can input and output different data. My problem is that when I add buttons and textboxes from the toolbox menu, I cannot put then on the place I want, I'm restricted to some positions (center, right, left, west, east and so on). My question is how can I create my elements on the position I want, how can I resize them. Could someone tell me some specific functions, which I should use.
Thankx

You should try to find a LayoutManager that suits you. If you can't find one, you can set the Layout to null, then use absolute positioning.
setLayout(null);
yourComponent.setLocation(50, 50);
yourComponent.setSize(40, 20);You need to set both the location and size of components when the layout is null.

About ale partner frofile and modal distribution

hi sir\medam
my broblem about ale, achualy i done data send and recive through BD10 AND BD11. but not use partner profile nd modal distribution. my problem has how use partner profile nd modal distribution.
plz say step by step processing. and how send data from outbond nd inbond probond processind.
thansk in advance
regard
mukesh goyal

sending side:
1) we20 partner profile here u select the logical system
in outbound parameters create the parameters(message type ,port, idoc type)
2) bd64 create the model view goto environment-->generate partner profiles execute
here u will gat the message modeview wa created
3)goto bd10 send the material
4)we02 check the idoc status
5) goto se38 run rbdmoind program check idoc status
Receiving side:
we19 check the idoc statusand run bd11
If helpful give the points

Best avenue to file complaints about bill and have them resolved

I have been a customer since before 2005 and went with Ntelos in November, I called the night I was at Ntelos to ask Verizon what my contract buy outs were and I was given the prices. The representative tried to offer me whatever promotions she could offer (there wasn't many) and I declined service (there she should have took the initiative to ask about disconnecting). Since my bf opted to keep his number his phone disconnected automatically. I was told my Verizon phone would cycle off within 24 - 48 hours by the Ntelos rep. That was not the case so I called verizon to ensure my phone would disconnect and they told it would at the end of the billing cycle (december 20) which makes sense. I understand I would be responsible for the November - December. Anyways, December 20th rolls around and mind you I've called already to ensure it will take place and it doesn't. I phone in and come to find out the person who took my orders didn't complete the disconnection and now I have to wait until January 20th for it to cycle off and I can finally pay my bill! Well get this in my November - December bill they've charged me $51 for Monthly access (I have a work discount) and $49.99 for insurance and smartphone access for 12/21 - 1/20 and won't refund my $51 as they say that I called out on the phone. I turned the phone on and had voicemails that I think I checked around the time period that they are mentioning (1 day) and that data was used (1 day) I had no outbound calls after December 11th my birthday. Because there are no comments in my account (that I specifically asked them to make) my phone should have been disconnected when I had called in the first of December... really!?! The phone should have been turned off regardless and it was one day out of 30 seriously? I mean the phone has been turned off this whole time and literally only checked to make sure Verizon did their job. I CAN'T HELP IT YOU DON'T KNOW HOW TO DO YOUR JOB, I PUT THE EFFORT IN MULTIPLE TIMES TO LET YOU KNOW MY PHONE NEEDED TO BE DISCONNECTED YOU SHOULD HAVE KEPT RECORD OF IT!!! What really heats me up is that I was told a supervisor would give me a call back after they got out of a meeting and I have not rec'd a call back yet. VERIZON Reps/Supervisors your customers are the reason why you have get a paycheck, I suggest you start treating them a little better. You can't seriously tell me giving me back my $51 for service I DID NOT USE (except according to you for one day you can't even give me details about?) is really going to hurt your pockets. I've been jerked around by your reps for the last 2 months as one told me my contracts were up in January and I shouldn't' be charged for disconnection fees at all, she credited me those termination fees but they later got rejected (after she said her supervisor approved while I was on hold) and NO ONE HAD THE COURTESY TO NOTIFY ME!
I've worked in customer service before and I'll be first to tell you that your reps are not trained very well and you have horrible ethic! You should not charge your customers for an error that was your fault; especially since it was your reps that I asked specifically to note my account and didn't (this isn't my first rodeo with you all, it should be standard procedure to give your reps time to comment before throwing them into another phone call). I'm not doing this for my health here, that $51 could buy diapers and baby food for my daughter and you are crazy if you think I'm going to let it slip through my fingers to line your pockets. I will keep escalating it until you do something about it and I don't care that you already gave me an inconvenience credit I deserve that and my $51 so don't try to justify it that way! This has been way more than an inconvenience, so don't worry I'll inconvenience you as well!
>> Edited to comply with the Verizon Wireless Terms of Service <<
Message was edited by: Verizon Moderator

With my new provider I am only using the chat function to settle anything with them so I can save the conversations I've had with them (not that I've had any issues thus far). It should be standard procedure for them to comment your account while they are on the phone with you before hanging up. I should have been annoying and asked them to read back their comments (hindsight ugh!). I'm sorry that you are having to deal with this as well, just know you are not the only one receiving horrible customer service. I'll share with you what I wrote on their Facebook page. They really should take some accountability for their actions and have better follow up on resolving issues (or train their representatives better). I can't stand having to talk to another person time and time again explaining the same thing i just explained to 3 people before them.
Almost immediately, I received some attention after posting this:
Dear Verizon,
I am appalled, especially after reading your credo, that you are refusing to credit back money that is owed to me because your representatives didn't take the necessary time that they should have to comment (after I specifically asked) in my account after I diligently called in multiple times to ensure that my disconnection took place when it was scheduled to and was told that it would (an ongoing issue since the beginning of December). Come to find out that the representatives I spoke with prior to December 20th didn't do their jobs correctly by not entering the disconnection orders in. "Verizon Credo- a set of principles that describes our culture of integrity, respect, performance excellence and accountability. The Credo is a blueprint that directs us to live up to the highest standards possible when serving our customers, shareowners, communities and each other." Let me school you on something here because it appears that you just put that mission statement up on your website 'cause it sounds good, you certainly do not follow through! Accountability: Noun - the quality or state of being accountable; especially an obligation or willingness to accept responsibility or to account for one's actions (i.e. public officials lacking accountability). It doesn't matter that you cannot find any proof in my statements it doesn't change the fact that it happened and I am not a liar. I seriously wouldn't exhaust this must effort had I been lying. I'll take this a step further and reference your statement "we focus outward on the customer, not inward. We make it easy for customers to do business with us, by listening, anticipating and responding to their needs." First of all, when I made my initial call to you all asking what my contract buyout prices were and your rep tried to offer me promotions (or lack there of) to keep me as a customer and I declined she should have "anticipated" my need for disconnection. I shouldn't have had to jump through so many hoops to get my service disconnected from you all and pay my final bill. It's not my fault that your representatives weren't trained well enough to correctly put through disconnection orders. Based on my interactions with your customer service I could see where people would disconnect their services regularly!!!!! You are not making it easy for me to severe ties with you and conduct BUSINESS and you are not responding to my NEEDS. I think you forget that I could be a potential customer in the future. If it's one thing I learned from my Communications Degree is that negative feedback will reach more consumers vs. positive feedback of a company and how they handle their business. I have 1,000 plus facebook friends and twitter followers so I'm pretty sure my negative experience could reach quite a few people! You say you have integrity? How is it moral uprightness to charge me for a whole month of service (regardless if the phone was turned on once) for a billing period that shouldn't have existed if your customer service reps did their job correctly? I suggest that you all take a good look at the way you are treating your current customers because we are the reason you get a paycheck! You should make your customers a priority especially if they've been with you for 10 + years regardless if they are disconnecting service or not! How about following through, taking ACCOUNTABILITY and having that supervisor representative call me back from my phone conversation last night like I am a priority (how every customer should be treated) and helping me get the money that I am owed, regardless if the phone had been turned on for a short period (your rep couldn't even tell me what numbers I supposedly called - exactly the phone has been off since December 20th if not before unless turned on to confirm disconnection)! Oh but let me guess did you all forget to put that in my account comments as well? Probably like there is no mention of the formal complaint I filed against some of your representatives that there was supposedly no ticket number for. I thought I was going to regret leaving Verizon for another provider but it turns out that I only wish I would have left sooner and actually gone to a authorized dealer/ Verizon Store to process my disconnection because your customer service line is a joke!

PPT on ALE and IDOC

Hi,
Any body can send me the ppt on ale and idoc .
great thanks in advance .
Regarding
kumar

Hi Anil,
The best way is to read the book ALE,IDOC... by Aravind nagpal,
Just read this you will get a clear idea about these.
The ppts will cover only the basic part,but i find this book as very useful when you do the coding or checking for soem settings.
Regards,
Sasi

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
Ankit

1. 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

ALE and Idocs configuration

Hi Gurus,
Please tell me the ALE and Idocs configuration settings
Thnaks in advance

Hi,
Please refer to the details mentioned in the hyper-links beow.
You will get the details how to go about it.
To see the IDOC & status check it in WE02/WE05
You will get step by step process.
ABAP Development
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.geocities.com/xplosion78/customised_ALE_IDOC_BY_SACHIN_DABHADE.zip
http://help.sap.com/saphelp_45b/helpdata/en/35/b0ea5187a62488e10000009b38f9b7/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/c4/6bc368fef411d28d0900104b56737d/frameset.htm
ABAP Development
Follow below steps to create custom IDOC.
1.Create segments through transaction WE31.
2.Create IDoc Type through transaction WE30 by attaching created segments.
3.Message type through transaction WE81.
4.Link Idoc and message type in WE82 transaction.
Check the transaction WEDI for ALE settings
Check these links for more details on IDoc's:
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
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
Hope this will help.
Regards,
Priyanka.

How to create items and BOMs using web services

Hi All,
I need to create, change and read Items and BOMs through web services (using SOA Gateway, right). I found this one here: "Process Item (convenience wrapper version)" or "Process Item" within
Internal Name     EGO_ITEM_PUB
Type               PL/SQL
Product          Advanced Product Catalog
Status          Active
Business Entity     Catalog Item
Right now, I don't know how to use it. If somebody has a simple example to create a single item, this would be perfect! Which one would be the right one to read detailed information about an existing item?
The second object I need to maintain (create, change and read) is BOM. Which API can I use here?
btw: I use EBS 12.1.1 on windows.
Many thanks,
Konrad

Hi!
Thanks for your quick answer but unfortunately, I must admit that I'm an absolute beginner with Oracle and EBS and so things like:
Enable trace and generate the tkprof file or open the form using forms builder to get the name of the API used in thta screen.or
Please check e-trm site for your question do not help me to much :-(
Any other advice?
Konrad
Api's in EBS
Re: Api's in EBS
http://sairamgoudmalla.blogspot.com/2009/05/script-to-find-oracle-apis-for-any.html
API
Fixed Asset API
List of API
Re: List of APIs
Regard
Helios

About NLS_DATE_FORMAT and NLS_LANG.

Hi
According to Oracle9 i Recovery Manager Userâs Guide Before invoking RMAN, set the NLS_DATE_FORMAT and NLS_LANG environment variables. These variables determine the format used for the time parameters in RMAN commands such as RESTORE, RECOVER, and REPORT.
I ahve already configured ramn. The V$NLS_PARAMETERS are
For Target database
PARAMETER               VALUE
NLS_LANGUAGE               AMERICAN
NLS_TERRITORY               AMERICA
NLS_CURRENCY               $
NLS_ISO_CURRENCY          AMERICA
NLS_NUMERIC_CHARACTERS          .,
NLS_CALENDAR               GREGORIAN
NLS_DATE_FORMAT               DD-MON-YY
NLS_DATE_LANGUAGE          AMERICAN
NLS_CHARACTERSET          WE8ISO8859P1
NLS_SORT               BINARY
NLS_TIME_FORMAT               HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT          DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT          HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT          DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY          $
NLS_NCHAR_CHARACTERSET          AL16UTF16
NLS_COMP               BINARY
NLS_LENGTH_SEMANTICS          BYTE
NLS_NCHAR_CONV_EXCP          FALSE
For Catalog database
PARAMETER               VALUE
NLS_LANGUAGE               AMERICAN
NLS_TERRITORY               AMERICA
NLS_CURRENCY               $
NLS_ISO_CURRENCY          AMERICA
NLS_NUMERIC_CHARACTERS          .,
NLS_CALENDAR               GREGORIAN
NLS_DATE_FORMAT               DD-MON-YY
NLS_DATE_LANGUAGE          AMERICAN
NLS_CHARACTERSET          US7ASCII
NLS_SORT               BINARY
NLS_TIME_FORMAT               HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT          DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT          HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT          DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY          $
NLS_NCHAR_CHARACTERSET          AL16UTF16
NLS_COMP               BINARY
NLS_LENGTH_SEMANTICS          BYTE
NLS_NCHAR_CONV_EXCP          FALSE
If i want to restore my database with in the specific time. Will the above setup cause any problem.
Please i need urget advice about NLS_DATE_FORMAT and NLS_LANG.
Arif.

In control file replace:
MATUR_DT POSITION(78:85) DATE 'YYYYMMDD',
OR
On WinDoze, edit registry and set NLS_DATE_FORMAT to YYYYMMDD
On *nix set NLS_DATE_FORMAT environment variable to YYYYMMDD

Data Fir IDOC ALE and EDI

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

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

Regarding ALE and IDOC

Iam an Infant as far as ABAP is concerned. I have some basic ABAP knowlegde and i know SAP scripts and smart forms. But no idea about data transfer techniques. I have one silly question :
Is it possible to learn ALE and IDOC on a home PC. I mean can i practice them at home. I dont have any network access so i wanted to know can i practice at home on my personal system.
Can my home PC behave as both sender and receiver system. If it is possible pls let me know how to go about it guys.
I know this is a very very silly question, but as i said, iam still learning to crawl in ABAP. It will take some time before i walk.
Thank You.

Hi guys,
I must thank every one of you for sending such quick and helpful responses. I bought the book "ALE, EDI and IDOC" from Aravind Nagpal and its a great book for beginner as well as for an expert. I have started practising ALE my PC by logging into 2 clients and it is working fine. I was able to send and receive the IDOC.
Thank you again.
This is a great forum,
Cheers,
Mahesh.
Edited by: Mahesh Kumar on Jan 21, 2009 3:32 PM

Regarding ALE and EDI

can any one explain me what is ALE and EDI and what is difference between two?
plese explain me with example..
thanks in advance.
with regards,
kps moorthy.

The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
This is an article posted on the site below, You Can easily check it out.
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci983331,00.html
1) ALE = Application Link Enable: Initially developed for SAP as an abstract layer to extract master and transactional data to be sent ellectronically to other SAP systems. These days is also being used to send data no non-SAP systems. ALE is not a protocol or anything like that, it's just abstract layer composed by a set of applications which are capable of extracting aplication data on a 1-time basis or periodically, by selection criteria or incrementally by deltas.
2) In contrast, EDI = Electronic data interface, this is a comunication protocol not designed by SAP but it´s an industry standard. Of course most SAP software supports EDI, but EDI it's no software but the specification of the protocol in itself.
ALE(Application Link Enabling) refers to the losely coupled systems whereas the EDI speaks about the Electronic Document Exchange. We need to enable ALE in order to use the EDI feature. ALE builds the bridge and EDI is the means by which the data moves in and out of the SAP system just like vehicles moving over the bridge. IDOC(Intermediate Documents) are the data containers which will be moving in and out of SAP carrying data.
Thus summarising we need to establish ALE between the systems in order to use EDI between them. In case we need to use EDI between SAP and some other target system then we need a EDI subsystem which understands these IDOCs and converts into the format understood by the target system.
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.
Check this link for more details.
http://sapabap.iespana.es/sapabap/sap/faq/ale_idocs_bapi.htm
ALE/Idoc information
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
Check these step-by-step links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287
https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985
EDI information
http://www.erpgenie.com/sapedi/index.htm
Please refer to site http://edifactory.de which will give you good documentation about EDI.
Check these links for EDI
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sapgenie.com/sapedi/edi_sap_training.htm
www.sap-img.com/basis/ difference-between-edi-and-idoc.htm
help.sap.com/saphelp_nw04/helpdata/ en/35/26b592afab52b9e10000009b38f974/content.htm
help.sap.com/saphelp_nw04/helpdata/ en/35/26b594afab52b9e10000009b38f974/content.htm
http://www.onestopsap.com/interview-Question/edi/
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi2.jhtml
http://www.sapgenie.com/sapgenie/docs/i830v3020.xls
http://help.sap.com/saphelp_46c/helpdata/en/0b/2a655d507d11d18ee90000e8366fc2/frameset.htm
http://www.hud.gov/offices/hsg/comp/edi/0306sec1.cfm
http://www.sapgenie.com/sapedi/index.htm
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.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sap-img.com/abap/ale-bapi.htm
http://www.sap-img.com/basis/difference-between-edi-and-idoc.htm
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
http://www.sapgenie.com/ale/whitepaper.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
regards,
srinivas
*reward for useful answers*</b>

Transaction code to learn for sample codes about trees and containers

trnasaction code to learn for sample codes about trees and containers

hi check this....,
REPORT Ztree_TEST_PGM.
Type-pools : fibs,stree.
data : t_node type snodetext.
data : node_tab like t_node occurs 0 with header line.
clear : node_tab, node_tab[].
node_tab-type = 'T'.
node_tab-name = 'Earth'.
node_tab-tlevel = '01'.
node_tab-nlength = '5'.
node_tab-color = '4'.
node_tab-text = 'Hello'.
node_tab-tlength ='5'.
node_tab-tcolor = 3.
append node_tab.
clear node_tab.
node_tab-type = 'P'.
node_tab-name = 'Europe'.
node_tab-tlevel = '02'.
node_tab-nlength = '6'.
node_tab-color = '1'.
node_tab-text = 'Hello'.
node_tab-tlength ='5'.
node_tab-tcolor = 4.
append node_tab.
clear node_tab.
node_tab-type = 'P'.
node_tab-name = 'Germany'.
node_tab-tlevel = '03'.
node_tab-nlength = '7'.
node_tab-color = '4'.
node_tab-text = 'Hello'.
node_tab-tlength ='5'.
node_tab-tcolor = 4.
append node_tab.
clear node_tab.
node_tab-type = 'P'.
node_tab-name = 'Berlin'.
node_tab-tlevel = '04'.
node_tab-nlength = '6'.
node_tab-color = '4'.
node_tab-text = 'Hello'.
node_tab-tlength ='5'.
node_tab-tcolor = 3.
append node_tab.
clear node_tab.
node_tab-type = 'P'.
node_tab-name = 'Asia'.
node_tab-tlevel = '02'.
node_tab-nlength = '4'.
node_tab-color = '1'.
node_tab-text = 'Hello'.
node_tab-tlength ='5'.
node_tab-tcolor = 3.
append node_tab.
clear node_tab.
node_tab-type = 'P'.
node_tab-name = 'India'.
node_tab-tlevel = '03-'.
node_tab-nlength = '5'.
node_tab-color = '1'.
node_tab-text = 'Hello'.
node_tab-tlength ='5'.
node_tab-tcolor = 3.
append node_tab.
clear node_tab.
node_tab-type = 'P'.
node_tab-name = 'Bombay'.
node_tab-tlevel = '04-'.
node_tab-nlength = '6'.
node_tab-color = '1'.
node_tab-text = 'Hello'.
node_tab-tlength ='5'.
node_tab-tcolor = 3.
append node_tab.
clear node_tab.
CALL FUNCTION 'RS_TREE_CONSTRUCT'
TABLES
    NODETAB                  = node_tab .
DATA: type_mapping TYPE stree_ctl_type_mapping_tab.
DATA: wa_type TYPE stree_ctl_type_mapping.
CLEAR: type_mapping[].
    wa_type-type = 'A'.
    wa_type-icon = '@BL@'.
    APPEND wa_type TO type_mapping.
CALL FUNCTION 'RS_TREE_LIST_DISPLAY'
EXPORTING
   USE_CONTROL                     = 'L'.
A list of other function modules that can also be used to construct tree reports:
SEUT,                            Hierarchy framework
RS_TREE_ADD_NODE                 Insert nodes
RS_TREE_AUTOMATIC_REFRESH
RS_TREE_COMPRESS                 Hide subtree(s)
RS_TREE_CONSTRUCT                Construct new hierarchy or insert subtree
RS_TREE_CONTROL_PREPARE
RS_TREE_CREATE                   Create hierarchy
RS_TREE_DELETE_NODE              Delete node with associated sub-tree
RS_TREE_EXPAND                   Expand subtree
RS_TREE_GET_CURRENT_LAYOUT       Get layout information for displayed hierarchy
RS_TREE_GET_CURRENT_NODE         Get node at which cursor is positioned
RS_TREE_GET_CURRENT_ROOT         Get current root node
RS_TREE_GET_CURRENT_TREE         Get structure information for displayed hierarchy
RS_TREE_GET_INPUT                Get entires from input fields
RS_TREE_GET_MARKED_NODES         Get selected nodes
RS_TREE_GET_MODIFICATION_LOG     Get change log for hierarchy
RS_TREE_GET_NODE                 Get nodes for specified ID
RS_TREE_GET_NODE_BY_NAME         Get node for specified node name
RS_TREE_GET_PREDECESSOR          Get preceding node
RS_TREE_GET_SEARCHSTRING         Get last search strinng
RS_TREE_LIST                     Simulate hierarchy or subtree display
RS_TREE_LIST_DISPLAY             Display hierarchy
RS_TREE_LIST_DISPLAY             Display hierarchy
RS_TREE_MODIFY_NODE
RS_TREE_MOVE                     Reassign node with subtree
RS_TREE_POP                      Get hierarchy from the stack and restore
RS_TREE_PUSH                     Place hierarchy on the stack
RS_TREE_RESET_LOCK               Deselect node
RS_TREE_SET_CURRENT_LAYOUT       Set layout with marked cursor position
RS_TREE_SET_CURRENT_TREE         Set other hierarchy
RS_TREE_SET_LOCK                 Select node
RS_TREE_SET_NODE                 Change Nodes
RS_TREE_SET_SCROLL_POS           Position node at the beginning of the page
RS_TREE_SLEEP
RS_TREE_SORT_CHILDREN
regards,
venkat.

Multiple routing and BOM

Hai gurus,
1) My client manufacture whisky using process industry scenario.
2) They produce whisky in bottling unit using either Auto line 1 or Auto line 2( work center)
3) Also they select the BOM 1 or BOM 2( Old bottle or New Bottle) based on the availability.
4) So for selection of BOM i had created the production version using old and new bottle.
5) How to select the routing as it will be known only while converting planned orde to process order.
6) Actually i am selecting the BOM1 or BOM2(old or new bottle) based on the availability during partial conversion of
planned order to process order or by doing read pp master.
7) If that is case how to select the routing Auto line 1 or 2)while converting planned order to process order as it will known only on the begining of that day production.
waiting for the positive reply
regards,
sekar chand

Hai Kumar,
Thanks for you reply.
In Production Version we define the selection of BOM1 or BOM2( old or new bottle) based on the availability.
But the work center Auto line 1 may be used under BOM 1 and BOM2 based on the capacity or avialbility of the line
or Auto line 2 may be used under BOM 1 and BOM 2 based on the availabilty of the line.
It that is the case how to create Production version and select the same, for work center and BOM
waiting for the positive reply.
Regards,
sekar chand

About ALE and BOM Positions

Similar Messages

Maybe you are looking for