Extending an existing form
Hi there,
for my introduction I have a lousy question:
How do I extend an existing form in SBO ?
(vice versa, how can I hide formelements in an existing form)
I know, I have to capture an event, but which.
Do you have sample code ? Perhaps C#-Code
greetings,
Holger
Hi Holger,
Moreless, you need to catch load event, get the form you need to extend and make the modifications.
Here you have got an example of how to add a checkbox to an existing form. By the way, say that if you are going to make so many changes, you could improve performance saving you extended form into an xml file, and loading it when the estandar form should be loaded. I think there is an example on the help files.
If pVal.FormType = 65 Then
If pVal.EventType = SAPbouiCOM.BoEventTypes.et_FORM_LOAD And Not pVal.BeforeAction Then
Dim oForm As SAPbouiCOM.Form
oForm = con.Forms.Item(FormUID)
CreateControls65(oForm)
End If
End If
Public Sub CreateControls65(ByVal oForm As SAPbouiCOM.Form)
Try
Dim oItem, oBaseItem As SAPbouiCOM.Item
Dim oCheck As SAPbouiCOM.CheckBox
oItem = oForm.Items.Add("chkPrice", SAPbouiCOM.BoFormItemTypes.it_CHECK_BOX)
'Create a base item'
oBaseItem = oForm.Items.Item("14")
oItem.Top = oBaseItem.Top
oItem.Height = oBaseItem.Height
oItem.Width = oBaseItem.Width + 20
oItem.Left = oBaseItem.Left + oBaseItem.Width + 15
oForm.DataSources.UserDataSources.Add("ID" + oForm.UniqueID.Trim(), SAPbouiCOM.BoDataType.dt_SHORT_TEXT, 3)
oCheck = oItem.Specific
oCheck.Caption = "Get Sales Prices"
oCheck.Checked = False
oCheck.DataBind.SetBound(True, "", "ID" + oForm.UniqueID.Trim())
Catch ex As Exception
MsgBox("Found error, msg=" + ex.Message)
End Try
End Sub
Hope this example helps.
Regards,
Ibai Peñ
Similar Messages
-
How to extend an existing IDOC!
tell me the steps to extend the existing IDOC !
Thanks1>we31(create new segments with fields u want to populate)
2>we30(create an extension idoc type).in we30 u will get to radio buttons.1>basic type 2>extension.click on the extension and then copy the basic type.Now will get all the segmnts .Now add the new segments under the parent segement which needs to be extended.
3>attach the extended idoc type to basic type and message type to tcode WE82.
4>Now u have to search for an exit where u have to write ur code in order to populate the fields which u have extended.Basically u will write in the Function module.Make sure u r writing in the correct exit.Evry messagetype will have a function module.
5>create a project in cmod and activate the function exit.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type. Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
First, letâs determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application. It may be necessary to enhance an ALE function module even in situations where an IDOC extension has not been performed if the IDOC data being passed to and from the application requires modifications. The following approach applies to both situations.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Error handling is a very important consideration when making enhancements to inbound ALE/EDI objects. In ALE and EDI inbound processing, workflow is used for handling errors at different levels such as technical and application. If workflow has been configured for the interface, the error messages and workflow items flow to the inbox of the named recipient(s).
It is also critical to enhance the workflow that handles notifications of the inbound ALE/EDI process. In most scenarios this is not a very difficult task because SAP lets you influence the workflow parameters and messages in function exits (customer functions). You typically do this using flags and message codes to trigger certain workflow actions. If you conform to the status codes and flags stipulated for workflow processing, the enhancement could be error-free and seamless. In the case of an inbound IDOC with an extension, you should populate the EDIDC fields IDOCTYP (new IDOC type) and CIMTYP (extension type) accordingly.
IDOC REDUCTIONS
When distributing or communicating master data to other systems, the volumes of data transmitted over communication lines may be large, resulting in performance problems and/or excessive usage of resources such as disk space and bandwidth. Careful scrutiny of the master data Basic IDOC type may reveal that many of the segments are redundant or are simply not being used. If this is true, then the basic IDOC type is a candidate for a technique known as IDOC reduction. The R/3 System provides the ability to eliminate unused segments and irrelevant segment fields from the Basic IDOC type. This procedure is relatively simple and easy to implement. IDOC reduction is available for only a few message types such as DEBMAS, CREMAS, GLMAST, MATMAS, and certain POS messages.
When performing an IDOC reduction, a new message type is created based on an existing message type. The IDOC segments associated with that message type are proposed for editing. Mandatory segments of the IDOC type canât be excluded. By default optional segments are excluded, but you can choose to include an optional segment and only certain fields in the optional segment. If you have extended the Basic IDOC type and created a new IDOC type associated with a corresponding message type and you are creating a new message type (view) based on it for purposes of IDOC reduction, then the enhanced IDOC type is presented for editing along with the additional segments.
Letâs use the Vendor Master IDOC type CREMAS01 as an example to demonstrate IDOC reduction. Message type CREMAS is used for communicating Vendor Master data to other R/3 or external systems. If you browse the IDOC type CREMAS01 youâll see that it has 10 segments, with E1LFA1M being a mandatory segment (see Figure 6). To reduce this IDOC type:
Use transaction BD53 or from SALE go to Distribution scenarios -> Master data distribution -> Reduce IDOC type for master data.
Enter ZCREMS for View (message type).
Click on Create.
You will see a pop-up box. Enter CREMAS in the Derived From field. Enter.
Enter a description. Enter.
You will see a list display with segment E1LFA1M in green and a * symbol. The symbols used in IDOC reduction are: * for mandatory, 1 for selected, - for deselected, x for core selected, and the Î.â for core not selected. The corresponding elements are highlighted in green, white, red, violet, and gray, respectively.
Expand all trees. You will see nine other segments in red.
Place your cursor on the E1LFB1M segment for company code data and click on Select. It turns white with a 1 symbol.
Double-clicking on it will display a list of fields. You can select fields that you require (see Figure 7).
Note that if a child segment is selected, its parent is also selected automatically in order to maintain the hierarchical integrity.
After youâve selected the segments required and its fields, save.
From the main screen, click on Activate.
Activating the new message type ZCREMS will turn on the message type change pointer generation on a particular client. While creating a reduced IDOC type message is a client-independent activity, activation is client-dependent. An entry is created in table TBDA2 for a specific message type in a specific client and is activated. To delete this message type, you need to deactivate it from all clients on that instance. These message types are transportable.
Now that weâve created a new message type for a reduced IDOC type, letâs build the rest of the ALE configuration to work the interface with the following steps:
Define a logical system to represent the other R/3 or external system.
Configure the Customer Distribution Model to send message ZCREMS to this logical system.
Define a port, if needed, for this system.
Define a partner profile based on the logical system and maintain its outbound parameters. Make sure to use ZCREMS as the message type and CREMAS01 as the IDOC type.
Use transaction BD14 or execute program RBDSECRE or from BALE go to Master Data -> Vendors -> Send. Then, to specify a vendor or range of vendors and enter message type, go to ZCREMS and its target logical system.
Execute.
You can also capture changes to Vendor Master data and create IDOCs by executing transaction BD21 or program RBDMIDOC. Use transaction WE02 or WE05 to view the IDOCs created as a result of the preceding test. Notice the segments populated and the basic segments that are absent due to the reduction. You will find that the fields deselected from the segments have a value of /. This is equivalent to a null value. Eliminating segments may result in saving resources, while eliminating fields may not, unless the data is compressed. Also, if you look at the master data ALE function modules for these few message types, youâll see that a function module IDOC_REDUCTION_FIELD_REDUCE is called for every segment being populated. This in itself may be an overhead. It is important to weigh the pros and cons before implementing IDOC reduction. Of course, in certain cases, it may be a necessity for adjustment of data.
Enhancing ALE/EDI and IDOC extensions and conducting IDOC reductions is fairly simple. However, before proceeding with these tasks, you must carefully research the many options available in ALE and develop the best design for your business scenario.
IMPLEMENTING BAPI WITH ALE: A SAMPLE SCENARIO
Business application programming interfaces (BAPIs) provide an interface to Business Objects in the R/3 System. Business Objects are based on object-oriented technologies and represent an application objects, such as an address or a sales order. This next section prototypes an ALE interface that incorporates BAPI methods. When weâve finished, you should have a good idea of how easy it is to incorporate BAPIs with ALE and of how beneficial leveraging the 1000+ BAPIs available in the R/3 System can be when you want to interface with R/3 application objects.
Letâs start with a brief overview of SAP Business Objects and BAPIs.
SAP Business Objects. An SAP Business Object envelopes R/3 data and business processes while making the details of data structure and access methods transparent to a user interfacing with it. It consists of four layers: kernel, integrity layer, interface layer, and access layer. The kernel represents the R/3 data and its attributes. The integrity layer represents the business logic of the object and contains the business rules that govern the values of the kernel. The interface layer describes the interface mechanisms to external applications. BAPIs belong to the interface layer. The access layer represents communication methods, such as COM/DCOM, RFC, and CORBA.
SAP Business Objects and their details are stored in the Business Object Repository in the R/3 System.
BAPIs. BAPIs are "methods" of SAP Business Objects and represent their interface layer. BAPIs are essentially function modules in the R/3 System that are capable of invoking remote function calls (RFCs) for the purpose of communicating data through the function moduleâs import/export parameters and internal tables. BAPIs do not invoke screen dialogs. Like blackbox technology, BAPIs do not require the programmer or user to know the coding and implementation details of the interface to the Business Object. The user simply invokes the BAPI with its appropriate parameters and values in order to accomplish a task such as getting a list of materials from an external system or sending a list of contact person details to another system.
BAPIs can be executed synchronously or asynchronously while using the ALE communication layer for exchanging data. Typically, with asynchronous BAPI communications, an ALE IDOC is used to distribute the data. As we will learn in the following prototype, the ALE distribution model has to be configured in order to use the appropriate BAPI methods for the RFC destination that provides a gateway to the external system (R/3 or other). For this type of communication, an ALE IDOC interface must exist. If a particular BAPI (SAP-delivered or user-written) does not have an ALE IDOC interface, the interface can be generated using certain R/3 tools and procedures.
BAPIs are fast becoming the communication standard for exchanging data between business systems (including R/3). SAP Business Objects conform to Open Application Group (OAG) standards, and BAPIs support the COM/DCOM and CORBA guidelines. ALE and BAPIs is the strategic direction for all SAP interface technologies and will replace SAPâs traditional techniques in the future.
A BAPI/ALE PROTOTYPE ÷ CONTACT PERSON DETAILS
In the previous section, we learned how to enhance ALE functionality using the example of Customer Contact Person details. We extended the IDOC and enhanced a customer function with a few lines of ABAP code to achieve the additional functionality of distributing contact person details. While this was an exercise to learn IDOC extensions and customer-function enhancements, we can prototype a BAPI/ALE interface in this section that accomplishes the same purpose ÷ the distribution of contact person details. In release 4.5 of the R/3 System, message type ADR3MAS and IDOC type ADR3MAS01 have been provided to distribute contact person details with the aid of a BAPI method. The steps weâll walk through in a moment will illustrate the ease with which we can integrate BAPIs with ALE to get an interface up and running for many standard business scenarios or specialized cases that were not supported by ALE prior to the advent of BAPIs.
The ADR3MAS is considered to be a master data message type because it complements business master data, such as customer and vendor master. It is now supported by change document functionality, implying that change pointer mechanisms can be used to capture and then distribute changes occurring to contact person data using ALE IDOCs. The function module that accesses the R/3 data is a BAPI. In the R/3 System, contact person address is a business object. If we search the Business Object Repository (via transaction SWO1) with the keyword "address," for example, we will find business object BUS4003 under Cross-Application Components -> General Application Functions -> Address Management -> BUS4003: Address of a person in a company. This is the business object that pertains to our scenario, and a drill down on it reveals the details of the object, including its methods (see Figure 8). The method that would be of interest to us is "AddressContPart.SaveReplica." For your information, the corresponding BAPI function module is BAPI_ADDRCONTPART_ SAVEREPLICA in the function group SZAM.
Having gathered this information, Letâs build the outbound interface:
Create a logical system (via transaction SALE) to represent the receiver system.
Configure the distribution model. From transaction SALE, use option Maintain Distribution Model to create a model view for this scenario. Specify the sender system (the base logical system for the client you are working in, such as the logical system that has been assigned to that client) and the receiver system (the logical system). After positioning the cursor on the receiver system, click on Method and enter AddressContPart in the Object Name field on the panel that pops up. Also enter SaveReplica in the Method field on the pop-up panel. Enter and save the Distribution Model (see Figure 9).
From transaction WE20, create a partner profile based on the logical system for the interface. Use message type ADR3MAS and IDOC type ADR3MAS01, with an appropriate port.
Activate the change pointer for message type ADR3MAS. From SALE go to Set up Data Distribution -> Master Data Distribution -> Activate Change Pointers. Ensure that change pointer generation is active at the general level as well.
Now that weâve completed the configuration, letâs test the interface. The purpose of this test is only to create outbound IDOCs. Appropriate settings, such as port definitions and RFC destinations, can be made as required for purposes of communicating the IDOCs to the external system (or other R/3 system).
From the Customer Master or Vendor Master screens, create or make changes to contact person address. This should result in the creation of change pointers. (Check table BDCPS for change pointer entries with message type ADR3MAS.) After this, from transaction BALE go to Periodic Processing -> Process Change Pointers, enter ADR3MAS as the message type, and execute the transaction. This should result in a message indicating the number of master IDOCs created. Use transaction WE05 to display the IDOCs.
THE ALE AUDIT
In this section letâs take a look at the prototyping of the ALE Audit. ALE Audit is a powerful mechanism for verifying the success of ALE transactions/messages sent to another system. As you will see, implementing ALE Audit is not only easy but also very beneficial, because it facilitates the monitoring and tracking of transactions across systems while providing an entry point into error handling.
Program RBDSTATE is used for audit confirmation of ALE transactions between two R/3 systems; in other words, it indicates the success or failure of the ALE transaction on the target system. The program reports the status of the transaction on the target system back to the sending system. This process also serves as an interface itself from the target system to the sender system, facilitated by message type ALEAUD. In the following section, weâll look at the various steps needed to set up ALEAUD and execute program RBDSTATE.
SETTING UP ALEAUD and EXECUTING PROGRAM RDBSTATE
Letâs consider two different R/3 systems with base logical systems BK1CLNT010 (sender system) and BK2CLNT020 (target system). Assume that you are distributing characteristics master (message type CHRMAS) from BK1CLNT010 to BK2CLNT020. When you send CHRMAS02 IDOCs from BK1CLNT010, their status is 03 (data passed to port OK) if they were successfully externalized from the sender system. If the IDOCs were received and processed successfully on the target system, the status of those IDOCs on the target system is 53 (application data posted). Remember that you have to create a partner profile for BK1CLNT010 on the target system in order to receive the CHRMAS messages. The inbound parameters of BK1CLNT010 partner on the target system have CHRMAS as the message type and CHRM as the process code.
You now need to configure BK2CLNT020 to send ALEAUD messages to BK1CLNT010, the sender system. And you also need to configure BK1CLNT010 to receive those messages in order to update the status of CHRMAS IDOCs sent to the target system:
On the target system BK2CLNT020, configure the distribution of message flow of type ALEAUD to logical system BK1CLNT010.
Create filter object using object type MESTYP with a value of the message type for which you need audit confirmation. This message type must flow from the sender, BK1CLNT010 to BK2CLNT020. In this example, the value of the filter object type MESTYP is CHRMAS, message type for characteristics master. Save the distribution model. Use transaction BD64 to do this.
On target system BK2CLNT020, create an RFC destination with name BK1CLNT010. Choose the relevant connection type and enter the logon parameters and password for the R/3 system on which BK1CLNT010 resides. Use transaction SM59 to do this.
On target system BK2CLNT020, generate partner profile and port definition using transaction SALE, go to Communications -> Generate partner profile. Specify the customer model as described. Check the partner profile to ensure outbound parameter entries for message types ALEAUD and SYNCH.
On sender system BK1CLNT010, create a logical system for BK2CLNT020. Create a partner profile for logical system BK2CLNT020 with inbound parameters for message type ALEAUD, with process code AUD1.
Distribution of customer model on BK2CLNT020 to BK1CLNT010 is not necessary.
TESTING THE ALE CONFIRMATION PROCESS
Now you are ready to test the ALE audit confirmation process:
From the sender system, BK1CLNT010, send a couple of CHRMAS02 (characteristics master) IDOCs down to the target system, BK2CLNT020. Make sure that the status of the IDOCs is 03 (data passed to port).
Check the target system for receipt of these IDOCs. Make sure that they are in a status of 53 (application data posted).
Execute program RBDSTATE with appropriate parameters. Specify BK1CLNT010 for Confirm to System, CHRMAS for Message type, and date, if necessary.
Upon successful execution, informational messages will be issued indicating the IDOC number and status of the ALEAUD IDOC. (Note that a single ALEAUD audit IDOC can contain audit messages for multiple application IDOCs. This capability reduces the traffic of IDOCs between the two systems and keeps the overhead of audit confirmations at a minimum.)
Check the sender system for the receipt of the ALEAUD message. The status of the CHRMAS IDOCs that you sent to the target system must be changed to 41 (application document created in target system).
This completes the test of ALE audit confirmations (see Figure 10 and Figure 11 for IDOC display of target and sender system).
Audit confirmations can play a significant role in the reporting and monitoring of production systems. You can schedule program RBDSTATE periodically on target systems to report back to sender systems. Keep in mind that you need to maintain a sufficient time lag between the sending of application IDOCs to the target system and the execution of this audit program because the application documents need to be posted on the target system. This program can also be accessed from BALE using Periodic work -> Audit confirmation. -
How many Airport devices do I need to extend an existing network?
Hello all,
I hope one of you might be able to help me with a problem.
I recently just moved to a different apartment, and my router (from my local internet provider) does not reach to all the rooms in the apartment.
Since I also wanted to stream wireless music in my home office I read that the Airport express would be a great solution to both extend the existing network and stream wireless from my Apple products.
I went to buy the Airport express, and asked the guy in the local authorized reseller of Apple products, if I could use this without connecting it via cables to my router (hence using it via wifi only). And he said yes, which I believed. However, after trying to set it up, and failed. I started searching for questions about my issue.
So:
Do I need two airport devices if I want to extend my existing network, when the router is in the living room, and the speakers that I want to stream from are located in my home office in the other end of the apartment? The area that I want to extend the existing network to is the bed room, next to the office.
So I thought that I could set the Airport express up in my office and connect it to the mini-jack from the speakers, and voila it would just do as I wanted to. But since I'm not a technical expert, I might have misunderstood, and I really do not want long ethernet cables running all over the place.
Is the only solution then to buy two devices? (Oh and for your information, I am not able to move the router to the office since there is no outlet for the internet, the only place it can be set up is in the living room).
Hope someone can help enlighten me on this issue. Thank you :-)You need two AirPorts if you want to wirelessly "extend" the network, which will provide more wireless coverage....since both AirPorts will be broadcasting a wireless network.
You only need one AirPort Express if all that you want to do is use it for AirPlay to pick up the wireless signal and "join" your existing wireless network. In order to do this, the Express must be able to receive a good wireless signal from your router.
To test if you have a good signal, take a laptop or mobile device to the area where you want to install the AirPort Express and check to make sure that you can get a good wireless connection at that location. If you can, then the AirPort Express should work well at the same point. -
How do I add a field into an existing form in SharePoint Designer 2010 and...?
I'm trying to add an existing field to an existing form in SharePoint Designer 2010. It's a URL to the employee's photo. But each time I try to "Insert as picture" the url to the photo has a trailing comma. Why and more importantly, how do I get
rid of it?
Thanks!Hello,
See this similar thread:
http://sharepoint.stackexchange.com/questions/10149/comma-in-url-field
Hope it could help
Hemendra:Yesterday is just a memory,Tomorrow we may never see
Please remember to mark the replies as answers if they help and unmark them if they provide no help -
I want to extend my existing wireless router by using the AirPort Express for my Smart TV. Can I just plug in the AirPort halfway between the router and the Smart TV and have no direct connection to a computer or the TV, or do I need to plug in next to the TV and somehow connect the AirPort to the TV (ethernet)?
You are asking several different questions. If you need to store your photos, music, and movies on an external volume, you certainly can. Any externally connected hard disk drive will work, connected either directly to your Mac or to your Time Capsule as a shared volume.
You should not rely upon using that as a backup device though. Although you certainly may use it for both purposes, it is a better idea to have dedicated backup devices for a variety of reasons not limited to redundancy. You would not want to simultaneously lose all your pictures as well as your backup. If they are all on the same device, that could happen. Furthermore, a backup cannot back up the volume on which it is running.
As for adding an Extreme or Express, using its LAN port for your iMac, and then enable Internet sharing so you can effectively use the iMac as a "hotspot", you can do that too, but I am unclear on what benefit you believe this arrangement would convey for you.
An Extreme's Guest network is separate from its Main network; that is the reason for having it. -
How do you create a custom button in LiveCycle to add a new form page to an existing form?
Can someone tell me how to create a button to add a new form page to an existing form in Acrobat or Livecycle designer?
Hi,
You can use addInstance method to achieve your requiremnets.
form1.#subform[1].instanceManager.addInstance()
BR,
Paul Butenko -
How do I extend my existent airport extreme network by addition of a 2nd airport extreme?
How do I extend my existent Airport Extreme network by addition of a 2nd Airport Extreme?
Can you clarify which version of the AirPort Extreme that you have now along with the model that you plan to use as the second device?
The older "round" AirPort Exteme or the newer "square" version with rounded corners?
Are you planning to extend using wireless only.....or by connecting the AirPort Extremes using a wired Ethernet connection? -
Can someone tell me how to create a button to add a new form page to an existing form in Acrobat or Livecycle designer?
In Acrobat forms you can use the 'template' object's 'spawn' metod. A Lesson in Templates for Adobe Acrobat by Dave Wrigtht
-
Extending the existing functional locations to a new plant?
Hi Sapiens,
The following is my concern:
Q1) I have a set of functional locations(roughly around 5000 records) assigned to say Plant A.
I would like to extend these existing functional locations to Plant B. I am not permitted to do this using LSMW. I should execute this operation in one shot.
How to accomplish this?
Q2) After attaching all the functional locations to Plant B, i should replace the first 4 characters of the functional location structure with the Plant Code itself. Again not through an lsmw. How to accomplish this in one shot?
Please let me know the procedure of doing it with some guidelines.
Thanks in Advance,
VijayaHi
1. You can extentd to the other plant with SCAT ,BDC etc
2. But You can not replace the first four letters from the FL with the New plant code.Remember this is a master data
Regardas
Jignesh -
310N extending an existing network
I am trying to extend my existing network. I currently have the cable modem plugged into an older Linksys wireless router which works fine, from there I have wires going out to other parts of the house and a Linksys switch providing extra ports.One of the wires goes to the office upstairs, where I am trying to install a 310N to extend the reach of my wireless. I am willing to set it up as a separate wireless network.
I plugged the 310 into the switch and I got an IP address for a second, but I couldn't ping down to the first router from the computer. I reconfigured the 310 putting it on a different subnet, connecting the cable from the downstairs router to the WAN, to a normal port. I could not get it to work. I am fine using the 310 as a switch or a hub, I just need the extra wireless coverage.
Any suggestions?Follow this link
-
Hello,
Which setting should I used to extend my existing network?
Should I set the Airport Express to JOIN AN EXISTING WIRELESS NETWORK (CLIENT)?
Anything else I need to do to extend the range of my network?
Thank you,
JuhaNo problem.
Try the following ...
Set up a Wireless Distribution System (WDS)
(Note: To facilitate the WDS set up, place the base stations in near proximity of each other during the initial configuration phase. Be sure to jot down the AirPort ID MAC addresses for each of the base station that will be used in the WDS.)
Main Base Station Setup - AEBS
Either connect to the AirPort Extreme Base Station's (AEBS) wireless network, or, temporarily, connect directly (using an Ethernet cable) to the LAN port of the AEBS, and then, use the AirPort Admin Utility (located in /Applications/Utilities), in manual mode, to make the following settings.
WDS Tab
o Enable this base station as a WDS: main base station (checked)
o Allow wireless clients on this base station (optional)
o Click "+" to add a Remote base station.
o Select the base station that you want as the WDS Remote. This should be your AirPort Express Base Station (AX).
o AirPort ID: <verify that this is the correct wireless MAC address for the AX>
o Auto configure as a WDS remote base station (checked)
o Click "OK."
o Verify that the AX has been added to the list.
o Click "Update," and then verify the settings for the Remote.
o Allow wireless clients on this base station (checked)
o New network name: <verify that this is the same as the network name for the AEBS>
o TCP/IP: Configure using DHCP
o Base Station Password: <the AX's base station password if you're using one>
o Confirm: <same as previous step>
o Click "OK." -
SAPSCRIPT: Creating new Language for existing form
Hi Guys,
I need add an additional language for an existing form. Italian is not available for the this existing form. How can I add this language? do I need to copy the form with language EN? how can I include that form in the existing form? or there are other way to do this? Thanks in advance!
Regards,
Michael NacionalesThere is a change in the standard code.The reason for the above problem was because of a missing Enhancemnet point in a standard function module 'CV110_DOC_CREATE_WITH_TEMPLATE'.
IS-ADEC-MPD - Enhancement to copy MPD data
ENHANCEMENT-POINT CV110_DOC_CREATE_WTEMPL_01 SPOTS ES_SAPLCV110.
+*$*$-Start: CV110_DOC_CREATE_WTEMPL_01----------------------------------------------------------$*$*+
+**ENHANCEMENT 1 ZSF_AD_MPD_SAPLCV110. "active version**+
+*** copy MPD relevant data from templ. doc to current doc**+
+**CALL FUNCTION 'MPD02_COPY_MPD_DATA'**+
+**EXPORTING**+
+**is_draw = ls_draw**+
+**TABLES**+
+**ct_drad = lt_drad.**+
+*ENDENHANCEMENT.**$*$-End: CV110_DOC_CREATE_WTEMPL_01----------------------------------------------------------$*$*+
Created a custom enhancement point similar to SAP ECC6.0 EHP 3.0 system.
The reason was the buffer was not getting cleared previously.After inserting the above code the DIR's are getting created withot any issues.
Regards,
Prasad.B -
Multiple List Box showing Duplicate Options in Existing Form Library forms.
Good day. I currently have an InfoPath 2010 form library template that has a view containing 4 multiple selection list boxes. These list boxes get their values from a hidden view that contains 4 repeating tables in which I've set default values
for Value and Display name to populate the multiple selection list boxes.
The issue I am having is this: When adding new options to the repeating tables through the Default Values option window and publish, new forms display the new selection options successfully, while existing forms in the library when opened are displayed duplicates
of the first default value in the table in the place of the new options. (Example, Create Data[display] - 10[value] is displaying 4 times after adding 3 new options to the characteristics table that contains Create Data as it's first row item.)
When comparing the .XML of a new form to an existing form, groupX in this case shows all options in the new form .XML, but shows the duplicates in the .XML of an existing .XML file.
Is there a way to resolve this issue so that existing documents will display the proper selection options instead of the duplicates? I'd like to note that another list box had a value added and it displayed the value properly when published in both
new and existing forms.
Thanks!Hi Hemendra:
There are no rules on Section A.
Two out of three forms used so far by the users have these problems.
We did extensive trending study on all the submitted forms on both where the submit was successful and ones with Section A frozen up. Also, requested a user to submit a few forms per our instructions on different browsers. Even though there are some
forms in the past which could be claimed as success has some attachment uploaded to the Section A of the form, currently every time an attempt by any usetr to attach a smallest document the section A, it wipes out all the existing completed fields and freezes
up all the rest of the controls of that section and not any other part of the form.
Thanks,
SRA
SRAEngineer -
Hi,
Is it possible to modify an existing form of SAP Business One? For example if one needs to put an extra button on the form of outgoing payments.
Can anyone guide for the process.
Many thanks in advance.Hello Afzal,
It is definitely possible. Refer to SDK Help, samples are provided in it.
Also, post your questions, related to programming, on SDK programming forum.
Rahul -
Modifying an existing form in SAP B1
Hi everyone,
Is there any way to modify an existing form in SAP B1? If so can any one describe the complete procedure of doing that?Will highly appreciate it.Hi,
Its more advisable to do it in the Menu Event rather than the Form_Load event and its got to be done in the Before_Action = False.
In Menu Event,
paste this...
If pVal.BeforeAction = False Then
Dim objNewItem As SAPbouiCOM.Item
objItem = objForm.Items.Item("51")
objNewItem = objForm.Items.Add("cbSQ", SAPbouiCOM.BoFormItemTypes.it_CHECK_BOX)
objNewItem.Left = objItem.Left + objItem.Width + 10
objNewItem.Top = objItem.Top
objNewItem.Width = objItem.Width
objNewItem.Height = objItem.Height
objNewItem.FromPane = "5"
objNewItem.ToPane = "6"
objCheckBox = objForm.Items.Item("cbSQ").Specific
objCheckBox.Caption = "Sales Quotation"
objNewItem.Visible = False
objCheckBox = objForm.Items.Item("cbSQ").Specific
objCheckBox.DataBind.SetBound(True, "", "01")
Endif
The above is a small snippet for the addition of a checkbox.
Hope this helps.
Satish.
Maybe you are looking for
-
Real tough data retrieval - assistance needed
Late 2011 Macbook Pro with 500GB hard drive Lion 10.7 One morning out of absolutely nowhere I get this grey screen with a flashing question mark folder. I take it to the geniuses at the Apple store and they tell me my hard drive has failed (no explan
-
Trying to add a flowable/expandable text field to the end of a form
I have created a form in LiveCycle Designer. At the end of that form, I would like a Summary text box that expands to allow the person who is filling out the form to type as much information as is necessary and it will all be visible/print when they
-
HELP Application Server PE 9 - DocumentBuilderFactoryImpl not found
i getting this error in a Servlet. The same code work fine in a stand-alone local application written in NetBeans IDE... see the code : try{ src.getDocumentElement().normalize(); NodeList listOfJDBC = src.getDocumentElement().getElementsByT
-
If I delete photos in "iPhoto" will those photos also delete in the application "Photos"
Hey guys! I was wondering if I delete photos in "iPhoto" will those photos also delete in the new application "Photos". I transfered all my photos to "Photos" the second it came out, so I'd find it strange if I still needed "iPhoto" Thanks a lot!
-
Multiple Applications in Parent Controlled User Account
I've been running Mac for a while but this is the first time I've set up a second user. I'm also not as Mac savvy as a lot of you are on here but I can make my way around, so please be patient with me if I ask a silly question or two. In setting up