What is difference btw serial control uniqueness within inventory model

hi ,
what is difference btw serial control uniqueness within inventory model and item and with inventory .
and what is difference btw the serial number generation at item level and at organization level...
please help me ...
thanking....

1) When uniqueness is within inventory items, you cannot create 2 serial numbers for the same item. But you can have same serial# for 2 items.
In CTO scenario, sometimes this is a problem. So Oracle introduced the new option "within inventory model and item". In this case, Oracle generates a serial number by using the prefix defined at the Model level. This helps you maintain the uniqueness within all * numbers created for a given model.
2) If you choose generation at item level, you can specify the starting prefix/length for each item. When generation is at org levle, you need to specify it at the org
Hope this helps,
Sandeep Gandhi

Similar Messages

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

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

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

What's difference btw. Dreamweaver and photoshop

What is the difference between Dreamweaver CS4 and Photoshop
CS4? I am not sure which to purchase.

Dreamweaver is for creating web pages. Photoshop is for
editing creating
graphics. Fireworks is for creating graphics specifically for
use on the
web. The graphics would be used in Dreamweaver as you are
building the
page's HTML, and adding its interactivity.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"RaeKC" <[email protected]> wrote in message
news:gk7u8m$hjo$[email protected]..
> What is the difference between Dreamweaver CS4 and
Photoshop CS4? I am not
> sure which to purchase.

What is difference btw schema.core.xml and schema.user.xml in OVD

Hi
New to OVD, I'm looking at Oracle's OVD configuration properties Docoument
I'm confused with list of schema files on OVD especially difference between schema.core.xml and schema.user.xml
In the oracle document it mentioned as below.
Typically, the last file identified is schema.user.xml. Any and all changes to schema are applied to the schema.user.xml file to ensure standard files, such as schema.core.xml, remain unchanged between releases, but can also be virtually modified by having the changes in schema.user.xml override default-shipped schema in schema.core.xml.
If you are installing a manufacturer supplied schema (in DSML form), identify this file in the second to last file in the list of schema files. This will protect the distributed manufacturer file from modification while allowing local customization, which is then stored in schema.user.xml.
Based on above two paragaraphs i came to one understanding but i just want to hear from you what exactly its trying to say about those two files.
Not sure what exactly above mean can someone explain lettle in detail

Hi,
The LDAP schema used by OVD is shipped as several XML files such as schema.core.xml, schema.cosine.xml, schema.inetorperson.xml, schema.nis.xml etc. depending on in which RFC the attribute and object classes are defined.
All changes to these schemas (if any) are always applied to schema.user.xml, so this file contains all the custom attribute types & objetclasses.
Hope this clarifies a bit
Sylvain
When closing a thread as answered remember to mark the correct and helpful posts to make it easier for others to find them

Difference btw BOE and LC ?

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

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

Would you please summarize what the difference between tc and alv?

hi, experts,
would you please summarize what the difference between table control and alv base on the function and usage practice.
for example, as i know:
1.edit
tc: can edit in the same screen and save.
alv: pop up a sub screen to let user edit, so this is unconvenient.
2.functional button
alv: can have many functional button as default ,eg. sort, summary and so on
tc: developers must implements by himself.
3.color
alv: can have and change color
tc: cann't changed color
some client may required the data displayed in alv and edit in tc ,such as example BCALV_EDIT_02.
above are my idea, experts, would you give me some comments on my opinion and summarize what the difference between those two components? i should make it clear in order to consult the UI with my client.hunger for your advice, thanks!
Message was edited by:
liu shaochang

ALV Grid is basically used for display puropse. It is more user friendly. There are arious features ( such as coloring, sorting, saving to a local file, sedning by mail etc. ) These featurs make ALV Grid a very good option to display the data .
However , the table control is not only used to display data take from the database table, but also you can do operation such as deletion of data from database table, insertion of data into the database table and updation also. Yeah it has not got the various features whihc ALV has.
So table control and ALV Grid , if you are just using for display purpose, then ALV Grid is a better option due to its layout and attractive features. But if you want to do the database operations other than display, table control can be used.
As far as execution is concerned, I think ALV Grid is faster.
ALV grid control is faster when compared to Table control. But the comaprision is Negligible .
One of the major differences comes in taking of line items - ALV has an advantage over Table Control when it comes to update database from it.Table control only allows maximum of 999 records at a time where as this limitation is not there in ALV.
Also,a main feature of ALV Grid is that it contains a standard set of functions. These functions extend beyond the functions of a table control.
These two UI elements require different keyboard navigation, with ALV Grid being more user-friendly.
An application can display table data in ALV Grid or in a table control. In some applications you can choose between displaying and editing data in either ALV Grid or a table control. If a configurable button () appears in the right upper corner of the table, it is a table control.
Basically ALV is a way to display the output and Table Control is designed in screen painter through which you can get entries in Table Control, can delete some records etc for further processing and its not use only for Display.
ALV is Application List viewer:-
Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length.
In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output.
TABLE CONTROL:-
ABAP offers two mechanisms for displaying and using table data in a screen. These mechanisms are table controls and step loops. Table controls and step loops are types of screen tables you can add to a screen in the Screen Painter.

Difference btw J2ME and SAP MI

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

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

What is the difference btw Oracle bpm 10gr3 vs albpm 6.0.5 version

What is the difference btw Oracle bpm 10gr3 vs albpm 6.0.5 version
Are the build number common to them?

Projects built in ALBPM 6.0 can be used directly in Oracle BPM 10g, but the reverse is not true.
It's sometimes thought that Oracle BPM 10g was just a relabeling of the predecessor BEA product ALBPM. This is not the case.
In Studio, standards are better supported:
<li> By default, new processes now use horizontal swim-lanes. You can change the swim-lanes orientation individually for each process. You can define the default orientation for each project and for your Studio installation.
<li> It uses more sophisticated BPMN icons. BPMN is the new default process diagram theme. BPMN constructs now include Gateways (AND, OR (new in 10g), XOR, Multiple Instance (previously Split-N)). A new Timer event was added. Loop conditions for automatic activities and groups were added.
<li> Studio now supports Mac/OS 10.4 Tiger and Mac/OS 10.5 Leopard.
<li> Studio now supports Windows Vista.
<li> Studio now supports CVS and Subversion version control systems.
<li> The Studio UI incorporates Eclipse 3.3 improvements such as the following:
<li> New Minimize/Maximize behavior: When minizing view stacks in Studio, the view icons are placed on the nearest trim area. If a view is maximized, all other views are minimized, rather than hidden.
<li> Interactive tasks provide a new "previewable" property. The new Application Display Panel and Task Execution Panel of WorkSpace automatically start the execution of previewable tasks without locking the process instance. Enabled by default for Dashboards.
<li> New type of Activity: Time Activity. A process instance that arrives to this activity just sits idle until a timed event occurs.
<li> Option Process Notification Immediately on Termination Wait activities has been deprecated. Now both the Wait activity and the first activity in the interruption flow always execute in the same transaction.
<li> Although I'm not wild about it, there is an auto-layout feature re-arranges all visual elements of a process diagram automatically, minimizing superpositions and aligning the flow as much as possible. Only available for processes with horizontal lane orientation.
<li> New process property (Greedy Execution Mode) indicates the Process Execution Engine to collapse contiguous automatic tasks in a single transaction. This mode of execution provides better performance for some processes. Disabled by default.
<li> A new Process-Level debugger allows developers to introduce breakpoints and debug complete processes running in Studio. When the execution reaches a breakpoint, the Engine pauses and Studio's debugging view appears. You can inspect variables, add new breakpoints, resume and continue execution.
User Interface
<li> The Business Analyst and Business Architect profiles provide a simpler set of menu options and toolbars.
<li> New editor for BPM Object Presentations. It's easier to use, provides a WYSIWYG drag and drop interface, improved CSS support and a new Drag & Drop toolbar.
<li> You can now interrupt a running Simulation started with the Run to the End button.
<li> New BETWEEN operator added to Business Rules editor (on both Studio and WorkSpace). This operator works with Time and numeric types.
<li> The Documentation View now displays read-only documentation for the standard Fuego.* components.
<li> New on-line help book Oracle BPM Components Reference provides reference documentation for the standard Fuego.* components. Only available for the developer profile.
<li> This version introduces Project Dependency, which allows you to re-use components and role definitions from a common base project.
In the WorkSpace:
<li> WorkSpace has an edit mode which allows users to change and save the configuration and layout of panels.
<li> A new tabbed interface allows you to define multiple pages, each with its own set of panels. You can export the layout configuration to an XML file and re-import it on a different environment or as a different user. Administrators can define layouts for all users in a certain Role.
<li> You can export the data in the Worklist panel to a PDF or CSV
<li> You can see an OOTB chart representation of the distribution of items in the Worklist panel.
<li> WorkSpace includes the following new panels: Task Panel: Renders the execution of interactive tasks within the panel, instead of using the default modal dialogs. Dashboard Display Panel: Provides a way to display Dashboards within a Panel. View Chart Panel: Provides predefined graphical reports about process performance, work items distributions and workload. Application Panel: This panel contains an application (the execution of a Global Interactive). Applications can respond to work item selections or run independently.
<li> The user can now do re-assignment operations on multiple instances at once.
<li> The Business Rules editor shows additional auditing information, including who and when a rule was modified.
<li> WorkSpace now (optionally) stores session-specific information as client-side cookies. This allows load-balancing on a cluster environment without affecting the user experience.
Integration:
<li> New timeout property added to external resources of type HTTP Server. Use this setting to control timeouts on web service invocations.
<li> Authentication information added to external resources of type JMS (Java Messaging System)
<li> Processes exposed as Web Services can now provide a runProcess operation, which synchronously executes the complete process (from begin to end). Only meaningful on fully automated processes.
Enterprise:
<li> New Ant tasks to rebuild the Oracle BPM web applications for container-security.
<li> Configuration Wizard adds option Generic JNDI to the list of available LDAP servers. When using this option, you must provide a custom configuration file defining the mapping of object classes, attributes and filters. This new feature is also the new mechanism for integrating with AquaLogic Interaction 6.5, replacing the old Identity Service.
<li> Configuration Wizard can now be run without user interaction ("silent mode"). You specify all configuration values in an XML file.
<li> Oracle BPM client applications (including WorkSpace, PAPI-WS and custom PAPI apps) are now able to connect to multiple environments (BPM Directories) simultaneously.
<li> Added Sybase as a new provider for the Engine database and BPM Directory database.
<li> More information added for auditing of Business Rules, including who and when a rule was modified.
<li> Updated bundled JDBC drivers to their latest version.
<li> The Engine now logs warning messages when it detects rogue threads. A new preference allows the administrator to disable automatic re-starts when the Maximum Number of Rogue Component Executions is reached. In addition, in the case of an automatic re-start the Engine now logs a complete thread dump.
<li> Simplified procedures for deploying BPM WorkSpace on WebLogic Portal. BPM Process Administrator now generates the WorkSpace EAR file as a WLP library module.
<li> Authentication information added to external resources of type JMS (Java Messaging System).
Dan

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

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

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

What's the difference between defining a Thread within a class and....

Guys,
I am really confused when it comes to thread.
What's the difference between defining a Thread within a class and implementing a Thread in a class?
I just want to know about this. What is the difference between the two code classes?
public class A
public A()
public Start()
Thread th = new Thread():
th.start(this);
public class A extends Thread
public A()
*{*{code}*}*
*public Start()*
*run();*

My Googling show that the E/A may be a little newer but it appears that the E/A was not originally sold in the USA. The E/A appears to be sold in a Spanish speaking country.

What is the difference between Serial numbers and Batch management.

Hi Gurus,
Can anyone explain the difference between Serial Number and Batch Management in breif.
Regards
Ravi

Hi,
Serial number management and batch management are different functions that can be
used in conjunction with each other.
A batch represents a non-reproducible subset
of the total quantity of a material held in stock, which is managed separately from
other subsets of the same material.
For Example Different production lots
(for example, paints, wallpapers, pharmaceutical products), delivery lots or quality
grades of a material.
whereas a serial number is a number that you give to an individual item of material in addition
to the material number, in order to differentiate between this individual piece and all
other items of the material. The combination of material number and serial number
is unique. It is not necessary to use the batch management function to use serial
number management.
Regards
VIjay.

What is the difference btw Flux

I was reading the discussion titled "Is this the end of iWeb?" (9.25.11 - 1.2.12) and the web design software Flux and MacFlux was mentioned. I was wondering if anyone knew the difference btw the two. Why is one called "MacFlux"? Is it more "Mac-like"? Is the one called Flux more like a Microsoft product: ie, hard to do the most simple task, not user friendly, etc.?

Flux tries to combine code entry plus drag and drop. This means that you have to spend a lot of time learning how the application works rather than learning about HTML & CSS. I chose the latter because its quicker and allows you to build more efficent code.
Flux encourages the use of inline styles which contributes to slow loading pages.
Rage WebDesign is like similar editors in that you enter code in one window and preview in another. With Rage, both windows are viewable at once. You can also preview in any browser with one click.
The advantage it has for me over similar products is the way in which you can click an item in the preview window and the appropriate code is highlighted. This is a huge time saver. With some responsive designs I have the code for several pages in one HTML doc so finding individual items and their related code can be a difficult at times.
You should be able to download a trial here...
http://www.ragesw.com/products/webdesign.html
Taco is also really good and a lot cheaper. Fraisse is free.
You can start with one of the thousands of free styesheets available on the internet to get familiar with HTML. Then try making changes in the CSS to customize the page.
Changing fonts, colors etc in an existing styesheet is quite easy and just requires a bit of common sense. Actually creating and modifying layouts involves a basic understanding of the math involved in positioning elements. Once you get your head around this you can do whatever you want.
CSS is advancing rapidly and, in combination with HTML5, can produce stunning results.
It all comes down to personal choice. I tried out about a dozen apps before settling with Rage WebDesign. One man's meat is another man's poisong they say!

What's the difference btw JDK and SDK?

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

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

Difference btw idoc ale and edi

Hi all,
I'm a beginner in abap, can anyone send me the concepts of ALE, IDOC and EDI and the difference btw all the three.
Also do send some materials for the same.

Hi,
ALE (Application Linking and Enabling)
Ale Technology is SAPs technology to support distributed yet integrated processes across several SAP systems.
Distributed Process:
A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.
Need for Distributed Process:
Business in Different Geographical Locations.
Non availability of dedicated network.
Cultural and language differences in Geographical locations.
Running of Mission-critical Applications (Like Maintenance downtime etc.).
Separate up gradation of Modules.
Distributed SAP SYSTEM CHALLENGES
A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.
Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.
Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.
Receiving systems that can handle their own problems and not tie up the sending system.
Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.
A sound technology and methodology that can be used in all distribution scenarios.
SAP Distributed environment:
ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
Benefits of ALE:
Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocs definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch ALE Service).
IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
Basic integrity check: A basic integrity check is performed on the control record.
Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function modules output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).
IDOC:
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404]
[http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm]
[http://www.sappoint.com/presentation.html]
[http://www.allsaplinks.com/idoc_search.html]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://www.erpgenie.com/sapedi/idoc_abap.htm]
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
[Re: How to create IDOC;
Check below link. It will give the step by step procedure for IDOC creation.
[http://www.supinfo-projects.com/cn/2005/idocs_en/2/]
ALE/ IDOC
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.sappoint.com/abap/ale.pdf]
[http://www.sappoint.com/abap/ale2.pdf]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sappoint.com/abap.html]
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs]
go trough these links.
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.sappoint.com/abap/ale.pdf]
[http://www.sappoint.com/abap/ale2.pdf]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm]
[http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sappoint.com/abap.html]
[http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
[http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc]
[http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419]
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://www.allsaplinks.com/idoc_sample.html]
[http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm]
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
[http://www.allsaplinks.com/idoc_sample.html]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[www.sappoint.com]
--here u can find the ppts and basic seetings for ALE
[http://sappoint.com/presentation.html]
[www.sapgenie.com]
[http://www.sapgenie.com/ale/index.htm]
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
RFC:
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
[http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm]
check out the following link it might help you
[http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf]
EDI:
Electronic Data Interchange
Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
Refer
[http://www.erpgenie.com/sapedi/index.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
[https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
[http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
[http://www.erpgenie.com/sapedi/index.htm]
[http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
EDI FLOW :
Here is some thing which helps you and here the purchase order is taken as example too..
Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
What parts of the business cycle can be supported by EDI?
Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
How does EDI get started?
EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
What is the flow of EDI?
The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
check this.
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
[https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
[http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
[http://www.erpgenie.com/sapedi/index.htm]
[http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
[ALE / IDOC / RFC / EDI]
[SAP ABAP and EDI/ALE/IDOC]
[Re: IDOC/BAPI/ALE/EDI]
Regards,
Dhruv Shah

DIFFERENCE between Tabstrip control and tabstrin(with wizard)

difference between table control and table control wizard.
and what is all about custom control
give simple examples

Hi
Table Control
http://help.sap.com/saphelp_erp2005vp/helpdata/en/d1/802338454211d189710000e8322d00/frameset.htm
Table Control Wizard
http://help.sap.com/saphelp_erp2005vp/helpdata/en/d1/802338454211d189710000e8322d00/frameset.htm
Tab Strip
http://help.sap.com/saphelp_erp2005vp/helpdata/en/04/10f2469e0811d1b4700000e8a52bed/frameset.htm
Tab Strip wizard
http://help.sap.com/saphelp_erp2005vp/helpdata/en/04/10f2469e0811d1b4700000e8a52bed/frameset.htm
http://www.sapmaterial.com/tablecontrol_sap.html
Custom Controls
A custom control is an area on a screen. You create them in the Screen Painter, and, like all other screen objects, they have a unique name. You use custom controls to embed controls. A control is a software component on the presentation server, which can be either an ActiveX control or a JavaBean, depending on the SAPgui you are using. They allow you to perform tasks, such as editing texts, locally on the presentation server. The control is driven by the application logic, which still runs on the application server.
The SAP Control Framework
The controls on the presentation server and the ABAP application programs on the application server communicate using the Structure link SAP Control Framework. This is programmed in ABAP Objects, and contains a set of global classes that you can find in the Class Browser under Basis ® Frontend services. These classes encapsulate the communication between the application server and presentation server, which is implemented using Remote Function Call.
All application controls are encapsulated in a global class. You can find the SAP Basis controls in the Class Browser under Basis ® Frontend Services or Basis ® Component Integration. Programs that use controls on a screen work with the methods and events of the global classes that encapsulates them.
Container Controls
Before you can work with a custom control on a screen, you must assign a Structure link SAP Container Control to it. Container controls are instances of special global classes from the SAP Control Framework. The global class for custom controls is called CL_GUI_CUSTOM_CONTAINER. To link a custom control to a container control, pass the custom control name to the CONTAINER_NAME parameter of the container control constructor when you instantiate it.
As well as using custom containers, you can link controls to a screen using a SAP Docking Container. This is encapsulated in the global class CL_GUI_DOCKING_CONTAINER. The SAP Docking Container does not place the control within a screen. Instead, it attaches it to one of the four edges. You can nest containers. For example, you can use the SAP Splitter Container (classes CL_GUI_EASY_SPLITTER_CONTAINER or CL_GUI_SPLITTER_CONTAINER) within other containers. This allows you to split a custom control or docking control into more than one area, allowing you to embed more than one control.
One example,
program z.
Constants *
constants: c_me like trdir-cnam value 'VNDOVV',
c_myurl type scarr-url value
'http://www.brainbench.com/transcript.jsp?pid=147699',
c_width type i value 260,
c_height type i value 130.
Types *
types: begin of t_pgm,
year(4) type c,
name like trdir-name,
end of t_pgm,
begin of t_pgmkey,
id type i,
name like trdir-name,
end of t_pgmkey.
Data *
data: it_pgmkey type table of t_pgmkey.
Classes *
Definitions *
class screen_init definition create private.
public section.
class-methods init_screen returning value(this)
type ref to screen_init.
methods constructor.
private section.
class-data a_id type i.
data: splitter_h type ref to cl_gui_splitter_container,
splitter_v type ref to cl_gui_splitter_container,
picture type ref to cl_gui_picture,
tree type ref to cl_gui_simple_tree.
methods: fill_tree,
fill_picture.
endclass.
class screen_handler definition.
public section.
methods: constructor importing container
type ref to cl_gui_container,
handle_node_double_click
for event node_double_click
of cl_gui_simple_tree
importing node_key,
handle_picture_double_click
for event picture_dblclick
of cl_gui_picture.
private section.
data: html_viewer type ref to cl_gui_html_viewer,
editor type ref to cl_gui_textedit.
methods: fill_html,
fill_src importing programid type trdir-name.
endclass.
Implementations *
class screen_init implementation.
method init_screen.
data screen type ref to screen_init.
create object screen.
this = screen.
endmethod.
method constructor.
data: events type cntl_simple_events,
event like line of events,
event_handler type ref to screen_handler,
container_left type ref to cl_gui_container,
container_right type ref to cl_gui_container,
container_top type ref to cl_gui_container,
container_bottom type ref to cl_gui_container.
create object splitter_h
exporting
parent = cl_gui_container=>screen0
rows = 1
columns = 2.
call method splitter_h->set_border
exporting border = cl_gui_cfw=>false.
call method splitter_h->set_column_mode
exporting mode = splitter_h->mode_absolute.
call method splitter_h->set_column_width
exporting id = 1
width = c_width.
container_left = splitter_h->get_container( row = 1 column = 1 ).
container_right = splitter_h->get_container( row = 1 column = 2 ).
create object splitter_v
exporting
parent = container_left
rows = 2
columns = 1.
call method splitter_v->set_border
exporting border = cl_gui_cfw=>false.
call method splitter_v->set_row_mode
exporting mode = splitter_v->mode_absolute.
call method splitter_v->set_row_height
exporting id = 1
height = c_height.
container_top = splitter_v->get_container( row = 1 column = 1 ).
container_bottom = splitter_v->get_container( row = 2 column = 1 ).
create object picture
exporting parent = container_top.
create object tree
exporting parent = container_bottom
node_selection_mode =
cl_gui_simple_tree=>node_sel_mode_single.
create object event_handler
exporting container = container_right.
event-eventid = cl_gui_simple_tree=>eventid_node_double_click.
event-appl_event = ' '. "system event, does not trigger PAI
append event to events.
call method tree->set_registered_events
exporting events = events.
clear: event, events[].
event-eventid = cl_gui_picture=>eventid_picture_dblclick.
event-appl_event = ' '. "system event, does not trigger PAI
append event to events.
call method picture->set_registered_events
exporting events = events.
set handler: event_handler->handle_node_double_click for tree,
event_handler->handle_picture_double_click for picture.
call method: me->fill_picture,
me->fill_tree.
endmethod.
method fill_picture.
call method:
picture->load_picture_from_sap_icons exporting icon = '@J4@',
picture->set_display_mode
exporting display_mode = picture->display_mode_fit_center.
endmethod.
method fill_tree.
data: node_table type table of abdemonode,
node type abdemonode,
w_pgm type t_pgm,
w_cdat type rdir_cdate,
it_pgm type table of t_pgm,
w_pgmkey type t_pgmkey.
clear: a_id, it_pgmkey[].
select distinct name cdat from trdir into (w_pgm-name, w_cdat)
where cnam = c_me.
w_pgm-year = w_cdat(4).
append w_pgm to it_pgm.
clear w_pgm.
endselect.
sort it_pgm.
node-hidden = ' '. " All nodes are visible,
node-disabled = ' '. " selectable,
node-isfolder = 'X'. " a folder,
node-expander = ' '. " have no '+' sign for expansion.
loop at it_pgm into w_pgm.
at new year.
node-node_key = w_pgm-year.
clear node-relatkey.
clear node-relatship.
node-text = w_pgm-year.
node-n_image = ' '.
node-exp_image = ' '.
append node to node_table.
endat.
at new name.
add 1 to a_id.
node-node_key = w_pgmkey-id = a_id.
w_pgmkey-name = w_pgm-name.
node-relatkey = w_pgm-year.
node-relatship = cl_gui_simple_tree=>relat_last_child.
node-text = w_pgm-name.
node-n_image = '@0P@'.
node-exp_image = '@0P@'.
append w_pgmkey to it_pgmkey.
endat.
append node to node_table.
endloop.
call method tree->add_nodes
exporting table_structure_name = 'ABDEMONODE'
node_table = node_table.
endmethod.
endclass.
class screen_handler implementation.
method constructor.
create object: html_viewer exporting parent = container,
editor exporting parent = container
wordwrap_mode =
cl_gui_textedit=>wordwrap_at_fixed_position
wordwrap_position = 72.
call method: fill_html,
editor->set_readonly_mode exporting readonly_mode = 1.
endmethod.
method handle_node_double_click.
data: w_name type programm,
w_id type i,
w_year(4) type c,
w_pgmkey type t_pgmkey.
w_name = node_key+4.
w_id = w_name.
clear w_name.
read table it_pgmkey into w_pgmkey with key id = w_id
binary search.
if sy-subrc = 0.
w_name = w_pgmkey-name.
endif.
w_year = node_key(4).
if w_name is initial.
call method: fill_html,
html_viewer->set_visible exporting visible = 'X',
editor->set_visible exporting visible = ' '.
else.
call method: fill_src exporting programid = w_name,
editor->set_visible exporting visible = 'X',
html_viewer->set_visible exporting visible = ' '.
endif.
call method cl_gui_cfw=>flush.
endmethod.
method handle_picture_double_click.
call method: fill_html,
html_viewer->set_visible exporting visible = 'X',
editor->set_visible exporting visible = ' '.
call method cl_gui_cfw=>flush.
endmethod.
method fill_html.
call method html_viewer->show_url exporting url = c_myurl.
endmethod.
method fill_src.
types t_line(72) type c.
data src type table of t_line.
read report programid into src.
call method: editor->delete_text,
editor->set_text_as_r3table exporting table = src[].
endmethod.
endclass.
Data *
data this_screen type ref to screen_init.
Program execution *
load-of-program.
call screen 100.
Dialog Modules PBO *
module status_0100 output.
set pf-status 'SCREEN_100'.
set titlebar 'TIT_100'.
this_screen = screen_init=>init_screen( ).
endmodule.
Dialog Modules PAI *
module cancel input.
leave program.
endmodule.
Reward if usefull

What is difference btw serial control uniqueness within inventory model

Similar Messages

Maybe you are looking for